[solved] outgoing mails not RfC conform

[xxx]

Hi.

I already posted this on the mailing list yesterday. But, as already stated in IRC, the mailing list is less crowded since some times, so I decided to cross-post

One of our machines has a problem with outgoing mails getting blocked by our mail gateway. The local MTA logs the error as follows (I mystified host and mail addresses):

Code: Select all

2015-10-26 11:11:22 1ZpBkJ-0002B9-FL SMTP timeout while connected to our.mailgateway.local [10.255.252.92] after sending data block (16378 bytes written): Connection timed out
2015-10-26 11:11:22 1ZpBkJ-0002B9-FL == rcvr@domain.cxm <rcvr@domain.cxm> R=smarthost T=remote_smtp_smarthost defer (110): Connection timed out: SMTP timeout while connected to our.mailgateway.local [10.255.252.92] after sending data block (16378 bytes written)

Logging on the gateway shows more detail:

Code: Select all

Sep 18 10:32:07 nefw1 %ASA-4-108004: ESMTP Classification: Dropped connection for ESMTP Request from ProvDMZ:10.255.250.13/56134 to coresw_3_4:10.255.252.92/25; matched Class 4: header line length gt 998

A quick view on the message headers showed that indeed all of them have a „References“ line with more than 1100 characters, which is, according to RFC 822 way too much:

There are two limits that this specification places on the number of characters in a line. Each line of characters MUST be no more than 998 characters, and SHOULD be no more than 78 characters, excluding the CRLF.

So my question is:
Is this a bug that only affects version 3.1.3 (and smaller)?
If not: How does OTRS create these lines? Is it a default Perl module that handles the mail header lines?

[jojo]

wenn ich es richtig in Erinnerung habe dann wurde das geändert.

Aktuell ist die OTRS5, die 3.1 ist seit Jahren nicht mehr supported und gepflegt.

[xxx]

Danke jojo.
Dann werde ich mal die entsprechenden Module vergleichen. Leider haben die Vor-Verwalter so viel am System rumgewurstelt, dass der Aufwand, das upzugraden, bei Wochen liegen dürfte.
Mal sehen, ob ich die Verantwortlichen irgendwann überreden kann, mit einem "frischen" 5.0 anzufangen ...

Ich markiere den Thread schon mal als "solved" und werde bei Gelegenheit nachtragen, ob ich die entsprechende Änderung finde.