Both qmail-smtpd instances can share the tcp.smtp.cdb file without
trouble. Now that you actually brought up routing...I see that I have
made a mistake. You must do your scanning with the /var/qmail instance
or which ever vpopmail does it changes on. The other qmail instance must
be the one t
All that is needed is identical assign, rcpthosts and virtualdomains
files for mail delivery and acceptance. Patched qmails may or may not
need a bit more.
I am retracting this comment if the setup is for one qmail instance to
pass the mail to another qmail instance instead of both deliverin
[EMAIL PROTECTED] wrote:
OK then so I could have a box in wich I do...
take qmail sources and patch them with johns (great and nice) patch...
make setup check and ./config-fast fqdn
after this
after this
change /var/qmail for /var/qmail-scanning-server in conf-local... and again
./config-fast
Joshua Megerman wrote:
On Friday 09 November 2007 04:52:16 am [EMAIL PROTECTED] wrote:
OK then so I could have a box in wich I do...
take qmail sources and patch them with johns (great and nice) patch...
make setup check and ./config-fast fqdn
after this
after this
change /var/qmail for /var
Hi
> > I have vpopmail running with smtp-after-pop functionality
> > (--enable-roaming-users). the pop-daemon is from qmail. this works fine
> > for normal (unsecure) connection via port 110. but this doesn't work if
> > connecting via strunnel on port 995. I know, thats correct, because
> > stunn
