On 18 Feb 2008, at 12:27, Jeff Buehler wrote:
Hi all -
Sorry to be late to the game with this - in an earlier list email that I
inadvertently deleted (thinking I had no helpful input, of course!)
titled Problem with XMail on NetBSD-4 there was a discussion about the
error:
Recipient
Hi David -
I think I have finally solved this mysterious problem, and of course it
was an element I had not even considered (as it often is). The line
provider (Covad) for this server had a problem several weeks ago with
this line, about the time I was updating xmail to 1.25. When they were
Hi David -
I spoke too soon! The problem has reappeared, and consistently. So it was
NOT the line speed issue.
I will test SmartDNS settings and post the results. Presently
/etc/resolv.conf is set to the m0n0wall router on the LAN.
Jeff
Jeff Buehler wrote: Hi David - I think I have finally
On Tue, 19 Feb 2008, Jeff Buehler wrote:
Hi David -
I spoke too soon! The problem has reappeared, and consistently. So it was
NOT the line speed issue.
I will test SmartDNS settings and post the results. Presently
/etc/resolv.conf is set to the m0n0wall router on the LAN.
Are you using
Hi Davide -
Everything works when I use SmartDNS host to point to the same resolver
as the server uses (a m0n0wall router).
If I do not use SmartDNS host, I get the error to domains that can
receive email from other sources.
One example domain is trikorausa.com, although I am getting reports
On Tue, 19 Feb 2008, Jeff Buehler wrote:
Hi Davide -
Everything works when I use SmartDNS host to point to the same resolver
as the server uses (a m0n0wall router).
If I do not use SmartDNS host, I get the error to domains that can
receive email from other sources.
One example domain
