[ Scott D. Gregory writes: ]
>
> I recently had a confirmation get returned as "Undeleverable
> Message" (the user signed up thru my web page). For some reason
> majordomo didn't catch the subject. [...]
>
> After looking at the messages it seems that resend ignored the
> subject, and processed the body of the notification of confirmation
> (message 1). It rec'd the bounced confirmation (message 2) and sent that to
> majordomo-owner (me). Since it couldn't find any commands it sent
> back a help file. This was bounced and answered with a help message
> by resend. [...]
>
> Why didn't resend catch a taboo header?
Because resend was never involved, only majordomo, but only resend
uses the taboo stuff. The original bounced message was sent by
majordomo in response to a subscribe request, so the bounce went to
majordomo@yoursite (apparently because the bouncing MTA is broken and
didn't reply to majordomo-owner). Majordomo thought the bounced message
was another request, but couldn't parse it so it replied with a help
message, which bounced, etc.
Majordomo uses $majordomo_dont_reply (in majordomo.cf) on sender
addresses to break such loops. Add the appropriate robot name to that
regex.
--
Dave Wolfe
References:
|
|
