On 2022-01-16 04:41, Scott Kitterman wrote:
Not keeping the mail in memory for to better support large mails is on
my TODO
list for dkimpy-milter.
fuglu is already using dkimpy, but not dkimpy-milter, would you help
fuglu devs on make fuglu support milters ?
both is python btw
On Saturday, January 15, 2022 8:08:51 PM EST Robert Siemer wrote:
> > > Conceptually DKIM needs to go over the email twice: once to calculate
> > > and sign the checksum and once to write it out with the result of the
> > > previous step in the headers.¹
> >
> > Prepending a header does not
> > Conceptually DKIM needs to go over the email twice: once to calculate
> > and sign the checksum and once to write it out with the result of the
> > previous step in the headers.¹
>
> Prepending a header does not require rewriting the message body.
> Postfix queue files support efficient
> > So far I see that the after-queue content filter mechanism
> > (FILTER_README) forces you to write the email to disc again. (And
> > for no good reason, unfortunately: pipe should pass a read-only
> > file descriptor of the queue file to filter?s stdin. The filter
> > can use lseek() on that.)
Robert Siemer:
> Hello everyone,
>
> I need to DKIM sign possibly huge emails (up to 150MB).
>
> Conceptually DKIM needs to go over the email twice: once to calculate
> and sign the checksum and once to write it out with the result of
> the previous step in the headers.?
>
> A DKIM signer can do
On Sat, Jan 15, 2022 at 08:01:05PM +0100, Robert Siemer wrote:
> I need to DKIM sign possibly huge emails (up to 150MB).
No worries, you can do this with a milter, without storing
an extra copy of the complete message.
> Conceptually DKIM needs to go over the email twice: once to calculate
>
It appears that Benny Pedersen said:
>On 2022-01-15 20:01, Robert Siemer wrote:
>
>> I need to DKIM sign possibly huge emails (up to 150MB).
>
>insane
agreed
>> A DKIM signer can do this by either keeping the message in memory (a
>> no-go for me) or write it to a file.
>
>will a mount point on
Robert Siemer wrote:
> Gmail allows 150MB. Ok? And with that they are right. That is not
> "insane". Insane is the opposite: to reject an email, because a
> single file attachment ended up a little bigger than expected. Total
> user experience disaster.
I think you have me confused with someone
can’t do that? Or can it? How?
Regards,
Robert
> Gesendet: Samstag, 15. Januar 2022 um 20:16 Uhr
> Von: "Bob Proulx"
> An: postfix-users@postfix.org
> Betreff: Re: How to filter email (DKIM) without keeping the message in memory
> and without writing it to disc twice
On 2022-01-15 20:01, Robert Siemer wrote:
I need to DKIM sign possibly huge emails (up to 150MB).
insane
Conceptually DKIM needs to go over the email twice: once to calculate
and sign the checksum and once to write it out with the result of the
previous step in the headers.¹
what is your
Robert Siemer wrote:
> I need to DKIM sign possibly huge emails (up to 150MB).
I know you say you need this. But even if you had it would it
actually be useful to you?
DKIM is needed to interchange email with random email servers around
the Internet. Because said random servers will reject the
Hello everyone,
I need to DKIM sign possibly huge emails (up to 150MB).
Conceptually DKIM needs to go over the email twice: once to calculate and sign
the checksum and once to write it out with the result of the previous step in
the headers.¹
A DKIM signer can do this by either keeping the
Wietse Venema
> Use a per-recipient table:
>
> /etc/postfix/main.cf
> check_recipient_access hash:/etc/postfix/recipient_access.pcre
>
> /etc/postfix/recipient_access.pcre
> /^me@/ FILTER blah:blah-
> /./ reject_unknown_sender_domain
>
> Wietse
thanks a lot for
d tbsky:
> Hi:
> I want to filter all the mails send to filter...@example.com. so I
> create configuration at main.cf like below:
>
> smtpd_recipient_restrictions =
>check_recipient_access hash:/etc/postfix/filter_access,
>reject_unknown_sender_domain,
>permit
>
> and create
Hi:
I want to filter all the mails send to filter...@example.com. so I
create configuration at main.cf like below:
smtpd_recipient_restrictions =
check_recipient_access hash:/etc/postfix/filter_access,
reject_unknown_sender_domain,
permit
and create filter_access like below
Hallo Everyone,
I have a question: I want to implement an attachment filter
( mime_header_checks ), that filters special unicode Format characters.
Examples:
0x202E (right-to-left override)
0x202B (right-to-left embedding)
0x202D (left-to-right override)
0x202A (left-to-right embedding)
Complete
T.B.:
Hallo Everyone,
I have a question: I want to implement an attachment filter
( mime_header_checks ), that filters special unicode Format characters.
Examples:
0x202E (right-to-left override)
0x202B (right-to-left embedding)
0x202D (left-to-right override)
0x202A (left-to-right
T.B.:
According to RFC 2183/2184, content-disposition names containing
non-ASCII content must be encoded as ASCII strings.
This means you may need to handle content-disposition names that
violate RFC 2183/2184, besides correctly-encoded forms for UTF-8,
UTF-16, and so on. I am not sure
Heiko Wundram yazmış:
Am Tuesday 27 January 2009 13:08:18 schrieb Munroe Sollog:
This is the only mailing-list that I can't seem to create a filter
(sieve) for. Posts are sent to so many different combinations of users,
two different domains, two different users, and either can exist in
Tolga wrote, at 01/27/2009 08:19 AM:
Heiko Wundram yazmış:
I filter on the header
List-Post: mailto:postfix-users@postfix.org
which catches everything (AFAICT) that comes in over the list.
or by the From: line
Regards,
/Tolga
Your own message proves this to be incorrect:
Munroe Sollog escribió:
This is the only mailing-list that I can't seem to create a filter
(sieve) for. Posts are sent to so many different combinations of users,
two different domains, two different users, and either can exist in
either the TO: field or the CC: field. Is there a better
Jorey Bump yazmış:
Tolga wrote, at 01/27/2009 08:19 AM:
Heiko Wundram yazmış:
I filter on the header
List-Post: mailto:postfix-users@postfix.org
which catches everything (AFAICT) that comes in over the list.
or by the From: line
Regards,
/Tolga
Your own message
On Tue, Jan 27, 2009 at 02:37:22PM CET, Tolga to...@ozses.net said:
Jorey Bump yazmış:
Tolga wrote, at 01/27/2009 08:19 AM:
Heiko Wundram yazmış:
I filter on the header
List-Post: mailto:postfix-users@postfix.org
which catches everything (AFAICT) that comes in over the list.
On Tue, 27 Jan 2009 14:48:43 +0100
Erwan David er...@rail.eu.org wrote:
On Tue, Jan 27, 2009 at 02:37:22PM CET, Tolga to...@ozses.net said:
or by the From: line
Regards,
/Tolga
Your own message proves this to be incorrect:
From: Tolga to...@ozses.net
:0
Le Tue 27/01/2009, Chris Babcock disait
On Tue, 27 Jan 2009 14:48:43 +0100
Erwan David er...@rail.eu.org wrote:
On Tue, Jan 27, 2009 at 02:37:22PM CET, Tolga to...@ozses.net said:
or by the From: line
Regards,
/Tolga
Your own message proves this to be
Munroe Sollog a écrit :
This is the only mailing-list that I can't seem to create a filter
(sieve) for. Posts are sent to so many different combinations of users,
two different domains, two different users, and either can exist in
either the TO: field or the CC: field. Is there a better
26 matches
Mail list logo
