Search results

Will you describe in some way tech specs and configs for that real-world scenario? Maybe in form of a step-by-step tutorial, like "buy a 5-10-100-1000$ vps/aws/hardware server, install mailwizz+postfix/exim/powermta, make some config here and there, and that's your result in 700 mails per sec"))

If you're using PHP Mailer - try to modify its component for use base64 encoding. It is somewhere in apps/common/components/mailer/MailerPHPMailer.php protected function getMailer() { ... $this->_mailer->Encoding = "base64"; ... }

Can you PM me a link to your service/pricing/other useful info? We're moved away from thread topic)))

Good solution)) How many emails you're sending a day with such installation? And what way of processing emails (plain smtp, local pickup, redis)? We're testing different methods now for increasing sending speed. Stuck at 3-4k per minute per server.

In that case we're suggesting them to resubscribe users. It's additional list cleaning process, that may be useful. Anyway this situation totally depends on your customers. If you can trust them, it won't be problem to import their lists. But in our case it's not an option.

Oh, we just not allowing to import subscribers (except exported from our service as a backup). It's a usually very bad idea to allow customers to import they lists - it's like 90% that he is a spammer)))

Something like 10minutesmail? yeah, good idea to block such domains. And maybe tech accounts that normally shouldn't be used for subscribing, like info@, admin@, support@... etc

@justme Totally agree)

There is one little issue with FBL and Blacklisting) Some people just marks all letters as SPAM, even first confirmation letter, then subscribe again and again. Such people must go in blacklist.