[pfx] Re: Trouble with qmqp

2024-03-20 Thread Viktor Dukhovni via Postfix-users
On Wed, Mar 20, 2024 at 09:40:56PM +, Brad Koehn via Postfix-users wrote: > I’m trying to deliver email with Postfix 3.7.10 using `qmqpd`. > Unfortunately when I do this, the email is often unreadable by a > variety of email clients.  Can you be more specific about what you mean by "deliver

[pfx] Trouble with qmqp

2024-03-20 Thread Brad Koehn via Postfix-users
I’m trying to deliver email with Postfix 3.7.10 using `qmqpd`. Unfortunately when I do this, the email is often unreadable by a variety of email clients.  Curiously, if I deliver the same email directly to Dovecot via LMTP, clients have no issue with the message. I expected the opposite to be

[pfx] Don't BCC a particular domain

2024-03-20 Thread Richard Raether via Postfix-users
We have an auditor account where all incoming and outgoing mail is BCC'd to, to retain for compliance reasons. However, since mailman retains its own archives, and we have a mailman on a separate server with a separate domain, is there a way to tell postfix DO bcc everything EXCEPT DON'T bcc

[pfx] Re: collect emails in maildir folder without delivering them to user

2024-03-20 Thread Bill Cole via Postfix-users
On 2024-03-19 at 02:10:53 UTC-0400 (Tue, 19 Mar 2024 07:10:53 +0100) Fourhundred Thecat via Postfix-users <400the...@ik.me> is rumored to have said: Hello, I am running postfix server for my personal use. On the server, I have one unix user, and multiple aliases defined in /etc/aliases, so

[pfx] Re: [ext] Re: Feature request

2024-03-20 Thread Ralf Hildebrandt via Postfix-users
* Allen Coates via Postfix-users : > > Better yet, don't be lazy, include a fingerprint string in your RHS > > reject rule values. > Postscreen doesn't have the option of unique RHS fingerprints;  nonetheless, > it would useful to see which (of several) > ACLs was rejecting an incoming

[pfx] Re: Feature request

2024-03-20 Thread Allen Coates via Postfix-users
On 20/03/2024 13:17, Viktor Dukhovni via Postfix-users wrote: > On Wed, Mar 20, 2024 at 01:42:16PM +0100, Ralf Hildebrandt via Postfix-users > wrote: >> Hi! >> >> I wonder if this is possible: >> >> If a PCRE/regexp style map is triggering, it can be quite hard to >> find out WHICH pattern

[pfx] Postfix thinks smtp.gmail.com uses self-signed certificate

2024-03-20 Thread Cowbay via Postfix-users
Hi, I'm using debian 10, an old debian distribution. The Postfix version is 3.4.23. I found below in the log, it says "certificate verification failed for smtp.gmail.com[64.233.189.109]:465: self-signed certificate" 8<8<8< Mar 20 21:27:38 SERVER

[pfx] Re: Feature request

2024-03-20 Thread Viktor Dukhovni via Postfix-users
On Wed, Mar 20, 2024 at 09:17:58AM -0400, Viktor Dukhovni via Postfix-users wrote: > With bash <(command) inline file syntax, make the RHS unique on the fly: > > $ keystr=... > $ remap=/etc/postfix/... > $ postmap -q "$keystr" pcre:<(perl -pe 's/$/ LINE $./ unless >

[pfx] Re: Feature request

2024-03-20 Thread Viktor Dukhovni via Postfix-users
On Wed, Mar 20, 2024 at 01:42:16PM +0100, Ralf Hildebrandt via Postfix-users wrote: > Hi! > > I wonder if this is possible: > > If a PCRE/regexp style map is triggering, it can be quite hard to > find out WHICH pattern actually caused the action. > > So maybe postmap (when invoked with "-b",

[pfx] Feature request

2024-03-20 Thread Ralf Hildebrandt via Postfix-users
Hi! I wonder if this is possible: If a PCRE/regexp style map is triggering, it can be quite hard to find out WHICH pattern actually caused the action. So maybe postmap (when invoked with "-b", "-h" or "-q key") could emit which regular expression (or which line it was in) actually matched.