[Mimedefang] documentation bug/omission for newbies
skmimedefang at smail.inf.fh-bonn-rhein-sieg.de
Wed Apr 20 02:13:10 EDT 2016
-----BEGIN PGP SIGNED MESSAGE-----
On Tue, 19 Apr 2016, starlight.2016q2 at binnacle.cx wrote:
> At 02:58 4/19/2016 -0400, Steffen Kaiser skmimedefang at smail.inf.fh-bonn-rhein-sieg.de 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
> 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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
-----END PGP SIGNATURE-----
More information about the MIMEDefang