I have a situation where my NOC keeps getting their IP blocks flagged as spammers and I get caught up in the mix. SpamHaus will only allow the ISP to request removal. This last hit has lasted a week as of tomorrow, and it is affecting the ability for my clients on one of 3 servers to send mail to popular domains here in Canada. I have 3 web hosting VPS's (and will likely add a 4th in the New Year). One lesson I learned was to research the reputation of IP addresses before committing to a hosting centre. For the most part of the last 2 years I have struggled with email blocks, probably every other month. Right now they are offering to assign me new IP Addresses. Which brings me to... What is harder - redoing the IP Addresses over 3 machines, or finding a new provider and migrating all servers? I'm just interested in your thoughts before I go off and do something drastic. Thank you! Merry Christmas!
That's an interesting solution for sure! Is this difficult to set up in ISPConfig? Out of the 3 servers, right now only 1 is in the SpamHaus block but it's been well over a week and they haven't been de-listed.
A quick search produced this information: Steps to Configure an SMTP Relay Service Log in to the ISPConfig control panel as an administrator. Navigate to the System tab. Click on Server Config. Select the Mail tab to access the mail server settings. In the mail configuration settings, locate the fields for the relay host. Outgoing mail server (SMTP): Enter the hostname or IP address of your external SMTP relay service (e.g., smtp.sendgrid.com or smtp.gmail.com). Relay user: Enter the username provided by your SMTP relay service provider. Relay password: Enter the password associated with that user. Ensure the correct SMTP Port is specified (usually port 587 for authenticated submission, but check with your provider). Save the configuration changes. ISPConfig will automatically update the underlying Postfix configuration files, so manual command-line configuration is not necessary and may be overwritten. Test your email sending to confirm that emails are now being routed through the external relay. Notes System Emails: Emails generated by the ISPConfig system itself (e.g., notifications) will also use these relay settings. Per-Domain Relay: For multi-domain setups, you can enable per-domain relay options under System > Interface > Main Config > Email, allowing different domains to use different relays if needed. Troubleshooting: If you encounter issues (e.g., in the mail log), verify your credentials and ensure your relay service allows connections from your server's IP address. Sometimes, firewalls or SSL/TLS settings need adjustment. That sounds quite easy!
So I set up a domain relaying service with AhaSend. I configured it under the domain name of my server that is having problems. I did the initial steps above but when I send from a domain that is hosted on this server, I get (host send-us.ahasend.com[5.78.73.137] said: 556 Invalid account. Tenant or Domain not found for 'hosted_domain.com'. So it looks like I need to set up a relay for each individual domain hosted on this box. The notes that talk about how to do this don't match what I have in ISPCONFIG 3.2.11p2 other than getting to the check box "Show per domain relay options" which I have checked. But from here I don't see anyway to get to the per domain relay settings. If I delete an existing mail domain, won't that remove all of the existing email accounts? I certainly don't want that.
Which means you now have per domain relay settings for each email domain. Go to the email domain, and you will find them there. Btw. Your ISPConfig version is pretty old already, you should consider to update.
Till - you are the best!!! I see those relay options now. I have updating my installation on my list of things to do in January
Not having any luck with mail relay per domain. I entered the relay host, relay username, and relay password in Domains for test domain. I added 5 DNS entries to allow mail delivery by ahasend. Their dashboard confirms all settings are fine. I then open up my email client and send (no config changes in the email client) and I always get: host send-us.ahasend.com[5.78.73.137] said: 500 tenant 'e7835f38-xxxx-4137-xxxx-5c896a57e5f3' requires SMTP AUTH (in reply to end of DATA command) They are saying my software isn't doing the SMTP AUTH correctly. Till: Will updating my version of ISPConfig help?
You can try it, but I'm not aware at the moment that there are or have been any issues with that function.
If you still have the global smtp relay in place, you could try removing it and maybe check in Postfix main.cf afterwards if it really has been removed.
This was a bust so I have given up on setting up a mail relay for one server at this time. I was due to add a 4th server in the new year, and I have one I am working on adding to the mix. I'm at the point where I'm ready to run the install script. It is using the latest stable release and my ISPConfig servers (3 of them) are all using 3.2.11p2 Do I need to upgrade my 3 machines before adding the 4th?
Thought so. I was waiting to activate a snapshot of each server in case the upgrade went wrong. Do you think I can safely run the update script and not have a full backup?
