OpenEMM Support

sfantul · Joined: 15 Aug 2006 Posts: 40

I want to broke openemm in modules that stay on different computers.
Mashine 1: the database
Mashine 2: python ,c scripts and sendmail
Mashine 3: openemm interface
Mashine 4: openemm redirection server

Is this possible?
What i want to know to be more exact is how this 4 entities interact.
What i know:
The database is easy to separate from others .
-for this we have to properlly modify emm.properties ,agn.py and Mailgun.ini (By the way who uses this file beside webapps? and if nobody else uses it why cant be used just "emm.properties")

Both webapps write some log files to disk in the openemm file system (but i dont think this is a big problem they could write them anywhere. no other script use them).

Console app write some xml to disk when sending mails that the other scripts fetch. This is the first big problem.

Are there any other problems?
The redirection app for example have any contact with the filesystem ? (beside log files of course)

sfantul · Joined: 15 Aug 2006 Posts: 40

I'll answer myself .
Openem can be relatively easy split on 3 mashines .
1) Openemm user, filesystem , python and c script, sendmail and openemm interface
2)database
3)Redirection server.
This is important because the redirection server could be put in a location where a good uptime is ensured and also the database.
The interface doesnt need to be online all the time.

marton · Joined: 09 Aug 2006 Posts: 36

hi,

does it work? do you run openemm on three machines?

thanks in advance, marton

sfantul · Joined: 15 Aug 2006 Posts: 40

yes, I do , i have :
- the database on a mashine
- the interface , python scripts, log files , etc on an other mashine
- redirection (public) server on another mashine

ma · Posted: Wed Feb 21, 2007 9:23 am Post subject: distributed openemm

sfantul, I am curious: How many mails per hour can you send with this configuration?
_________________
The OpenEMM Team

sfantul · Joined: 15 Aug 2006 Posts: 40

Currently i have a mailing list of 600k subscribers and i limit the mailing to 50k per hour (but it can do better).I did this limitation because of the notifications that i receive from some domains that my mailing rate is too high.
But the mailing rate has nothing to do to with this configuration , its all about configuring sendmail (when i started i had a rate of 10k per hour max). I tried a lot of things to make the sending rate higher.

First big breakthrough was to split the queue folder in 10 folders with persistent runners on every queue
$sm -qp1s -NFAILURE -OQueueDirectory=$BASE/var/spool/QUEUE0
$sm -qp1s -NFAILURE -OQueueDirectory=$BASE/var/spool/QUEUE1
...
$sm -qp1s -NFAILURE -OQueueDirectory=$BASE/var/spool/QUEUE9
changing pickdist.py and mailer.sh accordingly and sorting the queue after the host. here are my defines in sendmail.mc:
define(`confQUEUE_LA', `50')dnl
define(`confREFUSE_LA', `51')dnl
define(`confCON_EXPENSIVE',`true')dnl
define(`confTO_ICONNECT', `5s')dnl
define(`confQUEUE_SORT_ORDER', `Host')dnl
define(`confMIN_QUEUE_AGE', `3h')dnl

This was a big improvement, but finally i'm using an extra postfix mailer as a smarthost which give me the results i was talking about.
The disadvantages of this last solution are that u need to also configure an postfix mailer and that the first type of bounce management does not work properlly.

joedj · Joined: 22 Apr 2008 Posts: 2

Hi sfantul,

We are interested in doing something similar. Can you tell us what kind of changes you made to pickdist.py to use the multiple queues, or provide a copy? I know this was a while ago now... :)

dcunniff · Joined: 14 Oct 2008 Posts: 4

Hi guys,

I'm looking for the same information if it could be provided. I too understand this was a long time ago.