Hi,
It seems there is no one replying here, so I thought I should chime in as it appears this is all moving over to Yahoo Customer Service on June 29, 2015...
I've gone through the entire Yahoo Feedback Loop (YFBL) process. It seems this requires setting up a few email address on your server, such as postmaster (or abuse), and then one other email address of your choice for handling the yahoo feedback emails that will be sent to you in ARF format.
I've set this all up, it only took about 30 minutes, and requires several confirmations, and clicking through to verify the emails, as well as checking and knowing your DKIM signature 1.) domain, 2.) s= selector, or you can use * for all, 3.) send feedback to - the email you setup on your own for handling yahoo feedback, and 4.) your postmaster, or abuse email address at your domain.
It's all setup and now waiting for Yahoo! activation.... so, hopefully within 24 hours or so, I will have notification... Here's what I find on the Yahoo website about the ARF file it will send for every complaint from a Yahoo user:
--
Each report consists of one message – with full headers, nothing “munged” or redacted – and some additional metadata as defined in the Abuse Feedback Reporting Format (ARF -
http://en.wikipedia.org/wiki/Abuse_Reporting_Format).
The From: header will be ‘Yahoo! Mail AntiSpam Feedback <feedback@arf.mail.yahoo.com>', while the SMTP MAIL FROM (envelope sender) is of the format ‘cfl.<random>-<recipient address>=<recipient domain>@returns.bulk.yahoo.com’.
The source IP address may vary, but every report is signed with DomainKeys or DKIM using the signing domain ‘arf.mail.yahoo.com’. That signing domain is not used for any other purpose.
We cannot provide a sample report customized for your particular domain, but there is a sample in the ARF specification
--
What to do with the reports? ( from Yahoo:
http://feedbackloop.yahoo.net/faq.php ):
Yahoo!'s expectation is you will take steps to reduce the number of complaints. There are many different ways to achieve this, depending on what kind of business you operate and what kinds of mail you transmit. Some of the most common techniques include:
ISPs will likely figure out which of their users sent the message, determine if that user violated their policies, and then react appropriately – perhaps by sending a warning to the user, reducing their privileges, and/or removing them from the system.
A bulk sender or mailing list operator could:
choose to immediately cease sending additional similar mail to that recipient;
review how that address was initially added to their list, and adjust their processes so that the same mistake is not repeated, perhaps even removing all recipients obtained through that mechanism;
attempt to determine if the content of the message led to the report;
attempt to determine if the message should have been expected by the recipient – for example, do the recipients have a clear understanding of the frequency and content of the list?
Or, contact Return Path for assistance in developing the right process for your company.
------------
Now, the next step - DW - do you have some code that could process the ARF files to remove these email addresses automatically, or should I write something along the lines of what is already there (in dailymail.php) to handle bounces by looking at this email address and removing these emails from all of my Listmail PRO lists every day when dailymail runs?
