Re: [Mailman-Users] Users being unsubscribed without requesting it.
That's the best theory I have heard so far to explain the facts. The user's in question, who are being unsubscribed without asking to be, are people who like the mailing lists they are on, and would not be flagging emails from the list as spam. Now their ISP might, but they wouldn't. The list owners swear to me that these people are friends who want their emails. Some further info... I was including a link at the bottom of all emails sent by mailman (in the msg_footer field: "Click this link to unsubscribe: %(user_optionsurl)s?password=%(user_password)s=1=1" I thought perhaps users were accidentally clicking this and unsubscribing themselves, so I have removed the "=1" part of the URL so they will have to manually confirm. Maybe this would foil ISPs who are automatically following this link to unsubscribe people. Do ISPs really do this? _____ Steve Wehr Tunedin Web Design -Original Message- From: Keith Seyffarth [mailto:w...@weif.net] Sent: Saturday, August 19, 2017 10:55 AM To: Steve Wehr Cc: mailman-users@python.org Subject: Re: [Mailman-Users] Users being unsubscribed without requesting it. "Steve Wehr" <st...@tunedinweb.com> writes: > The problem is that when contacted, these users swear they DID NOT > unsubscribe themselves. So how can they be getting unsubscribed (with > messages in the logs like the one above) but they are not going to the > member options page and unsubscribing?? One possibility would be that they are marking these messages as "Junk" or "Spam" and their ESP/ISP, either through a manual or automated process, is following the unsubscribe link in the email to remove them from the list... -- from my mac to yours... Keith Seyffarth mailto:w...@weif.net http://www.weif.net/ - Home of the First Tank Guide! http://www.rpgcalendar.net/ - the Montana Role-Playing Calendar http://www.miscon.org/ - Montana's Longest Running Science Fiction Convention -- 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
[Mailman-Users] Users being unsubscribed without requesting it.
I host about a hundred lists and from time to time the list owners keep telling me that users are being unsubscribed from the list without asking to be. Now I assume these users are just being removed for bouncing, but when I check the mailman log files in /var/log/mailman I see this: subscribe:Aug 18 00:41:10 2017 (22583) saintsofswing: deleted dorrainescofi...@gmail.com; via the member options page My understanding of "via the member options page" means that that user unsubscribed themselves from the list. Users who bound have a completely different set of messages in the logs and it's clear they were removed by mailman for bouncing. The problem is that when contacted, these users swear they DID NOT unsubscribe themselves. So how can they be getting unsubscribed (with messages in the logs like the one above) but they are not going to the member options page and unsubscribing?? Thanks for your help. _____ Steve Wehr Tunedin Web Design <http://www.tunedinweb.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/archive%40jab.org
Re: [Mailman-Users] mailman not respecting /etc/postfix/transport ???
Hi Mark -- I think it is fixed I updated /etc/postfix/main.cf with local_recipient_maps = proxy:unix:passwd.byname $alias_maps $transport_maps Then I sent out a mailing from a test mailing list I have that includes my email address -- st...@tunedinweb.com. --> I received this mailing. YEAH! I did look in /etc/passwd and /etc/aliases... and did find "tunedin" in /etc/passwd, so is that why Mailman was able to deliver to tune...@tunedinweb.com ?? (I didn't find any of the other email addresses listed in /etc/postfix/transport in either of those files, so I don't know why some of those passed the telnet test and others did not) FYI... st...@tunedinweb.com now passes the telnet test: telnet localhost 25 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 tunedinweb.com ESMTP Postfix MAIL FROM: <st...@tunedinweb.com> 250 2.1.0 Ok RCPT TO: <st...@tunedinweb.com> 250 2.1.5 Ok quit 221 2.0.0 Bye Connection closed by foreign host. _____ Steve Wehr Tunedin Web Design 845-246-9643 -Original Message- From: Mark Sapiro [mailto:m...@msapiro.net] Sent: Saturday, September 10, 2016 12:24 PM To: Steve Wehr Cc: Mailman-Users@python.org Subject: Re: [Mailman-Users] mailman not respecting /etc/postfix/transport ??? On 09/10/2016 07:35 AM, Steve Wehr wrote: > I tried almost all the email addresses defined in > /etc/postfix/transport > > Many of them succeed in the telnet test below, but many of them fail. > There is no pattern I can find to success or failure. I thought maybe > there was some hidden characters in the file that were preventing the > hashing working when the file is compiled. So I was looking to see if > all the ones above a certain spot in the file failed, and all those > below succeeded, but that is not the case. Ideas? Are the ones that work in /etc/passwd and or /etc/aliases and the ones that fail not? I wrote: > Now, given that Postfix doesn't like st...@tunedinweb.com, the > question is what are the PHP scripts that mail to this address doing. > Are they connecting to this Postfix differently or even at all (maybe > they connect to mx.emailsrvr.com). The answer to this may still be of interest. > If you add > > local_recipient_maps = proxy:unix:passwd.byname $alias_maps > $transport_maps > > to Postfix main.cf, I think that will work. This is actually only > adding $transport_maps as proxy:unix:passwd.byname and $alias_maps are > the defaults. This will ensure that none of the addresses in > transport_maps > (/etc/postfix/transport) is rejected as an unknown local recipient. Have you tried this? I think it will work. If the answer to my first question above is yes, I'm sure it will work. -- Mark Sapiro <m...@msapiro.net>The highway is for gamblers, San Francisco Bay Area, Californiabetter 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/archive%40jab.org
Re: [Mailman-Users] mailman not respecting /etc/postfix/transport ???
I tried almost all the email addresses defined in /etc/postfix/transport Many of them succeed in the telnet test below, but many of them fail. There is no pattern I can find to success or failure. I thought maybe there was some hidden characters in the file that were preventing the hashing working when the file is compiled. So I was looking to see if all the ones above a certain spot in the file failed, and all those below succeeded, but that is not the case. Ideas? _ Steve Wehr Tunedin Web Design 845-246-9643 -Original Message- From: Steve Wehr [mailto:st...@tunedinweb.com] Sent: Saturday, September 10, 2016 10:22 AM To: 'Mark Sapiro' Cc: 'Mailman-Users@python.org' Subject: RE: [Mailman-Users] mailman not respecting /etc/postfix/transport ??? Here's another clue Mark... I had noticed that on some mailing lists I was subscribed as st...@tunedinweb.com, and on some others as tune...@tunedinweb.com. The former are failing as per my origilam problem, but the latter are sent successfully. So I tried: telnet localhost 25 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 tunedinweb.com ESMTP Postfix EHLO tunedinweb.com 250-tunedinweb.com 250-PIPELINING 250-SIZE 68157440 250-VRFY 250-ETRN 250-STARTTLS 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN MAIL FROM: <st...@tunedinweb.com> 250 2.1.0 Ok RCPT TO: <tune...@tunedinweb.com> 250 2.1.5 Ok quit 221 2.0.0 Bye Connection closed by foreign host. This works! Why?? Both st...@tunedinweb.com and tune...@tunedinweb.com are defined exactly the same in /etc/postfix/transport. _____ Steve Wehr Tunedin Web Design 845-246-9643 -Original Message- From: Mark Sapiro [mailto:m...@msapiro.net] Sent: Friday, September 09, 2016 1:38 PM To: Steve Wehr Cc: Mailman-Users@python.org Subject: Re: [Mailman-Users] mailman not respecting /etc/postfix/transport ??? On 09/09/2016 07:33 AM, Steve Wehr wrote: > Thanks Mark, Here are the results of the tests you suggested. Both > attempts at telnet failed. > > Tried your experiment: > > /etc/postfix>telnet localhost 25 > Trying ::1... > telnet: connect to address ::1: Connection refused Trying 127.0.0.1... > Connected to localhost. Interesting. I suggest you put SMTPHOST = '127.0.0.1' in mm_cfg.py since 'localhost' seems to resolve at least first to an IPv6 address on which Postfix isn't listening. I don't see exactly how this will help, but it might. Now, given that Postfix doesn't like st...@tunedinweb.com, the question is what are the PHP scripts that mail to this address doing. Are they connecting to this Postfix differently or even at all (maybe they connect to mx.emailsrvr.com). > /etc/postfix/transport: > st...@tunedinweb.comsmtp:mx.emailsrvr.com > ste...@tunedinweb.com smtp:mx.emailsrvr.com > ste...@tunedinweb.com smtp:mx.emailsrvr.com > w...@tunedinweb.com smtp:mx.emailsrvr.com > sti...@tunedinweb.com smtp:mx.emailsrvr.com > ad...@tunedinweb.comsmtp:mx.emailsrvr.com > err...@tunedinweb.com smtp:mx.emailsrvr.com > eve...@tunedinweb.com smtp:mx.emailsrvr.com > feedb...@tunedinweb.com smtp:mx.emailsrvr.com > em...@tunedinweb.comsmtp:mx.emailsrvr.com > ideachamp_or...@tunedinweb.com smtp:mx.emailsrvr.com > inqu...@tunedinweb.com smtp:mx.emailsrvr.com > mail...@tunedinweb.com smtp:mx.emailsrvr.com > mailman_ad...@tunedinweb.comsmtp:mx.emailsrvr.com > mailman-ow...@tunedinweb.comsmtp:mx.emailsrvr.com > ord...@tunedinweb.com smtp:mx.emailsrvr.com > payme...@tunedinweb.com smtp:mx.emailsrvr.com > r...@tunedinweb.com smtp:mx.emailsrvr.com > secur...@tunedinweb.com smtp:mx.emailsrvr.com > tune...@tunedinweb.com smtp:mx.emailsrvr.com > ver...@tunedinweb.com smtp:mx.emailsrvr.com > ab...@tunedinweb.comsmtp:mx.emailsrvr.com > postmas...@tunedinweb.com smtp:mx.emailsrvr.com If you add local_recipient_maps = proxy:unix:passwd.byname $alias_maps $transport_maps to Postfix main.cf, I think that will work. This is actually only adding $transport_maps as proxy:unix:passwd.byname and $alias_maps are the defaults. This will ensure that none of the addresses in transport_maps (/etc/postfix/transport) is rejected as an unknown local recipient. It appears that Postfix is doing the local recipient check before consulting transport_maps for a transport. I'm not that knowledgeable about the details of Postfix to fully understand this, but I think adding $transport_maps to local_recipient_maps in this case will solve your issue without causing other problems, but I suggest you test and be prepared to reverse when you do this. -- Mark Sapiro <m...@ms
Re: [Mailman-Users] mailman not respecting /etc/postfix/transport ???
Here's another clue Mark... I had noticed that on some mailing lists I was subscribed as st...@tunedinweb.com, and on some others as tune...@tunedinweb.com. The former are failing as per my origilam problem, but the latter are sent successfully. So I tried: telnet localhost 25 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 tunedinweb.com ESMTP Postfix EHLO tunedinweb.com 250-tunedinweb.com 250-PIPELINING 250-SIZE 68157440 250-VRFY 250-ETRN 250-STARTTLS 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN MAIL FROM: <st...@tunedinweb.com> 250 2.1.0 Ok RCPT TO: <tune...@tunedinweb.com> 250 2.1.5 Ok quit 221 2.0.0 Bye Connection closed by foreign host. This works! Why?? Both st...@tunedinweb.com and tune...@tunedinweb.com are defined exactly the same in /etc/postfix/transport. _____ Steve Wehr Tunedin Web Design 845-246-9643 -Original Message- From: Mark Sapiro [mailto:m...@msapiro.net] Sent: Friday, September 09, 2016 1:38 PM To: Steve Wehr Cc: Mailman-Users@python.org Subject: Re: [Mailman-Users] mailman not respecting /etc/postfix/transport ??? On 09/09/2016 07:33 AM, Steve Wehr wrote: > Thanks Mark, Here are the results of the tests you suggested. Both > attempts at telnet failed. > > Tried your experiment: > > /etc/postfix>telnet localhost 25 > Trying ::1... > telnet: connect to address ::1: Connection refused Trying 127.0.0.1... > Connected to localhost. Interesting. I suggest you put SMTPHOST = '127.0.0.1' in mm_cfg.py since 'localhost' seems to resolve at least first to an IPv6 address on which Postfix isn't listening. I don't see exactly how this will help, but it might. Now, given that Postfix doesn't like st...@tunedinweb.com, the question is what are the PHP scripts that mail to this address doing. Are they connecting to this Postfix differently or even at all (maybe they connect to mx.emailsrvr.com). > /etc/postfix/transport: > st...@tunedinweb.comsmtp:mx.emailsrvr.com > ste...@tunedinweb.com smtp:mx.emailsrvr.com > ste...@tunedinweb.com smtp:mx.emailsrvr.com > w...@tunedinweb.com smtp:mx.emailsrvr.com > sti...@tunedinweb.com smtp:mx.emailsrvr.com > ad...@tunedinweb.comsmtp:mx.emailsrvr.com > err...@tunedinweb.com smtp:mx.emailsrvr.com > eve...@tunedinweb.com smtp:mx.emailsrvr.com > feedb...@tunedinweb.com smtp:mx.emailsrvr.com > em...@tunedinweb.comsmtp:mx.emailsrvr.com > ideachamp_or...@tunedinweb.com smtp:mx.emailsrvr.com > inqu...@tunedinweb.com smtp:mx.emailsrvr.com > mail...@tunedinweb.com smtp:mx.emailsrvr.com > mailman_ad...@tunedinweb.comsmtp:mx.emailsrvr.com > mailman-ow...@tunedinweb.comsmtp:mx.emailsrvr.com > ord...@tunedinweb.com smtp:mx.emailsrvr.com > payme...@tunedinweb.com smtp:mx.emailsrvr.com > r...@tunedinweb.com smtp:mx.emailsrvr.com > secur...@tunedinweb.com smtp:mx.emailsrvr.com > tune...@tunedinweb.com smtp:mx.emailsrvr.com > ver...@tunedinweb.com smtp:mx.emailsrvr.com > ab...@tunedinweb.comsmtp:mx.emailsrvr.com > postmas...@tunedinweb.com smtp:mx.emailsrvr.com If you add local_recipient_maps = proxy:unix:passwd.byname $alias_maps $transport_maps to Postfix main.cf, I think that will work. This is actually only adding $transport_maps as proxy:unix:passwd.byname and $alias_maps are the defaults. This will ensure that none of the addresses in transport_maps (/etc/postfix/transport) is rejected as an unknown local recipient. It appears that Postfix is doing the local recipient check before consulting transport_maps for a transport. I'm not that knowledgeable about the details of Postfix to fully understand this, but I think adding $transport_maps to local_recipient_maps in this case will solve your issue without causing other problems, but I suggest you test and be prepared to reverse when you do this. -- Mark Sapiro <m...@msapiro.net>The highway is for gamblers, San Francisco Bay Area, Californiabetter 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/archive%40jab.org
Re: [Mailman-Users] mailman not respecting /etc/postfix/transport ???
Thanks Mark, Here are the results of the tests you suggested. Both attempts at telnet failed. Tried your experiment: /etc/postfix>telnet localhost 25 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 tunedinweb.com ESMTP Postfix EHLO tunedinweb.com 250-tunedinweb.com 250-PIPELINING 250-SIZE 68157440 250-VRFY 250-ETRN 250-STARTTLS 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN MAIL FROM: <st...@tunedinweb.com> 250 2.1.0 Ok RCPT TO: <st...@tunedinweb.com> 550 5.1.1 <st...@tunedinweb.com>: Recipient address rejected: User unknown in local recipient table quit 221 2.0.0 Bye Connection closed by foreign host. /etc/postfix>telnet 127.0.0.1 25 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. 220 tunedinweb.com ESMTP Postfix EHLO tunedinweb.com 250-tunedinweb.com 250-PIPELINING 250-SIZE 68157440 250-VRFY 250-ETRN 250-STARTTLS 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN MAIL FROM: <st...@tunedinweb.com> 250 2.1.0 Ok RCPT TO: <st...@tunedinweb.com> 550 5.1.1 <st...@tunedinweb.com>: Recipient address rejected: User unknown in local recipient table quit 221 2.0.0 Bye Connection closed by foreign host. from Defaults.py. Not in mm_cfg.py SMTPHOST = 'localhost' SMTPPORT = 0 /etc/postfix/mydomains: localhost OK tunedin OK # Always keep tunedinweb.com as a local domain, so that we can process mailman # email commands tunedinweb.com OK /etc/postfix/transport: st...@tunedinweb.comsmtp:mx.emailsrvr.com ste...@tunedinweb.com smtp:mx.emailsrvr.com ste...@tunedinweb.com smtp:mx.emailsrvr.com w...@tunedinweb.com smtp:mx.emailsrvr.com sti...@tunedinweb.com smtp:mx.emailsrvr.com ad...@tunedinweb.comsmtp:mx.emailsrvr.com err...@tunedinweb.com smtp:mx.emailsrvr.com eve...@tunedinweb.com smtp:mx.emailsrvr.com feedb...@tunedinweb.com smtp:mx.emailsrvr.com em...@tunedinweb.comsmtp:mx.emailsrvr.com ideachamp_or...@tunedinweb.com smtp:mx.emailsrvr.com inqu...@tunedinweb.com smtp:mx.emailsrvr.com mail...@tunedinweb.com smtp:mx.emailsrvr.com mailman_ad...@tunedinweb.comsmtp:mx.emailsrvr.com mailman-ow...@tunedinweb.comsmtp:mx.emailsrvr.com ord...@tunedinweb.com smtp:mx.emailsrvr.com payme...@tunedinweb.com smtp:mx.emailsrvr.com r...@tunedinweb.com smtp:mx.emailsrvr.com secur...@tunedinweb.com smtp:mx.emailsrvr.com tune...@tunedinweb.com smtp:mx.emailsrvr.com ver...@tunedinweb.com smtp:mx.emailsrvr.com ab...@tunedinweb.comsmtp:mx.emailsrvr.com postmas...@tunedinweb.com smtp:mx.emailsrvr.com (mx.emailsrvr.com is the rackspace email server where the mailbox for tunedinweb.com is hosted.) _ Steve Wehr Tunedin Web Design 845-246-9643 -Original Message- From: Mark Sapiro [mailto:m...@msapiro.net] Sent: Thursday, September 08, 2016 5:51 PM To: Steve Wehr Cc: Mailman-Users@python.org Subject: Re: [Mailman-Users] mailman not respecting /etc/postfix/transport ??? On 09/08/2016 02:02 PM, Steve Wehr wrote: > Here it is > > /etc/postfix>postconf -n ... > mydestination = hash:/etc/postfix/mydomains What's in /etc/postfix/mydomains ... > transport_maps = hash:/etc/postfix/transport What's in /etc/postfix/transport And what's in Mailman's Defaults.py/mm_cfg.py for SMTPPORT Before answering the above try the following: Assuming the Defaults.py settings are: SMTPHOST = 'localhost' SMTPPORT = 0 and they aren't overridden in mm_cfg.py, try the following shell session (postfix replies not shown) $ telnet localhost 25 EHLO tunedinweb.com MAIL FROM: <st...@tunedinweb.com> RCPT TO: <st...@tunedinweb.com> DATA . QUIT If that gives the error, try the same thing, but do $ telnet 127.0.0.1 25 to start. If that works but 'localhost' gives the reject try adding localhost to mynetworks = 23.253.149.133/32, 127.0.0.0/8, 10.208.195.27/32 and if that doesn't solve it, add SMTPHOST = '127.0.0.1' to mm_cfg.py. -- Mark Sapiro <m...@msapiro.net>The highway is for gamblers, San Francisco Bay Area, Californiabetter 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/archive%40jab.org
Re: [Mailman-Users] mailman not respecting /etc/postfix/transport ???
Here it is /etc/postfix>postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix debug_peer_level = 2 debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin xxgdb $daemon_directory/$process_name $process_id & sleep 5 home_mailbox = Maildir/ html_directory = no inet_interfaces = all inet_protocols = ipv4 mail_owner = postfix mailbox_command = /usr/bin/procmail mailbox_size_limit = 25600 mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man message_size_limit = 68157440 mydestination = hash:/etc/postfix/mydomains myhostname = tunedinweb.com mynetworks = 23.253.149.133/32, 127.0.0.0/8, 10.208.195.27/32 newaliases_path = /usr/bin/newaliases.postfix queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/postfix-2.10.1/README_FILES recipient_delimiter = + sample_directory = /usr/share/doc/postfix-2.10.1/samples sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop smtp_sasl_security_options = noplaintext smtp_tls_loglevel = 1 smtpd_banner = $myhostname ESMTP $mail_name smtpd_recipient_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_rbl_client sbl.spamhaus.org, reject_rbl_client xbl.spamhaus.org, reject_unauth_destination, check_policy_service unix:postgrey/socket smtpd_sasl_auth_enable = yes smtpd_sasl_local_domain = $myhostname smtpd_sasl_security_options = noanonymous smtpd_tls_auth_only = yes smtpd_tls_cert_file = /etc/postfix/postfix.crt smtpd_tls_key_file = /etc/postfix/postfix.key smtpd_tls_loglevel = 1 smtpd_tls_received_header = yes smtpd_use_tls = yes transport_maps = hash:/etc/postfix/transport unknown_local_recipient_reject_code = 550 virtual_alias_maps = hash:/etc/postfix/virtual _____ Steve Wehr Tunedin Web Design 845-246-9643 -Original Message- From: Mark Sapiro [mailto:m...@msapiro.net] Sent: Thursday, September 08, 2016 11:21 AM To: Steve Wehr Cc: Mailman-Users@python.org Subject: Re: [Mailman-Users] mailman not respecting /etc/postfix/transport ??? On 09/08/2016 08:03 AM, Steve Wehr wrote: > > To answer your questions Mark... ... > What information could I provide to help figure out why? How about > What do you have for Postfix mynetworks and smtpd_recipient_restrictions? > (The output from 'postconf -n' might be > useful.) > -- Mark Sapiro <m...@msapiro.net>The highway is for gamblers, San Francisco Bay Area, Californiabetter 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/archive%40jab.org
Re: [Mailman-Users] mailman not respecting /etc/postfix/transport ???
I am picking up this old thread that I never solved. Sorry for the delay. To answer your questions Mark... > This almost certainly is not a Mailman thing. I suspect the issue is because the mail > arrives from localhost[127.0.0.1], not because it's from Mailman. Well... There are several other PHP programs on my server that also send email to st...@tunedinweb.com, and those all work fine -- the /etc/postfix/transport file is respected and the mail routed off-platform. Only the mail sent by Mailman is being rejected with postfix errors I included below. What information could I provide to help figure out why? _ Steve Wehr Tunedin Web Design -Original Message- From: Mailman-Users [mailto:mailman-users-bounces+steve=tunedinweb@python.org] On Behalf Of Mark Sapiro Sent: Wednesday, June 22, 2016 12:22 PM To: mailman-users@python.org Subject: Re: [Mailman-Users] mailman not respecting /etc/postfix/transport ??? On 06/22/2016 07:53 AM, Steve Wehr wrote: > > The issue is that my email address st...@tunedinweb.com is also a > member of several mailing lists. When mailman tries to send to > st...@tunedinweb.com I see this error message in the postfix log /var/log/maillog: > > Jun 6 17:02:08 166941-web1 postfix/smtpd[25836]: NOQUEUE: reject: > RCPT from > localhost[127.0.0.1]: 550 5.1.1 <st...@tunedinweb.com>: Recipient > address > rejected: User unknown in local recipient table; > from=<tunedin-temp-bounces+steve=tunedinweb@tunedinweb.com> > to=<st...@tunedinweb.com> proto=ESMTP > helo=<166941-web1.tunedinweb.com> > > So it seems that mailman is not respecting the /etc/postfix transport > file settings. I want mailman to send mail for those addresses > specified in the transport file to the server where that email is hosted. Well, yes and no. Something is causing the mail from Mailman lists to be rejected by Postfix for "User unknown in local recipient table" before transport_maps is consulted for this user. This almost certainly is not a Mailman thing. I suspect the issue is because the mail arrives from localhost[127.0.0.1], not because it's from Mailman. What do you have for Postfix mynetworks and smtpd_recipient_restrictions? (The output from 'postconf -n' might be useful.) -- Mark Sapiro <m...@msapiro.net>The highway is for gamblers, San Francisco Bay Area, Californiabetter 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/steve%40tunedinweb.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/archive%40jab.org
Re: [Mailman-Users] AOL rejecting connections from mailman servers for DMARC Munging.
I recently have been fighting AOL over this exact same thing. To solve it I contacted AOL via their postmaster page and opened a ticket. They got back to me and said they "made some changes to their handling of mail from my IP address." I had been using mailman to send to AOL users for over a decade, so I didn't change anything in mailman. After about 2-3 weeks AOL has now stopped rejecting mailman emails. In the interim, I used Mark Sapiro's script to reset the moderation bits on all AOL users, encased in a little shell script I wrote: #!/bin/bash # This script resets the bounce bits for certain users in ALL lists. # # Run this script as ROOT for listname in $(ls /var/lib/mailman/lists/); do echo Resetting bounce bits in list $listname # Reset bounce bits for only AOL.COM members. /usr/lib/mailman/bin/withlist -r reset_bounce $listname -d aol.com done; Hope this is helpful. _____ Steve Wehr Tunedin Web Design 845-246-9643 -Original Message- From: Mailman-Users [mailto:mailman-users-bounces+steve=tunedinweb@python.org] On Behalf Of Ted Hatfield Sent: Tuesday, August 23, 2016 6:56 PM To: mailman-users@python.org Subject: [Mailman-Users] AOL rejecting connections from mailman servers for DMARC Munging. Hey all, Recently my mailman server was flagged by AOL and my messages were rejected with this error. SMTP DATA-2 protocol error: 521 5.2.1 : AOL will not accept delivery of this message. When I queried the AOL Postmaster about this issue this was my response. Few mails from IP xxx.xxx.xxx.xx were getting rejected from one of filters as Reply-to address is same as the TO address. This is caused as one of our filters triggered these emails as spam. I have added protection for your IP. As a good mailing practice, please use a different email address for your reply-to address. It seems to me that since dmarc munging adds the senders address to the reply-to header, if a user receives a copy of their own postings this is the result. Can anyone else confirm that this has happened to them and if so what else can someone do except to wrap the message from senders that implement dmarc rejection as in dmarc_moderation_action? Is there a recommended policy regarding this issue? Ted Hatfield -- 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/steve%40tunedinweb.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/archive%40jab.org
[Mailman-Users] mailman not respecting /etc/postfix/transport ???
I have about 100 mailing lists all using the domain name tunedinweb.com. All the commands to subscribe, etc, come to someth...@tunedinweb.com which come to my server and are processed by mailman. But I also have real email boxes @tunedinweb.com. Those are hosted off my server. So in order to make both mailman and my email work I have postfix configured with tunedinweb.com listed in the mydomains file, but have setup a transport file to tell postfix to redirect any email for someth...@tunedinweb.com to the server where that email is hosted. With lines in transport that look like this: st...@tunedinweb.comsmtp:mx.emailsrvr.com ste...@tunedinweb.com smtp:mx.emailsrvr.com This is all working fine. The issue is that my email address st...@tunedinweb.com is also a member of several mailing lists. When mailman tries to send to st...@tunedinweb.com I see this error message in the postfix log /var/log/maillog: Jun 6 17:02:08 166941-web1 postfix/smtpd[25836]: NOQUEUE: reject: RCPT from localhost[127.0.0.1]: 550 5.1.1 <st...@tunedinweb.com>: Recipient address rejected: User unknown in local recipient table; from=<tunedin-temp-bounces+steve=tunedinweb@tunedinweb.com> to=<st...@tunedinweb.com> proto=ESMTP helo=<166941-web1.tunedinweb.com> So it seems that mailman is not respecting the /etc/postfix transport file settings. I want mailman to send mail for those addresses specified in the transport file to the server where that email is hosted. I must be missing something. Can someone explain what is going wrong. Thanks again for your help. _ Steve Wehr Tunedin Web Design <http://www.tunedinweb.com/> 845-246-9643 -- 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
[Mailman-Users] Valid emails being unsubscribed?
Hi Mark and friends, I host about 100 mailing lists for clients, and have recently moved to a new installation of mailman. My clients are telling me they get lots of notices of people being unsubscribed from their lists, that they never got before, on the older version of mailman. I've been trying to validate the unsubscribes, but I'm not sure how to do it. I look in mailman's bounce log, and see that bounces are being received and users are being unsubscribe. I looked in the postfix maillog, and I see successful sends to these users, then a bounce would be returned. I've done some spot checks by sending an email from my personal email account to a few of the users who have been unsubscribed, and all those emails go through successfully and are not bounced back to me. The users tell me they are not unsubscribing from the list. I've also see some emails being unsubscribed in the bounce log, that I personally sent to and know that those are valid email addresses. Where could I go to learn more about why bounces are received, and try to debug this problem? Does the community have any suggestions for me? Thanks. --- Steve Wehr Tunedin Web Design www.Tunedinweb.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/archive%40jab.org
[Mailman-Users] Getting lots of unsubscribe emails after migrating to new mailman version
I host about 75 mailing lists for my clients. Last week I completed a migration to a new server and mailman 2.1.20. Ever since then mailman has been sending hundreds of unsubscribe notifications to many (but not all) of the list owners. The emails addresses in question seem to be old bad addresses that are being bounced. But one user has been receiving 250 such emails per day. Why did this happen after the emigration? Should I just let mailman run it's course and these will stop on their own? Are there some files I can check to see what is going on? Thanks to the community for your help. _ Steve Wehr Tunedin Web Design <http://www.tunedinweb.com/> 845-246-9643 -- 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
[Mailman-Users] Command output: post script, list not found: XXXXX
First of all I apologize of there is already ananswer to this question. I have been googling and reading your doc for days in hopes of finding an answer. I was running mailman successfully for years on my server. Then this week I cut over to a new server and hired someone to install the latest version of mailman and migrate all my existing lists. This mostly works. I can run /usr/lib/mailman/bin/list_lists and all my lists are displayed. I can use the mailman admin page to list all my lists and I can edit each of them from there. But when I try to send email to any list, my email is sent back to me with the following message: <t...@tunedinweb.com>: Command died with status 1: "/usr/lib/mailman/mail/mailman post test". Command output: post script, list not found: test I have run: root: /usr/lib/mailman/bin>sudo -u mail /usr/lib/mailman/mail/mailman post test ls -ld test drwxrwsr-x 2 apache mailman 4096 Apr 15 17:35 test root: /var/lib/mailman/lists>ls -l test total 20 -rw-rw 1 apache mailman 5061 Apr 15 17:35 config.pck -rw-rw 1 apache mailman 5060 Apr 15 17:34 config.pck.last -rw-rw-r-- 1 root mailman 22 Mar 29 13:50 request.pck Can you help me find out what is wrong? Thanks. _____ Steve Wehr Tunedin Web Design <http://www.tunedinweb.com/> 845-246-9643 -- 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
[Mailman-Users] How to include the email address of the recipient in the mailing
One problem we always have with mailing lists is that people forget which email address they used to subscribe. Often our subscribers have email aliases that they use. For example: a user subscribes to our mailing list as [EMAIL PROTECTED] This address is setup to forward mail to their real email address: [EMAIL PROTECTED] So now they get a mailing from Mailman at [EMAIL PROTECTED] They reply that they want to unsubscribe, and cannot, since [EMAIL PROTECTED] is not a member of the list. To help combat this I would like to add their %(email)s variable to the msg_footer. I'd like to say something like: You are subscribed to this list as %(email)s. But that variable is not allowed there. Can you suggest another solution?? Thanks! Steve Wehr Tunedin Web Design - TunedinWeb.com http://www.hvpages.com/ mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
[Mailman-Users] How to get status of the progress of sending to a large list
Hi, I'm converting my Lyris mailing lists to Mailman and so far so good. One feature that Lyris has is the ability to send a progress report to the person who posts an email to the list. This progress report shows how many list members have received the email so far and how many times Lyris has tried to send the mailing. Lyris keeps sending this report to the poster until all users on the list have received the mailing or it gives up on those who keep bouncing. This can take several days. I'm using Mailman to create mailing lists for some unsophisticated clients, and this feature was very reassuring to them that their email really got to all the list members. Is there anything like this I can setup with Mailman?? Thanks. Steve Wehr Tunedin Web Design - TunedinWeb.com -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
