Thank you all! That did the trick.
On Mon, 01 Oct 2007 21:40:35 -0700
Evan Platt <[EMAIL PROTECTED]> wrote:
> If you can get to it locally, but not remotely, it obviously isn't a
> spamassassin issue. You made no mention of your setup. Since you
> mentioned you can telnet localhost but not by
On Tue, 2 Oct 2007 at 00:34 -0400, [EMAIL PROTECTED] confabulated:
My mail client doesn't seem to be able to get to my spamassassin
server. When I "telnet 783" from the client, I get:
Trying ...
telnet: Unable to connect to remote host: Connection refused
I can telnet to localh
Ah. Could be that or / too. :)
Not a lot of information to go on ...
At 09:52 PM 10/1/2007, Daryl C. W. O'Shea wrote:
Evan Platt wrote:
If you can get to it locally, but not remotely, it obviously isn't
a spamassassin issue.
Actually, it sounds like he hasn't configured spamd to listen on an
Evan Platt wrote:
If you can get to it locally, but not remotely, it obviously isn't a
spamassassin issue.
Actually, it sounds like he hasn't configured spamd to listen on an
external interface. perldoc spamd..
-i [ipaddr], --listen-ip=ipaddr Listen on the IP ipaddr
Daryl
If you can get to it locally, but not remotely, it obviously isn't a
spamassassin issue. You made no mention of your setup. Since you
mentioned you can telnet localhost but not by the domain name, I'm
guessing you're behind a nat router? If that's the case, the problem
is when YOU behind the na
