Mailing List Archive: Smarthost (outgoing mail through Remote SMTP Server)

Smarthost (outgoing mail through Remote SMTP Server)

Mar 20, 2013, 11:17 AM

Post #1 of 10 (9123 views)

Hi, We want to setup so that all outgoing mail relay on Remote SMTP Server
(port 2525). We have installed qmail-smtp-auth and qmail-remote-auth
patches. The content of /var/qmail/control/smtproutes is:

:remotesmtpserver.com:2525 -username password

Also, tried this (without - before username):

:remotesmtpserver.com:2525 username password

We tried to send a message from command line as below:

# /var/qmail/bin/qmail-inject <<EOM
from: myuserid@gmail.com
Return-Path: myuserid@gmail.com
to: anotheruser@gmail.com
subject: Test Qmail

This is a test message from qmail.
EOM

Unfortunately, We are getting following error:

delivery 1: failure: 207.58.xxx.xxx_does_not_like_recipient./
Remote_host_said:_550_relay_refused_myuserid@gmail.com/184.106.xxx.xxx_unauthenticated/Giving_up_on_207.58.xxx.xxx./

We are wondering that this is somthing we need to do at our Qmail server or
it is related with Remote SMTP Server.

Any help on this is highly appreciated.

Thanks,
Sikkandar.

Re: Smarthost (outgoing mail through Remote SMTP Server) [ In reply to ]

cberry at davistl

Mar 21, 2013, 9:08 AM

Post #2 of 10 (8937 views)

Permalink

>207.58.xxx.xxx_does_not_like_recipient./Remote_host_said:_550_relay_refused_myuserid@gmail.com/184.106.xxx.xxx_unauthenticated/Giving_up_on_207.58.xxx.xxx./

Based on the error message it looks like the remote server doesn't think you're a valid relay user. If you look at why at it refused you though, it's saying that 184.106.xxx.xxx was unauthenticated which means that the auth portion of the conversation isn't being completed correctly. Try doing it manually and see what happens.

Re: Smarthost (outgoing mail through Remote SMTP Server) [ In reply to ]

shepherdzw at gmail

Mar 21, 2013, 10:26 AM

Post #3 of 10 (8959 views)

Permalink

does your qmail setup have the qmail smtproute auth patch?if your answer is no then you need to patch you source & recompile qmail.

cheers

Sent from my iPhone

On 21 Mar,2013, at 6:08 PM, "Chris Berry" <cberry@davistl.com> wrote:

> >207.58.xxx.xxx_does_not_like_recipient./Remote_host_said:_550_relay_refused_myuserid@gmail.com/184.106.xxx.xxx_unauthenticated/Giving_up_on_207.58.xxx.xxx./
>
> Based on the error message it looks like the remote server doesn't think you're a valid relay user. If you look at why at it refused you though, it's saying that 184.106.xxx.xxx was unauthenticated which means that the auth portion of the conversation isn't being completed correctly. Try doing it manually and see what happens.

Re: Smarthost (outgoing mail through Remote SMTP Server) [ In reply to ]

rnsikkandar at gmail

Mar 22, 2013, 4:24 AM

Post #4 of 10 (8966 views)

Permalink

smtproute auth patch is now applied as per the instruction here
http://www.syslogs.org/qmail-smtproute-auth-patch/ and here
http://petrocik.net/blog/?p=21

This time the error is different:

@40000000514c3d701229dd3c starting delivery 21: msg 278706 to remote
anotheruser@gmail.com
@40000000514c3d701229ecdc status: local 0/10 remote 1/20
@40000000514c3d7017be3194 delivery 21: deferral:
AUTH_LOGIN_not_supported_for_207.58.xxx.xxx./Remote_host_said:_250-remotesmtp.com_Hello_184-106-xxxx-xxx.static.cloud-ips.com_[184.106.xxxx.xxx]/250-SIZE_52428800/250-PIPELINING/250-AUTH_CRAM-MD5_PLAIN_LOGIN/250-STARTTLS/250_HELP/

(NOTE: Using 'telnet remotesmtp.com 25' with encoded username and password,
the remotesmtp.com server accept mail)

