- Original Message -
> From: "Jerry Cloe"
> Several months ago I could no longer deliver to @kc.rr.com, and this went on
> for
> months, finally mx records changed one day and all of a sudden its working
> again. I have to wonder if that wasn't some kind of test or mistake, and then
>
Nobody should listen to me at all because I have the memory of a goldfish. But
in a past life I knew lots about splat.rr.com. There were royalty issues with
the RoadRunner domains but I'm fairly sure Spectrum bought out the domain at
least. I do know it (rr.com) under markmonitor through
Several months ago I could no longer deliver to @kc.rr.com, and this went on
for months, finally mx records changed one day and all of a sudden its working
again. I have to wonder if that wasn't some kind of test or mistake, and then
they realized that yes, customers do still use those
In article <1692699245.1838651.1581216535504.javamail.zim...@baylink.com>,
Jay R. Ashworth via mailop wrote:
>Does anyone on the list know if there's such a sunset policy in process?
I doubt it. My twcny.rr.com address still works even though I haven't been
a Spectrum customer for quite a
A client got an email that appeared to be from Keap, or maybe InfusionSoft,
suggesting that Spectrum was trying to do that, and that users shouldn't add
contacts with those emails unless they were "bone-fide" (which was my only
hint)...
but my experience of email carrier buyouts is that no-one
On Sat, 8 Feb 2020, Aragon Gouveia via mailop wrote:
Does anyone know why this list breaks DKIM verification? In particular
it looks like it's altering From, Reply-To, and Cc headers, and failing
to perform any kind of resigning too.
Changing the From (and other headers) needs to be done by
There isnt a ton of info yet, but based on the Twitter rant we can infer a
few things.
He's fed up with "big tech" doing nothing about spam and unwanted
messaging. This is funny for a number of reasons. But unless I'm
misinterpreting something, DHH seems to think the big providers are in
cahoots
Just an update. We are proceeding using the existing mailop.org domain so
hopefully less disruption. We are to move DNS hosting soon (once we decide
if DNSSEC is worth it) and then we will start getting the new server ready.
Cutover is probably still a few weeks away.
On Sun, 29 Dec 2019,
Dnia 7.02.2020 o godz. 23:38:05 Al Iverson via mailop pisze:
> "OLA Workplace Skills Training Centre" traces to 1655 Palm Beach Lakes
> Blvd. Suite C-1005, West Palm Beach, FL, 33401 which appears to be
> SmartAdv LLC or Intelligent Media Group or Intelligent Holdings, Inc.
Name like "SmartAdv"
Interestingly,
(And yes, it has been happening a long time)
We just engaged on this issue (and others) with senior members of their
abuse team.
First reported to Amazon on November 27th, but this is a great example
why we escalated to senior members responsible.
Aside from slow take down
[NOTE: this is relevant to mail operations as a number of legitimate senders
are customers of Amazon AWS. Several of them are my clients.]
An operation that is easily distinguished by
> EHLO phylobago.mysecuritycamera.org
and a payload that begins with "This message is from a trusted
So, this https://hey.com/ has been making it rounds through my filter
bubble.
It seems to be a new concept(?) for an email service ("not client" as
the emphasize) by the Basecamp guys.
They say
> [Mail] deserves a dust off. A renovation. Modernized for the way we
> email today.
>
> With HEY,
In article
you write:
>"OLA Workplace Skills Training Centre" traces to 1655 Palm Beach Lakes
>Blvd. Suite C-1005, West Palm Beach, FL, 33401 ...
>I don't know anything about them personally but it sure seems like
>senders with explicit opt-in permission generally don't need a third
>party
On Fri, 7 Feb 2020, at 19:21, John Levine via mailop wrote:
In article ,
Philip Paeps via mailop wrote:
On 2020-02-07 08:34:13 (-0800), Jaroslaw Rafa via mailop wrote:
It would be best if autoresponders simply didn't reply to messages
from mailing lists.
That windmill is not going to budge
14 matches
Mail list logo