Hi,
Sorry for breaking the thread. Regarding our discussions with the
Subject, Mail delivery  problem, I missed a mail from Suresh due to 
a wrong dns entry and found about it just yesterday.
Well, I will be talking in qmail language. Assume I want a mail to be
delivered to [EMAIL PROTECTED] ( :) ) which does the helo filtering
and tries to map helo to a ip and checks it. So, I cannot deliver mail
to him from my local MTA on dialup. So, I use qmail as a smarthost and
try to relay mail to him by using control/smtproutes. But my ISP uses
SMTP-AUTH. So I patch qmail and now the control/smtproutes file has,

sureshdoesbadhelo.com:mysmtpauthisp.com <encrypted username> <encrypted passwd>

So when ever I send a mail from [EMAIL PROTECTED] to Suresh, qmail
will re-route it thru' mysmtpauthisp.com:25 which will take the username
and password, check it and if found correct will accept the mail for
relaying. Ok, till here?
Now I want to send a mail to suresh from [EMAIL PROTECTED]
qmail will still try to re-route every message to sureshdoesbadhelo.com
using same isp (i.e. mysmtpauthisp.com) and same username and password.
Am I right till here?
Now, when qmail tries to re-route this second message, mysmtpauthisp
will check the username and password and then maybe give up with an
error like "Relaying Denied" and bounce the message. So, I cannot mail
Suresh at all from my design address.

Can you please tell if the above thing is right or not and what to do
in such cases?

With warm regards,
-Payal


-- 
"Visit GNU/Linux Success Stories"
http://payal.staticky.com
Guest-Book Section Updated.


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
linux-india-help mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/linux-india-help

Reply via email to