Re: Delivery to Shared Folders via authenticated SMTP then LMTP

2009-04-22 Thread Andy Bennett
Hi, I've managed to get things working now. >> 2009-04-21 15:10:27 H=mx2.andrew.cmu.edu [128.2.11.36] >> F= >> temporarily rejected RCPT : response to "MAIL >> FROM:<>" from localhost [127.0.0.1] was: 430 Authentication require > > AB> Your reply went to the list and directly to me: the dire

Re: Delivery to Shared Folders via authenticated SMTP then LMTP

2009-04-22 Thread Duncan Gibb
Andy Bennett wrote: DG> To do what I think you want (ACLs for delivery to shared DG> mailboxes by users employing SMTPA), you need Exim to pass DG> the authenticated user from the SMTP transaction with the DG> MUA into the _MAIL_ line of the LMTP conversation. DG> MAIL FROM: AUTH= AB> Something

Re: much information from cyrus log

2009-04-22 Thread Andreas Winkelmann
> I'm trying to get as much information as possible from the cyrus log. > I've tried several modification of the syslog configuration > filewithout success. > > I also create a folder at /var/log/.. per user getting as much > information I want but... it's in different files and folders, and > is p

much information from cyrus log

2009-04-22 Thread Ana Ribas Roca
Hello I'm trying to get as much information as possible from the cyrus log. I've tried several modification of the syslog configuration filewithout success. I also create a folder at /var/log/.. per user getting as much information I want but... it's in different files and folders, and is

Re: initial slowness

2009-04-22 Thread Andreas Winkelmann
>>> The other option I ran into some time ago... and it had to due to >>> defining multiple authentication schemes in the SASL configuration. >>> When you define multiple, it will try each one in order. I stripped >>> it down to just PLAIN, which is what I wanted to use, and it was >>> much quicke

Re: initial slowness

2009-04-22 Thread Iv Ray
On 25.02.2009, at 01:15, Iv Ray wrote: > On 25.02.2009, at 00:28, Raymond T. Sundland wrote: > >> The other option I ran into some time ago... and it had to due to >> defining multiple authentication schemes in the SASL configuration. >> When you define multiple, it will try each one in order. I