[quote user="gideon220"]When I test this with an email client what would be my server name? Or how do I find out the server name that needs to be in my client? Is it just going to be smtp.server.domain.org? Or should i use my internet IP address? Selecting the option in core/general did work, but does that mean that anyone can send through this server?
[/quote]
Depends on the system. If your email client is running on the same system as Mercury/32 you can use "Localhost" or "127.0.0.1" as the server host name. If you're running on a different system on your local lan then you can use the internal IP address of the Mercury/32 system. If you are running from offsite then you need to use the hostname of the router or system connected to the internet.
If your server is actually connected to the internet then yes people can connect to port 25 to use your MercuryS host to send mail. You have to turn off relaying in the MercuryS setup.
<p>[quote user="gideon220"]When&nbsp; I test this with an email client what would be my server name?&nbsp; Or how do I find out the server name that needs to be in my client?&nbsp; Is it just going to be smtp.server.domain.org?&nbsp; Or should i use my internet IP address?&nbsp; Selecting the option in core/general did work, but does that mean that anyone can send through this server?
[/quote]</p><p>&nbsp;</p><p>Depends on the system.&nbsp; If your email client is running&nbsp; on the same system as Mercury/32 you can use "Localhost" or "127.0.0.1" as the server host name.&nbsp; If you're running on a different system on your local lan then you can use the internal IP address of the Mercury/32 system.&nbsp; If you are running from offsite then you need to use the hostname of the router or system connected to the internet.</p><p>If your server is actually connected to the internet then yes people can connect to port 25 to use your MercuryS host to send mail.&nbsp; You have to turn off relaying in the MercuryS setup.&nbsp;
</p>