Re: [courier-users] Filter API

This is a MIME GnuPG-signed message. If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.

--===============0947869870==
Content-Type: multipart/signed;
boundary="=_mimegpg-commodore.email-scan.com-22172-1167501368-0002";
micalg=pgp-sha1; protocol="application/pgp-signature"

This is a MIME GnuPG-signed message. If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.

--=_mimegpg-commodore.email-scan.com-22172-1167501368-0002
Content-Type: text/plain; format=flowed; charset="US-ASCII"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Bernd Wurst writes:

> Hallo.
>
> Am Samstag, 30. Dezember 2006 17:51 schrieb Sam Varshavchik:
>> > Is there any reason for this limitation?
>> Yes, it's a technical limitation. In some situations, after filtering is
>> complete Courier may decide to rewrite the message's MIME headers and MIME
>> encoding. The message gets parsed internally before filters get invoked.
>> If the filter changes the contents of the message, the starting and the
>> ending positions of the individual MIME sections in the message will now be
>> different, and the message will be corrupted.
>
> Thank you for the explaination.
>
> Is there a plan for removing this limitation?
> To me, it seems like it shouldn't be too hard, if courier would do it's
> mime-processing completely either before or after filter invocation but not
> reading before and rewriting afterwards. :)

See, it's a matter of efficiency. Rather than receiving a message, saving
its contents into a file, and then rereading the file again to parse the
message, the message is parsed on the fly, as it is being received and saved
into its file. Which means that the parsing part happens pretty much before
everything else happens.



--=_mimegpg-commodore.email-scan.com-22172-1167501368-0002
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBFlqg4x9p3GYHlUOIRAq09AJ0QDoSPpZ0vR9IBE/EoBnvSnzsLmgCfUu6y
2GIukUrUiW67fxPpKXNQiS8=
=cpt1
-----END PGP SIGNATURE-----

--=_mimegpg-commodore.email-scan.com-22172-1167501368-0002--


--===============0947869870==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?p...rge&CID=DEVDEV
--===============0947869870==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users

--===============0947869870==--