Bug 231046 - mail/ssmtp 2.64 doesnt send final ack - delays mail server with hanging LAST_ACT on FreeBSD11.2S
Summary: mail/ssmtp 2.64 doesnt send final ack - delays mail server with hanging LAST_...
Status: Closed Works As Intended
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
Depends on:
Reported: 2018-08-31 03:21 UTC by dewayne
Modified: 2020-07-04 21:36 UTC (History)
2 users (show)

See Also:
bugzilla: maintainer-feedback? (aragon)


Note You need to log in before you can comment on or make changes to this bug.
Description dewayne 2018-08-31 03:21:36 UTC
Unsure if this is an implementation issue or something around traffic flow.

Multiple messages being sent with ssmtp.  When the server starts rejecting messages due to connection rate setting, there are pending LAST_ACKs; which ssmtp should ack before terminating.  Instead ssmtp just stops.

Resulting in sockstat -s revealing
root     sendmail   31777 5  tcp4      ESTABLISHED
root     sendmail   31777 11 tcp4      ESTABLISHED
root     ssmtp      31603 3  tcp4       ESTABLISHED
root     ssmtp      31381 3  tcp4       ESTABLISHED
root     ssmtp      31257 3  tcp4       ESTABLISHED
root     sendmail   39991 9  tcp4       *:*                   LISTEN
?        ?          ?     ?  tcp4      LAST_ACK
?        ?          ?     ?  tcp4      LAST_ACK
?        ?          ?     ?  tcp4      LAST_ACK

The problem is that sendmail wont respond to new connections until the LAST_ACK timeouts.  

Workaround - increase number of connections to that particular port 2525 which is only for administrative email.  Aside: there are multiple jails transmitting to the sendmail (latest version) jail via lo0.  It just appears to be coming over its "localhost" addr.
Comment 1 Walter Schwarzenfeld freebsd_triage 2019-08-15 04:52:49 UTC
Maintainer feedback!
Comment 2 dewayne 2020-07-04 21:36:58 UTC
(In reply to Walter Schwarzenfeld from comment #1)
This appears to have been a configuration issue.  Functions correctly with ssmpt.conf of

#201910 added