On 25.01.23 01:48, Matus UHLAR - fantomas wrote:
You are right. The milter is called twice, because a FILTER
(spamassassin in this case) is applied, after which the message is
re-injected using pickup, which triggeres the second milter run
during cleanup. (Still, I think the graphic on the MILT
On 24.01.23 23:09, Jaroslaw Rafa wrote:
No. The Postfix documentation says:
non_smtpd_milters (default: empty)
A list of Milter (mail filter) applications for new mail that does not
arrive via the Postfix smtpd(8) server. This includes local submission via
the sendmail(1) command line, new
On 24.01.23 23:15, EML wrote:
I don't think there's any way to get bounces through the milters,
short of rewriting the bounce code.
Have a look at the "Signing internally-generated bounce messages"
paragraph on https://www.postfix.org/MILTER_README.html.
/internal_mail_filter_classes = bounce
Hi everyone,
I'm currently investigating a situation that milters are called twice,
once by smtpd, and once by cleanup, when both smtpd_milters and
non_smtpd_milters are configured (to the same values).
The graphic on https://www.postfix.org/MILTER_README.html suggests that
this is normal be
I agree with Thomas on this. If someone is spying on the server, any
past and future emails can be stolen. In case all incoming mails are
PGP-encrypted on the server, future emails can still be stolen, but
atleast any past correspondence is secure.
Yannik
Am 03.06.2015 um 03:50 schrieb Sebastian
> No. Parameter expansion is recursive, and this yields an infinite loop.
> The default value is never used when you override a parameter.
>
> You need to cut/paste the default value into the replacement. There
> is no support for prepend or append.
I see.
Yannik
Hi Noel,
> If you have postfix listening on several ports and want to know
> which port the client connected to, you can set a different syslog
> name to differentiate them in the logs. For example, it's common to
> set ' -o syslog_name=postfix/submission' on the port 587 submission
> listener.
I
just out of curiosity: wouldn't this also block legitimate users who use a
third party mailserver on port 25?
Am 24. Mai 2015 13:23:01 MESZ, schrieb Christos Chatzaras :
>Thank you everyone for the replies. I think I found the problem. The
>spambot (uploaded by hacked websites) does direct conne
Hi everyone,
is it possible at all to log the local port that is used for a
connection? There is "smtpd_client_port_logging" but this seems to only
log the remote port.
greetings
Yannik
