[Imap-uw] mailutil complains about NUL

Ross Boylan ross at betterworld.us
Wed Sep 20 11:39:50 PDT 2006


On Sat, Sep 09, 2006 at 07:29:04PM -0700, Mark Crispin wrote:
> On Sat, 9 Sep 2006, Ross Boylan wrote:
> >>What was the *exact* text of the error message?
> >Message contains NUL characters
> 
> That message came from the Cyrus server.
> 
> The latest imap-2006 development snapshot now transforms all NULs in 
> message text being uploaded to an IMAP server into 0x80 characters.  This 
> will eliminate this issue in mailutil.

I tracked down the NUL and changed it to a space manually, and the
whole box then transferred.

.. 
> >A small oddity is that I get (identifying info obscured)
> >The authenticity of host 'foo.server.com (127.0.0.1)' can't be established.
> >RSA key fingerprint is [xxx]
> >Are you sure you want to continue connecting (yes/no)?
> >{foo.server.com/imap} username: joe
> 
> Aha.  Mailutil is trying to do an rsh-IMAP session, it's going through ssh 
> (probably because someone lunk ssh to the name rsh thinking that would be 
> a good thing), and it isn't succeeding.  That must be a big factor in the 
> delays.
> 
> Try adding /norsh as well, e.g., {machine/user=joe/rsh}
> 
> Let me know if that cures the problem.
> 

/norsh cured the ssh prompt.  I still need to give the mailbox
password (just once per connection).  The whole operation still seems
rather slow, c 20 minutes for 100Mg mailbox.  These are all going to
the same box on the server.  Again, nobody is using much CPU.  I
suspect I may need to tune my Cyrus server.

I take it from your earlier response that even if I set up ssh so I
had passwordless login I would still need to answer a password prompt
for the mailbox.  So I need to work on my expect script.

Thanks for your help.

Ross

P.S. For those  who find this in the archive.  I used the /debug
option to narrow down which message was causing the trouble.  However,
the output is a little misleading because of the asynchronous
operations.  The debugging shows the messages as they go in; the error
about the NUL actually referred to a somewhat earlier message (I
think).


More information about the Imap-uw mailing list