[pfx] two 2822.From header with header_checks

2024-01-27 Thread Byung-Hee HWANG via Postfix-users
Hellow Postfix heackers,

I have some odd email [1]. That have two 2822.From headrs. I would like
to filer such style email. Is it possible to filter with header_checks?


From: Byung-Hee HWANG 
From: Byung-Hee HWANG 


Because Google Gmail don't like above style... i'm serious now... 

Thanks in advance!

[1]
https://gitlab.com/soyeomul/Gnus/-/raw/9fedd75c57c4dd4aa9739bb7999146e5c77afdf1/stuff/rfc2822-violation.txt


Sincerely, Byung-Hee

-- 
^고맙습니다 _布德天下_ 감사합니다_^))//
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org


[pfx] Re: Log/Capture outbound messages?

2024-01-27 Thread joe a via Postfix-users

On 1/26/2024 20:55:16, Viktor Dukhovni via Postfix-users wrote:

On Fri, Jan 26, 2024 at 07:51:31PM -0500, Wietse Venema via Postfix-users wrote:

joe a via Postfix-users:

Postfix  3.5.9-5.9.2

Perhaps not a postfix question at all.  Looking for a way to capture
outbound email, for troubleshooting purposes.

Is "smtp-sink" the way to do this?


That could be, if you are interested in outbund SMTP deliveries.
smtp-sink has a crude option to save messages to file.

If you want to save am "extra" copy for investigation, consider
using always_bcc, sender_bcc_maps or recipient_bcc_maps.


Or just deliver the messages to a maildir.  The OP rather failed to
specify clearly what "capture" or "outbound mail" meant.



Yes, not clearly expressed.

The suggestions are appreciated and should suffice for now.

Thanks.
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org


[pfx] Re: Log/Capture outbound messages?

2024-01-27 Thread joe a via Postfix-users

On 1/26/2024 19:51:31, Wietse Venema via Postfix-users wrote:

joe a via Postfix-users:

Postfix  3.5.9-5.9.2

Perhaps not a postfix question at all.  Looking for a way to capture
outbound email, for troubleshooting purposes.

Is "smtp-sink" the way to do this?


That could be, if you are interested in outbund SMTP deliveries.
smtp-sink has a crude option to save messages to file.

If you want to save am "extra" copy for investigation, consider
using always_bcc, sender_bcc_maps or recipient_bcc_maps.

Wietse
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org



Yes, outbound SMTP deliveries. Thanks for the suggestions.
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org


[pfx] Re: different queue time based on the sender address

2024-01-27 Thread Viktor Dukhovni via Postfix-users
On Sat, Jan 27, 2024 at 12:01:55PM +0100, Aleksandar Ivanisevic via 
Postfix-users wrote:

> in main.cf
> sender_dependent_default_transport_maps = hash:/etc/postfix/relay_by_sender
> 
> in /etc/postfix/relay_by_sender
> mysender.com smtp:[localhost]:588

The listening SMTP service for that port would have to be part of a
different Postfix "instance":

https://www.postfix.org/MULTI_INSTANCE_README.html

> in master cf
> 588   inet n   -   n   -   -   smtpd -o 
> maximal_queue_lifetime=1d -o sender_dependent_default_transport_maps=

With the parameters in question set in the main.cf file of that
instance.  You can only override parameters that are documented
as relevant to the service (smtpd(8)) in question, and even then
only to the extent that they're exclusively used by that service,
otherwise (as with e.g. virtual_alias_maps, used in both smtpd(8)
for recipient validation, and cleanup(8) for address rewriting)
you may not get the results you expected.

See the smtpd(8) manpage for the list of parameters known to smtpd(8),
and qmgr(8) and trivial-rewrite(8) for the parameters that are
"queue-wide", and can only be set per-Postfix-instance, rather than
per-SMTP-service.

-- 
Viktor.
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org


[pfx] Re: different queue time based on the sender address

2024-01-27 Thread Wietse Venema via Postfix-users
Aleksandar Ivanisevic via Postfix-users:
> i would like to have maximal_queue_lifetime (and possibly some
> other parameters) based on the sender address. So I did the following

This request is unlikely to be implemented. It is one of those
features that benefit a very small fraction of the pupulation at a
dispropertionate cost for implementation and maintenance.

> in main.cf
> sender_dependent_default_transport_maps = hash:/etc/postfix/relay_by_sender
> 
> in /etc/postfix/relay_by_sender
> mysender.com smtp:[localhost]:588
> 
> in master cf
> 588   inet n   -   n   -   -   smtpd -o 
> maximal_queue_lifetime=1d -o sender_dependent_default_transport_maps=

maximal_queue_lifetime and sender_dependent_default_transport_maps
are implemented in different programs. Postfix programs cannot send
main.cf settings into other Postfix programs. That is not a bug but
a safety feature.

Wietse
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org


[pfx] different queue time based on the sender address

2024-01-27 Thread Aleksandar Ivanisevic via Postfix-users


Hi,

i would like to have maximal_queue_lifetime (and possibly some other 
parameters) based on the sender address. So I did the following

in main.cf
sender_dependent_default_transport_maps = hash:/etc/postfix/relay_by_sender

in /etc/postfix/relay_by_sender
mysender.com smtp:[localhost]:588


in master cf
588   inet n   -   n   -   -   smtpd -o 
maximal_queue_lifetime=1d -o sender_dependent_default_transport_maps=


but when I try to send a mail, I see that sender is correctly recognized and 
mapped to port 588, but then I get a loop, as if 
sender_dependent_default_transport_maps= is ignored or overriden when using 
port 588


Jan 27 10:00:47 v2 postfix/smtp[320178]: 7DEE8301CF40: 
to=<3ig4thiixeh...@dkimvalidator.com>, relay=localhost[127.0.0.1]:588, 
delay=0.23, delays=0.1/0.02/0.02/0.09, dsn=2.0.0, status=sent (250 2.0.0 Ok: 
queued as 9CA48301CF48)

and then again

Jan 27 10:00:47 v2 postfix/smtp[320178]: 9CA48301CF48: 
to=<3ig4thiixeh...@dkimvalidator.com>, relay=localhost[127.0.0.1]:588, 
delay=0.23, delays=0.09/0.01/0.05/0.09, dsn=2.0.0, status=sent (250 2.0.0 Ok: 
queued as C0121301CF40)

…

until 

Jan 27 10:00:52 v2 postfix/smtp[320178]: DADDB301CF48: 
to=<3ig4thiixeh...@dkimvalidator.com>, relay=localhost[127.0.0.1]:588, 
conn_use=47, delay=0.1, delays=0.09/0/0/0, dsn=5.4.0, status=bounced (host 
localhost[127.0.0.1] said: 554 5.4.0 Error: too many hops (in reply to end of 
DATA command))


what am I doing wrong here? Is this the right line of thinking or should I use 
something else? If at all possible I would like to avoid runing another 
instance of postfix even or another MTA. postfix version is 3.5.8.

thank you.


___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org