Black Hole
May contain traces of nut
Somebody here understand the pros and cons of the email "reply to" field?
A club I am associated with (U3A) has set up a management system on-line database, which is capable of sending out group emails to members registered email addresses, while the email addresses themselves remain private on the system (amongst other handy things like membership fees etc etc). I could use this facility for one of my club responsibilities, so far I have used a dedicated Gmail account for it.
The trouble is that, so far, emails that have originated from the system have a "black hole" (pun not intended) source address, and no "reply to" field so that replies would default to the black hole destination unless the recipient edits an appropriate destination address into the "to" field before clicking "send". Emails have a line of text in them saying "when replying, please send to xxxx", but that's not a very user-friendly way of going about things and relies of the user getting it right (and many of that age group are only just coping with computer technology as it is).
It could be that the administrators don't know about "reply to", and need educating. If there were a reply to option when authoring an outgoing email (which a number of people can do with sufficient permissions), the replies (if any are expected) could be routed to the right place automatically. Am I right?
On the other hand, it could be that "reply to" is deprecated or maybe frowned on because of being a spam indicator.
My local U3A did not create the database system in the first place, some appropriately knowledgeable people elsewhere within U3A came up with it and developed it, and it is gradually propagating through the U3As as more get to hear about it and apply to use it (replacing tedious and error-prone manual record keeping). As far as I can make out it is all one huge database, with permissions sectioning it off for the various individual U3As. If the developers have not thought of "reply to", we will have to feed this back to them. On the other hand our local administrators may have simply missed a trick.
A club I am associated with (U3A) has set up a management system on-line database, which is capable of sending out group emails to members registered email addresses, while the email addresses themselves remain private on the system (amongst other handy things like membership fees etc etc). I could use this facility for one of my club responsibilities, so far I have used a dedicated Gmail account for it.
The trouble is that, so far, emails that have originated from the system have a "black hole" (pun not intended) source address, and no "reply to" field so that replies would default to the black hole destination unless the recipient edits an appropriate destination address into the "to" field before clicking "send". Emails have a line of text in them saying "when replying, please send to xxxx", but that's not a very user-friendly way of going about things and relies of the user getting it right (and many of that age group are only just coping with computer technology as it is).
It could be that the administrators don't know about "reply to", and need educating. If there were a reply to option when authoring an outgoing email (which a number of people can do with sufficient permissions), the replies (if any are expected) could be routed to the right place automatically. Am I right?
On the other hand, it could be that "reply to" is deprecated or maybe frowned on because of being a spam indicator.
My local U3A did not create the database system in the first place, some appropriately knowledgeable people elsewhere within U3A came up with it and developed it, and it is gradually propagating through the U3As as more get to hear about it and apply to use it (replacing tedious and error-prone manual record keeping). As far as I can make out it is all one huge database, with permissions sectioning it off for the various individual U3As. If the developers have not thought of "reply to", we will have to feed this back to them. On the other hand our local administrators may have simply missed a trick.