> I'm sure you could, but why add the complication and need to
> administer the list of users on the firewall? It's just as easy to add
> an alias for each of the users on the mailhub to deliver the mail to
> /dev/null or otherwise throw it away. quick, simple, no bounce, and no
> complication with the firewall. Yes you can do it on the firewall,
> but this is a pretty basic system admin trick, something you'll
> probably have to do frequently. (At least I know I do :-) I'd
> personally leave this task on the mailhub where you do your regular
> administration of mail addresses. Don't add any more maintenance to
> your firewall than you need to.
I will confess to being somewhat "less than forthright" about what
I'm doing. _Every_ piece of email to these certain users has been
spam, and although I could just redirect their stuff to /dev/null, I
would much rather the spammers remove these names from their list.
Why don't I just send the spammers email telling them? Because their
email addresses are usually bogus, which is why I've been getting the
bounce notice.
And, since I'm being completely honest, for those userids in the
list, I'll issue a "471" message, rather than a "571".
It's not really any more work to administer the names on the firewall
than to administer the names in /etc/aliases (after any coding that
has to be done).
-ron
--
ron snyder snyder @
roguewave .
com | This space
Rogue Wave Software, Inc | intentionally
{news,unix} admin | left blank
#include <std-dsclmr.h++> |
References:
|
|
