>I'm using the spf-mailet now and test it. I found this warning in the log file:
>"No SPF record found for host: googlemail.com"
>
>So I checked "googlemail.com" by mxtoolbox.com
>DNS-Record: v=spf1 redirect=_spf.google.com
Obvious things first - does your setup deal with SPF records for other dom
Hi David,
That's ironic: because of a hint from my provider to set up SPF to be on the
safe side (because of Google!), I dealt with the topic.
And now, of all people, should Google not be configured properly? It would be
possible.
The warning isn't really a problem, I can receive and send ema
Hi David,
That's ironic: because of a hint from my provider to set up SPF to be on the
safe side (because of Google!), I dealt with the topic.
And now, of all people, should Google not be configured properly? It would be
possible.
The warning isn't really a problem, I can receive and send ema
Hi,
> And yes, by other domains all works fine.
sorry, after wrote, the next problem with "myfritz.net":
DNS: v=spf1 ip4:212.42.244.0/24 ip6:2001:bf0:244::/48 -all
I think it's a james-problem.
The problems is with incoming mails, I recieve the mails an can read it without
problems.
Best wi
hi Gunter
>And yes, by other domains all works fine.
Google sucks :-)
--
David Matthews
m...@dmatthews.org
-
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@ja
Hi,
I test the "apache-jspf-resolver-1.0.3.jar" with newest source code and had the
same problem. After some time I fund a solution.
I changed the class "org.apache.james.jspf.impl.SPF".
In the constructor I changed the "executor" form "AsynchronousSPFExecutor" to
"SynchronousSPFExecutor" and
