Re: [mailop] Gmail deferrals resolved by transit encryption

2023-11-17 Thread Frank Bulk via mailop
We've been having delivery issues to gmail since November 15 at 12:17 pm 
(Central).  But there's still lots of email going through, too.

Here's an example from our mail server's logs:

Failed  rr=Site gmail.com (2607:f8b0:4001:c5a::1a) said after data sent: 
550 5.7.1  https://support.google.com/mail/?p=NotAuthorizedError 
75-20020a6b144e00b007a2a17ef77bsi3551757iou.146 - gsmtp 550-5.7.1 
[2607:fe28:0:4000::10] The IP you're using to send mail is not\n550-5.7.1 
authorized to send email directly to our servers. Please use the 
SMTP\n550-5.7.1 relay at your service provider instead. Learn"

What's interesting is that all the failure come from our email server's IPv6 
address, which has been in place for 5+ years and matching FQDN and PTR.

Frank 

-Original Message-
From: mailop  On Behalf Of Omar Thameen via mailop
Sent: Wednesday, November 15, 2023 11:50 AM
To: mailop@mailop.org
Subject: [mailop] Gmail deferrals resolved by transit encryption

This might be old news, but we started seeing delivery deferrals
to Gmail starting Nov 13 around 4pm EST.  It started at about 10%
of deliveries, mostly affecting larger accounts, and all having IP
and domain reputations in Google Postmaster Tools of high and medium.
Messages were delivered on subsequent retries.

Last night, when the deferrals increased to 25-30%, we deployed TLS
for deliveries, and the deferrals immediately went to zero.

Hope that helps others.

Omar
-- 
BIGLIST.com
___
mailop mailing list
mailop@mailop.org
https://link.edgepilot.com/s/38670079/wgcznbaNmE6bvgR0r99gWA?u=https://list.mailop.org/listinfo/mailop


Links contained in this email have been replaced. If you click on a link in the 
email above, the link will be analyzed for known threats. If a known threat is 
found, you will not be able to proceed to the destination. If suspicious 
content is detected, you will see a warning.

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


Re: [mailop] Anyone else seeing email backed up to Microsoft -- only IPv6

2022-10-25 Thread Frank Bulk via mailop
One tweet thread here on the topic:
https://twitter.com/dergrobi/status/1585016960785723392

Frank

-Original Message-
From: mailop  On Behalf Of mailop@mailop.org
Sent: Tuesday, October 25, 2022 5:17 PM
To: mailop@mailop.org
Subject: Re: [mailop] Anyone else seeing email backed up to Microsoft -- only 
IPv6

I cleared out my backlog earlier this afternoon by temporarily directing those 
three domains plus msn.com to one of the IPv4 addresses in their MX record, but 
after removing that override, email is backing up again. =(

Frank

-Original Message-
From: mailop  On Behalf Of Michael Peddemors via 
mailop
Sent: Tuesday, October 25, 2022 3:13 PM
To: mailop@mailop.org
Subject: Re: [mailop] Anyone else seeing email backed up to Microsoft -- only 
IPv6

On 2022-10-25 09:56, Andreas S. Kerber via mailop wrote:
> Am Tue, Oct 25, 2022 at 09:40:41AM -0500 schrieb Frank Bulk via mailop:
>> We had it last night, too, but this morning seeing it again for hotmail.com,
>> outlook.com, and live.com:
> 
> Confirmed:
> 
> @hotmail.com>, delay=00:00:01, xdelay=00:00:01, mailer=esmtp, 
> pri=41706, relay=hotmail-com.olc.protection.outlook.com. 
> [IPv6:2a01:111:f400:7e8a:0:0:0:33], dsn=4.7.500, reply=451 4.7.500 Server 
> busy. Please try again later from [2a01:111:e400:7e8f::47]. (AS750) 
> [BN7NAM10FT103.eop-nam10.prod.protection.outlook.com]
> 
> Quite a lot of mail queuing up already. Anybody know what's going on over 
> there?
> ___

Probably just finding out how much the spammers like using IPv6 ;)



-- 
"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://list.mailop.org/listinfo/mailop

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

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


Re: [mailop] Anyone else seeing email backed up to Microsoft -- only IPv6

2022-10-25 Thread Frank Bulk via mailop
I cleared out my backlog earlier this afternoon by temporarily directing those 
three domains plus msn.com to one of the IPv4 addresses in their MX record, but 
after removing that override, email is backing up again. =(

Frank

-Original Message-
From: mailop  On Behalf Of Michael Peddemors via 
mailop
Sent: Tuesday, October 25, 2022 3:13 PM
To: mailop@mailop.org
Subject: Re: [mailop] Anyone else seeing email backed up to Microsoft -- only 
IPv6

On 2022-10-25 09:56, Andreas S. Kerber via mailop wrote:
> Am Tue, Oct 25, 2022 at 09:40:41AM -0500 schrieb Frank Bulk via mailop:
>> We had it last night, too, but this morning seeing it again for hotmail.com,
>> outlook.com, and live.com:
> 
> Confirmed:
> 
> @hotmail.com>, delay=00:00:01, xdelay=00:00:01, mailer=esmtp, 
> pri=41706, relay=hotmail-com.olc.protection.outlook.com. 
> [IPv6:2a01:111:f400:7e8a:0:0:0:33], dsn=4.7.500, reply=451 4.7.500 Server 
> busy. Please try again later from [2a01:111:e400:7e8f::47]. (AS750) 
> [BN7NAM10FT103.eop-nam10.prod.protection.outlook.com]
> 
> Quite a lot of mail queuing up already. Anybody know what's going on over 
> there?
> ___

Probably just finding out how much the spammers like using IPv6 ;)



-- 
"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://list.mailop.org/listinfo/mailop

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


Re: [mailop] Anyone else seeing email backed up to Microsoft -- only IPv6

2022-10-25 Thread Frank Bulk via mailop
Benny,

Thanks, but I'm not sure how the Xbox article relates to what we're seeing?

While our email system doesn't allow us to force a certain domain to use IPv4 
(or IPv6), we could force it to deliver to certain IP addresses, which we could 
do to temporarily work around the issue.

Frank

-Original Message-
From: mailop  On Behalf Of Benny Pedersen via mailop
Sent: Tuesday, October 25, 2022 10:25 AM
To: mailop@mailop.org
Subject: Re: [mailop] Anyone else seeing email backed up to Microsoft -- only 
IPv6

Frank Bulk via mailop skrev den 2022-10-25 16:40:

> They're all IPv6 hosts, though it's possibly our MTA prefers that when
> communicating to Microsoft.

https://support.xbox.com/en-US/help/hardware-network/connect-network/ipv6-on-xbox-one

:-)

glibc have ipv6 preferelble /etc/gai.conf can change that to ipv4

all it is that now microsoft finaly open ipv6 in global scopes

https://serverfault.com/questions/1049845/configure-postfix-to-send-via-ipv4-but-receive-using-both-ipv4-ipv6
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

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


[mailop] Anyone else seeing email backed up to Microsoft -- only IPv6

2022-10-25 Thread Frank Bulk via mailop
We had it last night, too, but this morning seeing it again for hotmail.com,
outlook.com, and live.com:

@premieronline.net@hotmail.com  ubad=980379246, ()
Site (hotmail.com/2a01:111:f400:7ea9::33) said: 451 4.7.500 Server busy.
Please try again later from [2a01:111:e400:fc4a::4e]. (AS750)
[SN1NAM02FT0003.eop-nam02.prod.protection.outlook.com]

@premieronline.net@outlook.com
ubad=980379246, () Site (outlook.com/2a01:111:f400:fe59::33) said: 451
4.7.500 Server busy. Please try again later from [2a01:111:e400:fc64::41].
(AS750) [DM6NAM12FT053.eop-nam12.prod.protection.outlook.com]

@mypremieronline.com  @live.com
ubad=980379246, () Site (live.com/2a01:111:f400:7d00::33) said: 451 4.7.500
Server busy. Please try again later from [2a01:111:e400:fc12::48]. (AS750)
[VI1EUR05FT046.eop-eur05.prod.protection.outlook.com]

They're all IPv6 hosts, though it's possibly our MTA prefers that when
communicating to Microsoft.

Frank

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


[mailop] Office 365 issues

2021-04-22 Thread Frank Bulk via mailop
I presume most of you are aware of issues sending to domains hosted with
Office 365.

 

I got my first hint around 8:50 am Central when I received an NDR sending
email to two valid email addresses at the same company (they use Barracuda
Networks for web filtering):

d193123a.ess.barracudanetworks.com

Remote Server returned '554 5.0.0 mailto:christina.r...@sdncommunications.com:550> :550 5.1.1 The
email account that you tried to reach does not exist. Please try 5...)>'

I emailed a third valid email address at that company from Gmail and it
didn't arrive.

 

Then our monitoring system alerted us that email was queuing up on our ISP
email server to a certain Office 365 hosted domain . looking at our email
server outbound queue, there were lots of 

451 4.3.2 Temporary server error. Please try again later ATTR1
[BN8NAM12FT065.eop-nam12.prod.protection.outlook.com])

type messages.

 

Based on our ISP email server logs, the first example was at 8:00 am
Central.

 

Confirmed also here: https://downdetector.com/status/office-365/

 

Frank 

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


Re: [mailop] DNS issues for CloudFilter?

2021-01-11 Thread Frank Bulk via mailop
Looks like it's good now.

Frank 

-Original Message-
From: mailop  On Behalf Of mailop@mailop.org
Sent: Monday, January 11, 2021 11:36 AM
To: mailop@mailop.org
Subject: [mailop] DNS issues for CloudFilter?

Any others seeing DNS issues with CloudFilter (cloudfilter.net)?

I was made aware of this because emails to Mediacom are backing up in our
email server's outbound queue due to lack of DNS resolution of their two MX
records:
root@nagios:/home/fbulk# dig MX mchsi.com +short
10 mcc-east.mx.a.cloudfilter.net.
10 mcc-west.mx.a.cloudfilter.net.
root@nagios:/home/fbulk# dig A mcc-west.mx.a.cloudfilter.net +short
root@nagios:/home/fbulk# dig A mcc-east.mx.a.cloudfilter.net +short
root@nagios:/home/fbulk#

And when I checked cloudfilter.net itself against our internal and some
public DNS resolvers, I'm mostly getting SERVFAIL (see below).

Frank


DNS server: 8.8.8.8 (Google DNS)

; <<>> DiG 9.7.3 <<>> cloudfilter.net @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 3610
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;cloudfilter.net.   IN  A

;; Query time: 770 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Jan 11 11:31:46 2021
;; MSG SIZE  rcvd: 33


DNS server: 8.8.4.4 (Google DNS)

; <<>> DiG 9.7.3 <<>> cloudfilter.net @8.8.4.4
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 40187
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;cloudfilter.net.   IN  A

;; Query time: 836 msec
;; SERVER: 8.8.4.4#53(8.8.4.4)
;; WHEN: Mon Jan 11 11:31:46 2021
;; MSG SIZE  rcvd: 33


DNS server: 208.67.222.222 (OpenDNS)

; <<>> DiG 9.7.3 <<>> cloudfilter.net @208.67.222.222
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8251
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;cloudfilter.net.   IN  A

;; ANSWER SECTION:
cloudfilter.net.0   IN  A   208.83.136.86

;; Query time: 261 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Mon Jan 11 11:31:47 2021
;; MSG SIZE  rcvd: 49


DNS server: 208.67.220.220 (Open DNS)

; <<>> DiG 9.7.3 <<>> cloudfilter.net @208.67.220.220
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51154
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;cloudfilter.net.   IN  A

;; ANSWER SECTION:
cloudfilter.net.0   IN  A   208.83.136.86

;; Query time: 255 msec
;; SERVER: 208.67.220.220#53(208.67.220.220)
;; WHEN: Mon Jan 11 11:31:47 2021
;; MSG SIZE  rcvd: 49


DNS server: 9.9.9.9 (IBM Quad9)

; <<>> DiG 9.7.3 <<>> cloudfilter.net @9.9.9.9
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 9564
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;cloudfilter.net.   IN  A

;; Query time: 21 msec
;; SERVER: 9.9.9.9#53(9.9.9.9)
;; WHEN: Mon Jan 11 11:31:47 2021
;; MSG SIZE  rcvd: 33


DNS server: 2620:fe::fe (IBM Quad 9, secure)

; <<>> DiG 9.7.3 <<>> cloudfilter.net @2620:fe::fe
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 33114
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;cloudfilter.net.   IN  A

;; Query time: 368 msec
;; SERVER: 2620:fe::fe#53(2620:fe::fe)
;; WHEN: Mon Jan 11 11:31:47 2021
;; MSG SIZE  rcvd: 33


DNS server: 2620:fe::10 (IBM Quad 9, insecure)

; <<>> DiG 9.7.3 <<>> cloudfilter.net @2620:fe::10
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 45050
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;cloudfilter.net.   IN  A

;; Query time: 20 msec
;; SERVER: 2620:fe::10#53(2620:fe::10)
;; WHEN: Mon Jan 11 11:31:47 2021
;; MSG SIZE  rcvd: 33


DNS server: 1.1.1.1 (Cloudflare DNS)

; <<>> DiG 9.7.3 <<>> cloudfilter.net @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 61482
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;cloudfilter.net.   IN  A

;; Query time: 11 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Mon Jan 11 11:31:47 2021
;; MSG SIZE  rcvd: 33


DNS server: 1.0.0.1 (Cloudflare DNS)

; <<>> DiG 9.7.3 <<>> 

[mailop] DNS issues for CloudFilter?

2021-01-11 Thread Frank Bulk via mailop
Any others seeing DNS issues with CloudFilter (cloudfilter.net)?

I was made aware of this because emails to Mediacom are backing up in our
email server's outbound queue due to lack of DNS resolution of their two MX
records:
root@nagios:/home/fbulk# dig MX mchsi.com +short
10 mcc-east.mx.a.cloudfilter.net.
10 mcc-west.mx.a.cloudfilter.net.
root@nagios:/home/fbulk# dig A mcc-west.mx.a.cloudfilter.net +short
root@nagios:/home/fbulk# dig A mcc-east.mx.a.cloudfilter.net +short
root@nagios:/home/fbulk#

And when I checked cloudfilter.net itself against our internal and some
public DNS resolvers, I'm mostly getting SERVFAIL (see below).

Frank


DNS server: 8.8.8.8 (Google DNS)

; <<>> DiG 9.7.3 <<>> cloudfilter.net @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 3610
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;cloudfilter.net.   IN  A

;; Query time: 770 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Jan 11 11:31:46 2021
;; MSG SIZE  rcvd: 33


DNS server: 8.8.4.4 (Google DNS)

; <<>> DiG 9.7.3 <<>> cloudfilter.net @8.8.4.4
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 40187
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;cloudfilter.net.   IN  A

;; Query time: 836 msec
;; SERVER: 8.8.4.4#53(8.8.4.4)
;; WHEN: Mon Jan 11 11:31:46 2021
;; MSG SIZE  rcvd: 33


DNS server: 208.67.222.222 (OpenDNS)

; <<>> DiG 9.7.3 <<>> cloudfilter.net @208.67.222.222
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8251
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;cloudfilter.net.   IN  A

;; ANSWER SECTION:
cloudfilter.net.0   IN  A   208.83.136.86

;; Query time: 261 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Mon Jan 11 11:31:47 2021
;; MSG SIZE  rcvd: 49


DNS server: 208.67.220.220 (Open DNS)

; <<>> DiG 9.7.3 <<>> cloudfilter.net @208.67.220.220
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51154
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;cloudfilter.net.   IN  A

;; ANSWER SECTION:
cloudfilter.net.0   IN  A   208.83.136.86

;; Query time: 255 msec
;; SERVER: 208.67.220.220#53(208.67.220.220)
;; WHEN: Mon Jan 11 11:31:47 2021
;; MSG SIZE  rcvd: 49


DNS server: 9.9.9.9 (IBM Quad9)

; <<>> DiG 9.7.3 <<>> cloudfilter.net @9.9.9.9
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 9564
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;cloudfilter.net.   IN  A

;; Query time: 21 msec
;; SERVER: 9.9.9.9#53(9.9.9.9)
;; WHEN: Mon Jan 11 11:31:47 2021
;; MSG SIZE  rcvd: 33


DNS server: 2620:fe::fe (IBM Quad 9, secure)

; <<>> DiG 9.7.3 <<>> cloudfilter.net @2620:fe::fe
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 33114
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;cloudfilter.net.   IN  A

;; Query time: 368 msec
;; SERVER: 2620:fe::fe#53(2620:fe::fe)
;; WHEN: Mon Jan 11 11:31:47 2021
;; MSG SIZE  rcvd: 33


DNS server: 2620:fe::10 (IBM Quad 9, insecure)

; <<>> DiG 9.7.3 <<>> cloudfilter.net @2620:fe::10
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 45050
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;cloudfilter.net.   IN  A

;; Query time: 20 msec
;; SERVER: 2620:fe::10#53(2620:fe::10)
;; WHEN: Mon Jan 11 11:31:47 2021
;; MSG SIZE  rcvd: 33


