hard links
Hi, I'm trying to implement delivering by hard links e-mails to multiple mailboxes but I didn't succeded. I've made an every.aliases file and I have in /etc/aliases every: :include:/etc/mail/every.aliases. Now when I'm sending an e-mail to [EMAIL PROTECTED] I receive the e-mail in every mailboxes and I can't see any hardlinks. I put in imapd.conf singleinstancestore: yes. In mailer definition I have : Mcyrus, P=[IPC], F=lsDFMnqA5@/:|SmXz, E=\r\n, S=EnvFromL, R=EnvToL/HdrToL, T=DNS/RFC822/X-Unix, A=FILE /var/imap/socket/lmtp TIA, Marius
Re: graphing snmp information
On Mon, 19 Nov 2001, Lawrence Greenfield wrote: > You can also snmpwalk public .1.3.6.1.4.1.3.6 > and that should get you the same information. Oh, it will. But I am packaging the thing, and I want to do it as well as it can be done. For an example of what I mean by this, I am testing my patches that will properly daemonize master (pidfile locking, setsid, and all that) to lessen the headaches when starting master from something else than init. Once I have tested such patches enough, I will post the patches to this ML and to the bug-reporting address. Then I will try to add "process overlording" init-style to master :P Right now, my beta packages are distributing a "stand alone" patched cyrusMasterMIB file that has OIDs instead of cmuCyrus and enterprise.cmu. As long as you guys update the MIB file you're distributing should those OIDs change, I will notice it and do the same for the Debian package. > business. I'll consider how to correctly distribute the > CYRUS-MASTER-MIB so that it stays in sync with the cmu mib. Thanks. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
Re: [POLL] Cyrus v2.1 and SASL v2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 19 Nov 2001, Ken Murchison wrote: > Cyrus users, > > We are getting close to releasing Cyrus v2.1 (yeah, I know I've said > this a bunch of times already) and we are leaning towards making it > dependent on SASL v2. We would like to do this for a number of reasons: > > 1. Take advantage of the benefits of SASL v2 (improvements in memory > management, support for additional plugin types, simplified database > support, and improved error reporting). sounds very good! > 2. Take the lead in SASLv2 migration. Hopefully Sendmail, OpenLDAP, etc > would soon follow. i think they will follow soon! > 3. SASL v2 and v1.5.x can peacefully co-exist on the same system. I've > been running Sendmail 8.12.1/SASL 1.5.24 and Cyrus 2.1 CVS/SASL 2.0.4 > CVS for weeks without any problems. thats right. no problems with this solution. > 4. We would no longer have to maintain two Cyrus v2.1 source branches > (developer benefit). :) > 5. It WILL happen eventually, so why not now? the time is NOW. > The biggest (only?) downside for existing installations is that any > secrets stored in sasldb would have to migrated to the new format. This > will require resetting all of the users passwords because they can not > be extracted from the old sasldb (unless you have been using my APOP > patch). As stated above, this will eventually have to be done, so why > not now? again: the time is NOW. > We would like to get as much feedback (pro and con) on this as possible > before we make a final decision. PRO > Thanks, > Ken i hope that the new Cyrus_v2.1 release will depend on SASL_v2. greets, Joerg - -- _/_/_/_/ _/_/_/ _/ _/ _/_/ Joerg Pulz _/ _/_/ _/_/ _/_/ _/ _/ TU Muenchen _/ _/_/ _/ _/_/ _/ _/ ZBE-FRM-II _/_/_/ _/_/_/ _/ _/ _/ _/_/_/ Lichtenbergstrasse 1 _/ _/_/ _/ _/_/ 85747 Garching _/ _/ _/ _/ _/ _/ Tel.: +49 (0)89-289-14708 _/ _/_/ _/ _/ _/_/_/_/ Fax : +49 (0)89-289-14666 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7+kqPSPOsGF+KA+MRAhPfAJ9z3wp8DJ5sjVxiz4TblJ3Nw9JRBgCgp9vA LJKZsSqicmSjQmvebbrdFx8= =qOkG -END PGP SIGNATURE-
Re: Restoring backup
On Monday, November 19, 2001 09:38:52 AM +0100 Francesc Guasch Ortiz <[EMAIL PROTECTED]> wrote: +-- | I have a solaris 2.6 box with cyrus-imapd 1.5.19. | Someone removed all the files of an imap folder. The folder | has subfolders that are still there and available. | | I restored the backup but now the messages can't be | retrieved. Netscape communicator tells me there are | some messages there but when I try to read it shows | nothing. | The mailboxes file didn't had the folder, so I | went to cyradm and did a create mailbox. | | I tried to do reconstruct and reconstruct -r | | I tried to unsubscribe from the client and subscribe | again. | | What else can I try ? | | Is there some document I have missed that explains how | to restore a backup ? +-X8 What you have done is correct, you shouldn't have removed the cyrus.* files but that shouldn't matter that much. My experience is that netscape is probably at fault, remove the cache files under ns_imap and try again. If you can try using a more reliable imap client. /Michael -- This space intentionally left non-blank.
Re: Second vacation patch for cyrus-imapd-2.0.16
Quoting Gary Mills <[EMAIL PROTECTED]>: > The previous patch that I submitted made sure that the envelope > recipient address of the message that triggers a vacation response had > the same domain name as the one used by the MTA. Today's patch > ensures that this same address will be used as the originator of the > response message. Taking it from the first additional address is not > a good idea, since the additional addresses are supplied by the user, > and may be incorrect. The result would be that the response message > would be unreplyable. The one with the domain specified by the > administrator is more likely to be correct. > > The patch is for sieve/script.c. This has already been fixed in CVS. I uses whichever address (either envelope or :addresses) matches in th eone in the to/cc/bcc header. Ken -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
problem with vacation
Hello, i have a problem with vacation. I have to use the :addresses parameter and it seems, that this parameter is case sensitive, which does not make sense to me. Any ideas or solutions? Olaf Dreyer
Re: [POLL] Cyrus v2.1 and SASL v2
I whole heartedly support moving forward on SASLv2. It has to be done at some point, and the sooner some momentum is generated, the sooner other groups (sendmail, OpenLDAP have been mentioned) whille make the transition. Regarding complaints from those who don't want to mess with different software systems using different versions of SASL... DONT! Immediate upgrades to the latest version are not compulsory. How many recent messages start with "I'm running Cyrus 1.6.x on ...". If you have to wait for sendmail and OpenLDAP to catch up, don't worry, they will. If there are any compelling, non SASL updates in 2.1 that you just must have, I'm sure they can be back ported to 2.0.x. As far as I'm concerned, the improvements of SASLv2 ARE the compelling reason to upgrade. Cheers Chris
Sieve error: unexpected operator
I have come across this error whilest trying to get sieve to run properly.
This is using FreeBsd 4.4, cyrus 2.0.16 and the timseived which is built
with this. Has anybody seen this before or can diagnose the problem? This
error will also appear when a non-existent script is fed to test as I did
below with the script "noscript" which doesn't exist on the sieve server.
The entries "default" and "example1.script" exist in
/var/imap/sieve/a/arc and are owned by cyrus group=mail
/var/spool/imap/user/arc/36. is owned by cyrus group=mail
scout# sieveshell -u arc localhost
connecting to localhost
Please enter your password: <--- echoes password (Bad)
> list
example1 <- active script
> get example1
#Example from rfc 3028 pg 33
require ["fileinto"];
if header :contains "From" "[EMAIL PROTECTED]" {
fileinto "bsd-commit"; }
> list
example1 <- active script
> quit
scout# test /var/spool/imap/user/arc/36. /var/imap/sieve/a/arc/example1
test: /var/imap/sieve/a/arc/example1: unexpected operator
scout# test /var/spool/imap/user/arc/36. /var/imap/sieve/a/arc/default
test: /var/imap/sieve/a/arc/default: unexpected operator
scout# test /var/spool/imap/user/arc/36. /var/imap/sieve/a/arc/noscript
test: /var/imap/sieve/a/arc/noscript: unexpected operator
scout#
Thanks
Cheers:
-arc
Arley Carter[EMAIL PROTECTED]
Tradewinds Technologies, Inc. www.twinds.com
Winston-Salem, NC USA Network Engineering & Security
336-817-9554
Re: Sieve error: unexpected operator
You're running the wrong "test" command. You're running the standard
Unix test command instead of the (badly named) Cyrus sieve test
command.
Larry
Date: Tue, 20 Nov 2001 11:49:56 -0500 (EST)
From: Arley Carter <[EMAIL PROTECTED]>
cc: Ken Murchison <[EMAIL PROTECTED]>, Lawrence Greenfield <[EMAIL PROTECTED]>
I have come across this error whilest trying to get sieve to run properly.
This is using FreeBsd 4.4, cyrus 2.0.16 and the timseived which is built
with this. Has anybody seen this before or can diagnose the problem? This
error will also appear when a non-existent script is fed to test as I did
below with the script "noscript" which doesn't exist on the sieve server.
The entries "default" and "example1.script" exist in
/var/imap/sieve/a/arc and are owned by cyrus group=mail
/var/spool/imap/user/arc/36. is owned by cyrus group=mail
scout# sieveshell -u arc localhost
connecting to localhost
Please enter your password: <--- echoes password (Bad)
> list
example1 <- active script
> get example1
#Example from rfc 3028 pg 33
require ["fileinto"];
if header :contains "From" "[EMAIL PROTECTED]" {
fileinto "bsd-commit"; }
> list
example1 <- active script
> quit
scout# test /var/spool/imap/user/arc/36. /var/imap/sieve/a/arc/example1
test: /var/imap/sieve/a/arc/example1: unexpected operator
scout# test /var/spool/imap/user/arc/36. /var/imap/sieve/a/arc/default
test: /var/imap/sieve/a/arc/default: unexpected operator
scout# test /var/spool/imap/user/arc/36. /var/imap/sieve/a/arc/noscript
test: /var/imap/sieve/a/arc/noscript: unexpected operator
scout#
Thanks
Cheers:
-arc
Arley Carter [EMAIL PROTECTED]
Tradewinds Technologies, Inc.www.twinds.com
Winston-Salem, NC USA Network Engineering & Security
336-817-9554
"Right Way" to track mailing-lists
Hi, I'm setting up a IMAP server, doing my installation of the 2.x series where I'll be tracking mailing lists. With the 1.6 series all I had to do was to call deliver such that it would deliver a message to the correct folder. With the 2.x series there are advantages to using lmtp for deliveries instead, avoiding the extra fork of the deliver process. So I'm wondering if there's any RightWay (tm) way to deliver mailing list messages to a shared folder? I could always subscribe a user to the mailing list, then allow access from the others to his folders, but that'll show up as user.mailinglist in the folderviews of the other users, what I want is for the mailing list folder to be named archive.mailinglist. Anyone with strong views on the issue? Thanks, Terje Elde
Re: Sieve error: unexpected operator
Ahh... I see said the blind man. Thanks. I had not thought of that. Cheers: -arc On Tue, 20 Nov 2001, Lawrence Greenfield wrote: > Date: Tue, 20 Nov 2001 11:56:24 -0500 > From: Lawrence Greenfield <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED], Arley Carter <[EMAIL PROTECTED]> > Cc: Ken Murchison <[EMAIL PROTECTED]> > Subject: Re: Sieve error: unexpected operator > > You're running the wrong "test" command. You're running the standard > Unix test command instead of the (badly named) Cyrus sieve test > command.
Re: "Right Way" to track mailing-lists
On 11/20/01 06:36 PM, Terje Elde sat at the `puter and typed: > Hi, > > I'm setting up a IMAP server, doing my installation of the 2.x series where > I'll be tracking mailing lists. > > With the 1.6 series all I had to do was to call deliver such that it would > deliver a message to the correct folder. With the 2.x series there are > advantages to using lmtp for deliveries instead, avoiding the extra fork of > the deliver process. So I'm wondering if there's any RightWay (tm) way to > deliver mailing list messages to a shared folder? > > > I could always subscribe a user to the mailing list, then allow access from > the others to his folders, but that'll show up as user.mailinglist in the > folderviews of the other users, what I want is for the mailing list folder to > be named archive.mailinglist. > > Anyone with strong views on the issue? > > Thanks, > Terje Elde I don't know exactly what you mean by 'tracking' mailing lists, but it sounds like you are setting up more of a mailing list bulletin board. I subscribe to about 9 different lists myself, and I simply create a folder for each (as well as a folder for each account I suck down from other servers (work, pop servers, etc.). For each list, I subscribe as leblanc+@keyslapper.org, and when the mail comes, sendmail calls procmail for filtering, which then calls deliver to drop it in the appropriate folder. Of course, if you're not using procmail, you can simply have sendmail call deliver the same way. Quite easy, really. So, I don't have to worry about creating a different account for each list then worrying about client configuration or folder permissions. Of course, my client makes it very easy to be whoever I want based on the folder I am sending mail from, but your users may not want to or be able to use it (mutt on *nix). If a list is open, setting up a bulletin board may be what you want, but for closed lists, your users won't be able to post unless they subscribe themselves. In which case, why bother with the board? I don't know if any of this helps, but I thought it might get your creative juices flowing if you had some ideas. HTH Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ QOTD: "I'm on a seafood diet -- I see food and I eat it." msg04582/pgp0.pgp Description: PGP signature
Re: [POLL] Cyrus v2.1 and SASL v2
> Regarding complaints from those who don't want to mess with different > software systems using different versions of SASL... DONT! Immediate > upgrades to the latest version are not compulsory. How many recent > messages start with "I'm running Cyrus 1.6.x on ...". If you have to > wait for sendmail and OpenLDAP to catch up, don't worry, they will. > I'd like to look at porting Postfix to SASL2 at some time shortly after Cyrus for SASL 2 comes out. Is there a porters guide someplace, or can someone post a summary of required steps?
imapmigrate-0.26
Hello, I'm trying to use the imapmigrate script against a UW-IMAP server to my cyrus server. The script is pulling the whole directory "mail/" from the old server. Is there a way to just have it pull the items under "mail/" so that my Cyrus folders don't look like "INBOX->mail->sent-mail". Also it seems to be pulling all of the stuff in my old home directory (ie -> file1, profile, history). Thanks, Harry Hoffman [EMAIL PROTECTED]
OT? (was re: [POLL] Cyrus v2.1 and SASL v2)
While we are talking about taking cyrus and SASL to the next level, is there any plan to remove the dependance that Cyrus has on UNIX groups for group based ACL's? - Original Message - From: "Jeremy Howard" <[EMAIL PROTECTED]> To: "Christopher D. Audley" <[EMAIL PROTECTED]>; "Cyrus Mailing List" <[EMAIL PROTECTED]> Sent: Tuesday, November 20, 2001 2:16 PM Subject: Re: [POLL] Cyrus v2.1 and SASL v2 > > Regarding complaints from those who don't want to mess with different > > software systems using different versions of SASL... DONT! Immediate > > upgrades to the latest version are not compulsory. How many recent > > messages start with "I'm running Cyrus 1.6.x on ...". If you have to > > wait for sendmail and OpenLDAP to catch up, don't worry, they will. > > > I'd like to look at porting Postfix to SASL2 at some time shortly after > Cyrus for SASL 2 comes out. Is there a porters guide someplace, or can > someone post a summary of required steps? > > >
Re: [POLL] Cyrus v2.1 and SASL v2
On Wed, 21 Nov 2001, Jeremy Howard wrote: > I'd like to look at porting Postfix to SASL2 at some time shortly after > Cyrus for SASL 2 comes out. Is there a porters guide someplace, or can > someone post a summary of required steps? There's a porters guide in the current CVS. Offhand, I'm not sure if it's in the most recent release or not. -Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski | Andrew Systems Group * Cyert Hall 235 * 412-CMU-TREK | Cyrus SASL Developer, /usr/contributed Gatekeeper
[no subject]
remove
Re: OT? (was re: [POLL] Cyrus v2.1 and SASL v2)
From: "Tim Pushor" <[EMAIL PROTECTED]> Date: Tue, 20 Nov 2001 14:38:31 -0700 While we are talking about taking cyrus and SASL to the next level, is there any plan to remove the dependance that Cyrus has on UNIX groups for group based ACL's? Well, it doesn't. It can also use the AFS PTS server for groups. We (CMU) haven't written anything else because we haven't yet needed anything else. I can easily imagine an LDAP authorization module working much the same way the PTS authorization module works, and it's something we'll probably look into doing, but only when we really feel the need. It shouldn't be all that hard for someone else to write such an LDAP authorization module. Larry
cvs
All that talk about cyrus 2.1 and sasl v2 made me want to take a look at it ... webcvs lists just too many branches to choose from :) so which one do i pick? imapd-sasl-v2(-base) or cyrus-2_1 ? -- Jure Pecar
Re: cvs
On Wed, 21 Nov 2001, Jure Pecar wrote: > All that talk about cyrus 2.1 and sasl v2 made me want to take a look > at it ... webcvs lists just too many branches to choose from :) so > which one do i pick? imapd-sasl-v2(-base) or cyrus-2_1 ? You'll want the imapd-sasl-v2 branch from the cyrus tree, and sasl-v2-rjs3 from the sasl tree. If you want what is currently slated to become Cyrus 2.1 without the SASLv2 integration, that's just on the HEAD of the tree. It's important to note that the last merge with the head of the imapd-sasl-v2 tree was a few weeks ago, so it's not entirely in sync with non-sasl-related changes. -Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski | Andrew Systems Group * Cyert Hall 235 * 412-CMU-TREK | Cyrus SASL Developer, /usr/contributed Gatekeeper
Re: Restoring backup
Hi Steven, I am not really sure, so maybe someone else can speak to this. The mailboxes file in 1.x is is just a text file, so you can edit it manually. I would have to look in the reconstruct code to see if there is anything there to recreate the mailboxes file (I don't think there is)If you want to have it match the existing directory structure, you could probably write a perl or shell script that would recursively scan the directories and place entries in the mailboxes file for each directory with some assumed permisions. Since the mailboxes file is "The" database for cyrus mailboxes, I don't know if you can really generate a fresh copy without making a lot of assumptions. I assigned someone here the task of putting together some scripts to verify the mailboxes file versus the /var/spool/imap directory structure vs the seen, subscription and quota files so that I could spot any discrepancies, if we ever get it working, I will send it to the list. Anyone else have a better answer? Thanks, John "Steven J. Sobol" wrote: > On Mon, 19 Nov 2001, John Wade wrote: > > > If it is an ACL problem, ACL's are stored in the mailboxes file. > > Take a look at the lines for the user's mailboxes, they should look > > somehing like this: > > I want to generate a fresh copy of that file. How do I do it, using > 1.6.*? (sorry, I used to know but I forgot) > > -- > JustThe.net LLC - Steve "Web Dude" Sobol, CTO - [EMAIL PROTECTED] > > In another world it may be true that "Information wants to be free." > Directory Assistance, or lack thereof, is a profit center here and now. >- John Myers, speaking in comp.dcom.telecom
How to setup mail forward in cyrus postfix setup.
I have Cyrus 2.0.9 and postfix running. everything is working fine, but I am trying to figure out how to set up mil aliases in it to forward an info user to me the system administrator. any ideas? -- Richmond Dyes IS Director Monroe Community Hospital 435 East Henrietta Road Rochester NY 14609 Phone: 716.760.6213
Re: OT? (was re: [POLL] Cyrus v2.1 and SASL v2)
I actually have some code to do LDAP based groups. It is not excessively flexible, because I don't really know LDAP. But I'm sure it could be easily adapted to take the search constraints as a configuration option. Is anyone interested in this? Lawrence Greenfield wrote: >From: "Tim Pushor" <[EMAIL PROTECTED]> >Date: Tue, 20 Nov 2001 14:38:31 -0700 > >While we are talking about taking cyrus and SASL to the next level, is there >any plan to remove the dependance that Cyrus has on UNIX groups for group >based ACL's? > > Well, it doesn't. It can also use the AFS PTS server for groups. > We (CMU) haven't written anything else because we haven't yet needed > anything else. I can easily imagine an LDAP authorization module > working much the same way the PTS authorization module works, and it's > something we'll probably look into doing, but only when we really feel > the need. > > It shouldn't be all that hard for someone else to write such an LDAP > authorization module. > > Larry > > >
Re: How to setup mail forward in cyrus postfix setup.
> On Tue, 20 Nov 2001 16:15:51 -0500, > Richmond Dyes <[EMAIL PROTECTED]> (rd) writes: rd> I have Cyrus 2.0.9 and postfix running. everything is working fine, but rd> I am trying to figure out how to set up mil aliases in it to forward an rd> info user to me the system administrator. any ideas? This has been discussed some on postfix-users. Actually, it comes up from time to time. Depending on how you're channeling mail to Cyrus, you might need to use a virtual map for some of the redirecting. -- Amos
Re: "Right Way" to track mailing-lists
> On Tue, 20 Nov 2001 18:36:59 +0100, > Terje Elde <[EMAIL PROTECTED]> (te) writes: te> With the 1.6 series all I had to do was to call deliver such that it would te> deliver a message to the correct folder. With the 2.x series there are te> advantages to using lmtp for deliveries instead, avoiding the extra fork of te> the deliver process. So I'm wondering if there's any RightWay (tm) way to te> deliver mailing list messages to a shared folder? I don't know if I've ever seen a manifesto as to the RightWay for doing this. This is the current hack we've arranged. Before we switched to the altnamespace we had all our shared folders under a "bb." prefix. Now we've moved all these folders up a level. To send mail to such a folder, just put a "+" before the address. If you don't like that, see the "postuser" setting in imapd.conf. (When we adjusted to the altnamespace I overlooked this "postuser" setting, otherwise we might have used it.) Suppose we created a Listar (or now eCartis) list of mylist. If we created a shared folder for it, it would be "mylist". So the cyradm command would just be: cm mylist shared In this example "shared" might be a partition for this folder. Continuing, allow posting to it: sam mylist anyone p If you're using LMTP-AUTH then you might be able to do something better here, but this opens another can of worms because not all MTA will pass the AUTH from SMTP over to LMTP. Anyway, if you want this folder to get the mail from the list, just add it to the list. Since we use Listar, the users entry might be: +mylist@domain : |PROTECTED|HIDDEN| Some lists we auto-generate on a daily basis so our code skips over entries that are listed as PROTECTED. Actually, some of the features of Listar is part of the reason we chose it as it made it easy to manipulate for out environment. If you want to block direct email to the shared folder and only allow the mail from the list, you might have to do something tricky. When we were using Sendmail a couple of years back this was really problematic because the maps applied to both port 25 mail and local mail. One of the reasons why I liked Postfix is because blocks on port 25 do not necessarily apply to blocks on local "client" mail. Consequently, we can block incoming mail to the address "+mylist@domain" and yet Listar can still direct mail to that address. Well, I said it was a hack, but at least it seems to have worked out fairly well. Now if only we could get Sieve scripts to work on shared folders. :-P (Actually, I wouldn't use Sieve for these folders that mirror a list, but it would still be nice to have. We have plenty of shared folders were this would be really handy.) -- Amos
Postfix-Cyrus delivery bug
Hi All, I have a mail server setup with Cyrus 2.0.16 /Postfix snapshot-20010808 with LDAP user database in RedHat 7.1. All works fine. But when a user receives an email with lot of addresses in the TO field, users then multiple copies (50-60) of that same email. I gave some investigation ang found when the email header size is bytes 2,427 mail get's delived correctly, but if it's 2,428 (one character more) above error occurs. (I'm not sure whether my header sizes are right, but one character difference is correct) Below are my log output maillog: Nov 21 12:59:32 Pirana postfix/qmgr[21575]: 97003153D5: from=<[EMAIL PROTECTED]>, size=3316, nrcpt=40 (queue active) Nov 21 12:59:32 Pirana postfix/pipe[29416]: 97003153D5: to=<[EMAIL PROTECTED]>, relay=cyrus, delay=0, status=deferred (temporary failure) imapd.log Nov 21 12:59:32 Pirana lmtpd[29418]: lmtp connection preauth'd as postman Nov 21 12:59:32 Pirana master[21506]: process 29418 exited, signaled to death by 11 Some of you please explain me what could be the problem, since I'm lost here. Thanks in advance, Regards, Eranga
