~sircmpwn/sr.ht-discuss

9 5

Support for html/txt emails in todo and lists

Details
Message ID
<e6e7c80d-0947-d9a5-d708-368e1e5d91d2@protonmail.com>
DKIM signature
missing
Download raw message
Hi all,
I've seen in the postmarketOS issue tracker that Drew would be open to
adding the option of supporting html/txt emails in todo and some mailing
lists [1] (I guess the idea would be to get the txt version only and
discard the html part).

I'm quite interested in that since I think many people using some tool
hosted on srht would not know how to send their email in text-only (or
maybe even could not, depending on their email provider).
This means that, until this is implemented, hosting code on srht only
can effectively prevent people from asking questions on user mailing
lists or sending tickets on todo.

Would anyone know if there is already work on that? (for instance, I
don't know if the pmOS folks want to do it to migrate their issues in
the long run or not?)
If not, could somebody point me to the part of the srht code I should be
looking at if I want to see whether I'm able to get this done? (though
that might be somewhat unlikely)

Thanks in advance,
T


[1]:
https://gitlab.com/postmarketOS/postmarketos/-/issues/49#note_1038978313
Details
Message ID
<CN9KMT9AQE5I.3GILC7IX42H2A@taiga>
In-Reply-To
<e6e7c80d-0947-d9a5-d708-368e1e5d91d2@protonmail.com> (view parent)
DKIM signature
missing
Download raw message
We provide resources to educate people on setting up plain text emails
in their mail client of choice:

https://useplaintext.email

Regarding the comments in that ticket, I am willing to consider a patch
which loosens up the content type filter such that list admins can
opt-in to allowing HTML email -- IF it has a plaintext part as well and
NOT by default.
Details
Message ID
<4e000121-da4c-6da4-8ae5-6b72f0eb9782@protonmail.com>
In-Reply-To
<CN9KMT9AQE5I.3GILC7IX42H2A@taiga> (view parent)
DKIM signature
missing
Download raw message
> Regarding the comments in that ticket, I am willing to consider a patch
> which loosens up the content type filter such that list admins can
> opt-in to allowing HTML email -- IF it has a plaintext part as well and
> NOT by default.

Yes, that's exactly the type of patch I meant.
Could you point me out to the part of the code I should be looking at,
to see whether I have a chance of making this happen?
Details
Message ID
<CN9LHC2OCBUM.3B3EOD6U013V5@taiga>
In-Reply-To
<4e000121-da4c-6da4-8ae5-6b72f0eb9782@protonmail.com> (view parent)
DKIM signature
missing
Download raw message
On Fri Sep 30, 2022 at 10:30 AM CEST, Tanguy Fardet wrote:
> Yes, that's exactly the type of patch I meant.
> Could you point me out to the part of the code I should be looking at,
> to see whether I have a chance of making this happen?

Just grep for the whitelist in lists.sr.ht
Details
Message ID
<91ada133-8f06-0f43-2632-551a3f604fbd@protonmail.com>
In-Reply-To
<CN9LHC2OCBUM.3B3EOD6U013V5@taiga> (view parent)
DKIM signature
missing
Download raw message
> Just grep for the whitelist in lists.sr.ht

Found it, thanks!
Details
Message ID
<87ediqshyx.fsf@bzg.fr>
In-Reply-To
<CN9KMT9AQE5I.3GILC7IX42H2A@taiga> (view parent)
DKIM signature
missing
Download raw message
"Drew DeVault" <sir@cmpwn.com> writes:

> Regarding the comments in that ticket, I am willing to consider a patch
> which loosens up the content type filter such that list admins can
> opt-in to allowing HTML email -- IF it has a plaintext part as well and
> NOT by default.

Did anyone managed to remove the text/html mimetype from the list of
rejected mimetypes and receive multipart emails in a sr.ht list?

I tested this but it does not seem to work yet.

Any feedback appreciated!

-- 
 Bastien
Details
Message ID
<878r8heefi.fsf@bzg.fr>
In-Reply-To
<87ediqshyx.fsf@bzg.fr> (view parent)
DKIM signature
missing
Download raw message
Bastien <bzg@gnu.org> writes:

> "Drew DeVault" <sir@cmpwn.com> writes:
>
>> Regarding the comments in that ticket, I am willing to consider a patch
>> which loosens up the content type filter such that list admins can
>> opt-in to allowing HTML email -- IF it has a plaintext part as well and
>> NOT by default.
>
> Did anyone managed to remove the text/html mimetype from the list of
> rejected mimetypes and receive multipart emails in a sr.ht list?
>
> I tested this but it does not seem to work yet.

FWIW I filed this ticket: https://todo.sr.ht/~sircmpwn/lists.sr.ht/210

-- 
 Bastien Guerry
Details
Message ID
<87le853w0m.fsf@gmx.com>
In-Reply-To
<CN9KMT9AQE5I.3GILC7IX42H2A@taiga> (view parent)
DKIM signature
pass
Download raw message

Drew DeVault <sir@cmpwn.com> wrote:

>I am willing to consider a patch which loosens up the content type
>filter such that list admins can opt-in to allowing HTML email -- IF it
>has a plaintext part as well and NOT by default.


Any updates on this?

--
Regards,
Salih
Details
Message ID
<878r3aneb8.fsf@bzg.fr>
In-Reply-To
<87le853w0m.fsf@gmx.com> (view parent)
DKIM signature
pass
Download raw message
Salih Muhammed <lr0@gmx.com> writes:

> Drew DeVault <sir@cmpwn.com> wrote:
>
>>I am willing to consider a patch which loosens up the content type
>>filter such that list admins can opt-in to allowing HTML email -- IF it
>>has a plaintext part as well and NOT by default.
>
> Any updates on this?

I did not manage to receive an email containing both plain text and
HTML parts on a list where I emptied the "Rejected mimetypes" field
and added "text/*" for permitted fields, I guess there is no update
yet on this.

-- 
 Bastien
Details
Message ID
<875xye3px5.fsf@gmx.com>
In-Reply-To
<878r3aneb8.fsf@bzg.fr> (view parent)
DKIM signature
pass
Download raw message
I've submitted a ticked 2 weeks ago https://todo.sr.ht/~sircmpwn/lists.sr.ht/212

--
Regards,
Salih
Reply to thread Export thread (mbox)