From: Samuel J S. <sst...@dp...> - 2006-02-01 20:29:32
|
I've come up with a workaround for this problem... I edited the "ticket_index_html.zpt" file and changed the following line: tal:attributes="value request/mail_to | python:here.getReplyTo() or '%s <%s>' % (here.from_name, here.from_email)" /> To: tal:attributes="value request/mail_to | python:here.getReplyTo() or '%s' % (here.from_email)" /> All it does is remove the automatic insertion of the recipient name and the <> around the recipient email address from the ticket screen which his what my users have been doing by hand... Works like a charm. Cheers, Sam Samuel J Stanaitis, Network Administrator Decorative Product Source, Inc. -----Original Message----- From: Kevin Campbell [mailto:ke...@lo...] Sent: Tuesday, January 24, 2006 4:25 PM To: sst...@dp... Subject: Re: [Mailmanager-users] MM 2.0.6 - Still getting "is not a valid email address" error. On Tue, Jan 24, 2006 at 02:22:05PM -0500, Samuel J Stanaitis wrote: > Initially it appeared that MM 2.0.6 had resolved the "is not a valid email > address" error. However it is happening again with a specific address, I'm > going to take a leap here and guess it has something to do with the format > of the address... > > Last, First M <First_M_Last@Domain.com> is not a valid email address. It's possible that that format is against standards, but I can't say offhand at the moment. > Should I figure out how to post bugs on SourceForge? :) Please. We use the list of bugs in sourceforge to check that we have cleared all known issues each time we release a new version. Without the bugs being filed through there it's possible that some fixes are lost when we merge our code branches. It also lets us get a rough idea of the quality of releases with regard to how many bugs exist and how quickly they are being resolved. Regards, Kevin -- Kevin Campbell Software Engineer Logicalware Ltd GPG Key: F480EC23 |