Topic: Server moved physical location will no longer receive email.

[shackleton]

Hi.

I moved my SME 7.1.3 server from one state (FL) with road runner cable to another state (GA) with AT&T DSL.  I'm behind the Motorola 2210-02-1006 DSL modem with a linksys router inbetween the server and the modem.  It was running perfectly when I took it down, however, after setting it up in the new state, people sending emails to any address on the server receive a "Remote host said: 553 Sorry, that domain isn't in my list of allowed rcpthosts." notification.  These same people can access the web pages hosted on the server and I can send emails with no problems.  I have updated the host information in the godaddy DNS control panel.  Except for having to change the local IP address from 192.168.1.1 to 192.168.2.1 to avoid a motorola modem / linkys router conflict, no settings have changed (i did update the new local IP address in the main setup portion directly on the SME server console).

-- The Linksys router was used in FL as well.
-- The server is setup in server only mode.

Any ideas or direction will appreciated (even the "you're an idiot, you should've known that you needed to..." kind).

Thanks,

Shackleton

[dmay]

Look in /var/qmail/control/rcpthosts for errors:

# cat /var/qmail/control/rcpthosts

Refresh the templated file and check again:

# expand-template /var/qmail/control/rcpthosts
# cat /var/qmail/control/rcpthosts

Two further commands to try:

# signal-event email-update

or

# signal-event post-upgrade; signal-event reboot

Darrell

[CharlieBrady]

I moved my SME 7.1.3 server from one state (FL) with road runner cable to another state (GA) with AT&T DSL.  I'm behind the Motorola 2210-02-1006 DSL modem with a linksys router inbetween the server and the modem.  It was running perfectly when I took it down, however, after setting it up in the new state, people sending emails to any address on the server receive a "Remote host said: 553 Sorry, that domain isn't in my list of allowed rcpthosts." notification.

Check that the MX records for your domain actually point to your server.

[shackleton]

Thanks for replies. 

Charlie, I double checked the MX records and they appear to point in the right direction.  The web pages can be accessed with no problems from off site.

Darrell, I followed your suggestions.  The rcpthosts file listed my domains.  I refreshed and tried again with no success.  I then tried the signal-event email-update with no success.

Do you have any other thoughts?


Thanks,

Shackleton

[CharlieBrady]

Charlie, I double checked the MX records and they appear to point in the right direction.  The web pages can be accessed with no problems from off site.

Web pages is irrelevant.

If your MX records are wrong (or wrong as seen by your correspondents) then they will be trying to send your mail to the wrong server, and that server will correctly reject them as a relay attempt.

Check the IP address reported in the bounce messages your correspondents are seeing. If they do show your server's IP address, then check your server's qpsmtpd logs.

[shackleton]

Hi Charlie,

The IP address listed in the error message appears to match the old IP from Florida.  The current host in the godaddy DNS control panel is pointed the current IP address. 

Might this just be a situation where the updated IP address has not fully propagated yet?  it's been about two days since bringing the server online and changing the IP address in the godaddy DNS control.

Thanks again,

Shackleton

[shackleton]

Hi,

Thanks for the ideas.  The problem wound up being that my new ISP is blocking the incoming side of port 25.  In case anybody reading this wanted to know.  I'm working on this new problem with advice from another set of posts.

Thanks,

Shackleton

[raem]

shackleton

my new ISP is blocking the incoming side of port 25.

See
http://wiki.contribs.org/PortRedirect