Colours

74 views
Skip to first unread message

John Cremona

unread,
Feb 3, 2023, 5:53:26 AM2/3/23
to SAGE devel
A few people who post to this list have their email configured so that quoted text is in a different colour, instead of having quoted text prefixed by > or similar.

I am partly colourblind and this confuses me as I literally cannot see that some text is in a different colour (for some combinations, e.g. I cannot see red text as different from black).

So I, at least, would welcome it if this system was not used.

John

Kwankyu Lee

unread,
Feb 3, 2023, 6:14:01 AM2/3/23
to sage-devel
On Friday, February 3, 2023 at 7:53:26 PM UTC+9 john.c...@gmail.com wrote:
A few people who post to this list have their email configured so that quoted text is in a different colour, instead of having quoted text prefixed by > or similar.

Right. It happens to me. I don't know how I can control this. 

Kwankyu Lee

unread,
Feb 3, 2023, 6:15:03 AM2/3/23
to sage-devel
Again. Sorry.

John Cremona

unread,
Feb 3, 2023, 6:31:07 AM2/3/23
to sage-...@googlegroups.com


On Fri, 3 Feb 2023 at 11:15, Kwankyu Lee <ekwa...@gmail.com> wrote:
Again. Sorry.

Never mind, it is not that important. 

--
You received this message because you are subscribed to the Google Groups "sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/444c48f1-52ac-4d55-bcc9-7e391134a2b6n%40googlegroups.com.

Salvatore Stella

unread,
Feb 3, 2023, 6:44:32 AM2/3/23
to sage-...@googlegroups.com
Hi,

>Right. It happens to me. I don't know how I can control this.

most likely this is because of e-mails being formatted as html. Try sending
plain-text e-mails instead.

S.

dim...@gmail.com

unread,
Feb 3, 2023, 6:44:55 AM2/3/23
to sage-...@googlegroups.com
On Fri, Feb 03, 2023 at 03:15:03AM -0800, Kwankyu Lee wrote:
> Again. Sorry.

I think this happens if you use Google's interface to Groups, rather
than an email client.

Posting using an email client (set to send in text mode - but probably
not necessarily) should be enough to avoid this.

Dima
signature.asc

G. M.-S.

unread,
Feb 3, 2023, 7:41:37 AM2/3/23
to sage-...@googlegroups.com

Sorry, John.

In my case, I get everything in black without any quoting, so I cannot distinguish the responses.

(I am not colorblind, I use Gmail and I have the standard configuration.)

Guillermo

Georgi Guninski

unread,
Feb 3, 2023, 7:42:29 AM2/3/23
to sage-...@googlegroups.com
You may consider the thunderbird email client or
some other MUA and try to disable html formatting
if the client supports it.

Can you point to colored testcase so I try it?

Once upon a time one could use gmail with console
client, but now google added additional authentication,
greatly reducing the options for client.

google turned Usenet to google groups and now they
are on the road to takeover email.

Dima Pasechnik

unread,
Feb 3, 2023, 9:08:48 AM2/3/23
to sage-devel


On Fri, 3 Feb 2023, 12:42 Georgi Guninski, <ggun...@gmail.com> wrote:
You may consider the thunderbird email client or
some other MUA and try to disable html formatting
if the client supports it.

Can you point to colored testcase so I try it?

Once upon a time one could use gmail with console
client, but now google added additional authentication,
greatly reducing the options for client.

gmail still supports application passwords, so one can still bypass 2FA for sending/receiving mail to/from gmail.

my previous message in this thread was sent from mutt+postfix.


google turned Usenet to google groups and now they
are on the road to takeover email.

--
You received this message because you are subscribed to the Google Groups "sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.

Georgi Guninski

unread,
Feb 3, 2023, 9:18:16 AM2/3/23
to sage-...@googlegroups.com
On Fri, Feb 3, 2023 at 4:08 PM Dima Pasechnik <dim...@gmail.com> wrote:

>
>
> gmail still supports application passwords, so one can still bypass 2FA for sending/receiving mail to/from gmail.
>
> my previous message in this thread was sent from mutt+postfix.
>

I love this, is it document somewhere?
I tried mutt with `imap` but couldn't make it work.

dim...@gmail.com

