~labrat

Recent activity

Re: How to handle labels? a day ago

From Reto to ~sircmpwn/aerc

On Tue, Feb 23, 2021 at 03:16:48PM +0000, Axel Dahlberg wrote:
> The only thing that now that I would like to change is the fact that
> unread emails also have the `unread`-tag. Is there someway to exclude
> tags? It's just annoying to also see the `unread`-tag since this is
> already visualised by the font.

No, I don't think so

> PS. I haven't really used these mailing lists before. How do you
> actually reply to a specific thread and not create a new one as I did
> with my last reply? What I do now is just click the "Reply to thread"
> button which opens aerc using that `mailto` link. But there seems to be
> something missing since it didn't add my last reply to the original
> thread.

Re: How to handle labels? a day ago

From Reto to ~sircmpwn/aerc

ah, thi gs like this confuse(ed) me:

IMAP keywords
All the non-standard message flags are called keywords in IMAP. Some clients use these automatically for marking spam (eg. $Junk, $NonJunk, $Spam, $NonSpam keywords). Thunderbird uses labels which map to keywords $Label1, $Label2, etc.

Dovecot stores keywords in the maildir filename's flags field using letters a..z. This means that only 26 keywords are possible to store in the maildir. If more are used, they're still stored in Dovecot's index files. The mapping from single letters to keyword names is stored in dovecot-keywords file. The file is in format:


0 $Junk
1 $NonJunk
0 means letter 'a' in the maildir filename, 1 means 'b' and so on. The file doesn't need to be locked for reading, but when writing dovecot-uidlist file must be locked. The file must not be directly modified, it can only be replaced with rename() call.

For example, a file named

Re: How to handle labels? a day ago

From Reto to ~sircmpwn/aerc

On 23 February 2021 14:06:57 CET, Simon Ser <contact@emersion.fr> wrote:
>IMAP flags aren't single-letter. They're just not well-supported by
>email clients.

>flag-keyword    = atom
>atom            = 1*ATOM-CHAR

ehm, am I *that* bad at reading RFCs?
1*char is a single letter yes?

Sure you can have a local mapping, however there's no (official) way to transfer the mappings, nor general client support for doing that.

In other words it doesn't work at all like you'd expect.

Re: How to handle labels? a day ago

From Reto to ~sircmpwn/aerc

What you call labels (gmail / protonmail sticky notes) and what emersion calls
labels (single letter thingies no one really uses) are very unrelated concepts.

imap simply doesn't have a similar feature as of yet as the two providers give you
with a non imap protocol.
IIRC jmap has something like that.

Aerc only talks imap so we don't have what you would like to use.

A workaround is using notmuch, there you can do things with labels / tags (sticky note version)

Re: Unable to send mail using ProtonMail Bridge 2 days ago

From Reto to ~sircmpwn/aerc

On 22 February 2021 15:47:04 CET, Tmpod@pm.me wrote:
>Can't both things work at the same time?

Sure, hold shift while dragging

Re: non ASCII letters in header fields 2 days ago

From Reto to ~sircmpwn/aerc

On Mon, Feb 22, 2021 at 02:20:27PM +0000, Simon Ser wrote:
> That's expected.

Thanks a bunch.
Am I correct that this is then a case of "broken email, not a go-message bug"?

Cheers,
Reto

Re: Unable to send mail using ProtonMail Bridge 2 days ago

From Reto to ~sircmpwn/aerc

On Mon, Feb 22, 2021 at 02:34:20PM +0100, Reto wrote:
> On 22 February 2021 14:10:16 CET, Simon Ser <contact@emersion.fr> wrote:
>
> >The "insecure" option blindly trusts the cert. So I don't think it's a
> >big deal to *not* negotiate STARTTLS when insecure is explicitly
> >specified by the user.
>
> That's not what it does in aerc no. "insecure" tries to start a non encrypted plain text connection.
> There is no cert involved at all.
>
> *if* the server advertises support for starttls we bail out saying that this is probably not what you should be doing.
> If starttls is available you really should use it. Anything else is most likely a configuration mistake.
>
> The whole connection string is a frequent point of confusion, people tend to brute force various combinations instead of reading what the options do.

Re: Unable to send mail using ProtonMail Bridge 2 days ago

From Reto to ~sircmpwn/aerc

On Mon, Feb 22, 2021 at 01:00:15PM +0000, Simon Ser wrote:
> > Also, how could I fix the "horribly insecure" transactions between
> > aerc and the bridge?
>
> There's no need to do this, since everything is local. Unix sockets
> would maybe make more sense than TCP for this use-case.

Assuming you trust everything on the host that can mess with routing tables and
firewalls and such, whatever can reroute and copy packets.

If you aren't the admin of the box (say on a company owned server) then that's
not guaranteed. If you are the sole user and admin, sure.

Re: Unable to send mail using ProtonMail Bridge 2 days ago

From Reto to ~sircmpwn/aerc

On Mon, Feb 22, 2021 at 01:01:17PM +0000, Simon Ser wrote:
> TLS without certificate checks is as good as cleartext anyways.

Indeed, that's why I don't want to blindly trust the cert.
If you pin it then at least you notice if it is different from the time you generated
the fingerprint...

Essentially you are then back to TOFU property wise, which is way better than just
using plain text.

Or do you have a different opinion here?

Re: Unable to send mail using ProtonMail Bridge 2 days ago

From Reto to ~sircmpwn/aerc

On Mon, Feb 22, 2021 at 12:28:13PM +0000, Simon Ser wrote:
> No, sorry. It would make sense to not try to negotiate STARTTLS when
> explicitly disabled by the user, I think.

Not particularly fond of it... If you can trivially disable protections people
will just blindly do that without thinking about it much.

Better would be cert pinning which is https://todo.sr.ht/~sircmpwn/aerc2/329