Re: mutt and icloud

[felixs]

On Thu, Mar 28, 2019 at 10:20:07AM -0400, Jude DaShiell wrote:
> Have we got any mutt users now able to get full access to their icloud
> accounts and are also able to send with mutt through their icloud
> accounts?  I'm interested in this and so is another contact who got shot
> down on another list for having sent an off topic post concerning mutt.
> 
I still do some (ongoing) testing to use mutt with my icloud account,
i.e. with googlemailapis.com, but after discarding oauth2 use for accessing
the scope mail.google.com, I decided to make a break before
continuing my testing with my cloud account.
I will keep you and the list informed.

felixs
> 

Re: [Fwd: Re: Impossible to connect to mail server via pops3 using mutt 1.11]

[Kevin J. McCarthy]

On Thu, Mar 28, 2019 at 10:20:54PM +0100, felixs wrote:

I tried to access the branch with the patch, but the access is
password-protected.


The repo is clonable via , which 
you will find under the clone button on the project details page.


If you open a particular commit, the options button has "Email patches" 
and "Plain diff" views.  So, for example the commit in question is 
available via 
 
and 



However, I was still thinking about making one more change the commit so 
behavior remains the same as before when you has $pop_auth_try_all 
unset.  For now, you're welcome to try the patch with that variable set.


--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA


signature.asc
Description: PGP signature

github (was: [Fwd: Re: Impossible to connect to mail server via pops3 using mutt 1.11])

[Cameron Simpson]

On 28Mar2019 22:20, felixs  wrote:

I tried to access the branch with the patch, but the access is
password-protected. Are you able to share the patchfile by other means?
Signing up with gitlab is another option, but I'd need some more time to
decide on whether it's the right choice for me.


You can sign up to github without any other obligations; it is free and 
gets you various useful facilities.


For example, my own code is published on bitbucket, but I have a github 
account in order to interoperate with various projects.


There isn't actually any particular downside.

Cheers,
Cameron Simpson 

Re: [Fwd: Re: Impossible to connect to mail server via pops3 using mutt 1.11]

[felixs]

On Wed, Mar 27, 2019 at 09:18:22AM -0700, Kevin J. McCarthy wrote:
> On Wed, Mar 27, 2019 at 04:54:04PM +0100, felixs wrote:
> > Having studied oauth2 more in depth I do not consider it to be secure
> > enough (as such) mainly because of its overwhelming complexity, and I will 
> > NOT use it for mail purposes.
> 
> Thanks for the update felixs.  I've just returned from overseas so my
> schedule is a bit full, but as soon as I can I will fix up and push the
> patch into stable.
> 
Hi Kevin,

I tried to access the branch with the patch, but the access is
password-protected. Are you able to share the patchfile by other means?
Signing up with gitlab is another option, but I'd need some more time to
decide on whether it's the right choice for me.
Could you email it as a patchfile?

Thanks in advance.

felixs

Re: Saving sent e-mails in INBOX for better threading?

[Gregor Zattler]

Hi Max,
* Max Görner  [2019-03-28; 13:24]:
> I wonder whether one could just configure mutt such as to save all send
> messages to Inbox again. Of course, that would clutter the inbox severely, but
>
>   a) I have a hook limiting the view to ~(~N|~F) already
>   b) the cluttering might be counteracted by Mutt's threading capabilities.
>
> Could some readers of this list please share their opinion/experiences with
> me? I am tempted to just try out, but I am also a bit afraid of bad
> consequences.

I do this since years and would not want handle email without.
It's so much easier to follow a thread if all messages are in the
same folder.

I send every email to me via Bcc: the incoming Bcc: copy is
handled by the same procmail scripts as all email and therefore
the email will go in the same folder(s).  Admittedly I get
duplicates this way, but I use procmail also as a duplicate
filter an anyway mutt is great in searching/deletung duplicates
too.


Ciao; Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-

Re: Saving sent e-mails in INBOX for better threading?

[Dave Woodfall]

On Thursday 28 March 2019 13:24,
Max Görner  put forth the proposition:
> Hello,
>
> I am a very pleased Mutt user for several years now. However, I would love to
> have a threading similar to GMail, showing send and received messages in the
> same thread.
>
> I wonder whether one could just configure mutt such as to save all send
> messages to Inbox again. Of course, that would clutter the inbox severely, but
>
>  a) I have a hook limiting the view to ~(~N|~F) already
>  b) the cluttering might be counteracted by Mutt's threading capabilities.
>
> Could some readers of this list please share their opinion/experiences with
> me? I am tempted to just try out, but I am also a bit afraid of bad
> consequences.

