Make sure /etc/sasldb2 can be read by user cyrus. The easiest way (which btw
should have been done automatically) is to have a sasl group, let it read
/etc/sasldb2, and add user cyrus to that group. Then, restart cyrus.
Oh, don't log on using a IMAP client in an admin account. See the Cyrus FAQ
f
Henrique de Moraes Holschuh wrote:
It's a standalone box that doesn't have anyone else to talk to, I really
don't think that I need kerberos.
1. Install cyrus21-imapd, cyrus21-admin, sasl2-bin, cyrus21-pop3d,
cyrus21-clients
2. for i in all your users ; do saslpasswd2 -c $i ; done
3. vi /etc/
On Wed, 18 Dec 2002, Jean-Marc V. Liotier wrote:
> If it is so straightforward, it is indeed very nice. But what about if I
> want to interface a local Postfix to it ? I can't get Postfix to talk to
Attached.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all an
On Wed, Dec 18, 2002 at 06:15:12PM +0100, Jean-Marc V. Liotier wrote:
| On Wed, 2002-12-18 at 17:03, Henrique de Moraes Holschuh wrote:
[...]
| If it is so straightforward, it is indeed very nice. But what about if I
| want to interface a local Postfix to it ? I can't get Postfix to talk to
| Cyrus
On Wed, 2002-12-18 at 17:03, Henrique de Moraes Holschuh wrote:
> 1. Install cyrus21-imapd, cyrus21-admin, sasl2-bin, cyrus21-pop3d,
> cyrus21-clients
>
> 2. for i in all your users ; do saslpasswd2 -c $i ; done
>
> 3. vi /etc/imapd.conf, edit at least the admins line, and make
>sure whateve
Tom Allison said:
> Well, I tried to install the new one and got stuck on this SASL stuff.
>
> I've been at this for a solid two days after three days of RTFMing.
I've heard of nightmarish stories about cyrus 2.x too, not from
debian users, but from a few people trying it on redhat(compiling fro
Tom Allison <[EMAIL PROTECTED]> wrote:
>nate wrote:
>> Tom Allison said:
>>
>>>I'm looking for suggestions on which of the .deb available IMAP
>>>servers might do well for scalability and security.
>>>
>>>I am planning on tying this in wi
> It's a standalone box that doesn't have anyone else to talk to, I really
> don't think that I need kerberos.
1. Install cyrus21-imapd, cyrus21-admin, sasl2-bin, cyrus21-pop3d,
cyrus21-clients
2. for i in all your users ; do saslpasswd2 -c $i ; done
3. vi /etc/imapd.conf, edit at least the adm
On Wed, 18 Dec 2002, Tom Allison wrote:
> I don't need to do kerberos. I don't know about PAM. All I'm trying to do
> is create a imap server, maybe pop-ssl, but nothing else. I've been doing
> this with uw-imapd for a while yet and wanted to move to cyrus on the basis
> of some of the features
nate wrote:
Tom Allison said:
I'm looking for suggestions on which of the .deb available IMAP
servers might do well for scalability and security.
I am planning on tying this in with a webmail interface, probably
squirrelmail.
I use cyrus, its quite scalable, very fast. Courier is good too I
On Tue, 17 Dec 2002, Tom Allison wrote:
> Does Cyrus 1.? support sieve? What's the "diff" between these two?
No. And the number of differences is to big to list...
> I'm finding that there are a *lot* of packages to bring in from
> unstable in order for cyrus21 to install. Considering that th
Henrique de Moraes Holschuh wrote:
On Thu, 12 Dec 2002, Tom Allison wrote:
I currently have procmail delivering a majority of my email into
filtered mailboxes (eg: ~/debian) with only the non-filtered email
being delivered to the /var/spool/mail/tallison.
Cyrus 2.1 can do this through sieve.
On Thu, Dec 12, 2002 at 04:43:22PM -0800, nate wrote:
> Colin Watson said:
> > You could just use something like the Delivered-To: header that postfix
> > adds?
>
> I was about to jump with joy thinking I could do that but checked
> the message you sent and there is no such header.
>
> I put a co
On Thu, 12 Dec 2002, Paul Tansom wrote:
> Exim base mail app. - I wavered on Qmail, but really didn't like it
> much, partly due to the license obstructing binary distribution and
> partly due to the configuration - the way it uses multiple hidden files
> for managing aliases is a pain and just pla
Henrique de Moraes Holschuh said:
> Cyrus adds those as well :-)
perhaps a newer version.. I checked about a dozen messages, and
did not find a single delivered-to header, or any header that
started with the word delivered.
nate
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
On Thu, 12 Dec 2002, Colin Watson wrote:
> On Thu, Dec 12, 2002 at 11:49:44AM -0800, nate wrote:
> > I do it this way for spam purposes. 99% of spam I recieve is not addressed
> > to any user on my system so I can only assume it was BCC'd or sent as part
> > of a mailing list. The only way to track
Colin Watson said:
> You could just use something like the Delivered-To: header that postfix
> adds?
I was about to jump with joy thinking I could do that but checked
the message you sent and there is no such header.
I put a copy of the headers for the message you sent here:
http://portal.aphrol
On Thu, Dec 12, 2002 at 11:49:44AM -0800, nate wrote:
> I do it this way for spam purposes. 99% of spam I recieve is not addressed
> to any user on my system so I can only assume it was BCC'd or sent as part
> of a mailing list. The only way to track down what address it was sent to
> is to have a
Tom Allison said:
> nate wrote:
>
>> no username, no password anywhere ..its quite handy.
>>
>
> what is to prevent anyone else from using it?
ACLs(access control lists), cyrus may be the only one of the major
MTAs to impliment them, I'm not sure. You can read up on them here:
http://asg.web.cmu.
Tom Allison said:
> I would think you would want authentication.
there is authentication, just not for those accounts. cyrus maintains
access control lists. You could(if you wanted) run a IMAP server that
provides anonymous access. But in this example, I must be logged in
under my main account in
> cool. I'm using postfix. But I've never heard of LMTP...
>
> Any starting points for RTFM-ing?
> I found something on the postfix.org site...
> In the postfix "big picture", where does this fit/replace?
LMTP is Local Mail Transfer Protocol. You can read all you want about it
in RFC 2033. The
On Wed, Dec 11, 2002 at 10:39:42PM -0500, Tom Allison typed the following...
> I'm looking for suggestions on which of the .deb available IMAP
> servers might do well for scalability and security.
>
> I am planning on tying this in with a webmail interface, probably
> squirrelmail.
...and that's
Chris Hilts wrote:
must configure your MTA to deliver to procmail instead of cyrus, and use
cyrdeliver to send the email from procmail to cyrus. Which is much slower
than simply delivering it to cyrus and using sieve in the first place.
As a side note, if your MTA can speak LMTP, that's probab
Chris Hilts wrote:
must configure your MTA to deliver to procmail instead of cyrus, and use
cyrdeliver to send the email from procmail to cyrus. Which is much slower
than simply delivering it to cyrus and using sieve in the first place.
As a side note, if your MTA can speak LMTP, that's probab
Henrique de Moraes Holschuh said:
> Unless you're talking about the VERY old cyrus 1.5, I object very heavily
> to your comment, I had uploads and backports for Cyrus 2.1 done some hours
> after the bug was announced on bugtraq...
>
yes, but until its fixed in stable, and announced on security.de
Tom Allison said:
> Under cyrus, I am assuming that the ~/mail/... structure is going to be
> the default as it is with squirrelmail today. It would be
> find with me, I can move things around easily enough in the
> procmail files.
nope, cyrus stores it's mail in a protected area of the system,
Tom Allison said:
> I don't understand what you mean by "no username/password". Do
> you mean no entry in /etc/passwd? Does cyrus manage it's own list of
> username/password?
nope, no username or password anywhere associated with the inbox. I have
about 65 mail accounts, only 1 has a username
> must configure your MTA to deliver to procmail instead of cyrus, and use
> cyrdeliver to send the email from procmail to cyrus. Which is much slower
> than simply delivering it to cyrus and using sieve in the first place.
As a side note, if your MTA can speak LMTP, that's probably the best way
On Thu, 12 Dec 2002, Tom Allison wrote:
> I currently have procmail delivering a majority of my email into
> filtered mailboxes (eg: ~/debian) with only the non-filtered email
> being delivered to the /var/spool/mail/tallison.
Cyrus 2.1 can do this through sieve. There are plugins for squirrelma
On Wed, 11 Dec 2002, nate wrote:
> Tom Allison said:
> > I'm looking for suggestions on which of the .deb available IMAP
> > servers might do well for scalability and security.
> >
> > I am planning on tying this in with a webmail interface, probably
> > squirrelmail.
>
> I use cyrus, its quite sc
On Thu, Dec 12, 2002 at 09:47:12AM -0500, Tom Allison wrote:
| cyrus sounds interesting an probably worthwhile.
| I have one question though that is really bothering me and I'm
| more than hesitant about making the switch.
|
| I currently have procmail delivering a majority of my email into
| f
On Wed, 11 Dec 2002, Tom Allison wrote:
> I'm looking for suggestions on which of the .deb available IMAP
> servers might do well for scalability and security.
You should use either Cyrus IMAPd 2.1 (http://people.debian.org/~hmh/ for
official Woody backport), or Courrier-IMAP.
> I am planning on
nate wrote:
Tom Allison said:
I'm looking for suggestions on which of the .deb available IMAP
servers might do well for scalability and security.
I am planning on tying this in with a webmail interface, probably
squirrelmail.
I use cyrus, its quite scalable, very fast. Courier is good too I
Tom Allison said:
> I'm looking for suggestions on which of the .deb available IMAP
> servers might do well for scalability and security.
>
> I am planning on tying this in with a webmail interface, probably
> squirrelmail.
I use cyrus, its quite scalable, very fast. Courier is good too I
hear(no
34 matches
Mail list logo
