We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It would be nice if GreenMail had an option to explicitly define error responses to test error handling in user's code.
For example check MailHog, a fake SMTP server. It has a special mode to randomly reject connections, authentications, etc.
Another good example is Netflix's Chaos Monkey that is used to test distributed systems.
The text was updated successfully, but these errors were encountered:
Thanks for the input.
We have something like this planned in #40 - where you can define event rules. Do you have any concrete error cases in mind?
Sorry, something went wrong.
Do you have any concrete error cases in mind?
I guess cases available in MailHog would be a good start:
SMTPAddressFailedException
SMTPSenderFailedException
These should cover most of the basic SMTP errors. I'm not sure about IMAP, though.
No branches or pull requests
It would be nice if GreenMail had an option to explicitly define error responses to test error handling in user's code.
For example check MailHog, a fake SMTP server. It has a special mode to randomly reject connections, authentications, etc.
Another good example is Netflix's Chaos Monkey that is used to test distributed systems.
The text was updated successfully, but these errors were encountered: