/usr/sbin/sendmail -X /tmp/mailtraffic.txt -bd -q30m
That will log all message traffic through your mailserver. Then you can
glean that log for the messages your looking for. I'd have cron job to
go through that log fairly often as that log will get very big very fast.
Curtis
On Thu, 17 Jul 2003, Professional Software Engineering wrote:
At 12:58 2003-07-17 -0600, Scott Miller wrote:
Hi all, I'm new to this list, and have just one question.
I'm wondering if anyone can help me configure Procmail. I have a
very unique situation here - and can't go into too much detail. I have a
customer who is under investigation, and I've received a court order to log
all incoming and outgoing mail for this particular user for a set period of
time. I was wondering if Procmail would help me to do this. Basically I
just need to dump all incoming into one file (while also delivering the mail
to the user), and outgoing into another, then at the end of the time period,
hand over the file.
Incoming is easy enough - just do that at the MTA via an alias. No need to
use procmail for that.
Outgoing is a LOT more difficult. Procmail isn't invoked for outgoing
email, and there are (as I see already described in another reply),
"issues" with expecting to capture them all.
If I were faced with a court order like that, I'd respond to it with a
request for necesary expertise provided by the court (or at the expense of
the party making this demand) - they're demanding that you do work which
may involve significant modification of how things are performed on your
servers just to comply.
A statement to the effect that there are a number of limitations to
capturing outbound email might prompt them to lay off of the expectation
that you can capture it all. In fact, at a minimum, you can express that
because there are many limitations, what you might provide may not
represent all of his communication sent through your service.
There are ways to hook procmail into your MTA, but it depends upon your
MTA. If you're not intimatley familiar with the MTA, you very well may end
up losing other mail (i.e. screwing with other customers, and possibly
losing business as a result), or taking down your mail server (and screwing
with other customers, and possibly losing business as a result).
<http://www.professional.org/procmail/smtp.html>
---
Sean B. Straw / Professional Software Engineering
Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
Please DO NOT carbon me on list replies. I'll get my copy from the list.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail
--
--
Curtis Maurand
mailto:curtis(_at_)maurand(_dot_)com
http://www.maurand.com
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail