Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
     Installed exim4 and setup localhost as mailserver

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
     Sending/receiving emails to local users is ok;
     LAN users receiving emails from server PC is ok, but cannot send
     emails.
   * What was the outcome of this action?
     exim paniclog /var/log/exim4/paniclog on lenovo has non-zero size, mail system might be broken. Up to 10 lines are quoted below.

2023-03-17 23:26:36 daemon_notifier_socket bind: Address already in use
2023-03-17 23:31:06 socket bind() to port 25 for address 127.0.0.1 failed: Address already in use: daemon abandoned
2023-03-17 23:31:34 socket bind() to port 25 for address 127.0.0.1 failed: Address already in use: daemon abandoned
   * What outcome did you expect instead?
     There is no error, and emails for LAN users via port 25 should work.

*** End of the template - remove these template lines ***

[...]

Looks like there is another program liestening on port 25.

cu Andreas

Control: tags -1 moreinfo
Control: severity -1 normal

[...]
  ^^^^^^^^^
[...]

Actually that does seem to be relevant at all, the message is from March
17.

What do the configuration files look like (especially
/etc/exim4/update-exim4.conf.conf)? What doi the log files show for
which mail?

cu Andreas

Control: tags -1 moreinfo
Control: severity -1 normal

[...]
  ^^^^^^^^^
[...]

Actually that does seem to be relevant at all, the message is from March
17.

What do the configuration files look like (especially
/etc/exim4/update-exim4.conf.conf)? What doi the log files show for
which mail?

cu Andreas

Each time I start the machine, my mailbox will have at least one such
email.

I attach the conf file and the email.

Each time I start the machine, my mailbox will have at least one such
email.

I attach the conf file and the email.

Each time I start the machine, my mailbox will have at least one such
email.

I attach the conf file and the email.

This is expected and intended behavior, you need to manually move the
paniclog away for the message to go away. See README.Debian 2.5.1

Andreas, we should probably include this reference into the mail
message.

Greetings
Marc

This is expected and intended behavior, you need to manually move the
paniclog away for the message to go away. See README.Debian 2.5.1

Andreas, we should probably include this reference into the mail
message.

Greetings
Marc

在 2023-04-09星期日的 15:14 +0200，Marc Haber写道：
Thank you. paniclog removed

在 2023-04-09星期日的 15:14 +0200，Marc Haber写道：
Thank you. paniclog removed

Dear maintainer,

I have the same issue on my server.  It seems to happen any time the
exim4 daemon gets restarted.  Logs indicate that the process is not shut
down correctly, leaving a stale daemon listening on the old port, which
causes the error on startup for the new daemon.  After an update just
now:

Oct 02 16:46:37 scully.more-magic.net systemd[1]: Stopping exim4.service - LSB: exim Mail Transport Agent...
Oct 02 16:46:37 scully.more-magic.net exim4[574161]: Stopping MTA:.
Oct 02 16:46:37 scully.more-magic.net systemd[1]: exim4.service: Deactivated successfully.
Oct 02 16:46:37 scully.more-magic.net systemd[1]: exim4.service: Unit process 701 (exim4) remains running after unit stopped.
Oct 02 16:46:37 scully.more-magic.net systemd[1]: Stopped exim4.service - LSB: exim Mail Transport Agent.
Oct 02 16:46:37 scully.more-magic.net systemd[1]: exim4.service: Consumed 2min 17.056s CPU time.
Oct 02 16:46:40 scully.more-magic.net systemd[1]: exim4.service: Found left-over process 701 (exim4) in control group while starting unit. Ignoring.
Oct 02 16:46:40 scully.more-magic.net systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 02 16:46:40 scully.more-magic.net systemd[1]: Starting exim4.service - LSB: exim Mail Transport Agent...
Oct 02 16:46:40 scully.more-magic.net exim4[574712]: Starting MTA: exim4.
Oct 02 16:46:40 scully.more-magic.net systemd[1]: Started exim4.service - LSB: exim Mail Transport Agent.

In /var/log/exim4/paniclog:

2023-10-02 16:51:10 socket bind() to port 25 for address (any IPv6) failed: Address already in use: daemon abandoned

If I use systemctl to stop the daemon, it leaves an exim4 process
running.  Manually calling "pkill exim4" and then using systemctl to
start exim4 resolves the issue (until the next restart).

I thought it was ipv6-related, but if I see message #5 in this bug it
seems that this is not necessarily the case.  Perhaps it is caused by
having exim listen on multiple interfaces (ipv4 and ipv6), or maybe it's
a red herring?

Anyway, I hope this helps debug the problem further!

Regards,
Peter Bex

If this is reproducible,it is probably unrelated to this bug report.
Does the last exim process eventually vanish if you wait a while? It
might stil be doing something, such as waiting for a timeout.

Greetings
Marc

process is still alive.  I can also still connect to port 25, exim
is still actively listening on both ipv4 and ipv6 interfaces.
Journalctl contains no errors, it just claims it stopped cleanly:

Oct 03 09:23:29 scully.more-magic.net systemd[1]: Stopping exim4.service - LSB: exim Mail Transport Agent...
Oct 03 09:23:29 scully.more-magic.net exim4[592530]: Stopping MTA:.
Oct 03 09:23:29 scully.more-magic.net systemd[1]: exim4.service: Deactivated successfully.
Oct 03 09:23:29 scully.more-magic.net systemd[1]: exim4.service: Unit process 575519 (exim4) remains running after unit stopped.
Oct 03 09:23:29 scully.more-magic.net systemd[1]: Stopped exim4.service - LSB: exim Mail Transport Agent.
Oct 03 09:23:29 scully.more-magic.net systemd[1]: exim4.service: Consumed 4.140s CPU time.


It only complains about the left-over process when I start it again:


Oct 03 09:38:40 scully.more-magic.net systemd[1]: exim4.service: Found left-over process 575519 (exim4) in control group while starting unit. Ignoring.
Oct 03 09:38:40 scully.more-magic.net systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 03 09:38:40 scully.more-magic.net systemd[1]: Starting exim4.service - LSB: exim Mail Transport Agent...
Oct 03 09:38:40 scully.more-magic.net exim4[592898]: Starting MTA: exim4.
Oct 03 09:38:40 scully.more-magic.net systemd[1]: Started exim4.service - LSB: exim Mail Transport Agent.


This is also usually when exim itself notices and creates the paniclog
entry.  Strangely enough, it didn't do that this time...

Cheers,
Peter