Re: Yahoo Postmaster or Email Admin

[Elizabeth Zwicky via NANOG]

Yes, yes I do. 

On Wednesday, July 27, 2016 9:44 AM, Josh Luthman 
<j...@imaginenetworksllc.com> wrote:
 

 Do you mean https://postmaster.yahoo.com/ ?

Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373
On Wed, Jul 27, 2016 at 12:39 PM, Elizabeth Zwicky via NANOG <nanog@nanog.org> 
wrote:

We encourage people to start at https://postmaster.yaho.com but I can help 
people who have filed tickets there and not had any luck can contact me, 
specifying a) what IP addresses and From: line they're talking about and b) 
exactly what error message they are getting when they try to send us mail.
Elizabeth
On Wednesday, July 27, 2016, 5:31:55 AM PDT, Mark Stevens 
<mana...@monmouth.com> wrote:Good Morning,

If there is a Yahoo postmaster or email Admin that could contact me
offline concerning a deferred IP address it would be great.


Thanks

Mark

Re: Yahoo Postmaster or Email Admin

[Elizabeth Zwicky via NANOG]

We encourage people to start at https://postmaster.yaho.com but I can help 
people who have filed tickets there and not had any luck can contact me, 
specifying a) what IP addresses and From: line they're talking about and b) 
exactly what error message they are getting when they try to send us mail.
Elizabeth
On Wednesday, July 27, 2016, 5:31:55 AM PDT, Mark Stevens 
 wrote:Good Morning,

If there is a Yahoo postmaster or email Admin that could contact me 
offline concerning a deferred IP address it would be great.


Thanks

Mark

Re: yahoo mta admin help needed

[Elizabeth Zwicky via NANOG]

Start by going to https://postmaster.yahoo.com and describing symptoms (they're 
not going to respond well to mentions of ACL blocks, and will want to know 
what's actually happening in SMTP).
Also, timeouts on the Yahoo side are also rare in the extreme, so if your 
problem is that attempts time out or vanish into a black hole, I would start 
troubleshooting elsewhere.
Elizabeth Zwicky

On Friday, July 1, 2016 12:27 PM, Lyndon Nerenberg <lyn...@orthanc.ca> 
wrote:
 

 Is there a Yahoo MTA admin listening who can help diagnose what might be a 
network ACL block to one of our SMTP server subnets?

Thanks,

--lyndon

Re: Looking for Yahoo eMail contact

[Elizabeth Zwicky via NANOG]

http://postmaster.yahoo.com, click on "Contact Us" at the top since your 
question isn't one of the giant ones in the middle of the page.
Elizabeth Zwicky 

On Monday, January 11, 2016 4:28 AM, Marc Storck <msto...@voipgate.com> 
wrote:
 

 Hello,

I’m looking for a Yahoo email administrator who could contact me offlist.

I have a customer with a clean record that is getting thsi error:

Error: "421 4.7.1 [TS03] All messages from x.x.x.x permanently deferred" when 
sending email to Yahoo

The customer is a local non-profit and sends a very limited amount of emails to 
members, suppliers and other contacts. Mailing-lists are only used to contact 
members of the NPO.

I checked the recommendation listed at
https://help.yahoo.com/kb/postmaster/SLN3436.html

and checked his IP address on several “multi-rbl” lookup sites. All looks clean.

So I need more input to understand what we need to correct.

Thank you very much in advance.

Best regards,

Marc

[no subject]

[Elizabeth Zwicky via NANOG]

---BeginMessage---
http://postmaster.yahoo.com will allow you to contact the postmaster team for 
assistance.
I've reported this error already, but fixing it won't help you any; basically, 
the web page without the link is all Yahoo's willing to publicly say about that 
error message, you'll need to talk to postmaster for help debugging your 
particular situation.
Elizabeth ZwickyYahoo Mail
 


 On Monday, April 27, 2015 2:02 PM, Matthew Black matthew.bl...@csulb.edu 
wrote:
   

 One of our user’s e-mail messages to Yahoo bounced with the following link for 
more information: http://postmaster.yahoo.com/errors/postmaster-27.html

which redirects to 
https://help.yahoo.com/kb/postmaster/SLN5067.html?impressions=true



That page contains a link to “Yahoo Mail and Yahoo Messenger Terms of Service”, 
which is broken!

http://https//info.yahoo.com/legal/us/yahoo/mail/en-us/http://https/info.yahoo.com/legal/us/yahoo/mail/en-us/

It redirects to an https link  saying, Server not found.



I hope someone from Yahoo can fix this.



matthew black

california state university, long beach





---End Message---

Re: why IPv6 isn't ready for prime time, SMTP edition

[Elizabeth Zwicky]

DMARC says nothing about rDNS, and given how late in the game
DMARC comes, it seems like an odd place to enforce rDNS.

