From nobody Thu Sep 26 15:01:33 2024 X-Original-To: freebsd-questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4XDxdC4XbKz5XPZv for ; Thu, 26 Sep 2024 15:01:35 +0000 (UTC) (envelope-from freebsd-doc@fjl.co.uk) Received: from bs2.fjl.org.uk (bs2.fjl.org.uk [84.45.41.208]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "bs2.fjl.org.uk", Issuer "bs2.fjl.org.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XDxdB6Ywsz4g0T for ; Thu, 26 Sep 2024 15:01:34 +0000 (UTC) (envelope-from freebsd-doc@fjl.co.uk) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of freebsd-doc@fjl.co.uk designates 84.45.41.208 as permitted sender) smtp.mailfrom=freebsd-doc@fjl.co.uk; dmarc=none Received: from roundcube.fjl.uk ([192.168.0.2]) by bs2.fjl.org.uk (8.16.1/8.16.1) with ESMTP id 48QF1XZ3003495 for ; Thu, 26 Sep 2024 15:01:33 GMT (envelope-from freebsd-doc@fjl.co.uk) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Date: Thu, 26 Sep 2024 16:01:33 +0100 From: Frank Leonhardt To: FreeBSD Mailing List Subject: Re: Odd SASL Behavior In-Reply-To: References: Message-ID: <6651a50a8935812ae8868e9e3e4c121c@fjl.co.uk> X-Sender: freebsd-doc@fjl.co.uk Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-1.39 / 15.00]; NEURAL_HAM_SHORT(-0.90)[-0.898]; NEURAL_HAM_LONG(-0.83)[-0.826]; NEURAL_SPAM_MEDIUM(0.53)[0.533]; R_SPF_ALLOW(-0.20)[+ip4:84.45.41.208:c]; ONCE_RECEIVED(0.10)[]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:25577, ipnet:84.45.0.0/17, country:GB]; MISSING_XM_UA(0.00)[]; RCVD_TLS_LAST(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; R_DKIM_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; DMARC_NA(0.00)[fjl.co.uk]; TO_DN_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-questions@freebsd.org]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4XDxdB6Ywsz4g0T X-Spamd-Bar: - On 2024-08-15 21:39, Tim Daneliuk wrote: > This is a puzzler - hoping someone can shed some light .. > > I have a sendmail/SASL configuration that's been unchanged for years > and years. > > Today, all of a sudden, users were unable to send mail from their UAs > because SASL > was grouching about failed password authentication. After poking > around and finding > nothing having changed, a reboot fixed this. > > Ideas? There's something spammers can do that upsets (old) SASL causing it to go wonky and start rejecting authentication. IME it also consumes a LOT of RAM while it's happening. A solution is to monitor your pagefile and issue a "service saslauthd restart" if it starts to grow. A reboot will also fix it, of course, but when I figured out what was killing the server this worked pretty well instead. Blackholing an IP that's failed authentication too often also helps. Regards, Frank. -- ------ 25-Nov-24 My apologies to everyone who I appear to have ignored for the last few years. A procmail script was misfiling some replies to Questions to the wrong folder.