Hi,
* default_delivery_status_filter
The documentation says this can also be used to modify the "explanatory
text". Maybe you could add an example for this?
If I extend the existing example like this:
/^4(\.\d+\.\d+ TLS is required, but host \S+ refused to start TLS: .+)/
5$1 No luck
Hi,
I have some more small suggestions, but I don't want to start a separate
thread for each ;-)
* First is a question:
Is default_delivery_status_filter affecting Postfix's messages (a) in
the SMTP session, (b) in the logfile, and/or (c) in DSNs?
I can't see any difference in (a) and (b), so
Hi,
thanks - this is indeed better, since it just collects all messages in
the deferred queue meanwhile.
I was bound to the idea of informing connecting clients of the outage,
but this indeed doesn't make much sense... ;-)
Cheers,
Thomas
Am 21.11.24 um 13:26 schrieb Ralph Seichter via Pos
o requires:
smtpd_delay_reject = no
So maybe you could introduce a dedicated option for that?: Answer with
400 to everything, with a custom message.
Cheers,
Thomas
Am 19.11.24 um 22:49 schrieb Wietse Venema:
Thomas Landauer via Postfix-users:
Hi,
when handing over incoming messages to an extern
Hi,
thanks!
Bottom line:
I think this is impossible to explain in words! Please include the table
at http://www.postfix.org/postconf.5.html#delay_logging_resolution_limit
The rest of this mail is just to convince you ;-)
When setting it to 6, I'm getting this in my logfile:
delays=0.12/0
Hi,
please clarify the following explanation at
http://www.postfix.org/postconf.5.html#delay_logging_resolution_limit
Large delay values are rounded off to an integral number of seconds; delay values below the delay_logging_resolution_limit are logged as "0", and delay values under 100s are lo
Hi,
when handing over incoming messages to an external command (i.e. a
`pipe` delivery in `master.cf`), is it possible to keep the sender "on
hold" in the SMTP session and then answer with 500 right away (if the
external command returns 1), instead of answering with `250 2.0.0 Ok:
queued as..
Hi,
thanks!
A detail first:
At
http://www.postfix.org/postconf.5.html#smtpd_delay_open_until_valid_rcpt
please change "mail transaction ID" to "queue ID" for consistency here:
The downside is that rejected recipients are logged with NOQUEUE instead of a
mail transaction ID
About DSN:
Thank
Hi,
thanks!
A detail first:
At
http://www.postfix.org/postconf.5.html#smtpd_delay_open_until_valid_rcpt
please change "mail transaction ID" to "queue ID" for consistency here:
The downside is that rejected recipients are logged with NOQUEUE instead of a
mail transaction ID.
Viktor's logfil
Hi,
my use case (same as in previous thread): I want to find out if outgoing
messages were delivered successfully, so I'm looking at the lines
containing `status=` in the logfile.
Problem: I'm running several domains/projects on the same server, so I
need to query multiple databases with the
Hi,
my use case: I want to find out if outgoing messages were delivered
successfully, so I'm looking at the lines containing `status=` in the
logfile.
But I need this only for some mails (not all). To find out, I have to
query the database for the Queue-ID. This step could be skipped if it
Hi,
thanks for the hints, guys - I went for rsyslog omprog and it looks good
so far :-)
--
Cheers,
Thomas
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
Hi,
thanks for the hint with the `domain` option! :-)
I had missed that :-(
--
Cheers,
Thomas
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
Hi,
my use case:
I need to find out if an outgoing message was successfully delivered or not.
I know this can be achieved by setting up some filesystem watcher for
the logfile, and/or by having a cronjob searching through the logfile
for the line containing `status=`.
But it would be so much ni
Hi,
yeah, I think the docs about the connection are clearer now :-)
However, the "three queries behavior" is still undocumented IMO. I did
read https://www.postfix.org/virtual.5.html and it is nicely explained
there.
But my point is: If somebody is configuring the database lookup at
`local_re
Hi,
Rather, Postfix address rewriting makes multiple queries against
whatever tables are configured, using various fragments of the input
address as documented for virtual(5), aliases(5), canonical(5), etc.
Sorry, I still don't get it :-(
If everything is tried anyway, then what's the reason o
Hi everybody,
thanks for answering! :-)
The expansion parameters `%s`, `%u` and `%d` are not working as documented:
You're mistaken. The behaviour is exactly as documented.
Sorry, but where is this documented at
https://www.postfix.org/pgsql_table.5.html ? I see explanations for each
exp
Hi,
I think I found some bugs in `postfix-pgsql` lookup, or at least the
docs don't match the actual behavior.
1:
The expansion parameters `%s`, `%u` and `%d` are not working as documented:
If I'm just using `%s` in my query template like this:
query = SELECT foo FROM mytable WHERE foo = '%
18 matches
Mail list logo
