Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Email log retention #10

Open
JeffZwolle opened this issue Nov 25, 2021 · 4 comments
Open

Email log retention #10

JeffZwolle opened this issue Nov 25, 2021 · 4 comments

Comments

@JeffZwolle
Copy link

Hi Privex,

I have implemented this “WebUI for email logs”-solution and am happy with it. Thanks.

What is the retention time (in days) for log entries in the RethinkDB database?
Is it configurable somewhere?
Or is a separate daily cronjob needed? I have zero experience with RethinkDB. Maybe you know what command is needed to delete log entries older then 90 days?

Jeff

@drlight17
Copy link

Hi Privex,

I have implemented this “WebUI for email logs”-solution and am happy with it. Thanks.

What is the retention time (in days) for log entries in the RethinkDB database? Is it configurable somewhere? Or is a separate daily cronjob needed? I have zero experience with RethinkDB. Maybe you know what command is needed to delete log entries older then 90 days?

Jeff

Check my fork.. Work is still in progress however.

@JeffZwolle
Copy link
Author

@drlight17
Thank you.
Definitely interesting.

@JeffZwolle
Copy link
Author

@drlight17

I did not see an issues tab on your repository.
https://stackoverflow.com/questions/29692626/why-is-issues-tab-not-present-in-my-repos-github-page

That is why I now try to contact you here to ask my question about migration:

As you know, previously I had Privex postfix-parser installed.
Now I would like to switch to drlight17 mta-log-parser.
Do I need to start with an empty database or can mta-log-parser continue in the same database that postfix-parser was also using?

@drlight17
Copy link

drlight17 commented Jul 21, 2023

@drlight17

I did not see an issues tab on your repository. https://stackoverflow.com/questions/29692626/why-is-issues-tab-not-present-in-my-repos-github-page

Hmm... Funny. Somehow the issues were swiched off in repo settings. Thanks. I returned them. =)

That is why I now try to contact you here to ask my question about migration:

As you know, previously I had Privex postfix-parser installed. Now I would like to switch to drlight17 mta-log-parser. Do I need to start with an empty database or can mta-log-parser continue in the same database that postfix-parser was also using?

Yes, I think you can save your database as it's structure is generally the same. But to be safe do the backup before switch to mta-log-parser. Try and make an issue if there are troubles.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants