PDA

View Full Version : Send Mail: Version 8.0 behavior change?


deramor
04-03-2012, 06:09 PM
Hello-

I recently purchased a VBP version 8.0 license. I used to be using 7.7a for my builds. I have e-mail notifications for success and failure. We use an SMTP server to send our mail (no authentication). Without changing anything in the VBP project file, the build fails to send e-mail messages to this server while running under version 8.0. These steps had previously run and continue to do so under 7.7a. I tweaked my send mail step and got it to pass by removing all text in the "From" field. Previously it was simply "Visual Build" with no Quotes which worked under 7.7a. I can not find any mention of changes to this step in the version history so here I am. I would like to keep the "From" information. Otherwise the message appears to be from no one and resembles spam.

I have attached some relevant info. Some of the info was omitted due to it containing internal company information. I do not believe it will effect any debugging. Does anyone have any thoughts?

kinook
04-03-2012, 08:28 PM
I believe the SMTP spec requires a valid from address (or blank). It appears that the mail component we use allowed a name-only from value, but doesn't allow that in newer versions (presumably to be more compliant with the spec). Try something like

"Visual Build" <noreply@mydomain.com>

in the From address field.

deramor
04-04-2012, 09:48 AM
Thanks for the reply!

Are there any illegal characters for this field? I tried:
"Visual Build" <noreply@company.com> which worked
"Visual Build" <Visual.Build@Company.com> which worked
"Visual Build" <Visual_Build@Company.com> which did not work.

I can live with one implementation over the other. I just find it worth while to mention that some characters seem to be not allowed. I would assume that any character allowed in an e-mail address should work in this field.

kinook
04-04-2012, 10:05 AM
All of those addresses worked in my tests. The RFC for email addresses is here: http://tools.ietf.org/html/rfc2822#section-3.4