Re: a bit additional work required on openSUSE 15.2 with James 3.5.0

Hey guys,

I got "inspired" by this topic to write down a guide myself. Although I 
only have SPF set up right now I may take the time to also have a look 
into DKIM and DMARC. It won't be perfect, but same as with Davids guide: 
It should others new to James get started.

I'll happy to contribute, even if it's just a rather long wall of text.

Greetings,

Matt

Am 29.09.2020 um 08:12 schrieb Tellier Benoit:
> Yes, SPF, DKIM but also DKIM spam handling is techie topic for "Self
> Hosting" use case.
>
> Having a bit more doc regarding that could be nice too.
>
> On the new documentation [1] we would benefit from having a "setting up
> SPF & DKIM" section
>
> [1]
> https://github.com/apache/james-project/tree/master/docs/modules/servers/pages/distributed/configure
>
> Cheers,
>
> Benoit
>
> Le 29/09/2020 à 12:59, David Matthews a écrit :
>> Hi Tellier
>>> I gave your link a read and found it very interesting.
>>>
>>> Especially I believe the SPF part would deserve more visibility.
>>>
>>> Would you agree sharing it on the Apache James community website as a
>>> "How to" ? [1] [2]
>> Yes of course.
>>
>> Regarding SPF, I'd add that DKIM is also a must and the info at
>>
>> https://dmatthews.org/email_auth.html
>>
>> should be equally visible. I found out the hard way that these days, if you try and run an email server without implementing SPF and DKIM for your domains, the mega providers will silently put all your mail in junk boxes. Not so convinced about DMARC which I don't really see the point of, but you may as well have that also as it's not difficult to implement.
>>
>> Somewhat grudgingly, I have to admit that these technologies do make some sense, apart from raising the bar by gmail, hotmail etc against people like me that just want to run their own email or provide a service for a small number of customers.
>>
>> I do check incoming mail for SPF (but not DKIM) and I have spamassassin sitting in the background, but it very seldom has to take action. Just  dropping anything from an IP in a DNSBL pretty much solves the spam problem. A relative of mine that uses one of the mega providers recently observed to me that there is very little in his spam box these days. Putting spammers out of business is good!
>>
>> --
>> David Matthews
>> [email protected]
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>