Re: [Mailman-Users] The right way to reply to a mailing list / Re:
A.K. Eyma a...@tip.nl wrote: snip Having all mail of a list come in with [listname] first in each subject line is more tidy. In that way you would differentiate at one glance in your inbox between Filtering maillist messages to a folder per list is a far more tidy way of dealing with the problem of identifying messages. Hell even Thunderbird can do that: https://support.mozilla.org/en-US/kb/organize-your-messages-using-filters Re: [Mailman-Users] The right way for responses that have been sent offlist to you and [Mailman-Users] Re: The right way for responses that have been sent onlist, i.e. via the list. [] is the list's 'stamp' on mails, why insert it after Re:? I am making sense, really! ;)) kind regards, Aayko Eyma -- Roel Wagenaar, Linux-User #469851 with the Linux Counter; http://linuxcounter.net/ Antw.: Omdat het de volgorde verstoord waarin mensen tekst lezen. Vraag: Waarom is top-posting een slechte gewoonte? Antw.: Top-posting. Vraag: Wat is het meest ergerlijke in e-mail? Diplomacy is the art of letting someone else get your way. -- 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] We're sorry, we hit a bug!
L.S. Bug in Mailman version 2.1.15 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. The above message shows up on the web pages, unfortunately the last log written to is qrunner, error is empty, so no info on what it is about. The last thing changed is the adres of the main pages. It looks like the mail-system is not affected, any idea what is going on? Would like to show some logging, but it simply is not there. -- Roel Wagenaar, Linux-User #469851 with the Linux Counter; http://linuxcounter.net/ Antw.: Omdat het de volgorde verstoord waarin mensen tekst lezen. Vraag: Waarom is top-posting een slechte gewoonte? Antw.: Top-posting. Vraag: Wat is het meest ergerlijke in e-mail? Why be difficult, when with a bit of effort, you can be impossible? -- 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] We're sorry, we hit a bug!
Mark Sapiro m...@msapiro.net wrote: The above message indicates the traceback was written to some 'error' log, just not the one you're looking at. You can always edit (temporarily) Mailman's scripts/driver and at line 33 change STEALTH_MODE = 1 to STEALTH_MODE = 0 and that will allow the traceback and other diagnostic info to be displayed instead of the We're sorry, we hit a bug! message. Would like to show some logging, but it simply is not there. It was successfully written to an 'error' log somewhere or the We're sorry, we hit a bug! message would say: Mailman experienced a very low level failure and could not even generate a useful traceback for you. Please report this to the Mailman administrator at this site. Thanks Mark, the page is showing that the log location was not writeable, must be the bug. Resetting the LOG_DIR to default saved me. Apologies for the noise. -- Roel Wagenaar, Linux-User #469851 with the Linux Counter; http://linuxcounter.net/ Antw.: Omdat het de volgorde verstoord waarin mensen tekst lezen. Vraag: Waarom is top-posting een slechte gewoonte? Antw.: Top-posting. Vraag: Wat is het meest ergerlijke in e-mail? Ignorence is when you don't know anything and somebody finds out. -- 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] unable to start Mailman
Tanstaafl tansta...@libertytrek.org wrote: (Sorry for replying to an older thread, I'm going back through older unread mails) Maybe these should be made an official part of mailman's extra tools? And maybe updated to work with MM3? And maybe you could stop TOP-posting? -- Roel Wagenaar, Linux-User #469851 with the Linux Counter; http://linuxcounter.net/ Antw.: Omdat het de volgorde verstoord waarin mensen tekst lezen. Vraag: Waarom is top-posting een slechte gewoonte? Antw.: Top-posting. Vraag: Wat is het meest ergerlijke in e-mail? Why be difficult, when with a bit of effort, you can be impossible? -- 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] Content-Transfer-Encoding: not workng as expected.
Mark Sapiro m...@msapiro.net wrote: I am guessing that you are talking about plain text message bodies with character set UTF-8, and your list is adding a msg_header or msg_footer, although there could be other cases as well. This issue is due to the Python email package. In order to add a msg_header or msg_footer to the message body, mailman has to do set_payload() on the email.message.Message instance. This in turn does set_charset() which encodes the body with the encoding of the body_encoding attribute of the email.charset.Charset instance for that character set. For UTF-8, this is base64. If my guess is correct, you may be able to avoid the re-encoding by making sure the list's msg_header and msg_footer are empty. Otherwise, you could look at Mailman/Handlers/Decorate.py and try adding the following near the beginning after import re import email.charset email.charset.CHARSETS['utf-8'] = (SHORTEST, None, 'utf-8') Yes, I have msg_footer active, and don't want it empty. I have adde your lines right after import re, and almost instantly get the We hit a bug message in the web interface. I have attached an extract from mailmans error log, hope the list will allow it. The error message is: admin(3051): from Mailman.Handlers.Decorate import decorate admin(3051): File /var/lib/mailman/Mailman/Handlers/Decorate.py, line 23, in module admin(3051): email.charset.CHARSETS['utf-8'] = (SHORTEST, None, 'utf-8') admin(3051): NameError: name 'SHORTEST' is not defined I have disabled the lines again. -- Roel Wagenaar, Linux-User #469851 with the Linux Counter; http://linuxcounter.net/ Antw.: Omdat het de volgorde verstoord waarin mensen tekst lezen. Vraag: Waarom is top-posting een slechte gewoonte? Antw.: Top-posting. Vraag: Wat is het meest ergerlijke in e-mail? Good judgement comes from experience. Unfortunately, experience comes from bad judgement. -- 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 is rewriting Message-Id
L.S.
As an experiment I have set up a read-only maillist with the help of these
notes:
http://whoopis.com/howtos/mailman-readonly-list.php
Seems to work fine, unfortunatily mailman is rewriting the Message-Id of the
injected emails.
From info on the web I was led to believe this should not happen, however I
can not find a config option to overrule this behaviour.
Is it save to alter /usr/lib/mailman/Mailman/Message.py so that the section:
if not self.has_key('message-id'):
self['Message-ID'] = Utils.unique_message_id(mlist)
is changed into:
if not self.has_key('message-id'):
self['List-Message-ID'] = Utils.unique_message_id(mlist)
Or will this create more problems than it solves?
Mailman is running on a dedicated virtual host, Debian 7
--
Roel Wagenaar,
Linux-User #469851 with the Linux Counter; http://linuxcounter.net/
Antw.: Omdat het de volgorde verstoord waarin mensen tekst lezen.
Vraag: Waarom is top-posting een slechte gewoonte?
Antw.: Top-posting.
Vraag: Wat is het meest ergerlijke in e-mail?
What happens if you get scared half to death twice?
--
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 is rewriting Message-Id
Mark Sapiro m...@msapiro.net wrote: On 11/13/2013 05:53 AM, Roel Wagenaar wrote: As an experiment I have set up a read-only maillist with the help of these notes: http://whoopis.com/howtos/mailman-readonly-list.php See the FAQs at http://wiki.list.org/x/3YA9 and http://wiki.list.org/x/OIDD. Seems to work fine, unfortunatily mailman is rewriting the Message-Id of the injected emails. What Mailman version is this? This should not happen unless General Options - anonymous_list is Yes or the new in 2.1.16 General Options - from_is_list setting is Wrap Message. Debian wheezy, which is version 2.1.15. Yes, anonymous_list is Yes as suggested in the forementioned web site. I'll set it to no and see what happens, and in the meantime read up at your links. -- Roel Wagenaar, Linux-User #469851 with the Linux Counter; http://linuxcounter.net/ Antw.: Omdat het de volgorde verstoord waarin mensen tekst lezen. Vraag: Waarom is top-posting een slechte gewoonte? Antw.: Top-posting. Vraag: Wat is het meest ergerlijke in e-mail? A fire at one end, a fool at the other, and a bit of tobacco in between. -- 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 is rewriting Message-Id
Stephen J. Turnbull step...@xemacs.org wrote:
Roel Wagenaar writes:
Seems to work fine, unfortunatily mailman is rewriting the Message-Id
of the
injected emails.
Seems very unlikely to me. The code you propose changing should prevent
that already. How did you determine that Mailman is rewriting the
Message-Id?
I suspect that what is actually happening is that you have an MUA that
does not set Message-ID and you are CC'ing yourself to check. Somehow the
message gets to Mailman without a Message-ID, so Mailman (or something
before Mailman in the process) adds one to the post it distributes, and
something (probably your MTA on the way back in to your mailbox) adds one
independently to the CC that you receive.
There are several other possible explanations (besides Mailman altering an
existing Message-ID, which can't be completely ruled out but I'd bet a
euro against a yen that something else is doing it), as well, but you
haven't given enough information to diagnose the issue.
Is it save to alter /usr/lib/mailman/Mailman/Message.py so that the
section:
if not self.has_key('message-id'):
self['Message-ID'] = Utils.unique_message_id(mlist)
is changed into:
if not self.has_key('message-id'):
self['List-Message-ID'] = Utils.unique_message_id(mlist)
No, it's not safe. Messages really should have a message ID according to
the RFCs, and if Mailman receives a message without one, it should add
one. Lack of a Message ID will mess up threading in archives and MUAs, as
most likely each downstream recipient will get a different Message ID,
just as you do.
--
Roel Wagenaar,
Linux-User #469851 with the Linux Counter; http://linuxcounter.net/
Antw.: Omdat het de volgorde verstoord waarin mensen tekst lezen.
Vraag: Waarom is top-posting een slechte gewoonte?
Antw.: Top-posting.
Vraag: Wat is het meest ergerlijke in e-mail?
Always remember you're unique, just like everyone else.
--
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 is rewriting Message-Id
You wrote:
Roel Wagenaar writes:
Seems to work fine, unfortunatily mailman is rewriting the Message-Id
of the
injected emails.
Seems very unlikely to me. The code you propose changing should prevent
that already. How did you determine that Mailman is rewriting the
Message-Id?
The mails are coming from my main mailhost, collected via rss2email and
processed by procmail.
A copy of the local delivered mail is sent to the maillists server, after
delivering it loses its threading thanks to the newly inserted message-id.
I suspect that what is actually happening is that you have an MUA that
does not set Message-ID and you are CC'ing yourself to check. Somehow the
message gets to Mailman without a Message-ID, so Mailman (or something
before Mailman in the process) adds one to the post it distributes, and
something (probably your MTA on the way back in to your mailbox) adds one
independently to the CC that you receive.
There are several other possible explanations (besides Mailman altering an
existing Message-ID, which can't be completely ruled out but I'd bet a
euro against a yen that something else is doing it), as well, but you
haven't given enough information to diagnose the issue.
Is it save to alter /usr/lib/mailman/Mailman/Message.py so that the
section:
if not self.has_key('message-id'):
self['Message-ID'] = Utils.unique_message_id(mlist)
is changed into:
if not self.has_key('message-id'):
self['List-Message-ID'] = Utils.unique_message_id(mlist)
No, it's not safe. Messages really should have a message ID according to
the RFCs, and if Mailman receives a message without one, it should add
one. Lack of a Message ID will mess up threading in archives and MUAs, as
most likely each downstream recipient will get a different Message ID,
just as you do.
Right now I am waiting for the next messages to come in and see wether Mark
Sapiro is right with some headers being wrongly set.
Thanks so far.
--
Roel Wagenaar,
Linux-User #469851 with the Linux Counter; http://linuxcounter.net/
Antw.: Omdat het de volgorde verstoord waarin mensen tekst lezen.
Vraag: Waarom is top-posting een slechte gewoonte?
Antw.: Top-posting.
Vraag: Wat is het meest ergerlijke in e-mail?
A fire at one end, a fool at the other, and a bit of tobacco in between.
--
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 is rewriting Message-Id
Mark Sapiro m...@msapiro.net wrote: On 11/13/2013 05:53 AM, Roel Wagenaar wrote: As an experiment I have set up a read-only maillist with the help of these notes: http://whoopis.com/howtos/mailman-readonly-list.php See the FAQs at http://wiki.list.org/x/3YA9 and http://wiki.list.org/x/OIDD. Seems to work fine, unfortunatily mailman is rewriting the Message-Id of the injected emails. What Mailman version is this? This should not happen unless General Options - anonymous_list is Yes or the new in 2.1.16 General Options - from_is_list setting is Wrap Message. Hei Presto, Changing the setting of anonymous_list to no has resulted in the correct Message-Id. Thanks for the fast and correct response. Never to old to learn. -- Roel Wagenaar, Linux-User #469851 with the Linux Counter; http://linuxcounter.net/ Antw.: Omdat het de volgorde verstoord waarin mensen tekst lezen. Vraag: Waarom is top-posting een slechte gewoonte? Antw.: Top-posting. Vraag: Wat is het meest ergerlijke in e-mail? The early bird gets the worm, but the second mouse gets the cheese. -- 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] Content-Transfer-Encoding: not workng as expected.
L.S. Mailman version 2.1.15-1 Debian Wheezy My /etc/procmailrc is decoding Content-Transfer-Encoding: base64 headers as standard rule forall incoming mail. Funny thing happens when filtered mailis beiing resend by Maiman, it encode the base64 part again, is there an option to prevent this? I don't seem to beable to find it. As a test case I havemade a copy recipy tgat make procmail send a copy of all mail to Mailman to the same server where the list-messages go to, these copies are not encoded. Funny. -- Roel Wagenaar, Linux-User #469851 with the Linux Counter; http://linuxcounter.net/ Antw.: Omdat het de volgorde verstoord waarin mensen tekst lezen. Vraag: Waarom is top-posting een slechte gewoonte? Antw.: Top-posting. Vraag: Wat is het meest ergerlijke in e-mail? Climate is what you expect. Weather is what you get. -- 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
