Re: [Mailman-Users] The "right" way to reply to a mailing list / Re:

2015-03-23 Thread Roel Wagenaar
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 >

Re: [Mailman-Users] We're sorry, we hit a bug!

2014-07-01 Thread Roel Wagenaar
rator 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.: Om

[Mailman-Users] We're sorry, we hit a bug!

2014-07-01 Thread Roel Wagenaar
ected, 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 gew

Re: [Mailman-Users] unable to start Mailman

2013-11-20 Thread Roel Wagenaar
Tanstaafl 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?

Re: [Mailman-Users] Content-Transfer-Encoding: not workng as expected.

2013-11-15 Thread Roel Wagenaar
ate.py", line 23, in 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://linuxcoun

[Mailman-Users] Content-Transfer-Encoding: not workng as expected.

2013-11-13 Thread Roel Wagenaar
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;

Re: [Mailman-Users] Mailman is rewriting Message-Id

2013-11-13 Thread Roel Wagenaar
Mark Sapiro 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

Re: [Mailman-Users] Mailman is rewriting Message-Id

2013-11-13 Thread Roel Wagenaar
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 th

Re: [Mailman-Users] Mailman is rewriting Message-Id

2013-11-13 Thread Roel Wagenaar
"Stephen J. Turnbull" 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.

Re: [Mailman-Users] Mailman is rewriting Message-Id

2013-11-13 Thread Roel Wagenaar
Mark Sapiro 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

[Mailman-Users] Mailman is rewriting Message-Id

2013-11-13 Thread Roel Wagenaar
d 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 Li