On Thu, 5 Jun 2003, Simon Byrnand wrote:

> >
> > I'm trying to get SAProxy working. According to the docs, I should point
> > my OE at 127.0.0.1, and then change my account to
> > "account_name:server". After I do this, I'm getting authentication
> > failures. I looked in my server log, and did some traces and I find that
> > the account is begin submitted as "account_name:server" instead of just
> > "account_name".
> >
> > I've gone over the OE config a few times, and its OK. The Host Map in
> > SAProxy looks good, so I'm now wondering if this is a perl issue of some
> > kind.
> >
> > Any ideas?
> 
> One - do you have any virus scanners installed on the computer ? Most
> virus scanners these days include a pop3 proxy server, so if that is
> installed/enabled then there may *already* be something listening on
> 127.0.0.1 port 110 before you run saproxy :)

Yes I am running Norton, but that doesn't sound right. I don't think you
can have two people listening on the same IP/port at the same time, one of
them gets an error. At least on Unix you can't. Who knows what MS allows.

In any case, I turned off Norton's email scanning and it still fails. I
could have sworn it worked once, but then as I started to install Perl
modules for spamassassin itself, there was such a blur of new perl
releases and modules that I wonder if its a bad interaction with another
module or something. There seems to be alot of confusion about Net::DNS in
particular. But I did uninstall all of Active Perl, and then reinstalled,
tried two different releases.

Any other ideas?

-- 

Jack Gostl      [EMAIL PROTECTED]




-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to