This is a discussion on Re: Problems with $mydomain entries in virtual within the mailing.postfix.users forums, part of the Mail Servers and Related category; Michael wrote: >>>>>@mydomain.com bitbucket # defined in aliases as /dev/null >>>> &...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Michael wrote:
>>>>>@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 than > 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? Because it is better > Plus, since they spoof other mailbox addresses then my 'unknown user' > response could get routed back to some innocent bystander. No- when you REJECT when the connection is made (politely hang up) you are telling the sender that the user does not exist. When you accept the message and then decide to bounce it- this is when backscatter is bounced to possible forged envelope senders > I don't think this is the problem ... there is nothing wrong with routing > unwanted messages to /dev/null But 'hanging up' on the zombie virus email is better than accepting and routing it to /dev/nul. > ... > >>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 Then maybe you should reconsider and accept your mail directly. If your ISP is accepting all your mail and forwarding to you, you can not 'hang up' on the original sender. In this case, dumping to the bit bucket is better than bouncing. Gerry |
![]() |
| Thread Tools | |
| Display Modes | |
|
|