61–70 of 91 posts
On my laptop, where I do all of my development work, I just configured Postfix to send everything to plain files: http://harold.internal.org/configuring-a-dev-box-mail-server... I like this a lot better than sending stuff out across the network.
> No fake recipient email addresses anymore, use real ones! What if you send to the wrong server by mistake; not to develmail.com? develmai.com won't save your butt then. Say something breaks in your configuration, and some mail-related layer resolves the address directly to an MX host and sends it there instead of the SMTP forwarding host it is supposed to be using ... know what I mean? If you don't want packets to…
On my laptop, where I do all of my development work, I just configured Postfix to send everything to plain files: http://harold.internal.org/configuring-a-dev-box-mail-server... I like this a lot better than sending stuff out across the network.
Personally, my local SMTP actually sends email, because I DO want legitimate email (mutt, cron) though, so I'd be scared to mix up two local smtp instances.
#sudo python -m smtpd -n -c DebuggingServer localhost:25
Works pretty well for me.
So this is useful for: 1. developing software that sends e-mails, but not having to set up a test environment/pray you don't break production, and 2. testing out new software that insists on sending e-mail when you're just one person in a small/localhost-only environment. I love it. One thing I'm sad to see is that there seems to be no TLS/STARTTLS support on the side of develmail. Given that TLS can be a bit finicky…
Please stop hijacking scrolling. Thankyou.
> No fake recipient email addresses anymore, use real ones! What if you send to the wrong server by mistake; not to develmail.com? develmai.com won't save your butt then. Say something breaks in your configuration, and some mail-related layer resolves the address directly to an MX host and sends it there instead of the SMTP forwarding host it is supposed to be using ... know what I mean? If you don't want packets to…
You're right, but it's just a suggestion. It's really up to you how you use the service, sometimes it might be handy to see real data :)
I'm not going to involve some random thing on the Internet in my test setup!
For one thing, I'm pretty sure I'd be violating a document that I signed about promising to safeguard my client's IT security, secrets and intellectual property.
Real data could be sensitive.
Anything of this sort that you set up will eventually be used by other people, who don't always know the full ramifications of what they are using. Somewhere down the line, someone will leak something into the test system. Maybe a user ID or password. Names of clients. Whatever.
Also, a test system has to be reliably operational. According to Murphy's Law, someone's thing you depend on on the Internet gonna disappear exactly when a lot of integration activity starts happening before a release.
Lastly, you should control every aspect of a test tool. Exactly how someone's SMTP thing handles SMTP could change in subtle ways from one day to the next.
On my laptop, where I do all of my development work, I just configured Postfix to send everything to plain files: http://harold.internal.org/configuring-a-dev-box-mail-server... I like this a lot better than sending stuff out across the network.
https://github.com/mailhog/MailHog looks like a really nice alternative, where you can also test HTML mail, etc. Personally, my local SMTP actually sends email, because I DO want legitimate email (mutt, cron) though, so I'd be scared to mix up two local smtp instances.
On my laptop, where I do all of my development work, I just configured Postfix to send everything to plain files: http://harold.internal.org/configuring-a-dev-box-mail-server... I like this a lot better than sending stuff out across the network.
Mailcatcher is an even simpler solution (assuming you can install rubygems): https://mailcatcher.me/