T 20090705 193140 4a50e03d Begin processing job MO000002 from postmaster@mail.server.jaaps.nl
W 20090705 193201 4a50e03d Error connecting to primary server '216.239.59.27'.
W 20090705 193223 4a50e03d Error connecting to alternate server '209.85.216.92'.
W 20090705 193244 4a50e03d Error connecting to alternate server '74.125.93.114'.
W 20090705 193305 4a50e03d Error connecting to alternate server '74.125.79.114'.
E 20090705 193305 4a50e03d Processing of job MO000002 incomplete or failed.
T 20090705 193305 4a50e03d Job MO000002 processing complete.
These are valid Google MX hosts. The first thing you need to do is turn on MercuryE session logging to see if you can determine why the connection is being rejected by these valid MX hosts. I assume you do have a fixed IP address but I see that the primary domain does have a SFP record and that may be causing the problem.
Answer Section:
jaaps.nl, MX, 100, mx-in-2.webreus.nl
jaaps.nl, MX, 10, mx-in-1.webreus.nl
jaaps.nl, A, 212.61.10.111
jaaps.nl, SOA, ns1.webreus.nl, hostmaster.webreus.nl (Serial=2009041403, Refresh=3h, Retry=1h, Expire=7d, Minimum=1h)
jaaps.nl, TXT, "v=spf1 a mx ?all"
jaaps.nl, NS, ns3.webreus.nl
jaaps.nl, NS, ns1.webreus.nl
I believe the ?all is neutral and implies that the sending from this domain may be somewhat restricted. If the receiving servers treat this a restricted to the MX hosts and A record only, i.e.
v=spf1 a mx -all
, then you can't send from your IP address using MercuryE. I may be completely wrong here but this screwy protocol causes a whole lot more problems than is solves and has little or no affect on spam.
<blockquote>T 20090705 193140 4a50e03d Begin processing job MO000002 from <a href="mailto:postmaster@mail.server.jaaps.nl">postmaster@mail.server.jaaps.nl</a>
W 20090705 193201 4a50e03d Error connecting to primary server '216.239.59.27'.
W 20090705 193223 4a50e03d Error connecting to alternate server '209.85.216.92'.
W 20090705 193244 4a50e03d Error connecting to alternate server '74.125.93.114'.
W 20090705 193305 4a50e03d Error connecting to alternate server '74.125.79.114'.
E 20090705 193305 4a50e03d Processing of job MO000002 incomplete or failed.
T 20090705 193305 4a50e03d Job MO000002 processing complete.</blockquote><p>These are valid Google MX hosts.&nbsp; The first thing you need to do is turn on MercuryE session logging to see if you can determine why the connection is being rejected by these valid MX hosts.&nbsp; I assume you do have a fixed IP address but I see that the primary domain does have a SFP record and that may be causing the problem.</p><p>Answer Section:
&nbsp;&nbsp;&nbsp; jaaps.nl, MX, 100, mx-in-2.webreus.nl
&nbsp;&nbsp;&nbsp; jaaps.nl, MX, 10, mx-in-1.webreus.nl
&nbsp;&nbsp;&nbsp; jaaps.nl, A, 212.61.10.111
&nbsp;&nbsp;&nbsp; jaaps.nl, SOA, ns1.webreus.nl, hostmaster.webreus.nl (Serial=2009041403, Refresh=3h, Retry=1h, Expire=7d, Minimum=1h)
&nbsp;&nbsp;&nbsp; <b>jaaps.nl, TXT, "v=spf1 a mx ?all"</b>
&nbsp;&nbsp;&nbsp; jaaps.nl, NS, ns3.webreus.nl
&nbsp;&nbsp;&nbsp; jaaps.nl, NS, ns1.webreus.nl</p><p>
I believe the ?all is neutral and implies that the sending from this domain may be somewhat restricted.&nbsp; If the receiving servers treat this a restricted to the MX hosts and A record only, i.e. <code>v=spf1 a mx -all</code>, then you can't send from your IP address using MercuryE.&nbsp; I may be completely wrong here but this screwy protocol causes a whole lot more problems than is solves and has little or no affect on spam.
</p><p>&nbsp;</p><p>&nbsp;</p><blockquote>&nbsp;</blockquote>