| 2008-12-15 16:53:49 |
Mark Sapiro |
mailman: statusexplanation |
|
This is only related to (non) Bug 265976 in that the exception is the same.
It is not clear to me if this is a bug or not. The code in HyperArch.py is suspicious. The existing code fragment is
if mm_cfg.ARCHIVER_OBSCURES_EMAILADDRS:
otrans = i18n.get_translation()
try:
atmark = unicode(_(' at '), cset)
i18n.set_language(self._lang)
body = re.sub(r'([-+,.\w]+)@([-+.\w]+)',
'\g<1>' + atmark + '\g<2>', body)
finally:
i18n.set_translation(otrans)
And it seems it possibly should be
if mm_cfg.ARCHIVER_OBSCURES_EMAILADDRS:
otrans = i18n.get_translation()
try:
i18n.set_language(self._lang)
atmark = unicode(_(' at '), cset)
body = re.sub(r'([-+,.\w]+)@([-+.\w]+)',
'\g<1>' + atmark + '\g<2>', body)
finally:
i18n.set_translation(otrans)
but I'm not sure. I may be misunderstanding it.
However, I am unable to duplicate this exception or any other with the message fragment posted with either English or Japanese as the list language, so I don't know if the above change would have any effect.
It is clear the message is defective in that it claims the body is us-ascii and it isn't, but I don't *think* that should cause this particular error.
Can you email me a complete message that causes this exception and also tell me the preferred_language of this list and the mm_cfg.py setting of DEFAULT_SERVER_LANGUAGE if it is set to other than 'en'.
|
|
| 2008-12-19 21:11:17 |
Mark Sapiro |
mailman: statusexplanation |
This is only related to (non) Bug 265976 in that the exception is the same.
It is not clear to me if this is a bug or not. The code in HyperArch.py is suspicious. The existing code fragment is
if mm_cfg.ARCHIVER_OBSCURES_EMAILADDRS:
otrans = i18n.get_translation()
try:
atmark = unicode(_(' at '), cset)
i18n.set_language(self._lang)
body = re.sub(r'([-+,.\w]+)@([-+.\w]+)',
'\g<1>' + atmark + '\g<2>', body)
finally:
i18n.set_translation(otrans)
And it seems it possibly should be
if mm_cfg.ARCHIVER_OBSCURES_EMAILADDRS:
otrans = i18n.get_translation()
try:
i18n.set_language(self._lang)
atmark = unicode(_(' at '), cset)
body = re.sub(r'([-+,.\w]+)@([-+.\w]+)',
'\g<1>' + atmark + '\g<2>', body)
finally:
i18n.set_translation(otrans)
but I'm not sure. I may be misunderstanding it.
However, I am unable to duplicate this exception or any other with the message fragment posted with either English or Japanese as the list language, so I don't know if the above change would have any effect.
It is clear the message is defective in that it claims the body is us-ascii and it isn't, but I don't *think* that should cause this particular error.
Can you email me a complete message that causes this exception and also tell me the preferred_language of this list and the mm_cfg.py setting of DEFAULT_SERVER_LANGUAGE if it is set to other than 'en'.
|
The problem turned out to be due to posts to an English language list from a member whose preferred language for the list was Japanese. The fix is as in the previously attached patch. |
|
