Re: SV: Telnet auth

2018-10-17 Thread sercoinful
Hi, When I replace "reject_unverified_sender" to "reject" it works. Thanks. Regards -- Sent from: http://postfix.1071664.n5.nabble.com/Postfix-Users-f2.html

Re: SV: Telnet auth

2018-10-17 Thread Wietse Venema
sercoinful: > Hi, > > I'm trying to use configuration like below. But authentication from local to > local via telnet still not working. Anyone could send mail to local from > local via telnet. Which part is not correct? I see no 'reject' action in the rule with 'permit_sasl_authenticated'

Re: SV: Telnet auth

2018-10-17 Thread sercoinful
Hi, I'm trying to use configuration like below. But authentication from local to local via telnet still not working. Anyone could send mail to local from local via telnet. Which part is not correct? main.cf smtpd_recipient_restrictions = permit_sasl_authenticated, reject_unauth_destination smtpd_

Re: SV: SV: Telnet auth

2016-05-18 Thread /dev/rob0
On Wed, May 18, 2016 at 06:47:45PM -0400, Wietse Venema wrote: > Noel Jones: > [ Charset windows-1252 converted... ] > > On 5/18/2016 3:46 PM, Sebastian Nielsen wrote: > > > It is actually possible to use multiple results when using the > > > built-in restriction commands (permit_sasl_authenticati

SV: Telnet auth

2016-05-18 Thread Sebastian Nielsen
Yeah, it do break forwarding where stupid mailservers (or more correctly, mailservers configured by stupid admins) just forward the mail verbatim, and even forge the MAIL FROM to the destination server. That is the thing that causes SPF to fail when for example: My server --> Receivers Company ser

Re: SV: SV: Telnet auth

2016-05-18 Thread Wietse Venema
Noel Jones: [ Charset windows-1252 converted... ] > On 5/18/2016 3:46 PM, Sebastian Nielsen wrote: > > It is actually possible to use multiple results when using the built-in > > restriction commands (permit_sasl_authentication, permit_mynetworks, reject, > > etc) > > (Eg, words that can be used in

SV: SV: SV: Telnet auth

2016-05-18 Thread Sebastian Nielsen
[mailto:owner-postfix-us...@postfix.org] För Noel Jones Skickat: den 18 maj 2016 23:28 Till: postfix-users@postfix.org Ämne: Re: SV: SV: Telnet auth On 5/18/2016 3:46 PM, Sebastian Nielsen wrote: > It is actually possible to use multiple results when using the > built-in restriction co

Re: SV: SV: Telnet auth

2016-05-18 Thread Noel Jones
On 5/18/2016 3:46 PM, Sebastian Nielsen wrote: > It is actually possible to use multiple results when using the built-in > restriction commands (permit_sasl_authentication, permit_mynetworks, reject, > etc) > (Eg, words that can be used in the rules chain instead of > "check_sender_access") > > Th

SV: SV: Telnet auth

2016-05-18 Thread Sebastian Nielsen
ostfix.org [mailto:owner-postfix-us...@postfix.org] För /dev/rob0 Skickat: den 18 maj 2016 22:36 Till: postfix-users@postfix.org Ämne: Re: SV: Telnet auth smime.p7s Description: S/MIME Cryptographic Signature

Re: SV: Telnet auth

2016-05-18 Thread /dev/rob0
Catalin Badirca wrote: > I will try to be more specific. Create an test account that can > send emails from postfix. Send THROUGH Postfix is more accurate wording than send FROM. Also, creation of the account does not matter. By default there is no checking of sender addresses. > Telnet on

Re: SV: Telnet auth

2016-05-18 Thread Catalin Badirca
This is what I was looking for. Thank you very very much Sebastien. I will try it right now and will post the result. Sent from my iPhone > On 18 May 2016, at 22:07, Sebastian Nielsen wrote: > > Yes. > Remove permit_sasl_authenticated and permit_mynetworks. > Then add the following rule inste

SV: Telnet auth

2016-05-18 Thread Sebastian Nielsen
Yes. Remove permit_sasl_authenticated and permit_mynetworks. Then add the following rule instead, immediately BEFORE reject_unauth_destination: check_sender_access hash:/etc/postfix/relay_auth Inside the file relay_auth, which must be postmap:ed, you have the following: yourdomain.com: permit_sas