[quote user="EMP"]
Okay, Im not so sure anymore if I actually can recieve messages. Everytime I send an email from an external Server to Mercury, the SMTP Server says:
Connection from xxx.xxx.xx.xx, Tue Feb 10 01:44:35 2009
EHLO mail.myisp.com
MAIL FROM:<mail@myisp.com>
RCPT TO:<postmaster@mercuryDynDNS.com>
DATA
DATA - 34 lines, 1138 bytes.
30 sec. elapsed, connection closed Tue Feb 10 01:45:05 2009
The 30 seconds look to me like a timeout, as outgoing mails need 1-2 secs :)
[/quote]
Turn on session logging in MercS for more detail.
[quote]
I put my domain in this http://www.mxtoolbox.com/diagnostic.aspx website's tool. I got:
RESULT: myDynDNS.com
Banner: 220 MercuryESMTP server ready.
Connect Time: 0 seconds - Good
Transaction Time: 0.594 seconds - Good
Relay Check: OK - This server is not an open relay.
Rev DNS Check: OK - xx.xxx.xx.xx resolves to xxx.xx.xxx.xx.cust.myISP.com
GeoCode Info: Geocoding server is unavailable
Session Transcript: HELO please-read-policy.mxtoolbox.com
250 CyberPunk Hello, please-read-policy.mxtoolbox.co [141 ms]
MAIL FROM: <test@mxtoolbox.com>
250 Sender OK - send RCPT [141 ms]
RCPT TO: <test@mxtoolbox.com>
553 We do not relay non-local mail, sorr [156 ms]
QUIT
221 Mercury Service closing channe [156 ms]
[/quote]
Looks good.
[quote]
So it seems the Server is reachable, but it doesnt accept any mails? My Firewall says that Mercury is listening to the following ports: 25, 79, 80, 110, 143
I forwarded 25 and 110 through the NAT, do I need to do more here?
[/quote]
You only need 110 open/forwarded if you are connecting to your local Mercury POP server from outside your LAN, otherwise it is a hole you should have shut.
[quote]
Further I've gone wild on the Local Domains and just entered every imaginable name/adress.
[/quote]
For each mail received with a domain part listed in "Local Domains", Core will attempt to deliver the mail to the local username part.
[quote]
I'm still unable to connect to a mailaccount. Every client gives me a "connection refused/denied" almost immediatly. Doesnt matter if I use 127.0.0.1, Lan IP, external IP or domain. What else could be wrong here? I have a DHCP Router if this changes anything :/
[/quote]
Your mail server should be assigned a static ip (either manually or via DHCP Static Lease) otherwise, if the assigned IP changes your port 25 forward will be pointing at a vacuum or the wrong machine.
What response do you get to:
telnet 127.0.0.1 25
?
[quote user="EMP"]<p>Okay, Im not so sure anymore if I actually can recieve messages. Everytime I send an email from an external Server to Mercury, the SMTP Server says:</p><p><i>Connection from xxx.xxx.xx.xx, Tue Feb 10 01:44:35 2009
EHLO mail.myisp.com
MAIL FROM:&lt;mail@myisp.com&gt;
RCPT TO:&lt;postmaster@mercuryDynDNS.com&gt;
DATA
DATA - 34 lines, 1138 bytes.
30 sec. elapsed, connection closed Tue Feb 10 01:45:05 2009</i>
</p><p>The 30 seconds look to me like a timeout, as outgoing mails need 1-2 secs :)</p><p>[/quote]</p><p>Turn on session logging in MercS for more detail.</p><p>[quote]
</p><p>&nbsp;I put my domain in this http://www.mxtoolbox.com/diagnostic.aspx website's tool. I got:</p><p><i>RESULT: myDynDNS.com
Banner: 220 MercuryESMTP server ready.
Connect Time: 0 seconds - Good
Transaction Time: 0.594 seconds - Good
Relay Check: OK - This server is not an open relay.
Rev DNS Check: OK - xx.xxx.xx.xx resolves to xxx.xx.xxx.xx.cust.myISP.com
GeoCode Info: Geocoding server is unavailable
Session Transcript: HELO please-read-policy.mxtoolbox.com
250 CyberPunk Hello, please-read-policy.mxtoolbox.co [141 ms]
MAIL FROM: &lt;test@mxtoolbox.com&gt;
250 Sender OK - send RCPT [141 ms]
RCPT TO: &lt;test@mxtoolbox.com&gt;
553 We do not relay non-local mail, sorr [156 ms]
QUIT
221 Mercury Service closing channe [156 ms]</i>
</p><p>[/quote]</p><p>Looks good.</p><p>[quote]
</p><p>So it seems the Server is reachable, but it doesnt accept any mails? My Firewall says that Mercury is listening to the following ports: 25, 79, 80, 110, 143</p><p>I forwarded 25 and 110 through the NAT, do I need to do more here?</p><p>[/quote]</p><p>You only need 110 open/forwarded if you are connecting to your local Mercury POP server from outside your LAN, otherwise it is a hole you should have shut.</p><p>[quote]
</p><p>Further I've gone wild on the Local Domains and just entered every imaginable name/adress.&nbsp;</p><p>[/quote]</p><p>For each mail received with a domain part listed in "Local Domains", Core will attempt to deliver the mail to the local username part.</p><p>[quote]
</p><p>I'm still unable to connect to a mailaccount. Every client gives me a "connection refused/denied" almost immediatly. Doesnt matter if I use 127.0.0.1, Lan IP, external IP or domain. What else could be wrong here? I have a DHCP Router if this changes anything :/</p><p>[/quote]</p><p>Your mail server should be assigned a static ip (either manually or via DHCP Static Lease) otherwise, if the assigned IP changes your port 25 forward will be pointing at a vacuum or the wrong machine.</p><p>What response do you get to:</p><p>telnet 127.0.0.1 25</p><p>?</p><p>&nbsp;</p>