Yes, build 22200 contains a fix for the FQDN (relay host) detection. A log line was added to the changed 'resolve-code' - but I've overlooked, that this code is also used as fallback in the MX/MXA check, in case nothing is resolved using the configured DNS. The next version will prevent these loglines, if the code is called from the MX/MXA check.
Thank you for reporting. Thomas DISCLAIMER: ******************************************************* This email and any files transmitted with it may be confidential, legally privileged and protected in law and are intended solely for the use of the individual to whom it is addressed. This email was multiple times scanned for viruses. There should be no known virus in this email! ******************************************************* Von: "K Post" <nntp.p...@gmail.com> An: "ASSP development mailing list" <assp-test@lists.sourceforge.net> Datum: 09.08.2022 17:55 Betreff: [Assp-test] Warnings for unable to resolve IP Has anything changed with recent dev versions of ASSP in terms of warnings in the logs for being unable to lookup an IP? For example: warning: can't resolve the IP-address for the destination stonewallkitchenvip.com using the configured DNS-servers Nothing's wrong with assp, stonewallkitchenvip.com doesn't exist, but I'm getting a lot of warnings in the logs for misconfigured (or non existent) domains since updating to the latest ASSP and I don't think I've had that before. I can stop the alert emails based on the warning, I just wanted to see if these are new / different warnings that ASSP is doing now or if there's been an uptick in bulk sending services doing things wrong. Thanks [Anhang "attm5aih.txt" gelöscht von Thomas Eckardt/eck] [Anhang "att78ilr.txt" gelöscht von Thomas Eckardt/eck]
_______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
