locked ldap users

2015-11-11 Thread klemen 
Hello.

I'm having a problem regarding locked users in ldap.
We are using 389DS ldap server. We lock our users with nsAccountLock=true.
If user successfully logs into dovecot, his credentials gets cached.
When this user is locked its credentials still stay in cache.
The problem I'm having is that our ldap server returns error code 53
("Unwilling to perform - Account inactivated"). Dovecot takes this error
code and decides that ldap doesnt work so it takes users credentials
from cache (like stated in docs). User can still login untill his
credentials are cleared from cache.

Error message in logs:
ldap(USERNAME,193.X.Y.Z,): ldap_bind() failed:
Server is unwilling to perform
Oct 20 14:39:31 SERVER dovecot: auth:
ldap(USERNAME,193.X.Y.Z,): Falling back to expired
data from cache


Does dovecot reacts to error code 53 as it should? Maybe our ldap server
should return different error code - like 49/533 (Account_disabled)? How
would dovecot react to error code 49?

Currenty we solve this problem by taking list of locked users and clear
cache every minute.

thank you and best regards,
Klemen Andreuzzi
Arnes

Active directory

2015-11-11 Thread Станислав Черкасов 

Hello.
I have a iRedmail server integrated with AD.
I make it following theese instructions 
http://www.iredmail.org/docs/active.directory.html

In my AD i have a user
attributes:
sAMAccountName = user1
userPrincipalName  = c...@int.mdom.com
proxyAddresses= ma...@out.lor.com


i need login with user user1 without domain and then have an address 
ma...@out.lor.com


i user it in /⁠etc/⁠dovecot/⁠dovecot-⁠ldap.conf
-⁠-⁠-⁠-⁠
hosts   = dc1.int.mdom.com:389
ldap_version= 3
auth_bind   = yes
dn  = userksa
dnpass  = sdjfuihJKHSAJKDHQUWjdskfh
base= OU=Users,OU=QOL,DC=int,DC=mdom,DC=com
scope   = subtree
deref   = never

user_filter = (&(objectClass=user)(sAMAccountName=%n) 
(memberof=CN=Mail_Users,OU=Groups,OU=SFP,DC=int,DC=mdom,DC=com))
pass_filter = (&(objectClass=user)(sAMAccountName=%n) 
(memberof=CN=Mail_Users,OU=Groups,OU=SFP,DC=int,DC=mdom,DC=com))




default_pass_scheme = CRYPT

user_attrs  = 
=home=/var/vmail/vmail1/%Ld/%Ln/Maildir/,=mail=maildir:/var/vmail/vmail1/%Ld/%Ln/Maildir/

-⁠-⁠-⁠-⁠


i have tried to do:
#user_filter= (&(proxyAddresses=%u) 
(objectClass=person)(memberof=CN=Mail_Users,OU=Groups,OU=SFP,DC=int,DC=mdom,DC=com))
#pass_filter= (&(proxyAddresses=%u) 
(objectClass=person)(memberof=CN=Mail_Users,OU=Groups,OU=SFP,DC=int,DC=mdom,DC=com))


but nothing works.

Dovecot+AD

2015-11-11 Thread Станислав Черкасов 

Hello.
I have a iRedmail server integrated with AD.
I make it following theese instructions 
http://www.iredmail.org/docs/active.directory.html

In my AD i have a user
attributes:
sAMAccountName  = user1
userPrincipalName   = c...@int.mdom.com
proxyAddresses  = ma...@out.lor.com


i need login with user user1 without domain and then have an address 
ma...@out.lor.com


i user it in /etc/dovecot/dovecot-ldap.conf

hosts   = dc1.int.mdom.com:389
ldap_version= 3
auth_bind   = yes
dn  = userksa
dnpass  = sdjfuihJKHSAJKDHQUWjdskfh
base= OU=Users,OU=QOL,DC=int,DC=mdom,DC=com
scope   = subtree
deref   = never

