SMTP Mapping = Relaying not allowed

[ngtech]

Hi,
When I use SMTP Mapping, remote server saying 'Relaying not allowed'. (Directly connect to the remote server is fine)

How can I solve it? Pls kindly help.

[logan]

Since your ISP does not allow relayed connections to their SMTP server, you will need to connect to the SMTP server directly from your client computer. To connect to the server directly, your email clients SMTP setting should point to your ISP's SMTP server, and your client computers will need either a NAT connection, or a WGIC connection to WinGate.

Configuring LAN clients to make a NAT connection
http://support.qbik.com/index.php?_a=kn ... ils&_i=119

Configuring LAN clients to make a WGIC connection
http://support.qbik.com/index.php?_a=kn ... ils&_i=120

[ngtech]

My service provider requred me to authenticate myself before sending mail. I did key-in the authentication info in Wingate.

I try out SMTP Mapping also but same error show. I thought SMTP Mapping is transparent to the remote server?

[logan]

The SMTP Mapping isn't transparent, sorry. Since the error message reported that the connection was denied because it was relayed, then I imagine connecting directly to the internet mail server from your client computer will solve the problem.

[ngtech]

Connecting directly to the Internet mail server don't have such problem. But it can't archieve what I want to do.

I am trying to setup an internal smtp server to deliver own domain email internally while outside mail will be route to Internet mail server.

[adrien]

Hi

relaying in this context isn't a function of how you connect to the server, but whether you are attempting to send an email to a local domain or not.

Relaying in SMTP terms is when you ask the SMTP server to take responsibility for delivery of a message to some other SMTP server. Normally ISP email servers won't do this for untrusted clients, i.e. computers outside their network, or computers that don't authenticate to them.

There are 2 SMTP processes in Wingate, the SMTP proxy (old, not recommended), and the SMTP server. The SMTP server can authenticate to your ISP gateway (in Email->Delivery->Deliver mail to gateway, "..." enter username and password).

Otherwise you would need to connect directly to the ISP mail server from your email clients, and have them provide the username and password.

So, depending on how you want email on your LAN to work, either

a) set up the LAN clients to deliver mail to the WinGate server.
* Set up WinGate to deliver to your ISP, with username/password
b) set up the LAN clients to deliver mail directly to your ISP.
* Set up the LAN clients to use the username/password

Adrien

[ngtech]

The SMTP server can authenticate to your ISP gateway (in Email->Delivery->Deliver mail to gateway, "..." enter username and password).

This is what I did. But it still saying me relaying..

FYI, my Wingate version is 6.1.4 Build 1099

[logan]

From what you have said, I am under the impression that your ISP is denying all relayed mail to their server, regardless of authentication. If this is the case, you will need to talk to your ISP about this problem. I am sure they will understand your current situation.

[ngtech]

Actually I did ask them regarding this. Their feedback is as long as I authenticated myself which I did by providing my user name & password to Wingate for authentication with the Internet server.

[adrien]

Hi

can you tell in the WinGate SMTP server logs whether the authentication is succeeding or failing? If you enable debug logging for the SMTP server, you should be able to see this.

Regards

Adrien

[ngtech]

Hi,
Pls advise.

