Re: [Mimedefang] documentation bug/omission for newbies

2016-04-20 Thread Bill Cole
On 20 Apr 2016, at 11:46, starlight.201...@binnacle.cx wrote: On Tue, Apr 19 2016 20:58 -0400 Dianne Skoll dfs at roaringpenguin.com wrote: Here it has taken me a couple of days to get up to speed, but just looking at that Microsoft picture would have taken me to the same place in 15 minutes.

Re: [Mimedefang] documentation bug/omission for newbies

2016-04-20 Thread starlight . 2016q2
>On Tue, Apr 19 2016 20:58 -0400 Dianne Skoll dfs at roaringpenguin.com wrote: >> >> Here it has taken me a couple of days to >> get up to speed, but just looking at that Microsoft >> picture would have taken me to the same place in >> 15 minutes. > >Oh, you mean like slide #52 of my slide deck? T

Re: [Mimedefang] documentation bug/omission for newbies

2016-04-20 Thread Dianne Skoll
Hi, Just a general comment: If someone hands you a MIME::Entity object, you shouldn't assume it's single-part. Nor should you assume it's multi-part. Your code should adapt to whatever it has been given. It turns out MIMEDefang does always start out with a multipart (for boring technical reaso

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

Re: [Mimedefang] documentation bug/omission for newbies

2016-04-18 Thread starlight . 2016q2
I'm still having trouble seeing it--apologies. Spent most of an hour going through the presentation deck Saturday while writing the body regex scanner and did not find anything that addresses it. Just looked again searching the document for "body," "open," "text," "match" "regex," "regular," "

Re: [Mimedefang] documentation bug/omission for newbies

2016-04-18 Thread Dianne Skoll
On Mon, 18 Apr 2016 15:32:37 -0400 starlight.201...@binnacle.cx wrote: > Hmm, I don't see how that works. The filter() method is described as > being called for each part where I want to examine just the body, > explicitly disregard subsequent parts and attachments. Also I don't > see any simpli

Re: [Mimedefang] documentation bug/omission for newbies

2016-04-18 Thread starlight . 2016q2
>On Sun, 17 Apr 2016 17:42:31 -0400 >starlight.2016q2 at binnacle.cx wrote: >> >> my $bdyscn_flag = 0; >> my $part0 = $entity->parts(0); >> ... elaborate code omitted > >But that's a rather roundabout way to do it; just do your single-part >processing inside filter() instead of filter_begin() Hmm,

Re: [Mimedefang] documentation bug/omission for newbies

2016-04-18 Thread Dianne Skoll
On Sun, 17 Apr 2016 17:42:31 -0400 starlight.201...@binnacle.cx wrote: > Would have saved me that day if the above tidbit were mentioned and > that one can easily write something similar to > my $bdyscn_flag = 0; > my $part0 = $entity->parts(0); > ... elaborate code omitted But that's a rather r

Re: [Mimedefang] documentation bug/omission for newbies

2016-04-17 Thread starlight . 2016q2
Hello, First, I must say MIMEDefang is awesome and thank you for this excellent software. Am a causal email hacker trying to keep my private MTA alive in the ever thickening email jungle. Lately have been increasing the degree of customization in MIMEDefang, with a trigger being the need to b

[Mimedefang] documentation bug/omission for newbies

2016-04-17 Thread starlight . 2016q2
[edited slightly from original to pass filter] Hello, First, I must say MIMEDefang is awesome and thank you for this excellent software. Am a causal email hacker trying to keep my private MTA alive in the ever thickening email jungle. Lately have been increasing the degree of customization i

[Mimedefang] documentation bug/omission for newbies

2016-04-17 Thread starlight . 2016q2
Hello, First, I must say MIMEDefang is awesome and thank you for this excellent software. Am a causal email hacker trying to keep my private MTA alive in the ever thickening email jungle. Lately have been increasing the degree of customization in MIMEDefang, with a trigger being the need to b

[Mimedefang] documentation bug/omission for newbies

2016-04-17 Thread starlight . 2016q2
Hello, First, I must say MIMEDefang is awesome and thank you for this excellent software. Am a causal email hacker trying to keep my private MTA alive in the ever thickening email jungle. Lately have been increasing the degree of customization in MIMEDefang, with a trigger being the need to h

Re: [Mimedefang] documentation bug/omission for newbies

2016-04-17 Thread starlight . 2016q2
Here's an improvment to the basic body-scan snippet so it does not attempt to scan a non-text first/body mime part: my $bdyscn_flag = 0; my $part0 = $entity->parts(0); if (defined $part0) { my ($type, $subtype) = split('/', $part0->effective_type); my $bh = $type eq 'text' ? $part0->bodyh