Re: System I/O error (in reply to end of DATA command) for LMTP delivery

OTH, my guess is that Cyrus is failing to create the tmpfile to stage 
the message.  Is /tmp (or its equivalent) full, or not writeable?

Without something from the Cyrus syslog, this will be hard to diagnose.


On 06/01/2018 12:51 PM, Stephen Ingram wrote:
> Ken-
>
> That all appears to be working correctly. Here's a cut from the 
> Postfix debug with addresses obfuscated:
>
> Jun  1 16:48:52 mx postfix/lmtp[18136]: send attr offset = 682
> Jun  1 16:48:52 mx postfix/lmtp[18136]: send attr dsn_orig_rcpt = 
> rfc822;[email protected] <mailto:rfc822%[email protected]>
> Jun  1 16:48:52 mx postfix/lmtp[18136]: send attr notify_flags = 0
> Jun  1 16:48:52 mx postfix/lmtp[18136]: send attr status = 4.3.0
> Jun  1 16:48:52 mx postfix/lmtp[18136]: send attr diag_type = smtp
> Jun  1 16:48:52 mx postfix/lmtp[18136]: send attr diag_text = 451 
> 4.3.0 System I/O error
> Jun  1 16:48:52 mx postfix/lmtp[18136]: send attr mta_type = dns
> Jun  1 16:48:52 mx postfix/lmtp[18136]: send attr mta_mname = imap.x.x
> Jun  1 16:48:52 mx postfix/lmtp[18136]: send attr action = delayed
> Jun  1 16:48:52 mx postfix/lmtp[18136]: send attr reason = host 
> imap.x.x[10.0.13.83] said: 451 4.3.0 System I/O error (in reply to end 
> of DATA command)
> Jun  1 16:48:52 mx postfix/lmtp[18136]: private/defer socket: wanted 
> attribute: status
> Jun  1 16:48:52 mx postfix/lmtp[18136]: input attribute name: status
> Jun  1 16:48:52 mx postfix/lmtp[18136]: input attribute value: 0
> Jun  1 16:48:52 mx postfix/lmtp[18136]: private/defer socket: wanted 
> attribute: (list terminator)
> Jun  1 16:48:52 mx postfix/lmtp[18136]: input attribute name: (end)
> Jun  1 16:48:52 mx postfix/lmtp[18136]: B7B0B9A2EB0: to=<[email protected]>, 
> orig_to=<[email protected]>, relay=imap.x.x[10.0.13.83]:24, delay=0.3, 
> delays=0.19/0/0.09/0.02, dsn=4.3.0, status=deferred (host 
> imap.x.x[10.0.13.83] said: 451 4.3.0 System I/O error (in reply to end 
> of DATA command))
>
> Steve
>
> On Fri, Jun 1, 2018 at 9:33 AM, Ken Murchison <[email protected] 
> <mailto:[email protected]>> wrote:
>
>     On 6/1/18 12:21 PM, Stephen Ingram wrote:
>
>         I'm receiving a 451 4.3.0 System I/O error (in reply to end of
>         DATA command) error from Postfix when trying to deliver to
>         cyrus-imap and not really sure why. I'm on CentOS 7 (2.4.17-8)
>         after downgrading from current version. I'm using Kerberos
>         GSSAPI to connect to the front end, but authentication appears
>         to be working fine as I can see authenticated when enabling
>         LMTP debugging in Postifx. All messages are refused for
>         delivery though. I'm not sure what to do. Any suggestions?
>
>
>     Any chance that Kerberos is negotiating a security layer?
>
>     -- 
>     Kenneth Murchison
>     Cyrus Development Team
>     FastMail Pty Ltd
>
>
>     ----
>     Cyrus Home Page: http://www.cyrusimap.org/
>     List Archives/Info:
>     http://lists.andrew.cmu.edu/pipermail/info-cyrus/
>     <http://lists.andrew.cmu.edu/pipermail/info-cyrus/>
>     To Unsubscribe:
>     https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
>     <https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus>
>
>

-- 
Ken Murchison
Cyrus Development Team
FastMail US LLC

----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

null