During the past months, we have discovered an annoying usability
problem. Users enter invalid email addresses (e.g. separated by " "
or ", " instead of “,”, or lacking a domain part). RT3 doesn’t seem
to handle this situation very gracefully.
What are my options to fix this? Two-stage ticket creation/reply
might help, but how easy is it to implement? Should I verify the
addresses on the client, using JavaScript?
Current mail filters: many dial-up/DSL/cable modem hosts, and the
following domains: atlas.cz, bigpond.com, di-ve.com, hotmail.com,
netscape.net, postino.it, tiscali.co.uk, tiscali.cz, tiscali.it, voila.fr.
Users enter invalid email addresses (e.g. separated by " "
or ", " instead of “,”, or lacking a domain part). RT3 doesn’t seem
to handle this situation very gracefully.
…
What are my options to fix this?
I’m not sure if this answers your question, but did you read
perldoc -q address ?
Cheers,
Koos
Koos Pol koos_pol@nl.compuware.com writes:> On Thursday 29 April 2004 23:44, Florian Weimer wrote:
Users enter invalid email addresses (e.g. separated by " "
or ", " instead of “,”, or lacking a domain part). RT3 doesn’t seem
to handle this situation very gracefully.
…
What are my options to fix this?
I’m not sure if this answers your question, but did you read
perldoc -q address ?
This is actually the easy part. How would I integrate that into RT,
so that the user is given the possibility to correct his mistake?
Current mail filters: many dial-up/DSL/cable modem hosts, and the
following domains: atlas.cz, bigpond.com, di-ve.com, hotmail.com,
jumpy.it, libero.it, netscape.net, postino.it, simplesnet.pt,
tiscali.co.uk, tiscali.cz, tiscali.it, voila.fr.