suse-list@fresno.edu wrote:
On Friday 01 October 2004 05:01 pm, Rob Brandt wrote:
I'm getting a SuSE 9.1 installation ready to be used as a mail server for a client.
I've done the complete 9.1 installation and update. I have postfix running, and it can send mail to my regular mail accounts. I'm trying to get pop & imap services running and am getting nowhere. I have all varieties of pop & imap up, and the proper ports are listening on the server. However, I can retrieve mail neither from a networked workstation or even locally on the machine itself. I'm using regular linux user accounts (no virtual). I've tried various password authentication types in case there were some encryption running that I wasn't aware of. I've reset my password to be sure I know what it is. Nothing seems to help here.
Can't get mail locally? Are you setting up your local mail retrieval as a pop3 or a maildir or what?
Tail (with -f) your /var/log/mail and /var/log/messages files as you try to pop the mail from another workstation and see what it says when the request arrives. Pop is usually started from inetd or xinetd, so check them too...
See if this link helps you set up a mail server. It does help a little.
When I was installing an e-mail server with suse 9.0, I spent *hours* to properly set it up (was migrating from an old RedHat). The fact that the RH was running fine with postfix, amavis, imap, etc was an indication to me that the migration should be easy, as I had a reference system. In fact, this reference it was almost useless, for no good reason. Things I learned the hard way: * imap runs normally, but refuses to accept any password from any user. SuSE modified it to accept only imaps (even locally) - so, why imap is still there??? * amavis rpm installed without warning, but added itself to postfix (without warning or telling it to me). All mails started to be rejected - Why? Where is amavisd logs??? (Tip: /var/cache/amavis/amavis.log !). Later, I discovered that without an known AV, amavis reject every e-mail (incoming and outgoing). * random problems receiving e-mail, writing it to nowhere: it was accepting mails, but it was never written to the mailbox file. Perhaps wrong main.cf, don't remember what caused it. * create your site certificate - aside the fact that I had to know that I had to create a site certificate to use ssl, it was documented at /usr/share/doc/packages/* Check these at yours and see these points. Some other problems (extra white page from lpr, logrotate didn't worked properly, strange 'failed' messages at boot indicating services that were started fine, lots of problems installing mailman - suse rpm, openoffice java dependency error, etc) caused me a lot of headaches, and my final impression of suse was somewhat bad - at the end of that day, it was *very* bad... :-) I know, living near the edge, installing recent released suse version can cause some troubles... that's the price. But unless you have some time to play with it, I don't recommend suse professional to be installed (for the first time) in a server... At least, I don't plan to do it soon... -- Marcos Lazarini