Re: [Mailman-Developers] Re: [Mailman-Users] complete personalisation

Mark, I reviewed the patch and think it reasonable to be included in 2.1.6. I will find time to test on my site and check in within a week. Thanks a lot, Mark Sapiro wrote: Stefan Hofmeir wrote: each subscriber of a newsletter list should see his email address in the "to" field, so I have set "pers

Re: [Mailman-Users] from field with real name

Stefan Hofmeir wrote: > >the sender (from field) of a newsletter list should be the address of >the list (anonymous_list = yes). > >previous from field (of the test list "mailman"): >From: [EMAIL PROTECTED] > >How it is possible to sent also a real name like >From: "list ABC <[EMAIL PROTECTED]>" in

Re: [Mailman-Users] complete personalisation

Stefan Hofmeir wrote: > >each subscriber of a newsletter list should see his email address in >the "to" field, so I have set "personalize: complete >personalisation". > >But why is every newsletter sent in "cc" to the list address? >To: Subscriber123 <[EMAIL PROTECTED]> >CC: mailmanlist <[EMAIL PR

Re: [Mailman-Users] Digests sent out with wrong timestamp

At 10:45 PM +0100 2005-02-06, Torsten Ehlers wrote: my MTA is qmail. The date of my machine is set correctly (I'm already using ntp, by the way). Ahh. This is a known issue with qmail. Other mails sent from this machine have the correct date. Most likely because t

Re: [Mailman-Users] complete personalisation

At 10:42 PM +0100 2005-02-06, Stefan Hofmeir wrote: But why is every newsletter sent in "cc" to the list address? To: Subscriber123 <[EMAIL PROTECTED]> CC: mailmanlist <[EMAIL PROTECTED]> How can I delete the "cc" field? See

Re: [Mailman-Users] Digests sent out with wrong timestamp

Hi, my MTA is qmail. The date of my machine is set correctly (I'm already using ntp, by the way). Other mails sent from this machine have the correct date. But I could fix the problem by using Mark's tip. It was a Mailman bug. Thanks! Torsten Jeff Groves schrieb am 06.02.2005 22:37: Brad: It see

[Mailman-Users] from field with real name

Hello, the sender (from field) of a newsletter list should be the address of the list (anonymous_list = yes). previous from field (of the test list "mailman"): From: [EMAIL PROTECTED] How it is possible to sent also a real name like From: "list ABC <[EMAIL PROTECTED]>" in every newsletter? --

[Mailman-Users] complete personalisation

Hello, each subscriber of a newsletter list should see his email address in the "to" field, so I have set "personalize: complete personalisation". But why is every newsletter sent in "cc" to the list address? To: Subscriber123 <[EMAIL PROTECTED]> CC: mailmanlist <[EMAIL PROTECTED]> How can I de

Re: [Mailman-Users] Is anyone using the SpamAssassin.py and spamd.pyhandlers?

John Fleming said the following on 2/6/2005 4:10 PM: Glenn, I have it working, and I'm a major newbie. Here's my mm_cfg.py snippet: Weird. All I did was change SPAMASSASSIN_HOST to 'localhost', restarted qrunner and *puf* it started working. That's vrry odd. But.. thanks :) Best, --Glenn (Thank

Re: [Mailman-Users] Digests sent out with wrong timestamp

Brad: It seems to be worse than not having the date set. The MTA itself is behaving very badly by setting the sent date to 0 seconds since the January 1, 1970 (standard zero time in UNIX). The chances that ALL messages are dated January 1, 1970 because of a time synchronization problem are pret

Re: [Mailman-Users] Digests sent out with wrong timestamp

Torsten: Which MTA are you using? It handles the situation of no "Date:" header is being added by a mail client VERY badly. Jeff G. Torsten Ehlers wrote: Hi, I'm using Mailman 2.1.5 on a Debian Woody installation. When I tell Mailman to receive my mails from a list in a daily digest I receive t

Re: [Mailman-Users] Is anyone using the SpamAssassin.py and spamd.pyhandlers?

Installed the patches, put the right things in mm_cfg.py: GLOBAL_PIPELINE.insert(1, 'SpamAssassin') SPAMASSASSIN_HOST = 'wingfoot.org' SPAMASSASSIN_DISCARD_SCORE = 7.5 SPAMASSASSIN_HOLD_SCORE = 5.0 SPAMASSASSIN_MEMBER_BONUS = 3 And, restarted mailman. In my logs, when I post something to a test lis

[Mailman-Users] Is anyone using the SpamAssassin.py and spamd.py handlers?

I'm running 2.1.5 on FreeBSD, with SpamAssassin 3.0.1_2. I followed the instructions from the FAQWizard, http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.023.htp I went to #2: Using patches by Jon Parise located at http://sourceforge.net/tracker/index.php?func=detail&aid=640518&group

Re: [Mailman-Users] Digests sent out with wrong timestamp

At 11:35 AM +0100 2005-02-06, Torsten Ehlers wrote: When I tell Mailman to receive my mails from a list in a daily digest I receive this digest but the header of the digest mail does not contain a Date line, i.e. the Mails are shown in my mail client with the date January 1st 1970. How can this

Re: [Mailman-Users] Digests sent out with wrong timestamp

Torsten Ehlers wrote: > >When I tell Mailman to receive my mails from a list in a daily digest I >receive this digest but the header of the digest mail does not contain a >Date line, i.e. the Mails are shown in my mail client with the date >January 1st 1970. How can this be fixed? This will be

Re: [Mailman-Users] preventing non-member posting in MM 2.1.5

david gordon wrote: I'm just updating a couple of lists from MM 2.0.13 to 2.1.5 It seems that the later version doesn't allow me to prevent non-member posting - surely that can't be correct, I must have missed something, somewhere? I'm looking for the "Restrict posting privilege to list members? (m

[Mailman-Users] Digests sent out with wrong timestamp

Hi, I'm using Mailman 2.1.5 on a Debian Woody installation. When I tell Mailman to receive my mails from a list in a daily digest I receive this digest but the header of the digest mail does not contain a Date line, i.e. the Mails are shown in my mail client with the date January 1st 1970. How c

[Mailman-Users] preventing non-member posting in MM 2.1.5

I'm just updating a couple of lists from MM 2.0.13 to 2.1.5 It seems that the later version doesn't allow me to prevent non-member posting - surely that can't be correct, I must have missed something, somewhere? I'm looking for the "Restrict posting privilege to list members? (member_posting_only