I came across an issue where Thunderbird appears to be connecting and using PLAIN TEXT authentication, leaving username and password visible, even though I have Authentication set it to SSL/TLS or STARTTLS.

In order to troubleshoot this issue, I found the following article:
https://wiki.mozilla.org/MailNews:Logging

Following the instructions in that article did NOT work!

It says you are supposed to use MOZ_LOG and MOZ_LOG_FILE as of April 2017 however these variables did not work even though it is June 2018. I had to use the old variable names of NSPR_LOG_MODULES and NSPR_LOG_FILE.

The following is the batch file (for Windows 10) that I used and was able to get a log for troubleshooting the authentication and connection to my POP3 and SMTP servers:

set NSPR_LOG_MODULES=negotiateauth:5,POP3:5,SMTP:5,timestamp
set NSPR_LOG_FILE=%USERPROFILE%\Desktop\tb-connect.log
"%ProgramFiles(x86)%\Mozilla Thunderbird\thunderbird.exe"

Using this log I was able to identify that it was indeed using PLAIN TEXT authentication. I am still in the process of trying to determine if this is a Thunderbird bug or a server side bug and will report back with further details when I have them.

I have posted a Bug Report on Thunderbird site in order to track the issue:
https://bugzilla.mozilla.org/show_bug.cgi?id=1467835

Here is an example bucket policy below for Amazon S3 that will limit it to a Specific Referer and URL only, so that your content can not be linked to from other websites.

{
 "Version": "2012-10-17",
 "Id": "HttpsRefererPolicyForMySite",
 "Statement": [
 {
 "Sid": "AllowGetRequestsReferredUrlSpecificForMySite",
 "Effect": "Allow",
 "Principal": "*",
 "Action": "s3:GetObject",
 "Resource": "arn:aws:s3:::my-bucket-name/*",
 "Condition": {
 "StringLike": {
 "aws:Referer": [
 "https://mysite.com/this-specific-page-only",
 "https://mysite.com/only-child-pages-of-this-page/*",
 "https://mysite.com/this-specific-page-and-child-pages*"
 ]
 }
 }
 },
 {
 "Sid": "ExplicitDenyIfNotUrlSpecificForMySite",
 "Effect": "Deny",
 "Principal": "*",
 "Action": "s3:GetObject",
 "Resource": "arn:aws:s3:::my-bucket-name/*",
 "Condition": {
 "StringNotLike": {
 "aws:Referer": [
 "https://mysite.com/this-specific-page-only",
 "https://mysite.com/only-child-pages-of-this-page/*",
 "https://mysite.com/this-specific-page-and-all-child-pages*"
 ]
 }
 }
 }
 ]
}