On Thu, Mar 21, 2013 at 10:56 PM, Shepherd Nhongo <shepherdzw@gmail.com>wrote:

> does your qmail setup have the qmail smtproute auth patch?if your answer
> is no then you need to patch you source & recompile qmail.
>
> cheers
>
> Sent from my iPhone
>
> On 21 Mar,2013, at 6:08 PM, "Chris Berry" <cberry@davistl.com> wrote:
>
> >207.58.xxx.xxx_does_not_like_recipient./
> Remote_host_said:_550_relay_refused_myuserid@gmail.com/184.106.xxx.xxx_unauthenticated/Giving_up_on_207.58.xxx.xxx./
>
> Based on the error message it looks like the remote server doesn't think
> you're a valid relay user. If you look at why at it refused you though,
> it's saying that 184.106.xxx.xxx was unauthenticated which means that the
> auth portion of the conversation isn't being completed correctly. Try
> doing it manually and see what happens.
>
>

Re: Smarthost (outgoing mail through Remote SMTP Server) [ In reply to ]

rnsikkandar at gmail

Mar 25, 2013, 6:31 AM

Post #5 of 10 (8937 views)

Permalink

It seems QMail does not send proper username and password to Remote SMTP
Server. Below is the log, got it from remote SMTP server log:

On Fri, Mar 22, 2013 at 4:54 PM, Sikkandar Dulkaranai <rnsikkandar@gmail.com
> wrote:

> smtproute auth patch is now applied as per the instruction here
> http://www.syslogs.org/qmail-smtproute-auth-patch/ and here
> http://petrocik.net/blog/?p=21
>
> This time the error is different:
>
> @40000000514c3d701229dd3c starting delivery 21: msg 278706 to remote
> anotheruser@gmail.com
> @40000000514c3d701229ecdc status: local 0/10 remote 1/20
> @40000000514c3d7017be3194 delivery 21: deferral:
> AUTH_LOGIN_not_supported_for_207.58.xxx.xxx./Remote_host_said:_250-remotesmtp.com_Hello_184-106-xxxx-xxx.static.cloud-ips.com_[184.106.xxxx.xxx]/250-SIZE_52428800/250-PIPELINING/250-AUTH_CRAM-MD5_PLAIN_LOGIN/250-STARTTLS/250_HELP/
>
> (NOTE: Using 'telnet remotesmtp.com 25' with encoded username and
> password, the remotesmtp.com server accept mail)
>
>
> On Thu, Mar 21, 2013 at 10:56 PM, Shepherd Nhongo <shepherdzw@gmail.com>wrote:
>
>> does your qmail setup have the qmail smtproute auth patch?if your answer
>> is no then you need to patch you source & recompile qmail.
>>
>> cheers
>>
>> Sent from my iPhone
>>
>> On 21 Mar,2013, at 6:08 PM, "Chris Berry" <cberry@davistl.com> wrote:
>>
>> >207.58.xxx.xxx_does_not_like_recipient./
>> Remote_host_said:_550_relay_refused_myuserid@gmail.com/184.106.xxx.xxx_unauthenticated/Giving_up_on_207.58.xxx.xxx./
>>
>> Based on the error message it looks like the remote server doesn't
>> think you're a valid relay user. If you look at why at it refused you
>> though, it's saying that 184.106.xxx.xxx was unauthenticated which means
>> that the auth portion of the conversation isn't being completed correctly.
>> Try doing it manually and see what happens.
>>
>>
>

Re: Smarthost (outgoing mail through Remote SMTP Server) [ In reply to ]

rnsikkandar at gmail

Mar 25, 2013, 6:34 AM

Post #6 of 10 (8976 views)

Permalink

Here is the log from Remote SMTP server:

2013-03-22 05:26:41 psqldb_auth_login authenticator failed for
184-106-xxx-xxx.static.cloud-ips.com (test.mydomain.net)
[184.106.249.81]: 535 Incorrect authentication data (set_id=AB\023)
2013-03-22 05:26:41 unexpected disconnect of 184.106.xxx.xxx:35127 via
207.58.xxx.xxx:2525 connection-lost

On Mon, Mar 25, 2013 at 7:01 PM, Sikkandar Dulkaranai <rnsikkandar@gmail.com
> wrote:

