Hi There,

Apologies -- forgot to edit the SL in my initial message.

Does anyone have a contact at Earthlink.net?

We started seeing DKIM fail for our clients only at Earthlink.net about 2
months ago (no issues with any other major ISPs) and now some mail is being
hard blocked with "551 ERROR: DKIM signature verification failed (signature
verification failed)".

Thank you!
Albert

On Mon, Jan 8, 2018 at 7:52 AM, <mailop-requ...@mailop.org> wrote:

> Send mailop mailing list submissions to
>         mailop@mailop.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
> or, via email, send a message with subject or body 'help' to
>         mailop-requ...@mailop.org
>
> You can reach the person managing the list at
>         mailop-ow...@mailop.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of mailop digest..."
>
>
> Today's Topics:
>
>    1. Re: Anyone with a pulse at combell.com? (Philip Paeps)
>    2. Re: Anyone with a pulse at combell.com? (Ken O'Driscoll)
>    3. Re: Anyone with a pulse at combell.com? (Charles McKean)
>    4. Re: Weird problems with mitigation at Hotmail/Outlook
>       (John Possidente)
>    5. Re: mailop Digest, Vol 123, Issue 8 (Albert Liu)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 8 Jan 2018 13:15:25 +0100
> From: Philip Paeps <phi...@trouble.is>
> To: mailop@mailop.org
> Subject: Re: [mailop] Anyone with a pulse at combell.com?
> Message-ID: <20180108121524.gp89...@rincewind.trouble.is>
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
> On 2018-01-08 09:44:10 (+0100), David Hofstee wrote:
> >On 6 January 2018 at 15:32, Philip Paeps <phi...@trouble.is> wrote:
> >>I'm getting repeated spamtrap hits from customers of combell.com.
> >>Forwarding messages (even just headers) to abuse@ gets bounces:
> >>
> >>  ab...@combell.com
> >>    host 217.21.178.56 [217.21.178.56]
> >>    SMTP error from remote mail server after end of data:
> >>    550 5.7.1 Message rejected as spam by Content Filtering.
> >>
> >>Asking abuse@ how they'd like to be told about their customers'
> >>network abuse gets bounced with the same error.  Great!
> >>
> >>Does anyone know any humans there?
> >>
> >> They're unfortunately too large to block outright.
> >
> >Did you try it with a non-"trouble.is" domain?
>
> Yes.  I sent these from postmaster@ the several domains where the
> spamtraps are hosted and from philip@ in the domains I've got mailboxes
> in.  Always the same error: "Message rejected as spam by Content
> Filtering".
>
> >E.g. an @gmail.com account?
>
> I don't have one of those.
>
> It doesn't look like the return address matters though.
>
> Aside: it seems more than a bit silly to run a content filter on abuse@.
> If their filter feeds into reputation monitoring systems, I've probably
> damaged my networks' reputations by being a good internet citizen and
> reporting abuse of their network!
>
> Philip
>
> --
> Philip Paeps
> Senior Reality Engineer
> Ministry of Information
>
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 08 Jan 2018 13:18:23 +0000
> From: Ken O'Driscoll <k...@wemonitoremail.com>
> To: mailop@mailop.org
> Subject: Re: [mailop] Anyone with a pulse at combell.com?
> Message-ID: <1515417503.3115.2.ca...@wemonitoremail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> On Mon, 2018-01-08 at 13:15 +0100, Philip Paeps wrote:
> > Aside: it seems more than a bit silly to run a content filter on
> > abuse@.
> > If their filter feeds into reputation monitoring systems, I've probably
> > damaged my networks' reputations by being a good internet citizen and
> > reporting abuse of their network!
>
> The RFC explicitly advises against that but people still do it.
>
> Their "email support" option appears to be a pop-up form which may allow
> you to circumvent any pre-acceptance testing:
>
> https://www.combell.com/en/support
>
> Ken.
>
> --
> Ken O'Driscoll / We Monitor Email
> t: +353 1 254 9400 | w: www.wemonitoremail.com
>
> Need to understand deliverability? Now there's a book:
> www.wemonitoremail.com/book
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Mon, 8 Jan 2018 09:36:07 -0500
> From: Charles McKean <charles.mckean.ml...@gmail.com>
> To: mailop <mailop@mailop.org>
> Subject: Re: [mailop] Anyone with a pulse at combell.com?
> Message-ID:
>         <CAGUsykktn=KempR=2w1yGRDQSBY7tjNrTxFad=XYyJERRv6NRA@mail.
> gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> On Mon, Jan 8, 2018 at 7:15 AM, Philip Paeps <phi...@trouble.is> wrote:
>
> >> Did you try it with a non-"trouble.is" domain?
> >
> > Yes.  I sent these from postmaster@ the several domains where the
> spamtraps
> > are hosted and from philip@ in the domains I've got mailboxes in.
> Always
> > the same error: "Message rejected as spam by Content Filtering".
> >
> >> E.g. an @gmail.com account?
> >
> >
> > I don't have one of those.
>
> Why not? Cost too high?
>
> I was able to contact them just now and open a ticket with them using
> the abuse address. Do not include the spam report and instead explain
> that your reports are getting rejected and ask them what they expect
> you to do to get this through to them.
>
>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 8 Jan 2018 10:18:15 -0500
> From: John Possidente <possiden...@gmail.com>
> To: Brian Curry <bcu...@merkleinc.com>
> Cc: mailop <mailop@mailop.org>, Edgaras | SENDER <edga...@sender.net>
> Subject: Re: [mailop] Weird problems with mitigation at
>         Hotmail/Outlook
> Message-ID:
>         <CALeKJxdfaTtXLP7PqY=o-nMu-rdNcNc8ZOsWQdisZujXBrciuw@mail.
> gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Thanks, Brian. That's not a bad idea. Worth a try, anyway.
>
> John
>
>
> On Fri, Jan 5, 2018 at 12:11 PM, Brian Curry <bcu...@merkleinc.com> wrote:
>
> > What *might* be going on there is MSFT lifts the “block” but doesn’t
> > change any thresholds/limits the IP is still susceptible to.
> >
> >
> >
> > You may want to prompt the robots to give you the “new IP space” form to
> > provide expected volumes from the IP, and see if MSFT will adjust
> > thresholds on the IP. That has worked in the past for me, along with the
> > mitigation.
> >
> >
> >
> >
> >
> > Brian Curry
> >
> > Email Deliverability Team Lead | Platform Services
> >
> > Merkle Inc.
> >
> >
> >
> > *From:* mailop [mailto:mailop-boun...@mailop.org] *On Behalf Of *John
> > Possidente
> > *Sent:* Friday, January 05, 2018 7:41 AM
> > *To:* Edgaras | SENDER <edga...@sender.net>
> > *Cc:* mailop <mailop@mailop.org>
> > *Subject:* Re: [mailop] Weird problems with mitigation at Hotmail/Outlook
> >
> >
> >
> > Seen this also recently (past couple of weeks at least). "Block has been
> > lifted" and then it's not.
> >
> > John
> >
> >
> >
> > On Fri, Jan 5, 2018 at 6:29 AM, Edgaras | SENDER <edga...@sender.net>
> > wrote:
> >
> > Hi,
> >
> >
> >
> > 2 days ago one of our IPs started getting an AS3150 block when sending to
> > Hotmail/Outlook.
> >
> > Which is very weird, as complaint rate and bounce rate are way below what
> > Outlook publishes as their official requirements.
> >
> >
> >
> > After submitting their delivery support form, we get the automatic email
> > saying that the IP has been mitigated: "Our investigation has determined
> > that the above IP(s) qualify for mitigation. The block has been lifted,
> and
> > the IP(s) have been granted increased daily sending limits."
> >
> >
> >
> > However, the IP still stays blocked! After replying to that email, we get
> > a copy-paste reply from Outlook.com support saying that "As previously
> > stated, your IP(s) do not qualify for mitigation at this time."
> >
> >
> >
> > ???
> >
> >
> >
> > Alright, we repeat the process the next day, with the same results -
> > initial email says that the IP has been mitigated, that doesn't work and
> > the IP is still blocked, and Outlook.com support says that the IP is not
> > eligible for mitigation.
> >
> >
> >
> > Asking to escalate to T3 did nothing.
> >
> >
> >
> > Has someone else experienced this? What to do in this situation?
> >
> >
> >
> > P.S. if anyone from Outlook/Hotmail are here, here is the ticket number:
> > SRX1410467394ID. I would greatly appreciate any help or insight into
> this.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Regards,
> >
> >
> > [image: Sender]
> >
> > Edgaras Vaitkevičius
> > edga...@sender.net
> > +370 627 60923 <+370%20627%2060923>
> >
> >
> > _______________________________________________
> > mailop mailing list
> > mailop@mailop.org
> > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
> >
> >
> >
> > *Named Search Agency of the Year by MediaPost*
> > <http://www2.merkleinc.com/l/47252/2017-11-21/52tbyb>
> >
> > This email and any attachments transmitted with it are intended for use
> by
> > the intended recipient(s) only. If you have received this email in error,
> > please notify the sender immediately and then delete it. If you are not
> the
> > intended recipient, you must not keep, use, disclose, copy or distribute
> > this email without the author’s prior permission. We take precautions to
> > minimize the risk of transmitting software viruses, but we advise you to
> > perform your own virus checks on any attachment to this message. We
> cannot
> > accept liability for any loss or damage caused by software viruses. The
> > information contained in this communication may be confidential and may
> be
> > subject to the attorney-client privilege.
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <https://chilli.nosignal.org/cgi-bin/mailman/private/mailop/
> attachments/20180108/a91259b9/attachment-0001.html>
>
> ------------------------------
>
> Message: 5
> Date: Mon, 8 Jan 2018 07:52:01 -0800
> From: Albert Liu <albert....@messagegears.com>
> To: mailop@mailop.org
> Subject: Re: [mailop] mailop Digest, Vol 123, Issue 8
> Message-ID:
>         <CAGFgzLOeLEXOkHaE_5KkjxXG5d7z1jpKWTJr42rZp18h+M5mKg@mail.
> gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi There,
>
> Does anyone have a contact at Earthlink.net?
>
> We started seeing DKIM fail for our clients only at Earthlink.net about 2
> months ago (no issues with any other major ISPs) and now some mail is being
> hard blocked with "551 ERROR: DKIM signature verification failed (signature
> verification failed)".
>
> Thank you!
> Albert
>
> On Mon, Jan 8, 2018 at 4:00 AM, <mailop-requ...@mailop.org> wrote:
>
> > Send mailop mailing list submissions to
> >         mailop@mailop.org
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> >         https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
> > or, via email, send a message with subject or body 'help' to
> >         mailop-requ...@mailop.org
> >
> > You can reach the person managing the list at
> >         mailop-ow...@mailop.org
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of mailop digest..."
> >
> >
> > Today's Topics:
> >
> >    1. Re: Anyone with a pulse at combell.com? (David Hofstee)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Mon, 8 Jan 2018 09:44:10 +0100
> > From: David Hofstee <opentext.dhofs...@gmail.com>
> > To: Philip Paeps <phi...@trouble.is>
> > Cc: mailop <mailop@mailop.org>
> > Subject: Re: [mailop] Anyone with a pulse at combell.com?
> > Message-ID:
> >         <CAKxMAXwYT3A8PZvRRCdhyYk1OAt4SrCKtC9nDDo6wqk0s8WGnQ@mail.
> > gmail.com>
> > Content-Type: text/plain; charset="utf-8"
> >
> > Hi Philip,
> >
> > Did you try it with a non-"trouble.is" domain? E.g. an @gmail.com
> account?
> >
> > Yours,
> >
> >
> > David
> >
> > On 6 January 2018 at 15:32, Philip Paeps <phi...@trouble.is> wrote:
> >
> > > I'm getting repeated spamtrap hits from customers of combell.com.
> > > Forwarding messages (even just headers) to abuse@ gets bounces:
> > >
> > >  ab...@combell.com
> > >    host 217.21.178.56 [217.21.178.56]
> > >    SMTP error from remote mail server after end of data:
> > >    550 5.7.1 Message rejected as spam by Content Filtering.
> > >
> > > Asking abuse@ how they'd like to be told about their customers'
> network
> > > abuse gets bounced with the same error.  Great!
> > >
> > > Does anyone know any humans there?
> > >
> > > They're unfortunately too large to block outright.
> > >
> > > Thanks.
> > > Philip
> > >
> > > --
> > > Philip Paeps
> > > Senior Reality Engineer
> > > Ministry of Information
> > >
> > > _______________________________________________
> > > mailop mailing list
> > > mailop@mailop.org
> > > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
> > >
> >
> >
> >
> > --
> > --
> > My opinion is mine.
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> > URL: <https://chilli.nosignal.org/cgi-bin/mailman/private/
> > mailop/attachments/20180108/648dec19/attachment-0001.html>
> >
> > ------------------------------
> >
> > Subject: Digest Footer
> >
> > _______________________________________________
> > mailop mailing list
> > mailop@mailop.org
> > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
> >
> >
> > ------------------------------
> >
> > End of mailop Digest, Vol 123, Issue 8
> > **************************************
> >
>
>
>
> --
> Albert Liu
> Head of Deliverability
> (404)-334-0929
> albert....@messagegears.com
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <https://chilli.nosignal.org/cgi-bin/mailman/private/mailop/
> attachments/20180108/e3354bf2/attachment.html>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> mailop mailing list
> mailop@mailop.org
> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
>
>
> ------------------------------
>
> End of mailop Digest, Vol 123, Issue 9
> **************************************
>



-- 
Albert Liu
Head of Deliverability
(404)-334-0929 <(404)%20334-0929>
albert....@messagegears.com
_______________________________________________
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Reply via email to