Re: [swinog] bluewin & DNSNULL

2019-07-11 Diskussionsfäden Marcel.Gschwandl
As pointed out by Daniel, the original issue was caused by a listing of this IP on Spamhaus SBL and Bluewin does in fact use Spamhaus as a RBL provider and has done so for quite some time. As to the "DNSNULL" part of the error message, this was caused by an issue in the lookup of the

Re: [swinog] Bluewin Error: Der MX-Eintrag fuer die Domaene aerni.com kann nicht verifiziert werden

2018-01-12 Diskussionsfäden Marcel.Gschwandl
Hello BenoƮt Put simply, we do DNS requests for MX or A records for the given sender domain, if either exists this check is passed. As for the issue at hand: the DNS servers of your customer are (were) not properly reachable from our IP ranges or more specifically we are (were) unable to get

Re: [swinog] Bluewin MX Protocol Errors

2015-11-03 Diskussionsfäden Marcel.Gschwandl
We were able to identify and reliably reproduce the problem in out testing environment, it is related to the TLS-Offloading which interferes with the traffic in some cases and brakes the communication with sending RSET commands and not handling the responses correctly. Thanks to all who

Re: [swinog] Bluewin MX Protocol Errors

2015-11-02 Diskussionsfäden Marcel.Gschwandl
Hi Dan, We don't see a general pattern, but can you contact me off-list so we might figure out if there is a wider issue here? Regards Marcel -Original Message- From: swinog-boun...@lists.swinog.ch [mailto:swinog-boun...@lists.swinog.ch] On Behalf Of Daniel Kamm Sent: Monday, November