Re: Configuration Tools.
Joshua Schmidlkofer wrote: What is the preferred method of managing Cyrus? js To let someone else do it. ;-) I prefer to just do it via command line but I also don't have LOTS of users...others use a web-based product whose title escapes me at the moment. =G=
Re: Cyrus IMAPd v2.1.10
Marc-Christian Petersen wrote: Hi there, can anyone give me he hint how can I get rid of this message? With v2.1.2 (I used this before upgrading) this worked fine. Nov 20 03:11:22 linux imapd[21940]: login: codeman.[10.0.0.10] mcp plaintext Nov 20 03:11:22 linux imapd[21940]: IOERROR: opening /opt/cyrus/var/lib/user/U/mcp.seen: No such file or directory Nov 20 03:11:22 linux imapd[21940]: DBERROR: opening /opt/cyrus/var/lib/user/U/mcp.seen: cyrusdb error Nov 20 03:11:22 linux imapd[21940]: Could not open seen state for mcp (System I/O error) Nov 20 03:11:22 linux imapd[21940]: open: user mcp opened INBOX TIA! ciao, Marc Try reconstructing the users mailbox...it seems like it's missing the seen db. =G=
Re: Skiplist / best practice for 2.1 branch
Henrique de Moraes Holschuh wrote: On Mon, 18 Nov 2002, Jonathan Marsden wrote: On 18 Nov 2002, Henrique de Moraes Holschuh writes: 1. Heavily tested and debugged AND patched BerkeleyDB 3.2, stay away from 4.x for now. (i.e. use the ones from RedHat or Debian, not upstream). Red Hat now supplies 4.0.14, for example the db4-4.0.14-14.i386.rpm in Then stick to Debian :-) Red Hat 8.0. It appears to work OK for me, but we have small setups only here... maybe we have just not met the bug(s) yet?? Well, people report a good range of trouble with DB4 in this list, but not many in DB 3.2. Maybe too few of us still use 3.2, though. In general, though the statement "Use 3.2... ie. use the ones from RedHat or Debian ..." is confusing, because for Red Hat 8.x users, the current RH-supplied production release of these libraries is now 4.0.14. I will keep that in mind. Are you recommending that RH 8.0 users running Cyrus should downgrade their BDB libraries to a 3.x RPM set for db3 (perhaps as supplied for No. That will break the OS. What will it take to get some/all of these patches into 2.1.11 or 2.2 or both? Is that a worthwhile objective? Or are these changes so No. CMU is slowly making their mind about the patches while they study them, but they will take a lot of time to leak into cyrus. And I don't expect all of them to, either. Linux-specific that they have would negative consequences if applied to a source tree used for a Solaris or *BSD build?? With Linux being No negative consequences that I know of. But increased resilience hides the real problems sometimes. putting this info into a FAQ (as well as making it the default in 2.2) seems approriate. It is in both AFAIK. Correct me if I'm wrong...wasn't one of the changes with 2.1.10 the ability to run with BDB 4.1? =G=
gpl sasl
This popped up on the postfix list...anyone from the Cyrus group checked it out? Just curious...it appears to be a ground up rewrite of the sasl libs... http://www.josefsson.org/libgsasl/ =G=
Re: Can't authorize via postfix
Jens wrote: >I am trying to set up so that a remote user can relay thru my postfix install >(debian system) . I seem to have everything set up correctly based on various >tests but (I think) my permissions are screwed up someplace. >From a remote system I can run imtest and authenticate. >From the same remote system using the same authorization mechanism but instead >of imtest I send an email - this gets me denied and a syslog message is >generated that there is no such thing as /etc/sasldb2 >Accessing the smtp server directly shows the appropriate authorization >mechanisms are available so I am thinking that maybe permissions for >/etc/sasldb2 are messed up. > >What authorizations should be on /etc/sasldb2 (I tried cyrus:nogroup and >cyrus:postfix) ? >Is there some other incantation I am missing to get sasl authorization to >work? > >Thanks > >Jens > > Actually, I was wondering when the Debian chroot of postfix would rear it's ugly head. There is really no reason to chroot postfix. Just edit postfix's master.cf file and change the chroot to no. That's has been the most common answer on the postfix user list for Debian users. Unless you are a secret masochist and like picking and choosing the files that will be necessary in the chroot jail. =G=
Re: Secure Imap Problems
you have to create them yourself...check out: http://www.ncsu.edu/imap/admin/sslcyrus.html Phil Dibowitz wrote: > First off, thanks to all who replied... > > Ken Murchison wrote: > >> >> You need to tell Cyrus where your cert, key, and CA file are located. >> See the tls_* options in imapd.conf(5). > > > > But, eh, there aren't any. And I'm not just blind, I even did a /tls at > the top of the man page and they weren't found. See my second post about > 'impad -s' giving 'invalid option -s' > > So I did try creat a key file and a certificate based on the > instructions at openssl. Since it's for company email only, I don't > think we'll need a CA's cert, cert's signed by us will be fine. I added > this: > > tls_cert_file: /usr/cyrus/etc/imaps.cert > tls_key_file: /usr/cyrus/etc/imaps.pem > > And restarted, but it didn't help much. > > >> You can't use imtest to test imaps (SSL-wrapped imap). The only way to >> do this is to use something like: >> >> openssl s_client -connect localhost:imaps >> >> an then login manually with: >> >> . login test > > > > Thanks for the info! Good to know. WHen I do the first command I get a > "CONNECTED", but it doesn't respond to the imap command. > > Phil > -- =G= -=* I'm sorry if doing things correctly offends you. *=-
Re: Lmtp time-out for one user
I would have to agree with you in that it is the client side not the server since this is the only user having this problem. At one of my previous jobs we used to have this problem on a regular basis. The "fix" we used was to remove the user's IMAP folder from their machine. Be careful not to remove any filters they have. After the folder was removed it would force netscape to rebuild it (I'm assuming the user is IMAP user). Just make sure netscape is closed before you try this. Another possibility is a hung process. This is easily checked for by closing netscape and looking for a netscape process still running on the user's machine. If it's there, KILL it. Warren Flemmer wrote: > Greetings > > I have been having problems with one users mailbox. This occurs > about weekly. I see the following in the mailq: > > (conversation with /var/imap/socket/lmtp[/var/imap/socket/lmtp] > timed out while sending end of data -- message may be sent more than once) > > Restarting the server has proven to be the only means I know to > solve the problem. Restarting cyrus or postfix has not fix the problem > in the past. Only one user ever seems to have this problem. > Other users can work without issue (even when this user is having > a problem) . The user can read the mail box but cannot copy > between mailboxes when the problem occurs. > > imapd.log shows no sign of a problem. The messages log the also > shows nothing. The maillog shows: > May 20 15:01:46 unicorn postfix/lmtp[31996]: 3EDB173C86: > to=<[EMAIL PROTECTED]>, > relay=/var/imap/socket/lmtp[/var/imap/socket/lmtp], delay=2948, > status=deferred (conversation with > /var/imap/socket/lmtp[/var/imap/socket/lmtp] timed out while sending end > of data -- message may be sent more than once) > > My feeling is that the mail client is the cause of the problem. It is > netscape 6.2, > but netscape 4.something has been loaded after 6.2. I will uninstall > both and > only load 6.2. > > But, how do I get the mailbox working without rebooting? > > Config: RedHat 7.1 > Postfix: 1.1.8 > cyrus: 2.0.16 > amavisd: 20020300 > lmtp: through socket > > Regards > Warren > -- =G= -=* I'm sorry if doing things correctly offends you. *=-
Re: double Return-Path in Cyrus
oops...I should pay more attention to where I paste stuff...see Birger's
response.
Galen Johnson wrote:
> I read this as:
> cyrus unix - n n - - pipe
> flags= user=cyrus argv=/usr/cyrus/bin/deliver -e -m -r ${sender}
> ${extension} ${user}
>
> but I haven't actually tried it...
>
> Luc de Louw wrote:
>
>> On 10 Apr 2002, Hein Roehrig wrote:
>>
>>
>>> The following message is a courtesy copy of an article
>>> that has been posted to comp.mail.imap as well.
>>>
>>> Hein Roehrig <[EMAIL PROTECTED]> writes in comp.mail.imap:
>>>
>>>
>>>> I also get bitten by this problem (on Cyrus 2.1.3.)
>>>
>>>
>>> Ok, I resolved the problem by 1) telling postfix not to put a
>>> Return-path (dropping the R flag from the pipe transport) and 2)
>>> passing a -r ${sender} to Cyrus deliver, thus providing it with the
>>> correct envelope sender.
>>>
>>> This also improves Sieve responses a lot :-)
>>>
>>> -Hein
>>>
>>
>>
>> This means the exaxt line in /etc/postfix/master.cf looks like this?
>>
>> cyrus unix - n n - - pipe
>> flags=R -r ${sender} user=cyrus argv=/usr/cyrus/bin/deliver -e -m
>> ${extension} ${user}
>>
>>
>> Does not work here, I got errors:
>>
>> Apr 10 15:02:32 test postfix/pipe[10055]: fatal: unknown flag: -
>> (ignored)
>> Apr 10 15:02:32 test postfix/pipe[10056]: fatal: unknown flag: -
>> (ignored)
>> Apr 10 15:02:33 test postfix/master[2135]: warning: process
>> /usr/libexec/postfix/pipe pid 10055 exit status 1
>> Apr 10 15:02:33 test postfix/local[10040]: warning: premature
>> end-of-input
>> from private/cyrus socket while reading input attribute name
>> Apr 10 15:02:33 test postfix/local[10040]: warning: private/cyrus socket:
>> malformed response
>>
>>
>> I'm using Postfix 1.1.7 and cyrus 2.0.16
>>
>> Thanks for any hints
>>
>> Luc
>>
>
>
--
=G=
-=* I'm sorry if doing things correctly offends you. *=-
Re: double Return-Path in Cyrus
I read this as:
cyrus unix - n n - - pipe
flags= user=cyrus argv=/usr/cyrus/bin/deliver -e -m -r ${sender}
${extension} ${user}
but I haven't actually tried it...
Luc de Louw wrote:
> On 10 Apr 2002, Hein Roehrig wrote:
>
>
>>The following message is a courtesy copy of an article
>>that has been posted to comp.mail.imap as well.
>>
>>Hein Roehrig <[EMAIL PROTECTED]> writes in comp.mail.imap:
>>
>>
>>>I also get bitten by this problem (on Cyrus 2.1.3.)
>>
>>Ok, I resolved the problem by 1) telling postfix not to put a
>>Return-path (dropping the R flag from the pipe transport) and 2)
>>passing a -r ${sender} to Cyrus deliver, thus providing it with the
>>correct envelope sender.
>>
>>This also improves Sieve responses a lot :-)
>>
>>-Hein
>>
>
>
> This means the exaxt line in /etc/postfix/master.cf looks like this?
>
> cyrus unix - n n - - pipe
> flags=R -r ${sender} user=cyrus argv=/usr/cyrus/bin/deliver -e -m
> ${extension} ${user}
>
>
> Does not work here, I got errors:
>
> Apr 10 15:02:32 test postfix/pipe[10055]: fatal: unknown flag: - (ignored)
> Apr 10 15:02:32 test postfix/pipe[10056]: fatal: unknown flag: - (ignored)
> Apr 10 15:02:33 test postfix/master[2135]: warning: process
> /usr/libexec/postfix/pipe pid 10055 exit status 1
> Apr 10 15:02:33 test postfix/local[10040]: warning: premature end-of-input
> from private/cyrus socket while reading input attribute name
> Apr 10 15:02:33 test postfix/local[10040]: warning: private/cyrus socket:
> malformed response
>
>
> I'm using Postfix 1.1.7 and cyrus 2.0.16
>
> Thanks for any hints
>
> Luc
>
--
=G=
-=* I'm sorry if doing things correctly offends you. *=-
Re: starting cyradm
check your /etc/imapd.conf file and make sure that cyrus is an admin. Ed Sanborn wrote: > Arthur, what drugs are you taking mun? > > "nuggen-ziggen-fry?" What are you talking about? > > > And as for a practice server - I don't have one > and have no budget for one. My original question > is more than likely a simple one with a simple > answer. Not sure a practice server would help here. > > -Ed > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Chong, Arthur > Sent: Wednesday, March 13, 2002 1:35 PM > To: [EMAIL PROTECTED] > Subject: starting cyradm > > > > How about nuggen-ziggen-fry and then re-load? > > by-all-means install on a practise server first... > > I've started to re-load with slightly different > parameters and can get both the "older" and > newer versions to load up properly now... > > yee-ha! > > == > Hi folks, > I'm having to create a mailbox for the first time on my > inherited Cyrus IMAP server. I am trying to start cyradm > and am having trouble: > ~cyrus @flyingfox >cyradm -user cyrus localhost > Please enter your password: > application-specific initialization failed: authentication failed > ~cyrus @flyingfox > > I am entering my cyrus account's password. Is this not the > password it is looking for? If I give it a goofy password that > I know is not wrong it gives me the same error. > -Ed > Ed Sanborn (978) 367-8478 > Principal Network Administrator > SnowShore Networks > 285 Billerica Rd. > Chelmsford, MA. 01824 > > -- =G= -=* I'm sorry if doing things correctly offends you. *=-
Re: cyrus-imapd-2.1.3 w/ BDB4: small typo in log output of imapd,pop3d?
h...did you have this working with BDB3 before or is this a new install? if it was using the BDB3 (for whatever reason) previously, I seem to recall that you will need to have BDB4 compiled with BDB3 support (./configure --help should tell you what to do). You may also need to convert the databases to BDB4 to have it work ok. This presupposes that it was using BDB3 before (or for some reason failed to pickup your config option to use bdb4...which I seem to recall seing other with that problem) Birger Toedtmann wrote: > Hi, > > I just set up cyrus-imapd-2.1.3 on a RH7.2 box that has BDB4 installed (re- > compiled src.rpm). Any ldd's of the imapd/pop3d binaries show correct bindings > to /lib/libdb-4.0.so, so everything seems ok - service works nice - despite > some log messagess: > > Mar 12 07:57:50 testbox pop3d[19141]: DBERROR db3: 9 lockers > ^^^ > > Mmmh. As far as I could see, this may not directly lie within cyrus-imapd's > code but BDB4s, but I could not find the string "db3" in any of them (imapd, > db-4.0.so). > > Ideas? > > > Regards, > > Birger > -- =G= -=* I'm sorry if doing things correctly offends you. *=-
Re: sieveshell pb
not sure if sieveshell works the same as installsieve (which is what I use and seems to be better) but I'm pretty sure it looks for a .script extension; ie, default.script. -- =G= -=* I'm sorry if doing things correctly offends you. *=- Mathieu Arnold wrote: > Hi > > I currently have a small problem with sieveshell : > > $ sieveshell -u mat -a mat 0 > connecting to 0 > Please enter your password: x > >> list > > default <- active script > >> get default default >> quit > > $ > < editing my sieve script > > > $ sieveshell -u mat -a mat 0 > connecting to 0 > Please enter your password: tcpip > >> list > > default <- active script > >> put default > > upload failed: put script: Did not specify script data > > and from here, can't do a damn thing : > >> list > > list failed: Setting script active: Expected a command. Got something else > >> quit > > $ > > hint, someone ? :) > > ps: cyrus-imapd-2.0.16_2 from freebsd ports
Re: starting cyrus at boot?
never used mandrake but you should be able to just add '/usr/cyrus.bin.master &' to your rc.local (or equivalent) file. -- =G= -=* I'm sorry if doing things correctly offends you. *=- Jeff Bert wrote: > Tried that and didn't find one for cyrus-imapd > > >>-Original Message- >>From: [EMAIL PROTECTED] >>[mailto:[EMAIL PROTECTED]]On Behalf Of Alain Tesio >>Sent: Friday, March 08, 2002 1:34 AM >>To: [EMAIL PROTECTED] >>Cc: [EMAIL PROTECTED] >>Subject: Re: starting cyrus at boot? >> >> >>On Fri, 8 Mar 2002 01:03:01 -0800 >>"Jeff Bert" <[EMAIL PROTECTED]> wrote: >> >> >>>Sure, I have: >>> >>>Linux Mandrake 8.1, kernel 2.4.8 >>> >>>I installed cyrus-imapd-2.0.16 from the tarball >>>that I downloaded from the cyrus site. >>> >>>Jeff >>> >>Go to rpmfind.net, download a rpm package for mandrake >>and install it, it should be easier. >> >>Alain >> >>
Re: Telnet: Connection closed by foreign host
It doesn't appear that cyrus is running. I don't see master in there
anywhere. Are you starting it up in both inetd.conf and as root? I
currently just have mine start up on boot. You should be able to just
type '/usr/cyrus/bin/master &" as root to kick it off. All the cyrus
info below are pipes from postfix. I assume you have master.cf set up
correctly in postfix (it appears that you do) and that you have set
mailbox_transport and fallback_transport to
"lmtp:unix:/var/imap/socket/lmtp" in postfix's main.cf...
what does your cyrus.conf and imapd.conf look like?
SIMICRO - Manou RABARY wrote:
> "[EMAIL PROTECTED]" wrote:
>
>
>>Please:
>>
>>1. what is your cyruis version and your sasl setup?
>>2. how do you start cyrus imapd?
>>3. What does ps aux |grep cyrus say?
>>
>
> 1. cyrus-imap 2.0.16 cyrus-sasl-1.5.27 without krb
> 2. to start imapd /usr/cyrus/bin/imapd and I started /usr/cyrus/bin/master
>
> 3. Many many things
>
> rajako:/home/manou# ps aux |grep cyrus
> postfix242 0.0 1.6 1884 756 ?S16:23 0:00 pipe -n
> cyrus -t unix flags=R user=cyrus argv=/usr/cyrus/bin/deliver -e -m
> ${extension} ${user}
> postfix244 0.0 1.6 1884 756 ?S16:23 0:00 pipe -n
> cyrus -t unix flags=R user=cyrus argv=/usr/cyrus/bin/deliver -e -m
> ${extension} ${user}
> cyrus 245 0.0 1.6 2272 776 ?S16:23 0:00
> /usr/cyrus/bin/deliver -e -m root
> cyrus 246 0.0 1.6 2272 776 ?S16:23 0:00
> /usr/cyrus/bin/deliver -e -m root
> postfix247 0.0 1.6 1884 756 ?S16:23 0:00 pipe -n
> cyrus -t unix flags=R user=cyrus argv=/usr/cyrus/bin/deliver -e -m
> ${extension} ${user}
> cyrus 248 0.0 1.6 2272 776 ?S16:23 0:00
> /usr/cyrus/bin/deliver -e -m root
> postfix251 0.0 1.6 1884 756 ?S16:23 0:00 pipe -n
> cyrus -t unix flags=R user=cyrus argv=/usr/cyrus/bin/deliver -e -m
> ${extension} ${user}
> cyrus 252 0.0 1.6 2272 776 ?S16:23 0:00
> /usr/cyrus/bin/deliver -e -m root
> postfix420 0.0 1.6 1884 756 ?S16:42 0:00 pipe -n
> cyrus -t unix flags=R user=cyrus argv=/usr/cyrus/bin/deliver -e -m
> ${extension} ${user}
> cyrus 421 0.0 1.6 2272 776 ?S16:42 0:00
> /usr/cyrus/bin/deliver -e -m root
> postfix 2140 0.0 1.6 1884 756 ?S17:48 0:00 pipe -n
> cyrus -t unix flags=R user=cyrus argv=/usr/cyrus/bin/deliver -e -m
> ${extension} ${user}
> postfix 2141 0.0 1.6 1884 756 ?S17:48 0:00 pipe -n
> cyrus -t unix flags=R user=cyrus argv=/usr/cyrus/bin/deliver -e -m
> ${extension} ${user}
> cyrus 2142 0.0 1.6 2272 776 ?S17:48 0:00
> /usr/cyrus/bin/deliver -e -m root
> postfix 2143 0.0 1.6 1884 756 ?S17:48 0:00 pipe -n
> cyrus -t unix flags=R user=cyrus argv=/usr/cyrus/bin/deliver -e -m
> ${extension} ${user}
> cyrus 2144 0.0 1.6 2272 776 ?S17:48 0:00
> /usr/cyrus/bin/deliver -e -m root
> postfix 2145 0.0 1.6 1884 756 ?S17:48 0:00 pipe -n
> cyrus -t unix flags=R user=cyrus argv=/usr/cyrus/bin/deliver -e -m
> ${extension} ${user}
> cyrus 2146 0.0 1.6 2272 776 ?S17:48 0:00
> /usr/cyrus/bin/deliver -e -m root
> postfix 2147 0.0 1.6 1884 756 ?S17:48 0:00 pipe -n
> cyrus -t unix flags=R user=cyrus argv=/usr/cyrus/bin/deliver -e -m
> ${extension} ${user}
> cyrus 2148 0.0 1.6 2272 776 ?S17:48 0:00
> /usr/cyrus/bin/deliver -e -m root
> cyrus 2149 0.0 1.6 2272 776 ?S17:48 0:00
> /usr/cyrus/bin/deliver -e -m root
> root 2163 0.0 1.0 1396 480 pts/0S17:55 0:00 grep cyrus
>
>
>
>
>>SIMICRO - Manou RABARY wrote:
>>
>>
>>>Hello,
>>>When I try to telnet my server in distance or from localhost, it says
>>>immediately 'connection closed by foreign host'. I try with a sandard
>>>mail clients but it says that server is not responding.
>>>My /var/log/imapd.log says nothing. The same for /var/log/messages and
>>>/var/log/mail.log. Port 143 is open.
>>>
>>>Is there some proces frozen or killed or not started?
>>>Ideas?
>>>
>>>Thanks in advance
>>>Manou
>>>
>>>
>
--
=G=
-=* I'm sorry if doing things correctly offends you. *=-
Re: Telnet: Connection closed by foreign host
Do you have a firewall in place? -- =G= -=* I'm sorry if doing things correctly offends you. *=- SIMICRO - Manou RABARY wrote: > Hello, > When I try to telnet my server in distance or from localhost, it says > immediately 'connection closed by foreign host'. I try with a sandard > mail clients but it says that server is not responding. > My /var/log/imapd.log says nothing. The same for /var/log/messages and > /var/log/mail.log. Port 143 is open. > > Is there some proces frozen or killed or not started? > Ideas? > > Thanks in advance > Manou > > -- =G= -=* I'm sorry if doing things correctly offends you. *=-
Re: Want sieve but don't want delivery duplicate supression
It's been a while since I had to do this and I'm not sure cyrus 2.0 supports this but if you want to share a folder amongst users just create a mailbox called bb+somename (you may not need the bb+) and set the acls for to allow whichever users you want to view the mailbox. Set up a sieve filter to dump any shared mail there. This folder will show up under the requisite users as another folder (a la exchange folders) -- =G= -=* I'm sorry if doing things correctly offends you. *=- Olaf Fr±czyk wrote: > On 2002.03.05 02:21:15 +0100 Sam Roberts wrote: > >> Can't you see if it's to you, and do a keep? > > > But it's not good for threading messages: > With this behaviour in mailboxes for group1 and group2 are no messages > for me. So I have to jump between mailboxes. It's not nice. > > And if I want to share this mailbox with other users, I have problem again: > They don't see mails which were addressed to me. > > If sieve could duplicate messages: put 1 message into two or three > mailboxes it could solve my problems. But it's not nice solution. > > Regards, > > Olaf > > > > >
Re: Postfix & cyrus
Your master.cf file should actually have an entry like the following:
cyrus unix - n n - - pipe
flags=R user=cyrus argv=/usr/cyrus/bin/deliver -e -m ${extension} ${user}
cyrdeliver has been deprecated in favor of deliver.
--
=G=
-=* I'm sorry if doing things correctly offends you. *=-
Manou Rabary wrote:
> Hi all,
> I use cyrus imap with postfix.
> I saw in a documentation ;-) how to use postfix to transport mail:
>
> insert in /etc/postfix/master.cf the following line:
>
>
> cyrus unix - n n - - pipe
> flags=R user=cyrus argv=/usr/sbin/cyrdeliver -e -m ${extension}
> ${user}
>
> But I can't locate cyrdeliver.
>
> In /var/log/mail.log, I have:
>
> Mar 4 16:20:38 rajako pipe[15758]: fatal: pipe_comand: execvp
> /usr/sbin/cyrdeliver: No such file or directory
> Mar 4 16:20:39 rajako postfix/pipe[15757]: 335C4C604:
> to=<[EMAIL PROTECTED]>, relay=cyrus, delay=3, status=bounced
> (Command died with status 1: "/usr/sbin/cyrdeliver")
>
>
> How can I solve the problem? What file to use instead of cyrdeliver?
>
> Thanx in advance
> Manou
>
Re: Problems with sieve and cyradm
I'm sure you'd rather have a real response instead of just a
regurgitation of what was said before...heheheheh.
I finally managed to get my sieve filter to work by changing my main.cf.
I set mailbox_transport=lmtp:unix:/var/imap/socket/lmtp (verify that
your lmtp socket is there or you can set it to
lmtp:localhost:lmtp)(however if you choose to connect via tcp you'll
need to make sure postfix is set up to use sasl; check out the
SASL_README for postfix)
One thing I found out on my own. After adding your sieve script using
installsieve; ie, installsieve -u username -i myscript.script
mail.domain.com, you then need to make it your active script by the
following command: installsieve -u username -a myscript mail.domain.com
I had it working all day today but hadn't actually activated my script.
Hope this helps.
--
=G=
-=* I'm sorry if doing things correctly offends you. *=-
Mike McLean wrote:
> On Fri, 2002-03-01 at 14:33, Galen Johnson wrote:
>
>>I'm having similar issues with sieve (aside from having trouble finding
>>any good docs for it {aside from reading the rfc which is currently in
>>front of me}). My research has turned up that you have to be using lmtp
>>in order for sieve to work properly. I have to look into setting tht up
>>properly in postfix this weekend (looks like fun).
>>
>>
>
> I guess I'll have to look into that.
>
>
>>As far as the cyadm piece goes...it looks like you may have a mail user
>>called mailadmin as well. I made sure that my mail admin user was
>>unique. Won't guarantee that this is actually the problem.
>>
>
> I figured this one out. I had to change what imap listens on in
> cyrus.com so it on localhost instead of the external interface. For
> some reason when it's set to just listen="imap" it only listens on the
> internal interface, and if I specify listen="[192.168.0.86]:imap" it'll
> listen on the external interface. So I must see if there's a way for it
> to listen on both
>
> Mike
>
>
>>--
>>=G=
>>
>>-=* I'm sorry if doing things correctly offends you. *=-
>>
>>Mike McLean wrote:
>>
>>>Hi,
>>>
>>>I've managed to get cyrus-imapd to work somewhat. I'm using postfix +
>>>cyrus-imapd on my freebsd 4.5 -stable system, from the ports tree. I
>>>managed to get everything configured so that cyrus handles local
>>>delivery and I can connect to it from an imap client on another box.
>>>
>>>However, I'm attempting to setup a sieve script. I followed an example
>>>and created the following. loaded it with sieveshell, and activated
>>>it. But nothing is getting filtered.
>>>
>>>require "fileinto";
>>>if header :is "X-Mailinglist" "flightgear-devel" {
>>>fileinto "INBOX.Listen.flightgear-devel";}
>>>elsif header :contains "Mailing-List" "allegro" {
>>>fileinto "INBOX.Listen.Allegro";}
>>>elsif header :contains "List-Id" "[EMAIL PROTECTED]" {
>>>fileinto "INBOX.Listen.Bind9-Users";}
>>>elsif header :contains "Mailing-list" "dri-user"{
>>>fileinto "INBOX.Listen.DRI-User";}
>>>elsif header :contains "From" "[EMAIL PROTECTED]"{
>>>fileinto "INBOX.ME";}
>>>else {
>>> fileinto "INBOX";
>>> }
>>>
>>>My other problem is that although I was able to use cyradm -u mailadmin
>>>localhost earlier to log in and add users, mailboxes and such. Now I
>>>can't
>>>
>>>I get the following:
>>>
>>>su-2.05a# cyradm -u mailadmin libolt.net
>>>Please enter your password:
>>>IMAP Password:
>>> LOGIN failed at
>>>/usr/local/lib/perl5/site_perl/5.005/i386-freebsd/Cyrus/IMAP/Admin.pm
>>>line 78
>>>cyradm: cannot authenticate to server with as mailadmin
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>
>
>
Re: Problems with sieve and cyradm
Mike McLean wrote:
> On Fri, 2002-03-01 at 14:33, Galen Johnson wrote:
>
>>I'm having similar issues with sieve (aside from having trouble finding
>>any good docs for it {aside from reading the rfc which is currently in
>>front of me}). My research has turned up that you have to be using lmtp
>>in order for sieve to work properly. I have to look into setting tht up
>>properly in postfix this weekend (looks like fun).
>>
>>
>
> I guess I'll have to look into that.
>
>
>>As far as the cyadm piece goes...it looks like you may have a mail user
>>called mailadmin as well. I made sure that my mail admin user was
>>unique. Won't guarantee that this is actually the problem.
>>
>
> I figured this one out. I had to change what imap listens on in
> cyrus.com so it on localhost instead of the external interface. For
> some reason when it's set to just listen="imap" it only listens on the
> internal interface, and if I specify listen="[192.168.0.86]:imap" it'll
> listen on the external interface. So I must see if there's a way for it
> to listen on both
>
> Mike
>
>
>>--
>>=G=
>>
>>-=* I'm sorry if doing things correctly offends you. *=-
>>
>>Mike McLean wrote:
>>
>>>Hi,
>>>
>>>I've managed to get cyrus-imapd to work somewhat. I'm using postfix +
>>>cyrus-imapd on my freebsd 4.5 -stable system, from the ports tree. I
>>>managed to get everything configured so that cyrus handles local
>>>delivery and I can connect to it from an imap client on another box.
>>>
>>>However, I'm attempting to setup a sieve script. I followed an example
>>>and created the following. loaded it with sieveshell, and activated
>>>it. But nothing is getting filtered.
>>>
>>>require "fileinto";
>>>if header :is "X-Mailinglist" "flightgear-devel" {
>>>fileinto "INBOX.Listen.flightgear-devel";}
>>>elsif header :contains "Mailing-List" "allegro" {
>>>fileinto "INBOX.Listen.Allegro";}
>>>elsif header :contains "List-Id" "[EMAIL PROTECTED]" {
>>>fileinto "INBOX.Listen.Bind9-Users";}
>>>elsif header :contains "Mailing-list" "dri-user"{
>>>fileinto "INBOX.Listen.DRI-User";}
>>>elsif header :contains "From" "[EMAIL PROTECTED]"{
>>>fileinto "INBOX.ME";}
>>>else {
>>> fileinto "INBOX";
>>> }
>>>
>>>My other problem is that although I was able to use cyradm -u mailadmin
>>>localhost earlier to log in and add users, mailboxes and such. Now I
>>>can't
>>>
>>>I get the following:
>>>
>>>su-2.05a# cyradm -u mailadmin libolt.net
>>>Please enter your password:
>>>IMAP Password:
>>> LOGIN failed at
>>>/usr/local/lib/perl5/site_perl/5.005/i386-freebsd/Cyrus/IMAP/Admin.pm
>>>line 78
>>>cyradm: cannot authenticate to server with as mailadmin
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>
>
>
--
=G=
-=* I'm sorry if doing things correctly offends you. *=-
Re: Problems with sieve and cyradm
I'm having similar issues with sieve (aside from having trouble finding
any good docs for it {aside from reading the rfc which is currently in
front of me}). My research has turned up that you have to be using lmtp
in order for sieve to work properly. I have to look into setting tht up
properly in postfix this weekend (looks like fun).
As far as the cyadm piece goes...it looks like you may have a mail user
called mailadmin as well. I made sure that my mail admin user was
unique. Won't guarantee that this is actually the problem.
--
=G=
-=* I'm sorry if doing things correctly offends you. *=-
Mike McLean wrote:
> Hi,
>
> I've managed to get cyrus-imapd to work somewhat. I'm using postfix +
> cyrus-imapd on my freebsd 4.5 -stable system, from the ports tree. I
> managed to get everything configured so that cyrus handles local
> delivery and I can connect to it from an imap client on another box.
>
> However, I'm attempting to setup a sieve script. I followed an example
> and created the following. loaded it with sieveshell, and activated
> it. But nothing is getting filtered.
>
> require "fileinto";
> if header :is "X-Mailinglist" "flightgear-devel" {
> fileinto "INBOX.Listen.flightgear-devel";}
> elsif header :contains "Mailing-List" "allegro" {
> fileinto "INBOX.Listen.Allegro";}
> elsif header :contains "List-Id" "[EMAIL PROTECTED]" {
> fileinto "INBOX.Listen.Bind9-Users";}
> elsif header :contains "Mailing-list" "dri-user"{
> fileinto "INBOX.Listen.DRI-User";}
> elsif header :contains "From" "[EMAIL PROTECTED]"{
> fileinto "INBOX.ME";}
> else {
> fileinto "INBOX";
> }
>
> My other problem is that although I was able to use cyradm -u mailadmin
> localhost earlier to log in and add users, mailboxes and such. Now I
> can't
>
> I get the following:
>
> su-2.05a# cyradm -u mailadmin libolt.net
> Please enter your password:
> IMAP Password:
> LOGIN failed at
> /usr/local/lib/perl5/site_perl/5.005/i386-freebsd/Cyrus/IMAP/Admin.pm
> line 78
> cyradm: cannot authenticate to server with as mailadmin
>
>
>
>
Re: newbie: cyradm fails
Take a closer look at where you indicate that your Cyrus/IMAP/Shell.pm is located. It's showing as /usr/local/local, not /usr/local. You either need to provide a link by doing something simliar to 'cd /usr/local/lib/perl/5.6.1;ln -s /usr/local/local/lib/perl/5.6.1/Cyrus'. That would be the easy fix...the better fix is to makje sure perl 5.6.1 is installed where it's supposed to be and then verify that when you configured cyrus that you pointed it to the proper place. Or, you can edit where perl looks for the include files by default and add your /usr/local/local/lib/perl/5.6.1 path to that (don't recall where that is just off the top of my head). -- =G= -=* I'm sorry if doing things correctly offends you. *=- Manou Rabary wrote: > Hello, > I have problem to run cyradm. When I run the command the following > message appears: > > Can't locate Cyrus/IMAP/Shell.pm in @INC (@INC contains: > /usr/local/lib/perl/5.6.1 /usr/local/share/perl/5.6.1 /usr/lib/perl5 > /usr/share/perl5 /usr/lib/perl/5.6.1 /usr/share/perl/5.6.1 > /usr/local/lib/site_perl .). > BEGIN failed--compilation aborted. > > I use Linux Debian 2.2.19 > Perl packages installed in the system > ii libdbi-perl1.13-3 > ii perl 5.6.1-7 > ii perl-5.005 6.3 > ii perl-5.005-bas 6.3 > ii perl-base 5.6.1-7 > ii perl-modules 5.6.1-7 > > I found Shell.pm in teh directory: > /usr/local/local/lib/perl/5.6.1/Cyrus/IMAP/Shell.pm > /usr/share/perl/5.6.1/Shell.pm > > > Can someone help me? Have I to add other .deb or hack within scripts?... > > Thanks in advance > > Manou > >
