>David,
>
>I'm happy to know a knowledgeable person related to DKIM. From what I
>can tell, the current james dkim mailet is only usable for non-virtual
>hosting servers, where the server rdns is the same as the 'from' domain
>in the email.
Definitely not - I'm using it on a linode VM.
David,
I'm happy to know a knowledgeable person related to DKIM. From what I
can tell, the current james dkim mailet is only usable for non-virtual
hosting servers, where the server rdns is the same as the 'from' domain
in the email. The james dkim mailet is going to need some modifications
Sorry for belated reply - I'm new to James, but not DKIM, which is pretty much
essential these days if you want the mega providers to not put your email in
spam boxes.
Firstly, DKIM is a per domain thing. You cannot put a single DKIM TXT record in
your server's DNS and expect that will work
Hi Jerry,
Here is what gmail think about your email:
DKIM validation fails. It can be a problem with the way you sign the
mail or a problem with Apache mailing-list implementation.
Could you send me a direct mail to matth...@apache.org so that I can
check?
Cheers,
-- Matthieu Baechler
On Fri,
On 12/28/2019 9:49 AM, Garry Hurley wrote:
I wonder if the problem is not with your setup but with the spam filters on
your recipients’ machines. You might remember that AOL used to be notorious for
marking messages from certain domains as ‘untrusted’ and ‘possible spam’ even
though a large
I wonder if the problem is not with your setup but with the spam filters on
your recipients’ machines. You might remember that AOL used to be notorious for
marking messages from certain domains as ‘untrusted’ and ‘possible spam’ even
though a large percentage of the spam on the Internet
Hi Peter,
Actually this tells me a lot. The message that I posted that you
received and gmail flagged did not come directly from my james server.
My post went to the Apache JAMES forum, and the forum server re-sent it
out to you and other subscribers. Anything related to my JAMES server,
On Fri, 27 Dec 2019 at 16:50, Jerry Malcolm wrote:
> I know just enough about DKIM to be very dangerous... so bear with me
> here...
>
> I am still struggling with mail I send being bounced. In the interim to
> protect my clients, I configured some of my tomcat apps to use Amazon's
> SES (SMTP)
I know just enough about DKIM to be very dangerous... so bear with me
here...
I am still struggling with mail I send being bounced. In the interim to
protect my clients, I configured some of my tomcat apps to use Amazon's
SES (SMTP) service bypassing my JAMES server. I analyzed the mail
