[Mailman-Users] Strange rejection
I'm moving mailing lists from one server to another using a couple of scripts which I've used successfully many times before for other such moves. On the 3rd list I've moved (second domain name) I've run into a very strange problem. On trying to post to the list on the new server my posts get delivered to the list and discarded with no further explanation. The vette logfile just says: Oct 24 23:15:30 2014 (2180) Message discarded, msgid: 1414210524.38839.9.ca...@pudina.fmp.com The Mailman version on the old system is 2.1.18, and 2.1.18-1 on the new one. The working environment is almost identical on both systems. The list configurations are completely identical. The two other lists which I've already moved to the new location are working properly, as best I can tell so far. I'm subscribed to the list, which is an open discussion list, added myself as a list moderator, and am on the accept_these_nonmembers list (or not - it makes no difference) in case I should get unsubscribed. The only thing I see which _might_ make a difference is that the new server is running Python 2.7.6 while the old one is running 2.7.3. I backed out the move and posted to this problem list in its old location, and the post went trough to the subscribers and the archive. There are no other related entries in the Mailman log files - just Message discarded in the vette file. Is there any way to turn on more thorough debugging, or tracebacks if there are hidden code glitches? What could be causing this? I'm Python-literate and can read tracebacks and poke diagnostic code into Mailman modules if someone can point me in the right direction to get to the bottom of this. I've got half a dozen or so lists to move so I have to get this solved. -- Lindsay Haisley | Everything works if you let it FMP Computer Services | 512-259-1190 | --- The Roadie http://www.fmp.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] Strange rejection
On 10/24/2014 11:17 PM, Lindsay Haisley wrote: The vette logfile just says: Oct 24 23:15:30 2014 (2180) Message discarded, msgid: 1414210524.38839.9.ca...@pudina.fmp.com Some handler in the pipeline is discarding the message. More below. Is there any way to turn on more thorough debugging, or tracebacks if there are hidden code glitches? At some point I augmented he vette logging for rejects to include the name of the handler and the reject reason. I jhought I had done something similar for discards, but I didn't. What could be causing this? I'm Python-literate and can read tracebacks and poke diagnostic code into Mailman modules if someone can point me in the right direction to get to the bottom of this. I've got half a dozen or so lists to move so I have to get this solved. In Mailman/Queue/IncomingRunner.py, in the _dopipeline() method look at the code for the except Errors.DiscardMessage: clause and the except Errors.RejectMessage, e: clause. Augment the syslog message in except Errors.DiscardMessage: similarly to that in except Errors.RejectMessage, e:, except there is no 'e' in the discard case so you can't include the 'reason:' part. Note that the only standard handlers that discard messages are MimeDel: Content filtering - filter_action = Discard Moderate: Privacy options... - Sender filters - member_moderation_action dmarc_moderation_action discard_these_nonmembers generic_nonmember_action Scrubber: if Non-digest options - scrub_nondigest is Yes and mm_cfg.ARCHIVE_HTML_SANITIZER = 0 and the outer message is text/html SpamDetect: Privacy options... - Spam filters - header_filter_rules with discard action header matches something in mm_cfg.KNOWN_SPAMMERS If you examine the above for Discard actions and maybe (temporarily) change them to Hold, that may help. -- Mark Sapiro m...@msapiro.netThe 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] Strange rejection
On Sat, 2014-10-25 at 08:36 -0700, Mark Sapiro wrote:
In Mailman/Queue/IncomingRunner.py, in the _dopipeline() method look at
the code for the except Errors.DiscardMessage: clause
and the except Errors.RejectMessage, e: clause. Augment the syslog
message in except Errors.DiscardMessage: similarly to that in except
Errors.RejectMessage, e:, except there is no 'e' in the discard case so
you can't include the 'reason:' part.
Thanks, Mark! This will at least tell me where my posts are getting
nuked.
Does this look correct?
--- IncomingRunner.py.orig 2014-10-25 10:53:02.0 -0500
+++ IncomingRunner.py 2014-10-25 11:03:40.0 -0500
@@ -157,8 +157,11 @@
os._exit(1)
except Errors.DiscardMessage:
# Throw the message away; we need do nothing else with it.
-syslog('vette', 'Message discarded, msgid: %s',
- msg.get('message-id', 'n/a'))
+syslog('vette', Message discarded, msgid: %s
+ list: %s,
+ handler: %s,
+ msg.get('message-id', 'n/a'),
+ mlist.real_name, handler)
return 0
except Errors.HoldMessage:
# Let the approval process take it from here. The message no
A test list posts correctly, so no stupid syntax or indentation errors
(which shouldn't be a problem anyway since the added code is all inside
a function call argument list)
I'm a great fan of intelligent logging! This would be a good mod for a
future version of MM 2.
--
Lindsay Haisley | Everything works if you let it
FMP Computer Services |
512-259-1190 | --- The Roadie
http://www.fmp.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] Strange rejection
On 10/25/2014 09:20 AM, Lindsay Haisley wrote:
Does this look correct?
--- IncomingRunner.py.orig2014-10-25 10:53:02.0 -0500
+++ IncomingRunner.py 2014-10-25 11:03:40.0 -0500
@@ -157,8 +157,11 @@
os._exit(1)
except Errors.DiscardMessage:
# Throw the message away; we need do nothing else with it.
-syslog('vette', 'Message discarded, msgid: %s',
- msg.get('message-id', 'n/a'))
+syslog('vette', Message discarded, msgid: %s
+ list: %s,
+ handler: %s,
+ msg.get('message-id', 'n/a'),
+ mlist.real_name, handler)
return 0
except Errors.HoldMessage:
# Let the approval process take it from here. The message no
Yes, it looks right.
A test list posts correctly, so no stupid syntax or indentation errors
(which shouldn't be a problem anyway since the added code is all inside
a function call argument list)
I'm a great fan of intelligent logging! This would be a good mod for a
future version of MM 2.
I plan to do it. I don't know why I didn't do it at the same time as the
reject logging enhancement, but I'll do it now.
--
Mark Sapiro m...@msapiro.netThe 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 Htdig integration with Nginx - Path variables
On 10/23/2014 01:56 AM, Andrew Hodgson wrote: The second issue is that the htdig CGI needs to be using HTTP and not HTTPS. I made this available under the HTTP context so nightly_htdig can crawl the archives. The htdig script is now not available under HTTPS. At one point I ran into this on my own site when trying to unconditionally use HTTPS. I looked at it at the time, and I think htdig can be made to use HTTPS, but I never followed up with it. Maybe I'll look again. -- Mark Sapiro m...@msapiro.netThe 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
[Mailman-Users] Change Mailman URLs on Subscribe Response
Since you're using Drupal (http://www.raystedman.org/CHANGELOG.txt), you might want to look at the User Mailman Register module: https://www.drupal.org/project/user_mailman_register It allows you to manage Mailman subscriptions from within your Drupal installation. Your users will never need to see the Mailman pages. (By the way your Drupal installation is extremely out of date ... and you really should hide that CHANGELOG.txt file so that people like me can't find out so easily that your Drupal installation is extremely out of date.) rac -- 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] Change Mailman URLs on Subscribe Response
Ooh, that's an interesting module. I currently have a Drupal site where people who want to join my list sign into Drupal using a special account I've set up, then go through a Webform that explains the list rules and then get forwarded to the Mailman subscription page. I wonder if this would be a more elegant solution. Thanks for posting that. Tracey -Original Message- From: Mailman-Users [mailto:mailman-users-bounces+tracey=fairhousing@python.org] On Behalf Of Russell Clemings Sent: Saturday, October 25, 2014 4:33 PM To: mailman-users@python.org Subject: [Mailman-Users] Change Mailman URLs on Subscribe Response Since you're using Drupal (http://www.raystedman.org/CHANGELOG.txt), you might want to look at the User Mailman Register module: https://www.drupal.org/project/user_mailman_register It allows you to manage Mailman subscriptions from within your Drupal installation. Your users will never need to see the Mailman pages. (By the way your Drupal installation is extremely out of date ... and you really should hide that CHANGELOG.txt file so that people like me can't find out so easily that your Drupal installation is extremely out of date.) rac -- 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/tracey%40fairhousing.c om -- 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] Change Mailman URLs on Subscribe Response
It would be a little different. The main difference is that the Mailman subscriptions are linked to the Drupal user account, so each subscriber would need to be a Drupal user. I think there's also a way to import existing Mailman subscriptions and create Drupal users for them, but I may be remembering a different module, Mailman Manager: https://www.drupal.org/project/mailman_manager rac -- Forwarded message -- From: Tracey McCartney tra...@fairhousing.com To: mailman-users@python.org Cc: Date: Sat, 25 Oct 2014 18:23:51 -0500 Subject: Re: [Mailman-Users] Change Mailman URLs on Subscribe Response Ooh, that's an interesting module. I currently have a Drupal site where people who want to join my list sign into Drupal using a special account I've set up, then go through a Webform that explains the list rules and then get forwarded to the Mailman subscription page. I wonder if this would be a more elegant solution. Thanks for posting that. Tracey -Original Message- From: Mailman-Users [mailto:mailman-users-bounces+tracey=fairhousing@python.org] On Behalf Of Russell Clemings Sent: Saturday, October 25, 2014 4:33 PM To: mailman-users@python.org Subject: [Mailman-Users] Change Mailman URLs on Subscribe Response Since you're using Drupal (http://www.raystedman.org/CHANGELOG.txt), you might want to look at the User Mailman Register module: https://www.drupal.org/project/user_mailman_register It allows you to manage Mailman subscriptions from within your Drupal installation. Your users will never need to see the Mailman pages. (By the way your Drupal installation is extremely out of date ... and you really should hide that CHANGELOG.txt file so that people like me can't find out so easily that your Drupal installation is extremely out of date.) rac -- 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/tracey%40fairhousing.c om -- 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] Squirrelmail and wrapped messages
I've converted a list to Mailman, and as I posted previously, I decided to use wrapped messages to keep AOL's hairtrigger spam filters from discarding incoming messages from AOL users. Now I'm getting complaints from Outlook 2007 and Squirrelmail users that the messages from Mailman show up as text attachments that aren't automatically displayed or previewed. It looks like Outlook 2007 users can turn previewing on, but I don't see any such options for Squirrelmail. How have other Mailman admins dealt with this? I wonder if it's possible to to make wrapped messages a user preference, or have them only turned on for certain domains as discussed previously. Is this a patch that would be accepted in the future? -- Ed -- 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
