On 2024-07-31 16:51, John Levine via mailop wrote:
Gmail gets lost in a mess of creating private Google cloud projects
alpine works *great* using the well-known oAuth2 client secrets from
Thunderbird.
M.
___
mailop mailing list
mailop@mailop.org
ht
On 2024-07-31 19:08, John Levine wrote:
which finally dies on a redirect to a localhost URL.
I know what's going on, they expect the client program to be running a
tiny web server on localhost to collect the credentials, but it
doesn't work.
Check Alpine's instructions at that screen:
> Autho
On 2025-02-06 12:09, Andreas S. Kerber via mailop wrote:
from our perspective the "450 4.7.26 Service does not accept messages sent over
IPv6" message started intermittently a couple of month ago
I'd hazard a guess this is due Microsoft only very recently starting to
add IPv6 support.
micro
On 2025-02-06 11:31, Chris Spencer via mailop wrote:
Via an include the problem will go away as the IP6 will no longer form
part of the hostname which I suspect is the issue here. We’ve likely
fallen foul of permitted characters per rfc1035
Permitted characters? How so?
An email sent by 2a0d:
On 2025-03-19 08:24, Bill Cole via mailop wrote:
I think that preserving the original is probably the right choice
Oh, if only they were. A specific example of this is that we're sending
out e.g.:
X-Discourse-Category: =?UTF-8?Q?=F0=9F=92=BC_Corporate_Events?=
List-ID: =?UTF-8?Q?fnord_|_=F0=
On 2025-03-18 18:30, Marcel Becker via mailop wrote:
Communicating and sharing details with that address is the correct
course of action.
We did, two months ago, with no results.
Hence the query here.
--
Michael Brown
Civilized Discourse Construction Kit, Inc.
https://www.discourse.org/
_
Since their new ARF system went into place, we've been getting invalid
ARF reports from Yahoo!
More specifically, they include mail samples that are not valid RFC822
messages (their attached parts profess to be 7-bit, but actually contain
UTF-8).
(we automatically process reports to track me