Re: [WebDNA] Re:BCC and/or Character limit [sendmail]
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 105599
interpreted = N
texte = This is a multi-part message in MIME format. --------------030606050103050606040106 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi Ken, Thanks for replying. > I'm not sure so you'll have to confirm this with Chris or someone who actually knows, but my guess is that there is no built-in webdna limit to the number of bcc addresses. I did email Chris on this a few days ago and didn't get an answer. That's why I've posted to the list again. > > > HOWEVER ... > > I think that some mail servers are configured to reject mail with too many cc's or bcc's in them, so this could be a problem for you even if there is no hard limit in webdna. > > Yes, I am aware of servers inbound monitoring and some that temporarily reject emails coming from a given IP after a certain per hour limit has been reached along with a fair understanding of how to avoid getting on blacklists. Only made it on a blacklist once years ago while using a shared SMTP server from a hosting company. I have recently installed Postfix on our Linux box and have it configured to limit the number of emails that it sends to a given server every so many seconds/max per hour. Prior to using WebDNA and Postfix to send out to our email newsletter, I was sending out the mass emails via a windows app that would send them in BCC packets of 50 to a hosted SMTP server without issue however it took hours. This last send I used WebDNA and Postfix to send the email list out and only included 35 BCC's per [sendmail] (in case there was some BCC limit) which took the template several minutes to complete. I would like to send somewhere in the neighborhood of 1000 BCC's per WebDNA [sendmail] so the template completes sending all the mail to Postfix in only a few seconds and then let Postfix do the queuing and governing of sending the actual mail. > >> I read somewhere in the "list archives" (posts were >> > from years ago) that [sendmail] has a 5000 character >> > limit. Can someone confirm this? > > Sorry, I don't know about this but I kind of doubt it. Why would the webdna sendmail context have such an arbitrary limit unless there were a corresponding limit for all email in general? > As I mentioned above, the age of the post where I got this info is years old and I was questing it myself. I'm still somewhat a newbie to WebDNA and continue to look for clarity and help. On a related topic, I also read that there is there a 5000 character limit for a db field? Do I have this info correct? If so, maybe that is where someone got the 5000 limit idea for [sendmail]. > But if there is such a limit, one way to get around it is by attaching a large file to your email rather than putting all that text into the email body itself. > Yes, the actual body of the email is very small. 2 lines of text. One text link to view the newsletter as a web page and a second to unsubscribe from receiving future newsletter emails from us. The actual newsletter is an html file inserted in the body of the email with [include file=] and it is usually fairly small. This last [include] html file was only 151.1KB. > Sincerely, > Kenneth Grome > > Best Regards, Steve --------------030606050103050606040106 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Hi Ken,
Thanks for replying.
I'm not sure so you'll have to confirm this with Chris or someone who actually knows, but my guess is that there is no built-in webdna limit to the number of bcc addresses.
I did email Chris on this a few days ago and didn't get an answer. That's why I've posted to the list again.
HOWEVER ... I think that some mail servers are configured to reject mail with too many cc's or bcc's in them, so this could be a problem for you even if there is no hard limit in webdna.
Yes, I am aware of servers inbound monitoring and some that temporarily reject emails coming from a given IP after a certain per hour limit has been reached along with a fair understanding of how to avoid getting on blacklists. Only made it on a blacklist once years ago while using a shared SMTP server from a hosting company.
I have recently installed Postfix on our Linux box and have it configured to limit the number of emails that it sends to a given server every so many seconds/max per hour. Prior to using WebDNA and Postfix to send out to our email newsletter, I was sending out the mass emails via a windows app that would send them in BCC packets of 50 to a hosted SMTP server without issue however it took hours.
This last send I used WebDNA and Postfix to send the email list out and only included 35 BCC's per [sendmail] (in case there was some BCC limit) which took the template several minutes to complete. I would like to send somewhere in the neighborhood of 1000 BCC's per WebDNA [sendmail] so the template completes sending all the mail to Postfix in only a few seconds and then let Postfix do the queuing and governing of sending the actual mail.
I read somewhere in the "list archives" (posts were > from years ago) that [sendmail] has a 5000 character > limit. Can someone confirm this?
Sorry, I don't know about this but I kind of doubt it. Why would the webdna sendmail context have such an arbitrary limit unless there were a corresponding limit for all email in general?
As I mentioned above, the age of the post where I got this info is years old and I was questing it myself. I'm still somewhat a newbie to WebDNA and continue to look for clarity and help.
On a related topic, I also read that there is there a 5000 character limit for a db field? Do I have this info correct? If so, maybe that is where someone got the 5000 limit idea for [sendmail].
But if there is such a limit, one way to get around it is by attaching a large file to your email rather than putting all that text into the email body itself.
Yes, the actual body of the email is very small. 2 lines of text. One text link to view the newsletter as a web page and a second to unsubscribe from receiving future newsletter emails from us. The actual newsletter is an html file inserted in the body of the email with [include file=] and it is usually fairly small. This last [include] html file was only 151.1KB.
Sincerely, Kenneth Grome
Best Regards,
Steve
--------------030606050103050606040106--
Associated Messages, from the most recent to the oldest:
This is a multi-part message in MIME format. --------------030606050103050606040106 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi Ken, Thanks for replying. > I'm not sure so you'll have to confirm this with Chris or someone who actually knows, but my guess is that there is no built-in webdna limit to the number of bcc addresses. I did email Chris on this a few days ago and didn't get an answer. That's why I've posted to the list again. > > > HOWEVER ... > > I think that some mail servers are configured to reject mail with too many cc's or bcc's in them, so this could be a problem for you even if there is no hard limit in webdna. > > Yes, I am aware of servers inbound monitoring and some that temporarily reject emails coming from a given IP after a certain per hour limit has been reached along with a fair understanding of how to avoid getting on blacklists. Only made it on a blacklist once years ago while using a shared SMTP server from a hosting company. I have recently installed Postfix on our Linux box and have it configured to limit the number of emails that it sends to a given server every so many seconds/max per hour. Prior to using WebDNA and Postfix to send out to our email newsletter, I was sending out the mass emails via a windows app that would send them in BCC packets of 50 to a hosted SMTP server without issue however it took hours. This last send I used WebDNA and Postfix to send the email list out and only included 35 BCC's per
[sendmail] (in case there was some BCC limit) which took the template several minutes to complete. I would like to send somewhere in the neighborhood of 1000 BCC's per WebDNA
[sendmail] so the template completes sending all the mail to Postfix in only a few seconds and then let Postfix do the queuing and governing of sending the actual mail. > >> I read somewhere in the "list archives" (posts were >> > from years ago) that
[sendmail] has a 5000 character >> > limit. Can someone confirm this? > > Sorry, I don't know about this but I kind of doubt it. Why would the webdna sendmail context have such an arbitrary limit unless there were a corresponding limit for all email in general? > As I mentioned above, the age of the post where I got this info is years old and I was questing it myself. I'm still somewhat a newbie to WebDNA and continue to look for clarity and help. On a related topic, I also read that there is there a 5000 character limit for a db field? Do I have this info correct? If so, maybe that is where someone got the 5000 limit idea for
[sendmail]. > But if there is such a limit, one way to get around it is by attaching a large file to your email rather than putting all that text into the email body itself. > Yes, the actual body of the email is very small. 2 lines of text. One text link to view the newsletter as a web page and a second to unsubscribe from receiving future newsletter emails from us. The actual newsletter is an html file inserted in the body of the email with [include file=] and it is usually fairly small. This last
[include] html file was only 151.1KB. > Sincerely, > Kenneth Grome > > Best Regards, Steve --------------030606050103050606040106 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Hi Ken,
Thanks for replying.
I'm not sure so you'll have to confirm this with Chris or someone who actually knows, but my guess is that there is no built-in webdna limit to the number of bcc addresses.
I did email Chris on this a few days ago and didn't get an answer. That's why I've posted to the list again.
HOWEVER ... I think that some mail servers are configured to reject mail with too many cc's or bcc's in them, so this could be a problem for you even if there is no hard limit in webdna.
Yes, I am aware of servers inbound monitoring and some that temporarily reject emails coming from a given IP after a certain per hour limit has been reached along with a fair understanding of how to avoid getting on blacklists. Only made it on a blacklist once years ago while using a shared SMTP server from a hosting company.
I have recently installed Postfix on our Linux box and have it configured to limit the number of emails that it sends to a given server every so many seconds/max per hour. Prior to using WebDNA and Postfix to send out to our email newsletter, I was sending out the mass emails via a windows app that would send them in BCC packets of 50 to a hosted SMTP server without issue however it took hours.
This last send I used WebDNA and Postfix to send the email list out and only included 35 BCC's per
[sendmail] (in case there was some BCC limit) which took the template several minutes to complete. I would like to send somewhere in the neighborhood of 1000 BCC's per WebDNA
[sendmail] so the template completes sending all the mail to Postfix in only a few seconds and then let Postfix do the queuing and governing of sending the actual mail.
I read somewhere in the "list archives" (posts were > from years ago) that [sendmail] has a 5000 character > limit. Can someone confirm this?
Sorry, I don't know about this but I kind of doubt it. Why would the webdna sendmail context have such an arbitrary limit unless there were a corresponding limit for all email in general?
As I mentioned above, the age of the post where I got this info is years old and I was questing it myself. I'm still somewhat a newbie to WebDNA and continue to look for clarity and help.
On a related topic, I also read that there is there a 5000 character limit for a db field? Do I have this info correct? If so, maybe that is where someone got the 5000 limit idea for
[sendmail].
But if there is such a limit, one way to get around it is by attaching a large file to your email rather than putting all that text into the email body itself.
Yes, the actual body of the email is very small. 2 lines of text. One text link to view the newsletter as a web page and a second to unsubscribe from receiving future newsletter emails from us. The actual newsletter is an html file inserted in the body of the email with [include file=] and it is usually fairly small. This last
[include] html file was only 151.1KB.
Sincerely, Kenneth Grome
Best Regards,
Steve
--------------030606050103050606040106--
Steve Raslevich
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
(1997)
Webcatalog error, Plug-in for Webstar (1996)
UPPERCASE (1997)
Ready,Set; Print! (1999)
WebCatalog can't find database (1997)
quitting (1997)
absolute paths for databases? (1997)
ShowNext Command (1997)
Bad Suffix (1999)
Bookmarked URL with cart (1998)
docs for WebCatalog2 (1997)
RE: [countChars] from