non useful log about wrong e-mail address format

This is the place to report bugs and get support. When posting in this forum, please always provide as much detail as possible.

Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum, do not report it as a bug.

This is the place to report bugs and get support

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.
Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum.
This thread is closed to new posts. You must sign in to post in the forums.
11/28/2009 11:38:10 AM
Gravatar
Total Posts 116
http://www.zoomicon.com http://birbilis.spaces.live.com http://www.delicious.com/birbilis http://twitter.com/Zoomicon

Re: non useful log about wrong e-mail address format

support for non-latin e-mail bodies is too needed if it doesn't exist already

also from what I understand you can define the mail template at email.config or something? Why not define/edit visually a template (and maybe have dropdown to choose from some ready made ones and add yours there too [with option to be portal global maybe if user is admin]) at the contact form settings and/or at site e-mail settings?

11/28/2009 11:45:24 AM
Gravatar
Total Posts 18439

Re: non useful log about wrong e-mail address format

I will add a splitter support but I think we should pick either , or ; not both and I will add info about the splitter in the help link. Though I guess if I pick comma I can just replace semi colon with comma before splitting.

I was also thinking about making an option where the user could pick from a list and it could go to different addresses. Like maybe if the splitter is | we make a choice dropdown and also include an alias with a | splitter so we don't show the real address in the dropdown so the same form could have a choice for Tech Support, Sales etc.

So maybe we have email address like:

techsupport1@myssite.com,techsupport2@mysite.com|sales@myssite.com

and an alias like

Support|Sales

and from that we can show a dropdown choice to the user with Sales or Support, then further split by comma to send to the different addresses.

Best,

Joe

11/28/2009 11:49:41 AM
Gravatar
Total Posts 18439

Re: non useful log about wrong e-mail address format

also from what I understand you can define the mail template at email.config or something? Why not define/edit visually a template (and maybe have dropdown to choose from some ready made ones and add yours there too [with option to be portal global maybe if user is admin]) at the contact form settings and/or at site e-mail settings?

There are a million possible improvements to any given feature, everything progresses incrementally and according to my own priorities to advance the project and make a living.

Best,

Joe

11/28/2009 12:12:07 PM
Gravatar
Total Posts 18439

Re: non useful log about wrong e-mail address format

I just added support for the .NET allowed encodings in my copy so this will be in the next version.

The history is that mojoPortal began it's life under .NET 1.1 which did not support anything but ascii, I found DotNetOpenMail and it was used by default and was a better option for a long time in mojoPortal but no-one was maintaining that project so it began to show problems and limitations over time. Apparently the support for utf8 and others was added in .NET 2.0 but I did not notice it because DotNetOpenMail was still working well at that point and there was no reason to change. I have not had complaints about encoding problems and only realized that .NET mail classes support these encodings today after researching to help you.

Going forward I will remove DotNetOpenMail since it now has various problems and limitations and the .NET mail classes are better at this point.

Best,

Joe

11/28/2009 12:49:13 PM
Gravatar
Total Posts 116
http://www.zoomicon.com http://birbilis.spaces.live.com http://www.delicious.com/birbilis http://twitter.com/Zoomicon

Re: non useful log about wrong e-mail address format

regarding the splitter, I think Unix style is ; and MS style used to be , in the past (in older Outlook Express if I remember well)

now Outlook 2007 supports both (changes , to ; as you write more addresses at say the To field)

11/28/2009 12:55:13 PM
Gravatar
Total Posts 18439

Re: non useful log about wrong e-mail address format

I will make it support both by just replace ; with , before splitting.

Best,

Joe

11/28/2009 12:58:49 PM
Gravatar
Total Posts 18439

Re: non useful log about wrong e-mail address format

If I produce a build with the utf-8 support would you be willing to test it for me using some Greek chars in the email? I'd like to make sure it is going to work before I completely remove DotNetOpenMail. I will also include the splitting in the build so you can set it back to multiple addresses like you had before.

Actually it won't really require a full installation I could just send you an updated mojoPortal.NET.dll after I complete the changes.

Best,

Joe

11/28/2009 12:59:25 PM
Gravatar
Total Posts 116
http://www.zoomicon.com http://birbilis.spaces.live.com http://www.delicious.com/birbilis http://twitter.com/Zoomicon

Re: non useful log about wrong e-mail address format

regarding the aliases, it could use the standard style of

 username <email>

and also the syntax

 username [email]

that Unix used to support (think I remember this well) and which Outlook converts to <...> (try writing geo [test@test.com] and pressing TAB at To field in a new mail at outlook 2007)

in fact that syntax should be available everywhere in mojoPortal where you define an e-mail address (using < and > in the XML is problematic - e.g. the syntax highlighter of Visual Web Designer chokes when writing "george <geo@test.com>" and parses it wrong and not sure if &lt; and &gt; are usable inside the XML string - outside of it would be clumsy to write since you'd have to concat multiple strings there). But you could allow "person [email]" in all strings and convert [ and ] to < and > before you pass it to MailAddress factory/constructor (check first in case it already supports the [...] and from which version and up - the <..> it should support for sure I believe, so you could use the "name" from the "name <mail>" for dropdowns if user gave one and if the name is empty show the mail [maybe MailAddress parses/splits it for you and gives you the parts already, checkout its properties/methods])

11/28/2009 1:11:08 PM
Gravatar
Total Posts 18439

Re: non useful log about wrong e-mail address format

I'm not talking about aliases for the email message itself what I meant was to not reveal the email address in the dropdown list that the user picks we would alias it in the dropdown with a simple string like Support or Sales. When it send the message it will just use the email address. If no alias is provided it will just list the email address in the dropdown. The alias in the dropdown could still refer to more than one email address, so the Support alias could still send to multiple support addresses separated by commas if needed.

11/28/2009 1:19:08 PM
Gravatar
Total Posts 116
http://www.zoomicon.com http://birbilis.spaces.live.com http://www.delicious.com/birbilis http://twitter.com/Zoomicon

Re: non useful log about wrong e-mail address format

but anyway, does it currently support the 

name <mail> 

and 

name [mail]

formats for addresses or just the plain e-mail?

(feel free to send me dll to try)

11/28/2009 1:27:04 PM
Gravatar
Total Posts 18439

Re: non useful log about wrong e-mail address format

I'll send the dll shortly, backup your original just in case. The new dll will support utf-8, utf-32, or unicode encoding and will handle splitting the to addess on either comma or semi colon and it has better log messages. If an unknown encoding is used it will use utf-8. It also supports splitting for cc and bcc but these are not used by the contact form. Those are the only changes at this time.

No it does not currently support anything but email address.

Thanks,

Joe

You must sign in to post in the forums. This thread is closed to new posts.