3 ms·
It's probably dependent on the type of site, then. If you're doing CRM, then that's very different than, say, updates on an order I just placed at an online mer
by kylemaxwell 15y ago
It's probably dependent on the type of site, then. If you're doing CRM, then that's very different than, say, updates on an order I just placed at an online merchant.
- pardner 15y agoThat makes sense. If my app was dealing with, say, medical records info, we would assuredly not want to forward mis-replies... in that case it would make more sense to use an auto responder that might say something like "To protect the security of your personal info ..."
- the_bear 15y agoYeah, this is only a problem if you're sending a notification on behalf of another user, like if tasks/events/contacts/leads are assigned by one user to another. I'm considering fixing this by auto-forwarding any replies, but then that has the same problem as a no-reply address in the event that a user actually does want to reach us. There's also another problem which is that tons of people have auto-replies for every single email they receive (not just when they're out of the office). I filter them all out, but I'm always concerned that there could be a false positive.