Hello Georges,
> thank you for your response.
I was busy otherwise recently. I suppose, this is still open, isn't it?
> cron is a key command for UNIX systems, and it is supposed to remain
> lightweight and efficient. This is why it does not implement the mailing
> features, and relies on other
Hello Frank,
thank you for your response.
cron is a key command for UNIX systems, and it is supposed to remain
lightweight and efficient. This is why it does not implement the mailing
features, and relies on other UNIX commands to do this job (`mail` or
`sendmail`)
You can browse the file
Hello,
> I am the new maintainer for cron package, since a few months. Please can
> one elaborate a little longer about use cases where too long lines are a
> problem?
Thanks for picking up this issue again. I'm not the original
reporter, but also effected, as I wrote in my comment last year.
Hello,
I am the new maintainer for cron package, since a few months. Please can
one elaborate a little longer about use cases where too long lines are a
problem?
Would it be sufficient to truncate such lines to 998 characters, hoping
that such a length would be sufficient to diagnose a problem?
The limit according to RFC 2822 is 998 characters.
Current versions of exim4, e.g., enforce this limit.
So if you do wrapping, you might as well use the correct limit.
Of course, wrapping slightly alters the content.
If this is deemed inacceptable, you might need to MIME encode the
message (QP
PS: Sorry, the MTA wasn't exim4, but opensmtpd. There is
a hardwired
#define SMTPD_MAXLINESIZE 2048
in the code.
Nevertheless, cron should wrap long lines to make sure the
cronjob messages are not lost.
Regards
Harri
--
To UNSUBSCRIBE, email to
Package: cron
Version: 3.0pl1-124
To avoid loosing cronjob mails with a line too long error
(exim4, for example) cron should wrap very long lines, e.g.
after 1024 chars.
Regards
Harri
--
aixigo AG, Karl-Friedrich-Strasse 68, 52072 Aachen, Germany
phone: +49 241 559709-79, fax: +49 241
7 matches
Mail list logo
