[Mailman-Users] Delivery errors and spam grading

Barry S. Finkel bsfinkel at att.net
Mon Mar 18 22:10:34 EDT 2019

On 3/18/2019 8:44 PM, Jim Dory wrote:
> On Mon, Mar 18, 2019 at 4:39 AM Stephen J. Turnbull <
> turnbull.stephen.fw at u.tsukuba.ac.jp> wrote:
>>    (You probably should
>> also disable the Digestable option in [Digest options]
> I'm also receiving several bounces back for errors such as:
>   "SMTP error from remote mail server after end of data:
>      554 Failed: Malformed MIME field: X-Ham-Report:"
> Or:
>   "SMTP error from remote mail server after end of data:
>      554 5.7.1 [P4] Message blocked due to spam content in the message."
> Mostly associated with the digest. Curious about the statement  above from
> Steve: is disabling the digest option something people do regularly to
> prevent issues like this? and if so - if I were to disable it now, what
> happens to those members who are using that option? I assume they just
> start automatically receiving non-digest messages, but figured I should ask.
> thanks, JD

The second "error" message is one over which you have little control.
The recipient's mail system detected content in the digest that it
considered spam.  I assume that if the messages in the digest had been
sent individually in non-digest mode, then the message that had the
objectionable content would have been similarly flagged.

As for the first "error" - A quick Google search showed that the


header line is written by Cpanel when it detects that the message is
not spam.  I do not know if any other software writes this line.
I am not an expert in MIME, but I do not see how any "X-" header
line could be treated as a malformed MIME header.

If you have users who are using digest mode, then removing that option
will cause consternation with those users.  And I doubt that the digest
mode has anything to do with this error message.

--Barry Finkel

More information about the Mailman-Users mailing list