PDA

View Full Version : Issue with 'Too many recipients'


EvdM
9th November 2006, 08:02
Dear All -

I need to send an e-mail invitation to a list of about 2000 addresses. If I try to do this from Thunderbird of Outlook (IMAP accounts to ISPConfig on Perfect Debian), I get an error: 'Too many recipients'.

Is there some way to (maybe temporary) increase the allowed total of recipients in Postfix (I assume)? Or is this general bad practice which should be handled in a totally different way? This mass mailing is something which I do not have to do very often, so I would prefer a simple 'fix'.

Thanks for all suggestions!

Erik

till
9th November 2006, 10:38
Is there some way to (maybe temporary) increase the allowed total of recipients in Postfix (I assume)? Or is this general bad practice which should be handled in a totally different way? This mass mailing is something which I do not have to do very often, so I would prefer a simple 'fix'.

Yes, its bad practice to send mail to 2000 recipients at once. The problem is not only the max recipients limit which you may change in the postfix main.cf file. The other problem is that when you send a email to 2000 addresses with BCC, if only one email address is incorrect, the complete sending process will fail and you will get back the mail with an error.

Either use a mailing list software for that or a nice (non free) windows tool for newsletters is groupmail, which sends the emails one by one and not at once like outlook or thunderbird.

EvdM
9th November 2006, 13:43
Thanks a lot for this clear answer. I will resort to the mailing list solution.

In these forums there are many references regarding running a list in ISPConfig. In fact, there are so many references that I kind of get lost.
Is there a specific recommendation for a very simple list implementation which works well? I have some basic mailman experience, but am no expert by any means.

Any suggestion or pointer is well appreciated, thanks a lot!

Erik

edge
9th November 2006, 14:34
I'm using MailWorksPro, but maybe this is something for you? http://www.phplist.com/

EvdM
11th November 2006, 09:39
I'm using MailWorksPro, but maybe this is something for you? http://www.phplist.com/

That seems great for that I want to do, thanks!

I have installed it, and ran into the following issues:

The installation created this .htacces file:


DirectoryIndex index.php

<FilesMatch "\.(php|inc)$">
Order allow,deny
deny from all
</FilesMatch>
<FilesMatch "(index.php|dl.php|ut.php|lt.php|download.php)$">
Order allow,deny
allow from all
</FilesMatch>
php_flag magic_quotes_gpc on


This seems to leave the directory inaccessible (error 500) in the ISPConfig Apache configuration.
If I remove .htaccess this problem seems gone. However, I am not sure if that leaves me vulnerable.

Also, if I try to access phplist like this (without the .htaccess), I get an error page:


Error: please make sure that index.php is your default document for a directory
If you have just installed PHPlist and get this message, make sure that your Apache configuration has somewhere

DirectoryIndex index.php index.html

or that at least index.php is mentioned before index.html
For other webservers please consult your manual to find how to make index.php be the default document for a directory.


I assume this has to do with the missing .htaccess, but could be something in the Apache2 configuration too...

I hope someone can suggest how to tackle this. I am out of clues...

Thanks a lot!

sjau
11th November 2006, 13:17
you need to set the options for the virtual host or that directory specifically to AllowOverride through .htaccess files.

http://httpd.apache.org/docs/1.3/howto/htaccess.html#troubleshoot

However since I don't have ISPConfig I don't know how to enable that in ISPConfig...

till
11th November 2006, 14:50
you need to set the options for the virtual host or that directory specifically to AllowOverride through .htaccess files.

http://httpd.apache.org/docs/1.3/howto/htaccess.html#troubleshoot

However since I don't have ISPConfig I don't know how to enable that in ISPConfig...

Add the following line in the apache directives field of the website in ISPConfig:

AllowOverride All