• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Outgoing mail error (#5.1.2) -- resolv.conf?

Z

zrcs

Guest
Since migrating to a new block of IPs on a shared hosting box running Plesk 8.1.1 and CentOS 4.3, our clients are complaining of getting mail rejection errors for messages that they send to certain domains.

Qmail is generating #5.1.2 errors (which the logs are full of) for these domains, although they are live, working remote domains that respond to nslookup, dig, and host (although not ping), and have clean dnsreports. Also, prior to changing our IPs, our server was sending mail to these domains without incident.

I've surfed the forums for hours here, trying a variety of seemingly applicable solutions, including adding the -Rt0 flag, checking reverse DNS configuration and adding SPF records to all mail domains. Antivirus is off, Spamassassin is disabled, MAPS protection is off, and relaying is set to "closed" (using authentication was causing messages to AOL, SBC, and others to pile up in our queue).

...and the problem continues. I'm wondering if there might be an issue with the server's resolv.conf, but both nameserver IPs listed there respond quickly.

I would be very appreciative if anyone could provide a possible solution.

Thanks.
 
does the rDNS on the new IP(s) match that of the mail server's hostname?

Or did your hostname change perhaps?

Just an idea..

Good Luck ;)
 
It turns out that the problem was somehow being caused by the recursion switches in named.conf. The "allow-recursion" and "recursion" settings were contradictory, i.e., recursion was turned off completely, but local recursion was switched on. Switching recursion on seems to have fixed the problem.
 
Back
Top