Well, here's what I've found so far, regarding differences.
This current config, which is the RPM install of cyrus-imap, also includes an
RPM install of squirrelmail.
My other RPM install of cyrus-imap, uses squirrelmail, but squirrelmail was
downloaded, installed, and configured by me. Perhap
Jonathan Villa wrote:
Actually, I'm not sure if the Centos4 RPMS come with the autocreate
patch. I assume they don't. I'm actually thinking of building this
from source as I've done with most of my other installs anyway.
I'll use the examples you've provided as well.
What's been tough for me
Actually, I'm not sure if the Centos4 RPMS come with the autocreate patch. I
assume they don't. I'm actually thinking of building this from source as I've
done with most of my other installs anyway.
I'll use the examples you've provided as well.
What's been tough for me is that on another Cen
Thanks Michael, all three points fully explain it.
I'm off to do that now.
- Original Message -
From: Michael Menge <[EMAIL PROTECTED]>
Sent: Wed, 3/21/2007 9:09am
To: info-cyrus@lists.andrew.cmu.edu
Subject: RE: Autocreateinboxfolders not being autocreated
Hi,
1. autocreate is NOT p
having recently made this mistake, are you sure centos4 comes with the
autocreate patches in their rpm? If not you'll need to recompile.
another thing to check, i believe autocreate* requires that
autocreatequota as well. Here is the relevant part of my config you may
want ot use ase a basis sin
Jonathan Villa wrote:
Yes, you may be missing something. Those options only affect new mailboxes
while they are created. If you say only the Trash folder is being created,
I guess the mailbox already exists and your client does create the Trash
folder. No autocreate* involved here.
the comm
Hi,
1. autocreate is NOT part of the normal cyrus distribution.
You have to patch cyrus to have the autocreate feature.
2. the autocreate funktion only creates folders,
if there is no INBOX for that user and he trys to
login or recieves a mail.
3. the user must exist (in pam, ldap, pas
> Yes, you may be missing something. Those options only affect new mailboxes
> while they are created. If you say only the Trash folder is being created,
> I guess the mailbox already exists and your client does create the Trash
> folder. No autocreate* involved here.
> Simon
I've tried this/test
hi,
i'am using cyrus-imapd version 2.2.12 on suse linux 9.3. in my setup
procmail calls deliver which works pretty well.
my man page of deliver says
deliver [ -C config-file ] [ -d ] [ -r address ]
[ -f address ] [ -m mailbox ] [ -a auth-id ]
[ -q ] [ userid ]
Does cyrus work with Cleversafe?
Thanks in advanced
--
Juan Pablo Baudoin
Gerente Nacional de sistemas
Kieffer & Asociados
Tel: (591) 2 243 3434
Cel: (591) 720 01485
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http:
as mentioned earlier, look into creating apparmor profiles _or_ remove
apparmor from yast.
(apparmor profiles are generated using the genprof command. might be an
idea to do a little research into it on the web before going near it.
there isn't much to it)
Steve
JOYDEEP wrote:
Steve Howe w
Steve Howe wrote:
> This is usually a problem with Apparmor. been through this myself
> painfully.
>
> I'm presuming you're using Suse that automatically comes with Apparmor
> installed?
>
> try:
>
> rcapparmor stop
GREAT ! It is really SuSE. THANKS A LOT.
now there is no more the reject problem.
This is usually a problem with Apparmor. been through this myself painfully.
I'm presuming you're using Suse that automatically comes with Apparmor
installed?
try:
rcapparmor stop
as root for an immediate fix, then look into creating apparmor profiles..
Steve
JOYDEEP wrote:
Dear list,
wh
Michael Menge wrote:
> If you use pam, you have to set the binddn and bindpw in /etc/ldap.conf
OK. should I copy these from slapd.conf ?
>
> Quoting JOYDEEP <[EMAIL PROTECTED]>:
>
>> Roland Felnhofer wrote:
>>> Hi,
>>>
>>> hmm, let me guess - you are running saslauthd with -a PAM?!
>>>
>>> try run
JOYDEEP wrote:
JOYDEEP wrote:
Rudy Gevaert wrote:
JOYDEEP wrote:
Dear list,
I can login the cyrus IMAP both as username as well as
[EMAIL PROTECTED]
How can I force cyrus to allow login as [EMAIL PROTECTED]only ?
I believe it is
virtdomains: userid
in imapd.conf
If you use pam, you have to set the binddn and bindpw in /etc/ldap.conf
Quoting JOYDEEP <[EMAIL PROTECTED]>:
Roland Felnhofer wrote:
Hi,
hmm, let me guess - you are running saslauthd with -a PAM?!
try running it /usr/sbin/saslauthd -a ldap
no need (with a more or less up-to-date version
16 matches
Mail list logo
