Accessing the body a message programatically
Hello, I need to extract some information from a message that is shown in notmuch-mode, and I was able to easily get the from and subject of the message. I now need to use the body, but I cannot find how to get it. I assume I should use notmuch-get-bodypart-text, but I don't know how to obtain the msg or part argument. In addition, can I get access to the List-Archive header? I could do it by spawning an external process to get the raw message, but it seems a bit heavy handed. Thanks, Alan signature.asc Description: PGP signature ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Syncing of IMAP accounts
Hi, I am using offlineimap to sync my email for use with notmuch. As far as I know, offlineimap supports Python 2.7 only and since Python 2.7 will EOL in about 2 weeks I am looking for a replacement. Does anyone have a suggestion? Thanks! Nick ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Google Mail
I just received an email from Google saying that they will stop supporting username/password authentication for protocols like IMAP in June 15, 2020. Or maybe February 15, 2021, I am a bit unclear here. Curiously, POP isn't mentioned, I assume it will be affected too. Presumably this means Application Specific Passwords will stop working, although that term isn't mentioned once in the email. I believe SMTP should continue working. Are there any alternatives to fetching mail with something like fetchmail that support Google's OAuth? Or maybe I should switch email providers to one that is actually friendly to open source software (unfortunately not always on option, e.g. for work email). === cut === G Suite logo Beginning June 15, 2020, non-Google apps that use only a password to access Google accounts will no longer be supported. Starting February 15, 2021, G Suite accounts will only allow access to apps using OAuth. Password-based access will no longer be supported. Dear Administrator, We're constantly working to improve the security of your organization's Google accounts. As part of this effort, and in consideration of the current threat landscape, we'll be turning off access to less secure apps (LSA) — non-Google apps that can access your Google account with only a username and password, without requiring any additional verification steps. Access through only a username and password makes your account more vulnerable to hijacking attempts. Moving forward, only apps that support a more modern and secure access method called OAuth will be able to access your G Suite account. Access to LSAs will be turned off in two stages: June 15, 2020 - Users who try to connect to an LSA for the first time will no longer be able to do so. This includes third-party apps that allow password-only access to Google calendars, contacts, and email via protocols such as CalDAV, CardDAV and IMAP. Users who have connected to LSAs prior to this date will be able to continue using them until usage of all LSAs is turned off. February 15, 2021 - Access to LSAs will be turned off for all G Suite accounts. What do I need to do? To continue using a specific app with your G Suite accounts, users in your organization must switch to a more secure type of access called OAuth. This connection method allows apps to access accounts with a digital key instead of requiring a user to reveal their username and password. We recommend that you share the user instructions (included below) with individuals in your organization to help them make the necessary changes. Alternatively, if your organization is using custom tools, you can ask the developer of the tool to update it to use OAuth. Developer instructions are also included below. MDM configuration If your organization uses a mobile device management (MDM) provider to configure CalDAV, CardDAV, and Exchange ActiveSync (Google Sync) profiles, these services will be phased out according to the timeline below: June 15, 2020 - MDM push of IMAP, CalDAV, CardDAV, and Exchange ActiveSync (Google Sync) will no longer work for new users. February 15, 2021 - MDM push of IMAP, CalDAV, CardDAV, and Exchange ActiveSync (Google Sync) will no longer work for existing users. Admins will need to push a Google Account using their MDM provider, which will re-add their Google accounts to iOS devices using OAuth. Other less secure apps For any other LSA, ask the developer of the app you are using to start supporting OAuth. If you use other apps on iOS or MacOS that access your G Suite account information through only a password, most access issues can be resolved by removing then re-adding your account. When you add it back, make sure to select Google as the account type to automatically use OAuth. Scanners and other devices No change is required for scanners or other devices using simple mail transfer protocol (SMTP) or LSAs to send emails. If you replace your device, look for one that sends email using OAuth. User instructions If you are using an app that accesses your Google account with only a username and password, take one of the following actions to switch to a more secure method and continue to access your email, calendar, or contacts. If you do not take one of the following actions, when LSA access is discontinued after February 15, 2021, you will begin receiving an error message that your username-password combination is incorrect. Email If you are using stand-alone Outlook 2016 or earlier, move to Office 365 (a web-based version of Outlook) or Outlook 2019, both of which support OAuth access. Alternatively you can use G Suite Sync for Microsoft Outlook. If you are using Thunderbird or another email client, re-add your Google Account and configure it to use IMAP with OAuth. If you are using the mail app on iOS or MacOS, or Outlook for Mac, and use only a password to login, you'll need to remove a
Re: Syncing of IMAP accounts
* Nicolas Bock: > I am using offlineimap to sync my email for use with notmuch. Try muchsync (http://www.muchsync.org) instead. -Ralph ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: Syncing of IMAP accounts
Thanks, I will! On Mon, Dec 16, 2019 at 2:47 PM Ralph Seichter wrote: > > * Nicolas Bock: > > > I am using offlineimap to sync my email for use with notmuch. > > Try muchsync (http://www.muchsync.org) instead. > > -Ralph > ___ > notmuch mailing list > notmuch@notmuchmail.org > https://notmuchmail.org/mailman/listinfo/notmuch ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: Syncing of IMAP accounts
Nicolas Bock writes: > As far as I know, offlineimap supports Python 2.7 only and since > Python 2.7 will EOL in about 2 weeks I am looking for a > replacement. Does anyone have a suggestion? I've been using mbsync (also known as isync) for several months and it is fast and feels incredibly solid. There are debian and fedora packages (search on "isync"). ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: Syncing of IMAP accounts
Thanks Ryan! I'll check that out too! On 12/16/19 3:03 PM, Ryan Tate wrote: Nicolas Bock writes: As far as I know, offlineimap supports Python 2.7 only and since Python 2.7 will EOL in about 2 weeks I am looking for a replacement. Does anyone have a suggestion? I've been using mbsync (also known as isync) for several months and it is fast and feels incredibly solid. There are debian and fedora packages (search on "isync"). ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Attach public key and encrypt by default
I have two feature requests/questions for notmuch-emacs? One would it be possible to add or configure in support for automatically adding your gpg public key to messages? Second, could there be a feature that checks if there's a gpg key for the recipient of a message and if there is, turn on encryption by default? Thanks! -/-\-/-\-/- Carolyn "Lynn" Knight-Serrano [xe/xem/xyr/xemself] 🔐PGP Fingerprint: 0xf02b733b4382e451c8c2fff550858748146544cb 🕸Fediverse: @gigavinyl@catgirl.science ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: Accessing the body a message programatically
Alan Schmitt writes:
> Hello,
>
> I need to extract some information from a message that is shown in
> notmuch-mode, and I was able to easily get the from and subject of the
> message. I now need to use the body, but I cannot find how to get it. I
> assume I should use notmuch-get-bodypart-text, but I don't know how to
> obtain the msg or part argument.
>
If you mean interactively for a currently displayed message, have a look
at the function notmuch-show-current-part-handle, and the way it uses
notmuch-show-get-{message,part}-properties.
> In addition, can I get access to the List-Archive header? I could do it
> by spawning an external process to get the raw message, but it seems a
> bit heavy handed.
there is a couple of patches by Johan Parin currently under review
to provide a configurable set of headers. You can find them via
https://nmbug.notmuchmail.org/status/#Review
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch
Re: Attach public key and encrypt by default
Oh! I figured out how to encrypt by default. I still can't figure out how to attach my public key by default though. On December 16, 2019 10:57:12 PM UTC, "Carolyn "Lynn" Knight-Serrano" wrote: >I have two feature requests/questions for notmuch-emacs? One would it >be possible to add or configure in support for automatically adding >your gpg public key to messages? Second, could there be a feature that >checks if there's a gpg key for the recipient of a message and if there >is, turn on encryption by default? Thanks! >-/-\-/-\-/- > >Carolyn "Lynn" Knight-Serrano [xe/xem/xyr/xemself] > >🔐PGP Fingerprint: 0xf02b733b4382e451c8c2fff550858748146544cb > >🕸Fediverse: @gigavinyl@catgirl.science >___ >notmuch mailing list >notmuch@notmuchmail.org >https://notmuchmail.org/mailman/listinfo/notmuch -/-\-/-\-/- Carolyn "Lynn" Knight-Serrano [xe/xem/xyr/xemself] 🔐PGP Fingerprint: 0xf02b733b4382e451c8c2fff550858748146544cb 🕸Fediverse: @gigavinyl@catgirl.science ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: Attach public key and encrypt by default
Two ideas: echo “-- “ > ~/.signature gpg -a -e $USER >> !$ This is hardly polite, but at least the signature will be stripped off by many archives and replies. Alternatively, (add-hook ‘message-setup-hook (lambda () (mml-attach-file “path/to/pubkey.gpg”)) But this still puts kilobytes of useless crud on every message. Please don’t. Maybe a URL to your key in your signature would be enough? -- Brian Sniffen > On Dec 16, 2019, at 10:52 PM, Carolyn Lynn Knight-Serrano > wrote: > > Oh! I figured out how to encrypt by default. I still can't figure out how to > attach my public key by default though. > >> On December 16, 2019 10:57:12 PM UTC, "Carolyn "Lynn" Knight-Serrano" >> wrote: >> I have two feature requests/questions for notmuch-emacs? One would it >> be possible to add or configure in support for automatically adding >> your gpg public key to messages? Second, could there be a feature that >> checks if there's a gpg key for the recipient of a message and if there >> is, turn on encryption by default? Thanks! >> -/-\-/-\-/- >> >> Carolyn "Lynn" Knight-Serrano [xe/xem/xyr/xemself] >> >> 🔐PGP Fingerprint: 0xf02b733b4382e451c8c2fff550858748146544cb >> >> 🕸Fediverse: @gigavinyl@catgirl.science >> ___ >> notmuch mailing list >> notmuch@notmuchmail.org >> https://notmuchmail.org/mailman/listinfo/notmuch > > -/-\-/-\-/- > > Carolyn "Lynn" Knight-Serrano [xe/xem/xyr/xemself] > > 🔐PGP Fingerprint: 0xf02b733b4382e451c8c2fff550858748146544cb > > 🕸Fediverse: @gigavinyl@catgirl.science > ___ > notmuch mailing list > notmuch@notmuchmail.org > https://notmuchmail.org/mailman/listinfo/notmuch ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
