Re: notmuch-emacs: forward messages inline
On Fri 2015-11-06 14:23:22 -0500, Matthew Lear wrote: > I guess that's one way, but it's a bit of a faff. Unless it was possible to > wrap > it all up in lisp, I don't really think it's a good option. It seems to be specifically what you're looking to do, so i don't see it as a "faff" but *shrug* > No arguments on the 'being sane' front, although I have seen > notmuch-emacs fail to correctly formulate an RFC822 attachment of the > original email message a few times. I suspect this was due to MS Outlook > formatting but can't be sure, though. If you have a repeatable use case, please report it. I would expect that "inline forwarding" would be much *more* likely to formulate the message incorrectly, since it would involve re-flowing text, etc. rfc822/message-style forwarding is just an unfiltered byte-dump as a part inside a newly-composed message. > My main use of notmuch is at work where I have to handle large amounts > of email such as bug notifications from a couple of systems, messages > to/from lists, auto generated stuff for tracking, plus the usual reams > of corporate email from teams and colleagues. Notmuch allows me to > handle this fantastically. great! :) > A common use case of forwarding messages inline is to take an email > already received, and send it onto colleagues. It's not uncommon for > this to initiate a new thread of conversation and other people could > be added to the thread as appropriate. If I were to forward a message > I received as an RFC822 attachment, in order for the conversation to > be coherent and contained in the text when other people were added to > the thread, the email containing my attachment would need to be > forwarded to (additional) recipients because 'replying to all' and > including new recipients wouldn't contain the original message. It sounds like you're saying you'd like to have a reply mode that includes attachments as well. is that right? Or when replying, you'd like to have a per-attachment option to go ahead and re-include it? fwiw, i'd also like to be able to forward entire threads directly from notmuch, instead of having to forward only one message at a time. > As I see it, to be able to forward and include people starting a new > thread based on the forwarded message, it needs to be inline. Make > sense? Hm, this kind of forwarding usually results in reverse-chronological ordering, which i find impossible to read effectively, particularly when i'm jumping into the middle of it. Also, if the original message itself contains attachments, it doesn't forward those attachments effectively. right? It'd be nice to be able to bounce the relevant messages to the new recipient (e.g. "| /usr/sbin/sendmail f...@example.com") and then follow up with In-Reply-To and References set properly, all in one clean action. But depending on the age of the original message and the dmarc/anti-spam policies of the domains of the original author and the new recipient, i can imagine that the original message might not make it through, even if the followup would. I hear you that it sounds like we're missing something to cleanly handle the real-world workflow you describe, but i don't think inline-forwarding is it. --dkg ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: "notmuch new" does not remove my file from db (double slash problem ?)
On Tue, Apr 14, 2015 at 04:52:29PM +0300, Tomi Ollila wrote:
> On Tue, Apr 14 2015, franc...@avalenn.eu wrote:
> > I have a little problem here.
> > I have a message of which I had multiple copies and I deleted one of
> > them but "notmuch new" does not suppress this copy.
> >
> > $ notmuch search --output=files id:20150216180408.HA14616@myhost
> >
> > /home/francois/Maildir/my_first_box/cur/1424110151_0.24869.myhost,U=742:2,S
> >
> > /home/francois/Maildir/my_second_box/cur/1424110163_0.24869.myhost,U=14486:2,S
> > /home/francois/Maildir/my_third_box//cur/1429004021.3224_3.myhost:2,S
> >
> > The last copy is the one I deleted.
> > I tried to readd the message to this box and after I have this status :
> >
> > $ cp ~/Maildir/my_second_box/cur/1424110163_0.24869.myhost,U=14486:2,S
> > ~/Maildir/my_third_box/cur
> > $ notmuch new
> > Processed 1 file in almost no time.
> > No new mail.
> > $ notmuch search --output=files id:20150216180408.HA14616@myhost
> >
> > /home/francois/Maildir/my_first_box/cur/1424110151_0.24869.myhost,U=742:2,S
> >
> > /home/francois/Maildir/my_second_box/cur/1424110163_0.24869.myhost,U=14486:2,S
> > /home/francois/Maildir/my_third_box/cur/1429004021.3224_3.myhost:2,S
> > /home/francois/Maildir/my_third_box//cur/1429004021.3224_3.myhost:2,S
> >
> > And if I redelete it I come back to beginning :
> >
> > $ rm ~/Maildir/my_third_box/cur/1429004021.3224_3.myhost:2,S
> > $ notmuch new
> > No new mail. Detected 1 file rename.
> > $ notmuch search --output=files id:20150216180408.HA14616@myhost
> >
> > /home/francois/Maildir/my_first_box/cur/1424110151_0.24869.myhost,U=742:2,S
> >
> > /home/francois/Maildir/my_second_box/cur/1424110163_0.24869.myhost,U=14486:2,S
> > /home/francois/Maildir/my_third_box//cur/1429004021.3224_3.myhost:2,S
> >
> >
> > I don't know how the file path with double slash was added in the
> > first place to the DB but I have a real problem with it.
> >
> > Anyone have any idea of how I can solve this ?
>
> When you remoted file from my_third_box/ directory timestamp was updated
> and notmuch new should have noticed file disappearing -- it may be that
> as it has same message id as another it somehow did not get disappeared
> from db.
>
> what you can do is to move all of the messages to another directory,
> run notmuch new, restore (some of) the files and run notmuch new again
> (and then restore tags...)
>
> something like this:
>
> mkdir ~/tmp-20150414
> notmuch search --output=files id:20150216180408.HA14616@myhost | xargs mv -T
> ~/tmp-20150414
> notmuch new
> mv ~/tmp-20150414/1424110151_0.24869.myhost,U=742:2,S
> ~/Maildir/my_first_box/cur/
> notmuch new
>
> if you do this, report...
I finally did this and the result is still the same.
I think my last chance is to drop completely the notmuch db and
reimporting from dump.
$ notmuch search --output=files id:20150216180408.GA24515@myhost
/home/francois/Maildir/another_box/cur/1446803446_0.30241.myhost,U=7096:2,S
/home/francois/Maildir/my_second_box/cur/1446803455_0.30241.myhost,U=3407:2,S
/home/francois/Maildir/my_first_box/cur/1446803465_0.30241.myhost,U=32711:2,S
/home/francois/Maildir/my_third_box//cur/1429004021.3224_3.myhost:2,S
$ notmuch search --output=files id:20150216180408.GA24515@myhost | xargs
--delimiter="\n" mv -t ~/tmp-$(date +%Y%m%d)
mv: impossible d'évaluer «
/home/francois/Maildir/my_third_box//cur/1429004021.3224_3.myhost:2,S »: Aucun
fichier ou dossier de ce type
$ ls -ltra ~/tmp-20151106
total 1576
-rwxr-xr-x 1 francois francois 453137 nov. 6 10:50
1446803446_0.30241.myhost,U=7096:2,S*
-rwxr-xr-x 1 francois francois 453137 nov. 6 10:50
1446803455_0.30241.myhost,U=3407:2,S*
-rwxr-xr-x 1 francois francois 453137 nov. 6 10:51
1446803465_0.30241.myhost,U=32711:2,S*
drwxr-xr-x 72 francois francois 241664 nov. 6 11:05 ../
drwxr-xr-x 2 francois francois 4096 nov. 6 11:09 ./
$ notmuch new
No new mail.
$ notmuch search --output=files id:20150216180408.GA24515@myhost
/home/francois/Maildir/my_third_box//cur/1429004021.3224_3.myhost:2,S
$ mv ~/tmp-20151106/1446803465_0.30241.myhost,U=32711:2,S
~/Maildir/my_first_box/cur/
« /home/francois/tmp-20151106/1446803465_0.30241.myhost,U=32711:2,S » -> «
/home/francois/Maildir/my_first_box/cur/1446803465_0.30241.myhost,U=32711:2,S »
« /home/francois/tmp-20151106/1446803465_0.30241.myhost,U=32711:2,S »
supprimé
$ notmuch new
Note: Ignoring non-mail file:
/home/francois/Maildir/my_first_box/cu
Re: notmuch-emacs: forward messages inline
Hi Daniel, > On 5 Nov 2015, at 21:42, Daniel Kahn Gillmor wrote: >> On Fri 2015-11-06 04:51:53 +0900, Matthew Lear wrote: >> Are there any recommended ways to selectively forward an email as >> inline with notmuch-emacs rather than as an RFC822 attachment, eg have >> a new shortcut key that can be used for this purpose in addition to f? >> I have toggled one of the mml configuration variables (I forget >> exactly what it was) which switched the forwarding method to inline >> (ACAICT this also removed the ability of being able to forward as >> RFC822), but it also included various header information in the body >> of the email. Not good. > > I suppose you could reply to the message (r) and just change the > addresses, which would include the previous message "inline". If you > don't like that it leaks the previous message-id in the In-Reply-To and > References headers, you can just kill them from the buffer manually. I guess that's one way, but it's a bit of a faff. Unless it was possible to wrap it all up in lisp, I don't really think it's a good option. > But can i ask why you'd want this? forwarded messages as RFC 822 > attachments are significantly more sane for any MUA to deal with. No arguments on the 'being sane' front, although I have seen notmuch-emacs fail to correctly formulate an RFC822 attachment of the original email message a few times. I suspect this was due to MS Outlook formatting but can't be sure, though. My main use of notmuch is at work where I have to handle large amounts of email such as bug notifications from a couple of systems, messages to/from lists, auto generated stuff for tracking, plus the usual reams of corporate email from teams and colleagues. Notmuch allows me to handle this fantastically. A common use case of forwarding messages inline is to take an email already received, and send it onto colleagues. It's not uncommon for this to initiate a new thread of conversation and other people could be added to the thread as appropriate. If I were to forward a message I received as an RFC822 attachment, in order for the conversation to be coherent and contained in the text when other people were added to the thread, the email containing my attachment would need to be forwarded to (additional) recipients because 'replying to all' and including new recipients wouldn't contain the original message. As I see it, to be able to forward and include people starting a new thread based on the forwarded message, it needs to be inline. Make sense? -- Matt ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: weird paths in notmuch database
2015-11-06 16:34 GMT+01:00 Tomi Ollila : > Ah, so path > /export/home/username/mail//home/username/local/mail/archive/cur/1446805732.2711_9.hostname:2,S > > does not exist? It probably used to be (?) (via some long-gone symlink?) > and now it is just garbage in the database (that does not go away)...? No, it never existed. I'm positive about that. ...however, I just noticed that my muttrc config contains set folder="/home/username/local/mail" Maybe mutt-kz is screwing up things when it calls notmuch internally? Davide ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: weird paths in notmuch database
On Fri, Nov 06 2015, Davide Mancusi wrote: > 2015-11-06 16:24 GMT+01:00 Tomi Ollila : >> And notmuch config get database.path prints /export/home/username/mail >> I presume ? > > Correct. > >> If that is the case then this symlink should have no effect. >> >> Is there any symlinks inside /export/home/username/mail >> ( find /export/home/username/mail -type l ) (provided that >> was the database.path -- and sure there are no bind mounts ;D?) > > No symlinks and no bind mounts. Ah, so path /export/home/username/mail//home/username/local/mail/archive/cur/1446805732.2711_9.hostname:2,S does not exist? It probably used to be (?) (via some long-gone symlink?) and now it is just garbage in the database (that does not go away)...? > > Cheers, > Davide Tomi ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: [PATCH] emacs: Fontify From with message-header-other
On Thu, Nov 05 2015, "H. J. Illikainen" wrote: > Commit e26d767897e8ab59f05808a12ac5c9c1e3c7030f changed the > fontification of the body associated with the From header to > message-header-from. However, that face is non-existent, and in > message.el (message-font-lock-keywords) the From-header falls through > and is attributed the message-header-other face. > > This commit removes the fontification of the [Ff]rom header in > notmuch-show-mode in order to fontify it using the message-header-other > face. > > This only affects non-default configurations where > notmuch-message-headers is set to display From. I grepped emacs 24.3 sources for message-header-subject and message-header-from and, indeed, there is not reference to message-header-from (but plenty of message-header-subject). So, to me this change looks good (and trivial) -- I have not tested it (yet), though. Tomi > --- > emacs/notmuch-show.el | 2 -- > 1 file changed, 2 deletions(-) > > diff --git a/emacs/notmuch-show.el b/emacs/notmuch-show.el > index 49fd198..793f1a5 100644 > --- a/emacs/notmuch-show.el > +++ b/emacs/notmuch-show.el > @@ -353,8 +353,6 @@ operation on the contents of the current buffer." > 'message-header-cc) > ((looking-at "[Ss]ubject:") > 'message-header-subject) > -((looking-at "[Ff]rom:") > - 'message-header-from) > (t > 'message-header-other > > -- > H. J. Illikainen > > ___ > 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: weird paths in notmuch database
2015-11-06 16:24 GMT+01:00 Tomi Ollila : > And notmuch config get database.path prints /export/home/username/mail > I presume ? Correct. > If that is the case then this symlink should have no effect. > > Is there any symlinks inside /export/home/username/mail > ( find /export/home/username/mail -type l ) (provided that > was the database.path -- and sure there are no bind mounts ;D?) No symlinks and no bind mounts. Cheers, Davide ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: weird paths in notmuch database
On Fri, Nov 06 2015, Davide Mancusi wrote: > 2015-11-06 16:14 GMT+01:00 Tomi Ollila : >> How is the symlink exactly shown in ls -l /path/to/symlink output ? > > $ ls -l /home/username/local > lrwxrwxrwx 1 username group 21 Jan 23 2015 /home/username/local -> > /export/home/username And notmuch config get database.path prints /export/home/username/mail I presume ? If that is the case then this symlink should have no effect. Is there any symlinks inside /export/home/username/mail ( find /export/home/username/mail -type l ) (provided that was the database.path -- and sure there are no bind mounts ;D?) Tomi ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: weird paths in notmuch database
2015-11-06 16:14 GMT+01:00 Tomi Ollila : > How is the symlink exactly shown in ls -l /path/to/symlink output ? $ ls -l /home/username/local lrwxrwxrwx 1 username group 21 Jan 23 2015 /home/username/local -> /export/home/username ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: weird paths in notmuch database
On Fri, Nov 06 2015, Davide Mancusi wrote: > 2015-11-06 14:09 GMT+01:00 David Bremner : >>> $ notmuch search --output=files 'path:/home/**' >>> /export/home/username/mail//home/username/local/mail/archive/cur/1446805732.2711_9.hostname:2,S >>> /export/home/username/mail/archive/cur/1446805732.2711_9.hostname:2,S > [...] >> >>The directory must be specified relative to the top-level maildir >>(and without the leading slash). >> >> Please try with correct search syntax in order to narrow down the >> problem. > > The unusual search was just to illustrate the problem. I get the paths > even with tag searches, like so: > > $ notmuch search --output=files > 'id:20151106102835.ga2...@hostname.domain.com' > /export/home/username/mail//home/username/local/mail/archive/cur/1446805732.2711_9.hostname:2,S > /export/home/username/mail/archive/cur/1446805732.2711_9.hostname:2,S How is the symlink exactly shown in ls -l /path/to/symlink output ? (you can do the s/$USER/username/ conversion :) Tomi ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: weird paths in notmuch database
2015-11-06 14:09 GMT+01:00 David Bremner : >> $ notmuch search --output=files 'path:/home/**' >> /export/home/username/mail//home/username/local/mail/archive/cur/1446805732.2711_9.hostname:2,S >> /export/home/username/mail/archive/cur/1446805732.2711_9.hostname:2,S [...] > >The directory must be specified relative to the top-level maildir >(and without the leading slash). > > Please try with correct search syntax in order to narrow down the > problem. The unusual search was just to illustrate the problem. I get the paths even with tag searches, like so: $ notmuch search --output=files 'id:20151106102835.ga2...@hostname.domain.com' /export/home/username/mail//home/username/local/mail/archive/cur/1446805732.2711_9.hostname:2,S /export/home/username/mail/archive/cur/1446805732.2711_9.hostname:2,S ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: weird paths in notmuch database
Davide Mancusi writes: > Hi all, > > I have noticed that notmuch ends up with non-existing paths to some > messages. For instance: > > $ notmuch search --output=files 'path:/home/**' > /export/home/username/mail//home/username/local/mail/archive/cur/1446805732.2711_9.hostname:2,S > /export/home/username/mail/archive/cur/1446805732.2711_9.hostname:2,S > [...] # more follow > I'm not sure if there are really bad paths in the database, or notmuch is just handling illegal search syntax badly. To quote notmuch-search-terms(7): The directory must be specified relative to the top-level maildir (and without the leading slash). Please try with correct search syntax in order to narrow down the problem. ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
weird paths in notmuch database
Hi all, I have noticed that notmuch ends up with non-existing paths to some messages. For instance: $ notmuch search --output=files 'path:/home/**' /export/home/username/mail//home/username/local/mail/archive/cur/1446805732.2711_9.hostname:2,S /export/home/username/mail/archive/cur/1446805732.2711_9.hostname:2,S [...] # more follow Note that my mail folder is /export/home/username/mail. The first path does not exist. However, I have a symlink from /home/username/local to /export/home/username. Could that be the problem? Also, is there a way to get rid of these non-existent paths in the database? They are fed to another program in a script and it chokes on them. Thanks in advance for your help. Cheers, Davide ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
