1 |
I have travelled exactly the same path as you, and feel all your pain. |
2 |
|
3 |
At first I used claws but after a few months it got unbearably slow when |
4 |
dealing with calendars and invites, so I switched to Thunderbird. It |
5 |
works well enough for me. |
6 |
|
7 |
Let's first establish your needs, I see a few points that don't make |
8 |
much real-world sense. |
9 |
|
10 |
You retrieve your mail from Gmail, and then selectively delete stuff |
11 |
from Google's servers. Why are you doing that? Gmail is built to archive |
12 |
everything forever and most people's mail quickly gets to be a lot of |
13 |
mail. I can understand leaving all of it there in an archive, or |
14 |
deleting all of it, depending on how you like to do your backups, but I |
15 |
don't understand the selective delete part. Looks like a lot of manual |
16 |
work on your part. |
17 |
|
18 |
I wouldn't try using mail clients to directly access the same local |
19 |
mailbox structure. No two clients work the same way, they all index |
20 |
mails differently, other subtle differences exist and there's always |
21 |
locking issues. Mutt and kmail might not respect each other's turf... |
22 |
|
23 |
I recommend a man in the middle - a local IMAP serve of your choice that |
24 |
works fast for you and stores mail acceptably for you. Fetch your mail |
25 |
using fetchmail or one of it's friends, use procmail to filter it and |
26 |
feed it into your IMAP server, and connect to IMAP locally using any GUI |
27 |
mail client you choose. This gives you a standard interface (IMAP) |
28 |
instead of a weird interface (disk files store wherever however) and all |
29 |
locking issues just go away. |
30 |
|
31 |
The above is what I did (and delete everything off Google's servers so I |
32 |
do my own backups), and it makes most of the rest of your post redundant |
33 |
and no longer apply. |
34 |
|
35 |
|
36 |
On 27/05/2013 14:49, Mick wrote: |
37 |
> I would be grateful if some kind soul guided my hand on configuring mutt to |
38 |
> behave like ... errm ... kmail! O_o |
39 |
> |
40 |
> Before you have a go, please let me explain myself. I love kmail, or better |
41 |
> said, I *used to* love kmail as it was back then when no semantic desktop, no |
42 |
> mysql database, no akonadi, no redland and what not, was imposed upon us. I |
43 |
> have no need for anything else than what kmail used to do back in the latter |
44 |
> part of KDE3. A simple flat file address book (OK, use sqlite if you really |
45 |
> must) and the simple search for messages it used to offer, was all that I ever |
46 |
> needed. In particular I found its integration with kgpg and kleopatra |
47 |
> extremely useful, and this is what has stopped me moving to other GUI mail |
48 |
> clients. I tried many of them was surprised to see how much better kmail was |
49 |
> for my needs. |
50 |
> |
51 |
> Anyway, this was back then. Now kmail 1 is heading towards extinction and it |
52 |
> is a matter of time before devs pull the plug and push us all to the kmail 2 |
53 |
> abomination. Since the full KDEPIM semantic bloatware is not to my liking and |
54 |
> I do not wish to allow kmail 2 to irreversibly lose my thousands of mail |
55 |
> messages, I thought of giving mutt a closer look. I had used mutt on and off |
56 |
> in a simple IMAP set up. Now however I would like to use it on my laptop, |
57 |
> with the need for offline access to read and draft/edit my messages, multiple |
58 |
> accounts and quirky settings. There are a number of things that feel awkward |
59 |
> with mutt and I am not sure if this is because mutt is just not for me, or |
60 |
> because it takes much more effort to configure functions, which on a modern |
61 |
> GUI client are just a click away. |
62 |
> |
63 |
> So, let me start with the basics. I am using Gmail, for which I have |
64 |
> configured kmail to POP and download my messages in a local maildir without |
65 |
> deleting these from the server. The Gmail settings on the server show: |
66 |
> |
67 |
> POP enabled |
68 |
> Leave POPped messages on server |
69 |
> IMAP enabled |
70 |
> |
71 |
> With the above settings (not sure if they veer from the original Gmail |
72 |
> defaults) I am able to POP the Gmail server inbox and rather importantly I'm |
73 |
> also able to 'sync' with any sent messages on the server. I will not pretend |
74 |
> to understand how the latter is performed - haven't sniffed the packets to see |
75 |
> what happens - but this is what I get: |
76 |
> |
77 |
> - When I send a message from kmail it will be saved in my local maildir sent |
78 |
> gmail subfolder and will also show up in the Sent folder of the Gmail webmail. |
79 |
> |
80 |
> - When I send a message from the Gmail webmail the message will show up as |
81 |
> new (and downloaded if I click on it) when I launch my kmail. |
82 |
> |
83 |
> - This sync'ing happens once only. If I thereafter delete a message on the |
84 |
> server the local copy is not affected and vice versa. This is useful for me |
85 |
> because I can delete locally any messages which are not particularly |
86 |
> important, but might want to refer to them in the distant future. Delete |
87 |
> messages on the server that I only want to keep locally. Delete both when I |
88 |
> don't want to keep them whatsoever. |
89 |
> |
90 |
> However, I am at a loss as to how I should configure my .muttrc to achieve |
91 |
> this functionality. Ideally I would also like to replicate my current kmail |
92 |
> maildir folder structure in mutt, so that I can access the Gmail server with |
93 |
> either client; e.g. |
94 |
> |
95 |
> ~/Mail/ |
96 |
> |_inbox (all unfiltered messages drop in here) |
97 |
> |_.inbox.directory |
98 |
> |_.Gentoo.directory |
99 |
> |_Gentoo |
100 |
> |_cur |
101 |
> |_new |
102 |
> |_tmp |
103 |
> |
104 |
> |
105 |
> Can you please point me in the right direction for this set up? |
106 |
> |
107 |
|
108 |
|
109 |
-- |
110 |
Alan McKinnon |
111 |
alan.mckinnon@×××××.com |