-
Notifications
You must be signed in to change notification settings - Fork 6
Home
First, you'll need to configure Exchange so that Timberwolf can impersonate your target users.
Then, you'll need to make sure Timberwolf can be authenticated as the right user.
Once you've got that set up, run this to import your first batch of email:
java -jar timberwolf-0.1.0.XXXX.jar --domain MY.LDAP.DOMAIN \
--exchange-url https://mail.example.com/ews/exchange.asmx \
--hbase-clientport 1234 --hbase-quorum hbase.example.com \
--hbase-table myemail \
--hbase-metadata-table myemailtimes
(To see a list of all the options Timberwolf supports, run java -jar timberwolf-0.1.0.XXX.jar -h
.)
Depending on how much email you have to ingest, that will run for a few seconds or a few hours. We've seen Timberwolf ingest 250,000 emails per hour before it runs into Exchange throttling limits, but it may run differently in your environment. When it's done, the table named by --hbase-table
will have all your past email in it.
Once you've successfully ingested some email, Timberwolf will use the table at the --hbase-metadata-table
argument to keep track of where it left off ingesting, so that if you run it again with the same arguments you'll only get new messages. To ingest email periodically, run Timberwolf as part of a cron job or as part of another regularly-invoked service.