Separate SMTP authentification for each user

Aug 11 05 10:23 am

In my wingate version 6.0.4 I have setup the local mail server with 4 different user. Each user has an own local mailbox. I also have an email account for each user at my provider gmx.

The SMTP Server mail.gmx.net checks user name and password sending an email. Therefore I configured the Wingate Mail Server to this SMTP server under "Server" accordingly with username and password. I used the account from one of my users. The server should deliver all mails to the SMTP server mail.gmx.net. So the option "how to deliver: Use gateway" is selected.

But the server accepts only mail sent by the one account with wich the "server properties" are configured with. All other mail cannot be delivered because the smtp server checks the adress of the sender against the logged in account. See returned email below.

How can I configure wingate? Is there a chance to setup the smtp server login separate for each user?

Code:: Reason: Remote server failed FROM command ---------------------------------------------- A transcript of the session follows ---------------------------------------------- * Attempting connection to mail.gmx.net[213.165.64.20] - succeeded <= 220 {mp007} GMX Mailservices ESMTP => EHLO gmx.de <= 250-{mp007} GMX Mailservices <= 250-8BITMIME <= 250-ENHANCEDSTATUSCODES <= 250-AUTH=LOGIN CRAM-MD5 PLAIN <= 250-AUTH CRAM-MD5 LOGIN PLAIN <= 250 STARTTLS => STARTTLS <= 220 2.7.0 {mp007} Ready to start TLS => EHLO gmx.de <= 250-{mp007} GMX Mailservices <= 250-8BITMIME <= 250-ENHANCEDSTATUSCODES <= 250-AUTH=LOGIN CRAM-MD5 PLAIN <= 250-AUTH CRAM-MD5 LOGIN PLAIN <= 250 STARTTLS => AUTH CRAM-MD5 <= 334 PDIxMTkzLjExMjM3MDc4NDBAbXAwMDc+ <= 235 2.7.0 {mp007} Go ahead => MAIL FROM:<xxxx.yyyyyyy@gmx.de> <= 550 5.7.0 {mp007} Sender address does not belong to logged in user

Aug 12 05 2:13 pm

Can you try this: On the WinGate server, Delivery tab:

Click the button where the red cross is (above), and delete out the user name and password (image below).

On the email client, the setup would be:
POP3 / SMTP Server: Internal IP address of WinGate server
username: skater@gmx.de
password: blabla
"My SMTP server requires authentication"

On another computers email client, the setup would be:
POP3 / SMTP Server: Internal IP address of WinGate server
username: skater_mates@gmx.de
password: blablablur
"My SMTP server requires authentication"

If you are still having problems:

1. What domain you are using in Wingate as shown in image below.
2. What error message is happening on the email clients

Let us know how you got on.

Aug 15 05 1:42 am

Thank your for your answer, but it does not help.

Here a short report on the changes I made:

Here my first remark: My local mailbox is named "josef", my e-mail account at gmx is named "josef.skater@gmx.de". I have an email handler in wingate mapping "josef.skater" to "josef". So receiving mails works fine with both usernames on the email client. The passwords are different between my local mailbox "josef" and my GMX-Mailbox "josef.skater". At Outlook Express you can setup a different username/password for smtp. But trying to send mails with GMX password did not work either.

My domain in wingate is set to "gmx.de". I have aliases like "home" defined.

Here additional information after sending to "mail.gmx.net:
1) Logfile SMTP

Code:: 08/14/05 12:53:59 127.0.0.2 0000000994 Debug: ==== Attempting connection to mail.gmx.net[213.165.64.20] 08/14/05 12:54:00 127.0.0.2 0000000994 Debug: mail.gmx.net <=S: 220 {mp014} GMX Mailservices ESMTP 08/14/05 12:54:00 127.0.0.2 0000000994 Debug: mail.gmx.net C=>: EHLO gmx.de 08/14/05 12:54:00 127.0.0.2 0000000994 Debug: mail.gmx.net <=S: 250-{mp014} GMX Mailservices 08/14/05 12:54:00 127.0.0.2 0000000994 Debug: mail.gmx.net <=S: 250-8BITMIME 08/14/05 12:54:00 127.0.0.2 0000000994 Debug: mail.gmx.net <=S: 250-ENHANCEDSTATUSCODES 08/14/05 12:54:00 127.0.0.2 0000000994 Debug: mail.gmx.net <=S: 250-AUTH=LOGIN CRAM-MD5 PLAIN 08/14/05 12:54:00 127.0.0.2 0000000994 Debug: mail.gmx.net <=S: 250-AUTH CRAM-MD5 LOGIN PLAIN 08/14/05 12:54:00 127.0.0.2 0000000994 Debug: mail.gmx.net <=S: 250 STARTTLS 08/14/05 12:54:00 127.0.0.2 0000000994 Debug: mail.gmx.net C=>: STARTTLS 08/14/05 12:54:00 127.0.0.2 0000000994 Debug: mail.gmx.net <=S: 220 2.7.0 {mp014} Ready to start TLS 08/14/05 12:54:00 127.0.0.2 0000000994 Debug: mail.gmx.net C=>: EHLO gmx.de 08/14/05 12:54:00 127.0.0.2 0000000994 Debug: mail.gmx.net <=S: 250-{mp014} GMX Mailservices 08/14/05 12:54:00 127.0.0.2 0000000994 Debug: mail.gmx.net <=S: 250-8BITMIME 08/14/05 12:54:00 127.0.0.2 0000000994 Debug: mail.gmx.net <=S: 250-ENHANCEDSTATUSCODES 08/14/05 12:54:00 127.0.0.2 0000000994 Debug: mail.gmx.net <=S: 250-AUTH=LOGIN CRAM-MD5 PLAIN 08/14/05 12:54:00 127.0.0.2 0000000994 Debug: mail.gmx.net <=S: 250-AUTH CRAM-MD5 LOGIN PLAIN 08/14/05 12:54:00 127.0.0.2 0000000994 Debug: mail.gmx.net <=S: 250 STARTTLS 08/14/05 12:54:00 127.0.0.2 0000000994 Debug: mail.gmx.net C=>: MAIL FROM: 08/14/05 12:54:00 127.0.0.2 0000000994 Debug: mail.gmx.net <=S: 550 5.7.0 {mp014} Need to authenticate via SMTP-AUTH-Login 08/14/05 12:54:00 127.0.0.2 0000000994 Debug: mail.gmx.net C=>: RSET 08/14/05 12:54:00 127.0.0.2 0000000994 Debug: mail.gmx.net <=S: 250 2.0.0 {mp014} Flushed 08/14/05 12:54:00 127.0.0.2 0000000994 Debug: mail.gmx.net C=>: QUIT 08/14/05 12:54:00 127.0.0.2 0000000994 Debug: ==== Server mail.gmx.net closed connection

2) Returned mail to sender

Code:: This is a system generated message - Please do not reply ---------------------------------------------- Permanent delivery failure ---------------------------------------------- Your message has encountered permanent delivery problems to the following recipients: xxxxx.yyyy@t-online.de Reason: Remote server failed FROM command ---------------------------------------------- A transcript of the session follows ---------------------------------------------- * Attempting connection to mail.gmx.net[213.165.64.20] - succeeded <= 220 {mp014} GMX Mailservices ESMTP => EHLO gmx.de <= 250-{mp014} GMX Mailservices <= 250-8BITMIME <= 250-ENHANCEDSTATUSCODES <= 250-AUTH=LOGIN CRAM-MD5 PLAIN <= 250-AUTH CRAM-MD5 LOGIN PLAIN <= 250 STARTTLS => STARTTLS <= 220 2.7.0 {mp014} Ready to start TLS => EHLO gmx.de <= 250-{mp014} GMX Mailservices <= 250-8BITMIME <= 250-ENHANCEDSTATUSCODES <= 250-AUTH=LOGIN CRAM-MD5 PLAIN <= 250-AUTH CRAM-MD5 LOGIN PLAIN <= 250 STARTTLS => MAIL FROM:<pppp.skater@gmx.de> <= 550 5.7.0 {mp014} Need to authenticate via SMTP-AUTH-Login ---------------------------------------------- Your original message (in part): ---------------------------------------------- Received: From josef (unverified [127.0.0.1]) by SMTP Server [127.0.0.1] (WinGate SMTP Receiver v6.0.4 (Build 1025)) with SMTP id <0000000211@gmx.de>; Sun, 14 Aug 2005 12:53:43 +0200 Message-ID: <006e01c5a0be$6fdd4650$0100a8c0@josef> From: "ppppp qqqq" <pppp.skater@gmx.de> To: "<xxxxx.yyyy@t-online.de> Subject: Test Date: Sun, 14 Aug 2005 12:53:42 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_006B_01C5A0CF.33557480" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2527 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 This is a multi-part message in MIME format. ------=_NextPart_000_006B_01C5A0CF.33557480 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Test

Here additional information after sending to "mx0.gmx.net:
1) Logfile SMTP

