-
|
Hi! While Inbucket appears to meet our requirements, I am experiencing issues with data persistence. After reviewing the Inbucket Dockerfile, I noticed that the volumes are passed to the environment parameter INBUCKET_STORAGE_PARAMS with the folder /storage. Sending emails through the Docker container works correctly, but after restarting the container (using either "docker restart xxx" or "docker stop xxx" followed by "docker start xxx" but not "docker run"), the monitor is empty of emails, despite the fact that the data from the emails is still present in the /storage folder. I would appreciate any assistance you could provide to resolve this issue. Thank you. info logs from the restarts The command I am using to start the container is and the empty monitor + data storage is on the following picture You will see that i am not using port localhost:9000 because I am using an nginx reverse proxy for our local dev envs. Edit: |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
Yes, I think you have the correct understanding -- the contents of the monitor is in-memory, and does not survive a restart, while the content of mailboxes do. If your team only needs to check a few mailboxes with consistent names, you might just add links to them in the greeting.html file. The UI will also store recently accessed mailbox names via browser cookie to make switching between them quick once the user has opened them. I am currently adding scripting/extension support to Inbucket to facilitate more complex use cases. I can't promise it will help, but I'm interested to hear a bit more about your teams needs so that I can take them into consideration as I implement extension points. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @jhillyerd, Thank you a lot for your prompt answer. With the awesome-beautiful tool you made I am able to send a new email and if the sender is the same, then i can review the previous email. On our scenarios, we will need to remember the sender so that we can compare with the previous emails sent to the same sender. Another scenario is to test how the email can be parsed and how it looks inside the body html. Unfortunately, the emails used by the developers are all over the place and by design it is not possible to just use standard email addresses for our test case scenarios. I would love to see another tab near the monitor where we would be able to see the inbox, old and new emails, in one place, like the outlook office does. |
Beta Was this translation helpful? Give feedback.
-
|
It sounds like you would benefit from a "catch all mailbox" similar to what is discussed in #199 That is definitely something I am going to address with scripting, so that the From address (or sending IP addr) could be used to choose which mailbox to write to; or all mail regardless of From/To could go to a single mailbox, etc. I can't really give a timeline on when it will be available, but I do already have some basic scripting features working in development. I'll being pinging discussions and bugs that could benefit from scripting when I have a beta version available to experiment with. |
Beta Was this translation helpful? Give feedback.
It sounds like you would benefit from a "catch all mailbox" similar to what is discussed in #199
That is definitely something I am going to address with scripting, so that the From address (or sending IP addr) could be used to choose which mailbox to write to; or all mail regardless of From/To could go to a single mailbox, etc.
I can't really give a timeline on when it will be available, but I do already have some basic scripting features working in development. I'll being pinging discussions and bugs that could benefit from scripting when I have a beta version available to experiment with.