Path: ...!weretis.net!feeder9.news.weretis.net!panix!.POSTED.panix6.panix.com!nam.panix.com!robomod!not-for-mail
From: Rayner Lucas <usenet202101@magic-cookie.co.ukNOSPAMPLEASE>
Newsgroups: news.admin.moderation
Subject: Re: misc.legal.moderated
Date: Tue, 15 Oct 2024 13:35:33 EDT
Organization: The Lumber Cartel (TINLC)
Approved: NAM Approval Key <nam-approval-key@panix.com>
Message-ID: <MPG.4178b780835467fc9896e8@news.eternal-september.org>
References: <vejp2e$1a9c9$2@dont-email.me> <vel772$1k6il$2@dont-email.me> <slrnvgt0lg.1o79q.rayban@raybanana.net> <vem6l8$30dgi$1@jik4.kamens.us>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Injection-Info: reader1.panix.com; posting-host="panix6.panix.com:166.84.1.6";
	logging-data="20797"; mail-complaints-to="abuse@panix.com"
User-Agent: MicroPlanet-Gravity/3.0.4
Cancel-Lock: sha1:3vLg4Z1UWFNG5sqBF23TTStvx04=
Bytes: 3318
Lines: 22

In article <vem6l8$30dgi$1@jik4.kamens.us>, jik@kamens.us says...
> 
> Hello friends.
> 
> Somehow DNS within Postfix got wedged on
> mod-relay-1.kamens.us for several days. I didn't realize this
> was happening because my system monitors didn't detect the
> issue. I found out about it this morning when Postfix somehow
> got unwedged and I got several days worth of delayed logwatch
> emails.
> 
> I will investigate what happened and try to figure out how to
> monitor for this moving forward so it will be detected more
> quickly if it happens again.
> 
> In any case things should be working fine now.

Thanks for investigating and confirming that the relay service should be 
working again now. Much appreciated!

All the best,
Rayner