Mailing List Archive

Increasing probs with bare linefeed
Hi All,

I know that this was discussed several times but I was not able to find
a suitable solution and gratefully request your advise...

The last few days the number of rejected mails with "Bare line feeds"
raised, especially it looks like the german provider 1&1
(web.de/gmx.net) starts sending broken messages.

As far as I understood, wrapping with fixcrio would help, but can break
TLS, right? I found a patch on the list archives from Dean Gaudet of
1997 that just removes the "straynewline" warnings - will this have any
side effects? Are there better solutions?

regards

Oliver
--
Protect your environment - close windows and adopt a penguin!
PGP-Key: 3B2C 8095 A7DF 8BB5 2CFF 8168 CAB7 B0DD 3985 1721
Re: Increasing probs with bare linefeed [ In reply to ]
Oliver Welter <mail@oliwel.de> wrote:
>
> The last few days the number of rejected mails with "Bare line
> feeds" raised, especially it looks like the german provider 1&1
> (web.de/gmx.net) starts sending broken messages.
>
> As far as I understood, wrapping with fixcrio would help, but can
> break TLS, right?

It corrupts messages, and it should not be necessary to do this today.

> I found a patch on the list archives from Dean Gaudet of 1997 that just
> removes the "straynewline" warnings - will this have any side effects? Are
> there better solutions?

As you note, that patch was an attempt to work around a bug that was common in
incorrectly-set-up sendmail installations 15 years ago. It has no relevance
today.

Just contact the web.de/gmx.net postmaster and point out they're sending
broken messages. They'll get the hint soon enough when their customers start
complaining that none of their mail is getting through.

Charles
--
--------------------------------------------------------------------------
Charles Cazabon
GPL'ed software available at: http://pyropus.ca/software/
Read http://pyropus.ca/personal/writings/12-steps-to-qmail-list-bliss.html
--------------------------------------------------------------------------
Re: Increasing probs with bare linefeed [ In reply to ]
Hi Charles,

nice theory, I send a mail to 1&1 but did not receive any answer yet.
Meanwhilte the customers start to grumble. It looks like its not my
fault but the people are ignorant and it looks like "any other software"
silenty accepts the broken messages.

So, any suggestions?

Oliver

On 03.07.2013 22:55, Charles Cazabon wrote:
> Oliver Welter <mail@oliwel.de> wrote:
>>
>> The last few days the number of rejected mails with "Bare line
>> feeds" raised, especially it looks like the german provider 1&1
>> (web.de/gmx.net) starts sending broken messages.
>>
>> As far as I understood, wrapping with fixcrio would help, but can
>> break TLS, right?
>
> It corrupts messages, and it should not be necessary to do this today.
>
>> I found a patch on the list archives from Dean Gaudet of 1997 that just
>> removes the "straynewline" warnings - will this have any side effects? Are
>> there better solutions?
>
> As you note, that patch was an attempt to work around a bug that was common in
> incorrectly-set-up sendmail installations 15 years ago. It has no relevance
> today.
>
> Just contact the web.de/gmx.net postmaster and point out they're sending
> broken messages. They'll get the hint soon enough when their customers start
> complaining that none of their mail is getting through.
>
> Charles
>

--
Protect your environment - close windows and adopt a penguin!
PGP-Key: 3B2C 8095 A7DF 8BB5 2CFF 8168 CAB7 B0DD 3985 1721
Re: Increasing probs with bare linefeed [ In reply to ]
On Wednesday, July 3 at 08:21 AM, quoth Oliver Welter:
> The last few days the number of rejected mails with "Bare line
> feeds" raised, especially it looks like the german provider 1&1
> (web.de/gmx.net) starts sending broken messages.
>
> As far as I understood, wrapping with fixcrio would help, but can
> break TLS, right? I found a patch on the list archives from Dean
> Gaudet of 1997 that just removes the "straynewline" warnings - will
> this have any side effects? Are there better solutions?

There are a couple potential solutions you can try. The easiest would
be to use the tcpserver's tcp.smtp file (I'm assuming you have a
reasonably standard qmail install) to create a special handler for all
messages coming from 1&1's email server. You can disable TLS via
environment variables (unless they're relaying messages through you,
they shouldn't need it; the details of disabling TLS depend on how
you're getting TLS support), and then wrap qmail-smtpd with fixcrio.

(I admit, getting that done requires a little more work than "toggle
flag foo and it all works out". For instance, you may require a little
indirection, like a wrapper script that changes which qmail-smtpd
binary gets invoked based on the environment variables you've
specified. But such things should be relatively trivial to write.)

~Kyle
--
May your glass be ever full. May the roof over your head be always
strong. May you be in heaven half an hour before the devil knows
you're dead.
-- Old Irish Toast
Re: Increasing probs with bare linefeed [ In reply to ]
Am 08.07.2013 18:16, schrieb Kyle Wheeler:
> On Wednesday, July 3 at 08:21 AM, quoth Oliver Welter:
>> The last few days the number of rejected mails with "Bare line feeds"
>> raised, especially it looks like the german provider 1&1
>> (web.de/gmx.net) starts sending broken messages.
>>
>> As far as I understood, wrapping with fixcrio would help, but can
>> break TLS, right? I found a patch on the list archives from Dean
>> Gaudet of 1997 that just removes the "straynewline" warnings - will
>> this have any side effects? Are there better solutions?
>
> There are a couple potential solutions you can try. The easiest would be
> to use the tcpserver's tcp.smtp file (I'm assuming you have a reasonably
> standard qmail install) to create a special handler for all messages
> coming from 1&1's email server. You can disable TLS via environment
> variables (unless they're relaying messages through you, they shouldn't
> need it; the details of disabling TLS depend on how you're getting TLS
> support), and then wrap qmail-smtpd with fixcrio.

