My apologies to most listmembers for the noise; the usual address to
reach the listowner doesn't seem to be working (see below).
I tried to send mail to lynx-dev's owner- address, raising a
consistent malformatting issue in list mail (see below), and got a
bounce indicating even more issues. So I'm wondering if I could get
whoever runs the list to (a) deal with the issue I tried to raise and
(b) fix (or at least get fixed) the issue that prevented the mail from
getting through?
For (a), here's the content I tried to send:
I've been noticing, for a while now, that lynx-dev list mail has been
coming in with a minor format violation.
Specifically, it shows up as (to quote a recent list mail)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
but, while the base64 encoding is valid, the decoded content is not
valid text/plain; it represents line breaks as bare 0x0a octets,
without any preceding 0x0d octets. (See RFC2046 4.1.1.)
I would, of course, recommend you fix or replace whatever is
responsible for this malformatting.
For (b), the bounce I got says
>- The following addresses had permanent fatal errors -
> owner-lynx-...@nongnu.org
>
>- Transcript of session follows -
> ... while talking to eggs.gnu.org.:
> >>> RCPT To:
> <<< 550-Verification failed for
> <<< 550-Could not complete sender verify callout for
> .
> <<< 550-The mail server(s) for the domain may be temporarily unreachable, or
> <<< 550-they may be permanently unreachable from this server. In the latter
> case,
> <<< 550-you need to change the address or create an MX record for its domain
> <<< 550-if it is supposed to be generally accessible from the Internet.
> <<< 550-Talk to your mail administrator for details.
> <<< 550-Callout verification failed:
> <<< 550 550 Unrouteable address
> 550 owner-lynx-...@nongnu.org... User unknown
The problem with this is twofold: first, there's the problem with the
whole paradigm, in that it farms out part of spam filtering to entities
with no particular incentive to do it the way eggs.gnu.org wants it
done; second, there's the implementation problem, in that the verify
code doesn't seem to know how to speak SMTP. It dropped the connection
slightly over 60 seconds into my banner delay, a point at which any
client-side timeout SHOULD be at least five minutes (RFC2821 4.5.3.2):
2021-08-12 13:28:01.51: [RCTkjr.Sghk.Mgl] (11069) connection from
209.51.188.92/35416
[...]
2021-08-12 13:29:01.54: [RCTkjr.Sghk.Mgl] ident lookup aborted by client input
2021-08-12 13:29:01.54: [RCTkjr.Sghk.Mgl] drop delay 60.025715
2021-08-12 13:29:01.54: [RCTkjr.Sghk.Mgl] unexpected SMTP connection drop
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev
