Xequte User Forums - Send failure

Xequte User Forums

Profile Active Topics Forum FAQ

Forum membership is Free! Click Join to sign-up
Username:	Password:
Save Password
Forgot your Password?

Forum Tips
» This forum is for users to discuss their software problems and suggestions for improvement. Remember that only a tiny percentage of our users experience such problems (To be precise less than 0.7% have ever posted on this forum)
» Include your software version number (as displayed in the About Box)
» Check the FAQ before posting as most common questions have already been answered
» You don't need to also e-mail us separately as our support team will respond to all questions on this forum

All Forums

Xequte User Forums

MailList King

Send failure - unable to relay

New Topic

Reply to Topic

Printer Friendly

Author

Topic

djnicholson

United Kingdom
4 Posts

Posted - Oct 08 2009 : 03:30:37

We recently changed the IP address of our mail server. I processed mail in MailList King without changing its IP setting, and got an error.

I changed the IP address in MailList, but now get error 5.7.1 'Unable to relay for ... '. I'm guessing I've forgotten to do something I did when I installed the software, but can't figure out what.

The mail server is in house, and we just changed its IP address and plugged it into the new router. Otherwise mail is working fine.

Thanks
David

xequte

7504 Posts

Posted - Oct 08 2009 : 17:43:11

Hi David

"Unable to Relay" errors typically occur when you are signed into one ISP and trying to send to the mail server of a different ISP (e.g. logged into comcast.net and have set your isp to mail.verizon.com).

It can also indicate a general authentication issue, typically when your ISP requires you to download your mail before sending.

Nigel
Xequte Software
nigel@xequte.com

djnicholson

United Kingdom
4 Posts

Posted - Oct 09 2009 : 03:03:23

We have solved the problem. There was a setting in the mail server giving permission to relay to a specific IP address. That address has changed since we changed ISP's.

Sorry to bother you.

Thanks
David.