DNS server: 1.1.1.1 (Cloudflare DNS)

; <<>> DiG 9.7.3 <<>> cloudfilter.net @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 61482
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;cloudfilter.net.   IN  A

;; Query time: 11 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Mon Jan 11 11:31:47 2021
;; MSG SIZE  rcvd: 33


DNS server: 1.0.0.1 (Cloudflare DNS)

; <<>> DiG 9.7.3 <<>> cloudfilter.net @1.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 38136
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

Re: [mailop] SPF notification question

2020-06-05 Thread Frank Bulk via mailop
I have an automated system in place for our customers, partners, and friends 
domains to catch that and then I make them aware.  There’s currently about 108 
on my list that are broken. 

 

I’m not going to put a spotlight on everyone, but here’s a list of .edu domains:

ashland.edu

dmu.edu

sdstate.edu

usd.edu

If anyone has some good connections to those schools, please send a note of 
encouragement. 

 

Success rate is about 5 to 10%.  If I get a response from someone in the first 
few days after my first note then it’s usually 80% chance it will be resolved 
in two weeks. There’s some who think that the problem is our spam filtering 
server and lot of confusion on who/where to send my note – I usually encourage 
their IT consultant/department or their email or DNS resource.

 

Frank 

 

From: mailop  On Behalf Of Liam Fisher via mailop
Sent: Thursday, June 04, 2020 9:05 AM
To: mailop@mailop.org
Subject: [mailop] SPF notification question

 

Quick question to the hive mind about SPF.

 

 

What do you usually do for domains that have broken SPF records?  I mean the 
ones affecting your inbound to local delivery.

 

Do you notify the sender and what's the usual process?

 

 

 

___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


Re: [mailop] Strange information upon SMTP connection to icloud email server

2020-06-05 Thread Frank Bulk via mailop
Fair question -- none of our infrastructure uses 10.15.194.x. In any offline 
thread someone else believes this is a Dell device (based on the "EMC").

Frank 

-Original Message-
From: mailop  On Behalf Of Brandon Applegate via 
mailop
Sent: Thursday, June 04, 2020 7:50 PM
To: mailop@mailop.org
Subject: Re: [mailop] Strange information upon SMTP connection to icloud email 
server

On Thu, Jun 4, 2020 at 8:20 PM Frank Bulk via mailop  wrote:
>
> I was reviewing the details on an email deliverability error and I saw the
> following recorded by our "check script" when connecting to an icloud.com MX
> record:
> ===
> Trying 17.57.154.7...
>
> Connected to 17.57.154.7.
>
> Escape character is '^]'.
>
> 2020 Jun  4 18:20:48 10.15.194.199 message repeated 82 times: [ BCMSDK -
> unit 0 MMU subblock 12   reg EMC_ERROR_1 field
> EMC_CSDB_2_UPPER_BUFFER_UNCORRECTED_ERROR(value = 0x800) has  MMU parity
> error]
> 2020 Jun  4 18:20:49 10.15.194.199 BCMSDK - unit 0 MMU subblock 12   reg
> EMC_ERROR_1 field EMC_CSDB_2_UPPER_BUFFER_UNCORRECTED_ERROR(value =
> 0x800) has MMU parity error
>
>
> Timeout connecting to '17.57.154.7'
> connecting to an icloud.com MX record
> ===
>

Wow, looks like maybe a NIC error message (I’m guessing this based on
the “BCMSDK” - Broadcom SDK ?) “bled over” into the smtp connection ?
How does that even happen ?  Some sort of TCP offload on the host tied
in a knot ?

Dumb question - forgive me in advance - this wouldn't be from
something on your side (i.e. your monitoring box) ?  I guess if
10.15.194.199 isn't one of your IP's internally the answer would be
no...

___
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] Strange information upon SMTP connection to icloud email server

2020-06-04 Thread Frank Bulk via mailop
I was reviewing the details on an email deliverability error and I saw the
following recorded by our "check script" when connecting to an icloud.com MX
record:
===
Trying 17.57.154.7...

Connected to 17.57.154.7.

Escape character is '^]'.