The way I do this is to set record=^ in ~/.muttrc so it saves in the
same folder that the message was created and sent from:

set record=^

And a hook which also has the setting in the sourced file:

folder-hook .* source ~/.mutt/default

Then I have other hooks when I want to use a different folder -
mailing list messages get saved in =Sent, since the original message
will go to the list folder anyway:

folder-hook =Lists/* source ~/.mutt/listhook

Containing:

set record="=Sent"

That way I can have things in various folders for family, friends
etc.

Best,

Dave

>
> Sincerely
>
> Max Görner




--

All I ask of life is a constant and exaggerated sense of my own
importance.

Re: Saving sent e-mails in INBOX for better threading?

[Ben Boeckel]

On Thu, Mar 28, 2019 at 13:24:22 +0100, Max Görner wrote:
> I am a very pleased Mutt user for several years now. However, I would love to
> have a threading similar to GMail, showing send and received messages in the
> same thread.

Well, GMail and Mutt threading is different. Mutt uses Message-Id and
In-Reply-To headers. GMail guesses and does heuristics (personally, I
find it far inferior).

> I wonder whether one could just configure mutt such as to save all send
> messages to Inbox again. Of course, that would clutter the inbox severely, but

I do this with:

set record = '=acct/INBOX'

which saves outgoing messages to the account's INBOX. You can use
`folder-hook` to reset the variable based on which account you're in.

--Ben

mutt and icloud

[Jude DaShiell]

Have we got any mutt users now able to get full access to their icloud
accounts and are also able to send with mutt through their icloud
accounts?  I'm interested in this and so is another contact who got shot
down on another list for having sent an off topic post concerning mutt.



--

Re: Saving sent e-mails in INBOX for better threading?

[Jens John]

On Thu, 28 Mar 2019, at 13:32, Max Görner wrote:
> Could some readers of this list please share their opinion/experiences with
> me?

As someone who is only using mutt's threaded view, it's terrific and achieves 
exactly the behaviour I want from a mail client. mutt's way of displaying 
threads -- at least with Unicode characters -- also looks very tidy. 
Collapsing, splitting, merging threads is also a very convenient feature to 
have, especially in cases where the conversation partner or software breaks 
threading by applying worst practices on every occasion.

An issue is that when using multiple email clients, online IMAP must be used 
for all mailboxes (which I don't like -- I like to only pull IMAP to my local 
machine, which is the authoritative copy, and not push; also, I don't sync IMAP 
deletions from the server) OR you could just do it like I do, I BCC all 
outgoing emails to myself so I can have the same consistent inbox view from 
everywhere.

Multiple clients in my case means: mutt at home with isync (pull only), webmail 
from everywhere else.

Saving sent e-mails in INBOX for better threading?

[Max Görner]

Hello,

I am a very pleased Mutt user for several years now. However, I would love to
have a threading similar to GMail, showing send and received messages in the
same thread.

I wonder whether one could just configure mutt such as to save all send
messages to Inbox again. Of course, that would clutter the inbox severely, but

 a) I have a hook limiting the view to ~(~N|~F) already
 b) the cluttering might be counteracted by Mutt's threading capabilities.

Could some readers of this list please share their opinion/experiences with
me? I am tempted to just try out, but I am also a bit afraid of bad
consequences.


Sincerely

Max Görner


signature.asc
Description: PGP signature

Re: [Fwd: Re: Impossible to connect to mail server via pops3 using mutt 1.11]

[felixs]

On Wed, Mar 27, 2019 at 09:18:22AM -0700, Kevin J. McCarthy wrote:
> On Wed, Mar 27, 2019 at 04:54:04PM +0100, felixs wrote:
> > Having studied oauth2 more in depth I do not consider it to be secure
> > enough (as such) mainly because of its overwhelming complexity, and I will 
> > NOT use it for mail purposes.
> 
> Thanks for the update felixs.  I've just returned from overseas so my
> schedule is a bit full, but as soon as I can I will fix up and push the
> patch into stable.
> 
OK, I cloned the git repository and will do some testing with the patch.
I hope I'll be fast enough to get it done before you are about to commit
it. I already have encountered some problems to 'make' the manual, but
without problems/errors it would be somewhat boring. ;-)  
As I was used to subversion I am quite a beginner in using git.

Best regards

felixs