Re: [mailop] [Public] trouble delivering to cox.net

2022-10-07 Thread Atro Tossavainen via mailop
> I do see a not
> insignificant amount of mail to invalid recipients so you might want to
> check that you're understanding/processing bounces/deferrals properly.

Koli-Lõks OÜ spamtraps concur, seeing mail from USAA both to typotraps
as well as recycled domains. These are of course no longer undeliverable,
but a health check on the data ought to get rid of them just the same.

-- 
Atro Tossavainen, Founder, Partner
Koli-Lõks OÜ (reg. no. 12815457, VAT ID EE101811635)
Tallinn, Estonia
tel. +372-5883-4269, http://www.koliloks.eu/
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] [Public] trouble delivering to cox.net

2022-10-07 Thread James Hoddinott via mailop
Am guessing this resolved itself for you since I can see that over the past
24 hours over 97% of your traffic was happily accepted. I do see a not
insignificant amount of mail to invalid recipients so you might want to
check that you're understanding/processing bounces/deferrals properly.

On Tue, 4 Oct 2022 at 15:26, Gray, Justin via mailop 
wrote:

> Hey Y’all,
>
>
>
> We’re seeing some deferred responses when sending to @cox.net recipients.
> These mostly look to be happening from our operational member email
> address, usaa.customer.serv...@mailcenter.usaa.com
>
>
>
> We’ve reached out unblock.requ...@cox.net and they were super helpful at
> first with responding, but it’s been over a week and we are still being
> deferred and haven’t seen any response to our follow up questions.
>
>
>
> They mentioned that our messages were being rejected because of a
> spf_soft_fail and a blocklist_mailfrom block, they responded later
> mentioning our address had been removed from their vendor’s mailfrom
> blocklist. I see no issues with our SPF record that would indicate it would
> be soft failing from our sending IPs. Any help would be greatly
> appreciative!
>
>
>
> Sending IPs:
>
> HOST
>
> PUBLIC
>
> prodomx1l.usaa.com
>
> 167.24.115.105
>
> prodomx2l.usaa.com
>
> 167.24.25.85
>
> prodomx3l.usaa.com
>
> 167.24.115.106
>
> prodomx4l.usaa.com
>
> 167.24.25.86
>
> prodomx5l.usaa.com
>
> 167.24.115.107
>
> prodomx6l.usaa.com
>
> 167.24.25.87
>
> prodomx7l.usaa.com
>
> 167.24.115.108
>
> prodomx8l.usaa.com
>
> 167.24.25.88
>
> prodomx9l.usaa.com
>
> 167.24.115.109
>
> prodomx1xdfw.usaa.com
>
> 167.24.97.236
>
> prodomx2xdfw.usaa.com
>
> 167.24.97.237
>
> prodomx3xdfw.usaa.com
>
> 167.24.97.238
>
> prodomx4xdfw.usaa.com
>
> 167.24.97.239
>
>
>
>
>
> Recent MTA Logs:
>
>
>
> 2022-10-04T08:45:09.441425-05:00 prodomx3l sendmail[21279]:
> 294Dbnbu016048: to=<[REMOVED]@cox.net>, delay=00:00:01, xdelay=00:00:01,
> mailer=esmtp, tls_verify=OK, tls_version=TLSv1.2,
> cipher=ECDHE-RSA-AES256-GCM, pri=151884, relay=cxr.mx.a.cloudfilter.net.
> [34.212.80.54], dsn=4.0.0, reply=421 4.2.0  usaa.customer.serv...@mailcenter.usaa.com> sender rejected. Refer to
> Error Codes section at
> https://www.cox.com/residential/support/email-error-codes.html for more
> information. AUP#CXBL, stat=Deferred: 421 4.2.0  usaa.customer.serv...@mailcenter.usaa.com> sender rejected. Ref...ion at
> https://www.cox.com/residential/support/email-error-codes.html for more
> information. AUP#CXBL
>
>
>
> 2022-10-04T08:38:55.637598-05:00 prodomx6l sendmail[2477]: 294DaPSB020129:
> to=<[REMOVED]@cox.net>, delay=00:00:01, xdelay=00:00:01, mailer=esmtp,
> tls_verify=OK, tls_version=TLSv1.2, cipher=ECDHE-RSA-AES256-GCM,
> pri=150775, relay=cxr.mx.a.cloudfilter.net. [52.73.137.222], dsn=4.0.0,
> reply=421 4.2.0 
> sender rejected. Refer to Error Codes section at
> https://www.cox.com/residential/support/email-error-codes.html for more
> information. AUP#CXBL, stat=Deferred: 421 4.2.0  usaa.customer.serv...@mailcenter.usaa.com> sender rejected. Ref...ion at
> https://www.cox.com/residential/support/email-error-codes.html for more
> information. AUP#CXBL
>
>
>
> Thanks,
>
>
>
> *Justin Gray* | Information Security Engineer | Platform Threat Defense -
> SECWEB
>
> Information Security Engineering, Enterprise Security Group, USAA
>
> Cell: (512) 897-7779 | justin.g...@usaa.com
>
>
>
> USAA Classification: Public
> Disclaimer: This email and any attachments are the property of USAA and
> may contain confidential and/or privileged material. If you are not the
> intended recipient, any use, disclosure or copying of this email or any
> attachments is unauthorized. If you received this email in error, please
> immediately notify the sender and delete the email and any attachments from
> your computer.
> ___
> mailop mailing list
> mailop@mailop.org
> https://list.mailop.org/listinfo/mailop
>


-- 
James Hoddinott
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] Autodiscover in MS Outlook for POP/IMAP

2022-10-07 Thread Patrick Ben Koetter via mailop
Allessio,

* Alessio Cecchi via mailop :
> I was trying to configure an email account with MS Outlook via Autodiscover
> (IMAP and SMTP), but it seems to not be working. The account is hosted on my
> personal email server, the Autoconfig has no such problems.
> 
> I performed some tests with other email providers, for example with a
> standard email account hosted at OVH. During the configuration Outlook set
> "ssl0.ovh.net" as the IMAP server.
> 
> OVH domains have an Autodiscover record in the DNS zone, but Outlook will
> correctly configure an account even if I remove it.
> 
> Does MS Outlook stil support Autodiscover for all email providers?

it seems to me Microsoft removed support for Autodiscover SMTP / POP / IMAP
discovery when they updated Autodiscover and also changed the output format
from XML to JSON.

I write "seems" because I'd tried to verify that when I mailed with someone at
Microsoft half-officially, but unfortunately I wasn't able to get a concluding
answer.

That's unfortunate because we had wanted to implement the recent incarnation
of Autodiscover into automx, which to my current knowledge only supports any
client that uses autoconfig and Autodiscover for MS Outlook < 2016 at this
time.

p@rick

-- 
[*] sys4 AG

https://sys4.de, +49 (89) 30 90 46 64
Schleißheimer Straße 26/MG,80333 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief
Aufsichtsratsvorsitzender: Florian Kirstein

___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop