~labrat


#153 Does not start with Alacritty 5 days ago

Comment by ~labrat on ~sircmpwn/aerc2

On Wed, Oct 14, 2020 at 08:02:11PM -0000, ~jordan31 wrote:

How are you all handling this issue more efficiently?

Works for me just fine with alacritty. tcell loads stuff from the terminfo db by now I think. Which version of aerc do you run? Do update to the master branch and check there please.

#455 toggle sidebar 11 days ago

Comment by ~labrat on ~sircmpwn/aerc2

This is an issue tracker and not a support forum.

Please use the mailing list or IRC for such questions.

REPORTED RESOLVED INVALID

#454 Delegation of authentication to external command 13 days ago

Comment by ~labrat on ~sircmpwn/aerc2

this already works

#454 Delegation of authentication to external command 13 days ago

on ~sircmpwn/aerc2

REPORTED RESOLVED INVALID

#453 could not read header: message: malformed MIME header line 17 days ago

Comment by ~labrat on ~sircmpwn/aerc2

nah no need. We don't do such particular workarounds, if we would do something it would need to be more robust than that.

Mixing mbox and maildir certainly isn't a common issue anymore, considering that all common mail sync tools do follow the spec (isync, offlineimap) and even a default dovecot setup uses maildir or is at least not hard to setup with maildir (heck, I could manage it ;) )

There's some discussion going on here: https://github.com/emersion/go-message/pull/101

#453 could not read header: message: malformed MIME header line 18 days ago

Comment by ~labrat on ~sircmpwn/aerc2

well, "working fine" is not how I would put it if you set invalid headers. Don't take this as an offense btw, just stating a fact.

The problem is how to handle it... Sure we could work around it by implementing our own parser, but how broken do you wanna get?

The code currently uses the information in the header to do things like show the proper fields in the msglist, sort them etc. If we can't even assume a basic header set (from,to date) what shall we do?

It's all specified in RFCs how a mail should look. Now, both examples here are invalid mails yours doesn't add a : and OP's has continuation lines without preceding whitespace.

How do we want to parse that? from the point where we encounter the error the structure is invalid. Should we just assume that the thing only has one error and the rest is fine? What if it's not?

#453 could not read header: message: malformed MIME header line 18 days ago

Comment by ~labrat on ~sircmpwn/aerc2

bah, scratch the last part... typing on a mobile...

#453 could not read header: message: malformed MIME header line 18 days ago

Comment by ~labrat on ~sircmpwn/aerc2

other clients don't care because they adapted to people who send broken email. As broken mails were not an issue people kept sending broken emails... meaning those clients are part of the problem.

If postfix adds it, you have a misconfigured postfix instance Would have been much better to just say "broken"

#453 could not read header: message: malformed MIME header line 18 days ago

Comment by ~labrat on ~sircmpwn/aerc2

still broken, it's not a valid header and as such not parsable.

#453 could not read header: message: malformed MIME header line 18 days ago

Comment by ~labrat on ~sircmpwn/aerc2

~mato show the raw headers of that mail