I haven't seen this mentioned anywhere else, so for those who haven't
heard yet, Virbl is shutting down.
From their (now static) website: "The Virbl DNSBL-zone was emptied and
will be removed all together at a moment further on in the future.
Please remove any DNSBL-lookups against 'virbl.dnsbl.bi
Anyone else seeing connection issues to AOL? Saturday morning (EST) we
started getting
421 mtaig-maa03.mx.aol.com Service unavailable - try again later
on the initial connection where the responding AOL hostname varies.
From what we can tell we haven't seen a dramatic change in mail
Responding offline
thanks
Lili Crowley
AOL Postmaster
On Mon, Jan 23, 2017 at 10:29 AM, Derek Diget
wrote:
>
> Anyone else seeing connection issues to AOL? Saturday morning (EST) we
> started getting
>
> 421 mtaig-maa03.mx.aol.com Service unavailable - try again later
>
> on the init
On Mon, Jan 23, 2017 at 10:29 AM, Derek Diget
wrote:
> Anyone else seeing connection issues to AOL? Saturday morning (EST) we
> started getting
>
> 421 mtaig-maa03.mx.aol.com Service unavailable - try again later
>
> on the initial connection where the responding AOL hostname varies.
>
>
On Mon, Jan 23, 2017 at 10:29 AM, Derek Diget
wrote:
>
> Anyone else seeing connection issues to AOL? Saturday morning (EST) we
> started getting
>
> 421 mtaig-maa03.mx.aol.com Service unavailable - try again later
>
Yep,
~$ mailq
Queue ID- --Size-- ---Arrival Time --Sender
On 2017-01-23 8:29 AM, Derek Diget wrote:
Anyone else seeing connection issues to AOL? Saturday morning (EST) we
started getting
421 mtaig-maa03.mx.aol.com Service unavailable - try again later
on the initial connection where the responding AOL hostname varies.
We're seeing pretty mixed
We are working on an issue here that is causing this problem.
Stay tuned.
Thanks
Lili Crowley
AOL Postmaster
On Mon, Jan 23, 2017 at 11:17 AM, Jim Popovitch wrote:
> On Mon, Jan 23, 2017 at 10:29 AM, Derek Diget
> wrote:
> >
> > Anyone else seeing connection issues to AOL? Saturday morning
On Mon, Jan 23, 2017 at 11:52 AM, Lili Crowley wrote:
> We are working on an issue here that is causing this problem.
I see it as resolved now, Thank you Lili and TeamAOL.
-Jim P.
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/c
Good news! Thanks for the update!
Lili Crowley
AOL Postmaster
On Mon, Jan 23, 2017 at 12:52 PM, Jim Popovitch wrote:
> On Mon, Jan 23, 2017 at 11:52 AM, Lili Crowley
> wrote:
> > We are working on an issue here that is causing this problem.
>
> I see it as resolved now, Thank you Lili and Tea
We recently enabled starttls to every destination (announcing the starttls
extension).
We now see a lot of "454 4.3.3 TLS not available due to temporary reason"
in reply to the STARTTLS by a big B2B italian provider named Aruba. We
usually are able to send the email after 2-3-5 attempts, so this i
On Mon, 23 Jan 2017 at 12:52 -, Jim Popovitch wrote:
=>On Mon, Jan 23, 2017 at 11:52 AM, Lili Crowley
wrote:
=>> We are working on an issue here that is causing this problem.
=>
=>I see it as resolved now, Thank you Lili and TeamAOL.
+579 to that! (messages we had queued up. :)
--
**
Having STARTTLS on by default is a good idea but you do need to have a fallback
in place as there's quite a lot of problematic servers:
* you need to trust self signed certificates, it doesn’t make much sense to go
with plaintext if certificate is not valid
* incompatible cipher suites (ie. serv
Note that information about Google is about 3 years out of date, we no
longer fall back to unencrypted.
Your best bet for important domains you care about it to try and contact
their admins to fix it.
Other than that, it's basically up to your policies what to do... well, and
what your software c
According to my logs, Spamcop listed 69.25.202.114 for a while yesterday.
That led to great merriment, since that's Blue State Digital and mail
from mainstream political groups went into spamtraps that tested the
URLs, some of which were "Click here to donate now with your preregistered
credit car
On 23 Jan 2017 21:30:20 +, "John Levine" said:
> That led to great merriment, since that's Blue State Digital and mail
> from mainstream political groups went into spamtraps that tested the
> URLs, some of which were "Click here to donate now with your preregistered
> credit card!" Oops.
OK,
Seems to me the system is may be trying to verify the certificate? It may
be checking the revoking list?
But yes I would try to contact Aruba to get some info, may be someone on
the list has a contact there?
On Mon, Jan 23, 2017 at 11:42 AM, Brandon Long via mailop wrote:
> Note that informatio
On Mon, Jan 23, 2017, at 17:57, valdis.kletni...@vt.edu wrote:
> On 23 Jan 2017 21:30:20 +, "John Levine" said:
>
> > That led to great merriment, since that's Blue State Digital and mail
> > from mainstream political groups went into spamtraps that tested the
> > URLs, some of which were "Cli
17 matches
Mail list logo
