piping the data will give you problems with message size limits and timeouts
I think. Add a header to your new messages to prevent refinding them...
And you will probably want to move the messages to a new working directory
and delete them as you process them - or work in the archivedir itself - you
will have to clean up this folder though or it will eat all your disk.
-----Original Message-----
From: Carey Jung [mailto:car...@itfreedom.com]
Sent: Monday, July 28, 2003 9:57 AM
To: Mitch (WebCob); Thomas von Hassel
Cc: Courier Users
Subject: RE: [courier-users] filtering outgoing mail
That's half the solution though - the other part is to grep through the
archive directory and process the messages to determine which ones need to
be forwarded and to who - AND to skip ones that are a reforward of an
original message. A cron job and a bit of script should be able to do that
for you.
Yes, I'm working on that. It looks like greping for something like
'^[sr].*\@domain\.com' will get messages sent to or received by someone at
'@domain.com'. How do you detect the reforwards?
How would you go about re-injecting the msg into courier ?
I'm just piping the data file into 'sendmail arch...@bigbro.com'.
Carey
8 messages in net.sourceforge.lists.courier-usersRE: [courier-users] filtering outgoin...
