OK let's explore this first obvious way to address the problem (don't send confirmation message bounces to the bitbucket but instead make them available on the off-chance somebody needs to see them).
Yes, what you suggest would work... but how to clean it out? I cannot think of a way to trim such a mailbox of messages older than N days.
Or perhaps I don't understand what a ".qmail-spambounce" is? My sysadmin really likes Sendmail, I hate it but let him have his way, don't get me started.
I don't think the users will purge their own mailboxes. Or if they do, they won't enjoy it. Comments/thoughts?
THANKS
At 2:16 PM -0600 3/9/03, Jim Ramsay wrote:
On Sun, Mar 09, 2003 at 08:26:30AM -0800, Johnny Quazar wrote:Yes? Clues about how to make this happen? I can think of some things to try, all bad. Any suggestions will be appreciated!
You could set up a separate mailbox for these bounces... Set the following in every TMDA config: BOUNCE_ENV_SENDER = "[EMAIL PROTECTED]"
Then set up a .qmail-spambounce for each user to a specific mailbox they can check at their leisure.
-- Jim Ramsay [EMAIL PROTECTED] PGP Key ID: 0xBE28F488 _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
_____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
