Koozali.org: home of the SME Server

smtp-auth-proxy problem

Offline sum100

  • *
  • 6
  • +0/-0
smtp-auth-proxy problem
« on: March 17, 2011, 07:51:10 AM »
sme server 7.51 or 8b cannot  smtp-auth-proxy to a exim server , any one can help?
it must be /usr/local/sbin/smtp-auth-proxy.pl have problem。

# config show smtp-auth-proxy
smtp-auth-proxy=service
    Debug=disabled
    Passwd=mingle123
    PeerPort=2525
    Userid=mingle@smtp7.tsimtung.com
    status=enabled
# telnet localhost 26
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
451 Could not auth to mail server
Connection closed by foreign host.

In the log:


@400000004d809f2c2f1064ac Net::SMTP=GLOB(0x8e7a384)>>> AUTH PLAIN bWluZ2xlQHNtdHA3LnRzaW10dW5nLmNvbQBtaW5nbGVAc210cDcudHNpbXR1bmcuY29tAG1pbmdsZTEyMw==

This command should be sending the user name and password in the format:

[null_char]user_name[null_char]password

Where [null_char] is the "NULL" character (ASCII code 0).

However after decoding the string above we get:

mingle@smtp7.tsimtung.com[null_char]mingle@smtp7.tsimtung.com[null_char]mingle123

Which is clearly incorrect in format.

To correctly authenticate your server should issue the command like this:

AUTH PLAIN AG1pbmdsZUBzbXRwNy50c2ltdHVuZy5jb20AbWluZ2xlMTIz

Please feel free to manually telnet to our server and test the login.  For your reference, following is a debug log of a simulated SMTP session from smtp7.tsimtung.com using your account to authenticate:

>>> host in hosts_connection_nolog? no (option unset)
>>> host in host_lookup? yes (matched "*")
>>> looking up host name for 127.0.0.1
>>> IP address lookup yielded localhost
>>> gethostbyname looked up these IP addresses:
>>>   name=localhost.localdomain address=127.0.0.1
>>> checking addresses for localhost
>>>   127.0.0.1 OK
>>> host in host_reject_connection? no (option unset)
>>> host in sender_unqualified_hosts? no (option unset)
>>> host in recipient_unqualified_hosts? no (option unset)
>>> host in helo_verify_hosts? no (option unset)
>>> host in helo_try_verify_hosts? no (option unset)
>>> host in helo_accept_junk_hosts? no (option unset)
220 cix005.tsimtung.com ESMTP Exim 4.69 Thu, 17 Mar 2011 13:12:42 +0800
ehlo test.com
>>> host in pipelining_advertise_hosts? yes (matched "*")
>>> host in auth_advertise_hosts? yes (matched "*")
>>> host in tls_advertise_hosts? yes (matched "*")
250-cix005.tsimtung.com Hello localhost [127.0.0.1]
250-SIZE 20971520
250-PIPELINING
250-AUTH PLAIN LOGIN
250-STARTTLS
250 HELP
AUTH PLAIN AG1pbmdsZUBzbXRwNy50c2ltdHVuZy5jb20AbWluZ2xlMTIz
>>> plain authenticator:
>>>   $auth1 =
>>>   $auth2 = mingle@smtp7.tsimtung.com
>>>   $auth3 = mingle123
>>>   $1 =
>>>   $2 = mingle@smtp7.tsimtung.com
>>>   $3 = mingle123
>>> expanded string: yes
235 Authentication succeeded
QUIT
221 cix005.tsimtung.com closing connection


Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
Re: smtp-auth-proxy problem
« Reply #1 on: March 17, 2011, 01:08:06 PM »
sme server 7.51 or 8b cannot  smtp-auth-proxy to a exim server , any one can help?


Don't report problems here
- Please report bugs and potential bugs in the bug tracker

http://bugs.contribs.org/

Offline erroneus

  • ***
  • 62
  • +0/-0
Re: smtp-auth-proxy problem
« Reply #2 on: March 17, 2011, 03:57:42 PM »
Reporting bugs is a tedious, thankless and frustrating process.  Is it any mystery to anyone why users try to avoid it?

I have reported bugs only to have them rejected or doubted or simply ignored.  Only once do I recall a bug I filed getting addressed and I believe the issue is still open (I could be wrong) where it had to do with creating users in SME8 which resulted in some in-depth and detailed work with LDAP.  (Not that I understand it)

On top of that, people who are in the process of actually doing the magic behind the curtains are often "short" or impatient in a variety of ways with users.  This adds to the negative experiences of users... even those with a least a little technical inclination.

When the original poster made his request, he isn't yet even SURE that what he is experiencing is a bug!  He believes he may be doing something wrong and would like to be corrected in the event there is a mistake on his part.  If he gets confirmation that he is not doing anything wrong and that it "should work" then he has a comfortable basis for filing a bug report.  If this user were to do exactly as you say, he faces a strong possibility that after all the trouble and detail of filing a good bug report that it will be rejected without much review (as is often the case) and still have no idea what was wrong or what he might have done wrong to cause the problem in the first place.

It is simply unreasonable to expect people to torture themselves needlessly in this way.

And to sum100:

Before posting your question, it is always recommended to scan the forums here for similar topics and discussions to see if others have had a similar experience.  Similarly, scan the bug database for similar problems as they may have hints about resolutions and work-arounds for any problem you may be experiencing.

And take heart -- some of the most skilled developers have "weak people skills" and/or may come across as abrasive -- you shouldn't let it get to you personally.  We need to hear about your issues and ESPECIALLY if you are able to resolve them.  It is valuable data for the project.  I might suggest you try to duplicate your attempts against a different SMTP server to see if the problem is with this "exim" server or with others as well.  Determining the scope of the problem helps a great deal when trying to track down the source of a problem.

Offline byte

  • *
  • 2,183
  • +2/-0
Re: smtp-auth-proxy problem
« Reply #3 on: March 17, 2011, 04:57:32 PM »
Reporting bugs is a tedious, thankless and frustrating process.  Is it any mystery to anyone why users try to avoid it?

Erroneus, I think your post is both unhelpful and uncalled for.  Please next time do not bother posting to help someone as it wastes not only our time but the original posters time too.  I sense your post as you are bitter and don't want to help the community.  End of the matter far as I'm concerned.

Please sum100 do post your potential bug to the bug tracker as mentioned by Charlie.  Thanks.
--[byte]--

Have you filled in a Bug Report over @ http://bugs.contribs.org ? Please don't wait to be told this way you help us to help you/others - Thanks!

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
Re: smtp-auth-proxy problem
« Reply #4 on: March 17, 2011, 06:25:59 PM »
Erroneus, I think your post is both unhelpful and uncalled for.  Please next time do not bother posting to help someone as it wastes not only our time but the original posters time too.  I sense your post as you are bitter and don't want to help the community.  End of the matter far as I'm concerned.

Please sum100 do post your potential bug to the bug tracker as mentioned by Charlie.  Thanks.

sum100, please do. It's the only way that bugs can get identified and fixed.

I don't know what erroneus's problem is, but you can see for yourself via this search that bug reports such as yours will be dealt with carefully and thoroughly, via the bug tracker:

http://www.google.ca/search?q=site%3Abugs.contribs.org+smtp-auth-proxy