Message contains NUL characters ...

Derrick J Brashear shadow at
Mon Apr 25 09:25:15 EDT 2005

On Mon, 25 Apr 2005, Michael Sims wrote:

> Marc G. Fournier wrote:
>> Apr 24 15:29:02 hub postfix/lmtp[54800]: 0367A1298D0:
>> to=<admin at>, relay=/var/run/socket/lmtp[/var/run/socket/lmtp],
>> delay=273190, status=bounced (host
>> /var/run/socket/lmtp[/var/run/socket/lmtp] said: 554 5.6.0 Message
>> contains NUL characters (in reply to end of DATA command))
> Hi,
> This is a FAQ (although it appears not to be in the actual FAQ or the
> wiki...). Basically you want to configure your MTA so that NULs are stripped
> before the messages containing them are passed to LMTP.  Check the archives
> (watch for wrapping on this URL):
> +postfix&q=b
> As for why this suddenly became a problem when it wasn't before, I have no
> idea; maybe someone else can shed some light on that...

Well, there's also the possibility as we discussed in October that your 
mta is passing (too) long (to be compliant) lines to cyrus, and the logic 
doesn't distinguish and prints the same error.

The most recent patch we got messes with the prot_stdio code which is 
really not the most desirable way to deal. We'll come up with another 

Cyrus Home Page:
Cyrus Wiki/FAQ:
List Archives/Info:

More information about the Info-cyrus mailing list