Re: Debian package (was: Efficiency issues/thoughts)
Clemens Fischer <[email protected]>
| Newsgroups | gmane.mail.ifile.general |
|---|---|
| Message-ID | <[email protected]> |
Jason Rennie <[email protected]> writes: > [email protected] said: >> Indeed, I cannot read some of the old messages due to rotten >> cookies... > > This is worth discussing if you think there is a better solution. Does > sourceforge offer mailing lists? err-hm, well, ifile gets archived at gmane.org already, and for some months now ... > [email protected] said: >> But to stay on topic, I think it is wrong to build any special parsing >> into ifile (like MIME, headers, signatures, etc.). I think that such >> a job should be carried out by other (small) programs designed for >> that purpose (ie., the Unix way). Rationale: such small programs can >> be used by other programs, and when standards change, there is just >> one place to adapt that change. > > There are benefits to both approaches (lots of little programs/one program > that does everything). ifile uses the Unix approach for handling > differences between e-mail clients, but I don't know if it would be most > appropriate for parsing code. We'll see :) the past week has seen this discussion already, and for classification MIME while staying "within bounds" (of ifile), mr. browne has presented a perfectly fine solution including perl-snippets. full MIME for ifile would increase its processing time beyond what's feasable for real-time email filters. i think it would be another tool for this reason alone, although integrating meta-mail, selectable by an option would be a good idea. to make it more general, it should be a pre-processing option, so that users can specify anything suiting their needs. clemens