It's cleaned up now -- maybe it automatically happened after the aforementioned
quarantine?
Thanks,
Frank
-Original Message-
From: mailop On Behalf Of Bill Cole
Sent: Friday, April 26, 2019 3:27 PM
To: mailop@mailop.org
Subject: Re: [mailop] Looking for GoDaddy email/DNS contact
On 2
We had a customer not renew their domain name (IRONINGENUITY.COM), but upon
expiration their MX records were left still pointing to us. We're looking
for a way for that to get cleaned up (ideally null MX record, second best is
to reset to GoDaddy's default MX record for such domains), but since th
FYI:
https://www.mediapost.com/publications/article/331556/mailchimps-mandrill-ap
p-suffers-service-outage-c.html
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
Looks to be a DNSsec issue ... please correct me if I have that wrong.
Frank
-Original Message-
From: Frank Bulk (frnk...@iname.com)
Sent: Thursday, May 3, 2018 8:28 AM
To: 'mailop@mailop.org' (mailop@mailop.org)
Subject: No MX records for mail.mil
I haven't investigated this thorough
I haven't investigated this thoroughly, but it seems like mail.mil is not
returning MX records from certain DNS resolvers.
Frank
DNS server: 1.1.1.1 (Cloudflare DNS)
; <<>> DiG 9.7.3 <<>> MX mail.mil @1.1.1.1
;; global options: +cmd
;; Got answer:
;;
Thanks. Most of them are "AS843". I wish I knew what that meant. Poking
through those pending outbound messages in our queues, nothing seems sneaky or
suspicious about them. Hopefully they will eventually deliver.
Frank
-Original Message-
From: Benjamin BILLON
Sent: Thursday, Febr
Anyone else see email queued up to outlook.com and Hotmail.com domains? It
started around 5:30 pm U.S. Central and we're still seeing some issues.
Here are some just some status logs from our email servers:
@outlook.com Site outlook.com (104.47.38.33) said after data sent:
452 4.3.1 Insufficie
Starting just after 9 pm (U.S. Central) we started seeing a little:
ubad=14039790, Site (hotmail.com/104.47.10.33) said: 451 4.7.500
Server busy. Please try again later from [96.31.0.20]. (AS761)
[DB5EUR03FT004.eop-EUR03.prod.protection.outlook.com]
ubad=14039790, Site (hotmail.com/
Our outbound queues are draining now, down 37% from 10:56 pm U.S. Central,
where it was the highest of the last 16 hours.
Frank
-Original Message-
From: Frank Bulk [mailto:frnk...@iname.com]
Sent: Monday, September 25, 2017 11:59 AM
To: Anne P. Mitchell Esq. ; mailop@mailop.org
Subject:
Our spam filtering vendor also saw it in their outbound queues:
https://edgewavecom.statuspage.io/
Frank
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Brotman, Alexander
Sent: Wednesday, September 20, 2017 2:18 PM
To: mailop@mailop.org
Subject: Re: [mailop] Comcast timeouts
We saw email delivery delays to cox.net today, between 12:58 and 7:32 pm
(U.S. Central). Our email server logged the following for each of them:
Site cox.net (68.6.19.3) said in response to MAIL FROM (452 4.1.0
ESMTP server temporarily not available - Refer to Error Codes section at
http:/
We saw things clear up around 1:20 pm U.S. Central. Whatever it was, it didn’t
really show up in DownDetector, so end-user facing access was apparently OK.
Frank
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Torsten Reinert
via mailop
Sent: Thursday, July 13, 2017 1:33 PM
Anyone else seeing delivery issues to mx01.perfora.net? Sample logs/data
below:
Frank
Open (74.208.5.21) Error 181sec (399 TCP Read failed (Err Code Zero after
180 seconds) 180 sec)
ubad=14022638, Site (sibleypresby.church/74.208.5.21) said: 450 Requested
mail action not taken: mailbox unavailab
Exactly. =)
This week was calm -- no alerts regarding our server queues about this issue.
Perhaps it was just one spammer that had a non-working SMTP server.
Frank
-Original Message-
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Bill Cole
Sent: Thursday, May 25, 2017 7:1
Thanks. Last logged occurrence was 5:07 pm U.S. Central.
Frank
From: Michael Wise [mailto:michael.w...@microsoft.com]
Sent: Friday, June 2, 2017 12:13 PM
To: Frank Bulk ; mailop@mailop.org
Subject: RE: [mailop] Hotmail server(s) out of memory?
Looks like the issue is being mitigate
It appears to be the second -- some bulk mail sender has started sending mail
with invalid Unsubscribe information and users that try to unsubscribe are
generating queue noise.
Frank
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Dave Warren
Sent: Monday, May 22, 2017 9:41 P
Just starting last week we started seeing our outbound queues fill up with
undeliverable client messages generated because of this one-click unsubscribe
feature. Since this Apple feature has been in place for over six months, I’m
surprised we haven’t seen this until now.
Here are the domain
Same here -- many of my customers, for example those who go to O365, aren't
aware of the implications when they add Microsoft's suggested SPF record,
and then wonder why some emails (originated from a non-O365 system) aren't
being received. Fortunately our helpdesk is very attuned to these issues
sm,
Do you think the sending domain was not aware of that when they wrote the
policy?
Frank
-Original Message-
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of SM
Sent: Sunday, May 21, 2017 8:13 AM
To: Kurt Jaeger ; mailop@mailop.org
Subject: Re: [mailop] SPF record
Hi Kur
Neil,
Thanks for sharing with ExactTarget.
Are you saying that checking the box on our commercial spam filtering system’s
“check SPF” feature, which quarantines messages that have SPF failures (-all),
was a poor decision on my part?
I don’t understand what DMARC has to do with this
I guess it depends on how our customers forward to the email account provided
by us. I’m sure that there are some messages that we do block due to
forwarding, but when I manually examined four weeks of SPF-based blocks, I
don’t recall seeing one example. You’re very much right that waiting for
John,
I'm a bit bewildered -- these aren't random strangers, they're the actual
sender. Am I supposed to second-guess the sender's instructions? If I have
to second-guess every sender's "-all" then I have to have another layer of
subjective analysis -- currently manual, in my situation.
Frank
I looked at the last week of blocked email from Travelocity.com and found just
one blocked message.
It was a flight change email from traveloc...@e.travelocity.com with a source
IP of 66.244.67.50.
fbulk@frankb-PC:/mnt/c/Users/fbulk$ dig TXT e.travelocity.com +short
"spf2.0/pra include:cust-sen
Yet the senders, via their SPF records with a "-all", told me to reject those
messages. As MTA's, we're doing what the send told us to do.
Frank
-Original Message-
From: John Levine [mailto:jo...@taugh.com]
Sent: Friday, May 19, 2017 9:56 AM
To: mailop@mailop.org
Cc: frnk...@iname.com
S
My $WORK domain is also labeled the same “50”, so I suspect the same “limited
sampling” issue.
Frank
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Stefano Bagnara
Sent: Friday, May 19, 2017 9:03 AM
To: mailop
Subject: Re: [mailop] SymantecCloud "Message filtered"
On 1
We have an automated SPF checking system in place for clients/partners/vendors
and auto-notify them of invalid/malformed SPF records every three weeks. The
responsive ones got them fixed up, but I still have three die-hards that
haven't made any changes. Their domains are low-volume, so they p
Our outbound email queues to Yahoo were somewhat delayed this afternoon ..
from what I see on downdetector.com, looks like it's not just us.
http://downdetector.com/status/yahoo-mail
Our queues are draining and the downdetector graph suggests that the issue
is resolving.
Frank
Not sure this this is related:
http://www.express.co.uk/life-style/science-technology/758307/BT-Mail-Down-Email-Address-BT-Internet-Not-Working
Frank
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Alberto Miscia via
mailop
Sent: Tuesday, January 24, 2017 12:06 PM
To: mailop@
Bill,
Thanks for bringing up all those points. While perhaps the practical
implications of the TLS1.0's brokenness may not be as applicable to email, it
doesn't mean ESPs should automatically be satisfied with the status quo. If
most vendors have found a way to implement TLS 1.1 and 1.2 then
We saw this start to ramp up around 8:20 am (U.S. Central) and about an hour
later messages were predominately getting delayed, yet even now a few do get
delivered from time to time.
Someone on the outages listserv posted about this, too.
(https://puck.nether.net/pipermail/outages/2016-June/0092
We're seeing multiple Microsoft-hosted domains having difficulty getting our
email.
@hsitire.com Open (207.46.163.170) Error
4sec (399 TCP Read failed (Connection reset by peer after 4 seconds) 4 sec)
@animalhealthinternational.comOpen (207.46.163.170) Error
4sec (
I want to disable it for the reasons that Eric spelled out. TLS 1.0 is broken,
so if we turn it off on websites, shouldn't we turn it off for all protocols?
Not that we promise our customers end-to-end encryption for all their e-mail
messages and handling, but I'd like to take advantage of the
Sounds like Synacor (who hosts cableone.net) has had issues again. From our
email server logs:
Open (64.8.70.47) Error 0sec (421 4.3.4 allocated resources
exceeded)
Open (64.8.70.47) Error 4sec (399 TCP Read failed (Connection reset
by peer after 4 seconds) 4 sec)
First log entry
Finally has a chance to look at my logs … looking at error count over time (all
U.S. Central) I see the following:
Server 1:
1 25 12:3
1 25 12:4
4 25 13:1
22 25 13:2
22 25 13:3
24 25 13:4
31 25 13:5
18 25 14:0
8 25 14:1
16 25 14:2
We saw the same thing too, just too busy dealing with the fallout of a
lightning strike.
Frank
-Original Message-
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Keenan Tims
Sent: Wednesday, May 25, 2016 3:09 PM
To: mailop@mailop.org
Subject: [mailop] Connection failures to
FYI, we did see more delivery issues to 98.139.171.245 for other Yahoo! hosted
email domains, with our email server logging:
(98.139.171.245) said in response to MAIL FROM (451 4.3.2 Internal
error reading data)
I saw first one at 10:30 am and last one was 7:36 pm (U.S. Central), so it's
When connecting to this email host
telnet 98.139.171.245 25
Trying 98.139.171.245...
2016 May 3 12:17:20 10.18.120.197 BCMSDK - unit 0 L3_ENTRY_IPV6_UNICAST
entry 1487 parity error
2016 May 3 12:17:20 10.18.120.197 BCMSDK - Unit 0: mem:
2103=L3_ENTRY_IPV6_UNICAST blkoffset:9
2016 May 3 12:
Is this worth bringing up to the appropriate IETF group? Perhaps it could be
errata for RFC 7208 Section 5.4?
Frank
-Original Message-
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Steve Atkins
Sent: Friday, April 29, 2016 12:18 PM
To: mailop
Subject: Re: [mailop] SPF ch
Thanks, I see same thing test right now, I’ll report it.
Frank
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Kurt Andersen (b)
Sent: Friday, April 29, 2016 12:40 PM
To: Steve Atkins
Cc: mailop
Subject: Re: [mailop] SPF check overly stringent?
On Fri, Apr 29, 2016 at 10:
Steve,
Thanks for your feedback.
Seems that the Word to Wise SPF checking tool skips "2607:fe28:0:4000::20" when
I check sigiowa.com.
Frank
-Original Message-
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Steve Atkins
Sent: Friday, April 29, 2016 12:18 PM
To: mailop
Sub
Probably not related, but we had a few of these today, first one at 8:16 am
(Central), last one at 2:30 pm:
ubad=-1, Site (redacted.domain/207.46.163.170) said: 451 4.3.2 Temporary server
error. Please try again later ATTR2
We saw these IPs involved:
207.46.163.138
207.46.163.170
207.46.
We saw this in small part today, starting at 10:45 am (Central), and clearing
up by 6:36 pm. Our email server logged this;
399 TCP Read failed (Connection reset by peer after 32 seconds)
Across several MXes.
Frank
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf
Delivery resumed at 7:42 pm (Central) and our queue is now drained.
Never heard anything back from my own contacts or tweets.
Frank
-Original Message-
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of frnk...@iname.com
Sent: Sunday, April 03, 2016 12:18 PM
To: mailop@mailop.or
Since 9:11 pm (U.S. Central) we've been seeing our queue to hickortyech.net
(now owned by Consolidated Communications) backup with messages like this
logged on our email server:
Site (hickorytech.net/192.86.64.40) said: 451 4.3.0
: Temporary lookup failure
with IPs 192.86.64.40, .41, and .4
You can also try: https://sslanalyzer.comodoca.com/
Just append ":25" to the host.
Frank
-Original Message-
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Tim Bray
Sent: Friday, April 01, 2016 3:58 AM
To: Kirk MacDonald ; mailop@mailop.org
Subject: Re: [mailop] Gmail red ope
Anyone aware of email servers that take the approach that CloudFlare has, which
is not allow the lowest common denominator or cleartext to be used if there’s a
better/more-secure cipher, but still support the old stuff (in CloudFlare’s
case, SHA-1) if that’s all it can do?
https://blog.cloudfla
Are you taking that approach because the workaround is less than ideal?
Otherwise the current “workaround” could be the new standard.
Frank
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Vick Khera
Sent: Tuesday, March 22, 2016 8:54 PM
To: mailop
Subject: Re: [mailop] Yahoo
Thanks. By 2:30 pm (U.S. Central) our outbound queues were essentially drained.
Frank
From: cverv...@apple.com [mailto:cverv...@apple.com]
Sent: Sunday, March 20, 2016 3:11 PM
To: Frank Bulk
Cc: stevem ; Alarig Le Lay ;
mailop@mailop.org
Subject: Re: [mailop] Email delivery issues to ya
Our queues are all caught up.
Frank
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Frank Bulk
Sent: Wednesday, March 16, 2016 3:56 PM
To: 'Brett Schenker' ; Vick Khera
Cc: mailop@mailop.org
Subject: Re: [mailop] Email issue with Synacor?
Thanks. The CableOne NOC responde
Now this isn’t email servers, but in terms of websites, ~9% of surveyed sites
support it: https://www.trustworthyinternet.org/ssl-pulse/
Frank
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Brandon Long via
mailop
Sent: Wednesday, March 02, 2016 7:30 PM
To: Franck Martin
C
Thanks for the additional data points -- so it isn't just me.
What's nasty is that the messages are kicked back to the sender, not just
delayed.
Frank
-Original Message-
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Frank Bulk
Sent: Friday, February 05, 2016 5:27 PM
To: m
We saw some of this in our logs tonight:
Site yahoo.com (98.136.217.203) said in response to MAIL FROM (451 4.3.2
Internal error reading data)
Site yahoo.com (66.196.118.36) said in response to MAIL FROM (451 4.3.2
Internal error reading data)
Site yahoo.com (66.196.118.37) said in response to MAI
I'd recommend that rather than forward messages to Google that you have
those Google accounts POP the messages from smokva.net.
Frank
-Original Message-
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Petar
Bogdanovic
Sent: Thursday, December 10, 2015 9:44 AM
To: mailop@mailo
CableOne NOC contacted me to check ... by which times our outbound queue for
cableone.net was already empty. Issues appears to have been resolved by their
partner, Synacor.
Frank
-Original Message-
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of frnk...@iname.com
Sent: Tue
I'm pleasantly surprised -- the CableOne NOC responded in less than ten
minutes, acknowledging the issue and indicating they have already contacted
their vendor. From the response, it appears that intra-domain email is
working for their customers.
Frank
-Original Message-
From: Frank Bul
@ATTCares confirmed it was affecting Yahoo mail, too. My queues cleared up
around 9 pm Central.
Frank
-Original Message-
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Frank Bulk
Sent: Tuesday, November 10, 2015 5:42 PM
To: 'Jay Hennigan' ; mailop@mailop.org
Subject: Re: [m
We alias all the abuse addresses for the domains we host to our ISP abuse
account ... we get very little spam.
Frank
-Original Message-
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Matthew Newton
Sent: Tuesday, September 15, 2015 7:27 AM
To: David Hofstee
Cc: mailop@mail
FYI
From: Outages [mailto:outages-boun...@outages.org] On Behalf Of Grant Ridder
via Outages
Sent: Tuesday, June 09, 2015 2:09 PM
To: outa...@outages.org
Subject: [outages] gmail delay
6/9/15, 11:33 AM
We're investigating reports of an issue with Gmail. We will provide more
information
We’re seeing none of that. It’s all delivering to all Yahoo MTAs just fine,
though we’re not hitting 98.138.112.33 very often.
Frank
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Tim Bosserman
Sent: Wednesday, May 06, 2015 4:20 PM
To: mailop@mailop.org
Subject: [mailop] An
59 matches
Mail list logo
