Re: [PATCH] emacs: don't start processes stopped
Steven Allen writes: > It causes this function to fail with: > > let: Wrong type argument: null, t > > Support for this was removed from Emacs in April > 2019 (5c5e309527e6b582e2c04b83e7af45f3144863ac) because it never > worked correctly (apparently). pushed d ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: [PATCH v2] legacy-display: accept text/plain legacy display parts
Daniel Kahn Gillmor writes: > https://www.ietf.org/id/draft-autocrypt-lamps-protected-headers-02.html > Makes it clear that the "Legacy Display" part of an encrypted message > with protected headers can (and indeed, should) be of content-type > text/plain, though some clients still generate the Legacy Display part > as content-type text/rfc822-headers. Notmuch should recognize the > part whichever of the two content-types it uses. pushed, d ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: [PATCH 2/2] legacy-display: drop tests that try to match headers in a Legacy Display part
Daniel Kahn Gillmor writes: > These tests were an attempt to establish that the content of the > "Legacy Display" part is the same as the actual protected headers of > the message. But this is more conservative than we need to be. pushed. d ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: [PATCH] debian: Add packaging for python3-notmuch2
On Mon 2019-12-23 17:17:22 -0500, Daniel Kahn Gillmor wrote:
> Ship a new debian package for the notmuch2 CFFI-based Python interface
> to notmuch.
>
> Unlike the notmuch python module, the new notmuch2 module is no longer
> arch-independent, because it builds and ships a shared object in
> addition to the python code.
>
> This patch encourages new downstream development to rely on notmuch2
> instead of on notmuch, to get the benefits of the new module.
>
> I welcome any suggested improvements to this packaging, but it appears
> to me to be sufficient to get "import notmuch2" to work and do some
> basic tests.
> ---
> debian/control | 24 +++-
> debian/rules | 11 ++-
> 2 files changed, 29 insertions(+), 6 deletions(-)
>
> diff --git a/debian/control b/debian/control
> index fb2b31c1..a1371fc8 100644
> --- a/debian/control
> +++ b/debian/control
> @@ -98,6 +98,25 @@ Depends:
> libnotmuch5 (>= ${source:Version}),
> ${misc:Depends},
> ${python3:Depends},
> +Description: Python 3 legacy interface to the notmuch mail search and index
> library
> + Notmuch is a system for indexing, searching, reading, and tagging
> + large collections of email messages in maildir or mh format. It uses
> + the Xapian library to provide fast, full-text search with a very
> + convenient search syntax.
> + .
> + This package provides a legacy Python 3 interface to the notmuch
> + functionality, directly interfacing with a shared notmuch library.
> + .
> + New projects are encouraged to use python3-notmuch2 instead.
> +
> +Package: python3-notmuch2
> +Architecture: any
> +Section: python
> +Depends:
> + libnotmuch5 (>= ${source:Version}),
> + ${misc:Depends},
> + ${python3:Depends},
> + ${shlibs:Depends},
> Description: Python 3 interface to the notmuch mail search and index library
> Notmuch is a system for indexing, searching, reading, and tagging
> large collections of email messages in maildir or mh format. It uses
> @@ -105,7 +124,10 @@ Description: Python 3 interface to the notmuch mail
> search and index library
> convenient search syntax.
> .
> This package provides a Python 3 interface to the notmuch
> - functionality, directly interfacing with a shared notmuch library.
> + functionality using CFFI bindings, which interface with a shared
> + notmuch library.
> + .
> + This is the preferred way to use notmuch via Python.
>
> Package: ruby-notmuch
> Architecture: any
> diff --git a/debian/rules b/debian/rules
> index bf9d0bbd..8de49d0f 100755
> --- a/debian/rules
> +++ b/debian/rules
> @@ -1,7 +1,5 @@
> #!/usr/bin/make -f
>
> -export PYBUILD_NAME=notmuch
> -
> export DEB_BUILD_MAINT_OPTIONS = hardening=+all
>
> %:
> @@ -19,17 +17,20 @@ override_dh_auto_configure:
>
> override_dh_auto_build:
> dh_auto_build -- V=1
> - dh_auto_build --buildsystem=pybuild --sourcedirectory bindings/python
> + PYBUILD_NAME=notmuch dh_auto_build --buildsystem=pybuild
> --sourcedirectory bindings/python
> + PYBUILD_NAME=notmuch2 dh_auto_build --buildsystem=pybuild
> --sourcedirectory bindings/python-cffi
> $(MAKE) -C contrib/notmuch-mutt
>
> override_dh_auto_clean:
> dh_auto_clean
> - dh_auto_clean --buildsystem=pybuild --sourcedirectory bindings/python
> + PYBUILD_NAME=notmuch dh_auto_clean --buildsystem=pybuild
> --sourcedirectory bindings/python
> + PYBUILD_NAME=notmuch2 dh_auto_clean --buildsystem=pybuild
> --sourcedirectory bindings/python-cffi
> dh_auto_clean --sourcedirectory bindings/ruby
> $(MAKE) -C contrib/notmuch-mutt clean
>
> override_dh_auto_install:
> dh_auto_install
> - dh_auto_install --buildsystem=pybuild --sourcedirectory bindings/python
> + PYBUILD_NAME=notmuch dh_auto_install --buildsystem=pybuild
> --sourcedirectory bindings/python
> + PYBUILD_NAME=notmuch2 dh_auto_install --buildsystem=pybuild
> --sourcedirectory bindings/python-cffi
> $(MAKE) -C contrib/notmuch-mutt DESTDIR=$(CURDIR)/debian/tmp install
> dh_auto_install --sourcedirectory bindings/ruby
> --
Pinging on this patch as well. If we want the notmuch2 python module to
be used, we need to get it in wider distribution. having it installable
via "apt install python3-notmuch2" would be a good start.
Note that making this change means that the notmuch package will pass
through the NEW queue, which can take longer than we might like,
depending on the Debian FTP team's available time. I see this as an
argument for making this change earlier, rather than later, though, so
that the NEW queue doesn't trip us up if we have a more urgent change we
want to see made later.
--dkg
signature.asc
Description: PGP signature
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch
Re: [PATCH] debian: add Build-Depends-Package for libnotmuch5.symbols
On Mon 2019-12-23 15:14:38 -0500, Daniel Kahn Gillmor wrote: > See lintian informational tag > symbols-file-missing-build-depends-package-field for hints about this > minor metadata update. > > Signed-off-by: Daniel Kahn Gillmor > --- > debian/libnotmuch5.symbols | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/debian/libnotmuch5.symbols b/debian/libnotmuch5.symbols > index 308567b8..2ae73dad 100644 > --- a/debian/libnotmuch5.symbols > +++ b/debian/libnotmuch5.symbols > @@ -1,4 +1,5 @@ > libnotmuch.so.5 libnotmuch5 #MINVER# > +* Build-Depends-Package: libnotmuch-dev > notmuch_built_with@Base 0.23~rc0 > notmuch_config_list_destroy@Base 0.23~rc0 > notmuch_config_list_key@Base 0.23~rc0 > -- Ping on this patch. it should be unobjectionable, but i'd appreciate a review! --dkg signature.asc Description: PGP signature ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: Working with 2FA-enabled mail (app password not possible)
Chris Coutinho writes: > My company recently made our Office365 mail service 2FA-enabled by > default and disallowed app-specific passwords. Before this, I used > Offlineimap to download my mail and index/search it using Notmuch. Now > that that's no longer possible, I'm looking to the community for > options. > > What do you use for syncing your mail to your local system(s) and > utilizing the power of Notmuch? Hmm. Wonder if this is the real reason IMAP suddenly stopped working for me on my work Office365 domain after updating my password. Although it does work for some people. Weird. OAuth is the solution for Google, and I suspect OAuth may be the solution for Microsoft too. If so, you need a program that supports IMAP using OAuth. gemail supports Google OAuth, I suspect it might be possible to get it to work with Microsoft too. However I don't know anything about how to register the Oauth app with Microsoft. http://www.bytereef.org/howto/oauth2/getmail.html Apparently OfflineIMAP also supports Oauth. Another option might be davmail. https://sourceforge.net/p/davmail/bugs/717/ -- Brian May https://linuxpenguins.xyz/brian/ ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Working with 2FA-enabled mail (app password not possible)
Hi, My company recently made our Office365 mail service 2FA-enabled by default and disallowed app-specific passwords. Before this, I used Offlineimap to download my mail and index/search it using Notmuch. Now that that's no longer possible, I'm looking to the community for options. What do you use for syncing your mail to your local system(s) and utilizing the power of Notmuch? Thanks in advance, Chris ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: email recipient not taken into account when replying?
On Wed, Jan 08 2020, Alan Schmitt wrote: > Is there another way to tell notmuch to use as From address the address > the email was sent to, if it's one of my emails? Yes. The user.other_email configuration entry should do that. For example, in ~/.notmuch-config: [user] name=Alan Schmitt primary_email=alan.schm...@polytechnique.org other_email=alan.schm...@inria.fr,alan.schm...@irisa.fr,presid...@lemondedujeu.org" -Carl signature.asc Description: PGP signature ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
email recipient not taken into account when replying?
Hello,
I sometimes receive some emails at the address
presid...@lemondedujeu.org. This email is declared as part of my
alternate emails (I do not consider this private information so I'm
posting it):
(setq message-alternative-emails
(regexp-opt '("alan.schm...@polytechnique.org"
"alan.schm...@inria.fr"
"alan.schm...@irisa.fr"
"presid...@lemondedujeu.org")))
When I reply in emacs, notmuch uses my email in polytechnique.org. The
surprising thing is that this does not cause a problem for the email in
inria.fr (replies are sent from that address), but only for
lemondedujeu.org (I did not test irisa.fr).
Is there another way to tell notmuch to use as From address the address
the email was sent to, if it's one of my emails?
Thanks,
Alan
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch
Re: [PATCH] emacs: don't start processes stopped
David Edmondson [2020-01-03T23:17:24Z] wrote: > On Friday, 2020-01-03 at 09:04:00 -08, Steven Allen wrote: > >> It causes this function to fail with: >> >> let: Wrong type argument: null, t >> >> Support for this was removed from Emacs in April >> 2019 (5c5e309527e6b582e2c04b83e7af45f3144863ac) because it never >> worked correctly (apparently). >> >> This also shouldn't be necessary as sentinels will not be called >> unless emacs is idle or waiting for input. Therefore, the >> `process-put' calls immediately following the `make-process' call >> should always complete before the sentinel is first called. > > Reviewed-by: David Edmondson And tested by me: the patch fixes the key retrieval problem. -- /// OpenPGP key: 4E1055DC84E9DFF613D78557719D69D324539450 // https://keys.openpgp.org/search?q=tliko...@iki.fi / https://keybase.io/tlikonen https://github.com/tlikonen signature.asc Description: PGP signature ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: filtering headers from forwarded messages
On Mon 2019-12-30 15:16:59 +0200, Teemu Likonen wrote:
> Daniel Kahn Gillmor [2019-12-20T13:50:03-05] wrote:
>
>> In notmuch-emacs, i can manually filter the headers by editing the
>> reply compose buffer, of course, but it's kind of a pain, and it'd be
>> nice to have it done automatically for me.
>
>> Has anyone else considered this use case, or thought about how to make
>> it easy/simple to do the right thing when using Notmuch? Are there
>> other factors that are worth considering?
>
> The underlying message-mode has these variables:
>
> message-forward-as-mime
> message-forward-before-signature
> message-forward-ignored-headers
> message-forward-included-headers
> message-forward-show-mml
>
> I have not studied those very closely but at least I know that when
> -as-mime is nil user can use -included-headers to set what headers user
> wants to include.
Thanks for the pointer! it looks like
message-forward-{ignored,included}-headers should do (roughly) what i
want. I'll try them out.
--dkg
signature.asc
Description: PGP signature
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch
