473,320 Members | 1,884 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,320 software developers and data experts.

Subject text length limit in system.net.mail?

Is anyone aware of a size limit imposed on the subject text when using the
System.Net.Mail library?

I'm getting problems of message not being recieved if the subject exceeds 15
chars.

Thx
Jun 18 '07 #1
4 8403
Hello Alec,

I assume that it is the mail server limitation, because the Subject in System.Net
get the string type and doesn't trim it

Relation the standard, below, there is no 15 chars limitation for the subject

"RFC 2822 ("Internet Message Format")"
2.1.1. Line Length Limits
There are two limits that this standard places on the number of
characters in a line. Each line of characters MUST be no more than
998 characters, and SHOULD be no more than 78 characters, excluding
the CRLF.

The 998 character limit is due to limitations in many implementations
which send, receive, or store Internet Message Format messages that
simply cannot handle more than 998 characters on a line. Receiving
implementations would do well to handle an arbitrarily large number
of characters in a line for robustness sake. However, there are so
many implementations which (in compliance with the transport
requirements of [RFC2821]) do not accept messages containing more
than 1000 character including the CR and LF per line, it is important
for implementations not to create such messages.

---
WBR, Michael Nemtsev [.NET/C# MVP].
My blog: http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

AMIs anyone aware of a size limit imposed on the subject text when
AMusing the System.Net.Mail library?
AM>
AMI'm getting problems of message not being recieved if the subject
AMexceeds 15 chars.
AM>
AMThx
AM>
Jun 18 '07 #2
Thanks for that info Michael.

Ok. It must be something else then.

I'm using Exchange Server 2003 and am aware that subject lines can normally
be much longer than 15 chars.

What I'm trying to do is send a batch of marketing messages (HTML format)
from our CRM database. The HTML of the body, plus the subject line and the
list of recipient email addresses all come from the SQL db.

By doing a lot of trial-and-error testing yesterday I found that I had to
either reduce the HTML in size such that it was going to be useless
(literally no more than a bare minimum valid doc with a single "hello"
paragraph), or reduce the subject text to 15 chars or less.

While going over those limits does not cause an exception, the message just
seems to vanish into the ether - not even being present in the Exchange log
file.

I have wondered if this is partly due to the Symantec AV client
(Corp/Enterprise ver 10.1). This certainly introduces a lengthy 1.5 - 2
minute delay in the message being handled, but I cannot be certain if it is
stopping the messages altogether. I have tried stopping all the Symantec
services. This allows the messages to be delivered far more quickly (I'm
using my own address for testing), but it doesn't seem to prevent the larger
content variations from disappearing.

I'm at a real loss to know what's going on here. I have used Net.Mail very
successfully in other projects, but in those cases, the content of the
message had very little DB-sourced content (though there was interaction to
SQL in terms of lookups and saving of data).

Using the same project to test a "plain text" version of sending works every
time, so I have been checking the content of the DB stuff for invalid
characters that might cause the process to "stall", but as yet have not
found anything obvious.

The subject text is input via a simple Win-form textbox. The HTML content
is create using an HTML editor component based on the Nikhil Kothari
component. While it does introduce unwanted variations in the html source,
I don't think its anything that would cause such an issue.

Any further help would be deeply appreciated.

Regards,

Alec
"Michael Nemtsev" <ne*****@msn.comwrote in message
news:a2***************************@msnews.microsof t.com...
Hello Alec,

I assume that it is the mail server limitation, because the Subject in
System.Net get the string type and doesn't trim it

Relation the standard, below, there is no 15 chars limitation for the
subject

"RFC 2822 ("Internet Message Format")"
2.1.1. Line Length Limits There are two limits that this standard places
on the number of
characters in a line. Each line of characters MUST be no more than
998 characters, and SHOULD be no more than 78 characters, excluding
the CRLF.

The 998 character limit is due to limitations in many implementations
which send, receive, or store Internet Message Format messages that
simply cannot handle more than 998 characters on a line. Receiving
implementations would do well to handle an arbitrarily large number
of characters in a line for robustness sake. However, there are so
many implementations which (in compliance with the transport
requirements of [RFC2821]) do not accept messages containing more
than 1000 character including the CR and LF per line, it is important
for implementations not to create such messages.

---
WBR, Michael Nemtsev [.NET/C# MVP]. My blog:
http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

AMIs anyone aware of a size limit imposed on the subject text when
AMusing the System.Net.Mail library?
AMAMI'm getting problems of message not being recieved if the subject
AMexceeds 15 chars.
AMAMThx
AM>

Jun 19 '07 #3
Hello Alec,

Well.... I'm not the expert in Exchange server, suggest to refer this question
to the exchage group

I see the other problem in the approach you choose.
If u fix your issue and everything will be working fine, than what if the
client, who u ship the app, decided to change the mail server? You are not
assured with new mail server limitation

I'd suggest to review your architecture, and add feature to send the links
to pre-generated html pages published somewhere.
So, if client's mail server works wrong, you can switch on alternative way

---
WBR, Michael Nemtsev [.NET/C# MVP].
My blog: http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

AMThanks for that info Michael.
AM>
AMOk. It must be something else then.
AM>
AMI'm using Exchange Server 2003 and am aware that subject lines can
AMnormally be much longer than 15 chars.
AM>
AMWhat I'm trying to do is send a batch of marketing messages (HTML
AMformat) from our CRM database. The HTML of the body, plus the
AMsubject line and the list of recipient email addresses all come from
AMthe SQL db.
AM>
AMBy doing a lot of trial-and-error testing yesterday I found that I
AMhad to either reduce the HTML in size such that it was going to be
AMuseless (literally no more than a bare minimum valid doc with a
AMsingle "hello" paragraph), or reduce the subject text to 15 chars or
AMless.
AM>
AMWhile going over those limits does not cause an exception, the
AMmessage just seems to vanish into the ether - not even being present
AMin the Exchange log file.
AM>
AMI have wondered if this is partly due to the Symantec AV client
AM(Corp/Enterprise ver 10.1). This certainly introduces a lengthy 1.5
AM- 2 minute delay in the message being handled, but I cannot be
AMcertain if it is stopping the messages altogether. I have tried
AMstopping all the Symantec services. This allows the messages to be
AMdelivered far more quickly (I'm using my own address for testing),
AMbut it doesn't seem to prevent the larger content variations from
AMdisappearing.
AM>
AMI'm at a real loss to know what's going on here. I have used
AMNet.Mail very successfully in other projects, but in those cases,
AMthe content of the message had very little DB-sourced content
AM(though there was interaction to SQL in terms of lookups and saving
AMof data).
AM>
AMUsing the same project to test a "plain text" version of sending
AMworks every time, so I have been checking the content of the DB
AMstuff for invalid characters that might cause the process to
AM"stall", but as yet have not found anything obvious.
AM>
AMThe subject text is input via a simple Win-form textbox. The HTML
AMcontent is create using an HTML editor component based on the Nikhil
AMKothari component. While it does introduce unwanted variations in
AMthe html source, I don't think its anything that would cause such an
AMissue.
AM>
AMAny further help would be deeply appreciated.
AM>
AMRegards,
AM>
AMAlec
AM>
AM"Michael Nemtsev" <ne*****@msn.comwrote in message
AMnews:a2***************************@msnews.micros oft.com...
AM>
>Hello Alec,

I assume that it is the mail server limitation, because the Subject
in System.Net get the string type and doesn't trim it

Relation the standard, below, there is no 15 chars limitation for the
subject

"RFC 2822 ("Internet Message Format")"
2.1.1. Line Length Limits There are two limits that this standard
places
on the number of
characters in a line. Each line of characters MUST be no more than
998 characters, and SHOULD be no more than 78 characters, excluding
the CRLF.
The 998 character limit is due to limitations in many implementations
which send, receive, or store Internet Message Format messages that
simply cannot handle more than 998 characters on a line. Receiving
implementations would do well to handle an arbitrarily large number
of characters in a line for robustness sake. However, there are so
many implementations which (in compliance with the transport
requirements of [RFC2821]) do not accept messages containing more
than 1000 character including the CR and LF per line, it is important
for implementations not to create such messages.

---
WBR, Michael Nemtsev [.NET/C# MVP]. My blog:
http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/
"The greatest danger for most of us is not that our aim is too high
and we miss it, but that it is too low and we reach it" (c)
Michelangelo

AMIs anyone aware of a size limit imposed on the subject text when
AMusing the System.Net.Mail library?
AMAMI'm getting problems of message not being recieved if the
subject
AMexceeds 15 chars.
AMAMThx
AM>

Jun 19 '07 #4
Finally figured what it was - Internet Message Filter for Exchange settings
were a little too protective. Had it on a setting of 5, but this seems to
be sinking any message that has long subject lines, or certain HTML tags,
such as "<pre>".

Al
"Michael Nemtsev" <ne*****@msn.comwrote in message
news:a2***************************@msnews.microsof t.com...
Hello Alec,

Well.... I'm not the expert in Exchange server, suggest to refer this
question to the exchage group

I see the other problem in the approach you choose. If u fix your issue
and everything will be working fine, than what if the client, who u ship
the app, decided to change the mail server? You are not assured with new
mail server limitation

I'd suggest to review your architecture, and add feature to send the links
to pre-generated html pages published somewhere.
So, if client's mail server works wrong, you can switch on alternative way

---
WBR, Michael Nemtsev [.NET/C# MVP]. My blog:
http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

AMThanks for that info Michael.
AMAMOk. It must be something else then.
AMAMI'm using Exchange Server 2003 and am aware that subject lines can
AMnormally be much longer than 15 chars.
AMAMWhat I'm trying to do is send a batch of marketing messages (HTML
AMformat) from our CRM database. The HTML of the body, plus the
AMsubject line and the list of recipient email addresses all come from
AMthe SQL db.
AMAMBy doing a lot of trial-and-error testing yesterday I found that I
AMhad to either reduce the HTML in size such that it was going to be
AMuseless (literally no more than a bare minimum valid doc with a
AMsingle "hello" paragraph), or reduce the subject text to 15 chars or
AMless.
AMAMWhile going over those limits does not cause an exception, the
AMmessage just seems to vanish into the ether - not even being present
AMin the Exchange log file.
AMAMI have wondered if this is partly due to the Symantec AV client
AM(Corp/Enterprise ver 10.1). This certainly introduces a lengthy 1.5
AM- 2 minute delay in the message being handled, but I cannot be
AMcertain if it is stopping the messages altogether. I have tried
AMstopping all the Symantec services. This allows the messages to be
AMdelivered far more quickly (I'm using my own address for testing),
AMbut it doesn't seem to prevent the larger content variations from
AMdisappearing.
AMAMI'm at a real loss to know what's going on here. I have used
AMNet.Mail very successfully in other projects, but in those cases,
AMthe content of the message had very little DB-sourced content
AM(though there was interaction to SQL in terms of lookups and saving
AMof data).
AMAMUsing the same project to test a "plain text" version of sending
AMworks every time, so I have been checking the content of the DB
AMstuff for invalid characters that might cause the process to
AM"stall", but as yet have not found anything obvious.
AMAMThe subject text is input via a simple Win-form textbox. The HTML
AMcontent is create using an HTML editor component based on the Nikhil
AMKothari component. While it does introduce unwanted variations in
AMthe html source, I don't think its anything that would cause such an
AMissue.
AMAMAny further help would be deeply appreciated.
AMAMRegards,
AMAMAlec
AMAM"Michael Nemtsev" <ne*****@msn.comwrote in message
AMnews:a2***************************@msnews.micros oft.com...
AM>
>>Hello Alec,

I assume that it is the mail server limitation, because the Subject
in System.Net get the string type and doesn't trim it

Relation the standard, below, there is no 15 chars limitation for the
subject

"RFC 2822 ("Internet Message Format")"
2.1.1. Line Length Limits There are two limits that this standard
places
on the number of
characters in a line. Each line of characters MUST be no more than
998 characters, and SHOULD be no more than 78 characters, excluding
the CRLF.
The 998 character limit is due to limitations in many implementations
which send, receive, or store Internet Message Format messages that
simply cannot handle more than 998 characters on a line. Receiving
implementations would do well to handle an arbitrarily large number
of characters in a line for robustness sake. However, there are so
many implementations which (in compliance with the transport
requirements of [RFC2821]) do not accept messages containing more
than 1000 character including the CR and LF per line, it is important
for implementations not to create such messages.

---
WBR, Michael Nemtsev [.NET/C# MVP]. My blog:
http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/
"The greatest danger for most of us is not that our aim is too high
and we miss it, but that it is too low and we reach it" (c)
Michelangelo

AMIs anyone aware of a size limit imposed on the subject text when
AMusing the System.Net.Mail library?
AMAMI'm getting problems of message not being recieved if the
subject
AMexceeds 15 chars.
AMAMThx
AM>


Jun 20 '07 #5

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

0
by: Notlwonk | last post by:
I have written an event sink in C# that hooks into our Exchange Server 2000 store. The sink fires and the various LOG files are created, but for some reason I cannot seem to read-in the e-mail...
16
by: Christine | last post by:
I was wondering if it is possible to read in a text file as a data type other than string. I would like to read it in as some type that handles numbers, like double, or float.
6
by: Aaron Smith | last post by:
Is there a way to put a limit on the text size of a datagrid column? Thanks, Aaron -- --- Aaron Smith Remove -1- to E-Mail me. Spam Sucks.
5
by: Daniel | last post by:
c# string size limit? length of string limit?
4
by: Derty | last post by:
Any way to limit the length of databound text on a datalist itemtemplate?
3
by: Laangen_LU | last post by:
Dear Group, my first post to this group, so if I'm on the wrong group, my apologies. I'm trying to send out an email in Chinese lanuage using the mail() function in PHP. Subject and...
11
by: =?Utf-8?B?VmxhZCBIcnlib2s=?= | last post by:
Using IIS7, Vista x64, ASP.NET 2.0. I am getting HTTP 400 "Bad Request" for the following URL:...
1
by: Lilith | last post by:
I'm looking at practical string lengths and the capacity of a text box. I'm using a string to progressively add the status of a process periodically and dumping that text into a text box. I don't...
3
by: =?Utf-8?B?anAybXNmdA==?= | last post by:
I've got some code that is chopping my subject line on the messages I receive, and I do not know why. Our server is running Active Directory and SQL Server 2000 Enterprise. The email is sent,...
0
by: DolphinDB | last post by:
The formulas of 101 quantitative trading alphas used by WorldQuant were presented in the paper 101 Formulaic Alphas. However, some formulas are complex, leading to challenges in calculation. Take...
0
by: DolphinDB | last post by:
Tired of spending countless mintues downsampling your data? Look no further! In this article, you’ll learn how to efficiently downsample 6.48 billion high-frequency records to 61 million...
0
by: ryjfgjl | last post by:
ExcelToDatabase: batch import excel into database automatically...
0
by: Vimpel783 | last post by:
Hello! Guys, I found this code on the Internet, but I need to modify it a little. It works well, the problem is this: Data is sent from only one cell, in this case B5, but it is necessary that data...
0
by: ArrayDB | last post by:
The error message I've encountered is; ERROR:root:Error generating model response: exception: access violation writing 0x0000000000005140, which seems to be indicative of an access violation...
1
by: PapaRatzi | last post by:
Hello, I am teaching myself MS Access forms design and Visual Basic. I've created a table to capture a list of Top 30 singles and forms to capture new entries. The final step is a form (unbound)...
0
by: CloudSolutions | last post by:
Introduction: For many beginners and individual users, requiring a credit card and email registration may pose a barrier when starting to use cloud servers. However, some cloud server providers now...
0
by: Shællîpôpï 09 | last post by:
If u are using a keypad phone, how do u turn on JavaScript, to access features like WhatsApp, Facebook, Instagram....
0
by: Faith0G | last post by:
I am starting a new it consulting business and it's been a while since I setup a new website. Is wordpress still the best web based software for hosting a 5 page website? The webpages will be...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.