A couple people have suggested to me that I use Cyrus-IMAP as
opposed to Courier-IMAP, and have given some good arguments
for that decision direction. However, I have still have one
show stopper for that switch: some external programs that work
directly with the storage space of all the mail. Due
Hello,
One of the disadvantage of using Cyrus might be that there is
no API to the mail store other than the IMAP protocol. You simply
cannot go mucking around the mail store with "external programs"
without the potential to cause problems.
That said, mail is stored in directories that map unto f
Hi,
still having troubles with cyrus!
MAJOR PROBLEM : I cannot set up mailboxes.
Getting access to cyrus gives me:
#> cyradm --user cyrus --auth login localhost
IMAP Password:
Login failed: generic failure at
/usr/lib/perl/5.6.1/Cyrus/IMAP/Admin.pm line 114
cyradm: cannot authentic
>A couple people have suggested to me that I use Cyrus-IMAP as
>opposed to Courier-IMAP, and have given some good arguments
>for that decision direction. However, I have still have one
>show stopper for that switch: some external programs that work
>directly with the storage space of all the mail.
On Fri, 31 Jan 2003, Earl R Shannon wrote:
> Cyrus documentation calls the IMAP server a black box. This is defined
> to mean that the users do not have access to the account/data accept
> through the well defined ( :-/ ) IMAP protocol. This black box concept
> also extends to a certain extent to
On Fri, 31 Jan 2003, Adam Tauno Williams wrote:
> SASL documentation?! There is some floating about. I love SASL, but
> the shreds of documentation are universally terrible.
If you have specific suggestions as to what needs to be added, please let
us know. If you actually have text, that'd be
Adam Tauno Williams said:
> SASL documentation?! There is some floating about. I love SASL, but
> the shreds of documentation are universally terrible.
AFAIK, this is also true for much of the software that CMU produces,
however the quality of the software has been so good that no one seems to
Hello,
You are correct on all counts. I was simply trying to make a point,
and IMAP is the major protocol used to access the mail store, at
least it is here. Nor did I mean to imply that any server that one
set's up to see how things worked should be a production machine.
In fact, because one woul
Christian Schulte wrote:
>
> Ken Murchison wrote:
>
> >I just committed support for per-domain quotas which works for all
> >domains except for the default domain (the code to make it work for the
> >default domain would be particularly crufty). To set a domain quota, do
> >something like the
On Fri, 31 Jan 2003, Earl R Shannon wrote:
> But that does now beg the question. There must be some form of
> coordination between the various processes as they access the
> mail store. Can this not be abstracted out and put in an API to
> make it easier for people to write their own applications?
Hi,
still having troubles with cyrus!
MAJOR PROBLEM : I cannot set up mailboxes.
Getting access to cyrus gives me:
#> cyradm --user cyrus --auth login localhost
IMAP Password:
Login failed: generic failure at
/usr/lib/perl/5.6.1/Cyrus/IMAP/Admin.pm line 114
cyradm: cannot authent
Earl R Shannon wrote:
But that does now beg the question. There must be some form of
coordination between the various processes as they access the
mail store. Can this not be abstracted out and put in an API to
make it easier for people to write their own applications? I would
venture a guess to
Hello,
I have been looking for information that might be able to help me in
a task that I am tasked to undertake, and can't find much useful
information on. Any help would be appreciated.
I am trying to convert a server running qmail to run exim -> cyrus. I am
quite familiar with the exim->
On Fri, 31 Jan 2003, John Alton Tamplin wrote:
> The point is if you expose the internal API for accessing the mailstore
> you are stuck with it and can't make changes. I can't imagine there is
> a big need for this or other people wanting to write code to implement
> that API, so if you really w
Hi.. you don't say which Exim you're using. I'd recommend at least Exim
4.12, which can use the "lmtp" transport to the unix domain socket Cyrus
lmtpd is listening on.
appendfile does exactly that and misses Cyrus completely.
Is your imapd a cyrus imapd? telnet to port 143 and see what it says.
For some of our users webmail has replaced client-based (Netscape) email
as their program of choice. We set up webmail so that our users could
access their email off campus, but more and more users prefer it for on
campus email.
Now we have suddenly had a problem with webmail -- not sending ema
I'm working on getting a Murder setup and I can authenticate and pull mail
directly from the backend server.
However, when I try to proxy the connection I get this in /var/log/messages
on the proxy/master:
Jan 31 13:40:35 zeus pop3[5437]: login: SERVER[192.168.247.241] hbeatty
plaintext
Jan 31 13
On Tue, 28 Jan 2003, John A. Tamplin wrote:
> Rob Siemborski wrote:
>
> >This really shouldn't be necessary. admins can authorize as any user
> >(e.g. login as user cyrus with the password for them, but get rights as
> >rjs3). Most SASL mechanisms allow this, though the regular imap LOGIN
> >co
What SASL mechanism are you using between your frontend and backends?
Or rather, what mechanisms are your backends advertising?
-Rob
On Fri, 31 Jan 2003, Hank Beatty wrote:
> I'm working on getting a Murder setup and I can authenticate and pull mail
> directly from the backend server.
>
> Howev
On Thu, Jan 30, 2003 at 03:49:57PM +0100, Peter Burggraef wrote:
> I don't know, what exim and cyrus are donig.
It's all explained in cyrus/doc/install-configure.html
As Matt says you need to tell it use the lmtp protocol. From memory this
transport is not included in exim by default, and you nee
On Fri, Jan 31, 2003 at 08:57:50AM -0500, Adam Tauno Williams wrote:
| It does not use maildir. It actually can use several storage backends, flat
| file to sleepcat and some others. Rumor of an SQL backend, that might be what
| your looking for.
SQL would be harder to do for what I'm doing.
My conf file looks like this:
##
# Global info's
##
configdirectory: /var/imap
partition-default: /var/spool/imap
unixhierarchysep: yes
altnamespace: yes
imapidresponse: no
##
#
I'm having a little trouble with the cyradm tool, firstly I'd like to point
out that I'm only running Cyrus in a lab & am not that familiar at this
point.
I'm authenticating using saslauthd -a pam, everything is working fine from
an imap perspective, only imaps, using local acccounts, it's runn
Ken Murchison wrote:
I'l have to talk to Rob and Larry again, but I think that if we're
interested in creating the directories on the fly, we'd want to do them
as needed (create just what we need now, not the entire tree) and do
this regardless of whether we're using virtdomains.
mkimap should
You aren't offering any SASL mechanisms. I believe the 2.2 code even
supports STARTTLS (and therefore PLAIN).
You need to support a SASL mechanism that allows proxy authentication.
The regular IMAP login command isn't good enough.
-Rob
On Fri, 31 Jan 2003, Hank Beatty wrote:
> And when I use i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'd like to announce the release of Cyrus SASL 2.1.11 on
ftp.andrew.cmu.edu. This version is primarily a bug-fix release.
Specifically, it addresses a number of issues in the build system, a
memory leak in the doors IPC method for saslauthd, and fixe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Apologies, the URL for the distribution was not included in the previous
announcement.
The URL for the Cyrus SASL 2.1.11 release is:
ftp://ftp.andrew.cmu.edu/pub/cyrus/cyrus-sasl-2.1.11.tar.gz
or
http://ftp.andrew.cmu.edu/pub/cyrus/cyrus-sasl-2.1.11.
PLAIN is your only choice (so you'll need to be sure you can get a TLS
layer between the frontend and backend). Like I said, I believe 2.2 has
this code. I know 2.1 does not.
-Rob
On Fri, 31 Jan 2003, Hank Beatty wrote:
> OK. That makes sense. Are there any SASL mechs that can use PAM?
>
> ---
OK. That makes sense. Are there any SASL mechs that can use PAM?
- Original Message -
From: "Rob Siemborski" <[EMAIL PROTECTED]>
To: "Hank Beatty" <[EMAIL PROTECTED]>
Cc: "Cyrus-Info" <[EMAIL PROTECTED]>
Sent: Friday, January 31, 2003 3:18 PM
Subject: Re: Murder and Backend Authentication
Christian Schulte wrote:
>
> Ken Murchison wrote:
>
> >I'l have to talk to Rob and Larry again, but I think that if we're
> >interested in creating the directories on the fly, we'd want to do them
> >as needed (create just what we need now, not the entire tree) and do
> >this regardless of whet
On Fri, 31 Jan 2003, Ken Murchison wrote:
> Like Rob said, just PLAIN, which will require you to use STARTTLS, which
> is only in 2.2. That being said, since you will likely only have one or
> two proxy admins, you could just put them in sasldb2 and use DIGEST-MD5.
This may break some clients, s
Hank Beatty wrote:
>
> OK. That makes sense. Are there any SASL mechs that can use PAM?
Like Rob said, just PLAIN, which will require you to use STARTTLS, which
is only in 2.2. That being said, since you will likely only have one or
two proxy admins, you could just put them in sasldb2 and use
Hi,
we are currently testing our installation of cyrus-imapd 2.1.11 using a
self-written Perl script that's imitating real use. We intend to contribute
the script when we've cleaned it up a little. Anyway, during our tests we
noticed something strange. In /etc/cyrus.conf we have the line:
ima
Sorry if this is just obvious but... Everyone keep stating that
STARTTLS is not supported in 2.1.x I'm assuming that it just doesn't
work for the Backend Authentication in a Murder since I'm using it to
connect to my standalone server just fine. Or do I have something very
worng going on here?
On Fri, 31 Jan 2003, Eric S. Pulley wrote:
> Sorry if this is just obvious but... Everyone keep stating that
> STARTTLS is not supported in 2.1.x I'm assuming that it just doesn't
> work for the Backend Authentication in a Murder since I'm using it to
> connect to my standalone server just fine.
I'm having a bit of a problem on our IMAP server. There are several
instances of ctl_deliver, some running for over 2 days.
# ps -ef|grep deliver
cyrus 331 303 27 Jan 29 ? 2671:33 ctl_deliver -E 3
cyrus 6736 303 26 12:48:32 ? 112:04 ctl_deliver -E 3
cyrus 2647 303
On Fri, Jan 31, 2003 at 09:57:40AM -0500, John Alton Tamplin wrote:
| Earl R Shannon wrote:
|
| > But that does now beg the question. There must be some form of
| > coordination between the various processes as they access the
| > mail store. Can this not be abstracted out and put in an API to
|
On Fri, 31 Jan 2003 14:14:53 +0100
Dennis Leist <[EMAIL PROTECTED]> wrote:
> #> cyradm --user cyrus --auth login localhost
> IMAP Password:
> Login failed: generic failure at
> /usr/lib/perl/5.6.1/Cyrus/IMAP/Admin.pm line 114
> cyradm: cannot authenticate to server with login as cyr
Phil Howard wrote:
One of the needs I have is to build a two-way mail store replica. Either
node may be delivered to, and either node may be accessed by the user but
only one at a time. The two nodes are topologically and geographically
far apart, and bandwidth between them is to be considered
On Fri, Jan 31, 2003 at 08:33:41PM -0500, John A. Tamplin wrote:
| Phil Howard wrote:
|
| >One of the needs I have is to build a two-way mail store replica. Either
| >node may be delivered to, and either node may be accessed by the user but
| >only one at a time. The two nodes are topologically
40 matches
Mail list logo
