as
smtp. This works as it seems that loop check is ignored if relayhost
is not to port 25, but I don't like this solution very much. Any other
way to turn this check off or so?
Regards,
Carlos Velasco
*** AVISO LEGAL ***
Este mensaje va dirigido, de manera exclusiva, a su
Some additional information.
Postfix version is 2.7.1
smtp -v shows:
Jun 17 18:36:00 mail:info postfix-dummy/smtp: postfix-dummy/smtp[4212]:
connecting to 1.1.2.1 port 25
Jun 17 18:36:00 mail:info postfix-dummy/smtp: postfix-dummy/smtp[4212]:
smtp_addr_one: host 1.1.2.1
Jun 17 18:36:00
Loop detection is on by default when the destination port is 25.
Loop detection matches on either banner hostnames or interfaces
or IP addresses found in inet_interfaces or proxy_addresses.
It could be good to have a switch to turn it off for cases like this :)
Alternatively, you can
On Thu, Jun 17, 2010 at 06:55:33PM +0200, Carlos Velasco wrote:
Loop detection is on by default when the destination port is 25.
Loop detection matches on either banner hostnames or interfaces
or IP addresses found in inet_interfaces or proxy_addresses.
It could be good to have a switch
answers and comments. :)
Regards,
Carlos Velasco
*** AVISO LEGAL ***
Este mensaje va dirigido, de manera exclusiva, a su destinatario y
contiene información confidencial y sujeta al secreto profesional,
cuya divulgación no está permitida por la ley. En caso de haber
recibido
but I can't find anything similar for LDAP queries.
Regards,
Carlos Velasco
g.1.en.html
https://github.com/PhilipHazel/pcre2/blob/master/pcre2-config.in
Regards,
Carlos Velasco
ve libs in non-standard locations, "make makefiles" doesn't work for me.
Regards,
Carlos Velasco
Wietse Venema via Postfix-users escribió el 10/12/2023 a las 19:44:
Carlos Velasco via Postfix-users:
*** And there is the milter, is custom made ***
You need to reduce complexity.
- If you remove the Milter, is the header still duplicated?
No.
Duplication only happens when, in milter, I
Jaroslaw Rafa via Postfix-users escribió el 10/12/2023 a las 22:32:
Dnia 10.12.2023 o godz. 22:16:27 Carlos Velasco via Postfix-users pisze:
That is because every Milter in the real world gets the client info
>from the smfi_connect() callback function and from Milter macros,
inst
Wietse Venema via Postfix-users escribió el 10/12/2023 a las 22:54:
Carlos Velasco via Postfix-users:
Wietse Venema via Postfix-users escribi? el 10/12/2023 a las 21:53:
Carlos Velasco via Postfix-users:
Wietse Venema via Postfix-users escribi? el 10/12/2023 a las 19:44:
Carlos Velasco via
Wietse Venema via Postfix-users escribió el 10/12/2023 a las 21:53:
Carlos Velasco via Postfix-users:
Wietse Venema via Postfix-users escribi? el 10/12/2023 a las 19:44:
Carlos Velasco via Postfix-users:
*** And there is the milter, is custom made ***
You need to reduce complexity
Wietse Venema via Postfix-users escribió el 13/12/2023 a las 1:59:
Carlos Velasco via Postfix-users:
Thus, the Postfix code that handles header update/delete requests
was still naively skipping the first header, making calls to delete
the prepended Received-SPF: header ineffective, and mis
, like authenticated
connection, protocol, ciphers, ...
Regards,
Carlos Velasco
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
Bill Cole via Postfix-users escribió el 11/12/2023 a las 15:31:
On 2023-12-10 at 16:37:16 UTC-0500 (Sun, 10 Dec 2023 22:37:16 +0100)
Carlos Velasco via Postfix-users
is rumored to have said:
[...]
And doing the same work in 2 different places can be called software
efficiency
Wietse Venema via Postfix-users escribió el 11/12/2023 a las 22:30:
Wietse Venema:
Patch below.
Carlos Velasco:
Tested patch against 3.8.3, now it works as expected. Thank you.
No duplicated "Received-SPF" and *removing "Received" in position
1 is now not the own
Hi,
Things have gotten stranger for case 1.
If milter "chgheader" is used, the Index 1 is the hidden (prepended) header of
postfix. So, you must start in index = 2 to delete the first header received in header
callback.
Regards,
Carlos Velasco
Carlos Velasco via Postfix-users escr
ut another new one,
just above the "own Postfix-prepended Received: header". This is weird.
I was trying to look into postfix code to see if I could make some custom make
changes for this, but I'm totally lost, any help would be appreciated.
Regards,
Carlos Velasco
___
Wietse Venema via Postfix-users escribió el 10/12/2023 a las 15:53:
Carlos Velasco via Postfix-users:
2. Duplicated SMTP Access Policy Delegation
This issue is related to headers too.
I'm using pypolicyd-spf as policy daemon to check SPF. It is working fine.
The execution happens before milter
Scott Kitterman via Postfix-users escribió el 10/12/2023 a las 18:09:
On December 10, 2023 3:54:13 PM UTC, Carlos Velasco via
Postfix-users wrote:
Wietse Venema via Postfix-users escribió el 10/12/2023 a las 15:53:
Carlos Velasco via Postfix-users:
2. Duplicated SMTP Access Policy
Wietse Venema via Postfix-users escribió el 10/12/2023 a las 18:49:
Carlos Velasco via Postfix-users:
That means you are somehow calling the policy server twice.
You didn't mention what version of the SPF policy server you are
using. Recent versions (under the project name SPF Engine, since
21 matches
Mail list logo