2020 Jun  4 18:20:48 10.15.194.199 message repeated 82 times: [ BCMSDK -
unit 0 MMU subblock 12   reg EMC_ERROR_1 field
EMC_CSDB_2_UPPER_BUFFER_UNCORRECTED_ERROR(value = 0x800) has  MMU parity
error]
2020 Jun  4 18:20:49 10.15.194.199 BCMSDK - unit 0 MMU subblock 12   reg
EMC_ERROR_1 field EMC_CSDB_2_UPPER_BUFFER_UNCORRECTED_ERROR(value =
0x800) has MMU parity error


Timeout connecting to '17.57.154.7'
connecting to an icloud.com MX record
===

Frank


___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


Re: [mailop] Issues with Microsoft

2020-04-21 Thread Frank Bulk via mailop
Another interesting one today:

 

Site hotmail.com (104.47.58.161) said after data sent: 452 4.3.1
Insufficient system resources (UsedVersionBuckets[D:\queue])
[BN8NAM11HT069.eop-nam11.prod.protection.outlook.com]
[BN8NAM11FT048.eop-nam11.prod.protection.outlook.com]

 

Frank

 

From: mailop  On Behalf Of Frank Bulk via mailop
Sent: Monday, April 20, 2020 3:18 PM
To: 'Evelyn Poon' ; mailop@mailop.org
Subject: Re: [mailop] Issues with Microsoft

 

Yes, definitely seeing issues today . only saw hotmail.com, not any other
Microsoft domains.

 

Site hotmail.com (104.47.56.161) said after data sent: 452 4.3.1
Insufficient system resources (TSTE)
[CO1NAM11HT140.eop-nam11.prod.protection.outlook.com]
[CO1NAM11FT005.eop-nam11.prod.protection.outlook.com]

Site hotmail.com (104.47.58.33) said after data sent: 450 4.7.3 Organization
queue quota exceeded. [DM6NAM10HT131.eop-nam10.prod.protection.outlook.com]
[DM6NAM10FT043.eop-nam10.prod.protection.outlook.com]

Site hotmail.com (104.47.70.33) said after data sent: 450 4.7.3 Organization
queue quota exceeded. [BN7NAM10HT207.eop-nam10.prod.protection.outlook.com]
[BN7NAM10FT054.eop-nam10.prod.protection.outlook.com]

Site hotmail.com (104.47.70.33) said after data sent: 450 4.7.3 Organization
queue quota exceeded. [BN7NAM10HT207.eop-nam10.prod.protection.outlook.com]
[BN7NAM10FT019.eop-nam10.prod.protection.outlook.com]

Site hotmail.com (104.47.70.33) said after data sent: 450 4.7.3 Organization
queue quota exceeded. [BN7NAM10HT222.eop-nam10.prod.protection.outlook.com]
[BN7NAM10FT025.eop-nam10.prod.protection.outlook.com]

Site hotmail.com (104.47.70.33) said after data sent: 450 4.7.3 Organization
queue quota exceeded. [BN7NAM10HT238.eop-nam10.prod.protection.outlook.com]
[BN7NAM10FT065.eop-nam10.prod.protection.outlook.com]

Site hotmail.com (104.47.56.161) said after data sent: 450 4.7.3
Organization queue quota exceeded.
[CO1NAM11HT128.eop-nam11.prod.protection.outlook.com]
[CO1NAM11FT022.eop-nam11.prod.protection.outlook.com]

 

Frank 

 

From: mailop mailto:mailop-boun...@mailop.org> >
On Behalf Of Evelyn Poon via mailop
Sent: Monday, April 20, 2020 2:22 PM
To: mailop@mailop.org <mailto:mailop@mailop.org> 
Subject: [mailop] Issues with Microsoft

 

Hi,

 

Is anyone else seeing a high volume of soft bounces at Microsoft with the
following error codes?

451 4.7.0 Temporary server error. Please try again later
452 4.3.1 Insufficient system resources
450 4.7.3 Organization queue quota exceeded.
451 4.4.25 Message failed to be replicated: No healthy secondary server
available to accept replica at this time.

 

Thanks,

Evelyn Poon

 

Director of Deliverability and Compliance

 

 

  _  

 

___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


Re: [mailop] Issues with Microsoft

2020-04-20 Thread Frank Bulk via mailop
Yes, definitely seeing issues today . only saw hotmail.com, not any other
Microsoft domains.

 

Site hotmail.com (104.47.56.161) said after data sent: 452 4.3.1
Insufficient system resources (TSTE)
[CO1NAM11HT140.eop-nam11.prod.protection.outlook.com]
[CO1NAM11FT005.eop-nam11.prod.protection.outlook.com]

