Blocking Delivery Status Notifications?

Helio Silva helio at HELIO.COM.BR
Wed Oct 16 14:16:26 IST 2002


You can make a procmail recipe to kill the "Disposition-Notification-To:"
header if the message is detected as spam.

something like this

:0
* ^X-MESSAGE-STATUS: SPAM            # or any taged spam header
* ^Disposition-Notification-To
| formail -I "Disposition-Notification-To:"

Of course it can become another configurable option of mailsanner future releases.


Helio Silva

At 04:47 16/10/02, you wrote:
>Hmmm I now even get bounced messages from spammers that
>request a delivery notification in their e-mails but then reject receiving
>it...
>
>Anyone having problems with DSN's or is it simply something that is
>allowed on most sites?
>
>
>   ----- The following addresses had permanent fatal errors -----
><rosana.cusnir at tecnipublicaciones.com>
>    (reason: 550 Sorry, this server is configured to refuse this sort of
>mail (to combat the SPAM problem))
>
>On Tue, 15 Oct 2002, Remco Barendse wrote:
>
>> Was thinking to put several phrases / bits of text from udesireable /
>> unwanted DSN e-mail replies into strings that we could put in a config
>> file. Then have mailscanner check every e-mail for these strings and
>> silently drop every e-mail with that text in it if the mail originates
>> from the domains in our localdomains list (like MS can do with
>> viruses).
>>
>> To put it simple : check every e-mail for text lines that would appear in
>> DSN reply messages from our local domain and silently drop them?
>>
>> This way 'good' DSN replies would be allowed through as well as incoming
>> DSN messages for failed e-mail messages but sensitive / private
>> information and replies spammers would like to have would be blocked.
>>
>>
>> On Tue, 15 Oct 2002, Julian Field wrote:
>>
>> > At 12:33 15/10/2002, you wrote:
>> > >Would it be possible to make the text of these DSN messages a string that
>> > >can be included sort of in a 'virus messages to be silently dropped' way
>> > >if it isn't possible to mess about with the DSN status in the
>> > >message headers?
>> > >This way (in this case Exchange) would still generate these 3 types DSN's
>> > >but they would never get delivered :)
>> >
>> > Not quite sure what you mean. Can you give an example or two?
>> > --
>> > Julian Field                Teaching Systems Manager
>> > jkf at ecs.soton.ac.uk         Dept. of Electronics & Computer Science
>> > Tel. 023 8059 2817          University of Southampton
>> >                              Southampton SO17 1BJ
>> >
>> >
>>
>>



More information about the MailScanner mailing list