Re: [Mimedefang] documentation bug/omission for newbies

2016-04-19 Thread Steffen Kaiser
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 19 Apr 2016, starlight.201...@binnacle.cx wrote: At 02:58 4/19/2016 -0400, Steffen Kaiser skmimedef...@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 a

Re: [Mimedefang] documentation bug/omission for newbies

2016-04-19 Thread Joseph Brennan
It's interesting to see Microsoft explaining MIME when their Outlook product does not parse it correctly. Now possibly the latest Outlook finally gets this right, but I know that as recently as 2 years ago it did not. Given a message with this format: message: multipart/... part 1: text/pla

Re: [Mimedefang] documentation bug/omission for newbies

2016-04-19 Thread Dianne Skoll
On Tue, 19 Apr 2016 20:11:39 -0400 starlight.201...@binnacle.cx wrote: > Is easy for a technically competent person new to MIME > to be smacked by the nuances, but a little up-front > explanation would for the same audience be of great > help and potentially save a lot of time. I made 158 slides

Re: [Mimedefang] documentation bug/omission for newbies

2016-04-19 Thread starlight . 2016q2
At 02:58 4/19/2016 -0400, Steffen Kaiser skmimedef...@smail.inf.fh-bonn-rhein-sieg.de wrote: >because MIMEDefang internally breaks up the message into parts >anyway and feeds all parts to filter(), I would construct your >code like so: [code omitted] Ah! I must concede that if one is looking fo

Re: [Mimedefang] documentation bug/omission for newbies

2016-04-19 Thread starlight . 2016q2
This is helpful: https://msdn.microsoft.com/en-us/library/office/aa563064%28v=exchg.140%29.aspx Shows a MIME hierarchy with a picture! Coming to this without having ever pondered MIME before (sorry) left me at a disadvantage when trying to write my first filter beyond cut/paste. Perhaps a not

Re: [Mimedefang] documentation bug/omission for newbies

2016-04-19 Thread starlight . 2016q2
Correction: "Guaranteed multipart" applies to only filter_begin() not to filter*(). I suggest adding brief documentation indicating the expected state of $entity for each of the filter*() callbacks. Some expansion regarding when filter() and filter_multipart() are called is worthwhile. Reading m

Re: [Mimedefang] documentation bug/omission for newbies

2016-04-19 Thread starlight . 2016q2
At 02:58 4/19/2016 -0400, Steffen Kaiser skmimedef...@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 _nev

Re: [Mimedefang] documentation bug/omission for newbies

2016-04-19 Thread Steffen Kaiser
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 18 Apr 2016, starlight.201...@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 me