Am Di, den 14.06.2005 schrieb Ankush Grover um 7:08: > > smtp_sasl_security_options = noanonymous, noplaintext > > I did this but after that i started getting errors like this > > mail postfix/smtp[1843]: 623A4BEE88: to=<ankush174@xxxxxxxxx>, > relay=mail.nextgenesolutions.com[216.251.43.97], delay=2, > status=deferred (Authentication failed: cannot SASL authenticate to > server mail.nextgenesolutions.com[216.251.43.97]: no mechanism > available) O, they seem to only offer LOGIN and/or PLAIN and no STARTTLS. That's bad from point of security. You can check what the ISP's MTA offers by telnetting it at port 25. > > > > > The entries for passwd file are as > > > > > > > > > > ISP mailserver username:password. > > > > > Did you set "relayhost" in main.cf? > > > > > I did not set relay host in main.cf . > > > > You did now? If not your ISP's smart host will not be used as the > > standard relay. As an alternate you could use the transport map, but in > > your case with dynamic IP situation you always want your ISP's MTA for > > relaying. > > > > I did put my ISP smpt server as relay host in main.cf .How can I be > sure that my mail server is correctly authenticating with the ISP > server . From the logs. In the above shown log part you see that authentication fails. If it succeeds the mail is going out and will reach it's destination. > Ankush Grover Alexander -- Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773 legal statement: http://www.uni-x.org/legal.html Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.11-1.27_FC2smp Serendipity 16:12:55 up 21 days, 14:50, load average: 1.19, 1.17, 0.94
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
