It's looking like Yahoo has quit responding correctly to greylisting, now returning a fatal error to the sender:
In our logs it looks like normal greylisting:
It showed up on both our MX-balanced Proxmox relays, but Yahoo has not re-tried it, as of about 30 minutes. Before this, I always saw Yahoo retry fairly quickly, and certainly not produce any error messages.
We are seeing it not only for senders using Yahoo proper (the test above is from a yahoo.ca user), but rogers.com, a major Canadian ISP that uses Yahoo for mail services.
Anyone else seeing this? Seems to have started very recently, like yesterday (2015-02-23).
Thanks,
Chip
<nosuch.user@[one of our domains]>:
Remote host said:
450 4.7.1 <nosuch.user@[one of our domains]>: Recipient address rejected: Service is unavailable (try later)
[RCPT_TO]
In our logs it looks like normal greylisting:
Feb 24 10:14:13 | smtpd | NOQUEUE: reject: RCPT from nm1-vm1.bullet.mail.bf1.yahoo.com[98.139.213.163]: 450 4.7.1 <nosuch.user@[one of our domains]>: Recipient address rejected: Service is unavailable (try later); from=<[our test account]@yahoo.ca> to=<nosuch.user@[one of our domains]> proto=ESMTP helo=<nm1-vm1.bullet.mail.bf1.yahoo.com> |
It showed up on both our MX-balanced Proxmox relays, but Yahoo has not re-tried it, as of about 30 minutes. Before this, I always saw Yahoo retry fairly quickly, and certainly not produce any error messages.
We are seeing it not only for senders using Yahoo proper (the test above is from a yahoo.ca user), but rogers.com, a major Canadian ISP that uses Yahoo for mail services.
Anyone else seeing this? Seems to have started very recently, like yesterday (2015-02-23).
Thanks,
Chip