Am 29.03.2012 12:08, schrieb Phill Edwards: > > Am 28.03.2012 15:31, schrieb Phill Edwards: > > I have had a Postfix SMTP server on my LAN for a long time and it works > really well for delivering my email via > > relayhost = smtp.example.com <http://smtp.example.com> > <http://smtp.example.com> (replaced my actuals ISP's > SMTP server here). > > > > I have now set up SMTP AUTH and it's working when sening emails from > PCs on my LAN. But when I send emails from > > outside (eg from my mobile phone) I get these errors: > > > > Mar 29 00:04:32 zrf postfix/smtpd[624]: warning: xx.xxx.180.193: > hostname > paxx-xxx-180-193.pa.nsw.optusnet.com.au > <http://paxx-xxx-180-193.pa.nsw.optusnet.com.au> > > <http://paxx-xxx-180-193.pa.nsw.optusnet.com.au> verification failed: > Name or service not known > > Mar 29 00:04:32 zrf postfix/smtpd[624]: connect from > unknown[xx.xxx.180.193] > > Mar 29 00:04:33 zrf postfix/smtpd[624]: NOQUEUE: reject: RCPT from > unknown[xx.xxx.180.193]: 554 5.7.1 > > <unknown[xx.xxx.180.193]>: Client host rejected: Access denied; > from=<m...@example.com <mailto:m...@example.com> > <mailto:m...@example.com <mailto:m...@example.com>>> > > to=<some...@example.com <mailto:some...@example.com> > <mailto:some...@example.com > <mailto:some...@example.com>>> proto=ESMTP > helo=<paxx-xxx-180-193.pa.nsw.optusnet.com.au > <http://paxx-xxx-180-193.pa.nsw.optusnet.com.au> > > <http://paxx-xxx-180-193.pa.nsw.optusnet.com.au>> > > Mar 29 00:04:33 zrf postfix/smtpd[624]: disconnect from > unknown[xx.xxx.180.193] > > where do you see here any authentication try? > connect -> reject > > > I ran some tests on the LAN which showed up seccuessful authentivation > attempts. This is a log of what happens when > a mobile phone tries to connect from outside the LAN. I'm assuming there are > no authentication tries because the > client has been rejected due to network restrictions before even attempting > any credentials are processed. > > let me guess - this is a iPhone? > > No, it's a Samsung Galaxy S II with K-9 Mail as the email client
if "permit_sasl_authenticated" is before restricitions the client can always authenticate, this is how the tings are working but the client has to be configured for authentication sadly it is not default in most clients while if the MUA developers would be a little smarter they would activate it and use the same credentials as for incoming server which fits 99% of all setups P.S.: please do not reply offlist!
signature.asc
Description: OpenPGP digital signature
