Date: Fri, 1 Dec 2000 12:47:00 +1100 (EST) From: Enno Davids <enno.davids@metva.com.au> To: freebsd-isp@FreeBSD.ORG Subject: Re: Email Monitoring Message-ID: <200012010147.MAA14864@metva.com.au>
next in thread | raw e-mail | index | archive | help
| You could set up an alias for each of their users so that incoming E-mail | goes to both the user and the administrator, but that doesn't cover outgoing | E-mail. | | A Perl script to scan the mail log for each of your users that would run on | a nightly basis would be a way to monitor outgoing recipients, but actually | intercepting content of outgoing E-mail would require a separate application | to interface with Sendmail or some other mail server program you intend on | using. You can do this with SMTPD if you want. If you don't know it SMTPD is, primarily aimed at people who want to get away from the sendmail bug of the month club (which is admittedly much less of a problem now than some years back). It also has good control over non-relaying and who gets to use your service. The idea is to have an inet spawned service which does SMTP _only_ and saves to a chrooted spool area. A delivery daemon picks up the spooled email and drops it in your real mailer for delivery (i.e. you can still use sendmail and its great flexibility to do delivery for you). For this purpose though it pays to know that the delivery can be made through an arbitrary mailer program (but one which supports a small subset of sendmail's command line arguments and has similar return codes is easiest). This means you can write a script which copies out those emails from the client being monitored and then does delivery and substitute it for the straight call to /usr/lib/sendmail. You may need to recompile to change the delivery agent though. Enno. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200012010147.MAA14864>