Index: [Article Count Order] [Thread]

Date:  Wed, 18 Jul 2007 21:09:11 -0700
From:  "T. Jay Fowler" <tjay (at mark) lowbrow.com>
Subject:  [coba-e:10413] Pop/poprelayd/dovecot/etc.
To:  BlueQuartz <coba-e (at mark) bluequartz.org>
Message-Id:  <8781210D-A10F-4642-AEFA-E892F4EAE991 (at mark) lowbrow.com>
X-Mail-Count: 10413

Hello,

I'm trying to reconstruct the changes that happened over the last  
year to BQ, specifically in the pop realm.  With a major update  
several months ago it looked like poprealyd was depricated. Upon  
reboot, my machine refused to accept all outgoing mail from my users  
mail clients, but would allow mail to flow freely to them (they could  
pop in).  I did realtime trobleshooting -- using the gui (clicking,  
unclicking pop/smtp auth and submission port, etc.) and command line  
and eventually figured out that poprelayd wasn't running and outbound  
mail started flowing again.

Several months go by and I need to reboot, mail stops again. I do a  
chkconfig and notice that poprelayd is not enabled.

I also noticed that dovecot was installed, and now notice in my  
logwatch that dovecot sessions are opened by users.

My question: how does this new stack behave. The old stack worked  
like this:

client -- pop3 -- mail comes to client
client sends mail -- poprelayd checks to see if the ip is in the db  
-- accepts connections

How does the new dovecot-integrated world work?  And do I have  
partial install or bad config if dovecot was a drop-in replacement  
for the former config?

Help appreciated.


t(dot)jay fowler
tjay (at mark) lowbrow.com