Hi dovecot list,
   I'm troubleshooting an LMTP delivery issue with Dovecot and would
   appreciate clarification on the meaning and impact of the following log
   message, which appears repeatedly during delivery attempts:

   auth-worker(2961): Debug: conn unix:auth-worker (pid=2948,uid=107):
   Disconnected: Connection closed (fd=-1)

   Environment

     o OS: Ubuntu (latest LTS, fully up to date)
     o Dovecot: distribution package (current version for Ubuntu)
     o MTA: Postfix
     o Delivery: LMTP to Dovecot
     o User database: MySQL (userdb lookup succeeds)
     o Mail storage: Maildir
     o Quotas: enabled via userdb (quota_rule)

   Context

     o LMTP accepts the recipient and completes userdb lookup successfully.
     o The mailbox path, uid, gid, and quota are correctly returned.
     o Postfix later receives a 451 4.3.0 Temporary internal error after the
       DATA phase.
     o The above auth-worker ... Disconnected: Connection closed (fd=-1)
       message appears around the same time.

   Questions

    1. Is this Disconnected: Connection closed (fd=-1) message
       expected/normal behavior for auth-worker processes once a lookup is
       complete?
    2. Under what circumstances would this indicate a real problem versus a
       harmless connection teardown?
    3. Could this message itself contribute to, or explain, LMTP 451 4.3.0
       Temporary internal error responses?
    4. Are there specific auth-worker, LMTP, or debug settings recommended to
       determine whether this disconnect is abnormal?

   So far, authentication and userdb lookups appear clean, and there are no
   explicit permission or quota errors logged, which makes it unclear whether
   this message is relevant to the delivery failure or simply informational.
   Any clarification on how to interpret this log entry -- and how to confirm
   whether it is benign or problematic -- would be greatly appreciated.

   Kind Regards,

   Kim
_______________________________________________
dovecot mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to