DKIM (Domain keys identified Mail) is a scheme for which allows a receiver to verify that the email originated (or authorized) by the domain’s owner via a digital signature.
Having DKIM signature adds credibility to the email messages sent from the origin host/domain, which is crucial for automated emailing system to avoid the messages from being suspected as SPAM email or spoofed email.
I managed to set up DKIM for an academic journal website which I’ve managed. The journal’s runs on Open Journal System web application, the addition of DKIM is crucial to avoid GMail or Microsoft Live from labeling the automated emails sent from the academic journal from being labeled as spam.
At first I found that the DKIM scheme that I’ve setup was running fine and the email messages was verified correctly from my Organizational email domain. However, I’ve noticed a problem when the automated email sent from OJS is not properly verified by Gmail-addressed account (@gmail.com). Upon inspection in the email header, I’ve noticed that the GMail marked the DKIM signature sent from my domain as “bad format”. Example below:
After hours of searching and debugging, including referring to the DKIM NS TXT record for reference, I finally found out that Gmail treat the “g=*” optional parameter as required, and thus I’ve to append “;g=*” to the DKIM TXT record on my domains’ DNS record.
The 1Malaysia email is touted to be more secure than the average email provider, but a quick search reveals that the domain is still alive at the time of this writing, but is giving invalid & untrusted “self-sign” security certificate: https://www.myemail.my/
What has happened to this grandeur project??
p/s: I’ve been prepping to get my hands on the said “USB Biometric” device a few years ago and to use it on my Linux system. Seems that day have never come :(
Here’s how to download all emails from your GMail account with Gmvault:
Download and setting up gmvault
1. First you need to install python-pip
sudo apt-get install python-pip
2. Then using ‘pip’, install gmvault
sudo pip install gmvault
3. Finally you can sync and backup GMail accounts with ‘gmvault‘
gmvault sync your_username @ gmail.com
4. gmvault will ask you to authenticate yourselves with GMail, and after that, the syncronization process starts. gmvault stores all the gmail backup in the ‘gmvault-db‘ directory.
p/s: Some users encounters error telling that the “All Mail folder is not visible”. You can enable All Mail folder visibility by checking the “Show in IMAP” box in Settings->Labels. Also, IMAP access should also be enabled for this to work.
p/s 2: It might not be obvious right now why you need to backup your emails when Gmail has gigabytes of storage. But according to Gmail discussions group, Google can and might disable access to all of its services, locking the users out from their emails forever.
GPG or the GNU Privacy Guard is a free and open source software that implements OpenPGP public-key cryptography message format (RFC4880). You can use GPG to encrypt, decrypt, sign and verify files or emails. To use GPG, you need to generate the public-key/private-key pairs in your computer by running this command, and choose the default option
The application will ask you to enter your ID and passphrase, make sure you choose a strong passphrase to guarantee the safety and security of your keys.
Encrypting and Decrypting Files
You can use GPG to encrypt files, it can be only decrypted by those who have your public-key. The command that can be used to encrypt file is :
gpg --out encrypted_file.txt --encrypt original_file.txt
Run this command to decrypt. Files encrypted with private key can only be decrypted with public key and vice-versa.
gpg --out decrypted.txt --decrypt encrypted_file.txt
Signing Email or body of texts
Alternatively, you can chose to sign emails/texts instead of encrypting them. Signing files is a way to ensure that the message/texts/emails are from the right sender and its content has not been tempered with. You can run this command to sign email or texts :
gpg --clearsign original_text.txt
This will produce a signature file which content the original text with PGP signature embedded at the bottom of the message.
To verify it (assuming you have the public key), you need to run this command:
gpg --verify original_text.txt.asc