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. - 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. 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...]).
