Under construction: Version: 2026-04-13
I take notes as I do things. Otherwise I forget what I did. Some of those notes are available at the links below. Maybe they will be useful to somebody.
More context >Here< and history >Here< (and scroll up)

Notes on the nerflings mailing list have moved from those pages to this one:
The nerflings.org mailing list (mechanics)
2025 mechanics.
2026 mechanics.
Test of gmail.com.
Most recent mechanics.

Connectivity Problems

In addition to problems getting gmail.com to accept my email, I have been having basic internet connectivity problems. The connection between the laptop in my lap at home and the mail/web server in the cloud regularly quits working. After a minute of two it starts working again, but it's difficult to edit a file if it takes two minutes to echo a character.

Update (2025-07-16): That seems not to be true anymore. Since moving the wireless router upstairs on 2025-07-04(Fri) it works better.

Update (2025-08-24): Maybe it is true. Yesterday it lost connection many times. Today it is not as bad, but still flakey.

Update (2025-09-12): Log of connectivity problems >here<.

What's up with the mailing list?

The nerflings.org mailing list (mechanics)

Scroll down to end for recent news or up for more context.

The nerflings.org mailing list 2025 (mechanics)

It's been a quiet over the winter.

The nerflings.org mailing list 2026 mechanics

Why does ED@gmail.com get bounced in less than 7 hours, while LW@gmail.com waits "deferred" for days? Ahdunno. Seems pretty random. See >Here< for why gmail.com is intentionally random.
The morning of 2026-04-24 I update DNS MX records for nerflings.org as described >Here<.

Test of gmail.com only

I make a test list which has only three addresses, my own and two gmail addresses. We can experiment with relaying gmail without spamming everyone. We find that gmail.com sometimes accepts a message but does not deliver it, not even to a spam filter, and also does not return a non-delivery status notification (bounce message). See >Here< for more on gmail.com.

I believe this is a violation of Internet Standard RFC-2821 "Simple Mail Transfer Protocol" (SMTP) [Page 24]. Is this a bug or defective by design? In either case it seems pointless to continue to carefully track it. Well, I have this pointless data anyway.

The eight digit hex numbers are queue IDs. That's what appears in the log file, and so it's easier to track than the email address. I now say "transferred to" rather than "sent out to". That's more accurate; it takes two to transfer. Note that they are transfered 20 addresses at a time, so it takes three transfers to get all 50 gmail.com addresses tranferred.
HTML5?
(checked 2026-05-02
)
      The Pirate Party has not registered a copyright on this rumor.