Local policy, sure; local DMARC policy, wait what?

Elizabeth


On 3/25/14, 2:12 PM, Paul Ferguson fergdawgs...@mykolab.com wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Isn't this just a local policy issue with handling DMARC? I know for
sure at least one other (very large) organization that (also) rejects
messages which do not have an rDNS entry, and it is a local DMARC policy.

- - ferg

On 3/25/2014 1:57 PM, Brielle Bruns wrote:

 On 3/25/14, 11:56 AM, John Levine wrote:
 I think this would be a good time to fix your mail server setup.
 You're never going to get much v6 mail delivered without rDNS,
 because receivers won't even look at your mail to see if it's
 authenticated.
 
 CenturyLink is reasonably technically clued so it shouldn't be
 impossible to get them to fix it.
 
 
 Nothing wrong with my mail server setup, except the lack of RDNS.
 Lacking reverse should be one of many things to consider with
 rejecting e-mails, but should not be the only condition.
 
 That would be like outright refusing mail unless it had both SPF
 and DKIM on every single message.
 
 Sure, great in theory, does not work in reality and will result in
 lost mail from legit sources.
 
 Already spoken to CenturyLink about RDNS for ipv6 - won't have
 rdns until native IPv6.  Currently, IPv6 seems to be delivered for
 those who want it, via 6rd.
 
 And, frankly, I'm not going to get in a fight with CenturyLink over
 IPv6 RDNS, considering that I am thankful that they are even
 offering IPv6 when other large providers aren't even trying to do
 so to their residential and small business customers.
 
 It is very easy for some to forget that not everyone has a gigabit
 fiber connection to their homes with ARIN assigned IPv4/IPv6 blocks
 announced over BGP.  Some of us actually have to make do with
 (sometimes very) limited budgets and what the market is offering us
 and has made available.
 
 


- -- 
Paul Ferguson
VP Threat Intelligence, IID
PGP Public Key ID: 0x54DC85B2
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iF4EAREIAAYFAlMx8VQACgkQKJasdVTchbJkBgD+PeCiFIefgXhmcsyIiqHAdiNX
slrBbBk3/edq9yiAsPAA/0zwEwPqfFTyjYvChdgMyC09aSDOFeGT8vf6HZzMCPDt
=OHTl
-END PGP SIGNATURE-

Re: Are DomainKeys for e-mail signing dead?

[Elizabeth Zwicky]

5.7.4 means you told us not to accept your mail unless it was validly
signed and it is not.
The solution for this is to make sure that mail with a From: in a domain
that requires this is validly signed.
Yahoo does not care whether you use DKIM or DomainKeys for this purpose;
other people may well like DKIM better, making it more fun.
I note that the help page you reference mentions DKIM and DomainKeys
together every time.

If your LISTSERV
-- gets mail from somebody with a domain that requires their mail to be
validly signed (for instance, via DMARC)
-- leaves that sender's address in the From: line
-- and breaks the DKIM signature

then the mail will not deliver to recipients at Yahoo. Your choices are:
-- ask (or force) the sender to join the LISTSERV from a sending domain
that does not do this
-- modify the From: to not be in the sender's domain
-- avoid breaking the DKIM signature
-- let the mail fail

Elizabeth


On 2/28/14 2:51 PM, Matthew Black matthew.bl...@csulb.edu wrote:

Apologies if I slept through prior discussions on the topic.



E-mail from our L-Soft LISTSERV was recently rejected by Yahoo with the
following error:



#@YAHOO.COM

Last error: 5.7.9 554 5.7.9 Message not accepted for policy reasons.
See http://postmaster.yahoo.com/errors/postmaster-28.html



I note:



1.   The e-mail error (5.7.9) references the link
http://postmaster.yahoo.com/errors/postmaster-28.html.

2.   That Yahoo page does not mention error 5.7.9, but references a
similar error 5.7.4 Message not accepted for policy reasons.

3.   It appears that Yahoo wants inbound messages signed using
DomainKeys technology.

4.   Yahoo is the lead inventor of DomainKeys, along with Cicso, PGP,
and Sendmail.

5.   L-Soft LISTSERV manuals and Yahoo both refer to the website
http://domainkeys.sourceforge.net/.

6.   When I click on the Documentation and DomainKeys Implementors
Mailing List links on that page, I get page not found.

7.   A 2007 USA Today Article
(http://usatoday30.usatoday.com/tech/products/cnet/2007-05-23-domainkeys-a
nti-spam_N.htm) mentions that DomainKeys have not been widely adopted.

8.   A basic Google search for DomainKeys comes up with no recent
articles. One website
(http://blog.wordtothewise.com/2011/09/dkim-is-done/) says that
DKIM/DomainKeys are dead.





Are the rumors of the death of DomainKeys premature? If not, is anyone
from Yahoo listening?



matthew black

california state university, long beach