-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 19 Apr 2016, [email protected] wrote:
At 02:58 4/19/2016 -0400, Steffen Kaiser
[email protected] wrote:
On Mon, 18 Apr 2016, starlight.2016q2 at binnacle.cx wrote:
I just spent a day butting my head against the fact that filter_begin()
is _always_ passed a multipart MIME message container that _never_ has a
useable $entity->bodyhandle(). This is not mentioned *anywhere*.
hmm, I would not rely on this assumption.
I looked, and one positively for certain can rely on it:
in mimedefang.pl version 2.78 at line 6008:
it is not documented and therefore v2.79 might implement it totally
different.
lines different than the first attempt. So all I'm
saying is that the "guaranteed multipart" state of
That would stick all future versions of MIMEDefang to that decision.
In fact, doing so would contradict the idea between
filter_begin()/filter/filter_multipart(), IMHO. For normal cases, you
need not to worry about the MIME structure of the message.
- --
Steffen Kaiser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEVAwUBVxcd9lGgR0+MU/4GAQKmiQf+PqOb0Pgn+b70smJENiXFFvrTl0AmgQOC
CWl284ibvFufaUrlLMXtUPh6oS6keQ8HkMcKdy6ve/otd/aoh6BAfdOxZNZH2Kwb
ylP6ee3I4jlgyoXeKM1FkfQhSRVthHSO99khZi4ScstPF4zeI6AYH2y5ERjXTxd5
Ucp3FRKj2Kz+oSW/ewv/BVSAhsZhm+S/wbx43EVGE1i+Vv4FHW8Bq9Q8+QxPm8Jc
9FyRwzjMKEMqfoBwDXCbszhoGN+F++8s2BBnwzBB55VGaKGeddUYEbjhqrrYya+n
OoDpgBYctO3xzNg1stpMfEU2hWeft7F0D0y72V7eQhcZhq4WK1f25A==
=lC1j
-----END PGP SIGNATURE-----
_______________________________________________
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID. You may ignore it.
Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list [email protected]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
