More information :
squatter is not able to index mailboxes on virtual domain !!
they interpret the "." of the domain name as a separator and substitute it !!
example :
su cyrus
squatter -r -v user/[EMAIL PROTECTED]
error opening [EMAIL PROTECTED]: Mailbox does not exist
May be a bug in 2.2 c
I use cyrus-imapd-2.2 from cvs on my system, all goes fine, but when I tried to
use squatter on a user I receive the following error :
SQUAT: Unknown error 1 (Closing index)
I used this command :
su cyrus
/usr/cyrus/bin/squater -r user/
Any idea ?
Thanks
vittorio
---
pnelson wrote:
On Fri, 2003-06-06 at 10:29, Ken Murchison wrote:
Patrick Nelson wrote:
Running Cyrus-imap 2.1.13 on RH9 and alls well. Moved the whole company
off of exchange a week ago and so far not even a hickup.
So, now I want to explore sieve, but I'm not sure where to begin. Is
there an
On Fri, 2003-06-06 at 10:29, Ken Murchison wrote:
> Patrick Nelson wrote:
> > Running Cyrus-imap 2.1.13 on RH9 and alls well. Moved the whole company
> > off of exchange a week ago and so far not even a hickup.
> >
> > So, now I want to explore sieve, but I'm not sure where to begin. Is
> > ther
QUESTION:
Does the Berkeley 4.1.25 database not like the version of POSIX threads in
Linux Mandrake 9.1, but is happy with the NGPT in Redhat 9.0? I ask because
when I built Cyrus-IMAP 2.1.12 against the db4.1 libs on Mandrake 9.1, I ran
into the problem described below:
///
On Fri, 2003-06-13 at 16:03, Ken Murchison wrote:
> pnelson wrote:
> > On Fri, 2003-06-13 at 15:38, Wil Cooley wrote:
> >
> >>On Fri, 2003-06-13 at 14:55, pnelson wrote:
> >>
> >>
> >>>require "fileinto";
> >>>if header :contains "Subject" "test" {
> >>> fileinto "INBOX.test;
> >>
> >>
pnelson wrote:
On Fri, 2003-06-13 at 15:38, Wil Cooley wrote:
On Fri, 2003-06-13 at 14:55, pnelson wrote:
require "fileinto";
if header :contains "Subject" "test" {
fileinto "INBOX.test;
^ You probably want a '"' here.
Oops email typo... the script has
On Fri, 2003-06-13 at 15:38, Wil Cooley wrote:
> On Fri, 2003-06-13 at 14:55, pnelson wrote:
>
> > require "fileinto";
> > if header :contains "Subject" "test" {
> > fileinto "INBOX.test;
>^ You probably want a '"' here.
>
Oops email typo... the script ha
On Fri, 2003-06-13 at 14:55, pnelson wrote:
> require "fileinto";
> if header :contains "Subject" "test" {
> fileinto "INBOX.test;
^ You probably want a '"' here.
Wil
--
Wil Cooley [EMAIL PROTECTED]
Naked Ape Consulting
On Fri, 2003-06-13 at 15:11, Carl P. Corliss wrote:
> What version of Cyrus are you using?
>
> On Friday 13 June 2003 03:55 pm, pnelson wrote:
> > Have Cyrus-imap working great and can...
> >
> > sieveshell -u pnelson -a pnelson localhost
> >
> > then:
> > >put test.siqeve
> > >activate test.sieve
Original Message
We've been happily running a cyrus mail server for several
years. Lately we've been attempting to migrate our Groupwise
users from the dark side over to our IMAP server. This seemed
straightforward enough. We're using imaputil to move the
Groupwise mailboxes
Have Cyrus-imap working great and can...
sieveshell -u pnelson -a pnelson localhost
then:
>put test.siqeve
>activate test.sieve
>list
test.sieve <- active script
The test.sieve is simply:
require "fileinto";
if header :contains "Subject" "test" {
fileinto "INBOX.test;
}
INBOX.test does exis
pnelson wrote:
Yes dumping to removable medium.
Why not write directly to tape rather than going through an extra step
and requiring extra disk space?
So a cyrus backup needs to contain:
/var/spool/imap
/var/lib/imap/mailboxes.db
to be useful as a backup, right? With these to things I can
On Fri, 13 Jun 2003, pnelson wrote:
> On Fri, 2003-06-13 at 12:11, Igor Brezac wrote:
> > On Fri, 13 Jun 2003, pnelson wrote:
> >
> > > On Fri, 2003-06-13 at 11:29, John Alton Tamplin wrote:
> > > > pnelson wrote:
> > > >
> > > > >My last thing to do prior to converting to production is a backup
On Fri, 2003-06-13 at 12:11, Igor Brezac wrote:
> On Fri, 13 Jun 2003, pnelson wrote:
>
> > On Fri, 2003-06-13 at 11:29, John Alton Tamplin wrote:
> > > pnelson wrote:
> > >
> > > >My last thing to do prior to converting to production is a backup
> > > >strategy. I have been doing this with tar s
On Fri, 13 Jun 2003, pnelson wrote:
> On Fri, 2003-06-13 at 11:29, John Alton Tamplin wrote:
> > pnelson wrote:
> >
> > >My last thing to do prior to converting to production is a backup
> > >strategy. I have been doing this with tar something like:
> > >
> > >tar -C /var/lib-czf lib-.tar.g
On Fri, 2003-06-13 at 11:29, John Alton Tamplin wrote:
> pnelson wrote:
>
> >My last thing to do prior to converting to production is a backup
> >strategy. I have been doing this with tar something like:
> >
> >tar -C /var/lib-czf lib-.tar.gzimap
> >tar -C /var/spool -czf spool-.tar.gz
pnelson wrote:
My last thing to do prior to converting to production is a backup
strategy. I have been doing this with tar something like:
tar -C /var/lib-czf lib-.tar.gzimap
tar -C /var/spool -czf spool-.tar.gz imap
tar -cf cyrus-.tar
This is producing a pretty big file(s):
lib-.tar.g
My last thing to do prior to converting to production is a backup
strategy. I have been doing this with tar something like:
tar -C /var/lib-czf lib-.tar.gzimap
tar -C /var/spool -czf spool-.tar.gz imap
tar -cf cyrus-.tar
This is producing a pretty big file(s):
lib-.tar.gz-> 2.2
Sorry guys, my fault :-)
I forgot to put
smtpauthrequiredpam_pgsql.sotry_first_pass
smtpaccount requiredpam_pgsql.sotry_first_pass
in my pam.conf file
Dmitry
After more searching I just realized that the following will also work
without the need for anonymous to have p rights.
/usr/cyrus/bin/deliver -m Junk -a boutilpj boutilpj
Michael Bacon wrote:
If you're using deliver, the user that needs "post" access to the
mailbox is not cyrus, but anonym
Hi,
I have a problem sending mail using sendmail SASL Authentication. I'm using
saslauthd -a pam for authentication. pam module is pam-pgsql Users can login to
Cyrus IMAPD and receive their mail using MS Outlook Express but they can't send
mail. The accounts setup to authenticate to mail server
On 13 Jun 2003, Rob Siemborski said:
> On Fri, 13 Jun 2003, Igor Brezac wrote:
>
>>> Anything that goes inside a lib should be -fPIC. Really. I have
>>> done this in the Debian build (which runs OK in S/390, IA64,
>>> Alpha, MIPS, MIPS-EL...) ages ago. I don't know if these changes
>>> are in CM
On Fri, 13 Jun 2003, Lawrence Greenfield wrote:
>Date: Fri, 13 Jun 2003 11:11:41 -0400 (EDT)
>From: Rob Siemborski <[EMAIL PROTECTED]>
>
>> > Yep. Arch dislikes mixing PIC and non-PIC code inside a
>> > relocatable object.
>>
>> Correct. On Solaris, I build lib/ and perl/
On Fri, 13 Jun 2003, Rob Siemborski wrote:
> On Fri, 13 Jun 2003, Igor Brezac wrote:
>
> > > Anything that goes inside a lib should be -fPIC. Really. I have done this in
> > > the Debian build (which runs OK in S/390, IA64, Alpha, MIPS, MIPS-EL...)
> > > ages ago. I don't know if these changes ar
Date: Fri, 13 Jun 2003 11:11:41 -0400 (EDT)
From: Rob Siemborski <[EMAIL PROTECTED]>
> > Yep. Arch dislikes mixing PIC and non-PIC code inside a
> > relocatable object.
>
> Correct. On Solaris, I build lib/ and perl/sieve/lib with -fPIC
> just to build cyrus-imap perl stuff.
Hmmm I see your point. Maybe not such a good idea.
Thanks for setting me straight.
Rich
On Fri, 2003-06-13 at 10:19, Rob Siemborski wrote:
> On Fri, 13 Jun 2003, Richard Houston wrote:
>
> > It would be very cool to have the actual messages stored in database as
> > well. The dbmail project is d
On Fri, 13 Jun 2003, Richard Houston wrote:
> It would be very cool to have the actual messages stored in database as
> well. The dbmail project is doing this in Mysql or Postgresql. Imagine
> the maturity of Cyrus with all the benefits of storage and backup in a
> database. Would be cool.
Except
On Fri, 13 Jun 2003, Igor Brezac wrote:
> > Anything that goes inside a lib should be -fPIC. Really. I have done this in
> > the Debian build (which runs OK in S/390, IA64, Alpha, MIPS, MIPS-EL...)
> > ages ago. I don't know if these changes are in CMU Cyrus.
>
> This in true only for shared libs
Just an idea,
It would be very cool to have the actual messages stored in database as
well. The dbmail project is doing this in Mysql or Postgresql. Imagine
the maturity of Cyrus with all the benefits of storage and backup in a
database. Would be cool.
Thanks
Rich
On Fri, 2003-06-13 at 03:34, G
On Fri, 13 Jun 2003, Henrique de Moraes Holschuh wrote:
> On Fri, 13 Jun 2003, [EMAIL PROTECTED] wrote:
> > Compiling with the -fPIC fixes the problem. I had to do this for the
> > following: imclient.c imparse.c xmalloc.c imapurl.c iptostring.c assert.c
> > util.c libisieve.c prot.c
> >
> > Why
On Fri, 13 Jun 2003, John Alton Tamplin wrote:
> > As far as I've been able to find, the only way to migrate use info
> > from an old box running sendmail authenticating against shadow to a
> > new system running postfix authenticating against sasldb2 is to use
> > the auto_transition feature. Is
John Alton Tamplin wrote:
blast wrote:
As far as I've been able to find, the only way to migrate use info
from an old box running sendmail authenticating against shadow to a
new system running postfix authenticating against sasldb2 is to use
the auto_transition feature. Is this true, or is th
Michael,
Thanks. Now to try and get Exim to deliver to subfolders using lmtp. :-)
Anybody get that working corectly?
Michael Bacon wrote:
If you're using deliver, the user that needs "post" access to the
mailbox is not cyrus, but anonymous. So "sam user.boutilpj anonymous p"
(or "anyone p")
On Fri, 13 Jun 2003, [EMAIL PROTECTED] wrote:
> Compiling with the -fPIC fixes the problem. I had to do this for the
> following: imclient.c imparse.c xmalloc.c imapurl.c iptostring.c assert.c
> util.c libisieve.c prot.c
>
> Why does -fPIC fix this problem?
Because of either:
1. AMD64 is unfo
blast wrote:
As far as I've been able to find, the only way to migrate use info
from an old box running sendmail authenticating against shadow to a
new system running postfix authenticating against sasldb2 is to use
the auto_transition feature. Is this true, or is there perhaps a
manual_trans
[EMAIL PROTECTED] wrote:
Compiling with the -fPIC fixes the problem. I had to do this for the
following: imclient.c imparse.c xmalloc.c imapurl.c iptostring.c assert.c
util.c libisieve.c prot.c
Why does -fPIC fix this problem?
Code to be used in a shared library must be position-independent, s
As far as I've been able to find, the only way to migrate use info from
an old box running sendmail authenticating against shadow to a new
system running postfix authenticating against sasldb2 is to use the
auto_transition feature. Is this true, or is there perhaps a
manual_transition feature
If you're using deliver, the user that needs "post" access to the mailbox
is not cyrus, but anonymous. So "sam user.boutilpj anonymous p" (or
"anyone p") is what you need. Should work after you do that.
Michael
--On Friday, June 13, 2003 9:35 AM -0300 Patrick Boutilier
<[EMAIL PROTECTED]> wr
On Fri, 13 Jun 2003, Rob Siemborski wrote:
> I'm anticipating doing a next 2.1 version of both SASL and Cyrus, and
> probably shortly thereafter a 2.2.1-ALPHA
...by early next month. ;)
-Rob
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Rob Siemborski * Andrew Systems Gr
On Fri, 13 Jun 2003, Henrique de Moraes Holschuh wrote:
> On Thu, 12 Jun 2003, Ken Murchison wrote:
> > I seem to recall this being fixed in CVS as well.
>
> IMHO CMU should package a 2.2alpha2. Too many fixes are already
> in CVS... enough that nobody should be using 2.2alpha anymore.
We're st
Compiling with the -fPIC fixes the problem. I had to do this for the
following: imclient.c imparse.c xmalloc.c imapurl.c iptostring.c assert.c
util.c libisieve.c prot.c
Why does -fPIC fix this problem?
> [EMAIL PROTECTED] wrote:
>
>>make[2]: Entering directory `/root/src/cyrus-imapd-2.1.13/perl/
Cyrus 2.1.13
According to the man page for deliver the "cat ..." command below should
put the message in the Junk folder however it goes directly into the INBOX.
Clip from 'man deliver":
-m mailbox
Deliver to mailbox. If any userids are specified,
attempts to
del
Henrique de Moraes Holschuh wrote:
On Thu, 12 Jun 2003, Ken Murchison wrote:
I seem to recall this being fixed in CVS as well.
IMHO CMU should package a 2.2alpha2. Too many fixes are already
in CVS... enough that nobody should be using 2.2alpha anymore.
That will probably happen soon. Th
Hi,
I don't suppose that custom MySQL connector is 'available' is it?
Regards,
Gareth.
On Thu, 2003-06-12 at 18:22, Brasseur Valéry wrote:
I use a custom mysql database connector for my mailboxes !
> -Original Message-
> From: Rob Siemborski [mailto:[EMAIL PROTECTED]
> Sent: Thursd
Hello list,
I've installed cyrus-imapd 2.1.13 and cyrus-sasl 2.1.13, but I am having
trouble authenticathing.
I don't want to create unix users for every imap user so I'd like to use
the sasldb athentication.
I'm using Solaris 8 platform.
My sasldb is at /etc/sasldb2 and the cyrus user can read
46 matches
Mail list logo
