Topic: Mail Delivery failling - 550 Relaying prohibited.

[Anonymous]

Hi,
Can anyone help me with this as it's driving me mad!

I've recently moved my SME 6.0.1 from my private network to a DMZ.  The server has my primary website mail and two virtual domains.  The trouble is that I cant send mail to any of the domains from the internet.  I keep getting this sort of message:

Your message has encountered delivery problems to the following recipient(s):

xxxxx@mydomain.org.uk
Delivery failed
550 Relaying is prohibited

No recipients were successfully delivered to.

Reporting-MTA: dns; MS1.xxxxxxxxxx.com
Received-From-MTA: dns; server2 (unverified [10.0.0.4])
Arrival-Date: Thu, 27 May 2004 08:50:48 +0100

Final-Recipient: rfc822; xxxxx@mydomain.org.uk
Action: failed
Status: 5.0.0 (Permanent failure - no additional status information available)
Remote-MTA: dns; mail.mydomain.org.uk
Diagnostic-Code: smtp; 550 Relaying is prohibited

==================================================

Now, the server is operating in private server only mode.

E-mail retrieval mode: Standard
POP and IMAP server access: Public

The server WAS running multi drop picking up mail from a POP3 account and the old server seetings are still visible.  No matter how many times I delete them and save the settings, they won't disappear.

Can anyone help me here?

Many thanks
for any help you can give me.
N

[raem]

> POP and IMAP server access: Public

As I read it you are attempting a POP connection to your server from a remote location using public POP access.
Your server won't let you do this as it will not act as a mail relay. Anyone could easily connect to your server and send relayed mail, not good. Public POP is insecure.
Best you instal secure mail contrib from pagefault.org or alternatively enable Webmail for secure https public access, and send mail using webmail from your remote location.


> The server WAS running multi drop ........and the old server settings are still visible

These settings are ignored if you select Standard delivery, which you said you have selected. I'm pretty sure it says that in the panel.

[ntblade]

Hi Ray, thanks for your response

> POP and IMAP server access: Public

Isn't that to allow users to log in and check their mail?

> As I read it you are attempting a POP connection to your server from a remote location using public POP access.

I'm trying to send mail to myself (as a test) to
xxxxx@mydomain.org.uk from my work email client.

Is that more clear?
Thanks

[dmajwool]

   
> POP and IMAP server access: Public
Isn't that to allow users to log in and check their mail?

To read mail yes, but not use the remote SME mail server to send mail.

> As I read it you are attempting a POP connection to your server from a remote location using public POP access.
I'm trying to send mail to myself (as a test) to
xxxxx@mydomain.org.uk from my work email client.
Is that more clear?

It should work as long as your work email client is using your work's smtp server to deliver the mail to your home address.

Hope I have understood you

David

[ntblade]

Thanks again for the reply.

To read mail yes, but not use the remote SME mail server to send mail.

Yep that's fine

It should work as long as your work email client is using your work's smtp server to deliver the mail to your home address.

We have our own SMTP server at work.  It also fails if I send mail from a web account.  Other people can't send to my server either.  Any other suggestions
N

[ntblade]

Eeeek!

If I do:
telnet mail.mydomain.org 110

I get:
+OK Microsoft Exchange POP3 server version 5.5.2653.23 ready

Any ideas?

[ntblade]

Fixed it!
I had typed one number wrong in the port forwarding section of my firewall.  Some poor lot were getting my email sent to them.  Sorry for being stupid but thanks for the help anyway
N