[ mailman-Patches-1025372 ] empty Cc:

SourceForge.net noreply at sourceforge.net
Thu Sep 16 03:30:12 CEST 2004


Patches item #1025372, was opened at 2004-09-09 20:02
Message generated for change (Comment added) made by tkikuchi
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1025372&group_id=103

>Category: None
>Group: None
Status: Open
Resolution: None
>Priority: 7
Submitted By: Rob Ellis (robellis)
Assigned to: Nobody/Anonymous (nobody)
Summary: empty Cc:

Initial Comment:
In lists migrated from 2.0.13, new messages without a
Cc: header
end up with an empty one when delivered by mailman (2.1.5).
Freshly created lists don't seem to have the problem ?

This is on a freebsd 4 stable machine running postfix
2.0.19,1
with mailman set up to use SMTPDirect. Python 2.3.3.

The attached patch to AvoidDuplicates.py/CookHeaders.py
seems to fix it...

- rob

----------------------------------------------------------------------

>Comment By: Tokio Kikuchi (tkikuchi)
Date: 2004-09-16 01:30

Message:
Logged In: YES 
user_id=67709

Okey, I take this one for testing at my site and merge into
CVS if no problem.
Looks like the latter part (CookHeaders.py) is unnecessary
because at least one cc is registered.



----------------------------------------------------------------------

Comment By: Morgan Fletcher (potstickr)
Date: 2004-09-15 23:53

Message:
Logged In: YES 
user_id=459672

Er, spoke too soon. Did a 'mailmanctl restart' and then sent
a test message, and did not see an empty cc header. Thanks!

----------------------------------------------------------------------

Comment By: Morgan Fletcher (potstickr)
Date: 2004-09-15 23:45

Message:
Logged In: YES 
user_id=459672

I tried this patch on a netbsd machine recently upgraded
from 2.0.8 to 2.1.5. After applying the patch and a 'make
install' I still see the empty Cc header. This bug is
causing some trouble for some our list members, so I was
really hoping this fix would work. Let me know if you need
debugging info or testing of possible patches.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1025372&group_id=103


More information about the Mailman-coders mailing list