Re: file corruption after transmission over email

2022-06-01 Thread Marcelo Laia
On 29/05/22 at 12:49, Kurt Hackenberg wrote: > On 2022/05/29 12:15, Marcelo Laia wrote: > > > If I send a message using > > > > tee >(lbdb-fetchaddr -a)|/usr/bin/msmtp -a gmail $@ > > > > the attached file with embedded image got corrupted > > What is that line intended to do? Hi Kurt! I'm

Re: file corruption after transmission over email

2022-06-01 Thread Kurt Hackenberg
On 2022/06/01 12:17, Marcelo Laia wrote: tee >(lbdb-fetchaddr -a)|/usr/bin/msmtp -a gmail $@ ... 1. http://www.jukie.net/bart/blog/lbdb-and-mutt Ah, bash's "process substitution". I forgot about that.

Re: file corruption after transmission over email

2022-06-01 Thread Patrick Shanahan
* Marcelo Laia [06-01-22 12:17]: > On 29/05/22 at 12:49, Kurt Hackenberg wrote: > > On 2022/05/29 12:15, Marcelo Laia wrote: > > > > > If I send a message using > > > > > > tee >(lbdb-fetchaddr -a)|/usr/bin/msmtp -a gmail $@ > > > > > > the attached file with embedded image got corrupted > >

Re: file corruption after transmission over email

2022-06-01 Thread Kevin J. McCarthy
On Sun, May 29, 2022 at 01:15:51PM -0300, Marcelo Laia wrote: tee >(lbdb-fetchaddr -a)|/usr/bin/msmtp -a gmail $@ Perhaps lbdb-fetchaddr is closing input before the end of the message, and tee is exiting on a SIGPIPE? Mutt 2.2 had a fix to properly reset signals (specifically SIGPIPE) on