Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I'm having issues sending mail from postfix. I believe my conf. is very standard, at the end it was put together from various guides. I'm trying to send mail from remote client (iOS Mail, and Mac OS X Mail.app, Thunderbird on Linux). From iOS Mail it works ok, it does not for Mail.app and Thunderbird. I'm using SASL authentication (dovecot), and TLS, configuration below along with log message.

Error:

Jan 05 12:27:41 svali postfix/smtpd[26448]: NOQUEUE: reject: RCPT from aaa.chello.sk[89.173.206.108]: 553 5.7.1 <xxx>: Sender address rejected: not owned by user xxx; from=<xxx> to=<yyy> proto=ESMTP helo=<[10.0.2.4]>
Jan 05 12:27:41 svali postfix/smtpd[26448]: disconnect from aaa.chello.sk[89.173.206.108]
Jan 05 12:31:01 svali postfix/anvil[26450]: statistics: max connection rate 2/60s for (submission:89.173.206.108) at Jan  5 12:24:33

When it works (iOS Mail app)

Jan 05 12:45:23 svali postfix/smtpd[26807]: connect from aaa.chello.sk[89.173.206.108]
Jan 05 12:45:24 svali postfix/smtpd[26807]: 1328056578: client=aaa.chello.sk[89.173.206.108], sasl_method=PLAIN, sasl_username=xxx
Jan 05 12:45:24 svali postfix/cleanup[26821]: 1328056578: message-id=<42EC179A-DE92-4526-9F0E-DA3B5EF76B80@aaa>
Jan 05 12:45:24 svali postfix/qmgr[2599]: 1328056578: from=<xxx>, size=650, nrcpt=1 (queue active)
Jan 05 12:45:24 svali postfix/smtp[26824]: 1328056578: to=<yyy>, relay=gmail-smtp-in.l.google.com[2a00:1450:400c:c05::1a]:25, delay=0.71, delays=0.17/0.01/0.04/0.49, dsn=2.0.0, status=sent (250 2.0.0 OK 1388925924 f3si3608555wik.58 - gsmtp)
Jan 05 12:45:24 svali postfix/qmgr[2599]: 1328056578: removed
Jan 05 12:45:26 svali postfix/smtpd[26827]: connect from mail-qe0-f42.google.com[209.85.128.42]
Jan 05 12:45:27 svali postfix/smtpd[26827]: 28DA856578: client=mail-qe0-f42.google.com[209.85.128.42]
Jan 05 12:45:27 svali postfix/cleanup[26821]: 28DA856578: message-id=<42EC179A-DE92-4526-9F0E-DA3B5EF76B80@aaa>
Jan 05 12:45:27 svali postfix/qmgr[2599]: 28DA856578: from=<yyy+caf_=dusan=xxx>, size=2535, nrcpt=1 (queue active)
Jan 05 12:45:27 svali postfix/smtpd[26827]: disconnect from mail-qe0-f42.google.com[209.85.128.42]
Jan 05 12:45:28 svali dovecot[26832]: lda(xxx): sieve: msgid=<42EC179A-DE92-4526-9F0E-DA3B5EF76B80@aaa>: stored mail into mailbox 'INBOX'
Jan 05 12:45:28 svali postfix/pipe[26831]: 28DA856578: to=<xxx>, relay=spamass, delay=1.1, delays=0.69/0.01/0/0.36, dsn=2.0.0, status=sent (delivered via spamass service)

Jan 05 12:45:28 svali postfix/qmgr[2599]: 28DA856578: removed ```

main.cf: http://ix.io/9GS

master.cf: http://ix.io/9GR

share|improve this question

1 Answer 1

The issue is with your mynetworks configuration in main.cf: http://www.postfix.org/postconf.5.html#mynetworks

Your mynetworks is set to 127.0.0.1; so the only box allowed to send mail is the postfix box. This means you're unable to connect to relay email based on the current settings.

share|improve this answer
    
I see. So the fact that I have permit_sasl_authenticated doesn't make any difference? What should I set mynetworks and smtpd_recipient_restrictions to, in order to deny relaying for non-authenticated SMTP clients? –  skrat Jan 5 at 17:17
    
Why does it work when sending from iOS Mail.app? –  skrat Jan 5 at 17:22
    
@skrat the mynetworks works in relaying of mail; I don't know how the app works that you're referring to. See serverfault.com/questions/337687/… for permit_sasl_authenticated with mynetworks. You can leave mynetworks to 127.0.0.1 but the server will not relay mail; e.g. you cannot directly connect to it to send mail. If you have a machine that you need to send mail you need to allow it in mynetworks. To verify that mynetworks is the issue set it to 0.0.0.0 to make it an open relay and then try sending –  josten Jan 5 at 21:59
    
Making it an open relay would make it an immediate target for spammers and my server would be black listed in an instant, thanks, I'd rather not. I'd rather understand why permit_sasl_authenticated doesn't work as expected. –  skrat Jan 7 at 11:25
    
@skrat that is why you have a firewall........................................ –  josten Jan 7 at 13:22

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.