Re: [mailop] TWC refusing mail

2017-12-17 Thread Scott Undercofler
Between outlook and .nl and .eu, we have been hammering away at spam the last 
few weeks so some senders have been, perhaps unfairly, caught up in the net. We 
weathered the holiday mail really well but have been pretty harsh on snowshoers 
and hit and run spammers. 

> On Dec 17, 2017, at 6:13 PM, Andrew Barrett  wrote:
> 
> I'm guessing that, like everyone else, TWC is just getting slammed with mail 
> sent by ESPs  for senders with holiday offers and the like, and is just not 
> as well equipped to handle it. Seems like every holiday season brings new 
> record volumes.
> 
>> On Sun, Dec 17, 2017 at 7:53 PM, Michael Rathbun  wrote:
>> On Mon, 18 Dec 2017 08:57:34 +1100, Mark Dale  wrote:
>> 
>> 
>> >Is it just us or are others experiencing this?
>> >
>> >Any clues as to why would be greatly appreciated.
>> 
>> We're seeing it, with a sudden onset on the 14th.  The IPs send requested
>> and/or transactional email, have excellent reputations, and are blocked
>> nowhere else.
>> 
>> The response is completely uncharacteristic of the rejections outlined on the
>> postmaster page.
>> 
>> The TWC IP reputation lookup gives clean bill of health.  Since there are no
>> blocks, no remediation can be requested.
>> 
>> mdr
>> --
>> The Duckage Is Feep.
>>-- Vaul Pixie
>> 
>> 
>> ___
>> 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
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


Re: [mailop] TWC refusing mail

2017-12-17 Thread Andrew Barrett
I'm guessing that, like everyone else, TWC is just getting slammed with
mail sent by ESPs  for senders with holiday offers and the like, and is
just not as well equipped to handle it. Seems like every holiday season
brings new record volumes.

On Sun, Dec 17, 2017 at 7:53 PM, Michael Rathbun  wrote:

> On Mon, 18 Dec 2017 08:57:34 +1100, Mark Dale 
> wrote:
>
>
> >Is it just us or are others experiencing this?
> >
> >Any clues as to why would be greatly appreciated.
>
> We're seeing it, with a sudden onset on the 14th.  The IPs send requested
> and/or transactional email, have excellent reputations, and are blocked
> nowhere else.
>
> The response is completely uncharacteristic of the rejections outlined on
> the
> postmaster page.
>
> The TWC IP reputation lookup gives clean bill of health.  Since there are
> no
> blocks, no remediation can be requested.
>
> mdr
> --
> The Duckage Is Feep.
>-- Vaul Pixie
>
>
> ___
> 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] TWC refusing mail

2017-12-17 Thread Michael Rathbun
On Mon, 18 Dec 2017 08:57:34 +1100, Mark Dale  wrote:


>Is it just us or are others experiencing this?
>
>Any clues as to why would be greatly appreciated.

We're seeing it, with a sudden onset on the 14th.  The IPs send requested
and/or transactional email, have excellent reputations, and are blocked
nowhere else.

The response is completely uncharacteristic of the rejections outlined on the
postmaster page.

The TWC IP reputation lookup gives clean bill of health.  Since there are no
blocks, no remediation can be requested.

mdr
-- 
The Duckage Is Feep.
   -- Vaul Pixie


___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


Re: [mailop] SPF recommendations

2017-12-17 Thread Noel Butler
On 15/12/2017 15:40, Brandon Long via mailop wrote:

> All that SPF authenticates is the RFC5321.From, which is rarely visible to 
> the end user and trivial for phishers to work around. 
> 
> Brandon

And its often all that's needed, no its not complete, no its not
perfect, but nothing ever is 

-- 
Kind Regards, 

Noel Butler 

This Email, including any attachments, may contain legally 
privileged
information, therefore remains confidential and subject to copyright
protected under international law. You may not disseminate, discuss, or
reveal, any part, to anyone, without the authors express written
authority to do so. If you are not the intended recipient, please notify
the sender then delete all copies of this message including attachments,
immediately. Confidentiality, copyright, and legal privilege are not
waived or lost by reason of the mistaken delivery of this message. Only
PDF [1] and ODF [2] documents accepted, please do not send proprietary
formatted documents 

 

Links:
--
[1] http://www.adobe.com/
[2] http://en.wikipedia.org/wiki/OpenDocument___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


Re: [mailop] SPF recommendations

2017-12-17 Thread Noel Butler
On 15/12/2017 14:28, John Levine wrote:

> In article <6582089ce2ad3fb3fd074ada73672...@ausics.net>,
> Noel Butler   wrote: 
> 
>> Agreed, if I publish a -all (which I do and have done for a very very
>> long time), I expect receivers doing SPF processing of my domains
>> messages, to honor that!  Who the hell are they to assume they know my
>> network and its senders better than me.
> 
> They don't know your network, but they know the junk that your users
> send them, some from your network, some from other places.

All the more reason to honor my -all 
If your not going to honor my decided polices, why bother with SPF,
DKIM, DMARC at all, or are you in favor of selective ignorance, either
way, everyone might as well stop using them all, right now if they take
the attitude of some around here. 

