Michael Bowe wrote:
Try something simple like
telnet 127.0.0.1 pop3
user [EMAIL PROTECTED]
pass password
I've tried with courier pop3.
observe# telnet 127.0.0.1 110
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
+OK Hello there.
USER [EMAIL PROTECTED]
+OK Password
Hi,
On Wed, 2004-01-14 at 11:24, Andrea Riela wrote:
Try something simple like
telnet 127.0.0.1 pop3
user [EMAIL PROTECTED]
pass password
I've tried with courier pop3.
observe# telnet 127.0.0.1 110
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
+OK Hello
Anders Brander wrote:
+OK POP3 clients that break here, they violate STD53.
Is this an error or a warning? It does return +OK and
nothing seems wrong about the output? Is there actually any
mail waiting? Please double-check.
I don't know, in my opinion is a bug, I've never seen that with
On Wed, 2004-01-14 at 10:10, Andrea Riela wrote:
Anders Brander wrote:
+OK POP3 clients that break here, they violate STD53.
I don't know, in my opinion is a bug, I've never seen that with qmail-pop3d,
only with courier-imap pop3 and pop3-ssl. There's probably a problem.
what exactly is a
Jeremy Kitchen wrote:
It states clearly that POP3 clients that break here, they
violate STD53 That is courier saying that. It doesn't HAVE to be
there, but it can be.
It's a courier bug, for you?
Another thing:
they look like successful logins to me. You have an MUA
issue, and are
On Wed, 2004-01-14 at 10:28, Andrea Riela wrote:
Jeremy Kitchen wrote:
It states clearly that POP3 clients that break here, they
violate STD53 That is courier saying that. It doesn't HAVE to be
there, but it can be.
It's a courier bug, for you?
no, I'm asking you, what do you think is
I assume you
are mailing the list because you are having a problem, am I incorrect?
No, I'm incorrect.
When I've seen
+OK POP3 clients that break here, they violate STD53.
I've supposed that's a bug, or that's a strange thing, a problem?
Well, I couldn't donwload my emails with courier, and
On Jan 14, 2004, at 10:26 AM, Andrea Riela wrote:
The :::192.168.17.13 for me is a strange thing too. But, If you
say
no, I agree with you.
Here's the patch to fix that, currently in CVS, that will be in the
next release (which will probably be out by the end of the week).
Courier might
Andrea Riela wrote:
Then, where is my problem? Pop3 and pop3-ssl don't completely
work. The auth is ok (thanks to Michael Bowe, for the patch),
but I couldn't download the emails.
Sorry Jeremy, sorry Peter,
I'm stupid. I need a beer :)
Here, all works fine with courier-pop3. Now I check the
Andrea Riela wrote:
18592 authvchkpw CALL fcntl(0x3,0x3,0)
18592 authvchkpw RET fcntl -1 errno 9 Bad file descriptor
Well, I've seen that MrSam has released another 2.2.2 version (20040112). In
the changelog there isn't our bug, but MrSam says that This build fixes all
reported bugs.
I
I should have a patch available soon
Well, Michael, now it partially works.
I send my test to you:
observe# openssl s_client -connect 127.0.0.1:995
CONNECTED(0004)
depth=0 /C=US/ST=NY/L=New York/O=Courier Mail
Server/OU=Automatically-generated POP3 SSL
key/CN=localhost/[EMAIL PROTECTED]
Original Message -
From: Andrea Riela [EMAIL PROTECTED]
Well, Michael, now it partially works.
I send my test to you:
observe# openssl s_client -connect 127.0.0.1:995
CONNECTED(0004)
depth=0 /C=US/ST=NY/L=New York/O=Courier Mail
Server/OU=Automatically-generated POP3 SSL
- Original Message -
From: Andrea Riela [EMAIL PROTECTED]
Subject: [vchkpw] vchkpw and courier 2.2.2 (probably a bug)
Hi folks,
I've tryed to connect courier-2.2.2 with authvchkpw to the
vpopmail-5.4.0-rc1, and probably I've finded a bug. MrSam has confirmed. I
hope my test could
13 matches
Mail list logo
