Hi Jan,
i tried postmas...@ewe.net <mailto:postmas...@ewe.net> and postmas...@ewetel.de. Will now try the third (your first suggestion) :) thanks. Stefan -----Ursprüngliche Nachricht----- Von: Jan-Philipp Benecke <j...@cleverreach.com> Gesendet: Montag 9 März 2020 15:53 An: Stefan Bauer <stefan.ba...@cubewerk.de> CC: mailop <mailop@mailop.org> Betreff: Re: [mailop] Ewetel postmaster wanted - your IP 116.203.31.6 seems to be dynamic - please use the smarthost of your ISP Hey Stefan, we hadn't any problems with them. We wrote them about our block on 14.01. and they did respond on the same day. When did you wrote them ? Did your wrote postmas...@ewetel.net or did you wrote postmas...@ewe.net ? Based on their answer, i think they have a internal list with dynamic ip ranges. Best, Jan-Philipp Jan-Philipp Benecke Deliverability Engineer Fon: +49 4402 97390-00 E-Mail: j...@cleverreach.com <mailto:j...@cleverreach.com> CleverReach GmbH & Co. KG HRA 4020 Oldenburg (Oldb.) cleverreach.de <http://www.cleverreach.com/de/> <http://www.cleverreach.com/de/> Vertreten durch: CleverReach Verwaltungs GmbH, HRB 210079 Oldenburg (Oldb.) //CRASH Building | Schafjückenweg 2 | 26180 Rastede | Germany Geschäftsführung: Jens Klibingat, Sebastian Schwarz & Sebastian Strzelecki Aufsichtsrat: Rolf Hilchner & Heinz-Wilhelm Bogena Stefan Bauer via mailop schrieb am 09.03.20 um 15:03: Hi, it's just DNS round robin for our senders. did not had a sigle issue with that over the previous 2 years. Still thinking, that ewetel/ewe just uses ancient RBLs, that reports the specific IP from a dynamic-block. Stefan -----Ursprüngliche Nachricht----- Von: Vytis Marciulionis <marciulionis.vy...@gmail.com> Gesendet: Montag 9 März 2020 14:52 An: Stefan Bauer <stefan.ba...@cubewerk.de> CC: mailop <mailop@mailop.org> Betreff: Re: [mailop] Ewetel postmaster wanted - your IP 116.203.31.6 seems to be dynamic - please use the smarthost of your ISP Hi Stefan, This could also happen because your PTR record of sending IP address resolves with 3 IPs e: IP 116.203.31.6 - PTR securetransport.cubewerk.de - IPs 178.254.23.77; 116.203.31.6; 188.68.39.254 I know that technically it is nothing bad but, I can imagine why some sensors could return errors, especially since the 3 IP addresses are from different ASNs: I guess those 3 IPs are set as fallback in this situation? On Mon, Mar 9, 2020 at 11:03 AM Stefan Bauer via mailop <mailop@mailop.org <mailto:mailop@mailop.org> > wrote: Never had delivery issues from hetzner-blocks so far (crossing fingers) but I'm aware of the past. Looks like there is at least one RBL around, that list our IP as dynamic. https://www.rbl-dns.com/bl?ip=116.203.31.6 One just have to pay to get de-listed. What a wonderful world. Stefan -----Ursprüngliche Nachricht----- Von: Andrew C Aitchison <and...@aitchison.me.uk> Gesendet: Montag 9 März 2020 10:47 An: Stefan Bauer <stefan.ba...@cubewerk.de> CC: mailop <mailop@mailop.org> Betreff: Re: [mailop] Ewetel postmaster wanted - your IP 116.203.31.6 seems to be dynamic - please use the smarthost of your ISP On Mon, 9 Mar 2020, Stefan Bauer via mailop wrote: > Any ewetel postmaster around? One of our IPs (subject) get flagged > as dynamic during delivery to ewetel. However this IP is static. I am not surprised that Ewetel has guessed wrong: whois 116.203.31.6 -h whois.ripe.net <http://whois.ripe.net> gives a /16 belonging to our old friends Hetzner. -- Andrew C. Aitchison Kendal, UK and...@aitchison.me.uk <mailto:and...@aitchison.me.uk> _______________________________________________ mailop mailing list mailop@mailop.org <mailto:mailop@mailop.org> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop -- Pagarbiai, Vytis Marčiulionis +37064734475 _______________________________________________ mailop mailing list mailop@mailop.org <mailto:mailop@mailop.org> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
