5 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Problems connecti...
FromSent OnAttachments
Greg EarleJun 27, 2005 12:14 pm 
Sam VarshavchikJun 27, 2005 12:26 pm 
Randall ShawJun 27, 2005 12:28 pm 
Greg EarleJun 27, 2005 2:56 pm 
Randall ShawJun 27, 2005 3:29 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Problems connecting to authdaemon after upgrading (0.44.2 -> 0.50.0) Actions...
From:Randall Shaw (cour@randallshaw.com)
Date:Jun 27, 2005 3:29:50 pm
List:net.sourceforge.lists.courier-users

Greg Earle scribbled something like:

I'm on Solaris 9. No ntsysv or rc.local stuff - all /etc/init.d scripts.

I got authdaemon started manually (will check for an init script now, thanks), but have a new problem - mail comes in, "submit" gets called, everything looks OK, "courieresmtpd" logs a message:

Jun 27 13:34:01 isolar courieresmtpd: [ID 702911 mail.info] started, ip=[::ffff:24.130.129.94]

An "250 Ok. 42C062BB.0001FC6" gets written to the "trigger" socket, and at some point "submit" writes a "QUIT" back to "courieresmtpd". But that's it - "courierd" never seems to be contacted (which always seems to be the next step after "courieresmtpd" gets the initial incoming connection), and the mail disappears into the bit bucket.

Scratching my head over this one ...

Hmmmm... By chance, when you upgraded, did you copy your old config files in over the new ones installed? Or did you do a patch from old version to new version, and go and adjust all your configurations in the new files?

I had upgraded from .39 up to .50, and had to basically 'start over' with config, because copying them in would have caused quite a stir. The 'big change' of courier-authlib being split off into its own daemon, makes the config files a slight bit different in how they perceive user accounts... Which in turn determines if mail gets delivered, or mail can be accessed, or if users can send out mail via authenticated smtp.

Your problem could lie anywhere in that mess =)

The behavior I notice with the new courier is:

Mail comes in from the world, esmtpd fires up, looks up the user, if they exist, it files the message if they are not over quota. If they don¹t exist, it rejects the mail. Courierd is never in the mix when a mail comes in for delivery, nor does courierd get involved when a user sends email out. As esmtpd handles both of those.

When a user comes in to get their mail, either courier-imapd, or courier-pop3d are activated.

To me, courierd itself is mearly the 'hub' for all the sub daemons... With authlib being the 'source' for all authentications. Authlib can be setup to read in user accounts from a multitude of types of locations... Which makes it quite nice and clean this way.

So... Not sure if I helped any with that rambling ? Or I could have just misread what your problem is... I do that.

-R