Re: What is DNF Check-upgrade Actually Doing

[Stephen Morris <steve.morris.au@xxxxxxxxx>]

On 1/12/24 10:53, Samuel Sieb wrote:

> On
>       11/30/24 3:44 PM, Stephen Morris wrote:
>       
> > On 1/12/24 10:32, Samuel Sieb wrote:
> >         
> > > On 11/30/24 3:04 PM, Stephen Morris
> > >           wrote:
> > >           
> > > > On 30/11/24 20:05, Tim via users
> > > >             wrote:
> > > >             
> > > > > As a comparison, have a look through
> > > > >               your menus for "view source" and
> > > > >               
> > > > >               see what a message looks like before Thunderbird converts
> > > > >               it into its
> > > > >               
> > > > >               own HTML rendition of the message (regardless of whether
> > > > >               it was HTML or
> > > > >               
> > > > >               plain text).
> > > > >               
> > > > >               
> > > > >               Thunderbirds re-rendering of messages is yet another
> > > > >               reason that
> > > > >               
> > > > >               I don't like it.
> > > > >               
> > > > >             
> > > >             I did a "view source" and after trawling through all the
> > > >             headers to get to what looks like your response there is no
> > > >             plain text and no html, it displays like encrypted data,
> > > >             there is nothing visible at all the matches your text.
> > > >             
> > > >           
> > >           
> > >           Content-Type: text/plain; charset="utf-8"
> > >           
> > >           Content-Transfer-Encoding: base64
> > >           
> > >           
> > >           The plain text is encoded as base64.
> > >           
> > >           
> > >         
> >         Thanks Samuel, I understood that the mails were mime encoded,
> >         but when I viewed the source to see whether when I previewed or
> >         opened the mail I was looking at plain text or a html version
> >         which is my preferred version, I was expecting to see the body
> >         of the email as either plain text or html tags, particularly
> >         when viewing the mail makes it look like the client is working
> >         with html.
> >         
> >       
>       
>       The funny thing with your emails is that the plain text part is
>       base64 encoded and the html part is not.
>       
>     
    That's interesting, I would have expected both to be the same. I
    used to use the "Auto" compose option, which supposedly sends the
    mail as plain text if there is no formatting otherwise it sends it
    as html, but after I think you requested that I stop sending through
    html, I changed the option to send both html and text for the
    relevant client to decide which one it was going to use, hence I
    would have expected both to be encoded, which I thought was a mail
    standard. 
    I'm using a version of Thunderbird that is several versions ahead of
    what's in the Fedora repositories, and I think I'm on the mail list
    for Thunderbird, so I'll raise it on there to see if I get any
    feedback.
    
    regards, 
    Steve

Attachment: OpenPGP_0x1EBE7C07B0F7242C.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

-- 
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue