After totally removing it and starting from scratch I was able to hack the init/conf scripts to work correctly.
Thanks again, bob On Thu, 2003-02-27 at 05:41, Justin Heesemann wrote: > On Thursday 27 February 2003 02:12, bob ketterhagen wrote: > > This vpopmail-5.2.1-r4.ebuild everything is default nothing special, I > > have it working on numerous other servers with not a single problem. It' > > s just the newest mailserver I have built that I am having this problem > > on. I can send myself email and recieve it. I can remove the relay > > table, check my email and it readds it but, it continues to stay empty. > > > > bob > > ok.. i guess i might have an answer. > courier-imap-1.7.ebuild makes use of authdaemon. > authdaemon doesn't get the TCPREMOTEIP env variable. > so: what should the poor vpopmail vopen_smtp_relay think it should set ?? > > i don't know, why this worked on your other servers. i guess you might be > running another version of courier-imap. > i have an ebuild for courier, which works.. but it's more or less a unclean > hack. > > a quick'n'dirty solution: > > make sure /usr/lib/courier-imap/authlib/authvchkpw exists. > > replace the "need net authdaemond" lines in your /etc/init.d/courier* scripts > with "need net" > > replace the AUTHMODULES="authdaemon" line with AUTHMODULES="authvchkpw" in > your /etc/courier-imap/imapd /etc/courier-imap/imapd-ssl > /etc/courier-imap/pop3d /etc/courier-imap/pop3d-ssl files. > > /etc/init.d/authdaemond stop > /etc/init.d/courier-imap restart > > (i hope i've covered every variable i changed...) >
Description: This is a digitally signed message part