I started this way but as I found several more "broken servers" besides
the 1&1 subnet I decided to give a global fix a try and just ported the
mentioned patch from Dean Gaudet to my netqmail and recompiled the stuff
(thats the moments I really love gentoo). Runs for nearly 36 hours now
without any problems so far.

Oliver

--
Protect your environment - close windows and adopt a penguin!
PGP-Key: 3B2C 8095 A7DF 8BB5 2CFF 8168 CAB7 B0DD 3985 1721
Re: Increasing probs with bare linefeed [ In reply to ]
Hi Oliver,

my Spamcontrol 2.7. includes a LF fix in qmail-smtpd. c.

Either you can install this, or you backport it to your current qmail-smtpd.c.

regards.
--eh.

PS: I'm 1&1 customer by myself.

Am 08.07.2013 um 22:23 schrieb Oliver Welter:

>
> Am 08.07.2013 18:16, schrieb Kyle Wheeler:
>> On Wednesday, July 3 at 08:21 AM, quoth Oliver Welter:
>>> The last few days the number of rejected mails with "Bare line feeds"
>>> raised, especially it looks like the german provider 1&1
>>> (web.de/gmx.net) starts sending broken messages.
>>>
>>> As far as I understood, wrapping with fixcrio would help, but can
>>> break TLS, right? I found a patch on the list archives from Dean
>>> Gaudet of 1997 that just removes the "straynewline" warnings - will
>>> this have any side effects? Are there better solutions?
>>
>> There are a couple potential solutions you can try. The easiest would be
>> to use the tcpserver's tcp.smtp file (I'm assuming you have a reasonably
>> standard qmail install) to create a special handler for all messages
>> coming from 1&1's email server. You can disable TLS via environment
>> variables (unless they're relaying messages through you, they shouldn't
>> need it; the details of disabling TLS depend on how you're getting TLS
>> support), and then wrap qmail-smtpd with fixcrio.
>
> I started this way but as I found several more "broken servers" besides the 1&1 subnet I decided to give a global fix a try and just ported the mentioned patch from Dean Gaudet to my netqmail and recompiled the stuff (thats the moments I really love gentoo). Runs for nearly 36 hours now without any problems so far.
>
> Oliver
>
> --
> Protect your environment - close windows and adopt a penguin!
> PGP-Key: 3B2C 8095 A7DF 8BB5 2CFF 8168 CAB7 B0DD 3985 1721
> <ignore straynewline.patch>

--
Dr. Erwin Hoffmann | FEHCom | http://www.fehcom.de | PGP Key-Id: 7E4034BE
Re: Increasing probs with bare linefeed [ In reply to ]
hi Erwin,

I meanwhile backported the patch from Dean Gaudet, but thanks for the info.

Oliver

Am 28.07.2013 18:17, schrieb Erwin Hoffmann:
> Hi Oliver,
>
> my Spamcontrol 2.7. includes a LF fix in qmail-smtpd. c.
>
> Either you can install this, or you backport it to your current qmail-smtpd.c.
>
> regards.
> --eh.
>
> PS: I'm 1&1 customer by myself.
>
> Am 08.07.2013 um 22:23 schrieb Oliver Welter:
>
>>
>> Am 08.07.2013 18:16, schrieb Kyle Wheeler:
>>> On Wednesday, July 3 at 08:21 AM, quoth Oliver Welter:
>>>> The last few days the number of rejected mails with "Bare line feeds"
>>>> raised, especially it looks like the german provider 1&1
>>>> (web.de/gmx.net) starts sending broken messages.
>>>>
>>>> As far as I understood, wrapping with fixcrio would help, but can
>>>> break TLS, right? I found a patch on the list archives from Dean
>>>> Gaudet of 1997 that just removes the "straynewline" warnings - will
>>>> this have any side effects? Are there better solutions?
>>>
>>> There are a couple potential solutions you can try. The easiest would be
>>> to use the tcpserver's tcp.smtp file (I'm assuming you have a reasonably
>>> standard qmail install) to create a special handler for all messages
>>> coming from 1&1's email server. You can disable TLS via environment
>>> variables (unless they're relaying messages through you, they shouldn't
>>> need it; the details of disabling TLS depend on how you're getting TLS
>>> support), and then wrap qmail-smtpd with fixcrio.
>>
>> I started this way but as I found several more "broken servers" besides the 1&1 subnet I decided to give a global fix a try and just ported the mentioned patch from Dean Gaudet to my netqmail and recompiled the stuff (thats the moments I really love gentoo). Runs for nearly 36 hours now without any problems so far.
>>
>> Oliver
>>
>> --
>> Protect your environment - close windows and adopt a penguin!
>> PGP-Key: 3B2C 8095 A7DF 8BB5 2CFF 8168 CAB7 B0DD 3985 1721
>> <ignore straynewline.patch>
>


--
Protect your environment - close windows and adopt a penguin!
PGP-Key: 3B2C 8095 A7DF 8BB5 2CFF 8168 CAB7 B0DD 3985 1721