I've got one reseller in Japan on this server. This issue first cropped up for him about 2 weeks ago when the last security update deal happened and we updated Cpanel. The problem last time seemed to be fixed by restarting relay. Customer is back with the same error message; he and his clients are having email that is sent to a domain that's not on his server bounce with a 550 error:
2004-06-27 11:39:52 H=yahoobb218120066008.******** (fmvne4) [**********] F=<************> rejected RCPT <************>: yahoobb218120066008.******* (fmvne4) [********] is currently not permitted to relay through this server. Perhaps you have not logged into the pop/imap server in the last 30 minutes or do not have SMTP Authentication turned on in your email client.
This wouldn't be nearly as irritating if it didn't appear so erratic. We ran /scripts/fixrelayd and restarted relay already. I checked /etc/localdomains (no issues there). I sent test emails from my personal domain on his server and from a test account on one of his domains that he supplied the first time this error occured to my business account on another box, and have no trouble sending the emails. I'm wondering if adding some IP addresses to /etc/relayhosts will fix the problem, but don't know exactly how that works or if it's even necessary as the issue is sporadic. It's really becoming a headache for all parties involved.
So, anyone got any other ideas?
2004-06-27 11:39:52 H=yahoobb218120066008.******** (fmvne4) [**********] F=<************> rejected RCPT <************>: yahoobb218120066008.******* (fmvne4) [********] is currently not permitted to relay through this server. Perhaps you have not logged into the pop/imap server in the last 30 minutes or do not have SMTP Authentication turned on in your email client.
This wouldn't be nearly as irritating if it didn't appear so erratic. We ran /scripts/fixrelayd and restarted relay already. I checked /etc/localdomains (no issues there). I sent test emails from my personal domain on his server and from a test account on one of his domains that he supplied the first time this error occured to my business account on another box, and have no trouble sending the emails. I'm wondering if adding some IP addresses to /etc/relayhosts will fix the problem, but don't know exactly how that works or if it's even necessary as the issue is sporadic. It's really becoming a headache for all parties involved.
So, anyone got any other ideas?