Re: [fetchmail-devel] Re: [fetchmail-users] Incorrect header line and lost mails

[Frederic M. <fre...@wo...>]

Rob MacGregor wrote:
> On 2/14/06, Frederic Marchal <fre...@wo...> wrote:
>   
>> I believe it is not fetchmail's job to enforce rfc822 that way. It
>> should be left to a program dedicated to that task or, at least, it
>> should not be the default option. It would be a good idea to tag the
>> mail with a specific header though. It would make it easier to filter
>> out with a program such as procmail. I wouldn't divert the mail to the
>> postmaster either. It is likely that a busy postmaster will throw it
>> away without looking at it if he is not the obvious recipient.
>>     
>
> However, the postmaster defined by fetchmail doesn't have to be The
> Postmaster.  Of course, there's nothing to say that the option can't
> both have a global setting and a per-user override.
>   
In my case, that account (which is not The Postmaster) received 82 mails
for the last 6 hours and they ended up at the secretary that must deal
with 80% of spam from various addresses every day. I double check that
account from time to time and I salvage a few mails every month. Sending
a mail to an account where the user spend most of his/her time deleting
spams is unreliable at best :-).

With the limited experience I gained from our small particular net, I
think it is best to let the mail go unchanged if fetchmail can extract
enough information to determine the next route. It could also add a
valid X-Envelope-To if none was found but, as you said in a previous
post, anything beyond that would be risky...

Now, other e-mail processing configurations may have requirements I
don't see. So, feel free to tell me about it. It would help me to have a
clear picture of what fetchmail must deal with if I start changing the
code, preferably before I do it :-).

Frederic