I think I found the cause – awaiting some test results to confirm.







From: LISTSERV Site Administrators' Forum [mailto:[log in to unmask]] On Behalf Of Peter M. Weiss

Sent: Friday, April 20, 2018 12:47 PM

To: [log in to unmask]

Subject: Re: Messages Not Being Distributed



Try an NSLOOKUP type=MX on the recipient @host.  That can be very telling.



You may need to telnet port 25 to each of them and begin a simulated RFC821 dialog.  Maybe a VRFY will fail.



In my former career, I've seen misconfigured MX hosts that would only be a problem when the preferred host wasn't available.



________________________________



To unsubscribe from the LSTSRV-L list, click the following link:

http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpeach.ease.lsoft.com%2Fscripts%2Fwa-PEACH.exe%3FSUBED1%3DLSTSRV-L%26A%3D1&data=01%7C01%7Cdmills1%40KENT.EDU%7Cec84a8da0c534fa7499c08d5a6de4b06%7Ce5a06f4a1ec44d018f73e7dd15f26134%7C1&sdata=HbLiPETJcBYrgkmHold83D0d9b%2FIjPvQz5ZjETa%2FceE%3D&reserved=0>



############################



To unsubscribe from the LSTSRV-L list:

write to: mailto:[log in to unmask]

or click the following link:

http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1