> It seems QMail does not send proper username and password to Remote SMTP
> Server. Below is the log, got it from remote SMTP server log:
>
>
>
> On Fri, Mar 22, 2013 at 4:54 PM, Sikkandar Dulkaranai <
> rnsikkandar@gmail.com> wrote:
>
>> smtproute auth patch is now applied as per the instruction here
>> http://www.syslogs.org/qmail-smtproute-auth-patch/ and here
>> http://petrocik.net/blog/?p=21
>>
>> This time the error is different:
>>
>> @40000000514c3d701229dd3c starting delivery 21: msg 278706 to remote
>> anotheruser@gmail.com
>> @40000000514c3d701229ecdc status: local 0/10 remote 1/20
>> @40000000514c3d7017be3194 delivery 21: deferral:
>> AUTH_LOGIN_not_supported_for_207.58.xxx.xxx./Remote_host_said:_250-remotesmtp.com_Hello_184-106-xxxx-xxx.static.cloud-ips.com_[184.106.xxxx.xxx]/250-SIZE_52428800/250-PIPELINING/250-AUTH_CRAM-MD5_PLAIN_LOGIN/250-STARTTLS/250_HELP/
>>
>> (NOTE: Using 'telnet remotesmtp.com 25' with encoded username and
>> password, the remotesmtp.com server accept mail)
>>
>>
>> On Thu, Mar 21, 2013 at 10:56 PM, Shepherd Nhongo <shepherdzw@gmail.com>wrote:
>>
>>> does your qmail setup have the qmail smtproute auth patch?if your answer
>>> is no then you need to patch you source & recompile qmail.
>>>
>>> cheers
>>>
>>> Sent from my iPhone
>>>
>>> On 21 Mar,2013, at 6:08 PM, "Chris Berry" <cberry@davistl.com> wrote:
>>>
>>> >207.58.xxx.xxx_does_not_like_recipient./
>>> Remote_host_said:_550_relay_refused_myuserid@gmail.com/184.106.xxx.xxx_unauthenticated/Giving_up_on_207.58.xxx.xxx./
>>>
>>> Based on the error message it looks like the remote server doesn't
>>> think you're a valid relay user. If you look at why at it refused you
>>> though, it's saying that 184.106.xxx.xxx was unauthenticated which means
>>> that the auth portion of the conversation isn't being completed correctly.
>>> Try doing it manually and see what happens.
>>>
>>>
>>
>

Re: Smarthost (outgoing mail through Remote SMTP Server) [ In reply to ]

feh at fehcom

Mar 25, 2013, 6:52 AM

Post #7 of 10 (8936 views)

Permalink

Hi,

does your authentication user name includes 'white spaces' ? If so, that's the failure.

regards.
--eh.

Am 25.03.2013 um 14:31 schrieb Sikkandar Dulkaranai:

> It seems QMail does not send proper username and password to Remote SMTP Server. Below is the log, got it from remote SMTP server log:
>
>
>
> On Fri, Mar 22, 2013 at 4:54 PM, Sikkandar Dulkaranai <rnsikkandar@gmail.com> wrote:
> smtproute auth patch is now applied as per the instruction here http://www.syslogs.org/qmail-smtproute-auth-patch/ and here http://petrocik.net/blog/?p=21
>
> This time the error is different:
>
> @40000000514c3d701229dd3c starting delivery 21: msg 278706 to remote anotheruser@gmail.com
> @40000000514c3d701229ecdc status: local 0/10 remote 1/20
> @40000000514c3d7017be3194 delivery 21: deferral: AUTH_LOGIN_not_supported_for_207.58.xxx.xxx./Remote_host_said:_250-remotesmtp.com_Hello_184-106-xxxx-xxx.static.cloud-ips.com_[184.106.xxxx.xxx]/250-SIZE_52428800/250-PIPELINING/250-AUTH_CRAM-MD5_PLAIN_LOGIN/250-STARTTLS/250_HELP/
>
> (NOTE: Using 'telnet remotesmtp.com 25' with encoded username and password, the remotesmtp.com server accept mail)
>
>
> On Thu, Mar 21, 2013 at 10:56 PM, Shepherd Nhongo <shepherdzw@gmail.com> wrote:
> does your qmail setup have the qmail smtproute auth patch?if your answer is no then you need to patch you source & recompile qmail.
>
> cheers
>
> Sent from my iPhone
>
> On 21 Mar,2013, at 6:08 PM, "Chris Berry" <cberry@davistl.com> wrote:
>
>> >207.58.xxx.xxx_does_not_like_recipient./Remote_host_said:_550_relay_refused_myuserid@gmail.com/184.106.xxx.xxx_unauthenticated/Giving_up_on_207.58.xxx.xxx./
>>
>> Based on the error message it looks like the remote server doesn't think you're a valid relay user. If you look at why at it refused you though, it's saying that 184.106.xxx.xxx was unauthenticated which means that the auth portion of the conversation isn't being completed correctly. Try doing it manually and see what happens.
>
>

