Done.

Yes, that should be fine. Patches welcome.

Would that be something we can do under the feature freeze?

I think we should put the non-To: addresses through 
horde_form_type_email's validate method.

Yes, at least for the reply-to field. The problem is that if a user 
enters a mis-formatted reply-to address then all replies are bounced 
and, of course, the user has no idea why he's not receiving any mail. 
A simple check to ensure proper formatting (e.g no spaces) would be 
useful to protect users from their own mistakes and spare us from time 
wasted digging through mail logs to determine the problem.

I think reply-to should be checked as well, since it's more like 
from_addr than that other two.

I tend to think that this might be too much for a sanity check. The 
purpose of the existing check is to make sure that users can set fake 
sender addresses. This has nothing to do with recipient addresses.

If that email confirmation could be applied to the other fields as 
well that'd be great. I think there should be some form of email 
address validation wherever a user is able to enter an email address. 
Cheers.

Looks like it's just from_addr.

Does that apply to the other 3 fields as well (alias, reply-to and bcc)?

Horde 3.2 has a configuration setting to require email confirmation of 
from addresses ($conf['user']['verify_from_addr']). Is that sufficient?

Ok, I'm submitting this again because the last couple times I 
submitted I was taken back to the create a new ticket screen without 
confirmation of the submission and a ticket search returned nothing..



In the Personal Information settings users are able to successfully 
enter mis-formatted email addresses, e.g. "xyz@te st.com", with a 
blank space in the address. This happens in the following fields: 
from, reply-to, alias, bcc.



We're in the process of setting up IMP 4.2 therefore we havent been 
able to test in that version yet.