This is a discussion on More vmailmgr woes within the Courier-Imap forums, part of the Mail Servers and Related category; Greetings, everybody. I've got a woe here. I'm installing courier IMAP, qmail, and vmailmgr. I'm aware of ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Greetings, everybody. I've got a woe here.
I'm installing courier IMAP, qmail, and vmailmgr. I'm aware of the newer daemonized setup for the courier imap/pop daemons. However, no matter what version I use, (and using --without-authdaemon doesn't help), I can't get things to work. The HOWTOs for courier-imap and vmailmgr are horribly out of date, and don't address more recent verions of courier-imap. Here are the verions I've tried: Via source: 4.0.3, 3.0.8, 1.7.3 via RPM (built via rpmbuild or downloaded from the 'net): 1.7.3 2.2.2 3.0.1 3.0.8 4.0.3 There's something missing here. An existing server with some really old (1.3.x?) version of courier-imap works fine. I have edited my imapd file to include authvmailmgr, have things set up in /etc/vmailmgr, but no matter what happens, authentication fails. Logging for vmailmgr shows nothing is happening - it logs that it is starting and stopping, but it doesn't show 'connections'. Is there something else that needs to change with the setup of courier or vmailmgr to let authvmailmgr know that it's got to talk to it's socket? Any help would be appreciated. I've worked a long time, googled a lot, but found no answers. |