3 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Reloading esmtpd ...
FromSent OnAttachments
Aleksander AdamowskiDec 5, 2003 1:46 am 
Jeff JansenDec 5, 2003 2:56 am 
Aleksander AdamowskiDec 5, 2003 7:15 am 
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] Reloading esmtpd config without disconnecting IMAP sessions?Actions...
From:Jeff Jansen (ivb_@sil.org)
Date:Dec 5, 2003 2:56:40 am
List:net.sourceforge.lists.courier-users

On Friday 05 December 2003 09:46, Aleksander Adamowski wrote:

Does anyone know how can one safely order esmtpd or courierd to reload all its config files without doing the same for imapd?

When I restart courier, all connected IMAP clients get a stream of "The server has disconnected" error messages. Even if I've only wanted to change a small change in queue handling (the "queuetime" file) or the list of local/accepted/hosted domains.

I assume that when you say "restart courier" you mean using whatever init scripts your distribution uses. I run redhat so I can restart the whole courier suite by running

/etc/init.d/courier restart

If you read your init script (/etc/init.d/courier for redhat, mandrake, suse, etc. - don't know about others) then you'll see exactly what it's doing and which processes are actually being started when you run it.

I think what you want is "courier restart" to restart the courier process and make it reread its configuration files. You can also run "esmtpd restart", "esmtpd-ssl restart", etc. to stop, start, and restart different parts of the courier suite. Again, the init script will show you exactly what's happening when you start and stop the entire thing.

The man pages also show you which options the processes take. "man courier", "man esmtpd", etc.

Hope that helps.