reconstruct -m -- gone for good?

2002-01-14 Thread Michael Bacon

I was getting ready to do our first big move of users from one PO to 
another since we went from 1.x to 2.0, and discovered that the reconstruct 
-m option is no longer available.  This was a pretty key part of our 
mailbox relocation process, and I was a bit sad to see it go.

I imagine this feature was turned off due to the change in the mboxlist, 
but is it gone for good?  Was it taken out because it was thought to be 
more trouble than it was worth, or is there a real coding barrier to 
getting it to work with the new code?

Thanks,
Michael Bacon
Duke University
[EMAIL PROTECTED]



Re: problem with vacation being case-sensitive

2002-01-14 Thread Gary Mills

On Mon, Jan 14, 2002 at 05:35:49PM +, John Holman wrote:
> 
> In fact, even when the local part of addresses is case sensitive, I think 
> it would be better to do a case insensitive match for purposes of deciding 
> eligibility for a vacation message. After all, if the message is delivered 
> (so the envelope recipient address is correct) and has a to/cc/bcc header 
> that satisfies a case-insensitive match, under what circumstances could it 
> be wrong to send a vacation message?

A major part of this problem is that the envelope recipient address
is constructed in such a way that it can never match a header recipient
address.  This happens because the MTA, sendmail in my case, strips
the domain portion of the envelope recipient, and then Cyrus lmtpd
appends `@unspecified.domain' to it.  This requires a configuration
option so that lmtpd will append the correct domain.  Lmtpd requires
some information only known to the MTA.

> If that is not agreed, perhaps there could be a configuration option for 
> the vacation facility to do a case-insensitive match?

Again, lmtpd needs to know some information, whether user names are
case-insensitive, known only to the MTA.

The real problem is that the Cyrus sieve module does not know the
e-mail address of the recipient, and must guess at it by by examining
headers.  Solving this would solve the other problems.

-- 
-Gary Mills--Unix Support--U of M Academic Computing and Networking-



lmtp seems to be dying

2002-01-14 Thread Chris Peck

Folks,
We upgraded to cyrus 2.0.16 the weekend of the 4th, other than issues we 
blamed on moving to the DB mailboxes (which we seemd to fix by moving to 
a flatfile), the system was quite stable.  All has been running fine 
until yesterday, when the lmtp process seemed to just die. master didn't 
start any new ones, so mail was not being delivered.

Here's the messages from my syslog after it dies:
Jan 14 13:47:14 mail1 sendmail[27168]: [ID 801593 mail.crit] 
g0EIktC3027096: SYSERR(root): Could not connect to socket 
/var/imap/socket/lmtp: Connection refused by localhost
Jan 14 13:47:14 mail1 sendmail[27170]: [ID 801593 mail.crit] 
g0EIlBC5025826: SYSERR(root): Could not connect to socket 
/var/imap/socket/lmtp: Connection refused by localhost

It has died three times already today (I stop & start master to fix it, 
not the best solution).

Here's the entries from my cyrus.conf file:

# UNIX sockets start with a slash and are put into /var/imap/sockets
SERVICES {
   # add or remove based on preferences
   imap  cmd="imapd" listen="imap" prefork=5
   imaps cmd="imapd -s" listen="imaps" prefork=1
   pop3  cmd="pop3d" listen="pop3" prefork=5
   pop3s cmd="pop3d -s" listen="pop3s" prefork=1
   sieve cmd="timsieved" listen="sieve" prefork=0

   # at least one LMTP is required for delivery
#  lmtp cmd="lmtpd" listen="lmtp" prefork=0
   lmtpunix  cmd="lmtpd" listen="/var/imap/socket/lmtp" prefork=1
}

any ideas???

Chris Peck
Manager of Unix Services
Information Technology
The College of William and Mary
Williamsburg, VA 23187




Re: problem with vacation being case-sensitive

2002-01-14 Thread John Holman

Just to say that this is also a problem for us. Our email addresses are 
case insensitive, and I can be mailed as [EMAIL PROTECTED] or 
[EMAIL PROTECTED] or any other combination. Users complain about having 
to put their mail address into the vacation facility at all - and are not 
at all happy about having to put in all likely combinations of upper and 
lower case.

In fact, even when the local part of addresses is case sensitive, I think 
it would be better to do a case insensitive match for purposes of deciding 
eligibility for a vacation message. After all, if the message is delivered 
(so the envelope recipient address is correct) and has a to/cc/bcc header 
that satisfies a case-insensitive match, under what circumstances could it 
be wrong to send a vacation message?

If that is not agreed, perhaps there could be a configuration option for 
the vacation facility to do a case-insensitive match?

John.


At 14:43 14/01/02, Olaf Dreyer wrote:
>Hello,
>
>i am still fighting with vacation. As far as i understand the source
>code, and what i read in the archives, the envelope address and the
>strings in the :addresses field are compared to To, Cc and Bcc fields.
>If they match, a vacation message may be sent.
>My sendmail configuration, which is derived from cyrusv2.mc, sets the
>recipient to lower case, and leaves the To/Cc/Bcc fields as provided by
>the sender. This behaviour is ok, as i want cyrus to store mails for
>Olaf.Dreyer and olaf.dreyer or even olaf.Dreyer in the same inbox.
>With sieve/vacation i really have to provide all possible variants?
>I think this would make vacation too difficult to use.
>
>TIA
>Olaf Dreyer





problem with vacation being case-sensitive

2002-01-14 Thread Olaf Dreyer

Hello,

i am still fighting with vacation. As far as i understand the source
code, and what i read in the archives, the envelope address and the
strings in the :addresses field are compared to To, Cc and Bcc fields.
If they match, a vacation message may be sent.
My sendmail configuration, which is derived from cyrusv2.mc, sets the
recipient to lower case, and leaves the To/Cc/Bcc fields as provided by
the sender. This behaviour is ok, as i want cyrus to store mails for
Olaf.Dreyer and olaf.dreyer or even olaf.Dreyer in the same inbox.
With sieve/vacation i really have to provide all possible variants?
I think this would make vacation too difficult to use.

TIA
Olaf Dreyer





Re: Compile error with Cyrus

2002-01-14 Thread Robert Scussel

I ended up with the same problem. The way I fixed it was sort of a hack.

THe default install for redhat 7.1 places com_err in /usr/include/et/

To work around this, you can either go in and manually change the
makefiles that look for com_err, or I symlinked /usr/unclude/com_err.h
with /usr/include/et/com_err.h. For some reason, even though Cyrus comes
with its own com_err.h, and /usr/include is included, it still can't
find com_err.h

Hope this helps,
B

"Paxton, Darren" wrote:
> 
> Good afternoon.
> 
> I have downloaded and attempted to run the cyrus compiler on my Linux system
> (Suse Linux 7.1 running 2.4.0).
> 
> The configure script appears to run without any problems, but on
> compilation, it fails with the following error:
> 
> imapd.c
> imapd.c:58: comm_err.h: No such file or directory
> make[1]: *** [imapd.o] Error 1
> make[1]: Leaving directory '/usr/local/tarballcyrus/imap'
> make: ***[all] Error 1
> 
> Could anyone out there help me with what could be the cause of this?
> 
> Is there a file missing from the tarball distribution?
> 
> Thanks
> 
> Darren
> 
> *** IMPORTANT NOTE **
> The above information is confidential to the addressee and may be
> privileged.  Unauthorised access and use is prohibited. William M. Mercer
> Limited is regulated by IMRO and the Personal Investment Authority.
> Registered in London No. 984275 Registered Office: Telford House, 14 Tothill
> Street, London SW1H 9NB

--
Robert Scussel
1024D/BAF70959/0036 B19E 86CE 181D 0912  5FCC 92D8 1EA1 BAF7 0959



C7B0PyGXjXzXA4MesIB ------------------最後通知----------------- I469m8gNRMMeKz885fmjLx7W

2002-01-14 Thread TEL : 0800-003-577

-½Ð¬Ý
 www.powerlee.com.tw-





IMAP 2.1.0 Perl module compilation

2002-01-14 Thread Ilya Sedelnikov


Hi, 

There's no "cc" compiler on my Solaris 8 machine.
Did somebody succeed to compile the Perl module ( $BASE_DIR/perl/imapd )
using "gcc" ?
(  Makefile, created from /perl/imap/Makefile.PL uses "cc" as a default
compiler.
   I tries to substitute "gcc" for "cc" but there is an -KPIC option
that "gcc"
   does not recognize )

Ilya 





Re[2]: Cyrus 2.0.16 - cyradm error

2002-01-14 Thread Alexander Lunyov

Hello birger,

Monday, January 14, 2002, 3:40:31 PM, you wrote:

>>   I have cyrus-sasl 1.5.24 and cyrus 2.0.16 on FreeeBSD 4.1.1.
>>   Cyrus itself works (telnet localhost imap - says that everything
>>   is ok), and i even can log in to. But i can't run cyradm, it says:
btd> System.  Your perl module should be linked to a library (libsasl.so) which 
btd> should contain an important function (sasl_client_init).  Normally, every 
btd> working cyrus-sasl installation should deploy libsasl.so somewhere
btd>  (/usr/local/lib/?) which should contain sasl_client_init().  

btd>  $ ldd /usr/local/lib/perl5/site_perl/5.005/i386-freebsd/auto/Cyrus/IMAP/IMAP.so


  it says:

kudr#ldd /usr/local/lib/perl5/site_perl/5.005/i386-freebsd/auto/Cyrus/IMAP/IMAP.so
/usr/local/lib/perl5/site_perl/5.005/i386-freebsd/auto/Cyrus/IMAP/IMAP.so:
/usr/local/lib/perl5/site_perl/5.005/i386-freebsd/auto/Cyrus/IMAP/IMAP.so: Exec
format error
/usr/local/lib/perl5/site_perl/5.005/i386-freebsd/auto/Cyrus/IMAP/IMAP.so: exit
status 1
kudr#

 and:

kudr# ldd -v /usr/local/lib/perl5/site_perl/5.005/i386-freebsd/auto/Cyrus/IMAP/IMAP.so
/usr/local/lib/perl5/site_perl/5.005/i386-freebsd/auto/Cyrus/IMAP/IMAP.so: this
is an ELF program; use objdump to examine.
kudr#
 

btd> will tell you against which libs your perl module is linked to.  Maybe this is
btd> an old lib whereas the correct one sits somewhere else?  Or your module is not
btd> at all linked to libsasl.so? (which is definitely a broken cyrus install then)

 And  if  it is so, what's then? Deinstall all (i mean cyrus-sasl,
 cyrus-imapd), then install again?


-- 
Best regards,
 Alexandermailto:[EMAIL PROTECTED]





Re: sieve and plain text password

2002-01-14 Thread birger

Ludovic Bellier schrieb am Mon, Jan 14, 2002 at 01:17:43PM +0100:
> ok
> I used your perl command to generate a base64 password but ...
> 
> > perl -e 'use
> MIME::Base64;$u=bellier;$p=tititoto;$r=encode_base64("$u\0$u\0$p");print
> "$r\n";'
> YmVsbGllcgBiZWxsaWVyAHRpdGl0b3Rv
> 
> the string does not end with a =
> 
> so timsieved does not want to let me in :
> > telnet localhost sieve
> Trying 127.0.0.1...
> Connected to localhost.
> Escape character is '^]'.
> "IMPLEMENTATION" "Cyrus timsieved v1.0.0"
> "SASL" "PLAIN"
> "SIEVE" "fileinto reject envelope vacation imapflags notify subaddress
> regex"
> OK
> authenticate "plain" "YmVsbGllcgBiZWxsaWVyAGthbWk6bmlz"
> NO ("SASL" "internal error") "Authentication error"
> 
> the error message is no longer the same

OK, sorry, I'm not as bright with base64 as I thought.  You're right, it
does not end with a "=", this is seemingly not the case with all base64 
user/passw encoded strings.

Anyway, the perl command above does result in a correct base64 string
which can be used for SMTP-AUTH (which we won't deal here with either, 
I'm sorry for the confusion).

Maybe you try a simple encode_base64($pass) for auth with sieve?


Regards,

- Birger



Re: Cyrus 2.0.16 - cyradm error

2002-01-14 Thread birger

Alexander Lunyov schrieb am Mon, Jan 14, 2002 at 03:09:18PM +0300:
> Hello All,
> 
>   I have cyrus-sasl 1.5.24 and cyrus 2.0.16 on FreeeBSD 4.1.1.
>   Cyrus itself works (telnet localhost imap - says that everything
>   is ok), and i even can log in to. But i can't run cyradm, it says:
> 
> 
> kudr# /usr/local/bin/cyradm
> Can't load '/usr/local/lib/perl5/site_perl/5.005/i386-freebsd/auto/Cyrus/IMAP/IM
> AP.so' for module Cyrus::IMAP: /usr/local/lib/perl5/site_perl/5.005/i386-freebsd
> /auto/Cyrus/IMAP/IMAP.so: Undefined symbol "sasl_client_init" at /usr/libdata/pe
> rl/5.00503/DynaLoader.pm line 169.
> 
>  at /usr/local/lib/perl5/site_perl/5.005/i386-freebsd/Cyrus/IMAP/Admin.pm line 4
> 3
> BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.005/i386-f
> reebsd/Cyrus/IMAP/Admin.pm line 43.
> BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.005/i386-f
> reebsd/Cyrus/IMAP/Shell.pm line 58.
> BEGIN failed--compilation aborted.
> kudr#
>   
>   What   i've   done wrong? Is it about configuration files, or is
>   it about the system?

System.  Your perl module should be linked to a library (libsasl.so) which 
should contain an important function (sasl_client_init).  Normally, every 
working cyrus-sasl installation should deploy libsasl.so somewhere
 (/usr/local/lib/?) which should contain sasl_client_init().  

 $ ldd /usr/local/lib/perl5/site_perl/5.005/i386-freebsd/auto/Cyrus/IMAP/IMAP.so

will tell you against which libs your perl module is linked to.  Maybe this is
an old lib whereas the correct one sits somewhere else?  Or your module is not
at all linked to libsasl.so? (which is definitely a broken cyrus install then)


Regards,

- Birger



Compile error with Cyrus

2002-01-14 Thread Paxton, Darren

Good afternoon.

I have downloaded and attempted to run the cyrus compiler on my Linux system
(Suse Linux 7.1 running 2.4.0).

The configure script appears to run without any problems, but on
compilation, it fails with the following error:

imapd.c
imapd.c:58: comm_err.h: No such file or directory
make[1]: *** [imapd.o] Error 1
make[1]: Leaving directory '/usr/local/tarballcyrus/imap'
make: ***[all] Error 1

Could anyone out there help me with what could be the cause of this?

Is there a file missing from the tarball distribution?

Thanks

Darren

*** IMPORTANT NOTE **
The above information is confidential to the addressee and may be
privileged.  Unauthorised access and use is prohibited. William M. Mercer
Limited is regulated by IMRO and the Personal Investment Authority.
Registered in London No. 984275 Registered Office: Telford House, 14 Tothill
Street, London SW1H 9NB 




Re: sieve and plain text password

2002-01-14 Thread Ludovic Bellier

ok
I used your perl command to generate a base64 password but ...

> perl -e 'use
MIME::Base64;$u=bellier;$p=tititoto;$r=encode_base64("$u\0$u\0$p");print
"$r\n";'
YmVsbGllcgBiZWxsaWVyAHRpdGl0b3Rv

the string does not end with a =

so timsieved does not want to let me in :
> telnet localhost sieve
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
"IMPLEMENTATION" "Cyrus timsieved v1.0.0"
"SASL" "PLAIN"
"SIEVE" "fileinto reject envelope vacation imapflags notify subaddress
regex"
OK
authenticate "plain" "YmVsbGllcgBiZWxsaWVyAGthbWk6bmlz"
NO ("SASL" "internal error") "Authentication error"

the error message is no longer the same

- Original Message -
From: <[EMAIL PROTECTED]>
To: "Ludovic Bellier" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, January 14, 2002 12:02 PM
Subject: Re: sieve and plain text password


> Ludovic Bellier schrieb am Mon, Jan 14, 2002 at 11:42:11AM +0100:
> > hello
> >
> > I use cyrus 2.0.16 and I've problem with the plaintext password
> > authentication.
> >
> > > telnet localhost sieve
> > Trying 127.0.0.1...
> > Connected to localhost.
> > Escape character is '^]'.
> > "IMPLEMENTATION" "Cyrus timsieved v1.0.0"
> > "SASL" "PLAIN"
> > "SIEVE" "fileinto reject envelope vacation imapflags notify subaddress
> > regex"
> > OK
> > authenticate "plain" "fswukcps"
> > NO ("SASL" "error base64 decoding string") "Authentication error"
> >
> > In the begining I did not have SASL PLAIN. I had to link the
> > /usr/local/lib/sasl directory in /usr/lib/sasl. Now I have a base64
error...
> > Hum ??
> > Any adea ?
>
> Your base64 string looks weird.  Note that base64 is *not* a plaintext
pass-
> word.
>
> You cannot use sieve's "plain" the same way as imap's native "LOGIN".
> The imapd itself converts the string given with "LOGIN" into a base64
string
> such that sasl-plain can decode it correctly.
>
> Valid base64 strings look like this:
>
>   Ymx1YgBibHViAG5hc2U=
>
> This is always significant longer than yours above and always ends with a
"=".
>
> You can generate a valid base64 string with perl:
>
> $ perl -e 'use MIME::Base64; $user=; $pass=;
$result = encode_base64("$user\0$user\0$pass"); print "$result\n";'
>
>
> Regards,
>
> - Birger
>
>




Cyrus 2.0.16 - cyradm error

2002-01-14 Thread Alexander Lunyov

Hello All,

  I have cyrus-sasl 1.5.24 and cyrus 2.0.16 on FreeeBSD 4.1.1.
  Cyrus itself works (telnet localhost imap - says that everything
  is ok), and i even can log in to. But i can't run cyradm, it says:


kudr# /usr/local/bin/cyradm
Can't load '/usr/local/lib/perl5/site_perl/5.005/i386-freebsd/auto/Cyrus/IMAP/IM
AP.so' for module Cyrus::IMAP: /usr/local/lib/perl5/site_perl/5.005/i386-freebsd
/auto/Cyrus/IMAP/IMAP.so: Undefined symbol "sasl_client_init" at /usr/libdata/pe
rl/5.00503/DynaLoader.pm line 169.

 at /usr/local/lib/perl5/site_perl/5.005/i386-freebsd/Cyrus/IMAP/Admin.pm line 4
3
BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.005/i386-f
reebsd/Cyrus/IMAP/Admin.pm line 43.
BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.005/i386-f
reebsd/Cyrus/IMAP/Shell.pm line 58.
BEGIN failed--compilation aborted.
kudr#
  
  What   i've   done wrong? Is it about configuration files, or is
  it about the system?
  In Admin.pm it stops on  line 43:

  use Cyrus::IMAP;

-- 
Best regards,
 Alexander  mailto:[EMAIL PROTECTED]





Re: sieve and plain text password

2002-01-14 Thread birger

Ludovic Bellier schrieb am Mon, Jan 14, 2002 at 11:42:11AM +0100:
> hello
> 
> I use cyrus 2.0.16 and I've problem with the plaintext password
> authentication.
> 
> > telnet localhost sieve
> Trying 127.0.0.1...
> Connected to localhost.
> Escape character is '^]'.
> "IMPLEMENTATION" "Cyrus timsieved v1.0.0"
> "SASL" "PLAIN"
> "SIEVE" "fileinto reject envelope vacation imapflags notify subaddress
> regex"
> OK
> authenticate "plain" "fswukcps"
> NO ("SASL" "error base64 decoding string") "Authentication error"
> 
> In the begining I did not have SASL PLAIN. I had to link the
> /usr/local/lib/sasl directory in /usr/lib/sasl. Now I have a base64 error...
> Hum ??
> Any adea ?

Your base64 string looks weird.  Note that base64 is *not* a plaintext pass-
word.

You cannot use sieve's "plain" the same way as imap's native "LOGIN".
The imapd itself converts the string given with "LOGIN" into a base64 string 
such that sasl-plain can decode it correctly.  

Valid base64 strings look like this: 

  Ymx1YgBibHViAG5hc2U=

This is always significant longer than yours above and always ends with a "=".

You can generate a valid base64 string with perl:

$ perl -e 'use MIME::Base64; $user=; $pass=; $result = 
encode_base64("$user\0$user\0$pass"); print "$result\n";'


Regards,

- Birger



sieve and plain text password

2002-01-14 Thread Ludovic Bellier

hello

I use cyrus 2.0.16 and I've problem with the plaintext password
authentication.

> telnet localhost sieve
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
"IMPLEMENTATION" "Cyrus timsieved v1.0.0"
"SASL" "PLAIN"
"SIEVE" "fileinto reject envelope vacation imapflags notify subaddress
regex"
OK
authenticate "plain" "fswukcps"
NO ("SASL" "error base64 decoding string") "Authentication error"

In the begining I did not have SASL PLAIN. I had to link the
/usr/local/lib/sasl directory in /usr/lib/sasl. Now I have a base64 error...
Hum ??
Any adea ?




sieve/vacation problems

2002-01-14 Thread Olaf Dreyer

Hello,

i am trying to get timsieved with vacation running on my system. I am
using SuSE Linux 7.2 with sendmail 8.11.6 and cyrus imapd 2.0.16.

Sieve and vacation are working, mails are filtered and vacation replies
are also sent. BUT, it looks like the addresses in the :addresses field
are case sensitive. My script looks like this:

require ["fileinto","vacation"];

vacation :days 1 :addresses ["[EMAIL PROTECTED]"] text:
Autogenerated Message:
On vacation for some time.




Suggestions for a good gui for cyrus admin ??

2002-01-14 Thread J.A.J. van Belkum

Howdy all,

I am looking for a good tool to use for Cyrus User Administration.  I
know that there are some available, but I am wondering if someone has
good experiences with one.  I am running the system on a redhat Linux
server and the cyrus system will serve about 1000 users.

I am open for any suggestions

Thanks,
Aukjan