Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
sounds like a domains issue. To avoid spam, mail servers don't take mail from anyone - they are fussy (who the hell are you?). Those that take mail from anyone and forward it are called open relays, and blacklisted.
If this is just you at home, laziest way through is to pretend to be on your isp's domain. If your mail server thinks it's isp.com, mail will flow to isp.com and email@example.com will usually work
Sorry, I should have elaborated better. I am currently connected to a closed LAN network for testing purposes, so I am trying to send mail locally from one client to the server, but right now I'm trying to send mail from the server itself.
Alright, so I went and researched a bit about the dovecot service and it seems like I have not configured anything in that dovecot.conf, so I went and removed some commented lines.
I also modified the Evolution settings a bit:
Email Address: firstname.lastname@example.org
Server Type: IMAP
Use Secure Connection: No Encryption
Authentication Type: DIGEST-MD5
[checked] Override server-supplied folder namespace
Server Type: SMTP
[checked] Server requires authentication
Use Secure Connection: No encryption
Authentication Type: DIGEST-MD5
In webmin, I have these settings in the Read User Mail module:
Mail server installed: Sendmail
Send mail using: SMTP server: 188.8.131.52
SMTP login name for mail server: smtp
SMTP password for mail server: 123456
SMTP authentication method: Digest-MD5
I can start the sendmail service without problems, but when I try to start or restart dovecot, I get the following:
Stopping Dovecot Imap: [FAILED]
Starting Dovecot Imap: Warning: Last died with error (see error log for more information): Auth process died too early - shutting down [OK]
Then, I go to the maillog and this entry comes up last:
Apr 5 01:30:09 linuxserver dovecot: dovecot v1.1.20 starting up (core dumps disabled)
Apr 5 01:30:10 linuxserver dovecot: Fatal: auth(default): APOP mechanism can't be supported with given passdbs
Apr 5 01:30:10 linuxserver dovecot: Auth process died too early - shuttng down
I'm not sure what I can do to make dovecot start normally, but I also don't know what passdbs is or does?
I'm sure that DIGEST-MD5 is supported, because there is a little button next to the authentication type box that checks which ones are not supported and it crosses them out.
I tried other supported types though, and it still gives me an error.
The exact error I'm currently getting when I try to send a mail from Webmin:
Anyway, I wanted to say thanks for the help guys, but it looks like we're scrapping the whole mail server thing since we're having too many problems and its taking too long. So we'll just stick with apache and FTP since those are working fine.
May I say a word here about mail servers?
Postfix seems to me to be one of the easiest to configure. You would be ready for a home for the bewildered before you stand that up - take it from someone who did. On linuxfromscratch.org blfs section there is a compile & configure for postfix that should get you up pretty quick. They also have stuff on all the main pop, imap stuff and hints.
It would be worth a telnet host 25 / nc host 25 and an EHLO to see if it offers DIGEST. If it does, it would then be worth seeing if you can do this by hand - just to rule out Evolution being buggy. I had issues with the check box for 'remember password' screwing with the login settings a while back.
You had some problems with authentication on the smtp server. Probably because the DIGEST-MD5 wasn't set up properly. I haven't used Postfix, or indeed anything but sendmail really. I have to say that looking after a mail server is a lot more work than either ftp or apache.