[mailop] Does Yahoo deferring mails ?

2017-03-30 Thread Yves-Marie Le Pors Chauvel 
Hi,

I've just show that Yahoo seems to defer many mails since one hour. This is
the exact same from all my IPs

All messages are :

Mar 30 09:38:15 lxc-postfix-front-19 postfix-smtp56/smtp[1403]:
87CFE4C2BFC0C: to=,
relay=mx-eu.mail.am0.yahoodns.net[188.125.69.79]:25,
delay=2.1, delays=0.13/0/0.22/1.8, dsn=4.0.0, status=deferred (host
mx-eu.mail.am0.yahoodns.net[188.125.69.79] said: 451 Resources temporarily
not available - Please try again later [#4.16.5]. (in reply to end of DATA
command))

Mar 30 09:18:01 vz-postfix-front-06 postfix-smtp43/smtp[27014]:
6B3856383F933: to=,
relay=mx-eu.mail.am0.yahoodns.net[188.125.69.79]:25,
delay=0.23, delays=0.08/0/0.13/0.02, dsn=4.3.2, status=deferred (host
mx-eu.mail.am0.yahoodns.net[188.125.69.79] said: 451 4.3.2 Internal error
reading data (in reply to MAIL FROM command))--

Does any one have the same messages ?

Regards,
Yves-Marie LE PORS-CHAUVEL
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Does Yahoo deferring mails ?

2017-03-30 Thread Stefano Bagnara 
Stats from 9 to 10 (CET) from my IPs:

6171: "250 ok dirdel"
  53: "451 4.3.2 Internal error reading data" in reply to the MAIL FROM
command.
  96: "451 Resources temporarily not available - Please try again later
[#4.16.5]." in reply to "."
   5: "421 4.7.0 [GL01] Message from () temporarily deferred -
4.16.50. Please refer to
http://postmaster.yahoo.com/errors/postmaster-21.html  in reply to MAIL FROM

So, less than 3% of messages fails with the 2 errors you saw.
Looking at past logs it is not unusual and I see a similar occourence also
in the past weekdays.

Stefano

On 30 March 2017 at 09:47, Yves-Marie Le Pors Chauvel <
ym.leporschau...@ccmbenchmark.com> wrote:

> Hi,
>
> I've just show that Yahoo seems to defer many mails since one hour. This
> is the exact same from all my IPs
>
> All messages are :
>
> Mar 30 09:38:15 lxc-postfix-front-19 postfix-smtp56/smtp[1403]:
> 87CFE4C2BFC0C: to=, 
> relay=mx-eu.mail.am0.yahoodns.net[188.125.69.79]:25,
> delay=2.1, delays=0.13/0/0.22/1.8, dsn=4.0.0, status=deferred (host
> mx-eu.mail.am0.yahoodns.net[188.125.69.79] said: 451 Resources
> temporarily not available - Please try again later [#4.16.5]. (in reply to
> end of DATA command))
>
> Mar 30 09:18:01 vz-postfix-front-06 postfix-smtp43/smtp[27014]:
> 6B3856383F933: to=, relay=mx-eu.mail.am0.yahoodns.
> net[188.125.69.79]:25, delay=0.23, delays=0.08/0/0.13/0.02, dsn=4.3.2,
> status=deferred (host mx-eu.mail.am0.yahoodns.net[188.125.69.79] said:
> 451 4.3.2 Internal error reading data (in reply to MAIL FROM command))--
>
> Does any one have the same messages ?
>
> Regards,
> Yves-Marie LE PORS-CHAUVEL
>
>
> ___
> 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] AOL not accepting mail tonight?

2017-03-30 Thread Lili Crowley 
I've been asked a couple of times, so want to state:

Bounces from yesterday evening's outage should not be unsubbed. They were
550s but that was us and not you guys.

Thanks!

Lili Crowley
AOL Postmaster


On Wed, Mar 29, 2017 at 11:12 PM, Toshiaki Onishi via mailop <
mailop@mailop.org> wrote:

> Same here, thanks!
>
> On Thu, Mar 30, 2017 at 1:57 PM, James Carbone  wrote:
>
>> Yes much better, thanks!
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> We are looking better here now.
>>
>> You should be seeing improvement (I hope)
>>
>>
>>
>> Lili Crowley
>> AOL Postmaster
>>
>>
>> On Wed, Mar 29, 2017 at 9:11 PM, Toshiaki Onishi via mailop <
>> mailop@mailop.org> wrote:
>>
>> Hi Tara
>>
>> I'm seeing the same thing over here as well.
>>
>> Regards
>>
>> Toshi
>>
>> On Thu, Mar 30, 2017 at 11:59 AM, Tara Natanson 
>> wrote:
>>
>> Anyone else having all mail to AOL rejected for the last hour?
>>
>>
>> Mar 29 20:45:12 p2-lvmail11 lsb1-99-208-250/smtp[22251]:
>> A88DFC2DBE9: to=, relay=mailin-01.mx.aol.com[64.
>> 12.91.195]:25, delay=0.18, delays=0.01/0/0.14/0.03, dsn=5.1.1,
>> status=bounced (host mailin-01.mx.aol.com[64.12.91. 195] said: 550 5.1.1
>> : Recipient address rejected: aol.com (in reply to
>> RCPT TO command))
>>
>> Tara Natanson
>> (Constant Contact)
>>
>> __ _
>> mailop mailing list
>> mailop@mailop.org
>> https://chilli.nosignal.org/cg i-bin/mailman/listinfo/mailop
>>
>>
>>
>>
>> --
>> Toshiaki Onishi
>>
>> Email Operations Specialist, APAC
>>
>> D +61 2 8277 6938 <+61%202%208277%206938>
>> M +61 404 882 045 <+61%20404%20882%20045>
>> toni...@groupon.com
>>
>> __ _
>> 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
>>
>> Download
>> 2 .txt
>>
>>
>>
>> ___
>> mailop mailing list
>> mailop@mailop.org
>> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
>>
>>
>
>
> --
> *Toshiaki Onishi*
>
> *Email Operations Specialist, APAC*
>
> *D* +61 2 8277 6938 <%2B61%202%208277%206902>
> *M* +61 404 882 045 <%2B61%C2%A0466%20792%20857>
> *toni...@groupon.com *
>
> ___
> 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] AOL not accepting mail tonight?

2017-03-30 Thread Brett Schenker 
Do we have a rough time frame that this happened? We need to reset the
mailable status of these aol addresses and don't want to change folks who
were legitimately marked. Thanks.

Brett

On Thu, Mar 30, 2017 at 11:43 AM, Lili Crowley 
wrote:

