大网数据广告活动
服务器运维问答

Mail stuck in exim queue for no reason?

· 52CE 我爱测

On my server, mail is sometimes delayed for apparently no specific reason. In this example two mails were generated by systemd-cron about failing cron jobs: mailq output (domains edited): 3m 1.9K 1i6W6d-0003UT-Ut <[email omitted]…

问题原文

原帖链接 · steiny · CC BY-SA 4.0

On my server, mail is sometimes delayed for apparently no specific reason.

In this example two mails were generated by systemd-cron about failing cron jobs:

mailq output (domains edited):

 3m  1.9K 1i6W6d-0003UT-Ut <[email omitted]>
          www-data@server

 3m  1.8K 1i6W6e-0003Uh-1y <[email omitted]>
          root@server

After some minutes or when I issue exim -qf the mail is finally sent and delivered without any issue.

/var/log/exim4/mainlog (Domains/IPs edited):

2019-09-07 10:30:04 1i6W6d-0003UT-Ut <= [email omitted] U=nobody P=local S=1914
2019-09-07 10:30:04 1i6W6e-0003Uh-1y <= [email omitted] U=nobody P=local S=1875
2019-09-07 10:34:13 Start queue run: pid=13447 -qf
2019-09-07 10:34:14 1i6W6d-0003UT-Ut => [email omitted] <www-data@server> R=smarthost T=remote_smtp_smarthost H=smtp.example.com [1.2.3.4] X=TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256 CV=yes DN="…" A=plain C="250 2.0.0 Ok: queued as 268D26139FAA"
2019-09-07 10:34:14 1i6W6d-0003UT-Ut Completed
2019-09-07 10:34:14 1i6W6e-0003Uh-1y => [email omitted] <root@server> R=smarthost T=remote_smtp_smarthost H=smtp.example.com [1.2.3.4] X=TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256 CV=yes DN="…" A=plain C="250 2.0.0 Ok: queued as BA7EE6139FAC"
2019-09-07 10:34:14 1i6W6e-0003Uh-1y Completed
2019-09-07 10:34:14 End queue run: pid=13447 -qf

When I sent an email from command line echo 'Test' | mail -s test root, the mail is delivered immediately, without log entries for start/end queue run:

2019-09-07 10:35:21 1i6WBk-0003V9-VR <= [email omitted] U=root P=local S=397
2019-09-07 10:35:21 1i6WBk-0003V9-VR => [email omitted] <root@server> R=smarthost T=remote_smtp_smarthost H=smtp.example.com [1.2.3.4] X=TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256 CV=yes DN="…" A=plain C="250 2.0.0 Ok: queued as 723116139F77"
2019-09-07 10:35:21 1i6WBk-0003V9-VR Completed

Do you know the reason for the delay? How can I have exim process all mail immediately?

My configuration:

  • up to date Debian Buster
  • exim version 4.92-8+deb10u2
  • both, root and www-data (among others) have aliases to [email omitted] (external)
  • standard Debian exim config (using update-exim4.conf)

/etc/exim4/update-exim4.conf.conf:

dc_eximconfig_configtype='smarthost'
dc_other_hostnames=''
dc_local_interfaces='127.0.0.1 ; ::1'
dc_readhost='server'
dc_relay_domains=''
dc_minimaldns='false'
dc_relay_nets=''
dc_smarthost='smtp.example.com::587'
CFILEMODE='644'
dc_use_split_config='true'
dc_hide_mailname='false'
dc_mailname_in_oh='true'
dc_localdelivery='maildir_home'

已采纳解答

原帖链接 · steiny · CC BY-SA 4.0

Apparently, this situation is caused by the combination of exim and systemd as described on the systemd-devel mailing list.

TL;DR: To send a mail from the command line exim forks a process to deliver the mail immediately. However, as the parent process exists, the systemd unit for this cron job terminates, and systemd kills all remaining processes in the control group, including the previously forked process responsible for mail delivery.

To prevent this I found two solutions (apart from fixing exim itself):

  • Using an SMTP client to send mail via TCP to the local exim daemon, such as swaks(1).
  • Delaying the end of the systemd unit, e.g., by calling exim -qf (queue flush) after calling mail.

Both solutions are not optimal. The first requires extra software and opens a local tcp connection while the second requires root privileges. For now, I will stick with swaks.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2019-09-07)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。