Releases: google/mail-importer
0.1.0 Initial release
Mail Importer 0.1.0
This is the initial release of Mail Importer for Gmail. It will import Thunderbird mailboxes as long as there are no invalid messages. (Invalid messages can occur for many reasons, but a common one is having an invalid From:
header.)
How can I run it?
As mentioned in the README, Mail Importer is not very user friendly. When you try your first import, you may want to test it on an account you don't care about first.
Building and Running
If you want to build and run Mail Importer yourself, follow the README instructions.
Downloading and Running
If you don't want to build from source, you can download the pre-packaged, runnable JAR and then run it like this:
java -jar mail-importer-0.1.0-jar-with-dependencies.jar --mailbox DIRECTORY
where DIRECTORY
is the Thunderbird mailbox to open.
Note that the Thunderbird Mail
directory usually has several sub-directories
called ImapMail
, OfflineCache
, and Mail
. Then under Mail
, you should
find individual accounts, like pop.mail.yahoo.com
or pop.csi.com
, and
Local Folders
. It is this last level of directory that contains the actual
mailbox.
For example, if you had old CompuServe mail on a Mac, you might run Mail
Importer like this:
java -jar ./target/mail-importer-1.0-SNAPSHOT-jar-with-dependencies.jar \
--mailbox /Users/me/Library/Thunderbird/my_profile/Mail/pop.csi.com
Authorizing the App
Note that when you run the app for the first time, it will print out a URL that you need to visit in order to authorize the application to manipulate your Gmail mailbox. When you visit the URL by copying it into your browser address bar, it will print out a code for you to copy. Copy that code back into Mail Importer where it prompts you.
For more information about this OAuth flow, see Using OAuth 2.0 for Installed Applications.
I found a bug! What do I do?
If you find a bug in Mail Importer, please use the Issue tracker on GitHub to report it.
A good bug report has:
- A summary of the problem.
- The version of Mail Importer, including whether it happened with a JAR built from source or the pre-packaged JAR.
- Information about the message that caused the problem, in order of preference:
- The original message.
- The headers from the original message.
- Redacted headers from the original message.
Don't include any private or confidential information as it will be publically available on GitHub.
If you can't provide the original due to confidentiality or privacy concerns, we understand that. Give
us as much info as you can and we'll try to ask questions or arrange a private way to get the data.
4. At least the last 50 lines of the console messages.