Re: [Mailman-Users] Microsoft blocking our Mailman lists
On Sunday, October 7, 2018, 11:28:28 AM, Lindsay Haisley wrote:
LH> FMP's mail and web server is a virtual server at Linode. We run half a
LH> dozen Mailman lists or so, all opt-in lists for a couple of non-profits
LH> and small business customers, all of which have been running
LH> successfully for many months. Today I got a large number of
LH> unsubscription notices from one of our lists, all of them for addresses
LH> at hotmail.com, msn.com and outlook.com. They contain the following
LH> text:
[...]
LH> Has anyone seen similar problems recently with Microsoft mail customers
LH> who are Mailman list subscribers?
No problems here with the two lists I run, although I'm not a stranger
to problems with blocklists or list users inadvertently reporting list
messages as spam.
This is almost certainly not going to have anything to do with
Mailman, but more to do with the reputation of the IP address of your
virtual server at Linode or IP netblock ("neighborhood") you are
sending from.
If you Google around for the error you reported, you should be able to
find a form to request de-listing. Perhaps they will while-list your
server's IP address even if they are not thrilled with the overall
experience with emails from Linode address space.
--
Best regards,
Robert Braver
rbra...@ohww.norman.ok.us
--
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/archive%40jab.org
Re: [Mailman-Users] A simple unsubscribe
On Friday, June 29, 2012, 12:39:06 PM, Brad Rogers wrote: BR> What's wrong with the current challenge and response method? Stops BR> people from maliciously (un)subscribing others. If there's anything in the content of the list messages that could be construed as an advertisement, the failure to have a one-click (or one email) unsubscribe is a violation of federal law (CAN-SPAM Act) and the FTC regulations promulgated thereunder. This bugs me, too. -- Best regards, Robert Braver rbra...@ohww.norman.ok.us -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] sender gets his own message!
Hello Andreas, On Thursday, February 3, 2011, 8:43:10 AM, you wrote: AH> I've just set up mailman 2.1.13, my only list till now is "mailman". AH> Everything works fine except the thing that the sender of a message gets his AH> own message, too. On an other server where I run mailman that doesn't occur. AH> I could not find any option to set. AH> Anyone an idea? To me, this is the normal and expected behavior. If for any reason users do not see their own message, they assume it didn't go through and resend it, or email me asking what is wrong. This is a configurable preference each user can set. The administrator can set this by pulling up a user in membership management, and checking the "not metoo" box. -- Best regards, Robert Braver rbra...@ohww.norman.ok.us -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] changes at aol
On Saturday, August 9, 2008, 1:40:19 PM, Steven Stern wrote: SS> On 08/09/2008 12:16 PM, Robert Braver wrote: [...] SS> | This means you will have to track down the individual message by SS> | the Message ID in order to identify the email address of the SS> | specific recipient. SS> If you add personalization in the footer, AOL will not redact it. Today, yes, but not after the changes being made by AOL that is the subject of this thread. http://postmaster.info.aol.com/fbl/arfinfo.html What is the difference between the traditional AOL Feedback Loop format and ARF? The traditional format is a MIME multipart message with one empty text part and one message/rfc822 part with the original message being complained about. Parts of the header of the message being complained about are redacted out, where normally the AOL ScreenName recipient would be present. ARF is defined in a internet draft located at http://www.mipassoc.org/arf/ . ARF messages have three mime parts, one part for general information, one machine parsable and meta data part, and the last part as the original message being complained about. The original message is redacted to protect clear text occurrences of AOL screen names and email addresses. An example ARF report (with redacted message) is provided on the page referenced above. -- Best regards, Robert Braver [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] changes at aol
On Saturday, August 9, 2008, 11:24:42 AM, Rick Pasotto wrote: RP> What exactly is this telling me? Does mailman or exim need to be changed RP> or do I need to do something? Follow the links for more information that are provided. It's pretty clear. You don't really have to do anything. The spam reports are moving to the standardized ARF format, and we will no longer have the choice to continue receiving AOL FBL reports in the format you (and I) are receiving them in now. While the ARF format allows for the inclusion of the entire message that is the subject of the complaint, AOL will be redacting the message. This means you will have to track down the individual message by the Message ID in order to identify the email address of the specific recipient. -- Best regards, Robert Braver [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Block spam from "-owner"?
On Wednesday, April 2, 2008, 7:19:10 PM, Jon Slater wrote: JS> I am getting a great deal of spam to almost all of my lists. Well, not the JS> lists per se, but to the owner's of the lists. [...] JS> I'm using SpamAssassin but these are coming in with spam score like "-0.6" I'm running SpamAssassin in front of my Mailman list addresses with great success. It seems to me your issue is to find out why the spam is scoring low, which would be more of a SpamAssassin question. Is most or all of the spam scoring low, or just some? -- Best regards, Robert Braver [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Re: [Mailman-Users] Turning of monthly membership mails
On Sunday, November 25, 2007, 11:56:29 AM, Daniel Herrmann wrote: DH> So, finally: How to turn off this mails? Mailing List Administration, General Settings page, set "Send monthly password reminders" to "No." -- Best regards, Robert Braver [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Re: [Mailman-Users] Preventing spam to list owners
On Sunday, September 30, 2007, 12:30:44 AM, Gary Spivey wrote:
GS> My lists are locked down to only allow posts from members, so my
GS> members are not getting any [spam]. However, as list owner, every
GS> one of my lists is getting a large amount of [spam] - generally
GS> sent to the listname-owner or to mailman-owner.
I run only a small handful of lists, with anywhere from 20 to 200
members each, and filter out at least 200 spams to the various list
addresses daily by running everything through SpamAssassin via a
small bit of procmail.
I've been doing this for about a year now, and very few spams get
through, resulting in very few messages for a moderator and uncaught
bounce notifications. Legitimate bounces (e.g. a user submitting
a message from a recently changed email addresses) still occur as
expected & desired.
Wholesale bouncing of list mail to non-subscribers is totally
unacceptable due to the amount of outscatter this will cause. (see
http://en.wikipedia.org/wiki/Backscatter#Backscatter_of_email_spam )
It only took one list member from one of the smaller lists (which is
private and not listed anywhere) who had their address book
harvested by a trojan to cause about 50 spam emails a day to that
list alone on an ongoing basis... so hiding the list addresses
doesn't guarantee that they won't eventually leak out and get on the
spam lists.
Aliases file entries and procmail script is below. I'm currently
tagging list filtered spam and shunting it to a specific folder
which I periodically review and flush, but it could just as easily
be sent to /dev/null.
>From the aliases file:
## listname mailing list
listname: "| /usr/bin/procmail -m /etc/procmailrcs/mailman.rc post listname"
listname-admin: "| /usr/bin/procmail -m /etc/procmailrcs/mailman.rc admin
listname"
listname-bounces: "| /usr/bin/procmail -m /etc/procmailrcs/mailman.rc bounces
listname"
listname-confirm: "| /usr/bin/procmail -m /etc/procmailrcs/mailman.rc confirm
listname"
listname-join: "| /usr/bin/procmail -m /etc/procmailrcs/mailman.rc join
listname"
listname-leave: "| /usr/bin/procmail -m /etc/procmailrcs/mailman.rc leave
listname"
listname-owner: "| /usr/bin/procmail -m /etc/procmailrcs/mailman.rc owner
listname"
listname-request: "| /usr/bin/procmail -m /etc/procmailrcs/mailman.rc request
listname"
listname-subscribe: "| /usr/bin/procmail -m /etc/procmailrcs/mailman.rc
subscribe
listname"
listname-unsubscribe: "| /usr/bin/procmail -m /etc/procmailrcs/mailman.rc
unsubscribe
listname"
The mailman.rc file is:
VERBOSE=yes
LOGFILE=/var/log/mailman-procmail.log
MMCOMMAND=$1
MMLIST=$2
:0fw
* < 256000
|/usr/bin/spamc
# Send on to Mailman if not marked as spam
:0 H
* !^X-Spam-Status: Yes
|/var/mailman/mail/mailman $MMCOMMAND $MMLIST
# Otherwise add tag and send to abuse mailbox
:0
* ^Subject:[]*\/[^ ].*
{
SUBJECT=$MATCH
}
# create the new subject token
SUBJECT="[$MMLIST Filtered] $MATCH"
# insert it into the headers
:0hf
| formail -I "Subject: $SUBJECT"
# and forward
:0
! spam
--
Best regards,
Robert Braver
[EMAIL PROTECTED]
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
