[pfx] Feature request

[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.

Yes, I could give all my regular expressions patterns a unique RHS or
find the regular expressions by divide-et-impera, but I'm being lazy.

-- 
Ralf Hildebrandt
  Geschäftsbereich IT | Abteilung Netz | Netzwerk-Administration
  Invalidenstraße 120/121 | D-10115 Berlin
  Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
  ralf.hildebra...@charite.de | https://www.charite.de

___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org

[pfx] Feature Request: Adjustable Header Log Size Limit in INFO/WARN/REJECT Header_Check

[Matthias Schneider via Postfix-users]

Dear Postfix Developers, 

I hope this message finds you well. I'm reaching out to address a concern 
related to the limit for the header key/value string in the "info", "warn" and 
"reject" header_check log message during the cleanup process. 

The current 200-character limit, introduced in 2002 (Postfix 1.1.11) to prevent 
log flooding, is defined in the following source code cleanup_message.c line 
265: 

vstring_sprintf(state->temp1, "%s: %s: %s %.200s from %s;"; 
state->queue_id, action, class, content, attr); 


As an active user, I have encountered challenges due to this limit while 
parsing long header values. Considering today's increased disk spaces, I 
believe that allowing users to adjust this limit according to their specific 
needs would greatly enhance the usability of Postfix in diverse environments. I 
know that a user can receive the full header key/value by using the milter 
protocol, but this can only be done synchron and not asynchron via log file 
parsing. 

I appreciate your consideration of this request and thank you for your ongoing 
dedication to Postfix development. 

Best regards 

Matthias Schneider 
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org