-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Sapiro wrote:
> I have identified the problem with 2.1.5 and earlier. Basically, it
> has nothing to do with PGP signed messages. The problem was if a
> message contained a multipart MIME sub-part which in turn contained
> one or more text/plain p
Mark Sapiro wrote:
>
>Regarding the original problem of the message body and attached patch
>not being in the archive, I have done some testing with the latest
>Scrubber, and it works properly with all the test messages Todd sent me.
>
>I note that the annotation "Skipped content of type multipar
Jeff DeReus wrote:
> It seems that adding the filter_types has one effect. When the list
> subscribers get a message that has been PGP signed, the signature is
> no longer valid.
I assume here that content filtering is On. There is not much Mailman
can do in these cases. I'm not sure what the s
It seems that adding the filter_types has one effect. When the list
subscribers get a message that has been PGP signed, the signature is no
longer valid.
When a patch is submitted (for developers) it is stripped from the message
that is posted to one list and the entire message with the patch is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Sapiro wrote:
> Todd Zullinger wrote:
[...]
>>Around line 300 in Handlers.Scrubber, the comments say:
>>
>># All parts should be scrubbed to text/plain by now.
>>
>>and then a simple test for a non text/plain ctype is made, replacing
>>it with
Todd Zullinger wrote:
>
>In the bug report I found, there's a link to the archived message:
>
>http://sablecc.org/lists/sablecc-user/2004-December/000159.html
>
>and that looks just like the archived messages I have from testing.
>
>It starts off with:
>
>Skipped content of type multipart/m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Sapiro wrote:
> Before giving up on the archive, look at the 'source' html of the
> archive page and look at the 'source' of the scrubbed attachment(s).
> I've seen scrubbed attachments that look like X is missing when
> viewed in browser A and lo
Todd Zullinger wrote:
>
>Jeff DeReus wrote:
>
>> I have enabled the content_filter and added mime_types to see if
>> this will solve my little problem.
>>
>> application/pgp-signature
>> multipart/signed
>
>Let us know if it does. I'm not really familiar enough with the code
>to know if it will he
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff DeReus wrote:
> On 5/17/06, Todd Zullinger <[EMAIL PROTECTED]> wrote:
[...]
>> To be clear, does the message arrive properly to list members or is
>> the attachment and body stripped there as well as in the archives?
>> In my testing only the arch
On 5/17/06, Todd Zullinger <[EMAIL PROTECTED]> wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Jeff DeReus wrote:
> > Unfortunately filter_content was not set to yes. I am assuming that
> > would be fairly "handy".
>
> I'm not sure whether that will any effect on the archiving or no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff DeReus wrote:
> Unfortunately filter_content was not set to yes. I am assuming that
> would be fairly "handy".
I'm not sure whether that will any effect on the archiving or not.
It's been a long time since I tested that.
> Although everything g
Unfortunately filter_content was not set to yes. I am assuming that would
be fairly "handy". Although everything goes through properly with
filter_content disabled and when unsigned. As to the message in the
archives, the only piece that successfully arrived was
Skipped content of type multipar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff DeReus wrote:
> The poster uses an OpenPGP/MIME signature.
Okay.
> the pass_mime_types ==
>
> multipart/mixed
> multipart/alternative
> text/plain
I should have asked whether the filter_content setting was yes or no
too. If it's no, then the
The poster uses an OpenPGP/MIME signature.
the pass_mime_types ==
multipart/mixed
multipart/alternative
text/plain
Thank you,
Jeff D
On 5/17/06, Todd Zullinger <[EMAIL PROTECTED]> wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Jeff DeReus wrote:
> > I am running mailman 2.1.5 w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff DeReus wrote:
> I am running mailman 2.1.5 with sendmail. One of my users sent in
> an attachment with a message to the list. When he signs with his
> PGP key, only the PGP signature remains in the message. I have yet
> to locate the rest of th
Hello,
I am running mailman 2.1.5 with sendmail. One of my users sent in an
attachment with a message to the list. When he signs with his PGP key, only
the PGP signature remains in the message. I have yet to locate the rest of
the message. It is necessary to disable the signature to allow his p
16 matches
Mail list logo
