Hi, On Thu, Feb 28, 2013 at 03:55:07PM +0100, Andrew Shadura wrote: > Hello. > > On 28 February 2013 15:16, Ricardo Mones <[email protected]> wrote: > >> > 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? > > What extra details do you need to send the message apart from From: > and To:? That should be perfectly enough to send a message. There's > absolutely no reason to refuse sending a message which doesn't have > Claws special headers.
There's account configurations for things like where to put account's sent messages or if messages have to be digitally signed, and more. That information cannot be extracted from To or From. That info is required for claws-mail to work properly, and there's no reason for the server to remove it. > > 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? > > This is what I have and I have no option to change the server > behaviour. No other mail client is affected by this behaviour, so this > is a fault of Claws Mail. No, that you can't change the server which is violating the IMAP standards doesn't make it a client problem :) The other servers out there had never such problem. In any case, you can put your drafts in a local folder instead of server's and the problem should be fixed. Of course, this has drawbacks if you use different computers. > > 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. > > I'd like it to be fixed, however. When the message is still in Drafts, > it doesn't have any special headers. There's no reason to refuse to > send it, as I said before. Yes, there is, as explained above. If the local folder drafts workaround doesn't work for you the only thing I can recommend is to try other mail clients in Debian and see if they work better with that ugly server. regards, -- Ricardo Mones ~ You have the capacity to learn from mistakes. You'll learn a lot today. /usr/games/fortune
signature.asc
Description: Digital signature