> I've been asked a couple of times, so want to state:
>
> Bounces from yesterday evening's outage should not be unsubbed. They were
> 550s but that was us and not you guys.
>
> Thanks!
>
> Lili Crowley
> AOL Postmaster
>
>
> On Wed, Mar 29, 2017 at 11:12 PM, Toshiaki Onishi via mailop <
> mailop@mailop.org> wrote:
>
>> Same here, thanks!
>>
>> On Thu, Mar 30, 2017 at 1:57 PM, James Carbone  wrote:
>>
>>> Yes much better, thanks!
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> We are looking better here now.
>>>
>>> You should be seeing improvement (I hope)
>>>
>>>
>>>
>>> Lili Crowley
>>> AOL Postmaster
>>>
>>>
>>> On Wed, Mar 29, 2017 at 9:11 PM, Toshiaki Onishi via mailop <
>>> mailop@mailop.org> wrote:
>>>
>>> Hi Tara
>>>
>>> I'm seeing the same thing over here as well.
>>>
>>> Regards
>>>
>>> Toshi
>>>
>>> On Thu, Mar 30, 2017 at 11:59 AM, Tara Natanson 
>>> wrote:
>>>
>>> Anyone else having all mail to AOL rejected for the last hour?
>>>
>>>
>>> Mar 29 20:45:12 p2-lvmail11 lsb1-99-208-250/smtp[22251]:
>>> A88DFC2DBE9: to=, relay=mailin-01.mx.aol.com[64.
>>> 12.91.195]:25, delay=0.18, delays=0.01/0/0.14/0.03, dsn=5.1.1,
>>> status=bounced (host mailin-01.mx.aol.com[64.12.91. 195] said: 550
>>> 5.1.1 : Recipient address rejected: aol.com (in reply
>>> to RCPT TO command))
>>>
>>> Tara Natanson
>>> (Constant Contact)
>>>
>>> __ _
>>> mailop mailing list
>>> mailop@mailop.org
>>> https://chilli.nosignal.org/cg i-bin/mailman/listinfo/mailop
>>>
>>>
>>>
>>>
>>> --
>>> Toshiaki Onishi
>>>
>>> Email Operations Specialist, APAC
>>>
>>> D +61 2 8277 6938 <+61%202%208277%206938>
>>> M +61 404 882 045 <+61%20404%20882%20045>
>>> toni...@groupon.com
>>>
>>> __ _
>>> 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
>>>
>>> Download
>>> 2 .txt
>>>
>>>
>>>
>>> ___
>>> mailop mailing list
>>> mailop@mailop.org
>>> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
>>>
>>>
>>
>>
>> --
>> *Toshiaki Onishi*
>>
>> *Email Operations Specialist, APAC*
>>
>> *D* +61 2 8277 6938
>> <%2B61%202%208277%206902>
>> *M* +61 404 882 045 <%2B61%C2%A0466%20792%20857>
>> *toni...@groupon.com *
>>
>> ___
>> 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
>
>


-- 
Brett Schenker
Man of Many Things, Including
5B Consulting - http://www.5bconsulting.com
Graphic Policy - http://www.graphicpolicy.com

Twitter - http://twitter.com/bhschenker
LinkedIn - http://www.linkedin.com/in/brettschenker
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] AOL not accepting mail tonight?

2017-03-30 Thread Tara Natanson 
We had to do the same thing and used the timeframe of 7:45-9:15pm eastern
time.  That pretty much covers it.  but if you search your logs for
"recipient address rejected" you'll see the huge spike for AOL at that
time.

Tara Natanson
(Constant Contact)

On Thu, Mar 30, 2017 at 12:10 PM, Brett Schenker 
wrote:

> Do we have a rough time frame that this happened? We need to reset the
> mailable status of these aol addresses and don't want to change folks who
> were legitimately marked. Thanks.
>
> Brett
>
> On Thu, Mar 30, 2017 at 11:43 AM, Lili Crowley 
> wrote:
>
>> I've been asked a couple of times, so want to state:
>>
>> Bounces from yesterday evening's outage should not be unsubbed. They were
>> 550s but that was us and not you guys.
>>
>> Thanks!
>>
>> Lili Crowley
>> AOL Postmaster
>>
>>
>> On Wed, Mar 29, 2017 at 11:12 PM, Toshiaki Onishi via mailop <
>> mailop@mailop.org> wrote:
>>
>>> Same here, thanks!
>>>
>>> On Thu, Mar 30, 2017 at 1:57 PM, James Carbone  wrote:
>>>
 Yes much better, thanks!











 We are looking better here now.

 You should be seeing improvement (I hope)



 Lili Crowley
 AOL Postmaster


 On Wed, Mar 29, 2017 at 9:11 PM, Toshiaki Onishi via mailop <
 mailop@mailop.org> wrote:

 Hi Tara

 I'm seeing the same thing over here as well.

 Regards

 Toshi

 On Thu, Mar 30, 2017 at 11:59 AM, Tara Natanson <
 tar...@natanson.net> wrote:

 Anyone else having all mail to AOL rejected for the last hour?


 Mar 29 20:45:12 p2-lvmail11 lsb1-99-208-250/smtp[22251]:
 A88DFC2DBE9: to=, relay=mailin-01.mx.aol.com[64.
 12.91.195]:25, delay=0.18, delays=0.01/0/0.14/0.03, dsn=5.1.1,
 status=bounced (host mailin-01.mx.aol.com[64.12.91. 195] said: 550
 5.1.1 : Recipient address rejected: aol.com (in
 reply to RCPT TO command))

 Tara Natanson
 (Constant Contact)

 __ _
 mailop mailing list
 mailop@mailop.org
 https://chilli.nosignal.org/cg i-bin/mailman/listinfo/mailop




 --
 Toshiaki Onishi

 Email Operations Specialist, APAC

 D +61 2 8277 6938 <+61%202%208277%206938>
 M +61 404 882 045 <+61%20404%20882%20045>
 toni...@groupon.com

 __ _
 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

 Download
 2 .txt



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


