Things to test before we push the new mailing list.

[myles]

• [x] Subscribe/unsubscribe.
• [x] Is there a CAPTCHA so the spammers don’t spam?
• [x] Is the CAPTCHA original enough to not get clobbered in automation
• [x] Can we go “approve requests” mode for subscription requests i we need to?
• [x] Is there a working email address for help?
• [x] Reply to… does it contain the list? (i.e, test munging behavior)
• [x] Do posts contain the signature?
• [x] Does threading work
• [x] Reply-all? (nope, only to the list)
• [x] Reply to list?
• [x] Attachments – send a big one - large attachments are thrown to moderation
• [x] Attachments – send a little one
• [x] Nonsubscriber posting - gets thrown to moderation
• [x] Ban somebody
• [x] Is there an archive?
• [x] PGP mail
• [x] HTML mail
• [x] Do you receive your own posts? (No, you don't)
• [x] Do you receive replies you’re cc’d on? (twice?) (No, replies are only to the list.)
• [ ] Delivery to a non-MX domain (A-record only)
• [x] SPF, is it sender ok?
• [ ] SPF good/neutral/bad sender sending to list
• [x] IPV6?
• [x] Does the web site's documentation indicate the location of the new list? http://gtalug.org/mailing-list/

[myles]

IPv6 is all setup. I don't know how you to test it though.

[mgjk]

it was a pie in the sky test, but I guess it can be tested by subscribing and using the system from an ipv6 only host... i found a 15 day free one.. hmmm

[myles]

So it looks like Gmail uses IPv6 when sending email. Sending from Gmail is working so IPv6 is working.

[myles]

Tried sending a 6MB file to the talks list and got this in return:

Your mail to 'talk' with the subject

    This is a 6MB file.

Is being held until the list moderator can review it for approval.

The reason it is being held:

    Message body is too big: 8443076 bytes with a limit of 40 KB

Either the message will get posted to the list, or you will receive
notification of the moderator's decision.  If you would like to cancel
this posting, please visit the following URL:

I like this idea to make sure people don't share binaries on the mailing list.

[mgjk]

I agree on the attachment size limit. I think the setting should be set to reject the attachment with an explanation. it shouldn't clog up the moderation queue.

[mgjk]

Not sure the checkboxes are meaningful for these tests. Do they mean "tested okay", and does an empty box mean "not tested " or "not okay?"

Can we add the link to the archives to http://gtalug.org/mailing-list/ ?

[mgjk]

Reply-to-list should be okay (for apps which use it... I think Mutt does?) Messages have in the headers a lot of useful info (the URLs check ok)

List-Id: GTALUG Talk List-Unsubscribe: http://gtalug.org/mailman/options/talk, mailto:talk-request@gtalug.org?subject=unsubscribe List-Archive: http://gtalug.org/pipermail/talk/ List-Post: mailto:talk@gtalug.org List-Help: mailto:talk-request@gtalug.org?subject=help List-Subscribe: http://gtalug.org/mailman/listinfo/talk, mailto:talk-request@gtalug.org?subject=subscribe

[mgjk]

SPF for the list to send is ok:

;; ANSWER SECTION:
gtalug.org.             10799   IN      TXT     "v=spf1 mx a a:penguin.gtalug.org ~all"

Received-SPF: pass (google.com: domain of talk-bounces@gtalug.org designates 69.164.222.247 as permitted sender) client-ip=69.164.222.247;

[myles]

Do they mean "tested okay", and does an empty box mean "not tested " or "not okay?"

Checked: Tested and Okay.

Unchecked: Not Tested or Not Okay.

[mgjk]

I think we should keep the existing sig from the old list, updating the URL. There was a lot of politics around it.

The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/mailing-list/

We lost some of the "how to unsubscribe" stuff from the Wiki. But that's a separate issue.

[mgjk]

I'm going to put this stuff in issues. They can be closed as not a problem if need be.

[myles]

@mgjk did you do the last two checkmarks yet. Or do you think they might not be needed?

[mgjk]

They’re not showstoppers, I think unlikely to be issues.

It’s okay to document that it wasn’t checked.

I’m too busy at the moment to test them properly, it’s more important that we go live.

From: Myles Braithwaite [mailto:notifications@github.com] Sent: September-08-14 4:28 PM To: gtalug/infrastructure Cc: mike Subject: Re: [infrastructure] Things to test before we push the new mailing list. (#24)

@mgjkhttps://github.com/mgjk did you do the last two checkmarks yet. Or do you think they might not be needed?

— Reply to this email directly or view it on GitHubhttps://github.com/gtalug/infrastructure/issues/24#issuecomment-54881802.