[pfx] Re: sendmail bounce messages

As always, very grateful for your clarifications. El 8/6/23 a las 18:12, Wietse Venema via Postfix-users escribió: Wietse Venema via Postfix-users: Victor Rubiella Monfort via Postfix-users: Hi, I want to prevent that sendmail milter rejections generates bounces messages. Reading sendmail doc

[pfx] sendmail bounce messages

Hi, I want to prevent that sendmail milter rejections generates bounces messages. Reading sendmail documentation I see "-N" option: echo "HELLO" | sendmail -N 'never' t...@test.es; echo $? 0 Jun  8 13:51:30 server.test postfix/cleanup[597560]: 077616620F: milter-reject: END-OF-MESSAGE from

[pfx] Re: logging strangeness

Hi, But what about show user login? Currently we have issues when fail2ban blocks IPS for a high number or failed logins, but is a customer with several mail accounts and he don't know which bad-configured account is causing the ban. Would be so healpfull shows the sasl_username that produce

[pfx] temporary lookup error with utf8mb4 characters

Hi, I have more info and I try to explain it better: First of all I have smtputf8_enable = no (disabled). I have several databases related with several mysql_virtual maps: - Some with utf8 + utf8_general_ci collation - Another ones with latin1 + latin1_spanish_ci. I'm using mysql-postfix (mys

[pfx] Re: temporary lookup error with utf8mb4 characters

Hi, I have more info and I try to explain it better: First of all I have smtp_utf8 = no (disabled). I have several databases related with several mysql_virtual maps: - Some with utf8 + utf8_general_ci collation - Another ones with latin1 + latin1_spanish_ci. I'm using mysql-postfix (mysql_tab

[pfx] Re: temporary lookup error with utf8mb4 characters

Hi again, I realized than same error is raised when database is in utf8 if email contains utf8mb4 characters. Which is the convenient database collation for postfix? We can force postfix to accept only utf8 characters?. El 13/4/23 a las 18:36, Víctor Rubiella Monfort via Postfix-users

[pfx] temporary lookup persistent after query collate error corrupt connection.

When mysql_table lookup is executing nonascii characters and database is in latin1, not only fails query, all sesion/connection is corrupted and produces a lot of "temporary lookup table" errors until sesion is recreated (about 1 minute later). Today some external ip was trying to deliver an e

[pfx] warn_if_reject for milters equivalent?

Hi!, There are any way to implement equivalent to "warn_id_reject" for milters? I'm deploying centralized spam milter on inet:X: and I would like to deploy as "dryrun" to evaluate rejections before full enable it, and activate it gradually on different servers. Thanks! __