--
Dr. Erwin Hoffmann | FEHCom | http://www.fehcom.de | PGP Key-Id: 7E4034BE

Re: Smarthost (outgoing mail through Remote SMTP Server) [ In reply to ]

rnsikkandar at gmail

Mar 25, 2013, 7:04 AM

Post #8 of 10 (8933 views)

Permalink

No space in username and username is base-64 encoded and stored in
control/smtpauth file. Is there a way to run qmail in Verbose mode to see
what is going on when email is being transmitted to remote SMTP?

On Mon, Mar 25, 2013 at 7:22 PM, Erwin Hoffmann <feh@fehcom.de> wrote:

> Hi,
>
> does your authentication user name includes 'white spaces' ? If so, that's
> the failure.
>
> regards.
> --eh.
>
> Am 25.03.2013 um 14:31 schrieb Sikkandar Dulkaranai:
>
> It seems QMail does not send proper username and password to Remote SMTP
> Server. Below is the log, got it from remote SMTP server log:
>
>
>
> On Fri, Mar 22, 2013 at 4:54 PM, Sikkandar Dulkaranai <
> rnsikkandar@gmail.com> wrote:
>
>> smtproute auth patch is now applied as per the instruction here
>> http://www.syslogs.org/qmail-smtproute-auth-patch/ and here
>> http://petrocik.net/blog/?p=21
>>
>> This time the error is different:
>>
>> @40000000514c3d701229dd3c starting delivery 21: msg 278706 to remote
>> anotheruser@gmail.com
>> @40000000514c3d701229ecdc status: local 0/10 remote 1/20
>> @40000000514c3d7017be3194 delivery 21: deferral:
>> AUTH_LOGIN_not_supported_for_207.58.xxx.xxx./Remote_host_said:_250-remotesmtp.com_Hello_184-106-xxxx-xxx.static.cloud-ips.com_[184.106.xxxx.xxx]/250-SIZE_52428800/250-PIPELINING/250-AUTH_CRAM-MD5_PLAIN_LOGIN/250-STARTTLS/250_HELP/
>>
>> (NOTE: Using 'telnet remotesmtp.com 25' with encoded username and
>> password, the remotesmtp.com server accept mail)
>>
>>
>> On Thu, Mar 21, 2013 at 10:56 PM, Shepherd Nhongo <shepherdzw@gmail.com>wrote:
>>
>>> does your qmail setup have the qmail smtproute auth patch?if your answer
>>> is no then you need to patch you source & recompile qmail.
>>>
>>> cheers
>>>
>>> Sent from my iPhone
>>>
>>> On 21 Mar,2013, at 6:08 PM, "Chris Berry" <cberry@davistl.com> wrote:
>>>
>>> >207.58.xxx.xxx_does_not_like_recipient./
>>> Remote_host_said:_550_relay_refused_myuserid@gmail.com/184.106.xxx.xxx_unauthenticated/Giving_up_on_207.58.xxx.xxx./
>>>
>>> Based on the error message it looks like the remote server doesn't think
>>> you're a valid relay user. If you look at why at it refused you though,
>>> it's saying that 184.106.xxx.xxx was unauthenticated which means that the
>>> auth portion of the conversation isn't being completed correctly. Try
>>> doing it manually and see what happens.
>>>
>>>
>>
>
> --
> Dr. Erwin Hoffmann | FEHCom | http://www.fehcom.de | PGP Key-Id: 7E4034BE
>
>
>

Re: Smarthost (outgoing mail through Remote SMTP Server) [ In reply to ]

feh at fehcom

Mar 25, 2013, 7:12 AM

Post #9 of 10 (8956 views)

Permalink

H,

Am 25.03.2013 um 15:04 schrieb Sikkandar Dulkaranai:

> No space in username and username is base-64 encoded and stored in control/smtpauth file. Is there a way to run qmail in Verbose mode to see what is going on when email is being transmitted to remote SMTP?
>

well, I don't know the SMTP-Auth patch you have applied. The one's I know don't require a BASE64 encoded username. If the base64.c module is missing; at least you need to encode both; username + password.

If so, take care about trailing '\n' while encoding. My SMTP Auth tutorial may give you some hints:

http://www.fehcom.de/qmail/smtpauth.html

regards.
--eh.

>
> On Mon, Mar 25, 2013 at 7:22 PM, Erwin Hoffmann <feh@fehcom.de> wrote:
> Hi,
>
> does your authentication user name includes 'white spaces' ? If so, that's the failure.
>
> regards.
> --eh.
>
> Am 25.03.2013 um 14:31 schrieb Sikkandar Dulkaranai:
>
>> It seems QMail does not send proper username and password to Remote SMTP Server. Below is the log, got it from remote SMTP server log:
>>
>>
>>
>> On Fri, Mar 22, 2013 at 4:54 PM, Sikkandar Dulkaranai <rnsikkandar@gmail.com> wrote:
>> smtproute auth patch is now applied as per the instruction here http://www.syslogs.org/qmail-smtproute-auth-patch/ and here http://petrocik.net/blog/?p=21
>>
>> This time the error is different:
>>
>> @40000000514c3d701229dd3c starting delivery 21: msg 278706 to remote anotheruser@gmail.com
>> @40000000514c3d701229ecdc status: local 0/10 remote 1/20
>> @40000000514c3d7017be3194 delivery 21: deferral: AUTH_LOGIN_not_supported_for_207.58.xxx.xxx./Remote_host_said:_250-remotesmtp.com_Hello_184-106-xxxx-xxx.static.cloud-ips.com_[184.106.xxxx.xxx]/250-SIZE_52428800/250-PIPELINING/250-AUTH_CRAM-MD5_PLAIN_LOGIN/250-STARTTLS/250_HELP/
>>
>> (NOTE: Using 'telnet remotesmtp.com 25' with encoded username and password, the remotesmtp.com server accept mail)
>>
>>
>> On Thu, Mar 21, 2013 at 10:56 PM, Shepherd Nhongo <shepherdzw@gmail.com> wrote:
>> does your qmail setup have the qmail smtproute auth patch?if your answer is no then you need to patch you source & recompile qmail.
>>
>> cheers
>>
>> Sent from my iPhone
>>
>> On 21 Mar,2013, at 6:08 PM, "Chris Berry" <cberry@davistl.com> wrote:
>>
>>> >207.58.xxx.xxx_does_not_like_recipient./Remote_host_said:_550_relay_refused_myuserid@gmail.com/184.106.xxx.xxx_unauthenticated/Giving_up_on_207.58.xxx.xxx./
>>>
>>> Based on the error message it looks like the remote server doesn't think you're a valid relay user. If you look at why at it refused you though, it's saying that 184.106.xxx.xxx was unauthenticated which means that the auth portion of the conversation isn't being completed correctly. Try doing it manually and see what happens.
>>
>>
>
>
> --
> Dr. Erwin Hoffmann | FEHCom | http://www.fehcom.de | PGP Key-Id: 7E4034BE
>
>
>

--
Dr. Erwin Hoffmann | FEHCom | http://www.fehcom.de | PGP Key-Id: 7E4034BE

Re: Smarthost (outgoing mail through Remote SMTP Server) [ In reply to ]

rnsikkandar at gmail

Apr 3, 2013, 5:47 AM

Post #10 of 10 (8903 views)

Permalink

Just an update on this. I have applied the patch available here
http://www.ingorohloff.de/soft/qmail.html. It worked for me.

