[<prev] [next>] [<thread-prev] [month] [year] [list]
Date: Fri, 21 Mar 2003 03:10:24 +1100
From: Mick <asurfer@...g.com.au>
To: popa3d-users@...ts.openwall.com
Subject: Re: popa3d[28669]: Didn't attempt authentication
Ok.
While the connecting IP is now being logged, I'm still seeing the same
authentication error:
Mar 20 09:03:23 X xinetd[595]: START: pop3 pid=8197 from=X.X.X.X
Mar 20 09:03:24 X popa3d[8197]: Didn't attempt authentication
Mar 20 09:03:24 X xinetd[595]: EXIT: pop3 pid=8197 duration=1(sec)
I checked and X.X.X.X is indeed the IP of the person who has an account
on the machine (the account is only there until I figure out how to
enable virtual user support in popa3d).
Solar Designer wrote:
>On Thu, Mar 20, 2003 at 11:47:35AM +0100, Michael Meyer wrote:
>
>
>>Mick wrote:
>>
>>
>>>Not surprisingly, the client he uses is Microsoft Outlook.
>>>
>>>
>>which version of popa3d? perhaps you should try to update to
>>popa3d 0.6.2.
>>
>>
>
>Yes, but this isn't related to the "problem" Mick is experiencing.
>There has been no such bugs.
>
>Mick, -- I am wondering why you had to setup the iptables rules to
>catch this, don't you log IP addresses connecting to popa3d with your
>[x]inetd, tcpd, or popa3d itself (if in standalone mode)? If you
>don't, then this is what you need to fix first. I've updated INSTALL
>included with 0.6.2 to be a little more verbose about how to approach
>this.
>
>
>
Hosted by DataForce ISP -
Powered by Openwall GNU/*/Linux