Petar Bogdanovic <petar-+Dgt6vZh/JqsTnJN9+BGXg@...> writes: >> in my logfiles. After analyzing the related network traffic, all >> these messages have in common that they contain an ASCII \0 in their >> bodies. This character is allowed by RFC 822 (but not in 2822 + >> 5322). > > While it's a bit unclean that the spamd part of milter-greylist can't > handle a null character, it's also not likely that I'll ever think a > null character belongs to an SMTP conversation. I have seen the error on automated generated messages only (e.g. newsletters) where the sender has probably an off-by-one error. But as I said, legacy SMTP allows it and would not explicitly block it hence. Enrico
Message
Re: spamd checks hang when message contains
2010-06-21 by Enrico Scholz