Please be aware that the content in SAP SQL Anywhere Forum will be migrated to the SAP Community in June and this forum will be retired.

I am trying to send an email from the server with an attachment using the system stored procedures xp_startsmtp and xp_sendmail.

call xp_startsmtp(
smtp_sender = '',
smtp_server = '',
smtp_sender_name = 'SQL DB MSG');

call xp_sendmail(
recipient = '',
subject = 'Hey Matt',
"message" = 'Just Checking in on you',
include_file = 'c:\\Test.txt');

This works when Test.txt is under a certain length like this:


This is either 44 characters or 49 characters depending on whether you count the new lines as characters.

Add one character to the above though to make either 45 or 50 respectively like this:


and the message does not go through.

On a single line this works at 54 characters:


but this fails at 55


Using a packet sniffer I can see the SMTP conversation and the server is responding with this:

Response: 451 see

The website basically says that some mailers put LF at the end of lines (specifically mentioning the mailer "sendmail v8" doing this with long lines) instead of CR LF and that causes problems down the line.

The xp_sendmail procedure calls another procedure that calls a .dll, which I assume packages and sends the message with the attachment. Because it uses the .dll I do not think I can adjust the output manually by adding some CR 's somewhere.

So, is this a bug? Should I handle this differently?


asked 01 Oct '10, 17:28

Siger%20Matt's gravatar image

Siger Matt
accept rate: 15%

edited 02 Oct '10, 14:55

Just very wild guesses: Does your Test.txt file contain LF or CR/LF pairs (cf. your other question...)? I have no solution but it could be that the attachment gets base64 encoded, and the interesting length behaviour might refer to the typical mail line length limit (72 characters IIRC) so that both the limit and an unexpected LF (without CR) form the problem. Have you tried to use the content_type parameter, eg. content_type = application/octet-stream?

(01 Oct '10, 18:09) Volker Barth
Comment Text Removed

The text file does not contain any viewable LF or CR/LF pairs, other than the ones that might be implicit as the lines change. It will be used with the file generated from my other question, but for testing I am using the above text typed into notepad and saved as txt. I tried specifying the content type and that failed as well with the same circumstances.
The documentation says that the include_file uses the application/octet-stream for the files, so I think the content_type only changes the message body type.

(01 Oct '10, 19:10) Siger Matt

@Siger: Do you have access to a completely different SMTP server? Just to test to see if the behavior is different. Also, use a hex viewer to see what the actual line breaks are. Plus, 451 is used by some SMTP services to flag spam; see

(02 Oct '10, 11:54) Breck Carter

Can you email me the actual test.txt file and SQL script you are using? I have tried to reproduce this with the data you included in the question and I cannot. My email address is gperrow at sybase dot com.

(04 Oct '10, 13:27) Graeme Perrow

Email sent. Thanks.

(04 Oct '10, 16:51) Siger Matt

Our base64 encoding did not conform exactly to the MIME standard. Most mail servers are flexible enough to accept it anyway, but the mail server Matt is using is very strict about it and will not accept our encoded data. I am in the process of fixing this and I will update this answer once I know what builds will contain the fix.

This is fixed in,, and

permanent link

answered 06 Oct '10, 13:47

Graeme%20Perrow's gravatar image

Graeme Perrow
accept rate: 54%

edited 06 Oct '10, 18:15

Thanks Graeme. We appreciate your work.

(06 Oct '10, 13:54) Siger Matt
Comment Text Removed

And thanks for supplying the according build numbers - that's valuable information. (Oh, and being no system developer, I feel somewhat proud to have noticed the connection to base64, see my comments above...)

(07 Oct '10, 07:17) Volker Barth
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 01 Oct '10, 17:28

question was seen: 3,334 times

last updated: 06 Oct '10, 18:15