Re: [mailop] Is there a contact for ono.com
Well then, that would explain why we've been receiving connection failures. Thanks! On Fri, Jul 17, 2020 at 1:23 PM Al Iverson via mailop wrote: > Oh yeah, I forgot that I blogged about this back in October: > https://www.spamresource.com/2019/10/dead-email-domain-onocom.html > > Al > > On Fri, Jul 17, 2020 at 11:21 AM Daniel Baqueiro via mailop > wrote: > > > > Ono closed their email service on September 30, 2019 as per their > website: https://www.vodafone.es/c/conocenos/cierre-ono/ > > > > Daniel Baqueiro > > Manager, Messaging Deliverability | GROUPON > > daniel.baque...@groupon.com > > > > > > > > On Wed, Jul 15, 2020 at 9:52 PM Oreva Akpolo via mailop < > mailop@mailop.org> wrote: > >> > >> We've been experiencing connection issues sending to ono.com. > Specifically, all mails to that domain are deferring with the following > response: > >> > >> connect to mx.ono.com[62.42.230.22]:25: Connection timed out > >> > >> Does anyone know a contact there I can reach out to? Or has anyone had > success sending to that domain? > >> > >> Thanks > >> ___ > >> mailop mailing list > >> 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 > > > > -- > Al Iverson // Wombatmail // Chicago > Song a day! https://www.wombatmail.com > Deliverability! https://spamresource.com > And DNS Tools too! https://xnnd.com > > ___ > mailop mailing list > 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
[mailop] CutWail infections growing again, all China based..
While most of these are probably already stopped, via various RBL's and rulesets common to most spam protection, it is worth posting.. Seeing the infection spike again, but strangely all from Chinese IP Ranges. Note, for the one provider, it is especially a bad overnight jump. *.adsl-pool.jlccptt.net.cn (The other ones do not have PTR records, so probably never get anywhere, you think the hackers would check if the IP address has a PTR record before even trying to spam/spread) Of course, there is no A record for that domain, and the whois does not have valid contact information. whois jlccptt.net.cn Domain Name: jlccptt.net.cn ROID: 20021209s10021s00014224-cn Domain Status: clientUpdateProhibited Domain Status: clientTransferProhibited Registrant: 吉林省数据通信局 Registrant Contact Email: jl...@mail.jl.cn Sponsoring Registrar: 北京新网数码信息技术有限公司 Name Server: ns.jlccptt.net.cn Name Server: ns2.jljlptt.net.cn Registration Time: 1997-02-19 00:00:00 Expiration Time: 2021-07-01 00:00:00 DNSSEC: unsigned 119.54.0.73 x1 73.0.54.119.adsl-pool.jlccptt.net.cn 119.54.11.3 x2 3.11.54.119.adsl-pool.jlccptt.net.cn 119.54.12.113 x2 113.12.54.119.adsl-pool.jlccptt.net.cn 119.54.13.183 x2 183.13.54.119.adsl-pool.jlccptt.net.cn 119.54.19.244 x2 244.19.54.119.adsl-pool.jlccptt.net.cn 119.54.20.174 x1 174.20.54.119.adsl-pool.jlccptt.net.cn 119.54.23.185 x1 185.23.54.119.adsl-pool.jlccptt.net.cn 119.54.24.198 x2 198.24.54.119.adsl-pool.jlccptt.net.cn 119.54.24.2 x1 2.24.54.119.adsl-pool.jlccptt.net.cn 119.54.24.233 x1 233.24.54.119.adsl-pool.jlccptt.net.cn 119.54.25.128 x1 128.25.54.119.adsl-pool.jlccptt.net.cn 119.54.27.124 x1 124.27.54.119.adsl-pool.jlccptt.net.cn 119.54.27.44x2 44.27.54.119.adsl-pool.jlccptt.net.cn 119.54.28.55x1 55.28.54.119.adsl-pool.jlccptt.net.cn 119.54.28.93x2 93.28.54.119.adsl-pool.jlccptt.net.cn 119.54.31.17x1 17.31.54.119.adsl-pool.jlccptt.net.cn 119.54.31.180 x1 180.31.54.119.adsl-pool.jlccptt.net.cn 119.54.31.198 x7 198.31.54.119.adsl-pool.jlccptt.net.cn 119.54.32.135 x2 135.32.54.119.adsl-pool.jlccptt.net.cn 119.54.32.201 x2 201.32.54.119.adsl-pool.jlccptt.net.cn 119.54.35.105 x2 105.35.54.119.adsl-pool.jlccptt.net.cn 119.54.37.58x1 58.37.54.119.adsl-pool.jlccptt.net.cn 119.54.38.117 x1 117.38.54.119.adsl-pool.jlccptt.net.cn 119.54.38.246 x1 246.38.54.119.adsl-pool.jlccptt.net.cn 119.54.39.193 x1 193.39.54.119.adsl-pool.jlccptt.net.cn 119.54.39.56x1 56.39.54.119.adsl-pool.jlccptt.net.cn 119.54.4.7 x2 7.4.54.119.adsl-pool.jlccptt.net.cn 119.54.40.179 x2 179.40.54.119.adsl-pool.jlccptt.net.cn 119.54.40.86x1 86.40.54.119.adsl-pool.jlccptt.net.cn 119.54.41.44x1 44.41.54.119.adsl-pool.jlccptt.net.cn 119.54.42.50x2 50.42.54.119.adsl-pool.jlccptt.net.cn 119.54.43.17x1 17.43.54.119.adsl-pool.jlccptt.net.cn 119.54.43.230 x3 230.43.54.119.adsl-pool.jlccptt.net.cn 119.54.46.15x1 15.46.54.119.adsl-pool.jlccptt.net.cn 119.54.46.87x1 87.46.54.119.adsl-pool.jlccptt.net.cn 119.54.47.187 x1 187.47.54.119.adsl-pool.jlccptt.net.cn 119.54.47.198 x1 198.47.54.119.adsl-pool.jlccptt.net.cn 119.54.47.243 x2 243.47.54.119.adsl-pool.jlccptt.net.cn 119.54.5.22 x1 22.5.54.119.adsl-pool.jlccptt.net.cn 119.54.6.220x3 220.6.54.119.adsl-pool.jlccptt.net.cn 119.54.8.10 x1 10.8.54.119.adsl-pool.jlccptt.net.cn 119.54.9.206x1 206.9.54.119.adsl-pool.jlccptt.net.cn 119.54.9.47 x2 47.9.54.119.adsl-pool.jlccptt.net.cn 119.55.136.88 x1 88.136.55.119.adsl-pool.jlccptt.net.cn 119.55.139.9x2 9.139.55.119.adsl-pool.jlccptt.net.cn 119.55.224.159 x2 159.224.55.119.adsl-pool.jlccptt.net.cn 119.55.224.220 x1 220.224.55.119.adsl-pool.jlccptt.net.cn 119.55.225.160 x1 160.225.55.119.adsl-pool.jlccptt.net.cn 119.55.226.41 x2 41.226.55.119.adsl-pool.jlccptt.net.cn 119.55.227.213 x1 213.227.55.119.adsl-pool.jlccptt.net.cn 119.55.255.147 x1 147.255.55.119.adsl-pool.jlccptt.net.cn 119.55.255.19 x1 19.255.55.119.adsl-pool.jlccptt.net.cn 119.55.255.217 x1 217.255.55.119.adsl-pool.jlccptt.net.cn 122.140.115.121 x1 121.115.140.122.adsl-pool.jlccptt.net.cn 122.140.115.13 x1 13.115.140.122.adsl-pool.jlccptt.net.cn 122.140.115.194 x1 194.115.140.122.adsl-pool.jlccptt.net.cn 122.140.234.195 x1 195.234.140.122.adsl-pool.jlccptt.net.cn 122.140.234.229 x1 229.234.140.122.adsl-pool.jlccptt.net.cn 122.140.68.109 x1 109.68.140.122.adsl-pool.jlccptt.net.cn 122.140.68.151 x2 151.68.140.122.adsl-pool.jlccptt.net.cn 122.140.70.30 x2 30.70.140.122.adsl-pool.jlccptt.net.cn 122.140.70.78 x2 78.70.140.122.adsl-pool.jlccptt.net.cn 122.141.157.158 x1 158.157.141.122.adsl-pool.jlccptt.net.cn 122.143.218.117 x3
Re: [mailop] DKIM Line Wrapping, Yahoo..
In article <3ccfb8d2-f004-1769-27e0-745dfa4ad...@linuxmagic.com> you write: >Hey Yahoo, > >You still haven't addressed line wrapping your DKIM lines.. > >While 540 characters in a header probably won't break most systems, it >would be more internet friendly to wrap them at a more reasonable >amount, makes it a lot easier for those who want to copy/paste/print >headers from your emails.. The SMTP mail spec says that the line length limit is for all lines in a mail message is 998 characters. I can't get very upset about standard compliant mail headers, particularly ones that only mail nerds are going to pay attention to. R's, John ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
Re: [mailop] host mx.tiscali.co.uk[62.24.139.42] said: 453 4.1.1 wJGljsu8zj2dp Recipient Lookup Failed (TT513)
Never seen it but isn’t that a case of recipient mailbox incorrect/no longer active? From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Stefan Bauer via mailop Sent: Friday, July 17, 2020 1:08 AM To: mailop Subject: [mailop] host mx.tiscali.co.uk[62.24.139.42] said: 453 4.1.1 wJGljsu8zj2dp Recipient Lookup Failed (TT513) Hi, smtp Jul 17 07:50:52 mx2 postfix/smtp[31049]: 51CBC5EBE3: to=mailto:john@tiscali.co.uk> >, relay=mx.tiscali.co.uk[62.24.139.42]:25, delay=9509, delays=9505/3/0.35/1.2, dsn=4.1.1, status=deferred (host mx.tiscali.co.uk[62.24.139.42] said: 453 4.1.1 wJGljsu8zj2dp Recipient Lookup Failed (TT513) (in reply to RCPT TO command)) According to the reply tiscali gives, they can not lookup the recipient. Anyone seen TT513? Thanks. Stefan ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
Re: [mailop] Is there a contact for ono.com
Oh yeah, I forgot that I blogged about this back in October: https://www.spamresource.com/2019/10/dead-email-domain-onocom.html Al On Fri, Jul 17, 2020 at 11:21 AM Daniel Baqueiro via mailop wrote: > > Ono closed their email service on September 30, 2019 as per their website: > https://www.vodafone.es/c/conocenos/cierre-ono/ > > Daniel Baqueiro > Manager, Messaging Deliverability | GROUPON > daniel.baque...@groupon.com > > > > On Wed, Jul 15, 2020 at 9:52 PM Oreva Akpolo via mailop > wrote: >> >> We've been experiencing connection issues sending to ono.com. Specifically, >> all mails to that domain are deferring with the following response: >> >> connect to mx.ono.com[62.42.230.22]:25: Connection timed out >> >> Does anyone know a contact there I can reach out to? Or has anyone had >> success sending to that domain? >> >> Thanks >> ___ >> mailop mailing list >> 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 -- Al Iverson // Wombatmail // Chicago Song a day! https://www.wombatmail.com Deliverability! https://spamresource.com And DNS Tools too! https://xnnd.com ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
Re: [mailop] Is there a contact for ono.com
Ono closed their email service on September 30, 2019 as per their website: https://www.vodafone.es/c/conocenos/cierre-ono/ Daniel Baqueiro Manager, Messaging Deliverability | GROUPON daniel.baque...@groupon.com On Wed, Jul 15, 2020 at 9:52 PM Oreva Akpolo via mailop wrote: > We've been experiencing connection issues sending to ono.com. > Specifically, all mails to that domain are deferring with the following > response: > > connect to mx.ono.com[62.42.230.22]:25: Connection timed out > > Does anyone know a contact there I can reach out to? Or has anyone had > success sending to that domain? > > Thanks > ___ > mailop mailing list > 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
[mailop] DKIM Line Wrapping, Yahoo..
Hey Yahoo, You still haven't addressed line wrapping your DKIM lines.. While 540 characters in a header probably won't break most systems, it would be more internet friendly to wrap them at a more reasonable amount, makes it a lot easier for those who want to copy/paste/print headers from your emails.. Just a friendly nudge, and reminder to others.. consider Best Practices and not only RFC compliance, and think of others .. Now, going back to collecting that $8M pounds this poor old dying widow wants to leave me... -- "Catch the Magic of Linux..." Michael Peddemors, President/CEO LinuxMagic Inc. Visit us at http://www.linuxmagic.com @linuxmagic A Wizard IT Company - For More Info http://www.wizard.ca "LinuxMagic" a Registered TradeMark of Wizard Tower TechnoServices Ltd. 604-682-0300 Beautiful British Columbia, Canada This email and any electronic data contained are confidential and intended solely for the use of the individual or entity to which they are addressed. Please note that any views or opinions presented in this email are solely those of the author and are not intended to represent those of the company. ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
[mailop] host mx.tiscali.co.uk[62.24.139.42] said: 453 4.1.1 wJGljsu8zj2dp Recipient Lookup Failed (TT513)
Hi, smtp Jul 17 07:50:52 mx2 postfix/smtp[31049]: 51CBC5EBE3: to=, relay=mx.tiscali.co.uk[62.24.139.42]:25, delay=9509, delays=9505/3/0.35/1.2, dsn=4.1.1, status=deferred (host mx.tiscali.co.uk[62.24.139.42] said: 453 4.1.1 wJGljsu8zj2dp Recipient Lookup Failed (TT513) (in reply to RCPT TO command)) According to the reply tiscali gives, they can not lookup the recipient. Anyone seen TT513? Thanks. Stefan ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
