Hi,
We want the email relay to listen on ports 25 and 587. Is this possible, and how can we achieve it? Using port 587 for sending mails in no problem.
Thanks for the the example, this worked in our test environment however in our prod we still use Version 2.4.1 which doesnt seem to include multiple configs.
Do you have any best practices or tips on how to update to 2.6.1?
Kind regards
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ah yes, of course that's not going work for such an ancient version! You would need to run two separate processes.
I have done the work for multiple "--port" values, so it will go into the next release. I have just pushed the changes to the github emailrelay-build repository so you could get new 2.6.1a binaries from there in an hour or so.
When upgrading you should check the release notes in the NEWS file for all intervening versions. I've attached the 2.5 and 2.6 release notes. Also note that an older executable may not be able to parse a newer version's envelope file.
You need to have multiple configurations "units", which are defined by adding arbitrary prefixes to every configuration item. For example,
A unit name is "declared" via the "spool-dir" item and you can use an empty unit name as well as non-empty names.
Using multiple "--port" values is not supported because no one has ever asked for it.
Hello,
Thanks for the the example, this worked in our test environment however in our prod we still use Version 2.4.1 which doesnt seem to include multiple configs.
Do you have any best practices or tips on how to update to 2.6.1?
Kind regards
Ah yes, of course that's not going work for such an ancient version! You would need to run two separate processes.
I have done the work for multiple "--port" values, so it will go into the next release. I have just pushed the changes to the github emailrelay-build repository so you could get new 2.6.1a binaries from there in an hour or so.
When upgrading you should check the release notes in the NEWS file for all intervening versions. I've attached the 2.5 and 2.6 release notes. Also note that an older executable may not be able to parse a newer version's envelope file.