As a couple points of interest, note that for one specific URL to work, you should NOT put /* on the end of it. To specify a specific URL, you use it like this:
https://mysite.com/this-specific-page-only

If you specify a URL with /* on the end, then it will only work for children of that URL, not the specific URL itself. For example, if you use this:
https://mysite.com/only-child-pages-of-this-page/*
then content will NOT play on the specific URL https://mysite.com/only-child-pages-of-this-page but WILL only play on https://mysite.com/only-child-pages-of-this-page/any-other-page

So if you want content to be available on your whole site (including the main domain), you will need to include BOTH the following:
https://mysite.com
https://mysite.com/*

However this sitll will not work for a url with extra GET data, such as:
https://mysite.com?data=123

So to include this you need add the * to the end without the slash, and this will inlcude the specific page as well as all child pages:
https://mysite.com*

My issue was that the OS X App Store on my MacBook was showing Updates available for both iTunes and Safari. I would click UPDATE and they would download and then say installing. But after supposedly installing, the new version was not available. When I ran Safari or iTunes it was still the old version. And then within a short period of time, they would both appear in the App Store again as an available Update.

So not sure what is causing the issue, but for whatever reason the updates are not being installed properly. So after going thru the update process several times I finally decided to look for another solution.

I found another way to do updates is to use the command line in Terminal.

First you can type this to get a list of available downloads (NOTE: that is a dash then a lower case L which stands for list):

 softwareupdate -v -l

This may take awhile, but will eventually return a list (if any) of available updates. Mine came back with this:

 Finding available software
  Software Update found the following new or updated software:
   * iTunesX-12.3
   iTunes (12.3), 238528K [recommended]

Now to install any specific update from the list you can type:

softwareupdate -v -i iTunesX-12.3

Or to install all the updates you can type:

softwareupdate -v -i -a

With the method above I was succesful at getting Safari to upgrade, but iTunes was still giving me a really hard time, and would not upgrade. You can not just delete iTunes and re-install it either as it is a protected file. But we can delete it from Terminal if we need to and then try re-installing it.

To Delete iTunes, type this in Terminal:

cd /Applications/

Then type the following (and enter your admin password if it asks):

sudo rm -rf iTunes.app/

Once you have deleted it, use the softwareupdate command above and try it again!

The Quick Enrol plugin for Moodle let’s you enrol a user into multiple courses at once, and makes enrolling much easier.

Based on the Quick Enrollment plugin by Adrien Jamot which is no longer supported.

Click here to DOWNLOAD Quick Enrol plugin v1.0

INSTALLATION

v1.0 currently works with Moodle 2.8 and 2.9. It may work with other versions but I not tested it yet.

Download and unzip the quickenrol folder.

Place the entire quickenrol folder in the /moodle/blocks/ folder.

Login as administrator and go to admin notifications. It should ask you to “upgrade database” to install. Note that this plugin does not add to or modify the database at all on installation (it will however add entries to databse when you enrol a student in a course).

Once installed, add the Quick Enrol block to your front page.

Click the “Enrol user in courses”, then choose the user and choose the courses you want them to be enrolled in (hold down CTRL on Windows or CMD on Mac to select multiple courses) and click SUBMIT … it’s that easy

Click here to DOWNLOAD Quick Enrol plugin v1.0

Okay so after several hours of messing around trying to figure out why my Samsung Galaxy S3 used to play the music I had on my SD Card, but now suddenly did not want to recognize it all, I found a solution.

STEP 1
Backup any music or other data you have on your SD Card.

STEP 2
Using My Files or any other file app (like ES File Explorer) copy one music file (only one) from your external sd card into your device Music folder.

STEP 3
Go to SETTINGS > MORE > STORAGE and choose FORMAT SD CARD. **** WARNING: This will delete everything on your SD Card. Make sure you backed it up before doing this. ****

STEP 4
Once it is formatted, choose UNMOUNT SD CARD.

STEP 5
Once it unmounts, choose MOUNT SD CARD.

STEP 6
Go back to My Files (or ES File Explorer) and copy the device Music folder to the root of your external SD Card. Do not individually copy stuff inside the Music folder, but choose the entire Music folder itself. When you copy the folder to the root of your external SD Card, this means that a new Music folder will appear alongside the Android folder.

STEP 7
Go to music app and you should now see two copies of the one file you copied over in Step 2.

STEP 8
Delete this file from your device Music folder and leave it in your SD Card Music folder.

STEP 9
Go to music app and there should now only be one copy.

STEP 10
Put all your music and data back on the SD Card now, but be careful NOT to copy any hidden files that were on the old SD Card. Only copy over .mp3 files or the specific data files you need.

Hope this helps!

I now have a Galaxy S3 running Android and although I love eSword, it is not available on Android, so instead I have been using MySword instead.

There are tons of free resources for eSword available and I thought it would be great if I could convert them to use with MySword.

It turns out that the file formats (for unlocked modules) are identical. So you simply need to change the extension name to get them to work.

Simply change the .bblx extension of the eSword Bible module to .bbl.mybible to make it a MySword Bible module.

That’s it!!

Thanks to Peter Pellerin at the following post for pointing it out:
http://www.biblesupport.com/topic/1415-instructions-for-making-your-own-mysword-modules/?p=4629