Blocking Delivery Status Notifications?

[Remco Barendse]

Small addition :

The message type is always multipart/report but there is also a
content type field.

For non-delivery reports *and* succesfully delivered reports this is
report-type=delivery-status

For read / not read receipts this is report-type=disposition-notification;

Unfortunately this isn't of much use because we might want to send out
NDSR's but if we allow all delivery-status messages this would also allow
for the succesfully delivered messages.

Ideally we would scan all report-type=delivery-status messages further for the text
Thread-Topic: Delivery Status Notification (Success)
If the message would contain both strings we would silently drop it.

But have no idea how much work or trouble this would cause to implement.
Would already be happy with a solution to filter any report type too
:)


On Tue, 22 Oct 2002, Remco Barendse wrote:

> Just to be sure I have checked some other files that I snatched out of the
> Exchange queue. Unfortunately a non delivery report (for mail sent to
> non-existent adresses) is also of the type multipart/report.
>
> But if I'd have to choose I would indeed prefer to silently drop all
> multipart/report messages and sacrifice the odd message to a non existent
> address. Replacing it with a warning wouldn't make much sense I guess.
>
> An option to keep / store the messages that we silently drop would be
> useful to check if there aren't any other message types that are now
> unintentionally dropped as well.
>
> Best regards,
> Remco
>
> On Tue, 22 Oct 2002, Julian Field wrote:
>
> > Okay,
> >
> > They all seem to be "multipart/report" MIME messages. Do you want to remove
> > the report, replacing it with a warning message of some sort? Or do you
> > want to delete the message entirely?
> >
> > Should be easy enough to detect in SweepContent.pm. It's just a matter of
> > getting the handling code right.
> >
> > At 11:07 22/10/2002, you wrote:
> > >Hello Julian,
> > >
> > >Attached I send you a small tar file with some DSN notifications that
> > >Exchange generates.
> > >
> > >Read/Not read receipts I was able to find in df/qf pairs but the 'You
> > >message has been succesfully delivered to' messages I couldn't find in a
> > >df/qf pair amongst all the files. I have encluded an example from such a
> > >message which was snatched from the internal MS Exchange queue which
> > >should give you an idea. As you can see Exchange happily reports all the
> > >people that are put on copy by the Exchange server but to whom the sender
> > >of the mail never intended to send the mail to.
> > >
> > >Sorry I couldn't find a df/qf pair for this message, if you need it I
> > >will continue to look for it.
> > >
> > >Please do not bounce the DSN's to the mailing list :)
> > >
> > >Thanks and best regards,
> > >Remco
> > >
> > >On Fri, 18 Oct 2002, Julian Field wrote:
> > >
> > > > At 13:09 18/10/2002, you wrote:
> > > > >Seriously though, I think there must be more people out there using
> > > > >Exchange and the reasons to block these stupid DSN confirmations are
> > > > >obvious.
> > > >
> > > > Can you send me a few of these Exchange DSN confirmations so I can see if
> > > > there's an easy way to catch them? Preferably the df/qf pairs out of a
> > > mail
> > > > server en route, that gives me a lot more info than just the message with
> > > > its headers.
> > > >
> >
> >
>
>