I all.
I got some kind of solution to the problem posted some month ago.
The trick is that in the configuration file of courier auth daemon there
was authpam and autvchkpw, by leaving only authvchkpw the problem
doesn't appears anymore.
don't ask me why.. I think that this could be a bug of
The QmailToaster has a lot to thank Miguel Beccari for. :)
Erik
On 4/14/07, Simone Marzona [EMAIL PROTECTED] wrote:
I all.
I got some kind of solution to the problem posted some month ago.
The trick is that in the configuration file of courier auth daemon there
was authpam and autvchkpw, by
Hello Simone,
Do you have an email address for Miguel? If you do, could you please send
it to me at [EMAIL PROTECTED]
Thank you . . .
Regards,
Nick
The QmailToaster has a lot to thank Miguel Beccari for. :)
Erik
On 4/14/07, Simone Marzona [EMAIL PROTECTED] wrote:
I all.
I got some
Have you tweaked /var/qmail/supervise/imap*/run to allow more incoming
connections?
The default is 40, even if you edit the imap configs, as the imap
stuff doesn't run as a service it runs from tcpservers.
Erik
On 3/12/07, Simone Marzona [EMAIL PROTECTED] wrote:
Hi all
I got a strange
I set up 120 connection both in tcpserver imapd run file and
in /etc/courier
On Mon, 2007-03-12 at 11:38 -0700, Erik A. Espinoza wrote:
Have you tweaked /var/qmail/supervise/imap*/run to allow more incoming
connections?
The default is 40, even if you edit the imap configs, as the imap
