mirror of
https://github.com/d99kris/nmail.git
synced 2026-04-26 17:56:00 +03:00
[GH-ISSUE #12] Gmail blocking nmail for security reasons #11
Labels
No labels
bug
enhancement
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nmail#11
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Kabouik on GitHub (Jan 14, 2020).
Original GitHub issue: https://github.com/d99kris/nmail/issues/12
Originally assigned to: @d99kris on GitHub.
I don't usually use Gmail but I tried it with an old account and noticed nmail was blocked, with the following statement:
Roughly translated, it basically claims that the application I tried to use does not satisfy Gmail's security standards. They say it uses a less secured connection technology, which makes the account more vulnerable. I can force authorizing the access despite the vulnerabilities.
Is it related to certificates and SSL? IMAP and SMTP ports are set to 993 and 465 in
main.conf.In any case, it would be useful to add that in the nmail instructions because the error from nmail is not straightforward, it just says that it failed to get message ids. I had to go check the Gmail webmail to see what happened.
@d99kris commented on GitHub (Jan 14, 2020):
Hmm. That is strange. I'm using
nmailwith several Gmail accounts. Are you able to use any other email client with this Gmail account?I believe Gmail by default blocks IMAP/SMTP access, unless one enables some "unsafe access" mode (I need to look up the exact name). This applies to all IMAP/SMTP clients.
But yep, it's a good idea to add some info on this in the README. Thanks for the input!
@Kabouik commented on GitHub (Jan 14, 2020):
Actually enabling those "less secure" applications did not solve the "Get message ids failed" in nmail, so maybe I spoke too fast. However, I did receive this email on Gmail, and it coincides with when I tried setting nmail for it, not another client.
I haven't tried reading those emails in any client lately, but I did some years ago and it was working.
@Kabouik commented on GitHub (Jan 14, 2020):
It finally succeeded fetching messages after I deleted the pass in
main.confto be prompted to type it again. Weirdly enough, I am positive that the password was correct before (tried several times before noticing this "less secure apps" issue in Gmail).@d99kris commented on GitHub (Jan 16, 2020):
Ok, good to hear you got it working. I guess there is still some room for improvement on
nmailside, such as:I'll keep this issue open until I've fixed those things.
@d99kris commented on GitHub (Jan 20, 2020):
I've implemented some improvements to the UI and added some note to the README. Feel free to re-open if you have suggestions for related improvements.