Re: [Mailman-Users] Mailman reusing message-id, leads to duplicate message suppression
* Stephen J. Turnbull step...@xemacs.org: Ralf Hildebrandt writes: Strictly speaking, all that womand wanted was to know if the message passed both mailing lists... So she should have more faith :) For lists hosted by the same Mailman, Mailman 3 might be able to In my case its two lists on the same mailman instance. -- Ralf Hildebrandt Charite Universitätsmedizin Berlin ralf.hildebra...@charite.deCampus Benjamin Franklin http://www.charite.de Hindenburgdamm 30, 12203 Berlin Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155 -- 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 reusing message-id, leads to duplicate message suppression
* Mark Sapiro m...@msapiro.net: On 11/05/2013 07:14 AM, Ralf Hildebrandt wrote: Strictly speaking, all that womand wanted was to know if the message passed both mailing lists... So she should have more faith :) In cases like this, I suggest that the user check the list's archive. Good point! Ralf Hildebrandt Charite Universitätsmedizin Berlin ralf.hildebra...@charite.deCampus Benjamin Franklin http://www.charite.de Hindenburgdamm 30, 12203 Berlin Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155 -- 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 reusing message-id, leads to duplicate message suppression
* Stephen J. Turnbull step...@xemacs.org: Note that the subject is incorrect. Mailman is not reusing the Message-ID, it is refusing to alter it which is correct behavior according to RFC 5322 (Message-ID is an originator field). I believe that according to RFC 5322 (and predecessors) Mailman SHOULD add a Resent-Message-ID to indicate that it handled the message, but I doubt this would change the duplicate-suppression behavior of Gmail and MS Exchange. I agree. The duplicate-suppression in Exchange uses both Message-ID and Date headers. Footnotes: [1] It's surprisingly difficult to handle duplicates truly gracefully. Ohhh yes. For example, I personally consider the mailing list copy to be the canonical copy of a post, but direct CCs often arrive more quickly. Same here. Happens all the time. -- Ralf Hildebrandt Charite Universitätsmedizin Berlin ralf.hildebra...@charite.deCampus Benjamin Franklin http://www.charite.de Hindenburgdamm 30, 12203 Berlin Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155 -- 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 reusing message-id, leads to duplicate message suppression
On Nov 06, 2013, at 09:05 AM, Stephen J. Turnbull wrote: For lists hosted by the same Mailman, Mailman 3 might be able to handle this by adding *both* List-Ids to the header, and only adding the (other) RFC 2369 headers for the list(s) the user is subscribed to. Of course this requires personalization, but that seems to be less and less a problem these days. MM2.1 adds X-BeenThere headers for every list the message flows through; these are to prevent loops. However MM3 got rid of this header in favor of the RFC 2919 List-ID headers. I took a quick look at that RFC just now and I didn't see anything about how many List-Id headers a message could have, but from the discussion it seems to assume there'd only be one header per message. If that solution is interesting to anybody, please let me know, and I'll check the relevant RFCs to see if multiple values are permissible for List-* headers (and for which ones). Code of course will depend on Barry's permission, but I suppose he wouldn't object to providing it as an option. Best to file a bug so we can explore the issue and solutions. You can then attach a branch to the bug. Cheers, -Barry signature.asc Description: PGP signature -- 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 reusing message-id, leads to duplicate message suppression
On Nov 06, 2013, at 09:51 AM, Ralf Hildebrandt wrote: I believe that according to RFC 5322 (and predecessors) Mailman SHOULD add a Resent-Message-ID to indicate that it handled the message, but I doubt this would change the duplicate-suppression behavior of Gmail and MS Exchange. This probably makes sense, so please submit a bug. Footnotes: [1] It's surprisingly difficult to handle duplicates truly gracefully. Ohhh yes. I've found 'd' in my MUA works about as well as anything. :) For example, I personally consider the mailing list copy to be the canonical copy of a post, but direct CCs often arrive more quickly. Same here. Happens all the time. Indeed. It would be great if you could suppress the direct CC, but of course, that's impossible since Mailman never sees them. The best you can do is suppress the list copy, but that isn't a great solution either if your MUA knows how to do sane things based on the List-* headers. -Barry -- 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 reusing message-id, leads to duplicate message suppression
In cases like this, I suggest that the user check the list's archive. Only if the list has an archive. --Barry Finkel -- 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] (solved) unable to start Mailman
Mark, It works fine now after I stopped the SELinux. Once again, thanks for your help. Charles On Wed, Nov 6, 2013 at 1:17 AM, c cc sub...@gmail.com wrote: withlist -l -r fix_url [listname} Okay, the lists are there now after I fixed the url. I will let you know see if it work when I get back to work tomorrow. Once again, thank you so much for your help and time. Charles On Wed, Nov 6, 2013 at 1:03 AM, c cc sub...@gmail.com wrote: Mark, Finally, I was able to get service mailman start to work, but in www.domain.com/mailman/listinfo only shows the list mailman, none of my old list are showing up. By the way, SElinux was the culprit, and once it was stopped, I was able to start mailman using: service mailman start. On Wed, Nov 6, 2013 at 12:34 AM, c cc sub...@gmail.com wrote: Mark, Thanks. I will double check all the permission on /var/lib/mailman/lists/ to make sure that they are all the same with the mailman list permission since that particular list was working fine before I moved the old lists over. I will send you the log files to your email tomorrow. Once again, thanks for your help. Charles On Tue, Nov 5, 2013 at 10:56 PM, Mark Sapiro m...@msapiro.net wrote: On 11/05/2013 06:38 PM, c cc wrote: Mark, No luck. [root@es1 bin]# ./check_perms -f directory must be at least 02775: /usr/lib/mailman (fixing) ... directory permissions must be 02775: /usr/lib/mailman/templates/eu (fixing) The permissions issues you have are with /var/lib/mailman/lists/. I don't know why check_perms is not picking those up. If you want, you can send me all of /var/lib/mailman/logs/error, but I won't be able to look at it in detail until Thurs eve. -- 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
