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
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.
* 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
> >
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
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?
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
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
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
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
* 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
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
* 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
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
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!
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
* 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?
> > >
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):
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
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
Nowadays, senders have a feedback that attach files that I sent was
corrupted.
Have a someone similar issue?
Thank you so much!
--
Marcelo
Hi,
* Jussi Peltola wrote:
On Fri, May 08, 2009 at 06:23:15PM -0700, zion wrote:
if LC_CTYPE is unset, file doesn't get corrupted.
In that case, what does ':set ?charset' in mutt report?
I think mutt is reading your file, assuming it's KOI8-R as stated in
your locale, and converting it to
On Fri, May 08, 2009 at 06:23:15PM -0700, zion wrote:
On Fri, May 08, 2009 at 04:34:14PM -0700, zion wrote:
Well, I just captured smtp session of loopback interface (same box where
mutt is running). Here is the relevant part:
03d0: 746f 3e38 353c 2f74 6f3e 0d0a 0909 093c to85/to.
Hello,
I have a mystery that I'm trying to solve to no avail. mutt-1.5.19 is
running on OpenBSD 4.5, --with-idn. I got a little sample XML (utf-8)
encoded file that I'm trying to send as attachment. When I attach it,
mutt correctly identifies it: [text/plain, 8bit, utf-8, 0.3K], since
there are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Friday, May 8 at 03:00 PM, quoth Aaron S.:
I have a mystery that I'm trying to solve to no avail.
Hopefully we can help!
I got a little sample XML (utf-8) encoded file that I'm trying to
send as attachment. When I attach it, mutt correctly
On Fri, May 08, 2009 at 06:04:42PM -0500, Kyle Wheeler wrote:
On Friday, May 8 at 03:00 PM, quoth Aaron S.:
I have a mystery that I'm trying to solve to no avail.
Hopefully we can help!
I got a little sample XML (utf-8) encoded file that I'm trying to
send as attachment. When I
Well, I just captured smtp session of loopback interface (same box where
mutt is running). Here is the relevant part:
03d0: 746f 3e38 353c 2f74 6f3e 0d0a 0909 093c to85/to.
03e0: 7265 6164 3e21 d091 e288 9ae2 9591 3c2f read!п.Б..Б../
03f0:
On Fri, May 08, 2009 at 04:34:14PM -0700, zion wrote:
Well, I just captured smtp session of loopback interface (same box where
mutt is running). Here is the relevant part:
03d0: 746f 3e38 353c 2f74 6f3e 0d0a 0909 093c to85/to.
03e0: 7265 6164 3e21 d091 e288 9ae2 9591 3c2f
27 matches
Mail list logo
