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
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.
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
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
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
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-
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