Bug#283311: mutt: use_from is a bad default, but I forgot why
Point 1) On Wed, 9 Mar 2005, Marco d'Itri wrote: On Mar 09, Bernhard Kaindl [EMAIL PROTECTED] wrote: maybe there was some bug in some configuration earlyer in use_from, but as it's enabled by default in upstream and in othere GNU/Linux packagings too, the reason might have been temporary. No, it was not temporary. Nice that you know. I don't know why you think it is a bad default but you know it was not because of some bug. Again, Why? You should not insist in things you don't know anymore. Point 2) You did not wanswer to this: and also the fcc files are written without a from header. - What is your comment on that? I'd even say that that might violate some RFC about mail, because normally mail programs will assume that there is a from header in the mail, having none in a saved mail folder means lack of function to me because the mailer cannot show the From address since there is none. - And did you check that it does not violate an RFC to not send and save the From header? Again no answer from you. And what is your justification for having a different default than upstream and not even knowing why? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#283311: mutt: use_from is a bad default, but I forgot why
Package: mutt Version: 1.5.6-20040907+3 Followup-For: Bug #283311 Hi, maybe there was some bug in some configuration earlyer in use_from, but as it's enabled by default in upstream and in othere GNU/Linux packagings too, the reason might have been temporary. For example also with exim you can end up exim not having add a From header, and also the fcc files are written without a from header. I'd even say that that might violate some RFC about mail, because normally mail programs will assume that there is a from header in the mail, having none in a saved mail folder means lack of function to me because the mailer cannot show the From address since there is none. In exim, it seems to be possible to configure it so that exim requires a From: header or otherwise immediately discard the mail as spam (rightfully..) and if that is configured, it seem to affect even local users of mutt with this default config. I'd propose to ask the upstream maintainers if they have an idea, and if not I think it should be revmoved just for having the same defaults than every other mutt package. Bernhard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#283311: mutt: use_from is a bad default, but I forgot why
On Mar 09, Bernhard Kaindl [EMAIL PROTECTED] wrote: maybe there was some bug in some configuration earlyer in use_from, but as it's enabled by default in upstream and in othere GNU/Linux packagings too, the reason might have been temporary. No, it was not temporary. For example also with exim you can end up exim not having add a From header, and also the fcc files are written Maybe then exim should not be misconfigured. -- ciao, Marco signature.asc Description: Digital signature