Site hotmail.com (104.47.58.33) said after data sent: 450 4.7.3 Organization
queue quota exceeded. [DM6NAM10HT131.eop-nam10.prod.protection.outlook.com]
[DM6NAM10FT043.eop-nam10.prod.protection.outlook.com]

Site hotmail.com (104.47.70.33) said after data sent: 450 4.7.3 Organization
queue quota exceeded. [BN7NAM10HT207.eop-nam10.prod.protection.outlook.com]
[BN7NAM10FT054.eop-nam10.prod.protection.outlook.com]

Site hotmail.com (104.47.70.33) said after data sent: 450 4.7.3 Organization
queue quota exceeded. [BN7NAM10HT207.eop-nam10.prod.protection.outlook.com]
[BN7NAM10FT019.eop-nam10.prod.protection.outlook.com]

Site hotmail.com (104.47.70.33) said after data sent: 450 4.7.3 Organization
queue quota exceeded. [BN7NAM10HT222.eop-nam10.prod.protection.outlook.com]
[BN7NAM10FT025.eop-nam10.prod.protection.outlook.com]

Site hotmail.com (104.47.70.33) said after data sent: 450 4.7.3 Organization
queue quota exceeded. [BN7NAM10HT238.eop-nam10.prod.protection.outlook.com]
[BN7NAM10FT065.eop-nam10.prod.protection.outlook.com]

Site hotmail.com (104.47.56.161) said after data sent: 450 4.7.3
Organization queue quota exceeded.
[CO1NAM11HT128.eop-nam11.prod.protection.outlook.com]
[CO1NAM11FT022.eop-nam11.prod.protection.outlook.com]

 

Frank 

 

From: mailop  On Behalf Of Evelyn Poon via mailop
Sent: Monday, April 20, 2020 2:22 PM
To: mailop@mailop.org
Subject: [mailop] Issues with Microsoft

 

Hi,

 

Is anyone else seeing a high volume of soft bounces at Microsoft with the
following error codes?

451 4.7.0 Temporary server error. Please try again later
452 4.3.1 Insufficient system resources
450 4.7.3 Organization queue quota exceeded.
451 4.4.25 Message failed to be replicated: No healthy secondary server
available to accept replica at this time.





Thanks,

Evelyn Poon





Director of Deliverability and Compliance

 

 

  _  

 

___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


[mailop] Saw some Microsoft resource issues this morning

2020-03-26 Thread Frank Bulk via mailop
Saw some Microsoft resource issues this morning .. here's the de-duped error
messages:

Site hotmail.com (104.47.55.33) said after data sent: 452 4.3.1 Insufficient
system resources (PendingCommits[Large])
[MW2NAM10HT119.eop-nam10.prod.protection.outlook.com]
[MW2NAM10FT040.eop-nam10.prod.protection.outlook.com]
Site hotmail.com (104.47.55.33) said after data sent: 452 4.3.1 Insufficient
system resources (PendingCommits[Large])
[MW2NAM10HT210.eop-nam10.prod.protection.outlook.com]
[MW2NAM10FT033.eop-nam10.prod.protection.outlook.com]
Site hotmail.com (104.47.55.33) said after data sent: 452 4.3.1 Insufficient
system resources (TSTE)
[MW2NAM10HT033.eop-nam10.prod.protection.outlook.com]
[MW2NAM10FT010.eop-nam10.prod.protection.outlook.com]

Frank 



___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


[mailop] Contact at networksolutions.com

2020-01-16 Thread Frank Bulk via mailop
We and our customers occasionally get email from netoworksolutions.com as it
pertains to their services.  I noticed that their domain name has two
different kinds of SPF errors -- anyone know anyone in their mail or DNS
operations that can effect a change?

https://tools.wordtothewise.com/spf/check/networksolutions.com
https://dmarcian.com/spf-survey/?domain=networksolutions.com

Frank 


___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


Re: [mailop] [FEEDBACK] Approach to dealing with List Washing services, industry feedback..

2020-01-16 Thread Frank Bulk via mailop
We have a professional services customer that collects email addresses at home 
and garden shows. As you can imagine, there’s lots of messy handwriting and 
some people are likely writing down a fake email address so they can get a free 
something-or-other.  We’ve told our customer the same thing – don’t wait until 
having visited all 10+ home and garden shows, send them a “welcome” email right 
away, and if comes back bad, remove their email address from your lists.

 

