Postfix->Cyrus-imap connection problem

[Paul Schmehl]

--On September 10, 2005 12:41:41 PM -0400 Chuck Swiger <cswiger at mac.com> 
wrote:
>
> [ ... ]
>> If anyone has a clue where to go from here, I'm all ears.  On a related
>> note, is there a utility that would allow me to view the conversation
>> between the lmtp sockets on postfix and imap?  If I could see what's
>> going on, maybe I could figure out why it's failing.
>
> Any chance you're getting locking problems with mail delivery, perhaps
> when an IMAP reader looses it's connection and the daemon is sitting
> there waiting for a timewhen when a LMTP delivery attempt is made?
>
I did some RFC reading about LMTP.  Then I reconfigured cyrus so LMTP would 
have a TCP socket on 127.0.0.1.  I was able to telnet to the port and carry 
on a complete SMTP conversation (LHLO, MAIL FROM:, RCPT TO:, DATA and 
QUIT), but after I typed "." on a single line (which ends the DATA 
transaction), I got an error about an invalid header.  This is not 
dissimilar to the error I'm getting from "real" mail (conversation with 
/var/imap/socket/lmtp timed out while sending end of data), which leads me 
to conclude that cyrus-imap is screwed up (at least on my system), so I'm 
googling the conversion from cyrus-imap to courier-imap right now.  (If 
anyone knows where I can get a tool that converts cyrus-imap mail and 
mailboxes to courier-imap Maildir style mailboxes and mail, please post the 
url.)

> If you want to debug LMTP further, start with this section of "man lmtp":
>
> TROUBLE SHOOTING CONTROLS
>         debug_peer_level (2)
>                The  increment  in verbose logging level when a remote
> client or
>                server matches a pattern in the debug_peer_list parameter.
>
>         debug_peer_list (empty)
>                Optional list of remote client or  server  hostname  or
> network
>                address  patterns  that  cause  the  verbose  logging
> level  to
>                increase by the amount specified in $debug_peer_level.
>
>         error_notice_recipient (postmaster)
>                The recipient of postmaster notifications  about  mail
> delivery
>                problems that are caused by policy, resource, software or
> proto-
>                col errors.
>
I already had all that, but thanks for taking the time to look it up and 
mention it anyway.

Paul Schmehl (pauls at utdallas.edu)
Adjunct Information Security Officer
University of Texas at Dallas
AVIEN Founding Member
http://www.utdallas.edu/