comms-analyzer-toolbox

comms-analyzer-toolbox copied to clipboard

Execute docker environment with : docker run --rm -ti -p 5601:5601 --mount type=bind,source=F:/comms-analyzer-toolbox/Files,target=/files --mount type=bind,source=F:/comms-analyzer-toolbox/Elastic,target=/toolbox/elasticsearch/data comms-analyzer-toolbox:latest python /toolbox/elasticsearch-gmail/src/index_emails.py --infile=/files/incoming.mbox --init=True --index-bodies=True --index-bodies-ignore-content-types=application,image --index-bodies-html-parser=html5lib --index-name=comm_data

testing with : import mailbox i = 1 for message in mailbox.mbox('incoming.mbox'): i=+1 print(i)

from inside docker container via exec indicates 15000 records

I refactored from --v as it was also failing.

Result is: {"type":"log","@timestamp":"2018-07-26T14:49:20Z","tags":["warning","elasticsearch","admin"],"pid":61,"message":"Unable to revive connection: http://localhost:9200/"} {"type":"log","@timestamp":"2018-07-26T14:49:20Z","tags":["warning","elasticsearch","admin"],"pid":61,"message":"No living connections"}

Launching MBOX email indexer....

INFO:root:Starting import from file /files/incoming.mbox INFO:root:Import done - total count 0

MBOX email indexing is complete!

Elastic appears to be running as per process

Not sure if anyone is still working on tis but i thought i would ask before going in for a full refactor.....

I have not re-visited this project in some time. If you've identified a fix/change to make it clearer how to run or to simply fix an error, please submit a PR and I'll incorporate it.

Thanks!