4 ms·
Part of the problem has traditionally been that email servers haven't been as easy to "hack" as web servers have. That was a failing on the part of the develope
by baudehlo 13y ago
Part of the problem has traditionally been that email servers haven't been as easy to "hack" as web servers have. That was a failing on the part of the developers of those servers.
Thankfully now you have things like Qpsmtpd, James, Lamson and Haraka which can do those things for you. But not many people install those servers. I'd love to see that change (for obvious reasons).
- e12e 13y agoPartly. But you've been able to do the equivalent of: echo "|magic-program" > .forward For a long, long time. Granted, it's a little unclear what happens if you manage to overload your server doing that, but in general MTAs are pretty good at taking care of your mail, either queueing and delivering, or giving up somewhat gracefully. The trick is to make sure that the "magic-program" is simple and robust -- and that isn't quite as hard as most people think, if you don't require it to parse arbitrary emails -- just accept and parse clearly valid ones, and reject everything else. Now, if you require to handle enough incoming requests that forking a process per mail is a problem ... you probably need to fix your architecture.
- baudehlo 13y agoThe fragility of parsing emails is a big problem though. But I agree that for the equivalent of webhooks it is the perfect platform, and simple scripts work. Except at scale.