severity 701093 wishlist tags 701093 = wontfix thanks On Thu, Feb 28, 2013 at 02:19:19PM +0100, Andrew Shadura wrote: > Control: retitle -1 claws-mail: don't generate/rely on non-standard > headers when sending messages > > Hello, > > On 28 February 2013 13:59, Andrew Shadura <bugzi...@tut.by> wrote: > >> So you're trying to re-send without making the server reachable again > >> and expect it to succeed? Is this a joke? :-P > > > Erm, it seems like you're joking. Of course I meant it's reachable > > again, but, well, either I have it reachable or not, Claws *must* try > > to deliver it, and it doesn't, and the network log shows, and the > > message I get confirms that. > > > Do you really want me to dig into the code? If I was you I'd not dare > > to let me do that :D > > Okay, it seems like I understand what's going on. I use IMAP mailbox, > and the server filters out all those special non-standard Claws mail > headers. I see no real reason to use them at all, as this information > can be found in standard RFC headers which already exist in the > message. Please don't rely on them.
The standard headers doesn't have the details saved in the special header. Have you seen them? Anyway the server must not remove headers sent by the client unless they have invalid data (8-bit data) which is not the case. Which IMAP server is that which removes client data without warning or error? There's no place in the RFCs (3501/2600) that allows that kind of server behaviour, so it's either a bug or a stupid feature of that server. But clearly not a claws-mail bug. Since you have changed the title I guess you don't want to close this report, which has become a feature request in fact, so tagging accordingly. regards, -- Ricardo Mones ~ bash: ./signature: No such file or directory /bin/bash
signature.asc
Description: Digital signature
