Re: [Dovecot] hardluck w/ sieve

2011-05-21 Thread errno 
On Saturday, May 21, 2011 10:53:55 PM errno wrote:
> I've followed the docs here:
> 
> http://wiki.dovecot.org/LDA/Sieve/Dovecot
> 
> ... in particular, the 'Per-user Sieve script location' scenario.
> 
> However, I'm unable to get any behavior that indicates that
> sieve is functioning correctly - well, functioning _at_all_ would
> be more accurate.
> 
> Relevant dovecot.conf:
> 

> plugin {
>   sieve = /var/sieve-scripts/%d/%u.sieve
> }
> 


... sheesh, of course the moment I send this it dawns on
me what the problem is...

The following fixed the issue:

plugin {
  sieve = /var/sieve-scripts/%d/%n.sieve
}

I was using %u when I should have been using %n.

Sorry for the noise!

[Dovecot] hardluck w/ sieve

2011-05-21 Thread errno 

I've followed the docs here:

http://wiki.dovecot.org/LDA/Sieve/Dovecot

... in particular, the 'Per-user Sieve script location' scenario.

However, I'm unable to get any behavior that indicates that
sieve is functioning correctly - well, functioning _at_all_ would
be more accurate.

Relevant dovecot.conf:

protocol lda {
  ...
  mail_plugins = sieve
}
auth default {
  ...
  passdb passwd-file {
args = /var/vmail/passwd
  }
  userdb static {
args = uid=vmail gid=vmail home=/var/vmail/%d/%u
  }
}
plugin {
  sieve = /var/sieve-scripts/%d/%u.sieve
}


ls -l /var/sieve-scripts/domain.com/user.sieve
-rw-r--r-- 1 vmail vmail 224 May 22 00:18 /var/sieve-scripts/domain/user.sieve


I of course have an extremely simple rule in the example 'user.sieve' file; but 
for whatever reasons, no filtering is occurring. 

Is there anything obvious in my configuration that's broke? How best to
debug?


Thankyou!

Re: [Dovecot] integrating procmail

2011-05-18 Thread errno 
On Wednesday, May 18, 2011 03:07:44 PM Jerry wrote:
> On Wed, 18 May 2011 14:50:54 -0700
> errno  articulated:
> > Below, I've provide the relevant snippets of my current functional
> > configuration; how best to integrate procmail into the mix?
> 
> Why procmail? Use sieve instead. It is fully supported in Dovecot 
> and IMHO far easier to use.
>

I hear you, and agree - I was able to determine that sieve was better 
supported. Unfortunately, I'm doing this for a client who is rather set 
in his ways and already has a largish custom procmail filter he 
wants/needs to use. For me to tell him, "no we need to use sieve
instead", he will see that as a failure on my part; and/or will request 
that I install and configure a different combination of software that will
facilitate his familiar territory of procmail.

Seeing as I already have postfix and dovecot functioning, I'd rather
just get procmail in there and be done with it; is this possible?


Thankyou!

[Dovecot] integrating procmail

2011-05-18 Thread errno 

Hello, list members!

I'm new to dovecot, and haven't needed to maintain an email server 
instance for quite some time.

I recently got a fairly simple postfix + dovecot installation functional 
as needed, however I now need to get procmail filtering incoming
mail, and after reading various docs and wikis, I find that I'm still
having a tough time feeling confident on how best to approach it in 
the simplest manner. (this is for a small installation 10 email 
accounts, max).

Below, I've provide the relevant snippets of my current functional
configuration; how best to integrate procmail into the mix?

/etc/postfix/main.cf:
...
alias_maps = hash:/etc/mail/aliases
local_recipient_maps = hash:/etc/postfix/vmailbox, $alias_maps
virtual_transport = dovecot
virtual_mailbox_domains = $mydomain
virtual_mailbox_base = /var/vmail/
virtual_mailbox_maps = hash:/etc/postfix/vmailbox
virtual_minimum_uid = 500
virtual_uid_maps = static:501
virtual_gid_maps = static:501
...


/etc/postfix/master.cf:
...
dovecot   unix  -   n   n   -   -   pipe
   flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/deliver -f ${sender} -
d ${recipient}
...


/etc/dovecot/dovecot.conf:
...
mail_location = maildir:~/Maildir

protocol lda {
  sendmail_path = /usr/sbin/sendmail
}
auth default {
  mechanisms = plain
  passdb passwd-file {
args = /var/vmail/passwd
  }
  userdb static {
args = uid=vmail gid=vmail home=/var/vmail/%d/%u
  }
  socket listen {
master {
  path = /var/run/dovecot/auth-master
  mode = 0600
  user = vmail
  group = vmail
}
  }
}
...


Thankyou for any tips, much appreciated!