You can use all the solid third party DS, e.g. amazonses, sendgrid, etc. Some mwz users send several million a day with them, though it might be wise to calculate the cost/month of the total delivery incl postmasteryHi,
Simple question:
What server set up (hosting) you would use to send 500/to 600k daily. I have never gotten to that volume
Also how would you set-up the delivery servers and cron jobs.
Thanks!
Hello Napoolion,
To send daily 500-600k you need to have your own server with 64 IPs.
Traffic ------------inbound------------ ------------outbound-----------
rcpts msgs kbytes rcpts msgs kbytes
Total 4737749 4733986 224730775.8 4737444 4737366 227577040.2
Last Hour 3307 3303 57221.0 3988 3988 129181.2
Top/Hour 269617 269598 24183000.8 268337 268337 24061199.5
Last Min. 42 42 583.9 36 36 527.6
Top/Min. 29833 29833 1314417.8 15971 15971 756740.8
Hi,
Simple question:
What server set up (hosting) you would use to send 500/to 600k daily. I have never gotten to that volume
Also how would you set-up the delivery servers and cron jobs.
Thanks!
Didn't understand Your "PICKUP" method clearly@Ibrahim Sharif you achieved that by smtp of pickup?
By pickup directoryDidn't understand Your "PICKUP" method clearly
I use my Infrustructers in 2 Parts mainly. Dedicated SMTP server and Remote Database server of 64 GB RAM to maintain all Campaigns reports there and no lag and risk of maintenance.By pickup directory
So mwz is on a third server? What dbf server do you use? And which ones have you tested? Is it next to the mwz server or far away?my Infrustructers in 2 Parts mainly. Dedicated SMTP server and Remote Database server
Is splitting the database significantly faster? But does it take longer to pull the data for whole camp reports? And with risk of maintenance you mean no risk of loosing data or dbf integrity when deleting the logs or what?Remote Database server of 64 GB RAM to maintain all Campaigns reports there and no lag and risk of maintenance.
Relay usually means sending via third party delivery server.This means I use "Relay method" right?
yes MW is on remote Server and i connect from remote to my SMTPs. MySQL format. both local MW and Remote MW tested and Remote is safer and painless.So mwz is on a third server? What dbf server do you use? And which ones have you tested? Is it next to the mwz server or far away?
i just use high ram and remote server to keep safe MW database. and while SMTP maintenance or any other issue dont harm main campaign reports.Is splitting the database significantly faster? But does it take longer to pull the data for whole camp reports? And with risk of maintenance you mean no risk of loosing data or dbf integrity when deleting the logs or what?
Yes. MY SMTP servers like Relay.i can use any 3rd party to connect to it from any app,script and be able to send emails with DKIM sigining .Relay usually means sending via third party delivery server.
yes MW is on remote Server and i connect from remote to my SMTPs. MySQL format. both local MW and Remote MW tested and Remote is safer and painless.
i just use high ram and remote server to keep safe MW database. and while SMTP maintenance or any other issue dont harm main campaign reports.
i forgot to include one thing.
I HAVE A DEDICATED 16 IP NAMESERVER FOR DNS HOSTING ONLY.
It is really helpful when you use 100+ Domains in your hands and keep more safe.
Yes. MY SMTP servers like Relay.i can use any 3rd party to connect to it from any app,script and be able to send emails with DKIM sigining .
Yes when i faced that only 1 IP caused 2 days of hardwork what happened and all of my Fresh Domains showed i am blacklisted then i build this DNS server to cover this issue. No mailing no black things or even White things from those IP, Just Domain Parking Lot. when i need to use separate server for any domain i just Transfer that part of DNS to my new Server.Seems you have a good setup!
Especially the nameserver part, which might help avoid problems with over-burdened registrars
Of course Faster !. My previous and almost 95%+ PMTA server installers,maintainers setup all things on same server. this cause serious trouble. I heard that Sometimes Database got corrupted and All reports vanished.the whole thing then was broken.From what you wrote it seems you have split the database, if so, does it make things faster?
Didn't try yet Amzons Servers. My Servers DISK TYPE is NVMe and RAIDED for 1 DISK FAILURE. so if main disk fails then the backup disk will run from same state. Same size 2 NVMe Disks to run the server.Have you tried with Amazon Aurora? It can handle databases up to 4TB size (last time checked) and is super-duper fast
You mean it gives the domains a clean rep before they get used?No mailing no black things or even White things from those IP, Just Domain Parking Lot.
Yeah, that is an F-My previous and almost 95%+ PMTA server installers,maintainers setup all things on same server.
Yup, they r gr82 NVMe Disks to run the server
Real scalability on the fly is hard to find:From about 50M sendings and with 5M Users i saw total Disk Space was 48GB*** [ df -h] all partitions collectively.
To expand partition Sizes and saving some pains in future i suggest to increase /var partitions for RedHAT and CentOS users. /home is enough 100GB for SMTP handler servers.
Its actually saving any harm from Hosted IP and relaxing All Mailer Domains to multiple IPsYou mean it gives the domains a clean rep before they get used?
The List Subscribers, Delivery Logs , and all others in 3 partsWhere did you split the database (which tables in which part)?
Interesting approach, so the subs are on the mwz server, the ds logs remote on a 2nd server, and the rest remote on a 3rd server?The List Subscribers, Delivery Logs , and all others in 3 parts