Thanks to everyone responded in this thread. Special thanks to Erwin
Hoffmann.

On Mon, Mar 25, 2013 at 7:42 PM, Erwin Hoffmann <feh@fehcom.de> wrote:

> H,
>
>
>
> Am 25.03.2013 um 15:04 schrieb Sikkandar Dulkaranai:
>
> No space in username and username is base-64 encoded and stored in
> control/smtpauth file. Is there a way to run qmail in Verbose mode to see
> what is going on when email is being transmitted to remote SMTP?
>
>
> well, I don't know the SMTP-Auth patch you have applied. The one's I know
> don't require a BASE64 encoded username. If the base64.c module is missing;
> at least you need to encode both; username + password.
>
> If so, take care about trailing '\n' while encoding. My SMTP Auth tutorial
> may give you some hints:
>
> http://www.fehcom.de/qmail/smtpauth.html
>
> regards.
> --eh.
>
>
> On Mon, Mar 25, 2013 at 7:22 PM, Erwin Hoffmann <feh@fehcom.de> wrote:
>
>> Hi,
>>
>> does your authentication user name includes 'white spaces' ? If so,
>> that's the failure.
>>
>> regards.
>> --eh.
>>
>> Am 25.03.2013 um 14:31 schrieb Sikkandar Dulkaranai:
>>
>> It seems QMail does not send proper username and password to Remote SMTP
>> Server. Below is the log, got it from remote SMTP server log:
>>
>>
>>
>> On Fri, Mar 22, 2013 at 4:54 PM, Sikkandar Dulkaranai <
>> rnsikkandar@gmail.com> wrote:
>>
>>> smtproute auth patch is now applied as per the instruction here
>>> http://www.syslogs.org/qmail-smtproute-auth-patch/ and here
>>> http://petrocik.net/blog/?p=21
>>>
>>> This time the error is different:
>>>
>>> @40000000514c3d701229dd3c starting delivery 21: msg 278706 to remote
>>> anotheruser@gmail.com
>>> @40000000514c3d701229ecdc status: local 0/10 remote 1/20
>>> @40000000514c3d7017be3194 delivery 21: deferral:
>>> AUTH_LOGIN_not_supported_for_207.58.xxx.xxx./Remote_host_said:_250-remotesmtp.com_Hello_184-106-xxxx-xxx.static.cloud-ips.com_[184.106.xxxx.xxx]/250-SIZE_52428800/250-PIPELINING/250-AUTH_CRAM-MD5_PLAIN_LOGIN/250-STARTTLS/250_HELP/
>>>
>>> (NOTE: Using 'telnet remotesmtp.com 25' with encoded username and
>>> password, the remotesmtp.com server accept mail)
>>>
>>>
>>> On Thu, Mar 21, 2013 at 10:56 PM, Shepherd Nhongo <shepherdzw@gmail.com>wrote:
>>>
>>>> does your qmail setup have the qmail smtproute auth patch?if your
>>>> answer is no then you need to patch you source & recompile qmail.
>>>>
>>>> cheers
>>>>
>>>> Sent from my iPhone
>>>>
>>>> On 21 Mar,2013, at 6:08 PM, "Chris Berry" <cberry@davistl.com> wrote:
>>>>
>>>> >207.58.xxx.xxx_does_not_like_recipient./
>>>> Remote_host_said:_550_relay_refused_myuserid@gmail.com/184.106.xxx.xxx_unauthenticated/Giving_up_on_207.58.xxx.xxx./
>>>>
>>>> Based on the error message it looks like the remote server doesn't
>>>> think you're a valid relay user. If you look at why at it refused you
>>>> though, it's saying that 184.106.xxx.xxx was unauthenticated which means
>>>> that the auth portion of the conversation isn't being completed correctly.
>>>> Try doing it manually and see what happens.
>>>>
>>>>
>>>
>>
>> --
>> Dr. Erwin Hoffmann | FEHCom | http://www.fehcom.de | PGP Key-Id: 7E4034BE
>>
>>
>>
>
> --
> Dr. Erwin Hoffmann | FEHCom | http://www.fehcom.de | PGP Key-Id: 7E4034BE
>
>
>