> As a quick "get me home fix" I'd like to set "anyone p" on all my
> mailbox folders until there is a solution to this problem.
> However, there doesn't seem to be any easy way to do this. I'm off to
> write a script now but if there is an easy way please can you let me
> know what it is...
> ---
On 11/04/11 10:18, cy...@jelmail.com wrote:
>
> Original Message:
> -
> From: Bron Gondwana br...@fastmail.fm
> Date: Mon, 11 Apr 2011 06:38:44 +0200
> To: cy...@jelmail.com, info-cyrus@lists.andrew.cmu.edu
> Subject: Re: Deliver to mailbox problem with v2.4.7
Original Message:
-
From: Bron Gondwana br...@fastmail.fm
Date: Mon, 11 Apr 2011 06:38:44 +0200
To: cy...@jelmail.com, info-cyrus@lists.andrew.cmu.edu
Subject: Re: Deliver to mailbox problem with v2.4.7
On Mon, Apr 11, 2011 at 12:17:47AM +0100, John wrote:
> On 09/04/11 23
On Mon, Apr 11, 2011 at 12:17:47AM +0100, John wrote:
> On 09/04/11 23:19, Dan White wrote:
> > On 09/04/11 22:33 +0100, John wrote:
> >> Sorry for delay in responding, I have been away.
> >>
> >> Setting "anyone p" made no difference:
> >
> > Can you test to see if the same problem happens with fo
On 09/04/11 23:19, Dan White wrote:
> On 09/04/11 22:33 +0100, John wrote:
>> Sorry for delay in responding, I have been away.
>>
>> Setting "anyone p" made no difference:
>>
>> localhost.localdomain> sam user/john anyone p
>> localhost.localdomain> lam user/john
>> john lrswipcda
>> anyone p
>>
>>
On 09/04/11 22:33 +0100, John wrote:
>Sorry for delay in responding, I have been away.
>
>Setting "anyone p" made no difference:
>
>localhost.localdomain> sam user/john anyone p
>localhost.localdomain> lam user/john
>john lrswipcda
>anyone p
>
>localhost.localdomain> sam user/john/folder.name/subfo
On 07/04/11 22:43, Dan White wrote:
> On 07/04/11 23:23 +0100, John wrote:
>> On 07/04/11 22:06, Dan White wrote:
>>> 'deliver' should deliver to the user's INBOX if it believes there's a
>>> permissions problem, or if it believes the mailbox doesn't exist. Does
>>> syslog give you any hints?
>>>
>
On 07/04/11 23:23 +0100, John wrote:
>On 07/04/11 22:06, Dan White wrote:
>> 'deliver' should deliver to the user's INBOX if it believes there's a
>> permissions problem, or if it believes the mailbox doesn't exist. Does
>> syslog give you any hints?
>>
>> What does your configuration look like? Ho
On 07/04/11 22:06, Dan White wrote:
> On 07/04/11 22:30 +0100, John wrote:
>> Good afternoon,
>>
>> I have just upgraded from Cyrus-IMAP 2.3.15 to 2.4.7 and my mailbox
>> delivery has stopped working.
>>
>> My procmail delivers mail using a command similar to the below :
>>
>> /usr/cyrus/bin/delive
On 07/04/11 22:30 +0100, John wrote:
>Good afternoon,
>
>I have just upgraded from Cyrus-IMAP 2.3.15 to 2.4.7 and my mailbox
>delivery has stopped working.
>
>My procmail delivers mail using a command similar to the below :
>
>/usr/cyrus/bin/deliver -a john -m folder/subfolder john < message
>
>Thi
I am wondering why you have been using procmail with cyrus.
You should deliver to cyrus malboxes using LMTP with unix socket or with
TCP.
You can easily change your configuration.
Also I think it is not very efficient to call the deliver process for
every message to be delivered to a malbox.
IF
Good afternoon,
I have just upgraded from Cyrus-IMAP 2.3.15 to 2.4.7 and my mailbox
delivery has stopped working.
My procmail delivers mail using a command similar to the below :
/usr/cyrus/bin/deliver -a john -m folder/subfolder john < message
This would result in message being dropped into j
12 matches
Mail list logo
