How to track down someone mislabeling msgs as abuse?
I have a mailing list which has 51 members, all friends of mine. We use it to communicate on things related to our history club. About 1-2 times a month, I receive an automated message from AOL's abuse list, saying that someone has marked one of the messages as "abuse". Unfortunately, there's no way to track down who this could be, since there are about 5 addresses on the list which are AOL addresses. All I get is this:
Feedback-Type: abuse User-Agent: AOL SComp Version: 0.1 Received-Date: Mon, 25 Jun 2018 10:04:00 -0400 (EDT) Source-IP: 98.173.52.230 Reported-Domain: mischievous.us Redacted-Address: redacted Redacted-Address: redacted@
Along with also a copy of the original message.
Using the "Received-Date" header, I can see that it looks as if the timing would point to one particular list member, but he says he's not doing anything like that. (As a matter of fact, he has told me, on a few occasions, that he didn't even see the message in question at all!)
I've read that some people have addressed this by inserting a unique string at the end of each person's message. I don't see a way to do this with Mailman 2.1.22. Would something like this be possible with more recent versions such as 2.1.27, or even the latest 3.x version? Are there other ways to address this? I don't want to reprimand the person, I just want to educate them to not mark list messages as abuse!
Any help would be greatly appreciated!
/raj
I put %(user_address)s in the message footer; that doesn't seem to get sanitized by the feedback loops.
It doesn't work for digests though, just regular messages.
I believe it also requires you to set OWNERS_CAN_ENABLE_PERSONALIZATION on mm_cfg.py.
As to your suspect, since he says he's not seeing the messages, is it possible he has an autofilter that's routing them directly to spam? I had a user like that recently.
On Mon, Jun 25, 2018 at 11:39 AM, Richard Johnson raj@mischievous.us wrote:
I have a mailing list which has 51 members, all friends of mine. We use it to communicate on things related to our history club. About 1-2 times a month, I receive an automated message from AOL's abuse list, saying that someone has marked one of the messages as "abuse". Unfortunately, there's no way to track down who this could be, since there are about 5 addresses on the list which are AOL addresses. All I get is this:
Feedback-Type: abuse User-Agent: AOL SComp Version: 0.1 Received-Date: Mon, 25 Jun 2018 10:04:00 -0400 (EDT) Source-IP: 98.173.52.230 Reported-Domain: mischievous.us Redacted-Address: redacted Redacted-Address: redacted@
Along with also a copy of the original message.
Using the "Received-Date" header, I can see that it looks as if the timing would point to one particular list member, but he says he's not doing anything like that. (As a matter of fact, he has told me, on a few occasions, that he didn't even see the message in question at all!)
I've read that some people have addressed this by inserting a unique string at the end of each person's message. I don't see a way to do this with Mailman 2.1.22. Would something like this be possible with more recent versions such as 2.1.27, or even the latest 3.x version? Are there other ways to address this? I don't want to reprimand the person, I just want to educate them to not mark list messages as abuse!
Any help would be greatly appreciated!
/raj
Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/ mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/ rclemings%40gmail.com
--
Russell Clemings russell@clemings.com
Thanks for the suggestion! I'll try it out.
As for routing directly to spam, I actually thought of that and asked him to verify that wasn't the case. He says he has no such filter.
I'm hoping that if I can provide proof that it's him, he'll take it more seriously and take a closer look. At any rate, if I can prove it's him, I'll have justification for removing him from the list or at least ask if he has a different email address I can use.
Thanks again!
/raj
On Jun 25, 2018, at 12:23 PM, Russell Clemings
mailto:rclemings@gmail.com> wrote: I put %(user_address)s in the message footer; that doesn't seem to get sanitized by the feedback loops.
It doesn't work for digests though, just regular messages.
I believe it also requires you to set OWNERS_CAN_ENABLE_PERSONALIZATION on mm_cfg.py.
As to your suspect, since he says he's not seeing the messages, is it possible he has an autofilter that's routing them directly to spam? I had a user like that recently.
On Mon, Jun 25, 2018 at 11:39 AM, Richard Johnson
mailto:raj@mischievous.us> wrote: I have a mailing list which has 51 members, all friends of mine. We use it to communicate on things related to our history club. About 1-2 times a month, I receive an automated message from AOL's abuse list, saying that someone has marked one of the messages as "abuse". Unfortunately, there's no way to track down who this could be, since there are about 5 addresses on the list which are AOL addresses. All I get is this: Feedback-Type: abuse User-Agent: AOL SComp Version: 0.1 Received-Date: Mon, 25 Jun 2018 10:04:00 -0400 (EDT) Source-IP: 98.173.52.230 Reported-Domain: mischievous.us http://mischievous.us/ Redacted-Address: redacted Redacted-Address: redacted@
Along with also a copy of the original message.
Using the "Received-Date" header, I can see that it looks as if the timing would point to one particular list member, but he says he's not doing anything like that. (As a matter of fact, he has told me, on a few occasions, that he didn't even see the message in question at all!)
I've read that some people have addressed this by inserting a unique string at the end of each person's message. I don't see a way to do this with Mailman 2.1.22. Would something like this be possible with more recent versions such as 2.1.27, or even the latest 3.x version? Are there other ways to address this? I don't want to reprimand the person, I just want to educate them to not mark list messages as abuse!
Any help would be greatly appreciated!
/raj
Mailman-Users mailing list Mailman-Users@python.org mailto:Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/rclemings%40gmail.com https://mail.python.org/mailman/options/mailman-users/rclemings%40gmail.com
--
Russell Clemings
mailto:russell@clemings.com>
I tried this just now, adding "%(user_address)" to the footer, and I'm geting:
Warning: The following illegal substitution variables were found in the msg_footer string: user_address
(I included "OWNERS_CAN_ENABLE_PERSONALIZATION = Yes" into mm_cfg.py, and I did bin/mailmanctl restart.)
What version of mailman are you using? Mine is 2.1.22, which I know is old.
/raj
On Jun 25, 2018, at 12:36 PM, Richard Johnson raj@mischievous.us wrote:
Thanks for the suggestion! I'll try it out.
As for routing directly to spam, I actually thought of that and asked him to verify that wasn't the case. He says he has no such filter.
I'm hoping that if I can provide proof that it's him, he'll take it more seriously and take a closer look. At any rate, if I can prove it's him, I'll have justification for removing him from the list or at least ask if he has a different email address I can use.
Thanks again!
/raj
On Jun 25, 2018, at 12:23 PM, Russell Clemings
mailto:rclemings@gmail.com> wrote: I put %(user_address)s in the message footer; that doesn't seem to get sanitized by the feedback loops.
It doesn't work for digests though, just regular messages.
I believe it also requires you to set OWNERS_CAN_ENABLE_PERSONALIZATION on mm_cfg.py.
As to your suspect, since he says he's not seeing the messages, is it possible he has an autofilter that's routing them directly to spam? I had a user like that recently.
On Mon, Jun 25, 2018 at 11:39 AM, Richard Johnson
mailto:raj@mischievous.us> wrote: I have a mailing list which has 51 members, all friends of mine. We use it to communicate on things related to our history club. About 1-2 times a month, I receive an automated message from AOL's abuse list, saying that someone has marked one of the messages as "abuse". Unfortunately, there's no way to track down who this could be, since there are about 5 addresses on the list which are AOL addresses. All I get is this: Feedback-Type: abuse User-Agent: AOL SComp Version: 0.1 Received-Date: Mon, 25 Jun 2018 10:04:00 -0400 (EDT) Source-IP: 98.173.52.230 Reported-Domain: mischievous.us http://mischievous.us/ Redacted-Address: redacted Redacted-Address: redacted@
Along with also a copy of the original message.
Using the "Received-Date" header, I can see that it looks as if the timing would point to one particular list member, but he says he's not doing anything like that. (As a matter of fact, he has told me, on a few occasions, that he didn't even see the message in question at all!)
I've read that some people have addressed this by inserting a unique string at the end of each person's message. I don't see a way to do this with Mailman 2.1.22. Would something like this be possible with more recent versions such as 2.1.27, or even the latest 3.x version? Are there other ways to address this? I don't want to reprimand the person, I just want to educate them to not mark list messages as abuse!
Any help would be greatly appreciated!
/raj
Mailman-Users mailing list Mailman-Users@python.org mailto:Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/rclemings%40gmail.com https://mail.python.org/mailman/options/mailman-users/rclemings%40gmail.com
--
Russell Clemings
mailto:russell@clemings.com>
Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/raj%40mischievous.us
Richard Johnson writes:
I tried this just now, adding "%(user_address)" to the footer,
Executive summary: Try adding "s" to the end of that.
The format string is "%s", which in very old Pythons needed to be referred to according to its position in the string. More modern Pythons allow you to interpolate "(user_address)" which looks up the variable user_address in a dictionary. But you still need the "s" at the end to tell Python to format the variable's value is expected to be a string, not an integer or something like that.
The error message seems unclear. I'm not sure if it's easy to do anything about it though. The format string language is complex, and I'm not sure it's easy for the program to diagnose the error more precisely.
Regards,
Steve
-- Associate Professor Division of Policy and Planning Science http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull@sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN
On 6/25/18 11:39 AM, Richard Johnson wrote:
Feedback-Type: abuse User-Agent: AOL SComp Version: 0.1 Received-Date: Mon, 25 Jun 2018 10:04:00 -0400 (EDT) Source-IP: 98.173.52.230 Reported-Domain: mischievous.us Redacted-Address: redacted Redacted-Address: redacted@
Along with also a copy of the original message.
Using the "Received-Date" header, I can see that it looks as if the timing would point to one particular list member, but he says he's not doing anything like that. (As a matter of fact, he has told me, on a few occasions, that he didn't even see the message in question at all!)
I've read that some people have addressed this by inserting a unique string at the end of each person's message. I don't see a way to do this with Mailman 2.1.22. Would something like this be possible with more recent versions such as 2.1.27, or even the latest 3.x version? Are there other ways to address this? I don't want to reprimand the person, I just want to educate them to not mark list messages as abuse!
Any help would be greatly appreciated!
/raj
Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/mark%40msapiro.net
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 6/25/18 11:39 AM, Richard Johnson wrote:
I have a mailing list which has 51 members, all friends of mine. We use it to communicate on things related to our history club. About 1-2 times a month, I receive an automated message from AOL's abuse list, saying that someone has marked one of the messages as "abuse". Unfortunately, there's no way to track down who this could be, since there are about 5 addresses on the list which are AOL addresses.
Sorry about the prior fumbled send :(
In my experience, AOL's redaction is not always complete, particularly if the message is VERPed, but in any case, beginning with Mailman 2.1.24 we have
- There is a new RCPT_BASE64_HEADER_NAME setting. If this is set to a non-empty string, that string is the name of a header that will be added to personalized and VERPed deliveries with value equal to the base64 encoding of the recipient's email address. This is intended to enable identification of the recipient otherwise redacted from "spam report" feedback loop messages.
E.g., set
RCPT_BASE64_HEADER_NAME = 'X-My-Recip'
in mm_cfg.py and the VERPed or personalized message will have a
X-My-Recip: header with the base64 encoded recip. The name of the header is a setting to prevent AOL from knowing what it is and redacting it too.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thanks! I have now upgraded to 2.1.27 and inserted this config. My test worked and I see how to decode it. Hopefully, I'm well placed when I see some of this "abuse" nonsense again. :)
/raj
On Jun 25, 2018, at 10:19 PM, Mark Sapiro mark@msapiro.net wrote:
On 6/25/18 11:39 AM, Richard Johnson wrote:
I have a mailing list which has 51 members, all friends of mine. We use it to communicate on things related to our history club. About 1-2 times a month, I receive an automated message from AOL's abuse list, saying that someone has marked one of the messages as "abuse". Unfortunately, there's no way to track down who this could be, since there are about 5 addresses on the list which are AOL addresses.
Sorry about the prior fumbled send :(
In my experience, AOL's redaction is not always complete, particularly if the message is VERPed, but in any case, beginning with Mailman 2.1.24 we have
- There is a new RCPT_BASE64_HEADER_NAME setting. If this is set to a non-empty string, that string is the name of a header that will be added to personalized and VERPed deliveries with value equal to the base64 encoding of the recipient's email address. This is intended to enable identification of the recipient otherwise redacted from "spam report" feedback loop messages.
E.g., set
RCPT_BASE64_HEADER_NAME = 'X-My-Recip'
in mm_cfg.py and the VERPed or personalized message will have a
X-My-Recip: header with the base64 encoded recip. The name of the header is a setting to prevent AOL from knowing what it is and redacting it too.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/raj%40mischievous.us
participants (4)
-
Mark Sapiro
-
Richard Johnson
-
Russell Clemings
-
Stephen J. Turnbull