That does sound a bit perplexing all right.
You can send me the url directly if you'd like.
amit IKF wrote:
Hi Eric,
Well another interesting factor I come across is that when I used same
smarthost from my another qmail toaster server its working fine. Thats
making me more confused to rectify the problem.
If I provide you with the smarthost can you please check what's its
showing at your end.
Thanks and regards,
Amit
On Fri, Dec 4, 2009 at 9:54 PM, Eric Shubert <[email protected]
<mailto:[email protected]>> wrote:
I don't know off hand exactly how QMT does authentication with
smtproutes.
That being said, 3 common auth methods are plain, login, and
cram-md5. QMT should only use a method that's shown by the receiving
server's AUTH reply to the ehlo command. You can check to see what
the receiving server lists by telnetting to it, and issuing an ehlo
command. I would check this first.
If cram-md5 is listed, that's probably what QMT will try to use
first. I don't know if QMT is programmed to try other methods if the
first one fails or not. From what you said, I'd guess not. It could
be either end of the connection though that's not doing/allowing a
2nd try. The RFC states pretty clearly that subsequent methods may
be tried should the first one fail.
I don't know of a way to tell smtproutes to which auth method to
use. It should be automatic, based on what the receiving server
shows is available. If you need to use a specific auth method, I
think you'll need to modify the source code. (I needed to do this
with the python smtp module a few months ago, which resulted in an
enhancement to that module. QMT doesn't use that python module though.)
BL, if the smarthost is showing cram-md5 and can't handle it, it
should allow subsequent retries. You need to determine whether it's
QMT or the smarthost that's not doing/allowing retries, and fix
accordingly. Otherwise, you might modify the QMT source to try plain
auth first, which I'm pretty sure will work for you.
Please note, I'm speculating a bit here, but HTH anywise.
amit IKF wrote:
Hi Everyone,
Some more details which I got after discussing with my ISP on
the below topic. According to my ISP, the server is sending some
kind of encrypted password for login authentication but it
require PLAIN authentication to connect to SMARTHOST.
I'm not getting where is problem because I'm entering PLAIN
password in SMTPROUTES.
Any help.
Thanks ans regards,
Amit
On Thu, Dec 3, 2009 at 2:19 PM, amit IKF <[email protected]
<mailto:[email protected]> <mailto:[email protected]
<mailto:[email protected]>>> wrote:
Hi Everyone,
I'm using smarthost in SMTPROUTES to relay mails from one of my
qmailtoaster server but its giving me error uanle to authenticate
remote server with given username and password. But with same
smart
host username and password I'm able to send mail from my Outlook
express.
My SMTPROUTES file looks like
:smart_host_server_ip:25 smarthost_username smarthost_password
Regards,
Amit
--
-Eric 'shubes'
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com <http://www.vickersconsulting.com>)
Vickers Consulting Group offers Qmailtoaster support and
installations.
If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com <http://qmailtoaster.com> for the
latest news, updates, and packages.
To unsubscribe, e-mail:
[email protected]
<mailto:[email protected]>
For additional commands, e-mail:
[email protected]
<mailto:[email protected]>
--
-Eric 'shubes'
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
