On Fri, Apr 14, 2023 at 03:31:17PM -0300, SysAdmin EM via Postfix-users wrote:
> Sorry for such a basic question but I couldn’t find a solution on my
> part. I’m trying to block a Subject using header_checks but it’s not
> working.
>
> This is my rule:
>
> /^Subject:.*Invalid HTTP_HOST
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
The rule not work
postmap -q "Subject: [KIS] ERROR (EXTERNAL IP): Invalid HTTP_HOST header: '
10.54.130.188:8020'. You may need to add u'10.54.130.188' to
ALLOWED_HOSTS." regexp:/etc/postfix/header_checks
WARN
/^Subject:.*You may need to add.*/ DISCARD BLOCK_TEMPORAL
any ideas??
On Fri, Apr
On Fri, Apr 14, 2023 at 05:51:21PM -0300, SysAdmin EM via Postfix-users wrote:
> postmap -q "Subject: [KIS] ERROR (EXTERNAL IP): Invalid HTTP_HOST header:
> '10.54.130.188:8020'. You may need to add u'10.54.130.188' to ALLOWED_HOSTS."
> regexp:/etc/postfix/header_checks
Works here (bash
Sorry for such a basic question but I couldn’t find a solution on my part.
I’m trying to block a Subject using header_checks but it’s not working.
This is my rule:
/^Subject:.*Invalid HTTP_HOST header.*/ DISCARD SUBJECTALERT
I used postmap to test the rule but not match.
postmap -q "[KIS]
On Fri, Apr 14, 2023 at 01:06:16PM -0400, Wietse Venema via Postfix-users wrote:
> Wietse Venema via Postfix-users:
> > As for the temp error becoming persistent, the Postfix pgsql: client
> > code returns an error when it gets an error from all of the hosts
> > configured in the Postfix pgsql:
Viktor Dukhovni via Postfix-users:
> On Fri, Apr 14, 2023 at 01:06:16PM -0400, Wietse Venema via Postfix-users
> wrote:
>
> > Wietse Venema via Postfix-users:
> > > As for the temp error becoming persistent, the Postfix pgsql: client
> > > code returns an error when it gets an error from all of
V?ctor Rubiella Monfort via Postfix-users:
> 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?.
With
Wietse Venema via Postfix-users:
> As for the temp error becoming persistent, the Postfix pgsql: client
> code returns an error when it gets an error from all of the hosts
> configured in the Postfix pgsql: client configuration file, or when
> all hosts have been flagged as 'down'. If a host
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
10 matches
Mail list logo