user_filter = (&(objectClass=user)(sAMAccountName=%n) 
(memberof=CN=Mail_Users,OU=Groups,OU=SFP,DC=int,DC=mdom,DC=com))
pass_filter = (&(objectClass=user)(sAMAccountName=%n) 
(memberof=CN=Mail_Users,OU=Groups,OU=SFP,DC=int,DC=mdom,DC=com))




default_pass_scheme = CRYPT

user_attrs  = 
=home=/var/vmail/vmail1/%Ld/%Ln/Maildir/,=mail=maildir:/var/vmail/vmail1/%Ld/%Ln/Maildir/




i have tried to do:
#user_filter= (&(proxyAddresses=%u) 
(objectClass=person)(memberof=CN=Mail_Users,OU=Groups,OU=SFP,DC=int,DC=mdom,DC=com))
#pass_filter= (&(proxyAddresses=%u) 
(objectClass=person)(memberof=CN=Mail_Users,OU=Groups,OU=SFP,DC=int,DC=mdom,DC=com))


but nothing works.

Re: OT - Re: hunting the fatty

2015-11-11 Thread mancyb...@gmail.com 
On Wed, 11 Nov 2015 10:20:07 -0600
Rick Romero  wrote:

>   Quoting mancyb...@gmail.com:
> 
> > On Wed, 11 Nov 2015 09:50:29 -0600
> > Rick Romero  wrote:
> >
> >> LOL.
> >>
> >> This is a horrible subject line.  I've been trying to resolve a DDOS
> >> issue, and ignoring a lot of email. 
> >>
> >> Here I had been thinking this was a sex-spam, and I just got around to
> >> wondering why the spam system isn't working quite right and they kept
> >> coming in.  :P
> >>
> >> Not sure if this was suggested, but use SSD's.  With a ton of mail
> >> combined with Maildir random reads/writes, SSD's are like night and day.
> >>
> >> Rick
> >
> > Very sorry about nasty subject ;)
> > Btw is it worth the offload on i/o by having some Dovecot index or cache
> > on an SSD ?
> 
> Lately I've separated the indexes onto another SSD-based volume, just to
> save read/writes, but I don't think it actually improved anything.
> 
> Rick

I'm going to try dm-cache and flashcache asap ..

Re: OT - Re: hunting the fatty

2015-11-11 Thread Rick Romero 

 Quoting mancyb...@gmail.com:


On Wed, 11 Nov 2015 09:50:29 -0600
Rick Romero  wrote:


LOL.

This is a horrible subject line.  I've been trying to resolve a DDOS
issue, and ignoring a lot of email. 

Here I had been thinking this was a sex-spam, and I just got around to
wondering why the spam system isn't working quite right and they kept
coming in.  :P

Not sure if this was suggested, but use SSD's.  With a ton of mail
combined with Maildir random reads/writes, SSD's are like night and day.

Rick


Very sorry about nasty subject ;)
Btw is it worth the offload on i/o by having some Dovecot index or cache
on an SSD ?


Lately I've separated the indexes onto another SSD-based volume, just to
save read/writes, but I don't think it actually improved anything.

Rick

Re: hunting the fatty

2015-11-11 Thread Christian Kivalo 

On 2015-11-11 03:44, mancyb...@gmail.com wrote:

On Tue, 10 Nov 2015 08:50:50 +0100
Christian Kivalo  wrote:


Hi,

