Topic: emails deprioritized due to a number of potential issues with mailing
==== Required information ====
- iRedMail version:
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Linux/BSD distribution name and version:
- Related log if you're reporting an issue:
Well, all is well, my server is sending and recieving, PTR record good, SPF record good, DKIM good now there is another issue. :\
I messaged yahoo support to see why emails from my server are going to spam and this is their response.
Thank you for contacting Yahoo! Mail.
Please note that if you are not the administrator for the mail server(s) affected, we encourage you to contact the administrator so they can address the possible issues regarding mailings from the mail server.
After looking into the issue, it appears that your emails may have become deprioritized due to a number of potential issues with your mailings. These deprioritizations were temporary but may be re-triggered if the sending IP profile continues to be poor.
To continue to receive prioritized delivery, we recommend ensuring that you conform to industry standard practices. Then you will not be deprioritized and you should see improvements in delivery times as well as available connections.
Please visit the following help pages for information on improving list maintenance:
http://help.yahoo.com/kb/index?page=con … id=SLN3435
http://help.yahoo.com/kb/index?page=con … id=SLN3443
http://help.yahoo.com/kb/index?page=con … id=SLN3433
If you are not conforming to the standards listed in the help pages above, then you will likely experience significant delays in connections, as our system automatically prioritizes connection availability based on the type of information contained in these FAQs. By trying the basic suggestions listed on the help page, you can potentially:
* Decrease your cost of mailings in bandwidth, hardware, AND management.
* Increase the effectiveness of your mailings - non-existent users can't open your mail or respond to your offers!
* Increase the speed of your delivery - emails sent to large numbers of non-existent users can definitely impact the time it takes for you to deliver your important messages.
Plus, you'll ensure that your messages are prioritized by our delivery system which helps us differentiate you from spammers.
If we can further assist you, please let us know.
Thank you again for contacting Yahoo! Mail.
What the eFF does that mean?
[ ... ]it appears that your emails may have become deprioritized due to a number of potential issues with your mailings. These deprioritizations were temporary but may be re-triggered if the sending IP profile continues to be poor.
To continue to receive prioritized delivery, we recommend ensuring that you conform to industry standard practices.
How do i fix this?
Here is a sample header
From Jesse Szypulski Thu Jan 24 15:26:18 2013 X-Apparently-To: email@example.com via 126.96.36.199; Thu, 24 Jan 2013 23:26:20 +0000 Return-Path: <firstname.lastname@example.org> X-YahooFilteredBulk: 188.8.131.52 Received-SPF: pass (domain of thesecond.org designates 184.108.40.206 as permitted sender) X-YMailISG: j6tctYEWLDsjMXS3GTx.fRO7Qv4hnjcajH1jvS_khlNRPeHO 12km1pmURlbhLM8pegbZSw2uQ5Ea11JUBlM3mdDc0Q0UWGbVDv_2wJNX9wkD SAr9RJXeMRNqKO987Hk6u23Clpacl0qlyx37dTbrMQg8TufwYgKVdM1USMmm H4rLsPjZaPYzAEBjVf_JHSmv0HApSgXXJ8NnKu5lU4HrP5HUDYCJgUUL6o_k Nq9dAT.ZUYIMNSPptw17Bbtv5JZ_WUAPFNdF0BhjFV3TRhDWclU7zSoSfeSK V1juYCeNiKoUaIljgacnOYdIfZmhxBRlgVaiPc5ijjZhZJBJhgRTy6iTEOy2 r6tkC5YicyMEnj4VIqbGztKsD9ekHyU5N0OtI4M4gvw7f7ZPapEtrjrcIz4P tJSYUO5brj7jdEZfuT8pPkAtqr0n8sBV7B6Vbn5J24uv2TQcbl_timymBseQ NFETa.9zkcFZ9pQHnSL6o_snAuLZdSs8O3ijWELOdFMGlQGIAuQcjK6z3Ofw R6egaHfJNtl.HgA4eSrj5ivXjAQJi6jiRI3sTnQ_NxiHRr_dU7B7yBM5qi2V 0EWnux11CbuyGZ0ZvMXWLBllHi._lMfnd0v2Zg.29XvUHjAOHUYa_NoCkMWf MXu1zSp53i6cDFt8y9mmQcewY2vmz2k64BvGdgnXbSQYKkJkydL5r2snHLYf Bvks8WgYQJ_1aoEGgzp4gi2g9ZirVSo7P2ZNH_WRhRODfodpNDutDUaOMv8Z RISge2YBGfTydn6uN9clMqtgd27M2EJSRGOohTjXAyFII1rCojimc97IE66K fZAIvUFhIhNHg_RGiJV4fU6LHRMp_iEb2AZCom_pidTVmckFGiTNbq_BdHmm W_HVOdruR1SH1NrPFa_XcWcSyCcCw0DPlFYaPB5MPpE_LIUl8CWiiEzOaV.r 1Wk5qQOqM_3DHWivRzg0QzFWnIOOeIMG4eVRxECPCg.o3OrFkwypXTUjGX9l Sth8mW8N9L4iNLlf2ip5.LPw56CtVIQCPQWs3l3a9jFDypmbow75flKVJG8r ceAIRXr.3iKjfw2iQqG83zGKqVVmY29oKqwlxYuQDPDqYBGf3_9AXUmPzZ4F RgGkj75RNUKyfvpQyjuiiQ_kh.ZB4Xa_.ObpSSuuPz2QQPqoEPFrlRlWRzbP UqY0YHgURHXQSi8aZYTeZHwnRk_C6.9h3uMfmykpl3V28hGTwW6JXrJ_u7gp JudY7cr0Hdldg_8CRn5nVy.U7uSbXfLKSXA- X-Originating-IP: [220.127.116.11] Authentication-Results: mta1019.mail.ne1.yahoo.com from=thesecond.org; domainkeys=neutral (no sig); from=thesecond.org; dkim=pass (ok) Received: from 127.0.0.1 (EHLO mail.thesecond.org) (18.104.22.168) by mta1019.mail.ne1.yahoo.com with SMTP; Thu, 24 Jan 2013 23:26:20 +0000 Received: from mail.thesecond.org (localhost [127.0.0.1]) by mail.thesecond.org (Postfix) with ESMTPA id B575B60E7A for <email@example.com>; Thu, 24 Jan 2013 23:26:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thesecond.org; s=mail; t=1359069979; bh=q5cyARPl5zX/knmvCnEy11G7/r6gcljJ44qrvv5DErY=; h=Date:From:To:Subject; b=JNULsTH2IyG0ap0VL5jJVd2un8PgZTf2LwaI1l/B5hRboTzspSmDBlb14yiIozBcd 2iEIeTK8gOUuZVs5WPAjkyYUILKWhNsKx1QezD8wDeOmlTC+j3e4BVzXLn9Svf1uhG 2XPiFLcc7zUF1g5VzjeI3OuT4sKQYOkut0mhqfzvGhDjNg5ry0z/b+bDZLnQWfGesY RHEeFA/7Xwc8/EkjcXQstp1KN3oKVURNsdBAnyMIsE4IWxVtXQj6oGIDorqiKH1DyF Nu4NkW1J+OCzgs7Iw3BANQ0s8390b1WODoxZShnFL8RRWciLN/0UXVSyMigBg+7cnj XHE8UyajZI+Tg== MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 24 Jan 2013 18:26:18 -0500 From: Jesse Szypulski <firstname.lastname@example.org> To: <email@example.com> Subject: TEST Message-ID: <firstname.lastname@example.org> X-Sender: email@example.com User-Agent: RoundCube WebMail Content-Length: 5
There filter reason is:
that is the IP of my mail server. not sure what the issue is.