spam handling rules with +detail email addresses?

[Ken Anderson]

Julian Field wrote:

> At 16:52 18/02/2004, you wrote:
>
>> Julian Field wrote:
>>
>>> At 01:04 18/02/2004, you wrote:
>>>
>>>> How does MailScanner/SA handle incoming email addressed to
>>>> user+detail at domain.com in rules?
>>>>
>>>> Sendmail will strip everything after/including the + sign, and deliver
>>>> to the 'user', but rules in MailScanner for both user+detail at domain.com
>>>> AND user at domain.com seem to be bypassed when using this syntax in an
>>>> email.
>>>>
>>>> I've only tested with rules/spam.actions.rules like this:
>>>>
>>>> To:     user+detail at domain.com    store notify
>>>> To:     user at domain.com store notify
>>>>
>>>> Both are bypassed and mail gets the default action applied to it if
>>>> it's
>>>> addressed to user+detail at domain.com
>>>
>>>
>>>
>>> But what is the envelope recipient address in this case? user or
>>> user+detail?
>>
>>
>> user+detail at domain.com is the envelope recipient reported in the
>> sendmail log. The entry below doesn't seem to work. The message gets the
>> default rule applied instead of the 'store notify' rule.
>> To:     user+detail at domain.com    store notify
>>
>> I tried both the suggestions below, and they do properly apply the
>> action "store notify", but for some reason, sendmail then tries to
>> deliver the message back to 127.0.0.1 instead of the mail hub!
>> This creates a problem with the same message being scanned, then
>> redelivered to the incoming sendmail and looping. Other 'store notify'
>> rules that are defined for normal email addresses work fine.
>>
>> We forward mail from the MailScanner box to the mailhub using the
>> virtusertable feature. No other rule or config issue has broken this
>> before, so I'm not sure what's happening. I'll turn up logging in
>> sendmail and see if it will tell me what it's doing with this mail.
>
>
> MailScanner doesn't get involved with message delivery at all, so I fail to
> see how it could have caused this delivery problem.

Yes, it seems like it has to be something with sendmail config, but then
again, the notify action is the only action that triggers it. I changed
the action to 'deliver', and the mail for user+detail is delivered
properly. But with action 'store notify', it loops back to localhost
(the incoming sendmail receives it again from notify?).

One odd thing I notice in the log - with the notify function, mail is
delivered to
"to=user+detail at domain.com"
(this loops back to localhost)

With 'deliver' action, mail is delivered to
"<to=user+detail at domain.com>"
(this gets correctly delivered to the mailhub)

Note the missing <> in the looping email. I'm not a sendmail guru, so
I'm not sure where this envelope TO is getting generated, but it may be
a clue?

Thanks for any ideas,

Ken Anderson
Pacific.Net




> --
> Julian Field
> www.MailScanner.info
> Professional Support Services at www.MailScanner.biz
> MailScanner thanks transtec Computers for their support
> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
>
>