unread,
Feb 3, 2023, 11:17:17 AM2/3/23
to sage-...@googlegroups.com
Yes, it's mutt+imap for reading, and locally installed postfix for
sending. This is being run on a more or less up to date Gentoo laptop.
(deleting messages from gmail might not work with my setup any more, it's a bit
iffy, as gmail deviates from normal imap here - but it's fixable)

in .muttrc I have a setup for several imap/email servers:
######################################################################
macro index <f2> '<change-folder>imaps://imap.gmail.com<enter>'
folder-hook 'gmail.com' 'source ~/.mutt/account.gmail'
macro generic "<esc>2" ":set from=dim...@gmail.com"

macro index <f3> '<change-folder>imaps://foo.bar<enter>'
folder-hook 'foo.bar' 'source ~/.mutt/account.foobar'
...

set reverse_name=yes
alternates <username>@gmail.com$ b...@foo.bar$ #...

# to select what mailbox/From: I want.

set use_from = yes
set envelope_from ="yes"
set mime_forward=yes

set sendmail="/usr/sbin/sendmail -oem -oi" # sendmail is actually postix
unset imap_passive # Don't wait to enter mailbox manually
set imap_check_subscribed
set mail_check=300
set timeout=10
# keep a cache of headers for faster loading (1.5.9+?)
set header_cache=~/.hcache
# Display download progress every 15K
set net_inc=15
....
######################################################################

In .mutt/account.gmail I have
######################################################################
# Automatically log in to this mailbox at startup
set imap_user=<username>
set imap_pass=<app. password>
unset record

set spoolfile="imaps://imap.googlemail.com/INBOX"
set folder="imaps://imap.googlemail.com"
set postponed="=Drafts"

set from="<username>@gmail.com"
macro index,pager d "<save-message>=[Google<quote-char> Mail]/Trash<enter><enter>" "Trash Message"
######################################################################

To generate <app. passwrd>, go you your Google account
settings->Security, and scroll to "Signing in to Google" to locate
"application passwords" menu, where you can generate new ones etc.
I have created one for imap, and one for postfix.



So this is all good for email reading etc; for sending I set up
postfix (probably built-in mutt's sending thing will work too, but I
didn't like it back then, as it's slow, and you have to wait for the
transaction with google's smpt server to complete). Postfix does proper
sendmail queing, sending in backgroud, etc. And it's nice to have a
working sendmail for sending from scripts etc...


For postfix, here is /etc/postfix/main.cf
#####################################################################
smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu)
biff = no

# appending .domain is the MUA's job.
append_dot_mydomain = no

# Uncomment the next line to generate "delayed mail" warnings
#delay_warning_time = 4h

readme_directory = no

# TLS parameters (the following 2 files are absent):
smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key

smtpd_use_tls=yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache

# See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for
# information on enabling SSL in the smtp client.

smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination
myhostname = <whatever> # FIX THIS TO A REAL VALUE (same as in /etc/mailname)
myorigin = /etc/mailname
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
mydestination = /etc/mailname, <FIRST PART OF myhostname>, localhost.localdomain, localhost
relayhost =
mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = all
inet_protocols = all

smtpd_sasl_local_domain = $myhostname
smtpd_sasl_auth_enable = yes
broken_sasl_auth_clients = yes

smtp_use_tls=yes
smtp_tls_security_level = may
smtp_tls_loglevel = 2

smtp_sasl_security_options = noanonymous

smtp_sender_dependent_authentication = yes
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd

sender_dependent_relayhost_maps= hash:/etc/postfix/sender_relay
smtp_sasl_mechanism_filter = ntlm,login,plain
compatibility_level = 2
###################################################################

now, it remains to specify /etc/postfix/sasl_passwd
###################################################################
smtp.gmail.com <username>:<app. password>
smtp.foo.bar baz:SECRET_FOO_BAR
....
## for some smtp servers, one needs 'b...@foo.bar' as username, not
## just 'baz'
###################################################################

and /etc/postfix/sender_relay
###################################################################
<username>@gmail.com [smtp.gmail.com]:587
b...@foo.bar [smtp.foo.bar]:587
...

###################################################################

Dont't forget to run postmap to generate their hashes (*.db files)
If I recall right, I don't need to touch postfix's master.cf.
I also have

$ cat /etc/postfix/sasl/smtpd.conf
pwcheck_method: saslauthd
mech_list: PLAIN LOGIN

which might be needed. One more catch: at different locations gmail
uses different names for folders such as Drafts, Trash (but this is easy
to figure out)

I'd be glad to help further with it.
Dima




signature.asc

Nils Bruin

unread,
Feb 3, 2023, 7:31:38 PM2/3/23
to sage-devel
On Friday, 3 February 2023 at 03:44:55 UTC-8 dim...@gmail.com wrote:

I think this happens if you use Google's interface to Groups, rather
than an email client.

Nope , google groups interface formats quoted text with a line to the left (as above). No colour introduced either. Perhaps there are some settings that change how quoted text is configured, but there's definitely a setting (and I would think the default) that typesets it as in this message.

Nils Bruin

unread,
Feb 3, 2023, 7:32:48 PM2/3/23
to sage-devel
Oh, ouch. That is in the preview! when it's posted it indeed just displays with a colour difference! This is an issue for googlegroups accessibility.

G. M.-S.

unread,
Feb 3, 2023, 7:58:20 PM2/3/23
to sage-...@googlegroups.com

FWIW, here is what I receive "as is".
You will notice that it is not a problem about HTML formatting.
Guillermo

*** BEGIN ***
Sender: sage-...@googlegroups.com
Date: Fri, 3 Feb 2023 16:31:38 -0800 (PST)
From: Nils Bruin <nbr...@sfu.ca>
To: sage-devel <sage-...@googlegroups.com>
Message-Id: <f901280a-7143-40fd...@googlegroups.com>
In-Reply-To: <Y9zzscGwc/n2Siup@hilbert>
Subject: Re: [sage-devel] Re: Colours
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_5076_2109657552.1675470698405"
X-Original-Sender: nbr...@sfu.ca
Reply-To: sage-...@googlegroups.com
Precedence: list
Mailing-list: list sage-...@googlegroups.com; contact sage-dev...@googlegroups.com
List-ID: <sage-devel.googlegroups.com>
X-Spam-Checked-In-Group: sage-...@googlegroups.com
X-Google-Group-Id: 560892725547
List-Post: <https://groups.google.com/group/sage-devel/post>, <mailto:sage-...@googlegroups.com>
List-Help: <https://groups.google.com/support/>, <mailto:sage-de...@googlegroups.com>
List-Archive: <https://groups.google.com/group/sage-devel
List-Subscribe: <https://groups.google.com/group/sage-devel/subscribe>, <mailto:sage-devel...@googlegroups.com>
List-Unsubscribe: <mailto:googlegroups-manage+56...@googlegroups.com>,
 <https://groups.google.com/group/sage-devel/subscribe>

------=_Part_5076_2109657552.1675470698405
Content-Type: multipart/alternative;
boundary="----=_Part_5077_26055156.1675470698405"

------=_Part_5077_26055156.1675470698405
Content-Type: text/plain; charset="UTF-8"


On Friday, 3 February 2023 at 03:44:55 UTC-8 dim...@gmail.com wrote:

I think this happens if you use Google's interface to Groups, rather
than an email client.

Nope , google groups interface formats quoted text with a line to the left
(as above). No colour introduced either. Perhaps there are some settings
that change how quoted text is configured, but there's definitely a setting
(and I would think the default) that typesets it as in this message.

--
You received this message because you are subscribed to the Google Groups "sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/f901280a-7143-40fd-97e0-34e8b23618f0n%40googlegroups.com.

------=_Part_5077_26055156.1675470698405
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Friday, 3 February 2023 at 03:44:55 UTC-8 dim...@gmail.com wrote:<div><s=
pan><br />I think this happens if you use Google's interface to Groups, rat=
her
<br />than an email client.
<br /></span><div><br /></div><div>Nope , google groups interface formats q=
uoted text with a line to the left (as above). No colour introduced either.=
 Perhaps there are some settings that change how quoted text is configured,=
 but there's definitely a setting (and I would think the default) that type=
sets it as in this message.<br /></div><br /></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;sage-devel&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:sage-devel+...@googlegroups.com">sage-dev=
el+unsu...@googlegroups.com</a>.<br />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/d/msgid/sage-devel/f901280a-7143-40fd-97e0-34e8b23618f0n%40googlegroups.=
com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msg=
id/sage-devel/f901280a-7143-40fd-97e0-34e8b23618f0n%40googlegroups.com</a>.=
<br />

------=_Part_5077_26055156.1675470698405--

------=_Part_5076_2109657552.1675470698405--
*** END***

seb....@gmail.com

unread,
Feb 4, 2023, 2:43:03 PM2/4/23
to sage-devel
FWIW: I've observed a similar behavior (see this post). I was using Firefox with a markdown plugin. In the preview, MD rendered correctly (I used quotes (">") and inline code ("`") tags). After posting, MD was removed and the quoted line appeared in red.
Reply all
Reply to author
Forward
0 new messages