I'm getting a load of bounce processing for HTML tags. Is there a setting to filter messages through lynx or something to strip out HTML? I'm not sure why a bounce message would be HTML formatted, but ours is not to reason why.
Bounce message for a non subscriber: Email b is not a subcriber of (redacted) Bounce message for a non subscriber: Email o:shapedefaults v:ext="edit" spidmax="1026" / is not a subcriber of (redacted) Bounce message for a non subscriber: Email br is not a subcriber of (redacted) Bounce message for a non subscriber: Email i is not a subcriber of (redacted) Bounce message for a non subscriber: Email o:shapelayout v:ext="edit" is not a subcriber of (redacted) Bounce message for a non subscriber: Email mailto:redacted@redacted.com is not a subcriber of (redacted) Bounce message for a non subscriber: Email /xml is not a subcriber of (redacted) Bounce message for a non subscriber: Email head is not a subcriber of (redacted) Bounce message for a non subscriber: Email /title is not a subcriber of (redacted)
pashdown@xmission.com writes:
I'm getting a load of bounce processing for HTML tags. Is there a setting to filter messages through lynx or something to strip out HTML?
No. I've never seen anything like this before. I'm not sure why it thinks these are bounces. We should fix that, most don't even have an "@" in them. I don't think we allow bare local-part addresses, you need a domain.
I'm not sure why a bounce message would be HTML formatted, but ours is not to reason why.
Do you have a copy of such a bounce message? If you're getting them consistently, you can set the forward_unrecognized_bounces_to option in the Bounce Processing group for the list settings.
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan
On 11/24/25 10:25 AM, Stephen J. Turnbull wrote:
Do you have a copy of such a bounce message? If you're getting them consistently, you can set the forward_unrecognized_bounces_to option in the Bounce Processing group for the list settings.
I really would like to see one of these bounce messages, however from the OP, forward_unrecognized_bounces_to won't do it as the bounce was somehow recognized as a DSN albeit with strange addresses resulting in the Bounce message for a non subscriber log messages.
I'm guessing, but I think maybe some spam was sent to the list-bounces address and it contained something matching one of the heuristic recognizers <https://gitlab.com/warsaw/flufl.bounce/-/tree/master/flufl/bounce/_detectors>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Where do I set forward_unrecognized_bounces_to ? I can't find documentation on this.
On 11/25/25 8:51 AM, pashdown@xmission.com wrote:
Where do I set forward_unrecognized_bounces_to ? I can't find documentation on this.
If you have Postorius it's Settings -> Bounce Processing -> Forward unrecognized bounces. It is a list attribute with 3 possible values which are discard them, forward to list owners/moderators or forward to the site admin. The default value when lists are created is forward to list owners/moderators. However none of this is relevant to your situation because the bounces you are getting that result in the Bounce message for a non subscriber log messages you are seeing are not unrecognized. As I said at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/... I think these are spam sent to the list-bounces address that one of the heuristic recognizers treats as a real DSN and parses those non-addresses. In order to see the actual messages, you will have to configure your MTA to deliver them to a human or you could apply this patch ``` --- a/src/mailman/runners/bounce.py +++ b/src/mailman/runners/bounce.py @@ -49,6 +49,7 @@ class BounceRunner(Runner): # List isn't doing bounce processing? if not mlist.process_bounces: return False + maybe_forward(mlist, msg) # Try VERP detection first, since it's quick and easy context = BounceContext.normal addresses = StandardVERP().get_verp(mlist, msg) ``` to copy all bounce messages to the forward_unrecognized_bounces_to destination. -- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Mark Sapiro -
pashdown＠xmission.com -
Stephen J. Turnbull