Re: lmtp versus deliver

2004-11-09 Thread Philip Chambers

On Mon, 08 Nov 2004 20:32:45 -0500 Ken Murchison [EMAIL PROTECTED] wrote:

 Philip Chambers wrote:
 
  On Fri, 05 Nov 2004 15:00:34 -0500 Ken Murchison [EMAIL PROTECTED] wrote:
  
  
 Philip Chambers wrote:
 
 
 This is cyrus-imap.2.2.8 with exim-4.41:
 
 I had been using lmtp to do normal deliveries but deliver to deliver to 
 specific 
 folders (as for spam being diverted to a spam-folder.
 
 I noticed in my exim logs that at busy times I was getting a few failures 
 from the 
 deliver program (logged as error code 75 or 65 by exim).  Can someone tell 
 me what 
 these two codes mean?
 
 On reflection I thought that I might be able to use lmtp to deliver to 
 specific 
 folders instead by using [EMAIL PROTECTED] as the address.  I tried this 
 and it worked. An advantage of this is the benefit of multiple deliveries 
 in one go.
 
 However, I have now found a difference which it would be nice to remove:
 
 Using deliver to deliver to user.folder, if the folder does not exist, 
 it delivers 
 to the user's inbox.  Using lmpt, if the folder does not exist, it rejects 
 the 
 message.
 
 Is it possible to get lmtp to deliver to the inbox if the specified folder 
 does not 
 exist?
 
 Either I'm confused or you're using the incorrect syntax.  To deliver to 
 a user-specific folder via LMTP, the address should be 
 [EMAIL PROTECTED]  If the folder doesn't exist (or doesn't allow 
 posting by the [un]authenticated user, then the message *will* go to the 
   user's INBOX.
  
  
  Thanks for that information, as you say, using plus as the separator 
  delivers to the 
  folder if there is a suitable acl or to the inbox if not.
  
  Using a dot to separate the username and foldername certainly works and the 
  delivery 
  takes place without any acl on the folder.
 
 Hmm, its probably because you are running deliver as the recipient user 
 and the mailbox name is taken literally (as the internal name).
 

It is lmtpd which is delivering direct to the folder, not deliver.

Using lmtp, if I give an address of [EMAIL PROTECTED] and the folder 
user.username.folder exists then delivery takes place, even without an ACL.

Phil.
---
Phil Chambers ([EMAIL PROTECTED])
University of Exeter

---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html


Re: lmtp versus deliver

2004-11-08 Thread Philip Chambers

On Fri, 05 Nov 2004 15:00:34 -0500 Ken Murchison [EMAIL PROTECTED] wrote:

 Philip Chambers wrote:
 
  This is cyrus-imap.2.2.8 with exim-4.41:
  
  I had been using lmtp to do normal deliveries but deliver to deliver to 
  specific 
  folders (as for spam being diverted to a spam-folder.
  
  I noticed in my exim logs that at busy times I was getting a few failures 
  from the 
  deliver program (logged as error code 75 or 65 by exim).  Can someone tell 
  me what 
  these two codes mean?
  
  On reflection I thought that I might be able to use lmtp to deliver to 
  specific 
  folders instead by using [EMAIL PROTECTED] as the address.  I tried this 
  and it worked. An advantage of this is the benefit of multiple deliveries 
  in one go.
  
  However, I have now found a difference which it would be nice to remove:
  
  Using deliver to deliver to user.folder, if the folder does not exist, it 
  delivers 
  to the user's inbox.  Using lmpt, if the folder does not exist, it rejects 
  the 
  message.
  
  Is it possible to get lmtp to deliver to the inbox if the specified folder 
  does not 
  exist?
 
 Either I'm confused or you're using the incorrect syntax.  To deliver to 
 a user-specific folder via LMTP, the address should be 
 [EMAIL PROTECTED]  If the folder doesn't exist (or doesn't allow 
 posting by the [un]authenticated user, then the message *will* go to the 
   user's INBOX.

Thanks for that information, as you say, using plus as the separator delivers 
to the 
folder if there is a suitable acl or to the inbox if not.

Using a dot to separate the username and foldername certainly works and the 
delivery 
takes place without any acl on the folder.

Phil.
---
Phil Chambers ([EMAIL PROTECTED])
University of Exeter

---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html


Re: lmtp versus deliver

2004-11-08 Thread Ken Murchison
Philip Chambers wrote:
On Fri, 05 Nov 2004 15:00:34 -0500 Ken Murchison [EMAIL PROTECTED] wrote:

Philip Chambers wrote:

This is cyrus-imap.2.2.8 with exim-4.41:
I had been using lmtp to do normal deliveries but deliver to deliver to specific 
folders (as for spam being diverted to a spam-folder.

I noticed in my exim logs that at busy times I was getting a few failures from the 
deliver program (logged as error code 75 or 65 by exim).  Can someone tell me what 
these two codes mean?

On reflection I thought that I might be able to use lmtp to deliver to specific 
folders instead by using [EMAIL PROTECTED] as the address.  I tried this 
and it worked. An advantage of this is the benefit of multiple deliveries in one go.

However, I have now found a difference which it would be nice to remove:
Using deliver to deliver to user.folder, if the folder does not exist, it delivers 
to the user's inbox.  Using lmpt, if the folder does not exist, it rejects the 
message.

Is it possible to get lmtp to deliver to the inbox if the specified folder does not 
exist?
Either I'm confused or you're using the incorrect syntax.  To deliver to 
a user-specific folder via LMTP, the address should be 
[EMAIL PROTECTED]  If the folder doesn't exist (or doesn't allow 
posting by the [un]authenticated user, then the message *will* go to the 
 user's INBOX.

Thanks for that information, as you say, using plus as the separator delivers to the 
folder if there is a suitable acl or to the inbox if not.

Using a dot to separate the username and foldername certainly works and the delivery 
takes place without any acl on the folder.
Hmm, its probably because you are running deliver as the recipient user 
and the mailbox name is taken literally (as the internal name).

--
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
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html


Re: lmtp versus deliver

2004-11-05 Thread Ken Murchison
Philip Chambers wrote:
This is cyrus-imap.2.2.8 with exim-4.41:
I had been using lmtp to do normal deliveries but deliver to deliver to specific 
folders (as for spam being diverted to a spam-folder.

I noticed in my exim logs that at busy times I was getting a few failures from the 
deliver program (logged as error code 75 or 65 by exim).  Can someone tell me what 
these two codes mean?

On reflection I thought that I might be able to use lmtp to deliver to specific 
folders instead by using [EMAIL PROTECTED] as the address.  I tried this 
and it worked. An advantage of this is the benefit of multiple deliveries in one go.

However, I have now found a difference which it would be nice to remove:
Using deliver to deliver to user.folder, if the folder does not exist, it delivers 
to the user's inbox.  Using lmpt, if the folder does not exist, it rejects the 
message.

Is it possible to get lmtp to deliver to the inbox if the specified folder does not 
exist?
Either I'm confused or you're using the incorrect syntax.  To deliver to 
a user-specific folder via LMTP, the address should be 
[EMAIL PROTECTED]  If the folder doesn't exist (or doesn't allow 
posting by the [un]authenticated user, then the message *will* go to the 
 user's INBOX.

--
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
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html