Lawrence Pit <[email protected]> wrote: > Hi Eric, > > > but that includes emails :) > > Yeah, sorry about the email format :[ Hope this time it's as expected.
Yep, you can check for deliverability of any message by checking: bogomips.org/unicorn-public/$MESSAGE_ID/ (or just look near the top of http://bogomips.org/unicorn-public/) Nothing hits the list until it hits the archives. I also suggest always Bcc:-ing yourself instead of having your mail client save to a "Sent" folder so you can: a) test deliverability (including the Message-ID: in headers if it's added by the server and not your client) b) get proper threading with any reply-to-all lists you're not subscribed to. > > I don't consider it the responsibility of the app server to sanitize it. > > fwiw, I agree :) ... similarly, why consider it the responsibility of > the app server to log it? it is an application level error, not a > unicorn error. I'm not entirely sure why unicorn logs it, either. I think it was already expected in 2009 for application servers to log that (thin/mongrel/...?) Similarly, I don't like the "timeout" feature of unicorn anymore, either since it encourages hiding bugs. There's no chance of removing either feature, of course. -- unsubscribe: [email protected] archive: http://bogomips.org/unicorn-public/
