Hello,
By accident a user reported a problem of redirected mails being lost.
After some troubleshooting I nailed down the problem to:
Nov 22 17:29:40 manaslu postfix/postdrop[23167]: warning: uid=980: File
too large
Nov 22 17:29:40 manaslu postfix/sendmail[23166]: fatal: ([EMAIL
afaik the digest-md5 occurs between cyrus and the imap client
(AUTHENTICATE command) so my doubt is about the user db and password
store. Is the password stored in plain text? (mysql auth like
http://www.delouw.ch/linux/Postfix-Cyrus-Web-cyradm-HOWTO/html/cyrus-config.html
)
kind regards
--
On Wed, Dec 05, 2007 at 08:48:00AM +, David Carter wrote:
On Tue, 4 Dec 2007, Wesley Craig wrote:
Changes to the Cyrus IMAP Server since 2.3.9
[...]
* Fixed the special case of RENAMEing an Inbox, so that it doesn't
keep the same mailbox uniqueid, thus allowing it to
Kuhlemann, Stefan wrote:
Hi mailinglist...
(again a newbie question ahead ;-) )
At the moment I am experimenting with cyrus, running on fedora 7.
Problem:
cyradm stopped working.
cyradm --user cyrus --auth plain --server localhost
cyradm: cannot connect to server
--server isn't
On Wed, 5 Dec 2007, Gabor Gombas wrote:
Hmm, can a regular user rename his own INBOX? I'm pretty sure no admin
actions were performed.
RFC 3501, section 6.3.5:
Renaming INBOX is permitted, and has special behavior. It moves
all messages in INBOX to a new mailbox with the given name,
On Dec 5, 2007 9:52 AM, Guillermo Gómez [EMAIL PROTECTED] wrote:
afaik the digest-md5 occurs between cyrus and the imap client
(AUTHENTICATE command) so my doubt is about the user db and password
store. Is the password stored in plain text? (mysql auth like
On Dec 5, 2007 9:52 AM, Guillermo Gómez [EMAIL PROTECTED] wrote:
afaik the digest-md5 occurs between cyrus and the imap client
(AUTHENTICATE command) so my doubt is about the user db and password
store. Is the password stored in plain text? (mysql auth like
Kuhlemann, Stefan wrote:
-Ursprüngliche Nachricht-
Von: Rudy Gevaert [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 5. Dezember 2007 12:48
An: Kuhlemann, Stefan
[...]
Problem:
cyradm stopped working.
cyradm --user cyrus --auth plain --server localhost
cyradm: cannot connect
I have installed cyrus-imap-2.2, cyrus_murder-2.2, cyrus-admin-2.2,
cyrus-pop3d-2.2, sasl2-bin, libhtml-parser-, cyrus-clients-2.2,
libsasl2-modules on a debian etch 32bit.
Mupdate works fine and the backend servers too. On the front end I can login
(which is as I understand is done locally)
On Wed, 5 Dec 2007, Frank Purmann wrote:
I have installed cyrus-imap-2.2, cyrus_murder-2.2, cyrus-admin-2.2,
cyrus-pop3d-2.2, sasl2-bin, libhtml-parser-, cyrus-clients-2.2,
libsasl2-modules on a debian etch 32bit.
Mupdate works fine and the backend servers too. On the front end I can login
Guillermo Gómez wrote:
Ive been looking on how to work cyrus imap with mysql and found two options:
cyrus pam with pam_mysql
cyrus sasl sql plugin
In the first one it look like the store can have the password encrypted MD5
The second one needs the passwords in the clear in the db
This is a brand new install. After running tools/mkimap and
starting master, I get this. What's the deal?
Dec 5 17:26:57 alberta.foo.com ctl_cyrusdb[3713]: DBERROR: error
listing log files: DB_NOTFOUND: No matching key/data pair found
Dec 5 17:26:57 alberta.foo.com ctl_cyrusdb[3713]: DBERROR:
pam_mysql would correlate to saslauthd, and the cyrus sasl plugin
would correlate to auxprop.
See documentation on the SASL pwcheck_method setting
(sasl_pwcheck_method in /etc/imapd.conf).
When set to saslauthd, the pwcheck_method will allow the use of
the PLAIN and LOGIN mechanisms, and
Guillermo Gómez wrote:
Thanks Dan, im reading and trying to digest all the material available.
What the customer wants is:
1.- md5-digest between imap client/server (squirrelmail/cyrus-imapd)
2.- md5 encrypted passwords stored in mysql db (cyrus-imap-??)
Is this combination possible?
Hi mailinglist...
(again a newbie question ahead ;-) )
At the moment I am experimenting with cyrus, running on fedora 7.
Problem:
cyradm stopped working.
cyradm --user cyrus --auth plain --server localhost
cyradm: cannot connect to server
The system worked fine now for a week or so. Since
On Tue, Dec 04, 2007 at 10:06:23PM -0500, Wesley Craig wrote:
The internal Cyrus mailbox ID ought to be unique, but it's not. On the
sub folder, remove the cyrus.header file and reconstruct. This will assign
a new, unique mailbox ID.
Thanks, that did the trick.
Any ideal how they ended
Rudy Gevaert wrote:
Hello,
By accident a user reported a problem of redirected mails being lost.
After some troubleshooting I nailed down the problem to:
Nov 22 17:29:40 manaslu postfix/postdrop[23167]: warning: uid=980: File
too large
Nov 22 17:29:40 manaslu postfix/sendmail[23166]:
-Ursprüngliche Nachricht-
Von: Rudy Gevaert [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 5. Dezember 2007 12:48
An: Kuhlemann, Stefan
[...]
Problem:
cyradm stopped working.
cyradm --user cyrus --auth plain --server localhost
cyradm: cannot connect to server
On Wed, Dec 05, 2007 at 11:34:10AM +, David Carter wrote:
RFC 3501, section 6.3.5:
Renaming INBOX is permitted, and has special behavior. It moves
all messages in INBOX to a new mailbox with the given name,
leaving INBOX empty. If the server implementation supports
On Tue, 4 Dec 2007, Wesley Craig wrote:
The internal Cyrus mailbox ID ought to be unique, but it's not. On
the sub folder, remove the cyrus.header file and reconstruct. This will
assign a new, unique mailbox ID. Any ideal how they ended up with the
same IDs?
Given that a user inbox is
20 matches
Mail list logo
