| Author |
|
L.S.Lim
Guest Group
Joined: 10 November 2003
Online Status: Online
Posts: 262
|
| Posted: 25 October 2005 at 4:44am | IP Logged
|
|
|
Dear Sir/Madam,
Our users often required to sent emails to the whole company, or some departments. But after selecting about 80 plus email address, it was only sent to 14 emails only, whereas, any recipient after that is not sent and cut off by the server.
Thank you,
L.S.Lim
|
| Back to Top |
|
| |
Alex
AfterLogic Support
Joined: 19 November 2003
Online Status: Offline
Posts: 2206
|
| Posted: 25 October 2005 at 12:50pm | IP Logged
|
|
|
Many mail servers limit the number of message recipients. For instance, if the TO field includes too many recipients, it would be truncated by the mail server, and only the recipients whose addresses are still present in the truncated field would receive the message.
There are two possible solutions of this problem:
1. You may split the list of the message recipients into the several smaller groups. Each group should include the maximum number of recipients allowed by the mail server. In your case, it's 5 groups of 14 addresses and one group of 10 addresses.
Then, you should send the message with the same content (but with the different value of the TO field) for each group. On each send, the TO field should include all the addresses of the recipients which belong to the current group.
Thus, each recipient would be able to see another 13 recipients of the same group (or 9 recipients for the last group).
2. If you'd like each recipient to be able to see all other 79 message recipients, you may use MailBee SMTP.SendEx method. This method allows sending the message to the addresses different from those
specified in TO, CC, and BCC fields.
Thus, you can send the message having all 80 recipients in TO, CC and BCC fields. You should still split the list of the recipients addresses into the groups as shown above, but now you should specify these groups in Recips parameter of SMTP.SendEx method.
However, your mail server may limit the number of recipients on SMTP session basis. In other words, no more than 14 recipient email addresses can be submitted during a single SMTP session.
In this case, you should call SMTP.Disconnect after each call to SMTP.Send or SMTP.SendEx method.
If this still does not help, the possible reason might be that the server limits the number of recipients submitted during certain amount of time. For instance, it might allow sending to 20 recipients per second.
If this is the case, you should use MailBee Message Queue to limit the number of emails submitted to the server per second.
Regards,
Alex
|
| Back to Top |
|
| |
L.S.Lim
Guest Group
Joined: 10 November 2003
Online Status: Online
Posts: 262
|
| Posted: 25 October 2005 at 8:23pm | IP Logged
|
|
|
Dear Mr.Alex,
Thank you for your reply. But our users are using OE, Outlook, and two other different types of Webmails, and all of those doesn't have any problem sending to more than 80 recipients at any one time.
Thank you,
L.S.Lim
|
| Back to Top |
|
| |
Alex
AfterLogic Support
Joined: 19 November 2003
Online Status: Offline
Posts: 2206
|
| Posted: 26 October 2005 at 12:56pm | IP Logged
|
|
|
Could you please provide us with a test account on your mail server, where using MailBee to send message to 80 recipients causes the problem, but using Outlook Express does not? You may send this information to support@afterlogic.com. Thanks.
Regards,
Alex
|
| Back to Top |
|
| |
L.S.Lim
Guest Group
Joined: 10 November 2003
Online Status: Online
Posts: 262
|
| Posted: 26 October 2005 at 9:10pm | IP Logged
|
|
|
Dear Mr.Alex,
I'm sorry, but our both our Mail Server and Webmail is running internally, access from outside our organisation is not available. Any other solutions to this?
Thank you,
L.S.Lim
|
| Back to Top |
|
| |
Alex
AfterLogic Support
Joined: 19 November 2003
Online Status: Offline
Posts: 2206
|
| Posted: 27 October 2005 at 4:12pm | IP Logged
|
|
|
Have you tried splitting recipients into groups and sending via SendEx method (as described above)?
Also, you may try to modify split From, To, CC headers into several lines. It might be possible that mail server cannot process very long header line. To do this, use the code like below:
Code:
SMTP.FromAddr = "addr1, addr2, ..., addr10," & vbCrLf & vbTab & "addr11, addr12, ..."
|
|
|
This way, To header will become multi-line, and no lines will be very long. Lines must be delimited with vbCrLf & vbTab sequence.
Please note that you should send using SendEx method (Send method does not support multi-line To/CC headers).
If this still does not help, please send us the following info to support@afterlogic.com
- the code you're using
- the problem email as .eml file (you can get it by calling using SMTP.Message.SaveMessage just before SMTP.Send)
- MailBee log file which shows the error (you can enable logging by setting SMTP.EnableLogging and SMTP.LogFilePath properties)
Regards,
Alex
|
| Back to Top |
|
| |
L.S.Lim
Guest Group
Joined: 10 November 2003
Online Status: Online
Posts: 262
|
| Posted: 27 October 2005 at 10:33pm | IP Logged
|
|
|
Dear Mr.Alex,
Which file should I modify? I've did a search but couldn't locate the file with SMTP.FromAddr. Does this means that I would need to modify the mdb for the wm_messages table, str_to field from text to memo? If I did that, there will be error when listing the message, and on error resume next code will list everything, but without the email addresses.
Regards,
L.S.Lim
|
| Back to Top |
|
| |
Alex
AfterLogic Support
Joined: 19 November 2003
Online Status: Offline
Posts: 2206
|
| Posted: 28 October 2005 at 9:36am | IP Logged
|
|
|
OK, now I see. Since you posted this topic in MailBee SMTP forum, I thought you question is related to MailBee.SMTP. However, you mentioned wm_messages table in the last posting, and it's now clear you're using WebMail Pro.
In WebMail Pro, max length of To/Cc/Bcc fields is 255 chars. However, it's not possible to increase this value just by replacing text to memo. Although you may try this, we cannot guarantee it will work.
The only reliable solution would be splitting email addresses into several groups (if To string exceeds 255 chars), and sending separate mail to each group.
Yuo should modify SendEmail function declared in functions_new.inc.asp to do this.
Currently, SMTP.Send is called only once in this function. You may replace it with multiple calls of SendEx method.
There is no SMTP.FromAddr in the code since FromAddr is set as "Msg.FromAddr = from", and then Msg object is assigned to SMTP.Message property.
Regards,
Alex
|
| Back to Top |
|
| |
L.S.Lim
Guest Group
Joined: 10 November 2003
Online Status: Online
Posts: 262
|
| Posted: 06 November 2005 at 6:19am | IP Logged
|
|
|
Dear Mr.Alex,
Can I have the modified codings?
Also, if I wanted to upgrade it to MySQL, anythings that I should take note of and can it solve the problem?
Thank you,
Regards,
L.S.Lim
|
| Back to Top |
|
| |
Alex
AfterLogic Support
Joined: 19 November 2003
Online Status: Offline
Posts: 2206
|
| Posted: 06 November 2005 at 8:14am | IP Logged
|
|
|
Both MySQL and MS Access have 255 chars limitation for text fields. MS SQL Server, on other hand, allows up to 8000 chars in varchar field.
If you wish to have "long To field" feature implemented for MS Access/MySQL, we may develop it for you in the terms of a custom project. Please contact us at
http://www.afterlogic.com/support/request_support.asp if you're interested in this.
Regards,
Alex
|
| Back to Top |
|
| |
MailBee.NET Objects 
MailBee.NET Queue 
MailBee Objects 
WebMail Pro PHP 
AfterLogic Aurora 
MailSuite Pro for Linux 
Unified Messaging Solution 
Search
Register
Login
Topic: More recipient in To fields
Privacy policy |
Refund policy