1. Forum
  2. Usenet
  3. COMP.MAIL.SENDMAIL

  • successful delivery not logged when message has 2 recipients and one se

    From Marco Moock@21:1/5 to All on Fri Oct 27 14:31:19 2023
    Hello!

    I experienced that 2 times with 8.17.1.9 on Debian 12.

    A message with 2 recipients got a 450 error of one server, the other
    one got delivered immediately.

    It was in the queue and I ran sendmail -q -v and it got delivered (I
    saw it on the output and now it finally reached the mailing list), but
    not logged.


    m@srv1:~$ sudo journalctl --no-pager -t sm-mta -S 0:00 |grep 'to=<[email protected]>'
    Oct 27 12:44:16 srv1.dorfdsl.de sm-mta[47521]: 39RAiAG4047519: to=<[email protected]>, delay=00:00:06, xdelay=00:00:06, mailer=esmtp, pri=62213, relay=mx.mailop.org. [IPv6:2a03:4000:37:599:d8ce:dff:fee1:81c2], dsn=4.3.2, reply=450-4.3.2 Service currently
    unavailable, stat=Deferred: 450-4.3.2 Service currently unavailable
    m@srv1:~

    I also experienced that with another mail this morning.

    --
    kind regards
    Marco

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Claus =?iso-8859-1?Q?A=DFmann?= @21:1/5 to Marco Moock on Fri Oct 27 09:54:26 2023
    Marco Moock wrote:

    I experienced that 2 times with 8.17.1.9 on Debian 12.

    Logging via "systemd"?

    It was in the queue and I ran sendmail -q -v and it got delivered (I

    m@srv1:~$ sudo journalctl --no-pager -t sm-mta -S 0:00 |grep 'to=<[email protected]>'

    You should grep for the "queue id" instead -- in the full log
    (whatever -t sm-mta is: does it select entries matching that?)

    --
    Note: please read the netiquette before posting. I will almost never
    reply to top-postings which include a full copy of the previous
    article(s) at the end because it's annoying, shows that the poster
    is too lazy to trim his article, and it's wasting the time of all readers.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marco Moock@21:1/5 to All on Fri Oct 27 21:45:01 2023
    Am 27.10.2023 um 09:54:26 Uhr schrieb Claus Aßmann:

    Marco Moock wrote:

    I experienced that 2 times with 8.17.1.9 on Debian 12.

    Logging via "systemd"?

    Yes, and I use journalctl to get the logs and that is default in all
    systemd based systems, some even don't have syslogd installed by
    default.

    You should grep for the "queue id" instead -- in the full log
    (whatever -t sm-mta is: does it select entries matching that?)

    -t, --identifier=SYSLOG-KENNUNG

    That seems to be the same identifier that syslogd uses and that was the
    issue.

    The sendmail -q command uses the 'sendmail' identifier instead of
    sm-mta.

    Oct 27 12:48:15 srv1.dorfdsl.de sendmail[47549]: 39RAiAG4047519: to=<[email protected]>, delay=00:04:05, xdelay=00:00:02, mailer=esmtp, pri=152213, relay=mx.mailop.org. [IPv6:2a03:4000:37:599:d8ce:dff:fee1:81c2], dsn=2.0.0, stat=Sent (Ok: queued as
    4SGzsW2V5mz8sgJ)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)