Re: file corruption after transmission over email
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 exec(). Child processes previously inherited Mutt's ignore setting, but this caused other incorrect behavior. Maybe adding '--output-error=exit-nopipe' to the tee command will help? Alternatively maybe capture stdin to a temp file and the perform the lbdb-fetchaddr msmtp separately? -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: file corruption after transmission over email
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
* 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 > > > > What is that line intended to do? > > Hi Kurt! > > I'm so sorry for don't had been do a complete explanation about that. > Sorry! > > Here [1] is a configuration that could bee explanation how to use LBDB > with mutt and msmtp. > > In this mean time, I migrate to abook and all work nice, now. > > I use abook in this way: > > set query_command = "abook --mutt-query '%s'" > set display_filter = "pee 'abook --add-email-quiet' 'cat -'" # all > opened messages have senders address added to abook database. > > I uninstalled lbdb from my machine. why uninstall lbdb? you can query it directly, ie: lbdbq Marcelo\ Laia lbdbq: 1 matches marcelol...@gmail.com Marcelo Laia then only add addresses to abook that you really need. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
Re: file corruption after transmission over email
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 so sorry for don't had been do a complete explanation about that. Sorry! Here [1] is a configuration that could bee explanation how to use LBDB with mutt and msmtp. In this mean time, I migrate to abook and all work nice, now. I use abook in this way: set query_command = "abook --mutt-query '%s'" set display_filter = "pee 'abook --add-email-quiet' 'cat -'" # all opened messages have senders address added to abook database. I uninstalled lbdb from my machine. Thanks! 1. http://www.jukie.net/bart/blog/lbdb-and-mutt -- Marcelo
Re: file corruption after transmission over email
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? Is the message intended to be on tee's standard input? If so, how does it get there? That line redirects tee's standard output to -- where? What will go through the pipe to msmtp? What is lbdb-fetchaddr? Putting it in () runs it in a subshell; that does not return a string. If you're trying to pass the message to be sent through tee (standard input to standard output), through a pipe to the standard input of msmtp, I don't think that command does that.
Re: file corruption after transmission over email
On 22/05/22 at 03:27, Marcelo Laia wrote: > On 18/05/22 at 01:17, Marcelo Laia wrote: > > > > Nowadays, senders have a feedback that attach files that I sent was > > corrupted. > > > > > After more tests, I found that if I use the mutt native smtp, attach is > properly transmitted. I could open it very well! > > So, I think there is a problem with msmtp or its configuration. No. Isn't msmtp problems. > This is only changes I do to get all works very well! I did more tests and found: If I send a message using tee >(lbdb-fetchaddr -a)|/usr/bin/msmtp -a gmail $@ the attached file with embedded image got corrupted The same result is got with tee >(lbdb-fetchaddr -a -c utf8) If I send a message using /usr/bin/msmtp -a gmail $@ the attached file with embedded image got loaded correctly. Have you some clue, here? Thank you so much! -- Marcelo
Re: file corruption after transmission over email
On 18/05/22 at 01:17, Marcelo Laia wrote: > > Nowadays, senders have a feedback that attach files that I sent was > corrupted. > After more tests, I found that if I use the mutt native smtp, attach is properly transmitted. I could open it very well! So, I think there is a problem with msmtp or its configuration. MSMTP config (msmtprc) defaults tls_trust_file /etc/ssl/certs/ca-certificates.crt logfile ~/.msmtp.log account gmail auth oauthbearer host smtp.gmail.com port 587 protocol smtp tls on from mylo...@gmail.com user mylo...@gmail.com passwordeval /path/to/scripts/OAuth2/get_teteraorg_token_gmail.sh MUTT native smtp relevant config (muttrc) set smtp_oauth_refresh_command="/path/to/scripts/OAuth2/get_teteraorg_token_gmail.sh" set smtp_authenticators="oauthbearer" set smtp_url = "smtp://mylo...@gmail.com@smtp.gmail.com:587/" set from = "mylo...@gmail.com" set use_from = yes set realname = "My Real Name" -- Marcelo
Re: file corruption after transmission over email
On 22/05/22 at 09:06, Marcelo Laia wrote: > On 18/05/22 at 01:17, Marcelo Laia wrote: > > > > Nowadays, senders have a feedback that attach files that I sent was > > corrupted. > > > > After a lot of tests, I found: > > 1. Files with image/figure was damaged > > 2. If images are remove from files, they are transferred by mutt intact. > > Could you do a test for me? If so, please, download the next files and > send it to me, one per message, using GMail. Send direct to my private > e-mail. > > pdf with image/figure > https://www.dropbox.com/s/y11l265wjt4dbbz/Mutt-test-estagio_assinado.pdf?dl=0 > > docx with image/figure > https://www.dropbox.com/s/ifu7qf1xnp2ev97/Mutt-test-figure.docx?dl=0 > > docx without image/figure > https://www.dropbox.com/s/q4c0t7vb8tu6ikp/Mutt-test.docx?dl=0 > Patrick Shanahan tell me that all three files was opened properly in their openSuse Box. He sent me all three files attached and all of then was properly opened in my Debian Box. I forwarded Patrick's message to he self. All three files was attached to that message automatically. Patrick report me that only two files arrived to his mail box: the pdf (attached) is corrupt. the docx (w/o image) was fine. The docx with image/figure was not transmitted to Patrick. Well, this is another problem I'm had having: when I sent more than one attachment, only the ones that "pass" are sent. When I forward to Patrick, I thought that only one, that one without image, would be sent. To my surprise, the pdf was too. I do not know what is happening. However, I don't have ideia how figure out that problem! Have you some idea? Thank you! -- Marcelo
Re: file corruption after transmission over email
On 18/05/22 at 01:17, Marcelo Laia wrote: > > Nowadays, senders have a feedback that attach files that I sent was > corrupted. > After a lot of tests, I found: 1. Files with image/figure was damaged 2. If images are remove from files, they are transferred by mutt intact. Could you do a test for me? If so, please, download the next files and send it to me, one per message, using GMail. Send direct to my private e-mail. pdf with image/figure https://www.dropbox.com/s/y11l265wjt4dbbz/Mutt-test-estagio_assinado.pdf?dl=0 docx with image/figure https://www.dropbox.com/s/ifu7qf1xnp2ev97/Mutt-test-figure.docx?dl=0 docx without image/figure https://www.dropbox.com/s/q4c0t7vb8tu6ikp/Mutt-test.docx?dl=0 Please, before send, inspect it if they are opened very well in your machine. Tell me what system are you using. I use Debian testing (Debian 5.17.3-1 (2022-04-18) x86_64) Thank you so much! -- Marcelo
Re: file corruption after transmission over email
* Marcelo Laia [05-21-22 15:24]: > On 20/05/22 at 01:30, Marcelo Laia wrote: > > On 20/05/22 at 01:22, Marcelo Laia wrote: > > > On 18/05/22 at 01:17, Marcelo Laia wrote: > > > > > > > > Nowadays, senders have a feedback that attach files that I sent was > > > > corrupted. > > > > > > > > Have a someone similar issue? > > > So, there are some issue with GMail to bypass! > > > > > > Have you using GMail? If so, could you do a test for me? > > > Please, note that there is a file size difference. It looks like GMail > > is cutting the file or removing a part of it. > > I was wrong! > > Yesterday, when I sent the message through the Yahoo server, mutt saved > it in the outbox, before sending it. For that reason, I thought the > Yahoo upload was ok. However, this morning, I found that the message had > not been sent. It was jammed in the msmtpq queue (msmtp.queue). When I > sent the message earlier, the file got corrupted. So, it doesn't be > relevant if you send by Yahoo or GMail: the file is corrupted in anyway. > I'm sorry for being wrong. > > Problem persist! > > Have you using GMail? If so, could you do a test for me? I have had no problems sending an included file via gmail or mail.yahoo.com using mutt. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
Re: file corruption after transmission over email
On 20/05/22 at 01:30, Marcelo Laia wrote: > On 20/05/22 at 01:22, Marcelo Laia wrote: > > On 18/05/22 at 01:17, Marcelo Laia wrote: > > > > > > Nowadays, senders have a feedback that attach files that I sent was > > > corrupted. > > > > > > Have a someone similar issue? > > So, there are some issue with GMail to bypass! > > > > Have you using GMail? If so, could you do a test for me? > Please, note that there is a file size difference. It looks like GMail > is cutting the file or removing a part of it. I was wrong! Yesterday, when I sent the message through the Yahoo server, mutt saved it in the outbox, before sending it. For that reason, I thought the Yahoo upload was ok. However, this morning, I found that the message had not been sent. It was jammed in the msmtpq queue (msmtp.queue). When I sent the message earlier, the file got corrupted. So, it doesn't be relevant if you send by Yahoo or GMail: the file is corrupted in anyway. I'm sorry for being wrong. Problem persist! Have you using GMail? If so, could you do a test for me? -- Marcelo
Re: file corruption after transmission over email
* Marcelo Laia [05-20-22 12:32]: > On 20/05/22 at 01:22, Marcelo Laia wrote: > > On 18/05/22 at 01:17, Marcelo Laia wrote: > > > > > > Nowadays, senders have a feedback that attach files that I sent was > > > corrupted. > > > > > > Have a someone similar issue? > > > > > > > > > I found that issue is related to GMail. > > > > I sent the same attach from a Yahoo account and I got it open normally, > > like a charm! > > > > Here is the headers: > > > > > > From: Marcelo > > To: echo > > Date: Fri, 20 May 2022 13:10:42 -0300 > > Subject: Test Yahoo > > > > [-- Anexo No.1 --] > > [-- Tipo: text/plain, Codificação: 7bit, Tamanho: 0,1K --] > > > > -- > > Marcelo > > > > [-- Anexo No.2: TCC Lúnia-Vieira-v3.docx --] > > [-- Tipo: > > application/vnd.openxmlformats-officedocument.wordprocessingml.document, > > Codificação: > > base64, Tamanho: 6,0M --] > > > > [-- application/vnd.openxmlformats-officedocument.wordprocessingml.document > > não é aceito (use > > 'v' para ver esta parte) --] > > > > > > Attach view (after C-v) > > > > I 1 [text/plain, > > 7bit, us-ascii, 0,1K] > > A 2 TCC Lúnia-Vieira-v3.docx > > [applica/vnd.openxm, base64, 6,0M] > > > > > > So, there are some issue with GMail to bypass! > > > > Have you using GMail? If so, could you do a test for me? > > > > Plus: > > > GMail > > From: Marcelo > To: echo > Date: Fri, 20 May 2022 12:50:17 -0300 > Subject: Test 8 emacs > > [-- Anexo No.1 --] > [-- Tipo: text/plain, Codificação: 7bit, Tamanho: 0K --] > > > [-- Anexo No.2: TCC Lúnia-Vieira-v3.docx --] > [-- Tipo: > application/vnd.openxmlformats-officedocument.wordprocessingml.document, > Codificação: > base64, Tamanho: 71K --] > > [-- application/vnd.openxmlformats-officedocument.wordprocessingml.document > não é aceito (use > 'v' para ver esta parte) --] > > > Yahoo > > From: Marcelo > To: echo > Date: Fri, 20 May 2022 13:10:42 -0300 > Subject: Test Yahoo > > [-- Anexo No.1 --] > [-- Tipo: text/plain, Codificação: 7bit, Tamanho: 0,1K --] > > -- > Marcelo > > [-- Anexo No.2: TCC Lúnia-Vieira-v3.docx --] > [-- Tipo: > application/vnd.openxmlformats-officedocument.wordprocessingml.document, > Codificação: > base64, Tamanho: 6,0M --] > > [-- application/vnd.openxmlformats-officedocument.wordprocessingml.document > não é aceito (use > 'v' para ver esta parte) --] > > > Attach View (after C-v) > > GMail > > I 1 [text/plain, 7bit, us-ascii, 0K] > A 2 TCC Lúnia-Vieira-v3.docx [applica/vnd.openxm, base64, 71K] > > > Yahoo > > I 1 [text/plain, 7bit, us-ascii, 0,1K] > A 2 TCC Lúnia-Vieira-v3.docx [applica/vnd.openxm, base64, 6,0M] > > > Please, note that there is a file size difference. It looks like GMail > is cutting the file or removing a part of it. > > -- > Marcelo I have not ever had that happen to me, that I can recall. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
Re: file corruption after transmission over email
On 20/05/22 at 01:22, Marcelo Laia wrote: > On 18/05/22 at 01:17, Marcelo Laia wrote: > > > > Nowadays, senders have a feedback that attach files that I sent was > > corrupted. > > > > Have a someone similar issue? > > > > > I found that issue is related to GMail. > > I sent the same attach from a Yahoo account and I got it open normally, > like a charm! > > Here is the headers: > > > From: Marcelo > To: echo > Date: Fri, 20 May 2022 13:10:42 -0300 > Subject: Test Yahoo > > [-- Anexo No.1 --] > [-- Tipo: text/plain, Codificação: 7bit, Tamanho: 0,1K --] > > -- > Marcelo > > [-- Anexo No.2: TCC Lúnia-Vieira-v3.docx --] > [-- Tipo: > application/vnd.openxmlformats-officedocument.wordprocessingml.document, > Codificação: > base64, Tamanho: 6,0M --] > > [-- application/vnd.openxmlformats-officedocument.wordprocessingml.document > não é aceito (use > 'v' para ver esta parte) --] > > > Attach view (after C-v) > > I 1 [text/plain, 7bit, > us-ascii, 0,1K] > A 2 TCC Lúnia-Vieira-v3.docx > [applica/vnd.openxm, base64, 6,0M] > > > So, there are some issue with GMail to bypass! > > Have you using GMail? If so, could you do a test for me? > Plus: GMail From: Marcelo To: echo Date: Fri, 20 May 2022 12:50:17 -0300 Subject: Test 8 emacs [-- Anexo No.1 --] [-- Tipo: text/plain, Codificação: 7bit, Tamanho: 0K --] [-- Anexo No.2: TCC Lúnia-Vieira-v3.docx --] [-- Tipo: application/vnd.openxmlformats-officedocument.wordprocessingml.document, Codificação: base64, Tamanho: 71K --] [-- application/vnd.openxmlformats-officedocument.wordprocessingml.document não é aceito (use 'v' para ver esta parte) --] Yahoo From: Marcelo To: echo Date: Fri, 20 May 2022 13:10:42 -0300 Subject: Test Yahoo [-- Anexo No.1 --] [-- Tipo: text/plain, Codificação: 7bit, Tamanho: 0,1K --] -- Marcelo [-- Anexo No.2: TCC Lúnia-Vieira-v3.docx --] [-- Tipo: application/vnd.openxmlformats-officedocument.wordprocessingml.document, Codificação: base64, Tamanho: 6,0M --] [-- application/vnd.openxmlformats-officedocument.wordprocessingml.document não é aceito (use 'v' para ver esta parte) --] Attach View (after C-v) GMail I 1 [text/plain, 7bit, us-ascii, 0K] A 2 TCC Lúnia-Vieira-v3.docx [applica/vnd.openxm, base64, 71K] Yahoo I 1 [text/plain, 7bit, us-ascii, 0,1K] A 2 TCC Lúnia-Vieira-v3.docx [applica/vnd.openxm, base64, 6,0M] Please, note that there is a file size difference. It looks like GMail is cutting the file or removing a part of it. -- Marcelo
Re: file corruption after transmission over email
On 18/05/22 at 01:17, Marcelo Laia wrote: > > Nowadays, senders have a feedback that attach files that I sent was > corrupted. > > Have a someone similar issue? > I found that issue is related to GMail. I sent the same attach from a Yahoo account and I got it open normally, like a charm! Here is the headers: From: Marcelo To: echo Date: Fri, 20 May 2022 13:10:42 -0300 Subject: Test Yahoo [-- Anexo No.1 --] [-- Tipo: text/plain, Codificação: 7bit, Tamanho: 0,1K --] -- Marcelo [-- Anexo No.2: TCC Lúnia-Vieira-v3.docx --] [-- Tipo: application/vnd.openxmlformats-officedocument.wordprocessingml.document, Codificação: base64, Tamanho: 6,0M --] [-- application/vnd.openxmlformats-officedocument.wordprocessingml.document não é aceito (use 'v' para ver esta parte) --] Attach view (after C-v) I 1 [text/plain, 7bit, us-ascii, 0,1K] A 2 TCC Lúnia-Vieira-v3.docx [applica/vnd.openxm, base64, 6,0M] So, there are some issue with GMail to bypass! Have you using GMail? If so, could you do a test for me? -- Marcelo
Re: file corruption after transmission over email
On 20/05/22 at 11:09, Patrick Shanahan wrote: > I have for many years w/o problem: > set send_charset="us-ascii:iso-8859-1:iso-8859-15:windows-1252:utf-8" Not solved! -- Marcelo
Re: file corruption after transmission over email
* Marcelo Laia [05-20-22 11:02]: > On 18/05/22 at 10:42, Paul Gilmartin via Mutt-users wrote: > > On May 18, 2022, at 10:17:56, Marcelo Laia wrote: > > > > > > Nowadays, senders have a feedback that attach files that I sent was > > > corrupted. > > > > > > Have a someone similar issue? > > > > > Do you know (Orr can thee recipients tell you): > > Content-Type: and Content-Transfer-Encoding: 7bit > > > > > I did some tests and neither solved the issue. > > Here is what I did. > > set send_charset="utf-8" > > or > > set send_charset="us-ascii:utf-8" > > or > > set use_8bitmime > > or > > set use_8bitmime = yes > > This is what I receive form server: > > Test 1 > > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > > Content-Type: > application/vnd.openxmlformats-officedocument.wordprocessingml.document > Content-Disposition: attachment; > filename*=iso-8859-1''TCC%20L%FAnia-Vieira-v3%2Edocx > Content-Transfer-Encoding: base64 > > > Test 2 > > Content-Type: text/plain; charset=utf-8 > Content-Disposition: inline > > Content-Type: > application/vnd.openxmlformats-officedocument.wordprocessingml.document > Content-Disposition: attachment; > filename*=utf-8''TCC%20L%C3%BAnia-Vieira-v3%2Edocx > Content-Transfer-Encoding: base64 > > > On the Sent Box, I got, for all messages sent: > > From: Marcelo > To: echo > Date: Fri, 20 May 2022 11:19:12 -0300 > Subject: Test 6 > > [-- Anexo No.1 --] > [-- Tipo: text/plain, Codificação: 7bit, Tamanho: 0K --] > > > [-- Anexo No.2: TCC Lúnia-Vieira-v3.docx --] > [-- Tipo: > application/vnd.openxmlformats-officedocument.wordprocessingml.document, > Codificação: > base64, Tamanho: 71K --] > > [-- application/vnd.openxmlformats-officedocument.wordprocessingml.document > não é aceito (use > 'v' para ver esta parte) --] > > Please, someone could help me? I have for many years w/o problem: set send_charset="us-ascii:iso-8859-1:iso-8859-15:windows-1252:utf-8" -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
Re: file corruption after transmission over email
On 18/05/22 at 10:42, Paul Gilmartin via Mutt-users wrote: > On May 18, 2022, at 10:17:56, Marcelo Laia wrote: > > > > Nowadays, senders have a feedback that attach files that I sent was > > corrupted. > > > > Have a someone similar issue? > > > Do you know (Orr can thee recipients tell you): > Content-Type: and Content-Transfer-Encoding: 7bit > I did some tests and neither solved the issue. Here is what I did. set send_charset="utf-8" or set send_charset="us-ascii:utf-8" or set use_8bitmime or set use_8bitmime = yes This is what I receive form server: Test 1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Content-Disposition: attachment; filename*=iso-8859-1''TCC%20L%FAnia-Vieira-v3%2Edocx Content-Transfer-Encoding: base64 Test 2 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Content-Disposition: attachment; filename*=utf-8''TCC%20L%C3%BAnia-Vieira-v3%2Edocx Content-Transfer-Encoding: base64 On the Sent Box, I got, for all messages sent: From: Marcelo To: echo Date: Fri, 20 May 2022 11:19:12 -0300 Subject: Test 6 [-- Anexo No.1 --] [-- Tipo: text/plain, Codificação: 7bit, Tamanho: 0K --] [-- Anexo No.2: TCC Lúnia-Vieira-v3.docx --] [-- Tipo: application/vnd.openxmlformats-officedocument.wordprocessingml.document, Codificação: base64, Tamanho: 71K --] [-- application/vnd.openxmlformats-officedocument.wordprocessingml.document não é aceito (use 'v' para ver esta parte) --] Please, someone could help me? Thank you -- Marcelo
Re: file corruption after transmission over email
On 18/05/22 at 10:42, Paul Gilmartin via Mutt-users wrote: > > Can you test by sending a message with only small > attachments to: e...@univie.ac.at > ??? > OK, I do that. But, I don't known what I need to search inside the echo response. Could you point me out? -- Marcelo
Re: file corruption after transmission over email
On May 18, 2022, at 10:17:56, Marcelo Laia wrote: > > Nowadays, senders have a feedback that attach files that I sent was > corrupted. > > Have a someone similar issue? > Do you know (Orr can thee recipients tell you): Content-Type: and Content-Transfer-Encoding: 7bit Can you test by sending a message with only small attachments to: e...@univie.ac.at ??? -- gil
