[Mailman-Developers] [ mailman-Bugs-540978 ] eMailadress too long ?
noreply@sourceforge.net
noreply@sourceforge.net
Thu, 02 May 2002 07:27:43 -0700
Bugs item #540978, was opened at 2002-04-08 14:56
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=100103&aid=540978&group_id=103
Category: mail delivery
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Markus Mandalka (mandalka)
Assigned to: Nobody/Anonymous (nobody)
Summary: eMailadress too long ?
Initial Comment:
I have a list
antiatomforum@lists.kommunikationssystem.de and others
with long names.
It seems that mailman can not handle with such long
names, because in the subscribe-mail (which you have
to answer to be in the list) the first columns are
some things from the header (unsubscribe:
xxx@lists.xxx and so on).
Whith names like atest@lists.kommunikationssystem.de
it works.
----------------------------------------------------------------------
Comment By: Giovanni Lopedote (giuans)
Date: 2002-05-02 16:27
Message:
Logged In: YES
user_id=531451
I've found it. A fast fix for is to comment lines 149-150
in Mailman/Handlers:/CookHeaders.py:
--- CookHeaders.py 2002-05-02 14:51:36.000000000 +0200
+++ CookHeaders.py.new 2002-05-02 16:12:09.000000000 +0200
@@ -146,8 +146,8 @@
# Wrap these lines if they are too long. 78
character width probably
# shouldn't be hardcoded, but is at least
text-MUA friendly. The
# adding of 2 is for the colon-space separator.
- if len(h) + 2 + len(v) > 78:
- v = CONTINUATION.join(v.split(', '))
+# if len(h) + 2 + len(v) > 78:
+# v = CONTINUATION.join(v.split(', '))
msg[h] = v
# Always delete List-Archive header, but only add it
back if the list is
# actually archiving
Tested with Mailman 2.1b1, Source Mage GNU/Linux 2.4.18,
Postfix 1.1.7.
I know there should be a better way, but I'm not a Python
programmer at all. :)
----------------------------------------------------------------------
Comment By: Barry Warsaw (bwarsaw)
Date: 2002-04-12 00:03
Message:
Logged In: YES
user_id=12800
I've confirmed this bug, but don't have a fix for it right now.
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=100103&aid=540978&group_id=103