>>>
>>>
>>> --
>>> *Toshiaki Onishi*
>>>
>>> *Email Operations Specialist, APAC*
>>>
>>> *D* +61 2 8277 6938
>>> <%2B61%202%208277%206902>
>>> *M* +61 404 882 045 <%2B61%C2%A0466%20792%20857>
>>> *toni...@groupon.com *
>>>
>>> ___
>>> 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
>>
>>
>
>
> --
> Brett Schenker
> Man of Many Things, Including
> 5B Consulting - http://www.5bconsulting.com
> Graphic Policy - http://www.graphicpolicy.com
>
> Twitter - http://twitter.com/bhschenker
> LinkedIn - http://www.linkedin.com/in/brettschenker
>
> ___
> 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] Spamhaus CSS listings of normal mail servers?

2017-03-30 Thread Robert L Mathews 
On 3/29/17 2:52 PM, Larry M. Smith wrote:

> "If you are authoritative for an IP address and you believe the issues
> that caused the listing have been solved, you can [request a delisting]."
> 
> Doesn't work for you?

Yes, it works great! But then we'd get re-listed a few hours later
because the underlying cause was still present.

Anyway, I've finally talked to the CSS folks at Spamhaus and found the
cause of this, and it was mostly self-inflicted. Details below in case
others have the same problem.

When sending to some destinations, our outbound mail servers used
multiple HELO/EHLO hostnames under tigertech.net, depending on the
source of the message internally, and it could further vary over time.
The reasons are boring and stupid; "it fixed an obscure problem in 2006
and we never stopped doing it".

The hostnames were valid in terms of RFC 2821 and had working DNS, but
certain recipients treat multiple HELO hostnames from the same IP
address within a short period with suspicion, because it's one
characteristic of snowshoe spam.

So when one of our IP addresses randomly happened to send more than
[some number of messages per minute] to a certain large ISP using
multiple HELO names, they were flagged as potential snowshoe spam
(despite being normal, often non-bulk messages). This was reported to
the CSS algorithm.

It further turns out that one of our customers sent a message to a
Spamhaus spamtrap on March 6, lowering the reputation of our netblock
just enough that the combination led to a CSS listing each time.
"Hilarity ensued."

Removing the multiple HELO hostnames from a single IP address solved it.
Don't do that. I should have known better, because our own anti-spam
point scoring system penalizes senders for this same thing (although it
uses the Public Suffix List to avoid flagging different hostnames under
the same registered domain name, which avoids this particular problem).

However, I know others do this, perhaps as a side-effect of a NAT setup
that has many different servers behind a single IP address. If that
describes you, it would be wise to ensure that all the servers or
instances consistently and permanently use the same HELO name.

Thanks to everyone who offered help with this; it was much appreciated.
I hope this description helps someone else.

-- 
Robert L Mathews, Tiger Technologies, http://www.tigertech.net/

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

Re: [mailop] Spamhaus CSS listings of normal mail servers?

