Re: [mailop] [EXTERNAL] Re: Vade - Blacklisting

[Brotman, Alex via mailop]

Apologies on not being clear.  The /24 is resolved with Vade as well (as of 
early this morning).

--
Alex Brotman
Sr. Engineer, Anti-Abuse & Messaging Policy
Comcast

From: mailop  On Behalf Of Scott Mutter via mailop
Sent: Tuesday, August 17, 2021 1:44 PM
To: mailop@mailop.org
Subject: Re: [mailop] [EXTERNAL] Re: Vade - Blacklisting

Thanks guys!  This all seems to be resolved now.  At least with Comcast - it 
would seem they were kind enough to allow an exemption for our IP address in 
this.  But I suspect any other mail server that is utilizing Vade we may run 
into this issue with them as well.

Appreciate others checking and verifying that they were not seeing any spam 
from this IP.  I know too well that spamming incidents can happen, but when 
they do I can usually tell because the IP is blocked with numerous lists and 
services.  And in those cases I very much understand why it's listed.  I do 
what I can to prevent these spamming incidents, but unfortunately some fall 
through the cracks every now and then.

Unfortunate that an entire class C was listed in this.  It might be important 
to note that a lot of providers further split up that class C into multiple 
entities and then delegate those IPs out to others for use.  I guess desperate 
times call for desperate measures which leads to a class C listing.  But seldom 
is it all 256 IPs in the class C that are a part of the abuse.

On Tue, Aug 17, 2021 at 9:23 AM Brotman, Alex 
mailto:alex_brot...@comcast.com>> wrote:
Comcast utilizes an RBL supplied by Vade, as the URL indicated.  This has been 
remediated as of early this morning, and it was noted that it wasn’t a single 
IP in the /24 that was to blame (I don’t have more information than that 
currently).

--
Alex Brotman
Sr. Engineer, Anti-Abuse & Messaging Policy
Comcast

From: mailop mailto:mailop-boun...@mailop.org>> On 
Behalf Of Scott Mutter via mailop
Sent: Monday, August 16, 2021 9:08 PM
To: mailop@mailop.org
Subject: Re: [mailop] [EXTERNAL] Re: Vade - Blacklisting

Thanks Alex.

This looks to be working now.

Was this being blocked by Comcast or by Vade?

Unfortunately I don't have services or access to the whole /24.  Tis a shame 
that an entire Class-C had to be blocked.

On Mon, Aug 16, 2021 at 2:55 PM Brotman, Alex 
mailto:alex_brot...@comcast.com>> wrote:
Not sure why my response didn’t go to the list:

Scott,

It looks like the /24 is blocked, and I’ll see if I can find out why (I’ll 
reply off-list with that info).  In the meantime, we’ll put in an exemption for 
the range.  That should be in place shortly.




--
Alex Brotman
Sr. Engineer, Anti-Abuse & Messaging Policy
Comcast

From: mailop mailto:mailop-boun...@mailop.org>> On 
Behalf Of Scott Mutter via mailop
Sent: Monday, August 16, 2021 2:25 PM
To: mailop@mailop.org
Subject: [EXTERNAL] Re: [mailop] Vade - Blacklisting

Got the response:


Hello,

Thank you for your report.
It has been taken into account in our continuous improvement processus. We will 
get back to you if necessary.
Please note that the analysis may take a few days and your situation might 
improve in the meantime.
We advise you to keep an eye on your performance.

Regards

Your Anti-Abuse Vade team.



And it's still blocked.

Apologies because I'm probably not in the right state of mind right now.  This 
is kind of a tipping point for me right now.  Just really frustrated at 
providers like this that feel they can hold us hostage simply because we're not 
Microsoft, or Yahoo, or Google.

I mean, if the IP is really sending out spam (why is it not on any other 
blacklist?) then I want to know.  I want to remedy the situation.  But to block 
an IP for no reason.  To refuse to unblock an IP for no reason.  ... Why is a 
reputable company like Comcast (?) going to bed with such an entity?

On Mon, Aug 16, 2021 at 1:03 PM Al Iverson 
mailto:aiver...@wombatmail.com>> wrote:
You might find 
https://sendertool.vadesecure.com/
 to be a better way
to work through the issue.

Good luck,
Al Iverson

On Mon, Aug 16, 2021 at 12:24 PM Scott Mutter via mailop
mailto:mailop@mailop.org>> wrote:
>
> Anybody from Vade on the list able to give any details as to why 
> 66.11.124.112 is listed?
>
> Apparently Comcast uses Vade as part of their blacklist and this IP is being 
> blocked by Comcast's mail servers
>
> 554 resimta-po-40v.sys.comcast.net 
> resimta-po-40v.sys.comcast.net 
> 66.11.124.112 found on one or more DNSBLs, see 
> http://postmaster.comcast.net/smtp-error-codes.php#BL001000
>
> Going to 
> 

