LMTP error reading configuration
Hello,
I am getting the following error on my dovecot LMTP server, upon delivery from my postfix mailserver:
Oct 6 03:31:09 m dovecot[36551]: lmtp: Fatal: Error reading configuration: read(/var/run/dovecot/config) failed: read(size=8192) failed: Interrupted system call - Also failed to read config by executing doveconf: /var/run/dovecot/config is a UNIX socket (path is from CONFIG_FILE environment)
This results in mail being deferred by postfix (different host), and successfully delivered at the next try:
Oct 6 03:31:10 mailer postfix/lmtp[44835]: 46F0BA329: to=d@l.ynx.fr, orig_to=<root>, relay=192.168.1.101[192.168.1.101]:24, delay=17, delays=0.2/0.01/16/0, dsn=4.4.2, status=deferred (lost connection with 192.168.1.101[192.168.1.101] while receiving the initial server greeting)
Any idea where it comes from?
I am running dovecot 2.3.21.1 (d492236fa0) on FreeBSD 14.1-RELEASE-p5.
Here is my configuration:
# 2.3.21.1 (d492236fa0): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.21.1 (49005e73) # OS: FreeBSD 14.1-RELEASE-p3 amd64 # Hostname: m.ynx.fr
mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = create special_use = \Trash } prefix = } passdb { args = scheme=CRYPT username_format=%u /usr/local/etc/dovecot/users driver = passwd-file } protocols = imap lmtp sieve service auth { inet_listener { port = 144 } } service lmtp { inet_listener lmtp { port = 24 } user = vmail } service managesieve-login { inet_listener sieve { port = 4190 } } ssl = no userdb { args = uid=vmail gid=vmail home=/home/vmail/%u driver = static } protocol lmtp { mail_plugins = " sieve" } protocol imap { mail_max_userip_connections = 100 }
Kind regards, D
On 07/10/2024 05:08, DaLynX via dovecot wrote:
Hello,
I am getting the following error on my dovecot LMTP server, upon delivery from my postfix mailserver:
Oct 6 03:31:09 m dovecot[36551]: lmtp: Fatal: Error reading configuration: read(/var/run/dovecot/config) failed: read(size=8192) failed: Interrupted system call - Also failed to read config by executing doveconf: /var/run/dovecot/config is a UNIX socket (path is from CONFIG_FILE environment)
This results in mail being deferred by postfix (different host), and successfully delivered at the next try:
Oct 6 03:31:10 mailer postfix/lmtp[44835]: 46F0BA329: to=d@l.ynx.fr, orig_to=<root>, relay=192.168.1.101[192.168.1.101]:24, delay=17, delays=0.2/0.01/16/0, dsn=4.4.2, status=deferred (lost connection with 192.168.1.101[192.168.1.101] while receiving the initial server greeting)
Any idea where it comes from?
I am running dovecot 2.3.21.1 (d492236fa0) on FreeBSD 14.1-RELEASE-p5.
Here is my configuration:
...
Looks like a tricky problem. Are there any other dovecot processes logging errors or warnings (e.g. the config process)? Is this happening on all messages or only occasionally and is there any pattern to it? If you look at the full lmtp logging from connect to when it gives the error, is there some pattern there that is different for when the problem happens compared to when it doesn't?
John
On 11/10/2024 20:56 EEST John Fawcett via dovecot dovecot@dovecot.org wrote:
On 07/10/2024 05:08, DaLynX via dovecot wrote:
Hello,
I am getting the following error on my dovecot LMTP server, upon delivery from my postfix mailserver:
Oct 6 03:31:09 m dovecot[36551]: lmtp: Fatal: Error reading configuration: read(/var/run/dovecot/config) failed: read(size=8192) failed: Interrupted system call - Also failed to read config by executing doveconf: /var/run/dovecot/config is a UNIX socket (path is from CONFIG_FILE environment)
This results in mail being deferred by postfix (different host), and successfully delivered at the next try:
Oct 6 03:31:10 mailer postfix/lmtp[44835]: 46F0BA329: to=d@l.ynx.fr, orig_to=<root>, relay=192.168.1.101[192.168.1.101]:24, delay=17, delays=0.2/0.01/16/0, dsn=4.4.2, status=deferred (lost connection with 192.168.1.101[192.168.1.101] while receiving the initial server greeting)
Any idea where it comes from?
I am running dovecot 2.3.21.1 (d492236fa0) on FreeBSD 14.1-RELEASE-p5.
Here is my configuration:
...
Looks like a tricky problem. Are there any other dovecot processes logging errors or warnings (e.g. the config process)? Is this happening on all messages or only occasionally and is there any pattern to it? If you look at the full lmtp logging from connect to when it gives the error, is there some pattern there that is different for when the problem happens compared to when it doesn't?
John
Is dovecot running in the first place?
Aki
participants (3)
-
Aki Tuomi
-
DaLynX
-
John Fawcett