Errors not showing up in logs
bubsy119 - May 18, 2009 - 07:16
| Project: | Mass Contact |
| Version: | 5.x-2.4 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
For a long time the module worked fine for me. There was no problem sending the Mass contact emails to 940 subscribers.
But since a few weeks i get errors when the admin sends the Mass contact, it shows the message that there are 13 errors.
When going to the logs to see these errrors, there are no messages for the Mass Contact.
It still uses the same emailadresses as before. I've tried to set the max emails for one run to 50, 100, ... -> still no luck
What can i try to fix this asap ?

#1
If you are and were using 5.x-2.4, then nothing changed in this module to cause your problems. If you are using the 5.x-dev release, then maybe you should try using the 5.x-2.4 version.
The error messages could be coming from a different module, for example, if you are using the SMTP Authentication Support module to send the e-mails, the error messages might be coming from it, instead of Mass Contact.
#2
@ oadaeh Thx for your reply.
We're using 5.x-2.4 and didn't changed anything.
There were no other modules installed the last couple of months, and were not using the SMTP Authenticatin module.
The website is hosted at Bluehost. They say that there is a limit of 750 sending e-mails in one hour. (In the Mass Contact module we have set to break up at 300 e-mails).
#3
The best thing I can come up with at this time, is that there are several e-mail addresses that are no longer valid. As I said, nothing has changed in that version of the code, and if you have changed nothing with the configuration of your site, then you are left with only a couple of directions to look: your host and your users. If you are pretty sure your host has not changed anything (which is not out of the realm of possibility), then you really need to see if you can verify that all the e-mail addresses are valid.
Breaking up the e-mails will not fix the per hour limit issue. If you are getting 13 errors (instead of 4) when you break up the recipients into groups of 300, then it is definitely the users' e-mail addresses you need to be looking at.
I have a question regarding your host's per hour limit: if you send an e-mail that includes 300 recipients, do they count that as one e-mail or 300? If they are only counting the number of e-mails (which they should) and not the number of recipients (which they should not), then you should be fine with sending through Mass Contact. I thought I remembered them having a max number of recipients per e-mail, however, so you might want to check that as well.
#4
Today the admin tried to send another mass Contact. But still no luck.
I've installed the module again, but it seems there wasn't a problem with that becouse the problem is still here.
There are 800 subscribers.
I tried to split up the users for testing at 790.
Now i get the following message:
* [Success] Send Remainder: example@email.com, example2@email.com, example3@email.com, example4@email.com, example5@email.com, example6@email.com, example7@email.com, example8@email.com, example9@email.com, example10@email.com,
* 1 errors encountered sending message. Please check the logs and try again.
The users at Send Remainder do they received the mail ?
The other (790) users didn't receive any email.
*********************************************************
EDIT:
@bluehost (Hosting) they say that they have a new limit:
"The 20 recipients is a new limit. If you need to send to more then 20 recipients at a time we suggest you set up a mailing list."
So i tried to breaking up the email into 20 e-mailadresses.
Now i did get 8 succesfull sendings and
32 errors encountered sending messages. Please check the logs and try again.
But still no errors inside the dblog :-(
*********************************************************
What's the best and fastest way to verify all the e-mailadresses are valid ? Or can i ignore that option in anyway ?
Still no errors or anything in the dblogs, is there any other place or method to see these errors ?
#5
Yesterday we tested the site with another host and all problems are gone. So it seems that there was a problem with the settings/restrictions at bluehost.
#6
Thanks for the update.