#1 Patch for git list 2 years ago

Ticket created by ~thrill_seeker on ~quf/sourcehut-client

Hi,

I would like to submit a patch that would include git list subcommand. I wanted to send it via git send-email, but there is no mailing list related to the project.

How can I contribute? If you agree, of course :)

Thanks!

-- TS

#351 Reply/forward encoding error with attachment 3 years ago

Comment by ~thrill_seeker on ~sircmpwn/aerc2

Aerc currently doesn't handle nested messages.

If you forward the attachment to the next person, you get the encoded, nested email (which looks like the gibberish you showed in the case of quoted-printable)

Okay, is there an easy way to reply/forward email without attachment, and attach files afterwards? As a workaround I mean.

Thank you for the information!

#351 Reply/forward encoding error with attachment 3 years ago

bug added by ~thrill_seeker on ~sircmpwn/aerc2

#351 Reply/forward encoding error with attachment 3 years ago

Ticket created by ~thrill_seeker on ~sircmpwn/aerc2

Hello,

I am experiencing problems related to encoding just when replying/forwarding some emails, and it seems related to attachment. Here is an example:

I received an email with plain text and accents, but without an attachment. The body is the following:

Aquest és un email de test amb arxiu adjunt. Moltes gràcies.

Then, I received the same message but this time with an attachment (plain text file); the body is almost the same.

If I try to reply/forward the email without attachment, the body is shown perfectly, including accents. But if I try to reply/forward the other email, the body is, in this case:

On Tue Mar 3, 2020 at 4:25 PM, Joan Albert Erráez wrote:

--4bd8fa31c22c329b895fcd74916459fae9c81f40ca02afbac791a4b3769a Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Content-Type: text/plain; charset=UTF-8

Aquest =C3=A9s un email de test amb arxiu adjunt.

Moltes gr=C3=A0cies.

--4bd8fa31c22c329b895fcd74916459fae9c81f40ca02afbac791a4b3769a--

I am not a Go programmer, so I do not know how to solve this. However, I noticed that, at least for forwardings (commands/msg/forward.go), response is handled differently depending on incoming email attachment.

Any idea for this?

Thank you very much anyway.

#266 write tcp 195.154.162.14:43250->74.125.133.108:993: write: broken pipe 3 years ago

Comment by ~thrill_seeker on ~sircmpwn/aerc2

Having this issue as well every 5-10 minutes approximately. I do not have the skills to write patches right now, but I hope some day I will :)