domainaware / parsedmarc

A Python package and CLI for parsing aggregate and forensic DMARC reports
https://domainaware.github.io/parsedmarc/
Apache License 2.0
1.02k stars 223 forks source link

Kibana issues #172

Closed ibiriebob closed 4 years ago

ibiriebob commented 4 years ago

I first configured the tool on a vm workstation using ubuntu 18.4 and got everything working correctly and then move this to a server running the same version of ubuntu. It appears all of the emails are being pulled correctly, however, I am not seeing anything within the Kibana dashboard.

I haven't processed that many emails just yet, I have about 10,000 saves in a folder and slowly moving them to be pulled.

The parsedmarc.ini is similar to the one below. Please let me know if you need any additional information.

[general]

Save aggregate and forensic reports to Elasticsearch

save_aggregate = True save_forensic = True

[imap]

Log into the DMARC report email address and download data.

host = mail.yourdomain.com port = 143 ssl = TFalse user = dmarc@yourdomain.com password = your_password_here watch = True

[elasticsearch]

Send data to Elastichsearch, which listens on port 9200.

hosts = 127.0.0.1:9200 ssl = False

[smtp]

For sending email

host = mail.yourdomain.com port = 587 ssl = True user = dmarc@yourdomain.com password = your_password_here from = dmarc@yourdomain.com

send results to this address

to = admin@yourdomain.com

ibiriebob commented 4 years ago

Does it make a difference using ubuntu server vs using workstation? I have the identical configuration for both and it is working on the workstation configuration. Do I need to configure different settings?

ibiriebob commented 4 years ago

So I am trying to figure this out and see that the elastic.py process doesn't appear to be running on the server configuration as appose to the workstation configuration after the move process.

image

image

ibiriebob commented 4 years ago

I just created a new vm using Ubuntu workstation instead of server and it is working fine.