- FITYK COMMAND LIST INSTALL
- FITYK COMMAND LIST ARCHIVE
- FITYK COMMAND LIST TRIAL
- FITYK COMMAND LIST DOWNLOAD
FITYK COMMAND LIST TRIAL
Again, cause it may take some trial & error, plus you don't want to spam yourself.
Turn OFF emails for any initial admin accounts. Make it private initially (as the migration of messages may take some trial & error). # (As these are the correctly formatted Dates) # Rename any "X-Original-Date:" fields to be "Date:" # These are invalid and are formatted like: # Ignore any old Dates without a timezone on the end. # invalid "Date:" and replacing it with "X-Original-Date:". # is immediately followed by a valid "X-Original-Date:". # Some older emails (circa 2004) have an invalid "Date:" format, which # These next two checks work together to clean up bad dates in old emails. Create a /etc/postfix/header_checks file (see header_checks setting above). header_checks = regexp:/etc/postfix/header_checks (Lets you modify/cleanup email headers, if needed, before sending to Google Groups. 
message_size_limit = 0 (Just in case you have large messages in your archives, you don't want postfix blocking them. Yes, there really should be square brackets in this value) relayhost = :587 (Google Apps SMTP relay host/port. (Ensures postfix "acts" like your Google Apps domain) Modify the basic setup to point at Google's SMTP Relay:. Your installation of postfix may be different) Using postfix + Google Apps SMTP Relay preserves the existing From: field, while using Gmail SMTP doesn't. Why go through all this trouble? Well, again, it's all about the From: field. FITYK COMMAND LIST INSTALL
Install postfix and configure to use Google Apps SMTP Relay
I chose to setup three "dummy" accounts just for the purpose of sending these emails, so that I was able to send up to 30K messages in a 24 hour period. So, if you have more than 10,000 messages in your old archves, you'll need to plan to send them in batchs of 10K, either on seperate days or via separate user accounts. NOTE: Google Apps SMTP Relay has a sending limit of 10,000 messages per day per user account. WARNING: PLEASE BE SURE TO REMOVE THESE SETTINGS AFTER YOU HAVE FINISHED THE MIGRATION! You likely don't want anyone who is able to "spoof" your IP address to send emails via this SMTP Relay. Left SMTP Auth and TLS both turned off (couldn't get postfix to work right with either enabled). Authentication: "Only accept email from specific IP addresses" (Added my computer's IP). In setting up my SMTP Relay, I gave it the following options: Scroll down to find the "SMTP relay service" setting. Go to "Apps" -> "Google Apps" -> "Gmail" -> "Advanced Settings". Here's another good reference on Google Apps SMTP Relay vs GMail SMTP: But, you should avoid GMail's SMTP, as using it will cause your migrated emails to all appear as if they came from one email address / user account in Google Groups. If you don't have Google Apps, you could technically use any SMTP server. Setup Google Apps SMTP Relayīecause GMail's SMTP will ALWAYS change the From: field, we'll use our Google Apps SMTP Relay. A list of all subscribers to a single SourceForge mailing list can be found at: /admin/mailman//subscribers/displayĮxport this subscriber list for each SF mailing list. FITYK COMMAND LIST ARCHIVE
wget -user= -ask-password Įxport this mbox archive for each SF mailing list.
In that situation, wget should still work
FITYK COMMAND LIST DOWNLOAD
Larger archives may fail to download via a browser. 
You will be prompted for your SourceForge credentials. SourceForge provides downloadable 'mbox' exports from:. Steps Export archives in mbox format from SourceForge Download the above mbox_send.py and ensure Python is installed. So, some instructions may be Ubuntu/Debian specific. I performed this migration from an Ubuntu 14.04 VM. This mbox_send.py script to (re-)send all emails in the 'mbox' to Google Group:. Migration of Mailing Lists from SourceForge to GoogleGroups References
0 kommentar(er)
