I'm seeing emails being dropped when mm3 talks to the local smtp server, with log errors like:
2021-06-23 15:42:24 1lvvea-007r8u-VN H=localhost (<FQDN>) [::1] F=<announce-bounces@<FQDN>> rejected after DATA: maximum allowed line length is 998 octets, got 1036
The email itself did not have such long lines AFAICT.
I can disable line length checking on the mailserver, but that sounds like a recipe for the next one along to drop the email.
Peter C
On 6/22/21 11:46 PM, peter@chubb.wattle.id.au wrote:
I'm seeing emails being dropped when mm3 talks to the local smtp server, with log errors like:
2021-06-23 15:42:24 1lvvea-007r8u-VN H=localhost (<FQDN>) [::1] F=<announce-bounces@<FQDN>> rejected after DATA: maximum allowed line length is 998 octets, got 1036
The email itself did not have such long lines AFAICT.
We would need to see the email itself in order to begin to understand if this is a Mailman issue or some issue withe the mail as received by Mailman.
Assuming the prototype archiver is enabled, you should be able to find the messages in Mailman's var/archives/prototype/LIST/new/ directory.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
- Mark Sapiro (mark@msapiro.net) [210623 15:34]:
We would need to see the email itself in order to begin to understand if this is a Mailman issue or some issue withe the mail as received by Mailman.
Assuming the prototype archiver is enabled, you should be able to find the messages in Mailman's var/archives/prototype/LIST/new/ directory.
One question, in order to ease debugging, can I forcefully activate the prototype archiver from the global configuration, or do I need to do that on a per-list basis?
Andi
On 6/23/21 7:10 AM, Andreas Barth wrote:
- Mark Sapiro (mark@msapiro.net) [210623 15:34]:
We would need to see the email itself in order to begin to understand if this is a Mailman issue or some issue withe the mail as received by Mailman.
Assuming the prototype archiver is enabled, you should be able to find the messages in Mailman's var/archives/prototype/LIST/new/ directory.
One question, in order to ease debugging, can I forcefully activate the prototype archiver from the global configuration, or do I need to do that on a per-list basis?
You need
[archiver.prototype] enable: yes
in mailman.cfg. I'm not sure if that's enough for existing lists. You may need to activate the archiver per list.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
- Mark Sapiro (mark@msapiro.net) [210623 16:21]:
On 6/23/21 7:10 AM, Andreas Barth wrote:
One question, in order to ease debugging, can I forcefully activate the prototype archiver from the global configuration, or do I need to do that on a per-list basis?
You need
[archiver.prototype] enable: yes
in mailman.cfg. I'm not sure if that's enough for existing lists. You may need to activate the archiver per list.
Thanks Mark, that's what I did. After the restart I needed to activate it on a per-list basis.
However, I'd prefer to be able to do that on global basis. Not a big issue, but still thought it worth asking.
Andi
On 6/23/21 7:45 AM, Andreas Barth wrote:
Thanks Mark, that's what I did. After the restart I needed to activate it on a per-list basis.
However, I'd prefer to be able to do that on global basis. Not a big issue, but still thought it worth asking.
You can do it with a mailman shell script. Something like
>>> for mlist in getUtility(IListManager).mailing_lists:
... for archiver in IListArchiverSet(mlist).archivers:
... if archiver.name == 'prototype':
... archiver.is_enabled = True
...
>>> commit()
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
did you ever find a solution to the issue "maximum allowed line length is 998 octets, got ... "? In the last days, I had some apple iphone originating emails in longish email threads where this happened. Can the prototype archiver be activated additionally to hyperkitty or only as alternative? In the latter case: (how) can I archive the messages in question manually afterwards?
On 2/9/24 13:50, Jörg Schulz wrote:
did you ever find a solution to the issue "maximum allowed line length is 998 octets, got ... "? In the last days, I had some apple iphone originating emails in longish email threads where this happened.
I'm not aware of a solution other that fixing the email clients involved.
Can the prototype archiver be activated additionally to hyperkitty or only as alternative? In the latter case: (how) can I archive the messages in question manually afterwards?
It can be active additionally to hyperkitty. There's nothing that prohibits all enabled archivers from being active on a list.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Maybe the solution would be to change the calls to email.sendmail like:
results = self._connection.sendmail(envsender, recipients, msg.as_string(maxheaderlen=XXX) )
?
This error comes from some ios mail users after a number of answer/reply sessions; the References: in the header grow.
Is this of any help?
Am 09.02.24 um 23:07 schrieb Mark Sapiro:
On 2/9/24 13:50, Jörg Schulz wrote:
did you ever find a solution to the issue "maximum allowed line length is 998 octets, got ... "? In the last days, I had some apple iphone originating emails in longish email threads where this happened.
I'm not aware of a solution other that fixing the email clients involved.
Can the prototype archiver be activated additionally to hyperkitty or only as alternative? In the latter case: (how) can I archive the messages in question manually afterwards?
It can be active additionally to hyperkitty. There's nothing that prohibits all enabled archivers from being active on a list.
participants (4)
-
Andreas Barth -
Jörg Schulz -
Mark Sapiro -
peter＠chubb.wattle.id.au