Email notification body is empty

JayZee · Joined: 10 Jan 2012 Posts: 11

I configured VV Pro to send email notifications on success and failure but the body of the email is blank. If I send a test email it works properly. Has anyone else had this issue. Any assistance would be much appreciated. Thank you.

TGRMN Software · Site Admin Joined: 10 Jan 2005 Posts: 8763

Is the e-mail body in the profile settings not empty?
Please also check the profile log (ViceVersa profile settings -> execution)
thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

JayZee · Joined: 10 Jan 2012 Posts: 11

Yes, the e-mail body in the profile settings is not empty and the profile log is also populated with the correct data. It is just not being put into the email body after the backup for some reason. Thanks for your quick response.

TGRMN Software · Site Admin Joined: 10 Jan 2005 Posts: 8763

Can you test changing the e-mail body in the profile settings and see if it's always empty, no matter what body you use? thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

JayZee · Joined: 10 Jan 2012 Posts: 11

I added a test comment to the first line and both a test email and manual run email bodies worked properly. I will remove my comment from the body and let the automatic schedule run and check it again. Thank you for your help.

JayZee · Joined: 10 Jan 2012 Posts: 11

The automatic scheduled backup ran and the same issue occurred. It seems to be happening when I'm not logged in the back operator's account. If I'm logged in the email body is fine.

TGRMN Software · Site Admin Joined: 10 Jan 2005 Posts: 8763

Are you using the variable %VV_LOG_FILE_CONTENT% in the body? thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

JayZee · Joined: 10 Jan 2012 Posts: 11

No, I don't see that variable in mine, here's a copy of my variables. Its the default with the addition of the Daily backup coment.

*************************************************
Daily Backup

E-Mail sent on %TIMEANDDATE%

Profile: %PROFILE%
Result: %VV_EXIT_CODE_DESC%
Exit Code: %VV_EXIT_CODE%
%VV_LAST_ERROR%
Profile Start Time: %VV_RUN_START_TIME%
Profile End Time: %VV_RUN_END_TIME%

Source: %VV_SOURCE_FOLDER%
Target: %VV_TARGET_FOLDER%
User: %USERNAME%
Computer: %COMPUTERNAME%

----------------------------------------------------------
%VV_EXECUTION_METHOD_DESC%

%VV_FINAL_STATUS_SUMMARY%

%VV_RUN_SUMMARY%

%VV_CONFLICT_SUMMARY%

%VV_COPIED_FILES%

%VV_COPIED_FILES_ERRORS%

%VV_DELETED_FILES%

%VV_DELETED_FILES_ERRORS%

*************************************************

JayZee · Joined: 10 Jan 2012 Posts: 11

I did some more investigation and found that if I removed all the data being added to the email after the %VV_CONFLICT_SUMMARY% line, the email would be sent properly. So I think there is an issue with the long file name lines i.e. over 635 characters. I "WireSharked" the messages and found that there was malformed packets being set on port 25 by VV when sending the email.

TGRMN Software · Site Admin Joined: 10 Jan 2005 Posts: 8763

Thank you, that's great info for us to possibly reproduce and implement a fix. Can the issue be summarized that if the e-mail body has a line longer than 635 characters , then the body is sent empty?
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

JayZee · Joined: 10 Jan 2012 Posts: 11

I think it would be more correct to say that the e-mail body is sent, but the data does not conform to the SMTP protocol and is discarded by the receiving server which results in an empty body.

TGRMN Software · Site Admin Joined: 10 Jan 2005 Posts: 8763

And that happens if any line of the e-mail is > 635 characters? I wonder if it's an issue with a specific mail server limitation, I'll try with GMAIL too. thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

JayZee · Joined: 10 Jan 2012 Posts: 11

I didn't do an extensive investigation on the problem so I don't know what the underlying issue is. WireShark reported that the packets were malformed so that has nothing to do with mail server limitations and if the line was too long the server would throw an exception 500 Line too long.
The specification for an email text line is set at a maximum of 1000 characters according to RFC 821 {The maximum total length of a text line including the <CRLF> is 1000 characters (but not counting the leading dot duplicated for transparency).} So I think there may be internal buffering issues in VV (maybe a 512 buffer length, just guessing) for the message queue.
So I think it should be very easy to reproduce the issue, just run WireShark and capture the malformed packets for a mirroring job with very long file names.

TGRMN Software · Site Admin Joined: 10 Jan 2005 Posts: 8763

OK, thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

TGRMN Software · Site Admin Joined: 10 Jan 2005 Posts: 8763

Hi,
We tried to reproduce this issue, but are unable to do so. Using two separate mail servers (incl. GMAIL) we are able to send e-mail with lines > 1000 chars. Wireshark does not report malformed SMTP packets. We will contact you via e-mail for further diagnosis.
thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com