Thanks for the tips. I created the tcp.pop3 file, and ran "qmailctl cdb" - but it didn't really do anything for pop3. I rechecked the LWQ documentation to ensure I wasn't supposed to add something to the cdb part of the script (didn't need too).
Then I had an epiphany. I should try to ssh to the server as my user and make sure mail was flowing still. Low and behold, I couldn't log in - the password didn't seem to be working. Ran passwd for the account (as root), and voila - pop3 is working as expected. So now I've created the 4 other accounts I needed, and they seem to be fine too. Sometimes, it's the simplest things..... Now, to get Antivirus and SpamAssassin running. Shawn -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Hendrik Schaink Sent: Sunday, February 08, 2004 3:14 PM To: CLUG General Subject: Re: [clug-talk] Help with Qmail? Hi Shawn, The qmail pop3 daemon needs a similar tcpserver access configuration as the smtp daemon. Remember how you had to configure tcpserver for smtp so that clients on your network could send e-mail using the config file "tcp.smpt" with lines 127.:allow, RELAYCLIENT="" 192.168.1.:allow; RELAYCLIENT="" You need to configure tcpserver in a similar fashion so that clients on your network can log into your pop3 server. In the same directory as tcp.smtp, create a file called tcp.pop3 with the following lines: 127.:allow 192.168.1.:allow :deny and put this into service using the same type of control that you used for tcp.smtp. Hope this helps getting you started. Hendrik Schaink Shawn wrote: >After Jeff's presentation on Qmail at the last meeting, I decided to try >Qmail on my new server installation. It's been "fun" - trying to use the >Life With Qmail guide on a Gentoo server that does the compilation part of >the install for you. Then, having to try and find what parts of the >procedure the compilation process (via the "emerge" command) has missed. >But, I think I got it. I'm able to send mail out from my console and >receive mail in (using mutt to test outgoing/incoming mail to my user >account). > >Pop3 is giving me problems though. My user account is configured the exact >same way it was on my previous server (same username/password). I've >started the POP3 processes, and a "nmap localhost" reveals that port 110 is >open. (just occured to me that I didn't verify it was Qmail opening the port >though - I'll check this in a bit). I'm trying to connect to the pop3 >server via MS Outlook on my Win2K box - but I'm getting a consistent >authentication failure. Not knowing enough about Qmail (yet), I'm hoping >someone on the list can point me in the right direction here. Which files >should I be checking? When I run qmailctl start/stop, I don't see any >errors reported (the script has been modifed as per the LWQ guide to include >the required pop3 commands). > >Getting email running on my new server is the only thing that's holding me >back from doing a wholesale migration to it. > >Any help is appreciated. Thanks. > >Shawn > > >_______________________________________________ >clug-talk mailing list >[EMAIL PROTECTED] >http://clug.ca/mailman/listinfo/clug-talk_clug.ca > > > -- Hendrik M. Schaink Chief Consultant "Integrated Business Solutions & Dependable Service" InfoVision Consulting Calgary, Alberta, Canada Phone: (403) 239-0099 "The Vision: We are the partners of choice for companies and organizations that share our commitment to creating a world that is truly wise, courageous, prosperous, innovative, inclusive, sustainable and humane." --Ruben Nelson _______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca _______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