Code:: 08/14/05 14:11:22 SMTP Server Debug: Domain send queue forced (ignores scheduled time and thread count) 08/14/05 14:11:22 127.0.0.2 0000001745 Debug: ==== Attempting connection to mx0.gmx.net[213.165.64.100] 08/14/05 14:11:22 127.0.0.2 0000001745 Debug: ==== Server mx0.gmx.net closed connection 08/14/05 14:11:24 127.0.0.2 0000001745 Traffic 0 0 0 0 2s 08/14/05 14:11:24 127.0.0.2 0000001745 Terminated exit code 0 08/14/05 14:11:24 SMTP Server Debug: Domain send queue forced (ignores scheduled time and thread count) 08/14/05 14:11:24 127.0.0.2 0000001746 Requested: SMTP Delivery to mx0.gmx.net [try 20] : Failed to deliver after 20 tries 08/14/05 14:11:24 127.0.0.2 0000001746 Debug: ==== job completed error 4 with RCP file remaining 0000000215 08/14/05 14:11:24 127.0.0.2 0000001746 Requested: Returned undeliverable mail for mx0.gmx.net

2) Returned mail to sender

Code:: This is a system generated message - Please do not reply ---------------------------------------------- Permanent delivery failure ---------------------------------------------- Your message has encountered permanent delivery problems to the following recipients: xxx.yyyy@t-online.de Reason: Failed all retries, giving up ---------------------------------------------- Your original message (in part): ---------------------------------------------- Received: From josef (unverified [127.0.0.1]) by SMTP Server [127.0.0.1] (WinGate SMTP Receiver v6.0.4 (Build 1025)) with SMTP id <0000000215@gmx.de>; Sun, 14 Aug 2005 13:51:22 +0200 Message-ID: <00b901c5a0c6$7dbcef70$0100a8c0@josef> From: "pppp qqqq" <pppp.skater@gmx.de> To: <xxxx.yyyyyy@t-online.de> Subject: Test Date: Sun, 14 Aug 2005 13:51:22 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00B6_01C5A0D7.4139D890" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2527 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 This is a multi-part message in MIME format. ------=_NextPart_000_00B6_01C5A0D7.4139D890 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Test

Why is is not possible in wingate to define an smtp server authentification for each local mailbox? This would help in my case.

The "gmx.net" server allows one other SMTP autentification method ""POP3 before SMTP". do you see a chnce to use this?

Aug 15 05 10:36 pm

Hi Skater,

This can be done, in fact have just modelled it on my network.

NAT must be installed and active.

Turn off the SMTP Server in Wingate with right click / stop.

In the client application configure for a direct connection to the internet:

Server: mail.isp.com
Auth: *************

Configure the NIC of the workstation to have a Default Gateway & DNS pointing to the Wingate machine eg: 192.168.0.1

If this schema works change the SMTP Server Startup in Wingate to disabled.

Report back if this is a solution for you.

Aug 16 05 4:42 am

Hi Nev,

I do not prefer to setup my clients in that way that they send email directly to my ISP. I want also use internal mails, there wingate should handle sending of all mails.

Regards
The Skater

Aug 16 05 5:55 pm

TheSkater wrote:Hi Nev,

I do not prefer to setup my clients in that way that they send email directly to my ISP. I want also use internal mails, there wingate should handle sending of all mails.

Regards
The Skater

Ok, Wingate is still handling the mail except it is NAT traffic, instead of Proxy server.

You could create another SMTP server with a different port say 8025, use that for local mail transfer with clients and have your authentication requirements to the internet via NAT.

Otherwise their is little option with this configuration apart from multiple SMTP proxy servers for each account with authentication by Wingate [ugggh] :-((

Aug 18 05 2:12 am

Hi

WinGate was not designed to deal with SMTP servers that need different credentials for each different return address. It can only use one username/password for each server. I don't know of any other mail servers that support this.

Can you talk to your ISP about relaxing this requirement? This is probably your easiest option, if your ISP can allow you to use one account to send from a number of mailboxes, your problem would be solved.

Otherwise, can you get WinGate to deliver directly to the end server rather than delivering all mail to a gateway? Sounds like most SMTP servers on the net are less paranoid than your ISP. Depending on your IP address and how your ISP configures reverse DNS, you may be blocked by some SMTP servers though.

Adrien

Aug 18 05 7:31 pm

Hi adrien,

thanks vor this clear answer about my "paranoid" ISP and the setup within wingate.

What do you mean exactly with "reverse DNS" when delivering mails directly. I tried this first but was not successfull delivering mails to "t-online.de" for example. Where can I find more information or examples for a usefull configuration for direct delivery?

Best regards
Josef