Meanwhile, I'm getting e-mails back reporting that my deliveries have

been delayed. So I suppose it does somehow send.. It's not my firewall

or router, I've opened the ports 110 and 25 in both also added an

exception for Mercury Mail.

 The server resolves but I cannot connect to port 25. 

Answer Section:
    krydox.servebeer.com, A, 69.65.19.125

You may be running into port 25 blocking and/or anti-spam systems blocking systems without a fixed IP addresses.  Instead of using MercuryE shift to MercuryC and send your mail via your ISPs SMTP host.  In addition, open an alternate port (587) on the MercuryS server so that we can test making the connection via this port.  If 587 works remotely and 25 does not then this is a port blocking problem.

Hello, I am running XAMPP 1.7.2 in which everything works fine and Mercury Mail 4.72 in Windows XP.

I'm running everything including XAMPP on one computer and only running the modules MercuryS, E & P and I'm having problems understanding a few things, which is problaby the cause of the problem I have, I cannot receive any e-mail but I am able to send mail.

Now, I've got a DNS host at NO-IP and they allow me to enter an MX_Record and it says "Enter the name of your external mail exchangers (mx records) as hostnames not IP addresses"

I'm not really sure what is ment here, or I just configured it wrong on one or the other side.

Say my hostname or URL (from NO-IP) is krydox.servebeer.com, do I need to put that in "Internet name for this system" in Mercury mail? And what's "Identify myself as" in the MercuryE SMTP Client config?

I've been reading some tutorials and it got me so far that I can send e-mails but it seems all of them are for setting everything up as "localhost" which is not what I want.

[quote user="Krydox"]

Say my hostname or URL (from NO-IP) is krydox.servebeer.com, do I need to put that in "Internet name for this system" in Mercury mail?[/quote]

Yes[quote]

And what's "Identify myself as" in the MercuryE SMTP Client config?

Alright thanks,

What about MX records? I've set it to computername.krydox.servebeer.com, thought that was right.

And I don't really get "Local domains" in the Core Module config.

The help file is a bit confusing, is the domain name here calliope.pmail.gen.nz and the computer name happens to be calliope too? Or do I put computername.krydox.servebeer.com here.

When entering domains into this section, you should usually provide

three entries per local Internet domain - a fully-qualified version, a

simple version, and a special entry called a domain literal version,

which is the IP number of your system enclosed in square brackets. For

example, if your system's Internet name was calliope.pmail.gen.nz

(192.156.225.76), you might create these domains definitions:

    calliope        calliope
    calliope        calliope.pmail.gen.nz
    calliope        [192.156.225.76] 

[quote user="Krydox"]

Alright thanks,

What about MX records? I've set it to computername.krydox.servebeer.com, thought that was right.

[/quote] If you have an A record for computername.krydox.servebeer.com pointing to your Mercury server ip, then yes, otherwise just use krydox.servebeer.com

[quote]

And I don't really get "Local domains" in the Core Module config.

The help file is a bit confusing, is the domain name here calliope.pmail.gen.nz and the computer name happens to be calliope too? Or do I put computername.krydox.servebeer.com here.

When entering domains into this section, you should usually provide

three entries per local Internet domain - a fully-qualified version, a

simple version, and a special entry called a domain literal version,

which is the IP number of your system enclosed in square brackets. For

example, if your system's Internet name was calliope.pmail.gen.nz

(192.156.225.76), you might create these domains definitions:

    calliope        calliope
    calliope        calliope.pmail.gen.nz
    calliope        [192.156.225.76] 

[/quote]

For mail addressed to any domains listed here, Mercury will attempt to deliver it to a Local User, not send on via SMTP.

you should probably have (the "server" part is irrelevant for non-netware environments, so you can use whatever you want, but MUST be there & SHOULD be the same for each entry):

server       computername

server       computername.krydox.servebeer.com

server       krydox.servebeer.com

server       [your.ip.add.ress]

Alright so my MX record should be same as my only A record which is krydox.servebeer.com. It's running on just one machine.

I tried both though and I'm still unable to receive e-mails with my current config:

My server's internet name is krydox.servebeer.com, Local domains is as you said, I tried my lan IP in it aswell as my wide.

I let both POP3 & SMTP servers listen on all interfaces, and the nameserver is simply my router's DNS server right? I can't leave it blank.

Meanwhile, I'm getting e-mails back reporting that my deliveries have been delayed. So I suppose it does somehow send.. It's not my firewall or router, I've opened the ports 110 and 25 in both also added an exception for Mercury Mail.

[quote user="Krydox"]

Alright so my MX record should be same as my only A record which is krydox.servebeer.com. It's running on just one machine.

[/quote]Good.[quote]

My server's internet name is krydox.servebeer.com,[/quote]Good.[quote]Local domains is as you said, I tried my lan IP in it aswell as my wide.

[/quote]That just means your server will accept mail for user@[outside.ip] & user@[inside.ip][quote]

I let both POP3 & SMTP servers listen on all interfaces[/quote]Good.[quote] and the nameserver is simply my router's DNS server right?[/quote]Yes.[quote] I can't leave it blank.[/quote]If you do it is up to Windows to do the lookups, I always specify a DNS server by IP address here.[quote]It's not my firewall or router, I've opened the ports 110 and 25 in both also added an exception for Mercury Mail.[/quote]

can you connect to port 25 from a machine inside your network?[quote]telnet inside.ip 25[/quote] from a machine outside your network? you can also use a port testing service like ShieldsUp at grc.com to test.

In your router add a forward for another external port (maybe 26) to port 25 on your server and repeat the external tests on port 26. If this works, then your ISP is probably blocking port 25.