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

- Forwarded message from felixs - Date: Sun, 31 Mar 2019 20:14:30 +0200 From: felixs To: Todd Zullinger Cc: mutt-users@mutt.org Subject: [Fwd: Re: Patch [was Re: [Fwd: Re: Impossible to connect to mail server via pops3 using mutt 1.11]] - Forwarded message from felixs

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

- Forwarded message from felixs - Date: Sat, 30 Mar 2019 23:52:02 +0100 From: felixs To: Todd Zullinger Cc: mutt-users@mutt.org Subject: Re: Patch [was Re: [Fwd: Re: Impossible to connect to mail server via pops3 using mutt 1.11] On Fri, Mar 29, 2019 at 03:35:28PM -0400, Todd

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

- Forwarded message from felixs - On Fri, Mar 29, 2019 at 03:43:11PM -0700, Kevin J. McCarthy wrote: > On Fri, Mar 29, 2019 at 07:57:49PM +0100, felixs wrote: > > OK, I managed to apply the patch as an email patchfile using > > > > git am /path/to/patch > > > > git log shows inclusion

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

On Fri, Mar 29, 2019 at 03:35:28PM -0400, Todd Zullinger wrote: > Hi, > > felixs wrote: > > On Thu, Mar 28, 2019 at 03:11:34PM -0700, Kevin J. McCarthy wrote: > >> 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 > >>> pas

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

On Sat, Mar 30, 2019 at 09:07:24AM +1100, Cameron Simpson wrote: > On 29Mar2019 13:05, felixs wrote: > > On Fri, Mar 29, 2019 at 08:42:33AM +1100, Cameron Simpson wrote: > > > On 28Mar2019 22:20, felixs wrote: > > > > I tried to access the branch with the patch, but the access is > > > > password

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

On Sat, Mar 30, 2019 at 09:07:24AM +1100, Cameron Simpson wrote: Therefore if your want to submit code _to_ a project it helps a great deal to have an account with the hosting web service. If, as you do, you just need access to the repo you don't normally need an account; the usual VCS clone o

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

On Fri, Mar 29, 2019 at 07:57:49PM +0100, felixs wrote: OK, I managed to apply the patch as an email patchfile using git am /path/to/patch git log shows inclusion of the patch commit. git status says that my cloned repo is +1 ahead of MASTER-ORIGIN Just to follow up, I slightly modified the

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

On 29Mar2019 13:05, felixs wrote: On Fri, Mar 29, 2019 at 08:42:33AM +1100, Cameron Simpson wrote: 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 gitl

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

On 29Mar2019 14:17, derek martin wrote: On Fri, Mar 29, 2019 at 08:42:33AM +1100, Cameron Simpson wrote: You can sign up to github without any other obligations; it is free and gets you various useful facilities. [...] There isn't actually any particular downside. Sure there is. It's yet a

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

Hi, felixs wrote: > On Thu, Mar 28, 2019 at 03:11:34PM -0700, Kevin J. McCarthy wrote: >> 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

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

On Fri, Mar 29, 2019 at 08:42:33AM +1100, Cameron Simpson wrote: > You can sign up to github without any other obligations; it is free > and gets you various useful facilities. [...] > There isn't actually any particular downside. Sure there is. It's yet another account to maintain/protect which

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

On Fri, Mar 29, 2019 at 08:57:36AM -0700, Kevin J. McCarthy wrote: > On Fri, Mar 29, 2019 at 12:48:46PM +0100, felixs wrote: > > On Thu, Mar 28, 2019 at 03:11:34PM -0700, Kevin J. McCarthy wrote: > > > The repo is clonable via , > > > which you will find under t

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

On Fri, Mar 29, 2019 at 12:48:46PM +0100, felixs wrote: On Thu, Mar 28, 2019 at 03:11:34PM -0700, Kevin J. McCarthy wrote: The repo is clonable via , which you will find under the clone button on the project details page. Yes, I did that as a first operatio

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

On Fri, Mar 29, 2019 at 08:42:33AM +1100, Cameron Simpson wrote: > 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

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

On Thu, Mar 28, 2019 at 03:11:34PM -0700, Kevin J. McCarthy wrote: > 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 > wi

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

On 29Mar2019 08:42, Cameron Simpson wrote: 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

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

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 par

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

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

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

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 m

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

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 m

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

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

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

On Sat, Mar 23, 2019 at 08:29:44PM +0800, Kevin J. McCarthy wrote: > On Sat, Mar 23, 2019 at 10:27:38AM +0100, felixs wrote: > > 'getoauthbearersupport' and 'no refresh command defined', not showing > > any willingness to download my e-mais. > > Hi felixs, > > The OAUTH support was added in

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

- Forwarded message from felixs - Date: Sun, 24 Mar 2019 12:59:35 +0100 From: felixs To: "Kevin J. McCarthy" Cc: mutt-users@mutt.org Subject: Re: Impossible to connect to mail server via pops3 using mutt 1.11 On Sat, Mar 23, 2019 at 08:29:44PM +0800, Kevin J. McCarthy wrote

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

On Sat, Mar 23, 2019 at 08:29:44PM +0800, Kevin J. McCarthy wrote: > On Sat, Mar 23, 2019 at 10:27:38AM +0100, felixs wrote: > > 'getoauthbearersupport' and 'no refresh command defined', not showing > > any willingness to download my e-mais. > > Hi felixs, > > The OAUTH support was added in vers

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

On Sat, Mar 23, 2019 at 08:29:44PM +0800, Kevin J. McCarthy wrote: On Sat, Mar 23, 2019 at 10:27:38AM +0100, felixs wrote: 'getoauthbearersupport' and 'no refresh command defined', not showing any willingness to download my e-mais. It looks like if $pop_authenticators is undefined (the defaul

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

On Sat, Mar 23, 2019 at 10:27:38AM +0100, felixs wrote: 'getoauthbearersupport' and 'no refresh command defined', not showing any willingness to download my e-mais. Hi felixs, The OAUTH support was added in version 1.11.0. Perhaps the POP implementation hasn't gotten enough testing. It lo