2017-03-30 Thread Paul Kincaid-Smith 
Robert, thanks for explaining the root cause of your Spamhaus CSS problem
and what you changed to fix it. I appreciate your generosity to share what
you learned -- helpful insights for the rest of us, and testimony to the
collaborative value of this Mailop list.

On Thu, Mar 30, 2017 at 10:50 AM, Robert L Mathews 
wrote:

> On 3/29/17 2:52 PM, Larry M. Smith wrote:
>
> > "If you are authoritative for an IP address and you believe the issues
> > that caused the listing have been solved, you can [request a delisting]."
> >
> > Doesn't work for you?
>
> Yes, it works great! But then we'd get re-listed a few hours later
> because the underlying cause was still present.
>
> Anyway, I've finally talked to the CSS folks at Spamhaus and found the
> cause of this, and it was mostly self-inflicted. Details below in case
> others have the same problem.
>
> When sending to some destinations, our outbound mail servers used
> multiple HELO/EHLO hostnames under tigertech.net, depending on the
> source of the message internally, and it could further vary over time.
> The reasons are boring and stupid; "it fixed an obscure problem in 2006
> and we never stopped doing it".
>
> The hostnames were valid in terms of RFC 2821 and had working DNS, but
> certain recipients treat multiple HELO hostnames from the same IP
> address within a short period with suspicion, because it's one
> characteristic of snowshoe spam.
>
> So when one of our IP addresses randomly happened to send more than
> [some number of messages per minute] to a certain large ISP using
> multiple HELO names, they were flagged as potential snowshoe spam
> (despite being normal, often non-bulk messages). This was reported to
> the CSS algorithm.
>
> It further turns out that one of our customers sent a message to a
> Spamhaus spamtrap on March 6, lowering the reputation of our netblock
> just enough that the combination led to a CSS listing each time.
> "Hilarity ensued."
>
> Removing the multiple HELO hostnames from a single IP address solved it.
> Don't do that. I should have known better, because our own anti-spam
> point scoring system penalizes senders for this same thing (although it
> uses the Public Suffix List to avoid flagging different hostnames under
> the same registered domain name, which avoids this particular problem).
>
> However, I know others do this, perhaps as a side-effect of a NAT setup
> that has many different servers behind a single IP address. If that
> describes you, it would be wise to ensure that all the servers or
> instances consistently and permanently use the same HELO name.
>
> Thanks to everyone who offered help with this; it was much appreciated.
> I hope this description helps someone else.
>
> --
> Robert L Mathews, Tiger Technologies, http://www.tigertech.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] QQ form submission question

2017-03-30 Thread Josh Nason 
Has anyone had any success submitting an inquiry at the following site for
QQ postmaster inquiries? The captcha keeps failing, so I'm assuming it may
simply not work anymore.

http://mail.qq.com/feedback_enterprise.html

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

[mailop] AWeber DKIM

2017-03-30 Thread Dave Warren 
Howdy! We push a DMARC reject policy for our clients unless they have a
need to do otherwise, especially for new projects/domains, so that we
can proactively help clients move toward authenticating all mail as they
add external services rather than building an ongoing technical debt of
unknown senders.

One of my customers has signed up with AWeber, but AWeber won't let her
use an address at her domain citing the DMARC reject policy. This seemed
like a good thing initially as it means they're at least aware of DMARC,
but she wasn't able to find anything about DKIM in her control panel and
when she opened a ticket asking how to set up DKIM she got back is "We
do not provide a DKIM record for you, as all mail is sent from our
servers.  Any emails sent from your AWeber account are not sent from
your servers directly."

I'm feeling like the rep has absolutely no idea what DKIM is or how it
works. As I don't have access to an AWeber account, can anyone tell me
what (if any) support they have for SPF or DKIM signing?

It's a small enough client that it should be relatively harmless to
relax their DMARC policy, but I feel like this just kicks the proverbial
can down the road a bit.

Feel free to respond on- or off-list as appropriate if you can point me
in the right direction here.


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