> I have a vision of small senders who publish -all as tiny gorillas,
> thumping their wee chests and bellowing "FEAR ME OH INTERNET" in their
> adorable high squeaky voices.

Some rather large gorilla's publish them as well :) 

> R's,
> John

errr I never asked the following, I know how it fails 

> PS:
> 
> How does DMARC fail at forwarding?
> Please review the previous million or so messages on this topic.

-- 
Kind Regards, 

Noel Butler 

This Email, including any attachments, may contain legally 
privileged
information, therefore remains confidential and subject to copyright
protected under international law. You may not disseminate, discuss, or
reveal, any part, to anyone, without the authors express written
authority to do so. If you are not the intended recipient, please notify
the sender then delete all copies of this message including attachments,
immediately. Confidentiality, copyright, and legal privilege are not
waived or lost by reason of the mistaken delivery of this message. Only
PDF [1] and ODF [2] documents accepted, please do not send proprietary
formatted documents 

 

Links:
--
[1] http://www.adobe.com/
[2] http://en.wikipedia.org/wiki/OpenDocument___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


Re: [mailop] TWC refusing mail

2017-12-17 Thread Mark Dale

Hi Scott,

I had missed that.  Just saw that SORBS have blacklisted the server.

Thanks,
Mark





On 18/12/17 09:36, Scott Undercofler wrote:

1010 is blacklisted. What ip space are you coming from?


On Dec 17, 2017, at 2:57 PM, Mark Dale  wrote:

Hi All,

We've recently started seeing mail get rejected ("deferred") by TWC.

An example error message in the mail log:

Dec 17 22:38:39 bissen postfix/smtp[27323]: 7ADBC2E851: 
to=, 
relay=dnvrco-cmedge02.email.rr.com[69.134.155.136]:25, delay=11160, 
delays=11159/0.12/0.88/0, dsn=4.0.0, status=deferred (host 
dnvrco-cmedge02.email.rr.com[69.134.155.136] refused to talk to me: 554 
dnvrco-cmimta02 esmtp ESMTP server not available AUP#I-1010)

The IP address in the log entry (69.134.155.136) is TWC

The Time Warner Cable Block Query website reports that they are not blocking 
mail from our server's IP and that our server's Return Path Sender Score 
Reputation Score = 99.

Is it just us or are others experiencing this?

Any clues as to why would be greatly appreciated.

Best,
Mark


--

MailmanLists - hosted discussion lists
Canberra, Australia
Tel: +61 .2 61003121
https://www.mailmanlists.net
===

___
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] TWC refusing mail

2017-12-17 Thread Scott Undercofler
1010 is blacklisted. What ip space are you coming from? 

> On Dec 17, 2017, at 2:57 PM, Mark Dale  wrote:
> 
> Hi All,
> 
> We've recently started seeing mail get rejected ("deferred") by TWC.
> 
> An example error message in the mail log:
> 
> Dec 17 22:38:39 bissen postfix/smtp[27323]: 7ADBC2E851: 
> to=, 
> relay=dnvrco-cmedge02.email.rr.com[69.134.155.136]:25, delay=11160, 
> delays=11159/0.12/0.88/0, dsn=4.0.0, status=deferred (host 
> dnvrco-cmedge02.email.rr.com[69.134.155.136] refused to talk to me: 554 
> dnvrco-cmimta02 esmtp ESMTP server not available AUP#I-1010)
> 
> The IP address in the log entry (69.134.155.136) is TWC
> 
> The Time Warner Cable Block Query website reports that they are not blocking 
> mail from our server's IP and that our server's Return Path Sender Score 
> Reputation Score = 99.
> 
> Is it just us or are others experiencing this?
> 
> Any clues as to why would be greatly appreciated.
> 
> Best,
> Mark
> 
> 
> -- 
> 
> MailmanLists - hosted discussion lists
> Canberra, Australia
> Tel: +61 .2 61003121
> https://www.mailmanlists.net
> ===
> 
> ___
> 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


[mailop] TWC refusing mail

2017-12-17 Thread Mark Dale

Hi All,

We've recently started seeing mail get rejected ("deferred") by TWC.

An example error message in the mail log:

Dec 17 22:38:39 bissen postfix/smtp[27323]: 7ADBC2E851: 
to=, 
relay=dnvrco-cmedge02.email.rr.com[69.134.155.136]:25, delay=11160, 
delays=11159/0.12/0.88/0, dsn=4.0.0, status=deferred (host 
dnvrco-cmedge02.email.rr.com[69.134.155.136] refused to talk to me: 554 
dnvrco-cmimta02 esmtp ESMTP server not available AUP#I-1010)


The IP address in the log entry (69.134.155.136) is TWC

The Time Warner Cable Block Query website reports that they are not 
blocking mail from our server's IP and that our server's Return Path 
Sender Score Reputation Score = 99.


Is it just us or are others experiencing this?

Any clues as to why would be greatly appreciated.

Best,
Mark


--

 MailmanLists - hosted discussion lists
 Canberra, Australia
 Tel: +61 .2 61003121
 https://www.mailmanlists.net
===

___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop