dovecot - Feb 2009 - OT: Fixing Messages To Be RFC 2822 Compliant

So....apparently I have some messages which are not RFC compliant sitting in
my mailboxes (mostly older ones), and I have some software which is refusing
to handle such messages.

1. Does anyone know of a nice way to verify that all my messages are
compliant/find those that aren't? (I suppose I could use the existing
failing software, but I was hoping for something a little more robust...)

2. Does anyone know of any tools that will do The Right Thing as far as
fixing these messages are concerned?

Googling didn't turn up much for me, but maybe I wasn't hitting the
right
terms ("RFC message repair", "fix email message", etc.).

Thanks.

Hello!

    I am not sure about what you want, but I found something that maybe 
useful for you.
    http://gd.tuwien.ac.at/linuxcommand.org/man_pages/formail1.html

Bye

Neil wrote:
> So....apparently I have some messages which are not RFC compliant sitting
in
> my mailboxes (mostly older ones), and I have some software which is
refusing
> to handle such messages.
>
> 1. Does anyone know of a nice way to verify that all my messages are
> compliant/find those that aren't? (I suppose I could use the existing
> failing software, but I was hoping for something a little more robust...)
>
> 2. Does anyone know of any tools that will do The Right Thing as far as
> fixing these messages are concerned?
>
> Googling didn't turn up much for me, but maybe I wasn't hitting the
right
> terms ("RFC message repair", "fix email message",
etc.).
>
> Thanks.
>
>   
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3354 bytes
Desc: S/MIME Cryptographic Signature
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20090223/166fb63e/attachment-0002.bin>

Hi,

Yeah, I'm vaguely familiar with formail, but (after reviewing the
literature) it doesn't seem like it can be used to identify/fix existing
messages (unless you already know how they're broken and give it explicit
instructions to fix them).

Is there something I'm missing?

Thanks.

On Mon, Feb 23, 2009 at 4:24 AM, Darabos Edv?rd Konr?d <
nil at hippy.csoma.elte.hu> wrote:
> Hello!
>
>   I am not sure about what you want, but I found something that maybe
> useful for you.
>   http://gd.tuwien.ac.at/linuxcommand.org/man_pages/formail1.html
>
> Bye
>
>
> Neil wrote:
>
>> So....apparently I have some messages which are not RFC compliant
sitting
>> in
>> my mailboxes (mostly older ones), and I have some software which is
>> refusing
>> to handle such messages.
>>
>> 1. Does anyone know of a nice way to verify that all my messages are
>> compliant/find those that aren't? (I suppose I could use the
existing
>> failing software, but I was hoping for something a little more
robust...)
>>
>> 2. Does anyone know of any tools that will do The Right Thing as far as
>> fixing these messages are concerned?
>>
>> Googling didn't turn up much for me, but maybe I wasn't hitting
the right
>> terms ("RFC message repair", "fix email message",
etc.).
>>
>> Thanks.
>>
>>
>>
>
>

Neil wrote, On 2/23/09 4:16 AM:
> So....apparently I have some messages which are not RFC compliant sitting
in
> my mailboxes (mostly older ones), and I have some software which is
refusing
> to handle such messages.
> 
> 1. Does anyone know of a nice way to verify that all my messages are
> compliant/find those that aren't? (I suppose I could use the existing
> failing software, but I was hoping for something a little more robust...)
I'm not aware of any such software. Some of the ambiguities of RFC822 were 
clarified in RFC2822, but there still isn't perfect consensus on how 
strongly any software should demand compliance. That argues for using the 
failing software to identify what it deems inadequately compliant.
> 2. Does anyone know of any tools that will do The Right Thing as far as
> fixing these messages are concerned?
That's a bit of a logical problem, as many things that could be wrong are 
the absence of information, such as missing headers. If you don't know 
what's wrong with a message then obviously there's no way to fix it, but
in
some cases even knowing what is wrong does not help.
> Googling didn't turn up much for me, but maybe I wasn't hitting the
right
> terms ("RFC message repair", "fix email message",
etc.).
You might have similar results for "pi equals 4" and for the same
reasons...