Hello,
i've just set up v2.1.12 on a RedHat 8.0 system using sasl2.
I've created a single user (urban) using cyradm, and now I'm using
Mozilla 1.0.1 ("the client") as MUA to test. The client is connecting
to the IMAP server using TLS sucessfully. When the client tries to
create the "Drafts" or
Hello imappers,
apparently the standard installation of cyrus imap entails changing
themail config such that local delivery is performed exclusively to
IMAP mailboxes.
I'm trying to configure a system on which some users should have mail
delivered to IMAP mailboxes, others however to their regula
Kevin Williams wrote:
> My imapd.conf file looks as follows:
>
> configdirectory: /var/imap
> partition-default: /var/spool/imap
> admins: cyrus root
> sasl_pwcheck_method: saslauthd
>
> I can successfully authenticate using the imtest command. When I
> tried to use cyradm, I originally got a "c
You wrote:
> any idea what I need to do? also does anyone have something I can toss =
> into a perl script to auto create mailboxes for users that have 15mb =
> quotas?
see:
http://www.unix-wissen.de/add-cyrus-user
for a (very) simple example of a script for adding cyrus users.
cheers,
is it naive of me to think that it might be possible to train users
of this list not to send HTML-formatted mails to the list?
that perhaps with constant reminders and pointers to the appropriate
documentation on netiquette things might improve?
any chance of configuring the list server to rejec
Does anyone know what the units are (i.e., Bytes, KBytes, etc) for
the setquota method? (Cyrus::IMAP::Admin)
Couldn't hurt to put this in the manpage!
cheers,
Rob Urban
joe ritter wrote:
> scripts still refer to the TCL based cyradm. I was
> wondering if anyone could share any batch creating and
> batch setup scripts with me and or any other tips on
> this procedure. Thanks in advance.
I just finished an example script for adding users. You may find
it helpful:
Scott Adkins wrote:
> 1) The configure process appears to pick up on the fact that Tru64 does
> have getnameinfo(), but not getaddrinfo(). The problem is that if one
> is found and the other is not, the definitions for both are included
> in lib/gai.h. Well, getnameinfo() on Tru64 h
Scott Adkins wrote:
> Yes, this is a concern for me... I am not exactly sure how this will be
> stored in Tru64. We are talking about a "char *" and an "int" stored in
> the same location. I have always known them to consume 4 bytes of memory,
> but my manager isn't so sure, thinking that maybe
