in reply to Re: Reliable email parsing
in thread Reliable email parsing
But when I say "RFC compliant" I mean support for all possible formats for email addresses, comments in email headers and all things like locale/language/encoding-specific, for example:
Content-Disposition: attachment; filename*0*=koi8-r'ru'%F0%D2%C9%D7%C5%D4 filename*1*=%20from filename*2=" russia.txt"
And about 'defect free'. There enough information on this topic now. Good example of it is DJB software and most basic&simple *NIX utils. I'm sure: more code == more bugs, so I always prefer smaller/simpler solutions.
I'm sure solution compliant to all these RFC can be coded under ~1000-1500 lines of code (I've partially done it already).
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^3: Reliable email parsing
by adamk (Chaplain) on Sep 14, 2006 at 02:59 UTC | |
|
Re^3: Reliable email parsing
by DrHyde (Prior) on Sep 14, 2006 at 10:00 UTC |