You could do this with smtp-poplock easily enough.
To get the logging information from one host to another, you could do a few
things. First, perhaps setup syslog to log to a remote host. But syslog is
annoying, so I'd avoid that.
All you need to do is setup a system of pipes and sockets to get logging lines
from your POP3 host to the SMTP host where you can run the readlog program. On
the POP3 host setup your pop3 software to log to a fifo, and then have another
process reading that fifo and catting the stuff to a mconnect(1) program
connected to a tcpserver(1) program on the SMTP host. The tcpserver on the SMTP
host would read from the socket and write to a fifo, which would then be read
by readlog, which would locally maintain your database file.
This would all be very easy to setup with smtp-poplock, shell scripts, and
ucspi-tcp. Or, perhaps you could use a different pop-before smtp solution but
the same socket and fifo idea.
smtp-popock is at
http://www.davideous.com/smtp-poplock/
- David Harris
Principal Engineer, DRH Internet Inc.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Erik
Bystr�m
Sent: Thursday, March 16, 2000 4:48 AM
To: [EMAIL PROTECTED]
Subject: POP-before-SMTP implementations
Has anyone implemented a POP-before-SMTP (selective relaying) system
that doesn't rely on the assumption that qmail and the POP daemon are
on the same host? Those I found on the qmail page unfortunately did.
[[[snip]]]
