> -----Original Message----- > Florin Andrei a écrit : > > There seems to be a massive difference between the speed of various > > providers, in terms of accepting messages for delivery. Yahoo stands out > > as, by far, the slowest of the big ones. > > > > Because the messages are legitimate, we signed up for the email feedback > > loop with Yahoo, so that messages flagged as spam by Yahoo users are > > reported back to us, so we can silence notifications for those accounts. > > That didn't seem to help. > > > > Messages @yahoo.com just accumulate in the deferred queue and stay > there > > for a long time. When they do get kicked back into the active queue, > > it's just a trickle. > > > > Everyone else's emails are delivered very quickly. It might be my > > imagination, but it seems some providers do accept messages more > quickly > > if you use the email feedback loop. > > > > Anyway, after a while, we end up with a bunch of @yahoo.com messages > in > > the queue, some domain typos, and not much else besides. > > > > One of the tricks some people seem to use is creating a dedicated > > transport for the slow destination. I'm reading the tuning and qshape > > README documents, and there are a lot of good suggestions there, but I > > was wondering what are the solutions that are being used *now* > > specifically for dealing with Yahoo. > > > > it looks like yahoo throttle you. > - if you send few mail, do nothing. just wait and things will hopefully > get better.
[Michael Hutchinson] Only OK if you're sending one or two E-Mails. > - if on the other hand you send a lot of mail, then you need to get in > touch with yahoo. there's nothing we can do to help you. [Michael Hutchinson] This also does very little. Yahoo don't list a Network Operations Centre and are about the hardest company to deal with when it comes to E-Mail delivery resolution. I've filled out dozens of forms to get particular IP's whitelisted for specific domains on their Mail systems, with no reply, let alone result. > one thing you can do is to ask your recipients to explicitely tag your > mail as "not spam" if it was ever tagged as spam. or they can reply (of > course, this doesn't work for silly noreply mail. [sigh, I just got an > internal one with a URL that doesn't work, and I don't know whom to > contact...]). [Michael Hutchinson] Unfortunately it only takes ONE user to click on "This is Spam" and you're back to square one. (and being IP banned is Square one). [Michael Hutchinson] We have had this exact problem, delivering Retail newsletters to people who have opted in for it. A lot of them are on Gmail and Yahoo, and this can be difficult with Bulk E-Mail. Despite contact with Google themselves and signing up for all of their reporting services regarding Spammy Emails and Certified Senders, the best result we've had is to use some Postfix configuration to resolve the issue. It does this by gently delivering the E-Mails at an acceptable rate (discovered with a LOT of testing and a LOT of IP bans (good they're not permanent, huh :). In our environment, on our servers, this has resolved the issue, and delivers mail to those domains a LOT faster than not performing the config on Postfix. In fact, if we dont configure, we get banned straight away against those domains and cannot deliver for several hours afterwards. We setup the postfix transport file with these entries: # destination domains that need to be rate limited hotmail.com hotmail: msn.com hotmail: live.com hotmail: windowslive.com hotmail: yahoo.com.ar yahoo: yahoo.com.au yahoo: yahoo.com.br yahoo: yahoo.ca yahoo: yahoo.com.cn yahoo: <snip> - there's more but you get the idea. Then we setup master.cf: yahoo unix - - - - - smtp hotmail unix - - - - - smtp Then setup main.cf: # Slow these destinations to avoid blacklisting, see /etc/postfix/transport for domains configured hotmail_destination_concurrency_limit = 2 hotmail_destination_rate_delay = 2s hotmail_destination_recipient_limit = 5 yahoo_destination_concurrency_limit = 4 yahoo_destination_rate_delay = 1s yahoo_destination_recipient_limit = 5 These settings can be tweaked depending on what server you're talking to. However, these values work for us, after having dealt with not getting 10,000 mails out per week. I hope this helps. Cheers, Michael Hutchinson mhutchin...@manux.co.nz
