[mailop] Apparently not. (was: Re: Is Spectrum trying to sunset rr.com and twc.com emails?)
- 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 > they realized that yes, customers do still use those addresses. Maybe, but I have an offlist reply which both appears -- and claims :-) -- to be authoritative, which says no such plans are in-work. Cheers, -- jra -- Jay R. Ashworth Baylink j...@baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274 ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
Re: [mailop] Is Spectrum trying to sunset rr.com and twc.com emails?
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 spectrum. There are millions of roadrunner.com and splat.rr.com users out there. While they had intended to move all new emails to a branded domain, that process is long and drawn out. On 2/8/20, 8:08 PM, "mailop on behalf of John Levine via mailop" wrote: 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 while. For all the reasons you cite it's much easier to keep the old addresses working even as you merge the infrastructure. I mean, aol.com addresses aren't going away even though they're now running on ex-Yahoo Verizon systems. ___ 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
Re: [mailop] Is Spectrum trying to sunset rr.com and twc.com emails?
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 addresses. -Original message- From:Jay R. Ashworth via mailop Sent:Sat 02-08-2020 08:54 pm Subject:[mailop] Is Spectrum trying to sunset rr.com and twc.com emails? To:mailop@mailop.org; 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 *ever* sunsets the domain names, cause there's no real reason to do so, and it pisses off end-users. The email also pointed to this domain name, which looks semi-official, and I can't decide if the whole thing is some clever spear-fishing attempt, or just someone who misunderstood something and is trying to be helpful. Does anyone on the list know if there's such a sunset policy in process? Cheers, -- jra -- Jay R. Ashworth Baylink j...@baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274 ___ 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
Re: [mailop] Is Spectrum trying to sunset rr.com and twc.com emails?
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 while. For all the reasons you cite it's much easier to keep the old addresses working even as you merge the infrastructure. I mean, aol.com addresses aren't going away even though they're now running on ex-Yahoo Verizon systems. ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
[mailop] Is Spectrum trying to sunset rr.com and twc.com emails?
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 *ever* sunsets the domain names, cause there's no real reason to do so, and it pisses off end-users. The email also pointed to this domain name, which looks semi-official, and I can't decide if the whole thing is some clever spear-fishing attempt, or just someone who misunderstood something and is trying to be helpful. Does anyone on the list know if there's such a sunset policy in process? Cheers, -- jra -- Jay R. Ashworth Baylink j...@baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274 ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
Re: [mailop] why does this list break DKIM?
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 the mailing list. If we done change the From then the list will be blocked for SPF failures. Other headers get added. The good news is that we are working on rehosting the list and this should improve our headers. I will also note that the 7th email to this list was about the headers and reply-to. Considering the how often it crops up on non-mail technical mailing lists it is perhaps no surprise it is a reoccuring topic on a list full of mail admins. https://chilli.nosignal.org/cgi-bin/mailman/private/mailop/2007-November/07.html -- Simon Lyall | Very Busy | Web: http://www.simonlyall.com/ "To stay awake all night adds a day to your life" - Stilgar ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
Re: [mailop] Hey.com?
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 with email marketers. Allowing them to spam people at will. So we
can assume this is supposed to be a solution to spam and unwanted
messaging.
He also spent some time talking about tracking pixels being "spy devices."
He mentioned, in colorful language, that Hey will rip out tracking pixels
or something like that. What is interesting is that his ire for tracking
opens is directed at marketers/senders and not mailbox providers. Or maybe
it's both? Either way, from this we can infer that Hey is going to "fix"
all the consumer privacy issues associated with email.
>From other tweets he mentioned that it will be a standalone application
that does all the email stuff; send, receive, store..it will also do all
the SPF, DKIM, DMARC stuff. It will also do spam filtering and reputation
scoring and everything that comes along with that. All built in house. You
will *not* be able to use this as a wrapper for your
gmail/hotmail/yahoo/aol mailboxes. Custom domains will come eventually. But
this is not another service you can tie a gmail inbox to. Thank goodness?
The plan is to charge people for it. Which isn't a bad thing.
All of this is just information gathered from a twitter rant and what
little there is on their website. So, take it all with a grain of salt. But
the gist of it is that tracking pixels are spying on you, "big tech" is
ruining email by helping spammers, and the Hey email service will solve all
of this. *Fingers crossed.*
Luke
On Sat, Feb 8, 2020, 9:24 AM Thomas Walter via mailop
wrote:
> 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, we’ve done just that. It’s a redo, a rethink, a simplified,
> > potent reintroduction of email. A fresh start, the way it should be.
>
> David Heinemeier Hansson (https://twitter.com/dhh) has been mentioning
> it on Twitter now and then and there are some rumors, but I haven't
> heard much else.
>
> Anyone on here who knows more?
>
> Regards from Germany,
> Thomas Walter
>
> --
> Thomas Walter
> Datenverarbeitungszentrale
>
> FH Münster
> - University of Applied Sciences -
> Corrensstr. 25, Raum B 112
> 48149 Münster
>
> Tel: +49 251 83 64 908
> Fax: +49 251 83 64 910
> www.fh-muenster.de/dvz/
>
> ___
> 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
Re: [mailop] ADMIN: Mailop in 2020
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, Simon Lyall via mailop wrote: We are planning to move the mailop list to new hosting in early 2020. We have got a donated VM. The plan is to move to a newer version of mailman and get the list configured with SPF, DKIM and various other good practices for email (and also web). More details closer to the move. The server is mostly setup and we are currently working on getting the DNS for mailop.org moved but have hit a delay. Worst case we may have to move the list to a new domain. The list now has just over 2000 subscribers and apart from technical issues with the hosting seems to be going okay. There will be a new person or two added to the admin team after the move. Hope you all have a Happy and low-Spam New Year. Simon Mailop list Admin. -- Simon Lyall | Very Busy | Web: http://www.simonlyall.com/ "To stay awake all night adds a day to your life" - Stilgar ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
Re: [mailop] A question ... who is optinx . org ???
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" smells spammy from 100 kilometers away. -- 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
Re: [mailop] Remarkable longevity of AWS-hosted spamming operation
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 time lines as a whole in the large cloud providers, and that issue.. their limitations on giving feedback doesn't help the infosec community, and issues like this can't be handled by a 'whack-a-mole' approach, and certainly don't have time to report every occurence of this. BTW, that domain is a 'free dynamic subdomain' .. It's only one of several pandemic issues raised with Amazon.. hopefully we have some feedback soon ;) On 2020-02-08 8:56 a.m., Michael Rathbun via mailop wrote: [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 sender." and a visible FROM of livenewsupd...@millan.pgw.jp has made 66 delivery attempts over the past six days, from 60 Amazon IPs. If a given IP was not on Spamhaus CSS at the time of delivery, it appears that it would have been added soon after. These figures reflect data from logs that have not yet been rolled into the archive. There are three deliverable local addresses in their customary drop, two which come to me and the other being "Nadine". The rest of the recipients are spamtrap accounts that result in the message being delivered to Rev. Bayes, and the IP dropped into the IP REFUSE list for at least 1440 minutes. At the moment there are 48 AWS IP addresses in that list. It is difficult to imagine how such a large-scale and essentially static operation (the EHLO, MAIL FROM and visible FROM, together with the opening string have been constant since the first messages rolled in on 16 Dec 2019) could persist. There was an apparent service interruption from 01 Jan to 09 Jan, after which delivery attempts continue as usual. The most recent delivery was approximately 45 minutes ago (the IP, 54.91.110.45, was not in CSS at delivery time; it is now).In that interval, at least four of the refuse-listed IPs have encountered refusal. Is nobody else seeing this and reporting it to AWS abuse? mdr -- "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://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
[mailop] Remarkable longevity of AWS-hosted spamming operation
[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 sender." and a visible FROM of >livenewsupd...@millan.pgw.jp has made 66 delivery attempts over the past six days, from 60 Amazon IPs. If a given IP was not on Spamhaus CSS at the time of delivery, it appears that it would have been added soon after. These figures reflect data from logs that have not yet been rolled into the archive. There are three deliverable local addresses in their customary drop, two which come to me and the other being "Nadine". The rest of the recipients are spamtrap accounts that result in the message being delivered to Rev. Bayes, and the IP dropped into the IP REFUSE list for at least 1440 minutes. At the moment there are 48 AWS IP addresses in that list. It is difficult to imagine how such a large-scale and essentially static operation (the EHLO, MAIL FROM and visible FROM, together with the opening string have been constant since the first messages rolled in on 16 Dec 2019) could persist. There was an apparent service interruption from 01 Jan to 09 Jan, after which delivery attempts continue as usual. The most recent delivery was approximately 45 minutes ago (the IP, 54.91.110.45, was not in CSS at delivery time; it is now).In that interval, at least four of the refuse-listed IPs have encountered refusal. Is nobody else seeing this and reporting it to AWS abuse? mdr -- "There are no laws here, only agreements." -- Masahiko ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
[mailop] Hey.com?
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, we’ve done just that. It’s a redo, a rethink, a simplified,
> potent reintroduction of email. A fresh start, the way it should be.
David Heinemeier Hansson (https://twitter.com/dhh) has been mentioning
it on Twitter now and then and there are some rumors, but I haven't
heard much else.
Anyone on here who knows more?
Regards from Germany,
Thomas Walter
--
Thomas Walter
Datenverarbeitungszentrale
FH Münster
- University of Applied Sciences -
Corrensstr. 25, Raum B 112
48149 Münster
Tel: +49 251 83 64 908
Fax: +49 251 83 64 910
www.fh-muenster.de/dvz/
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
Re: [mailop] A question ... who is optinx . org ???
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 opt-out service ... No kidding. FYI, West Palm Beach is about 20 miles from Boca Raton. Just saying. R's, John ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
Re: [mailop] [ext] Re: Business justification to use noreply sender addresses?
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 no matter how much you try to tilt it... People who write mail software have known at least since the 1980s that an autoresponder should only respond if the recipient's address is on the To: or maybe the Cc: line. I have a procmail man page from about 1991 with an autoresponder recipe that makes that check. + RFC 3834 from 2004, and speaking of procmailrc * !^FROM_DAEMON which includes `* !^Precedence: (list|junk|bulk)` -- -- Andreas :-) ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
