This section is now READ ONLY, please choose the section below that fit your question !
did you modify the exim_stage2.conf_template file ? there should never be delivery attemps at this stage because it is a queue only configuration.
Eventually try to find out these messages IDs in the exim_stage1 log file.
olivier wrote:just to be sure, is "email@example.com" the real address you are using ?
Well, firstname.lastname@example.org. I shortened it to domain.com for simplicity.
olivier wrote:did you modify the exim_stage2.conf_template file ?
Yes, but only after several thousand messages started piling up. The only change was to shorten the retry interval.
olivier wrote:Eventually try to find out these messages IDs in the exim_stage1 log file.
Here is what's in the exim_stage1 logfile with that message ID. It was a single entry.
Code: Select all
2006-11-29 18:31:02 1GpUD0-0000Jj-Qb => email@example.com R=filter_forward T=local_smtp H=127.0.0.1 [127.0.0.1] C="250 OK id=1GpUD0-0000Jp-T3"
olivier wrote:A full stock MailCleaner based on a decent hardware (P4, 2Ghz, 2GB RAM), will process up to 50'000 messages per day without a glitch.
With some customizations and tunings, you can go up to 150'000 or even 200'000 messages per days.
Can you comment on what types of tuning? While we're testing, the load is around 10,000 per day. But once these spool delay issues are resolved and we are comfortable doing so, we're going to shift several other high traffic domains over which will push well above 50,000 per day. If we can tune to 75,000 or 100,000, that would delay the need to invest in a second MC server (along with avoiding the double colocation expenses).
This cannot be generalized.
Basicaly, it's hardware optimization (drives, ram), OS optimization (partitions shemes, limits, cpus usage, etc..) and network too (dns caching, databases synchronization, etc..).
When I said 200'000 per day, it's a low estimation because we always want to keep some security, so we don't have systems that goes beyond that, although they surely could (this is per host of course, we have customers that are working with more than millions mails per dayon their clusters).
Anyway, I always suggest people to invest into at least a second host. This is for redundency and backups.
You should first check the MailCleaner has all required ports open to the outside as this will of course be a performence killer !
Another server does greylisting and RBL checks (to unload that from MC), leaving MC server to do Razor, Pyzor and DCC. I'm surprised that disabling Pyzor alone had (-seemingly-) such a dramatic performance improvement.
I know that is very subjective, seat-of-the-pants, but I didn't take any specific metrics.
Needless to say, I'm very curious if your problem could be related to the ClamAV (module) as well, and what would happen if you switch to the old ClamAV rather than ClamAV (module)?
Who is online
Users browsing this forum: No registered users and 2 guests