06/25/07 08:53:08 192.168.118.25 myuserid 0000129899 Created:
06/25/07 08:53:08 192.168.118.25 myuserid 0000129899 Debug: <=S: 220 Gateway ESMTP Service ready
06/25/07 08:53:08 192.168.118.25 myuserid 0000129899 Debug: C=>: EHLO mypc
06/25/07 08:53:08 192.168.118.25 myuserid 0000129899 Debug: <=S: 250-Gateway greets you
06/25/07 08:53:08 192.168.118.25 myuserid 0000129899 Debug: <=S: 250 SIZE 0
06/25/07 08:53:09 192.168.118.25 myuserid 0000129899 Debug: C=>: MAIL FROM: <myuserid@mycompany.com>
06/25/07 08:53:09 192.168.118.25 myuserid 0000129899 Debug: <=S: 250 Requested mail action okay, completed
06/25/07 08:53:09 192.168.118.25 myuserid 0000129899 Debug: C=>: RCPT TO: <myuserid@gmail.com>
06/25/07 08:53:09 192.168.118.25 myuserid 0000129899 Debug: <=S: 250 Requested mail action okay, completed
06/25/07 08:53:09 192.168.118.25 myuserid 0000129899 Debug: C=>: DATA
06/25/07 08:53:09 192.168.118.25 myuserid 0000129899 Debug: <=S: 354 Start mail input; end with CRLF.CRLF
06/25/07 08:53:09 192.168.118.25 myuserid 0000129899 Debug: <=S: 250 Mail accepted for delivery; id=0000000064
06/25/07 08:53:09 192.168.118.25 myuserid 0000129899 Requested: SMTP In: mail from myuserid@mycompany.com to myuserid@gmail.com (6223 Bytes)
06/25/07 08:53:09 192.168.118.25 myuserid 0000129899 Debug: C=>: QUIT
06/25/07 08:53:09 192.168.118.25 myuserid 0000129899 Debug: <=S: 221 SMTP Server Service closing transmission channel
06/25/07 08:53:09 192.168.118.25 myuserid 0000129899 Traffic 300 6115 0 0 1s
06/25/07 08:53:09 192.168.118.25 myuserid 0000129899 Terminated exit code 0
06/25/07 08:53:10 127.0.0.2 <system> 0000129901 Debug: ==== Attempting connection to mail.mycompany.com[xxx.xxx.xxx.xxx]
06/25/07 08:53:10 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com <=S: 220 myservice.provider.com -- Server ESMTP (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005))
06/25/07 08:53:10 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com C=>: EHLO Gateway
06/25/07 08:53:10 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com <=S: 250-myservice.provider.com
06/25/07 08:53:10 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com <=S: 250-8BITMIME
06/25/07 08:53:10 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com <=S: 250-PIPELINING
06/25/07 08:53:10 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com <=S: 250-DSN
06/25/07 08:53:10 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com <=S: 250-ENHANCEDSTATUSCODES
06/25/07 08:53:10 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com <=S: 250-EXPN
06/25/07 08:53:10 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com <=S: 250-HELP
06/25/07 08:53:10 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com <=S: 250-XADR
06/25/07 08:53:10 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com <=S: 250-XSTA
06/25/07 08:53:10 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com <=S: 250-XCIR
06/25/07 08:53:10 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com <=S: 250-XGEN
06/25/07 08:53:10 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com <=S: 250-XLOOP 95FD6AD445AF47688EBC450AA21A1D1B
06/25/07 08:53:10 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com <=S: 250-AUTH PLAIN LOGIN
06/25/07 08:53:10 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com <=S: 250-AUTH=LOGIN
06/25/07 08:53:10 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com <=S: 250-ETRN
06/25/07 08:53:10 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com <=S: 250-NO-SOLICITING
06/25/07 08:53:10 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com <=S: 250 SIZE 0
06/25/07 08:53:10 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com C=>: AUTH PLAIN [edited for security reasons]
06/25/07 08:53:10 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com <=S: 501 5.5.0 Invalid input (Invalid authentication protocol).
06/25/07 08:53:10 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com C=>: MAIL FROM:<myuserid@mycompany.com> SIZE=6222
06/25/07 08:53:10 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com <=S: 250 2.5.0 Address and options OK.
06/25/07 08:53:10 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com C=>: RCPT TO:<myuserid@gmail.com>
06/25/07 08:53:10 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com <=S: 530 5.7.1 Relaying not allowed: myuserid@gmail.com
06/25/07 08:53:10 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com C=>: RSET
06/25/07 08:53:11 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com <=S: 250 2.5.0 Ok.
06/25/07 08:53:11 127.0.0.2 <system> 0000129901 Debug: mail.mycompany.com C=>: QUIT
06/25/07 08:53:11 127.0.0.2 <system> 0000129901 Debug: ==== Server mail.mycompany.com closed connection

[Nev]

Hi,

Some remote gateways require different authentication procedures, in the past I have had to use this feature:



Can that help you?

[ngtech]

Hi Nev,
Thank for trying to help.

I enable TLS & use best method available but problem still exist.

[Nev]

Hi Nev,
Thank for trying to help.

I enable TLS & use best method available but problem still exist.

Yes hi,

Did you try the other auth' schemes / SASL, MD5 or NTLM?

[adrien]

in these 2 lines

250-AUTH PLAIN LOGIN
250-AUTH=LOGIN

the server is advertising that it supports 2 types of auth, PLAIN, and LOGIN.

WinGate tried PLAIN, but it looks like it failed for some reason. Try setting it to use LOGIN.

You may need to upgrade to 6.2.1, not sure if 6.1.4 supports LOGIN.

Regards

Adrien

[ngtech]

Nev,
Yes. I tried all the combination I can think of.

[ngtech]

Hi Adrien,
My Wingate 6.1.4 list LOGIN as an option. So does it means it support this authentication method?

[adrien]

hi

Yes, it looks like we put in LOGIN before 6.1.4, so you should try that one.

Adrien

[ngtech]

Hi,
Tried. Not success..

[adrien]

Hi

What do the logs say when it's set to LOGIN?

Adrien