Frank

 

From: mailop  On Behalf Of Luke via mailop
Sent: Thursday, January 16, 2020 11:36 AM
To: Jaroslaw Rafa 
Cc: mailop@mailop.org; Jesse Thompson 
Subject: Re: [mailop] [FEEDBACK] Approach to dealing with List Washing 
services, industry feedback..

 

I actually work for a company that sells a validation tool as a part of our 
platform and I'm still pretty confused by the appeal of such a thing. As Mr. 
Wise said before, "bounce processing!"

 

I want to believe a legitimate use case for validation exists but if you 
collect addresses in an appropriate manner, monitor engagement, pay attention 
to bounces and suppress addresses accordingly, there is no need to 
programmatically validate/invalidate address. Ever. 

 

Sometimes I hear about this scenario where someone collected the addresses 
appropriately, but it has been years since they've sent to them and they need 
to ensure they are valid before they try to re-engage them. So people think it 
makes sense to run the list through a validation service to eliminate the 
obviously bad addresses before sending to the rest. Or, you could just send to 
this list slowly over some period of time and let the bad ones bounce and let 
the good ones deliver. SMTP has build in address validation. And its free :)

 

Luke

 

On Thu, Jan 16, 2020 at 9:54 AM Jaroslaw Rafa via mailop mailto:mailop@mailop.org> > wrote:

Dnia 16.01.2020 o godz. 15:44:46 Jesse Thompson via mailop pisze:
> 
> Another factor that complicates things is that users are afraid to 
> unsubscribe (to send the signal directly to the marketer)
> 1) when the message was obviously unsolicited
> 2) because they're constantly told not to click on links within spam 
> messages

Myself, I never unsubscribe from any mass mailings if I didn't previously
knowingly and willingly subscribe to them (and I very rarely subscribe to
any). I guess that's pretty reasonable approach.

If I didn't subscribe and someone is sending me mass mailings nevertheless,
these people do not qualify to send them any "direct signals", because they
will most likely ignore it (or even treat the "unsubscribe" operation as a
confirmation that I actually read their messages, so they will put me on
more mailing lists). I didn't subscribe to their mailings, why should I ask
them to unsubscribe me? The only thing to be done about such messages is to
delete them or block the senders if they send too much.
-- 
Regards,
   Jaroslaw Rafa
   r...@rafa.eu.org  
--
"In a million years, when kids go to school, they're gonna know: once there
was a Hushpuppy, and she lived with her daddy in the Bathtub."

___
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] Dish webmail

2019-07-29 Thread Frank Bulk via mailop
We'll see if Dish renews their webmail certs by Wednesday night!

webmail.dishmail.netSSL_CERT CRITICAL
webmail.dishmail.net: certificate will expire on Jul 31 12:00:00 2019 GMT
login.dishmail.net  SSL_CERT CRITICAL
login.dishmail.net: certificate will expire on Jul 31 12:00:00 2019 GMT

Frank


___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


[mailop] Emailed notifications from facebook failing SPF checks

2019-07-25 Thread Frank Bulk via mailop
Our spam filtering vendor recently upgraded their platform and has improved
their SPF checking feature set.  We can now tag on Permanent Failures, which
we couldn't do before.

We also noticed that email from notificat...@facebookmail.com was having a
Soft Failure.  Turns out that facebook issues "mx-out.facebook.com" on the
HELO/EHLO, and that FQDN's SPF record doesn't include all the items that are
listed in facebookmail.com's SPF record.  

root@nagios:/tmp# dig TXT mx-out.facebook.com +short | grep spf
"v=spf1 a ~all"
root@nagios:/tmp# dig TXT facebookmail.com +short | grep spf
"v=spf1 ip4:66.220.144.128/25 ip4:66.220.155.0/24 ip4:66.220.157.0/25
ip4:69.63.178.128/25 ip4:69.63.181.0/24 ip4:69.63.184.0/25" "
ip4:69.171.232.0/24 ip4:69.171.244.0/23 -all"
root@nagios:/tmp#

Best I can understand from the IETF RFC, it is appropriate to check the
HELO: https://tools.ietf.org/html/rfc7208#section-2.3

Anyone from fb on this list, or is there someone who knows the email or DNS
folk at facebook and can forward this to them for consideration?

Regards,

Frank 


___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop