41–50 of 51 posts
I prefer self-hosting MailHog: https://github.com/mailhog/MailHog
I don't want to burst bubbles, but postfix with few lines of config can redirect all email to DEVs. You really want, whenever possible, to test everything using real tools. Doubly so, using tools you'll use it PROD. However, at least postfix is de-facto standard. apt-get install postfix, postfix-pcre bsd-mailx, config and done. Here's an example redirecting ALL outgoing emails, UNLESS they are to your OK domains. Red…
It's always fascinating to me when people say "not to burst your bubble but it's really simple to use this other tool which can already do the task", and then write an essay about all the workarounds they had to apply to make the other tool work
pünicode.com. Any local part will create a temp cache that you can check to see if your email system can deliver to international local and/or domain parts. EG, send an email to josé@pünicode.com and see it show up at pünicode.com/emails/josé.
I prefer self-hosting MailHog: https://github.com/mailhog/MailHog
Really cool. I couldn't find it documented anywhere, but if you save the unique (guid) url generated, how long is that available for? "Forever"?
I will probably update it to delete accounts that have been inactive for a year or something.
I had no idea on the availability of all the various options, which leads to the question: Where would one find examples of similar network test servers for other protocols/functions?
For example:
- A SAML IdP - Define accounts and complete a login, allow debug of request/response.
- A DNS Server - Define local domains and records, control whether Internet domains are resolvable or just local ‘corporate’ records.
- Syslog Server - Catch logs and make them temporarily available. (usually syslogd works for this, but maybe test harnesses have advantages).
- SNMP - Trap destination to capture/show alerts
I have a rule that any time someone ships a server, they're required to also ship a version that supports client testing purposes. Of course nobody has ever observed my rule. Doesn't make it a bad rule...
I have a rule that any time someone ships a server, they're required to also ship a version that supports client testing purposes. Of course nobody has ever observed my rule. Doesn't make it a bad rule...
I have used tools like these for nearly a decade and find them invaluable. My current favourite is Mailpit [1]. The “OG” I would consider Mailcatcher [2] from my Rails days [1] https://github.com/axllent/mailpit [2] https://mailcatcher.me/
An API driven approach like Msgdrop is more flexible, as many apps can’t configure a fake SMTP server, especially if you use tools like Mailgun or SendGrid.