Ken Smith:
>
> Wietse Venema wrote:
> > {snip}
> >> But senders are not getting DSN's
> > Why should Postfix send those?
> >
> > - What delivery status notifications did a remote SMTP client
> > request in the RCPT TO command?
> >
> > - What delivery status notifications did a local user request
Wietse Venema wrote:
{snip}
But senders are not getting DSN's
Why should Postfix send those?
- What delivery status notifications did a remote SMTP client
request in the RCPT TO command?
- What delivery status notifications did a local user request
with the Postfix sendmail -N command-line
Rafael Azevedo:
> Wietse,
> Also I've noticed that when the filter is applied it kinds of groups the
> pipe process per domain.
Indeed. It would be wasteful to filter the same message mutilple times.
Wietse
On Mon, Feb 27, 2023 at 05:39:50PM -0300, Rafael Azevedo wrote:
> Nevermind, got it working after
> changing default_destination_recipient_limit=1.
DO NOT do THAT. Instead, at most do it only for the transport in
question:
_destination_recipient_limit
Where is the content-filter
Nevermind, got it working after
changing default_destination_recipient_limit=1.
Em seg., 27 de fev. de 2023 às 17:30, Rafael Azevedo
escreveu:
> Wietse,
> Also I've noticed that when the filter is applied it kinds of groups the
> pipe process per domain.
>
> For example, I called my script for
On Mon, Feb 27, 2023 at 05:30:18PM -0300, Rafael Azevedo wrote:
> Also I've noticed that when the filter is applied it kinds of groups the
> pipe process per domain.
The Postfix queue manager batches message recipients by nexthop, up to
the per-transport recipient limit per batch. For
Wietse,
Also I've noticed that when the filter is applied it kinds of groups the
pipe process per domain.
For example, I called my script for 3 recipients within same domain and the
postfix pipe called my script like "script.sh recipie...@domain1.com
recipie...@domain1.com and so" and because of
Thanks for the reply Wietse.
This is my scenario:
mail in > postfix policy_check -> content_filter -> deliver
I noticed that when I'm using policy_check the action allows it to be
delivered.
After changing it I was able to send from policy_check to my footer pipe
script.
Is there a way to do
Wietse Venema:
> That is evendence that content_filter is not being used. Are you
> aware that your "smtpd -o content_filter=blah" will only process
> messages that arrive via SMTP port 25?
Rafael Azevedo:
> Hi Wietse, thanks for the reply.
>
> Yes I am. And this message is being sent through
Hi Wietse, thanks for the reply.
Yes I am. And this message is being sent through port 25.
There's one thing I have doubt about: will it process as the after-queue
content-filter?
Thanks once again.
Regards.
Em seg., 27 de fev. de 2023 às 12:32, Wietse Venema
escreveu:
> Rafael Azevedo:
> >
Fourhundred Thecat:
> > On 2023-02-27 15:08, Wietse Venema wrote:
> > Fourhundred Thecat:
> >>
> >> The problem is, postfix does not seem to distinguish between IP having
> >> no DNS record, and my DNS server being temporarily unavailable.
> >
> > Actually it does. 450 means temporary error.
>
>
> On 2023-02-27 15:08, Wietse Venema wrote:
Fourhundred Thecat:
The problem is, postfix does not seem to distinguish between IP having
no DNS record, and my DNS server being temporarily unavailable.
Actually it does. 450 means temporary error.
thank you, but I only see "450 4.7.25",
Rafael Azevedo:
> Even running this as the filter-script it just doesn't work:
>
> #!/bin/bash
> # Localize these.
> echo Message content rejected;
> exit 75;
>
>
> The message goes to final recipient instead of being rejected.
That is evendence that content_filter is not being used. Are you
natan:
> Hi
> In file i have:
>
> /^Content-(Type|Disposition):.*(file)?name=.*(\.|=2E)(exe|ade|adp|bas|bat|chm|cmd|cpl|hlp|hta|inf|ins|isp|img|js|jse|mde|msc|msi|msp|mst|pcd|pif|reg|scr|sct|shs|shb|vb|vbe|vbs|wsc|wsf|wsh|mim|b64|bhx|hqx|xxe|uu|uue)"/
>
>
> REJECT Sorry, we do not accept .${4}
Even running this as the filter-script it just doesn't work:
#!/bin/bash
# Localize these.
echo Message content rejected;
exit 75;
The message goes to final recipient instead of being rejected.
Thanks
Em seg., 27 de fev. de 2023 às 11:33, Rafael Azevedo
escreveu:
> Thats one of the
Dnia 27.02.2023 o godz. 16:10:29 natan pisze:
> Hi
> In file i have:
>
> /^Content-(Type|Disposition):.*(file)?name=.*(\.|=2E)(exe|ade|adp|bas|bat|chm|cmd|cpl|hlp|hta|inf|ins|isp|img|js|jse|mde|msc|msi|msp|mst|pcd|pif|reg|scr|sct|shs|shb|vb|vbe|vbs|wsc|wsf|wsh|mim|b64|bhx|hqx|xxe|uu|uue)"/
>
>
Dnia 27.02.2023 o godz. 09:56:47 Wietse Venema pisze:
> A much simpler rule would block all double extensions (such as
> 'name.pdf.jpg'), but I don't know if that would also block legitimate
> mail.
If someone sends you for example a .tar.gz file as an attachment... :)
--
Regards,
Jaroslaw
Hi
In file i have:
/^Content-(Type|Disposition):.*(file)?name=.*(\.|=2E)(exe|ade|adp|bas|bat|chm|cmd|cpl|hlp|hta|inf|ins|isp|img|js|jse|mde|msc|msi|msp|mst|pcd|pif|reg|scr|sct|shs|shb|vb|vbe|vbs|wsc|wsf|wsh|mim|b64|bhx|hqx|xxe|uu|uue)"/
REJECT Sorry, we do not accept .${4} file type.
natan:
> Hi
> I gat many many e-mails with virus and double exstension like:
> *.jpg.img
> *.pdf.img
> *.*.img
>
> I try in header_checks.pcre
>
[broken regexp omitted]
>
> and not working
The following blocks a 'bad' extension before a 'good' one such
as 'name.exe.pdf'.
1) Take the example
On Mon, Feb 27, 2023 at 11:33:48AM -0300, Rafael Azevedo wrote:
> /usr/bin/altermime --input=in.$$ \
>--disclaimer=/home/filter/stopka.txt \
>--disclaimer-html=/home/filter/stopka.html \
What is that last "\" for? To debug "altermime" test it outside the
Hi
But in config i have:
postconf |grep "mime_header_checks"
mime_header_checks = $header_checks
W dniu 27.02.2023 o 15:47, Matus UHLAR - fantomas pisze:
On 27.02.23 12:38, natan wrote:
I gat many many e-mails with virus and double exstension like:
*.jpg.img
*.pdf.img
*.*.img
I try in
On 27.02.23 12:38, natan wrote:
I gat many many e-mails with virus and double exstension like:
*.jpg.img
*.pdf.img
*.*.img
I try in header_checks.pcre
Thats one of the examples I tried here but its not working...
I receive the message like if it has not been through the filter.
Em seg., 27 de fev. de 2023 às 11:23, natan escreveu:
> Hi
> Auto added footer is very bad but nn one of server i have:
>
> smtp inet n - n -
On Mon, Feb 27, 2023 at 11:08:47AM -0300, Rafael Azevedo wrote:
> For every sent message we want to add a footer with a counter.
Whatever...
> I've tried to add the "content_filter" tag as shown:
>
> smtp inet n - n - 50 smtpd
> -o content_filter=footer
Dnia 27.02.2023 o godz. 15:22:27 natan pisze:
>
> $SENDMAIL "$@"
Hi
Auto added footer is very bad but nn one of server i have:
smtp inet n - n - - smtpd -o
content_filter=stopka
stopka unix - n n - - pipe
flags=Rq user=filter argv=/home/filter/add_filter.sh -f ${sender}
--
Ken Smith:
> and I can see these lines are now being added to the delivered e-mail
> headers
>
> Delivered-To: k...@kensnet.org
> X-Original-To: k...@kensnet.org
>
> But senders are not getting DSN's
Why should Postfix send those?
- What delivery status notifications did a remote SMTP client
Hi there,
I was doing a research about how to implement an outgoing email filter.
For every sent message we want to add a footer with a counter.
I've tried to add the "content_filter" tag as shown:
smtp inet n - n - 50 smtpd
-o content_filter=footer
Fourhundred Thecat:
> Hello,
>
> I am using simple python script to parse postfix logs, and ban offending
> IP addresses. One of the patterns I am matching is unknown host:
>
> NOQUEUE: reject: RCPT from unknown[195.133.40.183]: 450 4.7.25
> Client host rejected: cannot find your hostname
>
On 2023-02-27 at 04:49:55 UTC-0500 (Mon, 27 Feb 2023 10:49:55 +0100)
Fourhundred Thecat <400the...@gmx.ch>
is rumored to have said:
On 2023-02-27 08:43, Matus UHLAR - fantomas wrote:
On 27.02.23 08:07, Fourhundred Thecat wrote:
The problem is, postfix does not seem to distinguish between IP
Hi
I gat many many e-mails with virus and double exstension like:
*.jpg.img
*.pdf.img
*.*.img
I try in header_checks.pcre
Wietse Venema wrote:
Ken Smith:
Hi, first post to this list but long term Linux user here.
I have Postfix configured for virtual domains and delivery to cyrus-imap
via LMTP over IP. All is working well besides one detail.
It seems that when senders request a DSN they do not get any response.
On 27.02.23 08:07, Fourhundred Thecat wrote:
The problem is, postfix does not seem to distinguish between IP having
no DNS record, and my DNS server being temporarily unavailable.
On 2023-02-27 08:43, Matus UHLAR - fantomas wrote:
why do you think that?
the error above is a "4xx" which means
> On 2023-02-27 08:43, Matus UHLAR - fantomas wrote:
On 27.02.23 08:07, Fourhundred Thecat wrote:
The problem is, postfix does not seem to distinguish between IP having
no DNS record, and my DNS server being temporarily unavailable.
why do you think that?
the error above is a "4xx" which
34 matches
Mail list logo
