On Sat, 30 Nov 2002, Nuno Silva wrote:
> I'm not 100% sure, but I suppose that one can virtualize the
> connections. What I mean is: imapd (or pop3d or lmtpd...) wants to write
> something -> ask the daemon and the daemon will choose a free connection
> and commit those changes. This is the "one o
Hello!
Nicola Ranaldo wrote:
I cannot spread sql commands of a unique transaction over multiple pgsql
connection, and a connection cannot handle parallel transactions.
So if i have 1000 imapd process starting a transaction the mailbox daemon
has to open 1000 pgsql connection.
Reading from the D
On 29 Nov 2002, Su Li writes:
> Does any one knows, what port does Cyradm telnet to Cyrus IMAP? Like
> Sieve, the port is 2000.
> So I can telnet to the administration port and issue a command:
> "setacl username1 user.username1"
There is no separate administration port for Cyrus.
Instead, cyr
On Fri, 29 Nov 2002, Su Li wrote:
> Does any one knows, what port does Cyradm telnet to Cyrus IMAP? Like
> Sieve, the port is 2000.
>
> So I can telnet to the administration port and issue a command:
> "setacl username1 user.username1"
cyradm is pretty much just an imap client. Hence, it connec
Hi,
Does any one knows, what port does Cyradm telnet to Cyrus IMAP? Like Sieve, the port
is 2000.
So I can telnet to the administration port and issue a command: "setacl username1
user.username1"
Thanks,
Su Li
On Thu, 21 Nov 2002, Ralf Haferkamp wrote:
> cyrus-imapd fails to correctly seperate the different parts of mail under
> certain circumstances. This e.g. the case if one MIME part of the mail
> contains a multipart/alternative part, that has a boundary which contains
> the boundary of the enclousi
On Fri, 29 Nov 2002, Nicola Ranaldo wrote:
> Howewer i think a pgsql connection for every master child could not be a
> problem, on my production server (7500 very active users, cyrus.log is
> 20MB/day) the average number of imapd is 15, pop3d is 30, lmtpd is 5 (under
> mail-bombing lmtpd process
> Short answer: Avoid using procmail with cyrus, unless you want to have to
> screw with setuid problems with procmail and deliver and ACL wackiness on
> users' mailboxes. IMO, the hassle you go through as an admin to force the
Since I trust my users (otherwise, I wouldn't give them procmail acce
I cannot spread sql commands of a unique transaction over multiple pgsql
connection, and a connection cannot handle parallel transactions.
So if i have 1000 imapd process starting a transaction the mailbox daemon
has to open 1000 pgsql connection.
One solution could be:
BEGIN -> Allocate a new buff
