Re: 454 4.7.1 Relay access denied

2018-04-30 Thread Viktor Dukhovni
> On Apr 30, 2018, at 6:57 AM, Wietse Venema wrote: > >>> http://www.postfix.org/SMTPD_ACCESS_README.html >>> >>> But it lists smtpd_relay_restrictions in the wrong place (before >>> smtpd_recipient_restrictions). It's fixed now. >> >> ?Thanks, but the change in the web page isn't apparent to

Re: 454 4.7.1 Relay access denied

2018-04-30 Thread Wietse Venema
Dominic Raferd: > On 29 April 2018 at 21:46, Wietse Venema wrote: > > > Dominic Raferd: > > > Do you publish the order in which smtpd restriction lists are > > > processed? I thought I knew it but evidently not. > > > > ?? > > http://www.postfix.org/SMTPD_ACCESS_README.html > > > > But it lists s

Re: 454 4.7.1 Relay access denied

2018-04-29 Thread Dominic Raferd
On 29 April 2018 at 21:46, Wietse Venema wrote: > Dominic Raferd: > > Do you publish the order in which smtpd restriction lists are > > processed? I thought I knew it but evidently not. > > ​​ > http://www.postfix.org/SMTPD_ACCESS_README.html > > But it lists smtpd_relay_restrictions in the wrong

Re: 454 4.7.1 Relay access denied

2018-04-29 Thread Wietse Venema
Dominic Raferd: > Do you publish the order in which smtpd restriction lists are > processed? I thought I knew it but evidently not. http://www.postfix.org/SMTPD_ACCESS_README.html But it lists smtpd_relay_restrictions in the wrong place (before smtpd_recipient_restrictions). It's fixed now.

Re: 454 4.7.1 Relay access denied

2018-04-29 Thread Viktor Dukhovni
> On Apr 29, 2018, at 2:03 PM, Dominic Raferd wrote: > > Thanks for the correction. Not sure how they were slipping past - > maybe it was one of my permit_dnswl_client lines in > smtpd_recipient_restrictions (which came before > reject_unauth_destination), but am pleased that I am now stopping

Re: 454 4.7.1 Relay access denied

2018-04-29 Thread Dominic Raferd
On 29 April 2018 at 17:51, Wietse Venema wrote: > Dominic Raferd: >> On 29 April 2018 at 17:16, Wietse Venema wrote: >> > Dominic Raferd: >> >> Checking my logs I see that some senders are trying to fake our domain >> >> and use our server to send mails to third parties masquerading as one >> >>

Re: 454 4.7.1 Relay access denied

2018-04-29 Thread Wietse Venema
Dominic Raferd: > On 29 April 2018 at 17:16, Wietse Venema wrote: > > Dominic Raferd: > >> Checking my logs I see that some senders are trying to fake our domain > >> and use our server to send mails to third parties masquerading as one > >> of our own domains (without authenticating first). > >>

Re: 454 4.7.1 Relay access denied

2018-04-29 Thread Dominic Raferd
On 29 April 2018 at 17:16, Wietse Venema wrote: > Dominic Raferd: >> Checking my logs I see that some senders are trying to fake our domain >> and use our server to send mails to third parties masquerading as one >> of our own domains (without authenticating first). >> >> They are stopped by smtpd

Re: 454 4.7.1 Relay access denied

2018-04-29 Thread Wietse Venema
Dominic Raferd: > Checking my logs I see that some senders are trying to fake our domain > and use our server to send mails to third parties masquerading as one > of our own domains (without authenticating first). > > They are stopped by smtpd with response 'Relay access denied', but > instead of

454 4.7.1 Relay access denied

2018-04-29 Thread Dominic Raferd
Checking my logs I see that some senders are trying to fake our domain and use our server to send mails to third parties masquerading as one of our own domains (without authenticating first). They are stopped by smtpd with response 'Relay access denied', but instead of 5xx permanent rejection smtp

Re: NOQUEUE: reject: RCPT from ... 454 4.7.1 Relay access denied

2013-04-09 Thread Noel Jones
On 4/9/2013 3:46 AM, Indiana Jones wrote: > Hi, > Thank you for your input! > > I need Postfix to receive all messages sent to all users of mhm.lv > and deliver them locally to the > mail users of the same domain! If these users are local system accounts, add the domain to mydestination. http://

Re: NOQUEUE: reject: RCPT from ... 454 4.7.1 Relay access denied

2013-04-09 Thread Indiana Jones
> > > /var/log/maillog: > --- > Apr 9 02:44:35 mail postfix/smtpd[38430]: connect from > shark2.inbox.lv[89.111.3.82] > > > Apr 9 02:44:35 mail postfix/smtpd[38430]: NOQUEUE: reject: RCPT from > shark2.inbox

Re: NOQUEUE: reject: RCPT from ... 454 4.7.1 Relay access denied

2013-04-08 Thread Noel Jones
tfix/smtpd[38430]: NOQUEUE: reject: RCPT from > shark2.inbox.lv[89.111.3.82]: 454 4.7.1 : Relay access > denied; from= to= proto=ESMTP > helo= A little context would help... If this is supposed to be accepted and delivered locally, the problem is that postfix doesn't

Re: NOQUEUE: reject: RCPT from ... 454 4.7.1 Relay access denied

2013-04-08 Thread Rod K
shark2.inbox.lv[89.111.3.82]: 454 4.7.1 : Relay access denied; from= to= proto=ESMTP helo= Apr 9 02:44:35 mail postfix/smtpd[38430]: disconnect from shark2.inbox.lv[89.111.3.82] Apr 9 02:44:49 mail dovecot: pop3-login: Login: user=, method=PLAIN, rip=80.81.39.15, lip=80.81.39.2 Apr 9 02:44:49 mail

NOQUEUE: reject: RCPT from ... 454 4.7.1 Relay access denied

2013-04-08 Thread Indiana Jones
: --- Apr 9 02:44:35 mail postfix/smtpd[38430]: connect from shark2.inbox.lv[89.111.3.82]     Apr 9 02:44:35 mail postfix/smtpd[38430]: NOQUEUE: reject: RCPT from shark2.inbox.lv[89.111.3.82]: 454 4.7.1 : Relay access denied; from= to= proto=ESMTP