I'm not sure why you decided to add Django as a dependency of Mailman but it is a losey idea to add an additional entire operational development platform in order to just get a mailing list up and running.
It is bad enough that the mailman python modules are constantly pinning the CPUs of my systems, but adding Django not only means having to completely rework my apache server configuration, which is strangely enough is not running for the sole purpose of being used as an adjunct to the mail list, but to force feeds an unwanted enormous security hole since it is a development platform which is exposed to the public.
-- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com
On Oct 3, 2017, at 07:41, Ruben Safir <mrbrklyn@panix.com> wrote:
I'm not sure why you decided to add Django as a dependency of Mailman but it is a losey idea to add an additional entire operational development platform in order to just get a mailing list up and running.
You must be talking about Mailman 3, where the web ui and archiver are implemented as Django applications.
Please note that neither Postorius (web ui) nor HyperKitty (archiver) are *required* components so if you don’t like them, you don’t need to deploy them. Core is the only required piece and if you’re comfortable to write your own clients against Core’s REST API, you can do so using whatever technology you want, since it’s just HTTP+JSON. You can augment the functionality currently available via REST with shell access.
Cheers, -Barry
On 10/03/17 10:06, Barry Warsaw wrote:
On Oct 3, 2017, at 07:41, Ruben Safir <mrbrklyn@panix.com> wrote:
I'm not sure why you decided to add Django as a dependency of Mailman but it is a losey idea to add an additional entire operational development platform in order to just get a mailing list up and running.
You must be talking about Mailman 3, where the web ui and archiver are implemented as Django applications.
One thing to be said for Django is that at least it doesn't pull in PHP.
-- Phil Stracchino Babylon Communications phils@caerllewys.net phil@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958
On Tue, 2017-10-03 at 10:24 -0500, Dimitri Maziuk wrote:
You have to admit though, php scripts from 10 years ago still work.
Not always, unfortunately. PHP has implemented some show-stoppers which have required extensive editing of some of our customer scripts here. The deprecation of long array names ($HTTP_*_VARS) is an example. Yes, I can edit the php.ini file to make deprecated forms work, but the default behavior isn't always backward-compatible.
I hacked PHP support into Mailman some years ago for use in archive searches but fortunately my code was pretty simple.
--
Lindsay Haisley | "The first casualty when
FMP Computer Services | war comes is truth."
512-259-1190 |
http://www.fmp.com | -- Hiram W Johnson
One thing to be said for Django is that at least it doesn't pull in PHP.
You have to admit though, php scripts from 10 years ago still work.
Well, not all of them... Some things have been deprecated, and some odd work-arounds for shortcomings no longer behave the way they did because bugs have been corrected or loopholes closed.
--
from my mac to yours...
Keith Seyffarth mailto:weif@weif.net http://www.weif.net/ - Home of the First Tank Guide! http://www.rpgcalendar.net/ - the Montana Role-Playing Calendar
http://www.miscon.org/ - Montana's Longest Running Science Fiction Convention
On 10/03/2017 10:56 AM, Keith Seyffarth wrote:
One thing to be said for Django is that at least it doesn't pull in PHP.
You have to admit though, php scripts from 10 years ago still work.
Well, not all of them... Some things have been deprecated, and some odd work-arounds for shortcomings no longer behave the way they did because bugs have been corrected or loopholes closed.
Oh, come on. It was just a snark.
RedHat in particular is notorious for patching their RPMs without bumping major version numbers. That's how they provide their "stable API platform". As a result your PHP may report it's at version X, but the actual bugfixes and security features are from version Z.a.svn13378337. Go figure out which fine manual you need to read to figure out what incompatible improvements you couldn't live without all these years your PHP installation has today.
Film at 11.
Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
On Tue, 2017-10-03 at 12:02 -0500, Dimitri Maziuk wrote:
Oh, come on. It was just a snark.
Too early in the AM here for snark. My apologies!
--
Lindsay Haisley | "The first casualty when
FMP Computer Services | war comes is truth."
512-259-1190 |
http://www.fmp.com | -- Hiram W Johnson
Hi,
What is the minimum recommended hardware for running and operate Mailman?
If i rent a cloud service with this features: 8 Core Processor Memory: 32 GB 60 GB SSD Operating System: CentOS7
I have a mailing list of 82000, and we send daily email.
With this i could operate or i need more space in the hard drive?
Thanks
Saludos Cualquier duda estoy a tus ordenes. Dios te bendiga. Jesús Rivas Ayudante de Sistemas
T. (01 81) 8123-1293 01 800 836 9407 website | vCard | facebook | twitter
On 10/04/2017 10:38 AM, Jesus Rivas wrote:
What is the minimum recommended hardware for running and operate Mailman?
A Raspberry Pi
(only slightly facetious ;)
If i rent a cloud service with this features: 8 Core Processor Memory: 32 GB 60 GB SSD Operating System: CentOS7
I have a mailing list of 82000, and we send daily email.
With this i could operate or i need more space in the hard drive?
I'm assuming you're talking about Mailman 2.1 and not Mailman 3. My first comment is the RHEL/Centos Mailman 2.1 is something between 2.1.15-24.el7 and 2.1.15-24.el7 depending on which specific Centos 7 release you will have.
The current Mailman release is 2.1.24 and 2.1.25 will be released probably later this month. I.e., the Centos 7 package is 9 or 10 releases old. It's not as bad as it seems because some things from later releases such as DMARC mitigations have been backported as "bug fixes", but still, I would recommend installing the latest version from source.
As to your actual question, I think the configuration you describe is capable of supporting a list with 82,000 members, but see <https://wiki.list.org/x/4030518>.
Your actual issue will not be whether you can support a list of that size, but rather whether your MTA and whatever emailing limits might be placed on you by the cloud host can support 82,000 emails per day (or more realistically in the fraction of an hour that you expect them to be sent).
You definitely need to discuss this requirement with any potential cloud hosting service.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 10/04/2017 06:34 PM, Mark Sapiro wrote:
My first comment is the RHEL/Centos Mailman 2.1 is something between 2.1.15-24.el7 and 2.1.15-24.el7 ...
Ooops. That should be "something between 2.1.15-17.el7 and 2.1.15-24.el7"
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark, thanks for your answer.
I'm clear that cpu, ram etc... its ok.
Actually i have 10mbps and mailman/postfix delivered in 1-2 hour. its greats for us. But i need to move all my servers to the cloud, so, i’m checking for service cloud, and PerfectIP offer 30mpbs (cheap server :D ). My specific question is: with this hard disk (55Gb free space on Centos 7 without graphics desktop), can i manage 100k mailing list.
My main concern is the limited free space.
Saludos Cualquier duda estoy a tus ordenes. Dios te bendiga. Jesús Rivas Ayudante de Sistemas
T. (01 81) 8123-1293 01 800 836 9407 website | vCard | facebook | twitter
On Oct 4, 2017, at 8:34 PM, Mark Sapiro <mark@msapiro.net> wrote:
On 10/04/2017 10:38 AM, Jesus Rivas wrote:
What is the minimum recommended hardware for running and operate Mailman?
A Raspberry Pi
(only slightly facetious ;)
If i rent a cloud service with this features: 8 Core Processor Memory: 32 GB 60 GB SSD Operating System: CentOS7
I have a mailing list of 82000, and we send daily email.
With this i could operate or i need more space in the hard drive?
I'm assuming you're talking about Mailman 2.1 and not Mailman 3. My first comment is the RHEL/Centos Mailman 2.1 is something between 2.1.15-24.el7 and 2.1.15-24.el7 depending on which specific Centos 7 release you will have.
The current Mailman release is 2.1.24 and 2.1.25 will be released probably later this month. I.e., the Centos 7 package is 9 or 10 releases old. It's not as bad as it seems because some things from later releases such as DMARC mitigations have been backported as "bug fixes", but still, I would recommend installing the latest version from source.
As to your actual question, I think the configuration you describe is capable of supporting a list with 82,000 members, but see <https://wiki.list.org/x/4030518>.
Your actual issue will not be whether you can support a list of that size, but rather whether your MTA and whatever emailing limits might be placed on you by the cloud host can support 82,000 emails per day (or more realistically in the fraction of an hour that you expect them to be sent).
You definitely need to discuss this requirement with any potential cloud hosting service.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/jesus%40evangelizacion...
On 10/05/2017 08:23 AM, Jesus Rivas wrote:
My specific question is: with this hard disk (55Gb free space on Centos 7 without graphics desktop), can i manage 100k mailing list.
My main concern is the limited free space.
I think it should be enough as long as the list posts are not too large. I.e., if you were to send a 1 MB message to 100K users with VERP or personalization, that's 100 GB worth of messages and you might have a problem, but if the message is only 10 KB or if delivery is neither VERPed nor personalized so there is only one message copy per tens or more recipients, I don't think it would be an issue.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (8)
-
Barry Warsaw -
Dimitri Maziuk -
Jesus Rivas -
Keith Seyffarth -
Lindsay Haisley -
Mark Sapiro -
Phil Stracchino -
Ruben Safir