Charlie Brady wrote:
Suppose you have two addresses that forward to each other, either both
on the local server or one remote and one local.
qpsmtpd doesn't do forwarding between addresses, so doesn't need to
address this issue.
You may be right about purely local forwarding, but what about
I've been using the following, though I don't recall how I obtained it. I
checked my logs (28 days worth) and it hasn't rejected anything in that
time. I haven't done any direct testing.
==
#!/usr/bin/perl
=head1 NAME
loops
On Thu, 14 Feb 2008, Chris Lewis wrote:
Like Solaris usually does (grr), "hostname" returns the host node name (no
dots), not the FQDN. config/me contains the FQDN, but
$self->qp->config("me") _still_ returns the node name. I see the "sub
config" code uses `hostname` as the default, but shou
On Sat, 16 Feb 2008, Keith Ivey wrote:
Charlie Brady wrote:
> Suppose you have two addresses that forward to each other, either both
> on the local server or one remote and one local.
qpsmtpd doesn't do forwarding between addresses, so doesn't need to
address this issue.
You may be rig
Something changed somewhere at some point, unclear if it was on
spamassassin's side or qpsmtpd's, or related to some wierd network
issue, but we've started seeing something (possibly lost FIN packets,
but that makes little sense) causing qpsmtpd to hang waiting for the
spamassasin connection to fi
