OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Subject: Fake addresses
From: Barry A. Warsaw (bwarsawpython.org)
Date: Thu Jun 08 2000 - 11:14:51 CDT

[Please CC me on followups, I'm not a member of this list. Thanks,
-BAW]

I am in the process of doing some high traffic testing of my mailing
list manager called Mailman <www.list.org>. I am using Postfix
19991231-pl07 on a RH6.1 Linux box.

I have a list that's got about 25k fake addresses and about 10 real
addresses. When I send a message to the list, I want the real
addresses to get the message, but copies destined for the fake
addresses should be just bit bucketed.

The best approach I could come up with for the fake addresses in
Postfix was to give them fake domains (e.g. `user-9922mmtest.com')
and then create a transport file entry for those fake domains. E.g.

-------------------- snip snip --------------------
mmtest.com mmdeliver
.mmtest.com mmdeliver
-------------------- snip snip --------------------

Then in the master.cf file, I add a fake transport such as

# This is for testing Mailman. All addresses destined for mmtest.com are
# sent through this transport, and this is the easiest way to just chuck 'em.
mmdeliver unix - n n - - pipe
    user=bwarsaw argv=/bin/true

Now, this works, but it's still a huge resource drain on my system. I
can easily generate a mailq of 1M+ entries that takes over a day to
clear.

I'm wondering if there's a better way to set something like this up.
If not, then I'll probably write a simple smtp proxy for Mailman's
backend, which would sanitize those fake addresses out of the
recipients list before forwarding on to Postfix.

Thanks,
-Barry