Re: [mailop] [EXTERNAL] Re: Vade - Blacklisting

[John Devine via mailop]

I have fallen foul of this with IP’s from Hyperoptic in the UK, I was forever 
tying to clear an IP because the block was being listed, in the end I just gave 
up and used a tunnel with an IP from a reputable ISP

John Devine

> On 17 Aug 2021, at 18:43, Scott Mutter via mailop  wrote:
> 
> Thanks guys!  This all seems to be resolved now.  At least with Comcast - it 
> would seem they were kind enough to allow an exemption for our IP address in 
> this.  But I suspect any other mail server that is utilizing Vade we may run 
> into this issue with them as well.
> 
> Appreciate others checking and verifying that they were not seeing any spam 
> from this IP.  I know too well that spamming incidents can happen, but when 
> they do I can usually tell because the IP is blocked with numerous lists and 
> services.  And in those cases I very much understand why it's listed.  I do 
> what I can to prevent these spamming incidents, but unfortunately some fall 
> through the cracks every now and then.
> 
> Unfortunate that an entire class C was listed in this.  It might be important 
> to note that a lot of providers further split up that class C into multiple 
> entities and then delegate those IPs out to others for use.  I guess 
> desperate times call for desperate measures which leads to a class C listing. 
>  But seldom is it all 256 IPs in the class C that are a part of the abuse.
> 
> On Tue, Aug 17, 2021 at 9:23 AM Brotman, Alex  > wrote:
> Comcast utilizes an RBL supplied by Vade, as the URL indicated.  This has 
> been remediated as of early this morning, and it was noted that it wasn’t a 
> single IP in the /24 that was to blame (I don’t have more information than 
> that currently).
> 
>  
> 
> --
> 
> Alex Brotman
> 
> Sr. Engineer, Anti-Abuse & Messaging Policy
> 
> Comcast
> 
>  
> 
> From: mailop mailto:mailop-boun...@mailop.org>> 
> On Behalf Of Scott Mutter via mailop
> Sent: Monday, August 16, 2021 9:08 PM
> To: mailop@mailop.org 
> Subject: Re: [mailop] [EXTERNAL] Re: Vade - Blacklisting
> 
>  
> 
> Thanks Alex.
> 
>  
> 
> This looks to be working now.
> 
>  
> 
> Was this being blocked by Comcast or by Vade?
> 
>  
> 
> Unfortunately I don't have services or access to the whole /24.  Tis a shame 
> that an entire Class-C had to be blocked.
> 
>  
> 
> On Mon, Aug 16, 2021 at 2:55 PM Brotman, Alex  > wrote:
> 
> Not sure why my response didn’t go to the list:
> 
>  
> 
> Scott,
> 
>  
> 
> It looks like the /24 is blocked, and I’ll see if I can find out why (I’ll 
> reply off-list with that info).  In the meantime, we’ll put in an exemption 
> for the range.  That should be in place shortly.
> 
>  
> 
>  
> 
>  
> 
>  
> 
> --
> 
> Alex Brotman
> 
> Sr. Engineer, Anti-Abuse & Messaging Policy
> 
> Comcast
> 
>  
> 
> From: mailop mailto:mailop-boun...@mailop.org>> 
> On Behalf Of Scott Mutter via mailop
> Sent: Monday, August 16, 2021 2:25 PM
> To: mailop@mailop.org 
> Subject: [EXTERNAL] Re: [mailop] Vade - Blacklisting
> 
>  
> 
> Got the response:
> 
>  
> 
> Hello,
> 
> Thank you for your report.
> It has been taken into account in our continuous improvement processus. We 
> will get back to you if necessary.
> Please note that the analysis may take a few days and your situation might 
> improve in the meantime. 
> We advise you to keep an eye on your performance.
> 
> Regards
> 
> Your Anti-Abuse Vade team.
> 
>  
> 
> And it's still blocked.
> 
> Apologies because I'm probably not in the right state of mind right now.  
> This is kind of a tipping point for me right now.  Just really frustrated at 
> providers like this that feel they can hold us hostage simply because we're 
> not Microsoft, or Yahoo, or Google.
> 
> I mean, if the IP is really sending out spam (why is it not on any other 
> blacklist?) then I want to know.  I want to remedy the situation.  But to 
> block an IP for no reason.  To refuse to unblock an IP for no reason.  ... 
> Why is a reputable company like Comcast (?) going to bed with such an entity?
> 
>  
> 
> On Mon, Aug 16, 2021 at 1:03 PM Al Iverson  > wrote:
> 
> You might find https://sendertool.vadesecure.com/ 
> 
>  to be a better way
> to work through the issue.
> 
> Good luck,
> Al Iverson
> 
> On Mon, Aug 16, 2021 at 12:24 PM Scott Mutter via mailop
> mailto:mailop@mailop.org>> wrote:
> >
> > Anybody from Vade on the list able to give any details as to why 
> > 66.11.124.112 is listed?
> >
> > Apparently Comcast uses Vade as part of their blacklist and this IP is 
> > being blocked by Comcast's mail servers
> >
> > 554 resimta-po-40v.sys.comcast.net  
> > resimta-po-40v.sys.comcast.net 

Re: [mailop] [EXTERNAL] Re: Vade - Blacklisting

[Scott Mutter via mailop]

Thanks guys!  This all seems to be resolved now.  At least with Comcast -
it would seem they were kind enough to allow an exemption for our IP
address in this.  But I suspect any other mail server that is utilizing
Vade we may run into this issue with them as well.

Appreciate others checking and verifying that they were not seeing any spam
from this IP.  I know too well that spamming incidents can happen, but when
they do I can usually tell because the IP is blocked with numerous lists
and services.  And in those cases I very much understand why it's listed.
I do what I can to prevent these spamming incidents, but unfortunately some
fall through the cracks every now and then.

Unfortunate that an entire class C was listed in this.  It might be
important to note that a lot of providers further split up that class C
into multiple entities and then delegate those IPs out to others for use.
I guess desperate times call for desperate measures which leads to a class
C listing.  But seldom is it all 256 IPs in the class C that are a part of
the abuse.

On Tue, Aug 17, 2021 at 9:23 AM Brotman, Alex 
wrote:

> Comcast utilizes an RBL supplied by Vade, as the URL indicated.  This has
> been remediated as of early this morning, and it was noted that it wasn’t a
> single IP in the /24 that was to blame (I don’t have more information than
> that currently).
>
>
>
> --
>
> Alex Brotman
>
> Sr. Engineer, Anti-Abuse & Messaging Policy
>
> Comcast
>
>
>
> *From:* mailop  *On Behalf Of *Scott Mutter
> via mailop
> *Sent:* Monday, August 16, 2021 9:08 PM
> *To:* mailop@mailop.org
> *Subject:* Re: [mailop] [EXTERNAL] Re: Vade - Blacklisting
>
>
>
> Thanks Alex.
>
>
>
> This looks to be working now.
>
>
>
> Was this being blocked by Comcast or by Vade?
>
>
>
> Unfortunately I don't have services or access to the whole /24.  Tis a
> shame that an entire Class-C had to be blocked.
>
>
>
> On Mon, Aug 16, 2021 at 2:55 PM Brotman, Alex 
> wrote:
>
> Not sure why my response didn’t go to the list:
>
>
>
> Scott,
>
>
>
> It looks like the /24 is blocked, and I’ll see if I can find out why (I’ll
> reply off-list with that info).  In the meantime, we’ll put in an exemption
> for the range.  That should be in place shortly.
>
>
>
>
>
>
>
>
>
> --
>
> Alex Brotman
>
> Sr. Engineer, Anti-Abuse & Messaging Policy
>
> Comcast
>
>
>
> *From:* mailop  *On Behalf Of *Scott Mutter
> via mailop
> *Sent:* Monday, August 16, 2021 2:25 PM
> *To:* mailop@mailop.org
> *Subject:* [EXTERNAL] Re: [mailop] Vade - Blacklisting
>
>
>
> Got the response:
>
>
>
> *Hello,*
>
>
>
>
> *Thank you for your report. It has been taken into account in our
> continuous improvement processus. We will get back to you if necessary.
> Please note that the analysis may take a few days and your situation might
> improve in the meantime. We advise you to keep an eye on your performance.*
>
> *Regards*
>
> *Your Anti-Abuse Vade team.*
>
>
>
> And it's still blocked.
>
> Apologies because I'm probably not in the right state of mind right now.
> This is kind of a tipping point for me right now.  Just really frustrated
> at providers like this that feel they can hold us hostage simply because
> we're not Microsoft, or Yahoo, or Google.
>
> I mean, if the IP is really sending out spam (why is it not on any other
> blacklist?) then I want to know.  I want to remedy the situation.  But to
> block an IP for no reason.  To refuse to unblock an IP for no reason.  ...
> Why is a reputable company like Comcast (?) going to bed with such an
> entity?
>
>
>
> On Mon, Aug 16, 2021 at 1:03 PM Al Iverson 
> wrote:
>
> You might find https://sendertool.vadesecure.com/
> 
> to be a better way
> to work through the issue.
>
> Good luck,
> Al Iverson
>
> On Mon, Aug 16, 2021 at 12:24 PM Scott Mutter via mailop
>  wrote:
> >
> > Anybody from Vade on the list able to give any details as to why
> 66.11.124.112 is listed?
> >
> > Apparently Comcast uses Vade as part of their blacklist and this IP is
> being blocked by Comcast's mail servers
> >
> > 554 resimta-po-40v.sys.comcast.net resimta-po-40v.sys.comcast.net
> 66.11.124.112 found on one or more DNSBLs, see
> http://postmaster.comcast.net/smtp-error-codes.php#BL001000
> 
> >
> > Going to http://postmaster.comcast.net/smtp-error-codes.php#BL001000
> 
> leads to a spill where they pass the buck to Vade.
> >
> > Would really like to know why this IP is listed with Vade.  Or does Vade
> just add IPs to their blacklist because they can?
> > 

Re: [mailop] [EXTERNAL] Re: Vade - Blacklisting

[Brotman, Alex via mailop]

Comcast utilizes an RBL supplied by Vade, as the URL indicated.  This has been 
remediated as of early this morning, and it was noted that it wasn’t a single 
IP in the /24 that was to blame (I don’t have more information than that 
currently).

--
Alex Brotman
Sr. Engineer, Anti-Abuse & Messaging Policy
Comcast

From: mailop  On Behalf Of Scott Mutter via mailop
Sent: Monday, August 16, 2021 9:08 PM
To: mailop@mailop.org
Subject: Re: [mailop] [EXTERNAL] Re: Vade - Blacklisting

Thanks Alex.

This looks to be working now.

Was this being blocked by Comcast or by Vade?

Unfortunately I don't have services or access to the whole /24.  Tis a shame 
that an entire Class-C had to be blocked.

On Mon, Aug 16, 2021 at 2:55 PM Brotman, Alex 
mailto:alex_brot...@comcast.com>> wrote:
Not sure why my response didn’t go to the list:

Scott,

It looks like the /24 is blocked, and I’ll see if I can find out why (I’ll 
reply off-list with that info).  In the meantime, we’ll put in an exemption for 
the range.  That should be in place shortly.




--
Alex Brotman
Sr. Engineer, Anti-Abuse & Messaging Policy
Comcast

From: mailop mailto:mailop-boun...@mailop.org>> On 
Behalf Of Scott Mutter via mailop
Sent: Monday, August 16, 2021 2:25 PM
To: mailop@mailop.org
Subject: [EXTERNAL] Re: [mailop] Vade - Blacklisting

Got the response:


Hello,

Thank you for your report.
It has been taken into account in our continuous improvement processus. We will 
get back to you if necessary.
Please note that the analysis may take a few days and your situation might 
improve in the meantime.
We advise you to keep an eye on your performance.

Regards

Your Anti-Abuse Vade team.



And it's still blocked.

Apologies because I'm probably not in the right state of mind right now.  This 
is kind of a tipping point for me right now.  Just really frustrated at 
providers like this that feel they can hold us hostage simply because we're not 
Microsoft, or Yahoo, or Google.

I mean, if the IP is really sending out spam (why is it not on any other 
blacklist?) then I want to know.  I want to remedy the situation.  But to block 
an IP for no reason.  To refuse to unblock an IP for no reason.  ... Why is a 
reputable company like Comcast (?) going to bed with such an entity?

On Mon, Aug 16, 2021 at 1:03 PM Al Iverson 
mailto:aiver...@wombatmail.com>> wrote:
You might find 
https://sendertool.vadesecure.com/
 to be a better way
to work through the issue.

Good luck,
Al Iverson

On Mon, Aug 16, 2021 at 12:24 PM Scott Mutter via mailop
mailto:mailop@mailop.org>> wrote:
>
> Anybody from Vade on the list able to give any details as to why 
> 66.11.124.112 is listed?
>
> Apparently Comcast uses Vade as part of their blacklist and this IP is being 
> blocked by Comcast's mail servers
>
> 554 resimta-po-40v.sys.comcast.net 
> resimta-po-40v.sys.comcast.net 
> 66.11.124.112 found on one or more DNSBLs, see 
> http://postmaster.comcast.net/smtp-error-codes.php#BL001000
>
> Going to 
> http://postmaster.comcast.net/smtp-error-codes.php#BL001000
>  leads to a spill where they pass the buck to Vade.
>
> Would really like to know why this IP is listed with Vade.  Or does Vade just 
> add IPs to their blacklist because they can?
> ___
> mailop mailing list
> mailop@mailop.org
> https://list.mailop.org/listinfo/mailop



--
Al Iverson // Wombatmail // Chicago
Deliverability: 
https://spamresource.com
DNS Tools: 
https://xnnd.com
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop