On Mon, 2020-04-20 at 13:15 +0100, David Matthews wrote: > > Hi, > > > > I am about to deploy a James instance for personal usage. I have a > > restricted budget (say 50€/month) so I'm looking for the best setup > > possible for that target. > > hi Matthieu > > It's not so easy to understand what information you're hoping for,
You are right. Thanks for your try, I will try to refine my questions. Given my budget, I'm wondering which hardware/software combination is the more relevant. For example: * Should I take a big VM and choose Postgres/JPA backend with ActiveMQ and Lucene? * Should I choose a big VM with Cassandra/ElasticSearch and Rabbitmq? * Or should I go the container way with docker compose and another selection of software component? Each solution has some benefits and as I didn't had to target that kind of setup in the past, I'm wondering what people do. > but I assume some sort of virtual machine offering is going to meet > your needs. I have experience of VMs at Bytemark and Linode, but I'm > not well informed about which companies offer the best service/price, > although both of those two are OK. > > > * IMAP + SMTP (in and out) > > * TLS + SPF + DKIM > > You're talking about working to a budget and deploying your own James > server, so surely you'll deal with configuring James to give IMAPS > access and SMTP yourself? Yes, configuring is not an issue. > Here's my 2 cents worth on SPF and DKIM. > > 1)It's absolutely essential that you configure your domain's DNS with > these (and also DMARC) and that James signs outgoing email with your > DKIM private key. If you don't do that you'll be relying on > recipients at yahoo, gmail, hotmail etc to whitelist your email > address to get them delivery to inbox rather than junk folders. Thank you for the tip. > 2)The effective way to avoid get deluged with incoming spam yourself > is to configure James to use DNSBLs. If you do that, my experience is > that you don't really need to worry about checking SPF and DKIM (or > DMARC) on incoming email. Fact is that most spammers are already in > these blocklists, so just dropping everything that has been caught > there will solve the incoming spam problem at least 95%. I find that > with that in place even running spamassassin offers little extra. Ok, good to know > Here's a couple of Howto's to set up James (including IMAPS, DKIM and > DNSBL) > > https://dmatthews.org/java_email.html > > and to configure your domains DNS with SPF, DKIM and DMARC. > > https://dmatthews.org/email_auth.html > > That last page is rather tinyDNS specific, but it will be of some > help even if your domain's DNS server uses some other system, in > which case feedback would be appreciated and will be added to that > page. > I will definitely look at your guides, they look great. -- Matthieu --------------------------------------------------------------------- To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
