On 6 October 2017 at 18:43, Luis E. Muñoz via mailop <[email protected]> wrote: > I can confirm this for imp-5.mail.tiscali.it from IPv4s in US west, center > and east as well as Amsterdam. The rest of the MX servers work although the > wait seems unusually high.
We never try imap-5 because it is PRIO 50 and there are 4 PRIO 10 before that and we don't try the next MX in case of a timeout after the ".". I see the same delay on all of the etb-*.mail.tiscali.it. servers, now I get a reply much more often, usually 30-50 seconds after the ".". It could be that if the delay after the "." is under 60 seconds then the server send the 250 OK reply and everything is ok. If the delay is higher then the message MAY be delivered but the server won't reply anymore and the connection get stuck, and this will result in double deliveries. Weird. It really seems a buggy behaviour and not an antispam measure, so we now rerouted all of tiscali email to the IP pool "working fine" so I can't monitor anymore the delivery stats, I just can do some manual test. Thank you for the feedback, Stefano > Best regards > > -lem > > On 6 Oct 2017, at 8:13, Federico Santandrea wrote: > > We are also experiencing delays to Tiscali, but of a different nature. > > We have the 14 second delay before EHLO/HELO right after connecting, and no > delay on ".". Delivery to mailbox seems instant, at least for the test > setup. > > Also it looks like one of tiscali.it's MXes is just answering with "421 > 4.2.1 Service not available" to us, after the initial delay. > > This seems to be independent of the source IP address. > > On 06/10/2017 11:41, Stefano Bagnara wrote: > > 1) I tried an "outsider" IP that never sent an email and it did the > same, so it is not only a specific IP pool, but a larger issue. > 2) There is no disconnect after 30 seconds, instead the connection is > stuck forever until we timeout client side (5 minutes, but I tried > increasing to 30 minutes to no avail). > 3) The email are indeed delivered.. around 1 minute after the "." the > email is already in the target inbox even if we never got a response > at smtp time: the smtp connection is still stuck and eventually time > out. > > -- > Federico > > _______________________________________________ > mailop mailing list > [email protected] > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop > > > _______________________________________________ > mailop mailing list > [email protected] > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop > _______________________________________________ mailop mailing list [email protected] https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
