Re: Problems with $mydomain entries in virtual

>> >> @mydomain.com bitbucket # defined in aliases as /dev/null
>> >
>> > Why on earth do you do this? You should not discard mail to invalid
recipients.
>>
>> Well, I thought that was the best way to eliminate spam ... better tha=
n
telling the spammers that the users don't exist.
>
> Since they never bother to correct their lists why bother ?

Why bother to politely hang up?

Plus, since they spoof other mailbox addresses then my 'unknown user'
response could get routed back to some innocent bystander.

I don't think this is the problem ... there is nothing wrong with routing
unwanted messages to /dev/null

The problem is that unqualified names in 'virtual' get mapped to
'mydomain.com'

jane@otherdomain.com -> jane@mydomain.com

rather than

jane@otherdomain.com -> jane # as a local user



> The normal practice is not accept the messages is the first place
(difficult unless you are running 'direct-to-mx' I know), then you don't
> :-
>
> a clog up your queues with bounce messages (which would probably go to
forged senders anyway)
>
> b. clog your bandwidth with the message bodies of spam.

Exactly ... so just route them to /dev/null


Michael




--------------------------------------------------
Michael T. Howard michael@howards.org
23 Algonquin Avenue
Andover, MA 01810-5523 tele 978-474-4559
USA cell 978-886-3697
--------------------------------------------------