Re: How to reject generic FCrDNS clients

2021-11-12 Thread Demi Marie Obenour
On 11/11/21 10:28 AM, Bill Cole wrote: > On 2021-11-11 at 06:06:45 UTC-0500 (Thu, 11 Nov 2021 12:06:45 +0100) > Togan Muftuoglu > is rumored to have said: > >> Hi, >> >> How can I reject connections from generic Forward Confirmed Reverse >> DNS >> (FCrDNS) like “123-45-67-8.your.isp.com”. >> >>

Re: How to reject generic FCrDNS clients

2021-11-12 Thread Togan Muftuoglu
> "DMO" == Demi Marie Obenour writes: DMO> On 11/11/21 10:28 AM, Bill Cole wrote: >> On 2021-11-11 at 06:06:45 UTC-0500 (Thu, 11 Nov 2021 12:06:45 +0100) Togan >> Muftuoglu is rumored to have said: >> >>> Hi, >>> >>> How can I reject connections from generic Forward Confirmed Reverse DNS >>>

Re: domain email handled by postfix

2021-11-12 Thread Dominic Raferd
On 12/11/2021 04:53, Walt Pang wrote: How to set up postfix to forward all my domain's email to gmail, and enable authentication for SMTP outgoing messages? The good news is that we have had this working for our own domains for years. The bad news is that I don't have the time to explain our so

Re: How to reject generic FCrDNS clients

2021-11-12 Thread Bill Cole
On 2021-11-12 at 06:57:14 UTC-0500 (Fri, 12 Nov 2021 12:57:14 +0100) Togan Muftuoglu is rumored to have said: "DMO" == Demi Marie Obenour writes: DMO> On 11/11/21 10:28 AM, Bill Cole wrote: On 2021-11-11 at 06:06:45 UTC-0500 (Thu, 11 Nov 2021 12:06:45 +0100) Togan Muftuoglu is rumored to

normally accepted *_maps-settings refused if inside a pipemap chain

2021-11-12 Thread Mirko Vogt
Hello, I'm having a working virtual user/mailbox setup, where I use mysql as database backend and query it via "[..]_maps = proxy:mysql:[..]"-settings. I now played around with the lookup table type "pipemap", wrapping the previous setting(s) within a pipemap chain, e.g. transport_maps =

Re: How to reject generic FCrDNS clients

2021-11-12 Thread Bill Cole
On 2021-11-11 at 14:53:01 UTC-0500 (Thu, 11 Nov 2021 20:53:01 +0100) Togan Muftuoglu is rumored to have said: "Matus" == Matus UHLAR <- fantomas > writes: Matus> you can check hostnames by using pcre map in Matus> check_reverse_client_hostname_access. e.g. refuse regex Matus> /(\d+)[.-](\d+

Re: normally accepted *_maps-settings refused if inside a pipemap chain

2021-11-12 Thread Wietse Venema
Mirko Vogt: >transport_maps = > pipemap:{proxy:mysql:/etc/postfix/sql/mysql_transport_maps.cf, > inline:{FOO=BAR}} ... > Is postfix complaining about the "proxy:mysql:" transport setting within > a pipemap-chain expected behaviour or potentially a bug? If the former, > may I ask about the r

Re: domain email handled by postfix

2021-11-12 Thread Miles Fidelman
Walt Pang wrote: How to set up postfix to forward all my domain's email to gmail, and enable authentication for SMTP outgoing messages? Forwarding mail - that would be a job for procmail - pretty easy. SMTP authentication - last time I did that, I just went to the (rather excellent) postfix

Re: domain email handled by postfix

2021-11-12 Thread Ralph Seichter
* Walt Pang: > How to set up postfix [...] Studying http://www.postfix.org/documentation.html first, in depth, will help you. It is best always do one's homework before asking others. -Ralph

Re: domain email handled by postfix

2021-11-12 Thread Wietse Venema
Ralph Seichter: > * Walt Pang: > > > How to set up postfix [...] > > Studying http://www.postfix.org/documentation.html first, in depth, will > help you. It is best always do one's homework before asking others. Read enough so that you can ask meaningful questions and understand the responses. N

Re: domain email handled by postfix

2021-11-12 Thread Bill Cole
On 2021-11-12 at 12:07:43 UTC-0500 (Fri, 12 Nov 2021 12:07:43 -0500) Miles Fidelman is rumored to have said: Forwarding mail - that would be a job for procmail - pretty easy. Please, no. Procmail has been unmaintained for 2 decades and its security is unknowable beyond a certainty that ther

Re: Various questions about Postfix

2021-11-12 Thread Tyler Montney
"You seem to be explicitly setting many parameters to their defaults." I removed a bunch, but might have missed some. That "command_directory" parameter I definitely didn't set. I think that's a result of building from source. "You have the address mappings happening before, which means that the

Re: Postfix unable to locate opendmarc.sock file

2021-11-12 Thread bobby
So my opendkim file is located here: /var/spool/postfix/opendkim/opendkim.sock Do I need to move that, or is that location OK? As for the opendmarc.sock, I was not able to locate that file on my system. On Thu, Nov 11, 2021 at 9:12 PM raf wrote: > On Thu, Nov 11, 2021 at 06:39:27PM -0500, bobby

Re: Various questions about Postfix

2021-11-12 Thread Viktor Dukhovni
On Fri, Nov 12, 2021 at 03:47:22PM -0600, Tyler Montney wrote: > In my effort to be a little less flexible (to get more encryption), it > seems I'll do the opposite. I'll change that. Speaking of which... > > smtp_tls_mandatory_protocols Applies when sending mail to destinations for which TLS is

Re: Postfix unable to locate opendmarc.sock file

2021-11-12 Thread postfix
> On 11-12-2021 5:11 pm, bobby wrote: > As for the opendmarc.sock, I was not able to locate that file on my system. Did you install opendmarc? Look in the config /etc/opendmarc.conf to see what the socket is set to. If its not set then its using default. Mine is set as: Socket local:/var/run/ope

Re: Postfix unable to locate opendmarc.sock file

2021-11-12 Thread postfix
> On 11-12-2021 5:11 pm, bobby wrote: > So my opendkim file is located here: > /var/spool/postfix/opendkim/opendkim.sock > Do I need to move that, or is that location OK? While it will technically work, i believe it is bad practice and sockets should be under the /run/ directory. Im not 100% on

Re: Postfix unable to locate opendmarc.sock file

2021-11-12 Thread Viktor Dukhovni
> On 12 Nov 2021, at 8:00 pm, post...@ptld.com wrote: > > While it will technically work, i believe it is bad practice and sockets > should be under the /run/ directory. Im not 100% on this but i think running > it under /var/spool/ uses the hard drive while under /run/ its a ram-drive > only e