Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

What does ridiculously long message header in an error report mean?

0
Posted

What does ridiculously long message header in an error report mean?

0

• Q0053: Exim on my host responds to a connection with 220 *****… and won’t understand EHLO commands. • Q0054: I’m getting an Exim configuration error unknown rewrite flag character (m) in line 386 but I haven’t used any flags on my rewriting rules.

0

A5040: There has to be some limit to the length of a message’s header lines, because otherwise a malefactor could open an SMTP channel to your host, start a message, and then just send characters continuously until your machine ran out of memory. (Exim stores all the header lines in main memory). For this reason a limit is imposed on the total amount of memory that can be used for header lines. The default is 1MB, but this can be changed by setting HEADER_MAXSIZE in Local/Makefile. Exceeding the limit provokes the “ridiculous” error message. Prior to release 3.022 Exim used two separate limits, one on the length of an individual header line and one on the total number of header lines. A header line longer than 8192 used to provoke the error “Header line is ridiculously overlong”. In subsequent releases there is no limit on individual header lines; only the total matters.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123