On 2015-11-10 01:44, mancyb...@gmail.com wrote:
> Hello dear list,
> I've recently discovered 'doveadm stats' and I'm trying to use
> "doveadm stats dump user" and "doveadm stats dump session"
> to understand the pop/imap users that put more stress on the hard
> disks.
>
> My problem is that some users refuse to delete their emails from the
> server,
> so they keep 20GB of maildir files on the server, the webmail
> (roundcube) takes forever to open the inbox,
> the imap searches takes forever
> and meanwhile all the users wait.
> (already tried roundcube + memcache(d) but didn't help)

What is forever in your context?
I'm using roundcube and a folder with about 78k mails opens in < 1 sec
unsorted. A folder with about 37k messages from a mailinglist and 
thread
sort takes < 3 sec. My roundcube shows 200 messages per page by 
default.

On a side note, are you using an imap proxy for roundcube? It doesn't
help you with your dovecot problem but it speeds up roundcube.

To speed up imap searches i can recommend to implement fts-solr with
dovecot (or maybe fts-elasticsearch, am wanting to try that but solr
works...). That will speed up your searches after mailboxes are 
indexed.


> So my problem is not the storage usage itself:
> I don't care if the user gets tons of emails with big attachments;
> my problem is when the user opens / searches an imap folder with more
> than 10K mails
> and iostat util goes 100% for minutes.

Dovecot should be very quick to open even folders with a huge amount 
of

files due to its indexes.

I'm unable to reproduce any significant numbers in iostat when 
accessing

large mailfolders with roundcube.

Whats your configuration, filesystem, ...

> So I've enabled dovecot's stats and enjoying "doveadm stats top",
> "stats-top.pl" and "doveadm stats dump user/session",
> but talking about "doveadm stats dump user" and its output fields:
>
> user   reset_timestamp last_update num_logins  num_cmds
user_cpusys_cpu min_faults  maj_faults  vol_cs  invol_cs
disk_input  disk_output read_count  read_bytes  write_count 
write_bytes mail_lookup_pathmail_lookup_attrmail_read_count 
mail_read_bytes mail_cache_hits
>
> I'm not sure which of those fields can help me
> and I can't find any relevant documentation.
>
> So here are my questions:
>
> 1. is there a documentation for those 21 fields and for 'doveadm
> stats' in general ?
> 2. what's the difference between disk_output, read_bytes, read_count
> and mail_read_bytes ?
> 3. which field of those is, in your opinion, more representative for
> expressing the workload that gives me problems ?
> 4. which settings do I need to store 1 week worth of stats ?
>
> I'm currenty using the 'standard' values:
>
>   stats_refresh = 30 secs
>   stats_track_cmds = yes
>   stats_memory_limit = 16 M
>   stats_command_min_time = 1 mins
>   stats_domain_min_time = 12 hours
>   stats_ip_min_time = 12 hours
>   stats_session_min_time = 15 mins
>   stats_user_min_time = 1 hours
>
> Can you please tell me the correct parameters to store 1 week of stats
> ?

For stats somebody else has to jump in, i have only enabled the plugin
to see what to get out of it but not made any use of it.

Please share your doveconf -n output

> Thank you,
> Mike

regards
christian


By 'forever' I mean more than 1 minute.


That is really long. This should not take that long.


So there is no documentation / manual for 'doveadm stats' ?
Do I have to read the source to know which field does what ?


I don't know of more than whats on the dovecot wiki stats plugin page at 
http://wiki2.dovecot.org/Statistics



I mean the output fields of "doveadm stats dump user":

userreset_timestamp last_update num_logins  num_cmds
user_cpusys_cpu min_faults  maj_faults  vol_cs  invol_cs
disk_input  disk_output read_count  read_bytes  write_count 
write_bytes mail_lookup_pathmail_lookup_attrmail_read_count 
mail_read_bytes mail_cache_hits

what's the difference between disk_output, read_bytes, read_count and
mail_read_bytes ?


From the wiki page:
disk_output: Number of bytes written to disk -> i'd go for disk_input if 
your interested in reads

read_bytes: Number of bytes read using read() syscalls
read_count: Number of read() syscalls
mail_read_bytes: Number of message bytes read()

Not really much information but a base to start tests from.

Make yourself a testaccount and test. Thats the best way to figure stuff 
out by yourself.



(sorry to restate the same question, just making sure about it)

Thank you,
Mike


Regards
Christian

OT - Re: hunting the fatty

2015-11-11 Thread Rick Romero 

LOL.

This is a horrible subject line.  I've been trying to resolve a DDOS
issue, and ignoring a lot of email. 

Here I had been thinking this was a sex-spam, and I just got around to
wondering why the spam system isn't working quite right and they kept
coming in.  :P

Not sure if this was suggested, but use SSD's.  With a ton of mail
combined with Maildir random reads/writes, SSD's are like night and day.

Rick

Re: hunting the fatty

2015-11-11 Thread mancyb...@gmail.com 
On Wed, 11 Nov 2015 16:34:33 +0100
Christian Kivalo  wrote:

> On 2015-11-11 03:44, mancyb...@gmail.com wrote:
> > On Tue, 10 Nov 2015 08:50:50 +0100
> > Christian Kivalo  wrote:
> > 
> >> Hi,
> >> 
> >> On 2015-11-10 01:44, mancyb...@gmail.com wrote:
> >> > Hello dear list,
> >> > I've recently discovered 'doveadm stats' and I'm trying to use
> >> > "doveadm stats dump user" and "doveadm stats dump session"
> >> > to understand the pop/imap users that put more stress on the hard
> >> > disks.
> >> >
> >> > My problem is that some users refuse to delete their emails from the
> >> > server,
> >> > so they keep 20GB of maildir files on the server, the webmail
> >> > (roundcube) takes forever to open the inbox,
> >> > the imap searches takes forever
> >> > and meanwhile all the users wait.
> >> > (already tried roundcube + memcache(d) but didn't help)
> >> 
> >> What is forever in your context?
> >> I'm using roundcube and a folder with about 78k mails opens in < 1 sec
> >> unsorted. A folder with about 37k messages from a mailinglist and 
> >> thread
> >> sort takes < 3 sec. My roundcube shows 200 messages per page by 
> >> default.
> >> On a side note, are you using an imap proxy for roundcube? It doesn't
> >> help you with your dovecot problem but it speeds up roundcube.
> >> 
> >> To speed up imap searches i can recommend to implement fts-solr with
> >> dovecot (or maybe fts-elasticsearch, am wanting to try that but solr
> >> works...). That will speed up your searches after mailboxes are 
> >> indexed.
> >> 
> >> > So my problem is not the storage usage itself:
> >> > I don't care if the user gets tons of emails with big attachments;
> >> > my problem is when the user opens / searches an imap folder with more
> >> > than 10K mails
> >> > and iostat util goes 100% for minutes.
> >> 
> >> Dovecot should be very quick to open even folders with a huge amount 
> >> of
> >> files due to its indexes.
> >> 
> >> I'm unable to reproduce any significant numbers in iostat when 
> >> accessing
> >> large mailfolders with roundcube.
> >> 
> >> Whats your configuration, filesystem, ...
> >> 
> >> > So I've enabled dovecot's stats and enjoying "doveadm stats top",
> >> > "stats-top.pl" and "doveadm stats dump user/session",
> >> > but talking about "doveadm stats dump user" and its output fields:
> >> >
> >> > user reset_timestamp last_update num_logins  num_cmds
> >> > user_cpusys_cpu min_faults  maj_faults  vol_cs  invol_cs 
> >> >disk_input  disk_output read_count  read_bytes  
> >> > write_count write_bytes mail_lookup_pathmail_lookup_attr 
> >> >mail_read_count mail_read_bytes mail_cache_hits
> >> >
> >> > I'm not sure which of those fields can help me
> >> > and I can't find any relevant documentation.
> >> >
> >> > So here are my questions:
> >> >
> >> > 1. is there a documentation for those 21 fields and for 'doveadm
> >> > stats' in general ?
> >> > 2. what's the difference between disk_output, read_bytes, read_count
> >> > and mail_read_bytes ?
> >> > 3. which field of those is, in your opinion, more representative for
> >> > expressing the workload that gives me problems ?
> >> > 4. which settings do I need to store 1 week worth of stats ?
> >> >
> >> > I'm currenty using the 'standard' values:
> >> >
> >> >   stats_refresh = 30 secs
> >> >   stats_track_cmds = yes
> >> >   stats_memory_limit = 16 M
> >> >   stats_command_min_time = 1 mins
> >> >   stats_domain_min_time = 12 hours
> >> >   stats_ip_min_time = 12 hours
> >> >   stats_session_min_time = 15 mins
> >> >   stats_user_min_time = 1 hours
> >> >
> >> > Can you please tell me the correct parameters to store 1 week of stats
> >> > ?
> >> 
> >> For stats somebody else has to jump in, i have only enabled the plugin
> >> to see what to get out of it but not made any use of it.
> >> 
> >> Please share your doveconf -n output
> >> 
> >> > Thank you,
> >> > Mike
> >> 
> >> regards
> >> christian
> > 
> > By 'forever' I mean more than 1 minute.
> 
> That is really long. This should not take that long.
> 
> > So there is no documentation / manual for 'doveadm stats' ?
> > Do I have to read the source to know which field does what ?
> 
> I don't know of more than whats on the dovecot wiki stats plugin page at 
> http://wiki2.dovecot.org/Statistics
> 
> > I mean the output fields of "doveadm stats dump user":
> > 
> > userreset_timestamp last_update num_logins  num_cmds
> > user_cpusys_cpu min_faults  maj_faults  vol_cs  invol_cs
> > disk_input  disk_output read_count  read_bytes  
> > write_count write_bytes mail_lookup_pathmail_lookup_attr
> > mail_read_count mail_read_bytes mail_cache_hits
> > 
> > what's the difference between disk_output, read_bytes, read_count and
> > mail_read_bytes ?
> 
>  From the wiki page:
> disk_output: Number of bytes

Re: OT - Re: hunting the fatty

2015-11-11 Thread mancyb...@gmail.com 
On Wed, 11 Nov 2015 09:50:29 -0600
Rick Romero  wrote:

> LOL.
> 
> This is a horrible subject line.  I've been trying to resolve a DDOS
> issue, and ignoring a lot of email. 
> 
> Here I had been thinking this was a sex-spam, and I just got around to
> wondering why the spam system isn't working quite right and they kept
> coming in.  :P
> 
> Not sure if this was suggested, but use SSD's.  With a ton of mail
> combined with Maildir random reads/writes, SSD's are like night and day.
> 
> Rick

Very sorry about nasty subject ;)

Btw is it worth the offload on i/o by having some Dovecot index or cache on an 
SSD ?

log client certificate

2015-11-11 Thread Eugenio De Vena 
Hello, I would like to log the client certificate ( don't want to 
authenticate using client certificate but just "log" the client 
certificate if present ( both Subject and Public key ) ). Is it possibile ?

Eugenio



smime.p7s
Description: Firma crittografica S/MIME

Re: Problems after upgrade from 2.0 to 2.2

2015-11-11 Thread Christian Kivalo 

Hi,

On 2015-11-12 08:03, Frank Rust wrote:

Hi all,
after upgrade from some 2.0 version to 2.2.19 (debian) i face map
login problems:

# doveconf -n
# 2.2.19 (ca91d540fd87): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.9
# OS: Linux 2.6.32-5-amd64 x86_64 Debian 8.2 ext4
auth_debug = yes
auth_debug_passwords = yes
auth_verbose = yes
auth_verbose_passwords = plain
debug_log_path = /var/log/dovecot-debug.log
hostname = test.my.domain.de
info_log_path = /var/log/dovecot.log
mail_access_groups = smmta
mail_debug = yes
mail_location =
mbox:/extra/mail/mbox.dir/%u/mailboxes:DIRNAME=mBoX-MeSsAgEs:INDEX=/extra/mail/mbox.dir/%u/index:CONTROL=/extra/mail/mbox.dir/%u/control:INBOX=/extra/mail/%u
mail_plugins = quota
mail_privileged_group = smmta
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope
encoded-character vacation subaddress comparator-i;ascii-numeric
relational regex imap4flags copy include variables body enotify
environment mailbox date index ihave duplicate
namespace inbox {
  location =
  mailbox Drafts {
special_use = \Drafts
  }
  mailbox Junk {
special_use = \Junk
  }
  mailbox Sent {
special_use = \Sent
  }
  mailbox "Sent Messages" {
special_use = \Sent
  }
  mailbox Trash {
special_use = \Trash
  }
  prefix =
}


Missing inbox = yes in your default namespace.

See wiki http://wiki2.dovecot.org/Namespaces


passdb {
  driver = pam
}
plugin {
  mail_log_events = delete undelete expunge copy mailbox_delete
mailbox_rename flag_change append
  quota = fs:User quota
  quota_rule = *:storage=1G
  quota_rule2 = Trash:storage=+100M
  quota_warning = storage=95%% quota-warning 95 %u
  quota_warning2 = storage=80%% quota-warning 80 %u
  sieve = file:~/sieve;active=~/.dovecot.sieve
}
postmaster_address = postmas...@my.domain.de
protocols = " imap sieve pop3"
quota_full_tempfail = yes
ssl = required
ssl_cert = 

[ snip ]


Nov 12 07:47:27 imap(frank): Debug: Namespace inbox: type=private,
prefix=, sep=, inbox=no, hidden=no, list=yes, subscriptions=yes

   
inbox not set.


location=mbox:/extra/mail/mbox.dir/frank/mailboxes:DIRNAME=mBoX-MeSsAgEs:INDEX=/extra/mail/mbox.dir/frank/index:CONTROL=/extra/mail/mbox.dir/frank/control:INBOX=/extra/mail/frank
Nov 12 07:47:27 imap(frank): Debug: fs:
root=/extra/mail/mbox.dir/frank/mailboxes,
index=/extra/mail/mbox.dir/frank/index, indexpvt=,
control=/extra/mail/mbox.dir/frank/control, inbox=/extra/mail/frank,
alt=
Nov 12 07:47:27 imap(frank): Debug: fs quota add mailbox dir =
/extra/mail/mbox.dir/frank/mailboxes
Nov 12 07:47:27 imap(frank): Debug: fs quota block device =
/dev/mapper/ownCloudVG-ownCloudData
Nov 12 07:47:27 imap(frank): Debug: fs quota mount point = /extra
Nov 12 07:47:27 imap(frank): Debug: fs quota mount type = ext4
Nov 12 07:47:27 imap-login: Debug: SSL alert: close notify 
[134.169.39.105]


What could cause the problem?

The problem is not quota related (I enhanced the allowed quota and got
the same results)


best regards,
Frank


regards
christian

Problems after upgrade from 2.0 to 2.2

2015-11-11 Thread Frank Rust 
Hi all,
after upgrade from some 2.0 version to 2.2.19 (debian) i face map login 
problems:

# doveconf -n
# 2.2.19 (ca91d540fd87): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.9
# OS: Linux 2.6.32-5-amd64 x86_64 Debian 8.2 ext4
auth_debug = yes
auth_debug_passwords = yes
auth_verbose = yes
auth_verbose_passwords = plain
debug_log_path = /var/log/dovecot-debug.log
hostname = test.my.domain.de
info_log_path = /var/log/dovecot.log
mail_access_groups = smmta
mail_debug = yes
mail_location = 
mbox:/extra/mail/mbox.dir/%u/mailboxes:DIRNAME=mBoX-MeSsAgEs:INDEX=/extra/mail/mbox.dir/%u/index:CONTROL=/extra/mail/mbox.dir/%u/control:INBOX=/extra/mail/%u
mail_plugins = quota
mail_privileged_group = smmta
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope encoded-character 
vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy 
include variables body enotify environment mailbox date index ihave duplicate
namespace inbox {
  location = 
  mailbox Drafts {
special_use = \Drafts
  }
  mailbox Junk {
special_use = \Junk
  }
  mailbox Sent {
special_use = \Sent
  }
  mailbox "Sent Messages" {
special_use = \Sent
  }
  mailbox Trash {
special_use = \Trash
  }
  prefix = 
}
passdb {
  driver = pam
}
plugin {
  mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename 
flag_change append
  quota = fs:User quota
  quota_rule = *:storage=1G
  quota_rule2 = Trash:storage=+100M
  quota_warning = storage=95%% quota-warning 95 %u
  quota_warning2 = storage=80%% quota-warning 80 %u
  sieve = file:~/sieve;active=~/.dovecot.sieve
}
postmaster_address = postmas...@my.domain.de
protocols = " imap sieve pop3"
quota_full_tempfail = yes
ssl = required
ssl_cert = , method=PLAIN, 
rip=134.169.39.105, lip=134.169.39.22, mpid=9475, TLS, session=<...>

dovecot-debug.log:
Nov 12 07:47:27 imap-login: Debug: SSL: elliptic curve secp384r1 will be used 
for ECDH and ECDHE key exchanges
Nov 12 07:47:27 auth: Debug: auth client connected (pid=11158)
Nov 12 07:47:27 imap-login: Debug: SSL: where=0x10, ret=1: before/accept 
initialization [134.169.39.105]
Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2001, ret=1: before/accept 
initialization [134.169.39.105]
Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2001, ret=1: unknown state 
[134.169.39.105]
Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2001, ret=1: unknown state 
[134.169.39.105]
Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2001, ret=1: unknown state 
[134.169.39.105]
Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2001, ret=1: unknown state 
[134.169.39.105]
Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2001, ret=1: unknown state 
[134.169.39.105]
Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2001, ret=1: unknown state 
[134.169.39.105]
Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2002, ret=-1: unknown state 
[134.169.39.105]
Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2002, ret=-1: unknown state 
[134.169.39.105]
Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2001, ret=1: unknown state 
[134.169.39.105]
Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2002, ret=-1: unknown state 
[134.169.39.105]
Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2001, ret=1: unknown state 
[134.169.39.105]
Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2001, ret=1: unknown state 
[134.169.39.105]
Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2001, ret=1: unknown state 
[134.169.39.105]
Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2001, ret=1: unknown state 
[134.169.39.105]
Nov 12 07:47:27 imap-login: Debug: SSL: where=0x20, ret=1: SSL negotiation 
finished successfully [134.169.39.105]
Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2002, ret=1: SSL negotiation 
finished successfully [134.169.39.105]
Nov 12 07:47:27 auth: Debug: client in: AUTH1   PLAIN   service=imap
secured session=QkLwUFIkXsCGqSdplip=134.169.39.22   
rip=134.169.39.105  lport=993   rport=49246 resp= (previous 
base64 data removed)
Nov 12 07:47:27 auth-worker(11140): Debug: pam(frank,134.169.39.105): lookup 
service=dovecot
Nov 12 07:47:27 auth-worker(11140): Debug: pam(frank,134.169.39.105): #1/1 
style=1 msg=Password: 
Nov 12 07:47:27 auth: Debug: client passdb out: OK  1   user=frank  
Nov 12 07:47:27 auth: Debug: master in: REQUEST 3038248961  11158   1   
4e2362c2872f9288b7c8c3ebd8469620session_pid=11159   
request_auth_token
Nov 12 07:47:27 auth-worker(11140): Debug: pam(frank,134.169.39.105): lookup
Nov 12 07:47:27 auth: Debug: master userdb out: USER3038248961  frank   
system_groups_user=frankuid=1000gid=100 home=/home/frank
auth_token=1e04d2c61fb327ec14c1e54ff678d73a325d20bf
Nov 12 07:47:27 imap(frank): Debug: Loading modules from directory: 
/usr/lib/dovecot/modules
Nov 12 07:47:27 imap(frank): Debug: Module loaded: 
/usr/lib/dovecot/modules/lib10_quota_plugin.so
Nov 12 07:47:27 imap(frank):

Re: * Re: procmail as a content_filter with dovecot

2015-11-11 Thread Gerhard Wiesinger 

On 10.11.2015 23:38, Vicki Brown wrote:

Thank you. This may be helpful.


On Nov 10, 2015, at 13:01, Benny Pedersen  wrote:


https://www.google.dk/search?q=procmailrc+to+sieve




Find my enhanced version + wrapper script at with custom configuration at:
http://www.wiesinger.com/opensource/procmail2sieve/

Ciao,
Gerhard