So yesterday I did yum upgrade, change my plan at DigitalOcean for a bigger server
and figure my public DNS propagation was’nt totally spread because, sometimes, I was receiving a response from my old smtp.
So this morning I emailed at check-auth@verifier.port25.com
with and without the AntiVirus on and
1st : it’s work I send and receive
2nd : I receive the same result.
###Summary of Results
SPF check: pass
DomainKeys check: neutral
DKIM check: pass
Sender-ID check: pass
SpamAssassin check: ham
Everything looks good for me, and you ?
Thanks for your concern
When I type hostname -f
I get SERVER.DOMAIN not SERVER.DOMAIN.TLD
so to get SERVER.DOMAIN.TLD
I had to set my domain to DOMAIN.TLD ie. example.com
Silly mistake, Reading is fundamental, I wish I read the documentation before installing and using the software. ooppss…
@JOduMonTAlso Please Note in your Original Post please stress the importance that the CNAME records MUST end with a period (.) To aid with deliver-ability I would like to ask for you to add to your original post a section about RDNS and advising the Admins to contact their ISPs to configure reverse DNS
I’m sure the error is different and it says which line the error is. Look at the line and you’ll find the problem.
Please, cut’n’paste the error (or take a picture/screenshot).
I think that the first implementation could live without a web interface.
We need to automatically create the key during domain creation.
The interface has to show the key only, it shouldn’t be hard to add.
$enable_dkim_verification is to check incoming mail, it could be a default regardless of this sign feature.
I updated issue 1910 (http://dev.nethserver.org/issues/1910), but I’m still unsure about effectiveness of dkim (I’m using it).
Who has experience and wants to contribute data could add comments here.
@filippo_carletti DKIM is only for validating of our MAIL server for external servers like GOOGLE and so on , so without DKIM google could mark our letter like spam.
It’s not that easy, you control (through dns) how others should behave regarding dkim. And dkim setup is easy for a spammer. Assuming dkim pass as an ham indicator is a bad idea.
This is my second time doing DKIM, per the instructions on this page, this time I get the following errors:
amavisd -u amavis -g amavis showkeys#
No DKIM private keys declared in a config file
amavisd -u amavis -g amavis showkeys
Error in config file “/etc/amavisd.conf”: Undefined subroutine &Amavis::Conf::HASH called at /etc/amavisd.conf line 295.