Can anyone help with this one? I've tried everything (even enabling per site settings so that my form uses settings specified by the site admin and not in web.config)

In user.config I now have the following:

<add key="EnableSiteSettingsSmtpSettings" value="true" />

<add key="MaskSmtpPasswordInSiteSettings" value="true" />

<add key="ShowSmtpEncodingOption" value="true" />

<add key="DisableDotNetOpenMail" value="false" />

but keeps on saying the same message in the log (the strange thing is that the exception trace seems to be the same irrespective of the DisableDotNetOpenMail setting - is that option working at all?).

...

at mojoPortal.Net.Email.SendEmailNormal(SmtpSettings smtpSettings, String from, String replyTo, String to, String cc, String bcc, String subject, String messageBody, Boolean html, String priority)

at mojoPortal.Net.Email.SendEmail(SmtpSettings smtpSettings, String from, String replyTo, String to, String cc, String bcc, String subject, String messageBody, Boolean html, String priority)

...

Thanks for the reply Joe,

but it's not that the problem, I have filled-in the details at the site settings tab ok (I did it on purpose to make the settings easier to maintain and in the process of trying to troubleshoot why I can't send any e-mail from the portal [I never made it to])

we're not in medium trust and have tried with both values of DisableDotNetOpenMail (I'll set it to true again)

I wonder which is the offending e-mail string. Isn't the exception saying which one it is? (else couldn't you add some direct calls to that parsing function that .NET calls at the phase where you load site options the 1st time and also when those settings are updated from the GUI [both for the config files and the site settings tab that is]). That way we'd know what the offending string is exactly (you'd catch that exception and spit it out together with the exception)

Btw, another reason I set it to use per-site settings was so that the contact form wouldn't use the web.config ASP.net mail settings (in case they were the probkem) but the ones I set at the GUI (according to your docs) - in both cases though I see the exact same error trace and same error. Is it correct that the contact form will use the per site settings?

also using the following at web.config, but it didn't help that I added deliveryMethod="Network" and defaultCredentials="false" (if defaultCredentials is true at machine.config it will ignore userName/password). Trying using a userName with and without @mymailserver... too with no luck

------------------- 

<system.net>

<mailSettings>

<smtp deliveryMethod="Network" from="...@...">

<network defaultCredentials="false" host="..." port="25" password="..." userName="..." />

</smtp>

</mailSettings>

</system.net>

also tried with utf-8, latin1, iso-8859-1 for the encoding setting

I have the site e-mail address (at 1st page) set ok (that's the from I guess). The SMTP user is set too (tried it both as user and user@server). Also of course the form filled (by me) has the person's email address set. Is there other e-mail too to set somewhere?

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])

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)

.NET and SMTP should support any encoding, as long as you use base64 for the TransferEncoding (for single-byte ones you could also use QuotedPrintable [instead of 7-bit which will eat up data for sure], but using base64 is best since it also support multibyte ones like UTF-16 [the classic Unicode encoding]).

At LvS, at LvS_Utilities\subtitles\BaseSubtitleWriter.vb, I'm using:

Using writer As New StreamWriter(path, False, theEncoding)

  WriteSubtitles(subtitles, writer)

End Using

so you could use StreamWriter to write to any encoding the user told you to use, then tell .NET to use base64 for the TransferEncoding so that SMTP can transfer it fine

My experience on the above is from lots of research I had to do recently to fix osCommerce (well known PHP store) to send e-mails with Greek text. BTW, in osCommerce they have a store name that is used as the display name for e-mails (decent e-mail clients show both the display name AND the e-mail address, so there's no issue with phising - anyway SMTP headers can be faked to say anything - my comment regarding spam filters was that I think they have higher chance to catch a post that just has a newly seen from e-mail address with no display name, but I might be wrong with that [could check SpamAssassin's rulebase for example, although other engines use PETRI nets, neural nets etc. that are not always easy to checkout])

Also, regarding message body, .NET supports any encoding from what I understand, according to what is written at reference of BodyEncoding class on MSDN, not just us-ascii and "Unicode" (in the general sense) ones, like UTF-8, UTF-16 (this is called Unicode encoding officially in .NET if I'm not mistaken) and UTF-32. It's just that for the last 3 ones .NET selects a TransferEncoding of Base64 (instead of 7-bit or QuotedPrintable) for the MailMessage. 

From your replies above I understood you were saying .NET doesn't support say Russian encoding (or ISO-8859-7 [Greek]) etc. which doesn't sound accurate (in fact some older mail clients don't support UTF-8 so many admins would opt for using ISO-8859-7 in Greece)

The * is what is supported irrespective of codepages installed on the server. Such codepages are installed from Regional Settings (or if you have localized OS are preinstalled). You'd expect that an admin who wants to send ISO-8859-7 Greek text will have that codepage on their server, or ask their host (say if they use shared hosting) to add it (easy and no real overhead to do [just tiny disk space fraction to install the .NLS file]).

btw, regarding display names and stores, my experience with OSCommerce is that it supports the store name in the from field and decent e-mail clients should show both the (decoded) display name and the e-mail address in the format that .NET DisplayName property (see its ref) also shows, that is name <mail> if name is defined, else shows just mail (but not <mail>)

regarding phising, SMTP headers can be faked, it's totally unsafe anyway to trust

I'll do a little search on it and let you know. The idea is that the "Content-Transfer-Encoding" header has to be set, but if you were to set the header directly somehow I think you'd have to base64 the content yourself. I think best is to check out BodyEncoding property implementation in Mono [else maybe use .NET Reflector on MS impl. - latest one available by RedGate, still for free - might be able to show some info] to see how it sets the TransferEncoding to base64 when the BodyEncoding is UTF-8/UTF-16/UTF-32 (I hope that they use some public calls to do that, not under the hood trickery).

I don't mind implementing it myself, I want to start playing with mojoPortal's code anyway and maybe it's a good chance to do it...

at

http://community.discountasp.net/showthread.php?t=3762

there's a useful discussion that shows one can have a message with just a text/plain AlternateView, so they can set TransferEncoding there (modified their sample a bit since they were instantiating SmtpClient class twice by accident)

MailMessage email = new MailMessage(SENDER_EMAIL, RECIPIENT_EMAIL);

email.Subject = SUBJECT;

AlternateView plainView = AlternateView.CreateAlternateViewFromString(sMessageBody, Nothing, "text/plain");

plainView.TransferEncoding = System.Net.Mime.TransferEncoding.SevenBit;

email.AlternateViews.Add(plainView);

SmtpClient _client;

this._client = new SmtpClient(SMTP_SERVER, 25);

this._client.Credentials = new NetworkCredential(CRED_ID, CRED_LOGIN);

this._client.Timeout = TIMEOUT;

this._client.Send(email);



There's a CreateAlternateViewFromString that takes an encoding param (the example I used above had Nothing for the encoding)

http://msdn.microsoft.com/en-us/library/ms144596.aspx

so one can add an AlternateView of "text/plain" with the encoding the user asked and then tell it to use "base64" TransferEncoding (in the example I copy/pasted above they were using 7-bit)

----

Also in the same way can add more AlternateViews for HTML mimetype ("text/html" I think is the MIME type, but better check it out). For HTML with no images/attachments (just formatted text) it's easy to add with few changes I suppose