From: Adam Jacob Muller (lists-postfixadam.gs)
Date: Fri Dec 01 2006 - 17:32:24 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I think his idea, which seems interesting to me, is one of "did I do
anything that might trigger this bounce." Doing so would require
maintaining a database of some kind of unique characteristics of sent
mails in order to check all incoming bounces.

What about message IDs?
They seem to be replicated in bounces,
they are unique.

It seems easy enough to define 2 milters, one for incoming and one
for outgoing. The outgoing milter would add the message ID of the
mail to a database,
the incoming milter would check if incoming mail is a bounce (dunno)
and if so, check for a message id in the body, and compare against
the db.

-Adam

On Dec 1, 2006, at 6:03 PM, mouss wrote:

> Ronald F. Guilmette wrote:
>> [snip]
>> Both parts of this overall task would be greatly facilitated by
>> the ability
>> to pass certain mail message headers from the current (incoming)
>> message
>> from Postfix to the external policy server.
>>
>
> The policy server mechanism is mostly for doing access control
> based on envelope. if you want to check data, then you should use a
> content filter (possibly as a proxy_filter to be able to reject the
> transaction).
>> [snip]
>>
>> Content-Type: multipart/report;...
>> User-Agent: Vacation/...
>> X-MS-Embedded-Report:...
>> From: Mail Delivery Subsystem...
>> Subject: MDaemon Notification...
>>
>
>
> a look at spamassassin rules shows that trying to do such analysis
> is at least a hard problem...
>
> maybe you could explain how you would detect backscatter without
> talking of implementation.

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]