WealthLabPro (6.6.13.0) crashed shortly after email properties were being updated. The email properties settings seems correct. Also, when 'Send Test Email' button clicked, it said 'Email Message Successfully', however no message actually being sent. The error message resulted from the crash is shown below:

Log Name: Application
Source: .NET Runtime
Date: 12/15/2013 11:42:26 PM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: MY-PC
Description:
Application: WealthLabPro.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Net.Mail.SmtpException
Stack:
at WealthLab.WLPEmail.a(Boolean)
at WealthLab.WLPEmail.a()
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()

Thanks for any help.

Unfortunately, this is old news. A record for this bug exists on the Open Issues list since 6.4. Your email properties only seem correct but they are not - hence the crash:

QUOTE:
(90180) Email Unhandled Exceptions Crash WL 6.4. Errors when sending email and/or incorrect settings are not properly handled like in 6.3 and below, and within 30-60 seconds WL 6.4 crashes.

So, to fix it you have to double check your email settings and fix what's wrong. I think the bug wasn't considered a High issue because the cause is a user error which is easy to solve. But if we're lucky, this might get fixed in a future build.

Eugen,

I will double check the email settings. Thanks.

Eugene,

Below are two different version of settings I have tried (I have confirmed no typo errors in user name and/or password) but still the WL keep crashing. Do you have any suggestions? Thanks.

To be clear, Wealth-Lab is crashing because it's receiving an error when contacting the smtp server. (It should gracefully handle the error, but it does not.)

Try pointing to
plus.smtp.mail.yahoo.com

I have it pointed to 'plus.smtp.mail.yahoo.com', (although I don't have Yahoo Mail Plus), it still crashes.

Go back to smtp.mail.yahoo.com and use Port 587.

Cone:

WOW, the Test Mail did got through for the 1st time and so far it does not crash - it's working. I don't know how someone on the internet would suggest using port 645. I have fiddled with this error on and off for a long time - and am very glad that it's finally working. Thanks so much for the help. :))

And see this thread about sending email directly from the strategy. I use this alternate method with a parameter to keep from sending email every time I run a test.

http://www.wealth-lab.com/Forum/Posts/WLP-Email-Suggestion-33179

Advantages:
1. Full control of what gets emailed, subject and body. I add strategy-specific signal quality, sell reason and other attributes of the trade.
2. Allows different mailing lists per strategy (hardcoded in the strategy, in my case)
3. Can use a parameter to shut off emailing while testing. I only set the parameter in Strategy Monitor.
Disadvantages:
1. More code in each emailing strategy.
2. Changing email targets requires strategy code maintenance

I copy and paste standard email routines for composing and sending buy and sell alerts once a strategy has "matured."

Thank you. I will check it out.

When WLP (with the email properties set correctly) set to run a strategy in real-time, it crashed. The result of the crashes pointed to Email related. The error report from Windows are shown below.

Application: WealthLabPro.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.Net.Mail.SmtpException Stack: at WealthLab.WLPEmail.a(Boolean) at WealthLab.WLPEmail.a() at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at System.Threading.ThreadHelper.ThreadStart()

When bug 90180 will be fixed, unhandled exceptions should no longer produce crashes. Something went wrong, perhaps it was a temporary glitch, but it's hardly possible to tell based on this error message (not enough detail). Try experimenting with different email accounts to send email from until you find something that works for you.

Eugene, I will try that and will report back. Thanks