Stop Logging to Syslog

[Asai]

Greetings,

My logging config is as follows:

# doveadm log find
Debug: /var/log/dovecot-debug.log
Info: /var/log/dovecot.log
Warning: /var/log/dovecot.log
Error: /var/log/dovecot.log
Fatal: /var/log/dovecot.log

However, I'm still getting logs in /var/log/messages which I don't 
want.  I've looked into /etc/rsyslog.conf for clues, but can't find 
anything that would point to Dovecot logging to /var/log/messages.


Can anyone point me in the right direction here?

Thank you,
Asai

___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: Submission Service Copy To Sent

[Asai]

On 8/9/2022 11:05 AM, spi wrote:


Am 09.08.22 um 18:56 schrieb Asai:

Greetings,

We've had a longstanding problem with emails not being copied to the
Sent folder that seems to be a bug with various email clients
(Thunderbird, TypeApp.)

I know that Dovecot has the option to use the Submission service to
copy emails to Sent without using SMTP to do this.

Would this solve the problem we've seen over the years of emails not
being copied to the Sent folder on various clients under certain
(unknown) conditions?



I had the same issue some time ago, If I remember right, with submission
the IMAP client needs to support some additional IMAP features which
most clients currently don't do.

I did it the other way round - my clients send mails by smtp and a
postfix milter script catches the mail on the mail server and copies it
locally to the user's IMAP mailbox - the clients don't upload any sent
mails by IMAP anymore.

Am using mailfromd as milter: 
https://puszcza.gnu.org.ua/software/mailfromd/


--
Cheers
spi


Thank you for your helpful response,

Asai

Submission Service Copy To Sent

[Asai]

Greetings,

We've had a longstanding problem with emails not being copied to the 
Sent folder that seems to be a bug with various email clients 
(Thunderbird, TypeApp.)


I know that Dovecot has the option to use the Submission service to copy 
emails to Sent without using SMTP to do this.


Would this solve the problem we've seen over the years of emails not 
being copied to the Sent folder on various clients under certain 
(unknown) conditions?


Thanks for your insight here.

Asai

Re: Emails Ending up in Junk

[Asai]

Hello Łukasz,

This happens when the user is logged in on the computer.  The user has 
to check for important emails in Junk regularly.  We're trying to turn 
off adaptive Junk filters in Thunderbird right now, but I'm not sure if 
it's a TB issue or something with the server side filtering.   Also, 
Spamassassin isn't marking these emails as spam either, so we're kind of 
stumped right now.


On 4/2/2021 1:34 PM, Łukasz Szczepański wrote:
Thunderbird has built in spam control feature and can move message to 
junk on it self. When message is moved to Junk? Only when user is 
connected to mailbox or even when nobody is logon?
W dniu 2 kwi 2021, o 20:26, użytkownik Asai 
mailto:a...@globalchangemusic.org>> napisał:


Greetings,

I'm trying to debug an issue with a user who is finding emails
(user uses Thunderbird as client) ending up in Junk folder, and
constantly marks email as Not Junk, but important email ends up in
Junk folder.

I have sieve set up, but am unable to determine if this is the
result of a sieve problem (sieve will automatically move certain
emails into Junk if certain headers are present, but these headers
are not present on these emails.)

I'm looking in Dovecot debug logs to try to figure this out, but
all I can find is sometimes this, and I don't know if this is
relevant.  Can anyone point us in the right direction for solving
this issue?

Apr 01 11:51:05 imap(u...@domain.tld)<102535><+kTsYd6+f83AqEbH>: Debug: 
Mailbox Junk: Mailbox opened because: UID move
Apr 01 11:57:08 imap(u...@domain.tld)<102735>: Debug: 
Mailbox Junk: UID 565: Opened mail because: prefetch
Apr 01 11:57:08 imap(u...@domain.tld)<102735>: Debug: 
Mailbox Junk: UID 565: Opened mail because: access
Apr 01 11:57:08 imap(u...@domain.tld)<102735>: Debug: 
Mailbox Junk: UID 565: Opened mail because: full mail
Apr 01 12:00:20 imap(u...@domain.tld)<71333>: Debug: 
Mailbox Junk: Mailbox opened because: STATUS
Apr 01 18:52:10 imap(u...@domain.tld)<114066>: Debug: 
Mailbox Junk: Mailbox opened because: SELECT


--
Asai
520.260.6887

Emails Ending up in Junk

[Asai]

Greetings,

I'm trying to debug an issue with a user who is finding emails (user 
uses Thunderbird as client) ending up in Junk folder, and constantly 
marks email as Not Junk, but important email ends up in Junk folder.


I have sieve set up, but am unable to determine if this is the result of 
a sieve problem (sieve will automatically move certain emails into Junk 
if certain headers are present, but these headers are not present on 
these emails.)


I'm looking in Dovecot debug logs to try to figure this out, but all I 
can find is sometimes this, and I don't know if this is relevant.  Can 
anyone point us in the right direction for solving this issue?


Apr 01 11:51:05 imap(u...@domain.tld)<102535><+kTsYd6+f83AqEbH>: Debug: Mailbox 
Junk: Mailbox opened because: UID move
Apr 01 11:57:08 imap(u...@domain.tld)<102735>: Debug: Mailbox 
Junk: UID 565: Opened mail because: prefetch
Apr 01 11:57:08 imap(u...@domain.tld)<102735>: Debug: Mailbox 
Junk: UID 565: Opened mail because: access
Apr 01 11:57:08 imap(u...@domain.tld)<102735>: Debug: Mailbox 
Junk: UID 565: Opened mail because: full mail
Apr 01 12:00:20 imap(u...@domain.tld)<71333>: Debug: Mailbox 
Junk: Mailbox opened because: STATUS
Apr 01 18:52:10 imap(u...@domain.tld)<114066>: Debug: Mailbox 
Junk: Mailbox opened because: SELECT

Re: What's a Reasonable Inbox Size?

[Asai]

We rotate the folder to another name with the date like INBOX-2020-05-07
with instructions how to refresh their folder list (or even modify the
.subscription file for the).

We also cull Trash, deleted items, and spam folders automatically as well.

Regards,
KAM


That makes sense.  So you're saying that very large inboxes are 
generally bad for mobile devices?  How are they bad for the servers?


Asai

Re: What's a Reasonable Inbox Size?

[Asai]

Thanks for your response,

So, how do those rotation scripts work in concept?

People are still able to access their old inboxes, but it just moves 
them to an archived state?


On 5/7/2020 9:40 AM, Kevin A. McGrail wrote:

On 5/7/2020 11:39 AM, Asai wrote:

What's a reasonable inbox size?  Is 20+ GB reasonable and nothing to
worry about?


Great question.

At my firm, we wrote rotation tools that work for mbox format to rotate
inboxes monthly if they are over a certain size.  We also do the sent
items folders.

We find that large inboxes are bad for the server and bad for the client
because the MUAs just don't handle it well either.  1 or 2GBs and you
start to see issues.

After a little bit of user training, they like it.  Part of the routine
maintenance they need.

Regards,
KAM

What's a Reasonable Inbox Size?

[Asai]

Greetings,

I have several users who have inboxes that are over 20 GB.

Lately I have noticed Dovecot logs say it's taking over 30 seconds to 
sync their mailboxes.


As email admins,  how do you handle inboxes that are so large? Do you 
use mailbox types that have better performance like dbox? We're using 
maildir.


What's a reasonable inbox size?  Is 20+ GB reasonable and nothing to 
worry about?


Thanks for any insight here.

--
Asai7

Is It possbile to convert to DBox or MDBox on a per user basis?

[Asai]

Greetings,

Is It possbile to convert to DBox or MDBox on a per user basis?

If so, can someone point me to the correct documentation?

Thank you,

--
Asai

Issue with doveadm backup

[Asai]

Greetings,

Lately I've been seeing this error pop up when running a nightly cron to 
a backup share with doveadm:


 Error: stat(/vmail/domain.tld/user/.dovecot-box-sync.lock/tmp) failed: Not a 
directory: 1 Time(s)

This is the command:

doveadm backup -u u...@domain.tld maildir:backupshare/daily/domain.tld/user

Our main vmail directory is on an NFS share and seems to be working 
fine.  This has only occurred recently.


Can anyone offer any insights into what this is and fixing it if need be?

--
Asai

Postfix Dovecot Consultant Availability

[Asai]

Greetings,

We're in process of upgrading our Postfix / Dovecot installation, and 
would like to know if there are any qualified consultants out there that 
would be willing to work for us to help us verify and improve the 
deployment for our non-profit organization?  This would be a fairly 
simple job of looking over configs and making recommendations, but may 
give way into more ongoing work.


I know there are a lot of experts on this list that really know how 
Postfix and Dovecot work and we'd really appreciate some quality 
advice.  I'm sending this request to both Postfix and Dovecot lists.


Please email me directly with replies.

--
Asai

Re: Cached message size smaller than expected

[Asai]

Thanks, Sami,

The version is 2.3.7.2

On 1/21/2020 2:18 PM, Sami Ketola wrote:

Hi,

what dovecot version is this? This looks a lot like bug that was fixed in 
2.2.25.5

Sami


On 21 Jan 2020, at 17.59, Asai  wrote:

Greetings,

Can anyone help me to solve this problem?

When doveadm sync is running nightly, we have a certain user's mailbox that 
will not properly sync and the logs give me this error (user private info 
redacted):

Error: Mailbox USER/MAILBOX: UID=79: 
read(/vmail/domain.org/user/.MAILBOX/cur/1575914253.M611834P7822.triata4,S=41893,W=42718:2,Sc)
 failed: Cached message size smaller than expected (41893 < 41897, 
box=USER/MAILBOX, UID=79) (read reason=mail stream)

I have deleted the dovecot indexes in the synced backup of this mailbox, as 
well as in the actual user's mailbox itself and I'm still getting this error.

What am I missing?

Thank you for your help here.

-Asai


--
Asai
520.260.6887

Cached message size smaller than expected

[Asai]

Greetings,

Can anyone help me to solve this problem?

When doveadm sync is running nightly, we have a certain user's mailbox 
that will not properly sync and the logs give me this error (user 
private info redacted):


Error: Mailbox USER/MAILBOX: UID=79: 
read(/vmail/domain.org/user/.MAILBOX/cur/1575914253.M611834P7822.triata4,S=41893,W=42718:2,Sc)
 failed: Cached message size smaller than expected (41893 < 41897, 
box=USER/MAILBOX, UID=79) (read reason=mail stream)

I have deleted the dovecot indexes in the synced backup of this mailbox, 
as well as in the actual user's mailbox itself and I'm still getting 
this error.


What am I missing?

Thank you for your help here.

-Asai

Re: Home Directory Creation

[Asai via dovecot]

On 10/4/2019 10:31 PM, Aki Tuomi via dovecot wrote:
As experiment, you could maybe use mail_lua plugin to create the 
user directory on demand,

make a lua script with
function mail_user_created(user)
-- create directory for user:home
end
See https://doc.dovecot.org/plugin-settings/mail-lua-plugin/ and 
https://wiki.dovecot.org/Design/Lua

Aki


Success.

Using the mail_lua plugin, and configuring the lua script location in 
the dovecot configs I used this script to create the home folder under 
the user's mail directory.  Hopefully this will help somebody else.


require 'lfs'

function mail_user_created(user)
    path = "/vmail"
    domain = user:var_expand("%d")
    username = user:var_expand("%n")

    lfs.mkdir(path .. domain )
    lfs.mkdir(path .. "/" .. domain .. "/" .. username )
    lfs.mkdir(path .. "/" .. domain .. "/" .. username .. "/home")
    lfs.mkdir(path .. "/" .. domain .. "/" .. username .. 
"/home/sieve")


    --file = io.open("/etc/dovecot/lualog.log", "w")
    --file:write(path .. "/" .. domain .. "/" .. username .. 
"/home/sieve",  "\n")


end

Re: Home Directory Creation

[Asai via dovecot]

As experiment, you could maybe use mail_lua plugin to create the user directory 
on demand,

make a lua script with

function mail_user_created(user)
   -- create directory for user:home
end

See https://doc.dovecot.org/plugin-settings/mail-lua-plugin/ and 
https://wiki.dovecot.org/Design/Lua

Aki


Thanks, Aki.

I've tried it out and it looks promising.  The only issue is debugging, 
and the documentation isn't entirely clear to me.  I need to figure out 
how to output some debug data to some kind console or file.


Asai

Re: Home Directory Creation

[Asai via dovecot]

On 10/4/2019 12:58 AM, Sami Ketola via dovecot wrote:
It depends heavily on how do you add users to your system. If you are 
using LDAP to store the user information then you can create the home 
directory at the same time you add the user to ldap.


Sami


Hello, Sami.

Thanks for your reply.

We're just using a SQL backend to store user info.  How does this get 
done with LDAP? Perhaps we can do the same with a SQL backend.


Asai

Re: Home Directory Creation

[Asai via dovecot]

One thing Timo mentioned in this post 
(https://dovecot.org/list/dovecot/2013-May/090397.html) is: "You could 
also change your new user creation to trigger mkdiring the user's home."


Does anyone know where I can find any documentation on this, or has 
anyone done this?


Thanks,
Asai

Re: Home Directory Creation

[Asai via dovecot]

Looks like this still old reply from TImo applies: 
https://dovecot.org/list/dovecot/2013-May/090397.html


The welcome plugin could maybe of help:

https://doc.dovecot.org/plugin-settings/welcome-plugin/

Regards,

Stephan.


Thanks, Stephan, looks like Timo's already answered it.

OK, so the next question is how did I ever get this working in the first 
place?  I don't even remember.  I'll look at the welcome plugin.


Thanks!

Asai

Re: Home Directory Creation

[Asai via dovecot]

Tried your config here and it works. My debug log looks as follows for 
the first brief IMAP session:


Oct  3 22:28:56 drieka dovecot: imap-login: Login: 
user=, method=PLAIN, rip=::1, lip=::1, mpid=21949, 
secured, session=
Oct  3 22:28:56 drieka dovecot: imap(diederik-jan): Debug: Added 
userdb setting: plugin/=yes
Oct  3 22:28:56 drieka dovecot: imap(diederik-jan): Debug: Effective 
uid=1001, gid=1001, home=/vmail//diederik-jan/home
Oct  3 22:28:56 drieka dovecot: imap(diederik-jan): Debug: Home dir 
not found: /vmail//diederik-jan/home
Oct  3 22:28:56 drieka dovecot: imap(diederik-jan): Debug: Namespace 
inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, 
subscriptions=yes location=maildir:/vmail//diederik-jan
Oct  3 22:28:56 drieka dovecot: imap(diederik-jan): Debug: maildir++: 
root=/vmail//diederik-jan, index=, indexpvt=, control=, 
inbox=/vmail//diederik-jan, alt=
Oct  3 22:28:56 drieka dovecot: imap(diederik-jan): Debug: Namespace : 
/vmail//diederik-jan doesn't exist yet, using default permissions
Oct  3 22:28:56 drieka dovecot: imap(diederik-jan): Debug: Namespace : 
Using permissions from /vmail//diederik-jan: mode=0700 gid=default
Oct  3 22:29:02 drieka dovecot: imap(diederik-jan): Debug: INBOX: 
Mailbox opened because: SELECT
Oct  3 22:29:04 drieka dovecot: imap(diederik-jan): Logged out in=31 
out=747


Took me a few tries to get this working though. You need to configure 
the permissions of /vmail correctly. Are you sure you're looking in 
the correct log file for finding errors?


You can execute the following to find out:

$ sudo doveadm log find
Looking for log files from /var/log
Debug: /var/log/syslog
Debug: /var/log/mail.log
Info: /var/log/syslog
Info: /var/log/mail.info
Info: /var/log/mail.log
Warning: /var/log/mail.warn
Warning: /var/log/syslog
Warning: /var/log/mail.info
Warning: /var/log/mail.log
Error: /var/log/mail.warn
Error: /var/log/syslog
Error: /var/log/mail.info
Error: /var/log/mail.err
Error: /var/log/mail.log
Fatal: /var/log/mail.warn
Fatal: /var/log/syslog
Fatal: /var/log/mail.info
Fatal: /var/log/mail.err
Fatal: /var/log/mail.log



Thank you for your reply, Stephan.

But did it create the home directory in the new account's mail folder? 
e.g. /vmail/domain/user/home?


Because this debug message is exactly similar to what I'm getting: 
"Debug: Home dir not found: /vmail//diederik-jan/home"


I have thought that there could be a permissions problem, but dovecot is 
able to create all directories inside the main folder except for that 
"home" folder.  I'm starting to think that maybe sieve is creating that 
folder on the old server automatically.


My vmail dir (NFS share) is set to 750 (vmail:vmail), but all new 
maildirs get created with 700.


Here's our log file output:

[root@triata4 ~]# doveadm log find
Looking for log files from /var/log
Debug: /var/log/dovecot-debug.log
Info: /var/log/dovecot-info.log
Warning: /var/log/maillog
Error: /var/log/maillog
Fatal: /var/log/maillog

Asai

Re: Home Directory Creation

[Asai via dovecot]

Mr. Timo,

I would presume you are busy with many responsibilities, but might you 
have a few minutes to consider this problem?


Or is there any other Dovecot expert who may be able to offer advice on 
how to get the home directories created?  Thank you for those who have 
helped offer advice on this already.


Asai

On 10/2/2019 5:08 PM, Asai via dovecot wrote:

Hello,

I spent the afternoon troubleshooting this, and after hours, I still 
can't see what I'm missing.


On the older version of Dovecot (2.2) it worked fine to create a new 
user, then Dovecot would create the home folder under the maildir 
folder as outlined in the documentation, simply by creating a new user 
in the database, and opening the new user account in the mail client.



# 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.7.2 (7372921a)
# Hostname: triata4
auth_debug = yes
auth_debug_passwords = yes
auth_mechanisms = plain login
auth_verbose = yes
auth_verbose_passwords = plain
debug_log_path = /var/log/dovecot-debug.log
deliver_log_format = msgid=%m: from=%f: %$
hostname = triata.globalchange.media
info_log_path = /var/log/dovecot-info.log
mail_debug = yes
mail_fsync = always
mail_home = /vmail/%d/%n/home
mail_location = maildir:/vmail/%d/%n
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 mime foreverypart 
extracttext

namespace inbox {
  inbox = yes
  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 =
  separator = /
  type = private
}
passdb {
  args = /etc/dovecot/dovecot-mysql.conf
  driver = sql
}
plugin {
  mail_log_fields = uid box msgid from flags
  sieve = 
file:/vmail/%d/%n/home/sieve;active=/vmail/%d/%n/home/.dovecot.sieve

  sieve_after = /etc/dovecot/sieve/junk-spam.sieve
  sieve_before = /etc/dovecot/sieve/junk-spam.sieve
  sieve_dir = /vmail/%d/%n/home/sieve
}
protocols = imap lmtp sieve
service auth {
  unix_listener /var/spool/postfix/private/auth {
    group = postfix
    mode = 0660
    user = postfix
  }
  unix_listener auth-master {
    group = vmail
    mode = 0660
    user = vmail
  }
  unix_listener auth-userdb {
    group = vmail
    mode = 0666
    user = vmail
  }
  user = root
}
service imap-login {
  inet_listener imap {
    port = 143
  }
  inet_listener imaps {
    port = 993
    ssl = yes
  }
}
service lmtp {
  unix_listener /var/spool/postfix/private/dovecot-lmtp {
    group = postfix
    mode = 0660
    user = postfix
  }
}
service managesieve-login {
  inet_listener sieve {
    port = 4190
  }
  process_min_avail = 0
  service_count = 1
  vsz_limit = 64 M
}
service managesieve {
  process_limit = 1024
}
service stats {
  unix_listener stats-reader {
    group = vmail
    mode = 0660
    user = vmail
  }
  unix_listener stats-writer {
    group = vmail
    mode = 0660
    user = vmail
  }
}
ssl_cert = 

Re: Home Directory Creation

[Asai via dovecot]

Hello,

I spent the afternoon troubleshooting this, and after hours, I still 
can't see what I'm missing.


On the older version of Dovecot (2.2) it worked fine to create a new 
user, then Dovecot would create the home folder under the maildir folder 
as outlined in the documentation, simply by creating a new user in the 
database, and opening the new user account in the mail client.



# 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.7.2 (7372921a)
# Hostname: triata4
auth_debug = yes
auth_debug_passwords = yes
auth_mechanisms = plain login
auth_verbose = yes
auth_verbose_passwords = plain
debug_log_path = /var/log/dovecot-debug.log
deliver_log_format = msgid=%m: from=%f: %$
hostname = triata.globalchange.media
info_log_path = /var/log/dovecot-info.log
mail_debug = yes
mail_fsync = always
mail_home = /vmail/%d/%n/home
mail_location = maildir:/vmail/%d/%n
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 mime foreverypart extracttext

namespace inbox {
  inbox = yes
  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 =
  separator = /
  type = private
}
passdb {
  args = /etc/dovecot/dovecot-mysql.conf
  driver = sql
}
plugin {
  mail_log_fields = uid box msgid from flags
  sieve = 
file:/vmail/%d/%n/home/sieve;active=/vmail/%d/%n/home/.dovecot.sieve

  sieve_after = /etc/dovecot/sieve/junk-spam.sieve
  sieve_before = /etc/dovecot/sieve/junk-spam.sieve
  sieve_dir = /vmail/%d/%n/home/sieve
}
protocols = imap lmtp sieve
service auth {
  unix_listener /var/spool/postfix/private/auth {
    group = postfix
    mode = 0660
    user = postfix
  }
  unix_listener auth-master {
    group = vmail
    mode = 0660
    user = vmail
  }
  unix_listener auth-userdb {
    group = vmail
    mode = 0666
    user = vmail
  }
  user = root
}
service imap-login {
  inet_listener imap {
    port = 143
  }
  inet_listener imaps {
    port = 993
    ssl = yes
  }
}
service lmtp {
  unix_listener /var/spool/postfix/private/dovecot-lmtp {
    group = postfix
    mode = 0660
    user = postfix
  }
}
service managesieve-login {
  inet_listener sieve {
    port = 4190
  }
  process_min_avail = 0
  service_count = 1
  vsz_limit = 64 M
}
service managesieve {
  process_limit = 1024
}
service stats {
  unix_listener stats-reader {
    group = vmail
    mode = 0660
    user = vmail
  }
  unix_listener stats-writer {
    group = vmail
    mode = 0660
    user = vmail
  }
}
ssl_cert = 

Re: Home Directory Creation

[Asai via dovecot]

On 10/1/2019 11:42 PM, Aki Tuomi via dovecot wrote:

Can you configure mail_debug=yes, try again, and post the logs?

Aki


Hello Aki,

This is the only piece of relevant info I've been getting in the logs, 
and I'm trying to figure out how I can get more debug data on this:



Oct 02 07:34:09 
imap(asai2@triata.globalchange.media)<43553><9fylXO6TtycKCgDu>: Debug: 
Home dir not found: /vmail/triata.globalchange.media/asai2/home

Re: Home Directory Creation

[Asai via dovecot]

Asai via dovecot skrev den 2019-10-02 03:00:


https://doc.dovecot.org/configuration_manual/home_directories_for_virtual_users/#home-directories-for-virtual-users 



mail_home = /var/vmail/%d/%n
mail_location = maildir:~/mail

little diff


Hello,

Thanks for replying.  I understand that that's in the docs, but I had to 
go with another option that's listed in the docs, which is to set up the 
home directory under the mail directory.  This is due to backwards 
compatibility needs.


Asai

Home Directory Creation

[Asai via dovecot]

Hello,

I hate to have to ask this, but... why isn't the home directory being 
created automatically?


Due to legacy compatibility we've had to use this type of home dir config:

mail_location = maildir:/vmail/%d/%n
mail_home = /vmail/%d/%n/home

We're in the middle of upgrading to new hardware, and so I'm migrating 
configs to the new server, Dovecot 2.3.7 and Postfix 3.4.6


On our old server (Dovecot 2.2, Postfix 2.11) the home directory gets 
created automatically with a new user, but not on this one. The Dovecot 
debug logs just say "home dir not found."


Can anyone point me in the right direction?

Thank you,
Asai

Re: NFS Locking and Submission Service Authentication

[Asai via dovecot]

On 9/25/2019 4:17 PM, Adi Pircalabu via dovecot wrote:


How is your NFS export mounted on the client? Can you post the output 
of "egrep nfs /proc/mounts"?



Hi Adi, thank you for your reply.

Turns out that the problem was that the firewall on the Dovecot server 
needed to be opened to allow the NFS server to communicate lock 
commands, so I made a firewall exception and it's working now.


Asai

Re: NFS Locking and Submission Service Authentication

[Asai via dovecot]

On 9/25/2019 2:06 PM, Michael Peddemors via dovecot wrote:
For the record, ever since the last patches for NFS got committed, we 
don't see locking issues over NFS in general across all our platforms, 
but it also depends on how you configure your NFS server.


You might find that this is not a dovecot issue, but an NFS issue.

You might want to post more about your NFS setup(s) and then someone 
on the list might better assist you.


Thank you, Michael, for the advice.  Turns out the NFS locking problem 
was a firewall issue on the Dovecot server, which is now fixed.


Does anyone have any advice on the the Submission Service authentication?

For example, this is what's coming up in the logs:

Sep 25 14:39:04 triata4 dovecot: submission-login: Client has quit the connection (auth 
failed, 1 attempts in 2 secs): user=<%u>, method=PLAIN, rip=10.1.1.99, lip=10.1.1.99, 
TLS, session=

As you can see, it's choking on user=<%u>, which it's not expanding, so 
is there a variable I can put in there, or is it strictly hard coded 
authentication?


Thanks.

NFS Locking and Submission Service Authentication

[Asai via dovecot]

Greetings,

We're in the process of upgrading our Dovecot server to new hardware and 
new expanded storage.  We planned on using an NFS share for the mail 
storage, as we're running Postfix / Dovecot on a VM and wanted to 
separate out the mail storage from the VM for backup reasons.


I read as much as I could find on line regarding configuring Dovecot to 
use NFS, and set it up as best I could, but I'm still running into lock 
errors e.g.:


Sep 25 10:30:35 triata4 dovecot: 
imap(user@triata.globalchange.media)<75580>: Error: 
fcntl(/vmail/triata.globalchange.media/user/dovecot.index.log, write-lock, F_SETLKW) 
locking failed: No locks available
Sep 25 10:30:35 triata4 dovecot: 
imap(user@triata.globalchange.media)<75580>: Error: 
mail_index_wait_lock_fd() failed with file 
/vmail/triata.globalchange.media/user/dovecot.index.log: No locks available

Also, I have been trying to configure the Dovecot submission service to 
authenticate with Postfix, but I keep running into errors which are 
related to how I'm configuring the authentication.  How do we set the 
user@domain and password string for submission in the configs?


Thank you.

Please see doveconf -n below, if you see any other errors in this 
config, I'd be grateful if you pointed them out:


# 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.7.2 (7372921a)
# OS: Linux 3.10.0-957.27.2.el7.x86_64 x86_64 CentOS Linux release 
7.6.1810 (Core)  nfs

auth_debug = yes
auth_debug_passwords = yes
auth_mechanisms = plain login
auth_verbose = yes
auth_verbose_passwords = plain
debug_log_path = /var/log/dovecot-debug.log
deliver_log_format = msgid=%m: from=%f: %$
hostname = triata.globalchange.media
mail_debug = yes
mail_fsync = always
mail_home = /vmail/%d/%n/home
mail_location = maildir:/vmail/%d/%n
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 mime foreverypart extracttext

namespace inbox {
  inbox = yes
  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 =
  separator = /
  type = private
}
passdb {
  args = /etc/dovecot/dovecot-mysql.conf
  driver = sql
}
plugin {
  mail_log_fields = uid box msgid from flags
  sieve = file:/vmail/%d/%n/sieve;active=/vmail/%d/%n/.dovecot.sieve
}
protocols = imap lmtp submission sieve
service auth {
  unix_listener /var/spool/postfix/private/auth {
    mode = 0666
  }
  unix_listener auth-userdb {
    group = vmail
    mode = 0666
    user = vmail
  }
}
service imap-login {
  inet_listener imap {
    port = 143
  }
  inet_listener imaps {
    port = 993
    ssl = yes
  }
}
service lmtp {
  unix_listener lmtp {
    mode = 0666
  }
}
service managesieve-login {
  inet_listener sieve {
    port = 4190
  }
  process_min_avail = 0
  service_count = 1
  vsz_limit = 64 M
}
service managesieve {
  process_limit = 1024
}
service submission-login {
  inet_listener submission {
    port = 587
  }
}
ssl_cert = 

Re: Dovecot Logging and Shell Script Hang

[Asai via dovecot]

On Feb 27, 2019, at 11:00 AM, Aki Tuomi via dovecot  wrote:
> 
> 
>> On 27 February 2019 18:49 Asai via dovecot  wrote:
>> 
>> 
>> Greetings,
>> 
>> We have a PHP based shell script that runs a doveadm backup routine.
>> 
>> This script was running just fine, and then we turned on more logging for 
>> Dovecot (enabled the mail_log plugin). For some reason, once this was done, 
>> the shell script would run for a few minutes and then hang, as it added more 
>> log messages to the dsync STDOUT. Once the mail_log plugin was disabled, it 
>> ran without hanging.
>> 
>> Is there any way to run doveadm and temporarily suspend the mail_log plugin? 
>> Or is there a better way to do this?
>> 
>> Thanks for the insights.
>> 
>> Asai
>> 
> 
> You might want to enable mail_log plugin for imap/pop3 protocols only.
> 
> protocol imap {
>   mail_plugins = $mail_plugins mail_log
> }
> 
> protocol pop3 {
>   mail_plugins = $mail_plugins mail_log
> }
> 
> Aki

Thank you, Aki,  I will try that.

Dovecot Logging and Shell Script Hang

[Asai via dovecot]

Greetings,

We have a PHP based shell script that runs a doveadm backup routine.

This script was running just fine, and then we turned on more logging for 
Dovecot (enabled the mail_log plugin).  For some reason, once this was done, 
the shell script would run for a few minutes and then hang, as it added more 
log messages to the dsync STDOUT.  Once the mail_log plugin was disabled, it 
ran without hanging.

Is there any way to run doveadm and temporarily suspend the mail_log plugin?  
Or is there a better way to do this?

Thanks for the insights.
Asai

iOS Mail Client Not Copying to Sent Folder

[Asai]

Greetings,

We have many iOS clients, and some report that they’re having problems with iOS 
mail copying messages to their Sent folder.  This happens 2 - 3 times per day, 
and the phone just says Sending and the client never knows if it sends.  Client 
says apparently email DOES go out, but there is no recording of it.  This is 
usually on our LAN.

We’re not sure if this is solved via Postfix or Dovecot, or maybe something 
else, so I’m posting this message on both forums as a start.  Can anyone point 
us in the right direction here?

Running Postfix 2.11.1 and Dovecot ee 2.2.18.2

see doveconf -n below:

# 2.2.18.2 (866bffbafde7): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.8 (73d4f6cd676a)
# OS: Linux 2.6.32-358.el6.x86_64 x86_64 CentOS release 6.4 (Final) ext4
auth_mechanisms = plain login
auth_verbose = yes
auth_verbose_passwords = plain
deliver_log_format = msgid=%m: from=%f: %$
lock_method = dotlock
mail_home = /vmail/%d/%n/home
mail_location = maildir:/vmail/%d/%n
mail_plugins = " notify"
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 = yes
  location =
  prefix =
  separator = /
  type = private
}
passdb {
  args = /etc/dovecot/dovecot-mysql.conf
  driver = sql
}
plugin {
  mail_log_events = delete expunge copy mailbox_delete flag_change append 
mailbox_rename
  mail_log_fields = box msgid from flags
  sieve = /vmail/%d/%n/home/.dovecot.sieve
  sieve_before = /etc/dovecot/sieve/junk-spam.sieve
  sieve_default = /etc/dovecot/sieve/junk-spam.sieve
  sieve_dir = /vmail/%d/%n/home/sieve
}
protocols = imap lmtp sieve
service auth {
  unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0666
user = postfix
  }
  unix_listener auth-master {
group = vmail
mode = 0660
user = vmail
  }
  unix_listener auth-userdb {
mode = 0660
user = vmail
  }
  user = root
}
service imap-login {
  process_limit = 200
  process_min_avail = 16
  service_count = 0
  vsz_limit = 0
}
service managesieve-login {
  inet_listener sieve {
port = 4190
  }
  process_min_avail = 0
  service_count = 1
  vsz_limit = 64 M
}
ssl_cert = 

Re: Dovecot Oy merger with Open-Xchange AG

[Asai]

Agreed.  I think this is a positive move for Dovecot and Timo, Mikko, et 
al.  I think only good will come of this for open source communications.


On 3/25/15 2:46 PM, Andreas Kasenides wrote:
I hate to have started this, especially the "sister" thread that has 
dissented into a flame war of what is OSS.


Let me say that I believe there is nothing wrong trying to make money 
on ones efforts. Actually it is a must. How can anyone continue to put 
efforts into a project when there is no reward? Especially when most 
of the effort is by a single individual. Secondly there comes a point 
in time when any project needs help to advance. Any one individual 
will be unable to manage all the things that need to be done. It will 
either become a team effort of individuals employed elsewhere or 
somehow enter the commercial sector in some form. Both of these models 
have many examples out there and in the mean time maintaining their 
OSS root and community.


What I was mostly worried about was a sudden and rapid 
commercialization of the project in such a way that it completely 
disappears from the OSS community. I will give you an extreme example 
that we had the pleasure to be involved as payed customers and 
debugging contributors: KnowledgeTree DMS.  If you do not know the 
story you will simply not find it. After years of the community 
contributing to the project a sudden shift to complete 
commercialization destroyed the project entirely: ie sourceforge 
project closed, source code disappeared, mailing lists vanished even 
the domain name name closed down. If it wasn't for third party 
storage/downloading sites the project source code would have been 
practically non-existent. I consider such behavior firstly immoral 
since a project's success is not only its design but largely also its 
debugging, mostly done by thousands of unknown helpers writing their 
experiences and problems in mailing lists.


I hope Timo manages well, keeps the community going but also makes a 
living (or a ton of money ) out of Dovecot. He deserves it. It is not 
impossible, others have done so successfully.



On 25/03/15 22:46, Daniel Miller wrote:

On 3/19/2015 3:26 AM, Timo Sirainen wrote:

Hi all,

Today I can finally announce that Dovecot Oy company has merged with 
Open-Xchange AG. This helps us to get more Dovecot developers, 
support people and so on. Most importantly, eventually it should 
allow me to get back to doing what I like the most: Designing new 
and interesting stuff for Dovecot and perfecting the old stuff :) OX 
is a great match to Dovecot going forward. They also really like 
open source and share our plans for the future. Nothing big will 
change as a result of this merger: Dovecot will stay Dovecot with 
its own name and release schedules. We're not going to force OX and 
Dovecot to be the same product, other than having a somewhat deeper 
integration between them.




My initial impression is...sounds great!  Then, after further 
thought, and watching the flame war, I've changed my mind to...sounds 
great!


I'm operating under the assumption that you are continuing to be in 
charge of Dovecot and will choose what and how to implement changes 
and fixes.  I'm further operating under the assumption that you may 
choose to have certain features, appropriate for larger 
installations, that you will want to receive compensation for from 
your users.  And I'm assuming that by having OX behind you, those 
initial assumptions remain - Dovecot remains your baby, you will grow 
it as you see fit - but now you've got some financial backing that 
allows you more freedom to continue to develop Dovecot for 
general-purpose use while reasonably having certain features 
developed to support the paid model.


If I'm mistaken then please correct me - but I'm seeing nothing but 
upside.  Certainly for you, and if you were to abandon open source 
Dovecot today (which I've seen absolutely no indication) you've 
already provided a tool that has a significant user base and you 
deserve to be rewarded for it.  But based on your previous actions 
and your original post, and I have no reason not to take you at your 
word, this sounds like a win/win for Dovecot developers and users. 
Congratulations!




--
--asai

Replication Advice Needed

[Asai]

I successfully set up Dovecot replication, having 2 servers syncing with 
each other.  While I had both servers in the same room on a Gigabit 
network, they were syncing fine.  But I took one to another location, 
and syncing was turned off for about 2 weeks.  Now I've turned both back 
on, they're sort of syncing, but not really.  The one remote server is 
not populating emails into various folders and it really should be 
cranking to sync those emails.


Do anyone have any insights on how we could troubleshoot this?

--
--Asai

Dovecot replication causing deleted emails to reappear

[Asai]

Greetings,

I've set up replication successfully on two Dovecot servers.  I had fully 
synced the servers but then took one offline for 2 weeks.  When I restored it, 
the servers synced but ended up replacing deleted emails in random people's 
inboxes.

I'm using maildir.

Does anyone have any insights as to correcting this issue?

Asai

--
--Asai

Some Dsync Replication Errors

[Asai]

Greetings,

Working on setting up replication and ran into some errors I have 
questions about and wondering if there's something I need to change.


This one is fairly common:

Sep  3 12:58:25 molecular dovecot: dsync-server(u...@domain.org): 
Warning: Failed to do incremental sync for mailbox INBOX, retry with a 
full sync (Modseq 100298 no longer in transaction log)


These two I ran into yesterday and today:

Sep  2 11:13:32 molecular dovecot: dsync-server(us...@domain2.org): 
Error: Timeout during state=slave_recv_last_common


Sep  3 12:52:08 molecular dovecot: dsync-server(us...@domain3.org): 
Error: read(remote.mailserver.net) failed: EOF



Configs:

mail_plugins = notify replication

service doveadm {

inet_listener {

port = 1234

}

}

service replicator {

process_min_avail = 1

unix_listener replicator-doveadm {

mode = 0600

}

}

service aggregator {

fifo_listener replication-notify-fifo {

user = vmail

mode = 0600

}

unix_listener replication-notify {

user = vmail

mode = 0600

}

}

plugin {

mail_replica = tcp:sub.domain.org:1234

}


And doveconf -n:

[root@molecular dovecot]# doveconf -n

# 2.2.13.16 (94835dd63163): /etc/dovecot/dovecot.conf

# OS: Linux 2.6.32-431.el6.x86_64 x86_64 Scientific Linux release 6.5 
(Carbon) ext4


auth_mechanisms = plain login

auth_verbose = yes

auth_verbose_passwords = plain

deliver_log_format = msgid=%m: from=%f: %$

doveadm_password = secret

doveadm_port = 1234

mail_debug = yes

mail_home = /vmail/%d/%n/home

mail_location = maildir:/vmail/%d/%n

mail_plugins = notify replication

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

ihave duplicate

namespace {

  inbox = yes

  location =

  prefix =

  separator = /

  type = private

}

passdb {

  args = /etc/dovecot/dovecot-mysql.conf

  driver = sql

}

plugin {

  mail_log_fields = box msgid from flags

  mail_replica = tcp:sub.domain.org:1234

  sieve = /vmail/%d/%n/home/.dovecot.sieve

  sieve_dir = /vmail/%d/%n/home/sieve

}

protocols = imap pop3 lmtp sieve

service aggregator {

  fifo_listener replication-notify-fifo {

mode = 0600

user = vmail

  }

  unix_listener replication-notify {

mode = 0600

user = vmail

  }

}

service auth {

  unix_listener /var/spool/postfix/private/auth {

group = postfix

mode = 0660

user = postfix

  }

  unix_listener auth-master {

group = vmail

mode = 0660

user = vmail

  }

  unix_listener auth-userdb {

mode = 0660

user = vmail

  }

  user = root

}

service doveadm {

  inet_listener {

port = 1234

  }

}

service imap-login {

  process_min_avail = 3

  service_count = 0

  vsz_limit = 0

}

service managesieve-login {

  inet_listener sieve {

port = 4190

  }

  process_min_avail = 0

  service_count = 1

  vsz_limit = 64 M

}

service replicator {

  process_min_avail = 1

  unix_listener replicator-doveadm {

mode = 0600

  }

}

ssl_cert = 

Re: Dovecot Replication of Maildirs: Couldn't create lock file ... no such file or directory

[Asai]

Problem solved with changing the location of the home dir, however, is 
there a reliable way to do this on the "master" server with all the 
production data in place?


--Asai

On 8/27/14 11:47 AM, Asai wrote:

Greetings,

I'm setting up replication and am getting this error from the server 
where the replicated mails are being initially created:


Aug 27 11:03:53 molecular dovecot: dsync-server(u...@domain.org): 
Error: Couldn't create lock 
/vmail/domain.org/user/home/.dovecot-sync.lock: No such file or directory


Can anyone shed some light on this?

Here's the Replicator config of the server which is being replicated 
to (initially), and it is identical basically with the "master" server:


mail_plugins = notify replication

service doveadm {

inet_listener {

port = 1234

}

}

service replicator {

process_min_avail = 1

unix_listener replicator-doveadm {

mode = 0600

}

}

service aggregator {

fifo_listener replication-notify-fifo {

user = vmail

mode = 0600

}

unix_listener replication-notify {

user = vmail

mode = 0600

}

}

plugin {

mail_replica = tcp:sub.domain.org:1234

}


And doveconf -n:

[root@molecular dovecot]# doveconf -n

# 2.2.13.16 (94835dd63163): /etc/dovecot/dovecot.conf

# OS: Linux 2.6.32-431.el6.x86_64 x86_64 Scientific Linux release 6.5 
(Carbon) ext4


auth_mechanisms = plain login

auth_verbose = yes

auth_verbose_passwords = plain

deliver_log_format = msgid=%m: from=%f: %$

doveadm_password = secret

doveadm_port = 1234

mail_debug = yes

mail_home = /vmail/%d/%n/home

mail_location = maildir:/vmail/%d/%n

mail_plugins = notify replication

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

ihave duplicate

namespace {

  inbox = yes

  location =

  prefix =

  separator = /

  type = private

}

passdb {

  args = /etc/dovecot/dovecot-mysql.conf

  driver = sql

}

plugin {

  mail_log_fields = box msgid from flags

  mail_replica = tcp:sub.domain.org:1234

  sieve = /vmail/%d/%n/home/.dovecot.sieve

  sieve_dir = /vmail/%d/%n/home/sieve

}

protocols = imap pop3 lmtp sieve

service aggregator {

  fifo_listener replication-notify-fifo {

mode = 0600

user = vmail

  }

  unix_listener replication-notify {

mode = 0600

user = vmail

  }

}

service auth {

  unix_listener /var/spool/postfix/private/auth {

group = postfix

mode = 0660

user = postfix

  }

  unix_listener auth-master {

group = vmail

mode = 0660

user = vmail

  }

  unix_listener auth-userdb {

mode = 0660

user = vmail

  }

  user = root

}

service doveadm {

  inet_listener {

port = 1234

  }

}

service imap-login {

  process_min_avail = 3

  service_count = 0

  vsz_limit = 0

}

service managesieve-login {

  inet_listener sieve {

port = 4190

  }

  process_min_avail = 0

  service_count = 1

  vsz_limit = 64 M

}

service replicator {

  process_min_avail = 1

  unix_listener replicator-doveadm {

mode = 0600

  }

}

ssl_cert = lrwxrwxrwx   1 rootroot   25 Aug 26 16:50 dovecot.conf -> 
/etc/dovecot/dovecot.conf


drwxr-xr-x.  2 rootroot 4096 Aug 22 09:39 empty

srw-rw-rw-   1 rootroot0 Aug 27 11:42 imap-urlauth

srw---   1 dovecot root0 Aug 27 11:42 imap-urlauth-worker

srw-rw-rw-   1 rootroot0 Aug 27 11:42 indexer

srw---   1 dovecot root0 Aug 27 11:42 indexer-worker

srw---   1 rootroot0 Aug 27 11:42 ipc

srw-rw-rw-   1 rootroot0 Aug 27 11:42 lmtp

srw---   1 rootroot0 Aug 27 11:42 log-errors

drwxr-x---.  2 rootdovenull 4096 Aug 27 11:42 login

-rw---   1 rootroot5 Aug 26 16:50 master.pid

-rw-r--r--   1 rootroot   22 Aug 26 16:50 mounts

srw---   1 vmail   root0 Aug 27 11:42 replication-notify

prw---   1 vmail   root0 Aug 27 11:42 replication-notify-fifo

srw---   1 dovecot root0 Aug 27 11:42 replicator

srw---   1 dovecot root0 Aug 27 11:42 replicator-doveadm

srw-rw-rw-   1 rootroot0 Aug 27 11:42 ssl-params

srw---   1 rootroot0 Aug 27 11:42 stats

prw---   1 rootroot0 Aug 27 11:42 stats-mail

drwxr-x---.  2 rootdovenull 4096 Aug 27 11:42 token-login

Re: Dovecot Replication of Maildirs: Couldn't create lock file ... no such file or directory

[Asai]

The error, I presume, is that the home folder is unable to be created in 
the user's directory.


--Asai

On 8/27/14 11:47 AM, Asai wrote:

Greetings,

I'm setting up replication and am getting this error from the server 
where the replicated mails are being initially created:


Aug 27 11:03:53 molecular dovecot: dsync-server(u...@domain.org): 
Error: Couldn't create lock 
/vmail/domain.org/user/home/.dovecot-sync.lock: No such file or directory


Can anyone shed some light on this?

Here's the Replicator config of the server which is being replicated 
to (initially), and it is identical basically with the "master" server:


mail_plugins = notify replication

service doveadm {

inet_listener {

port = 1234

}

}

service replicator {

process_min_avail = 1

unix_listener replicator-doveadm {

mode = 0600

}

}

service aggregator {

fifo_listener replication-notify-fifo {

user = vmail

mode = 0600

}

unix_listener replication-notify {

user = vmail

mode = 0600

}

}

plugin {

mail_replica = tcp:sub.domain.org:1234

}


And doveconf -n:

[root@molecular dovecot]# doveconf -n

# 2.2.13.16 (94835dd63163): /etc/dovecot/dovecot.conf

# OS: Linux 2.6.32-431.el6.x86_64 x86_64 Scientific Linux release 6.5 
(Carbon) ext4


auth_mechanisms = plain login

auth_verbose = yes

auth_verbose_passwords = plain

deliver_log_format = msgid=%m: from=%f: %$

doveadm_password = secret

doveadm_port = 1234

mail_debug = yes

mail_home = /vmail/%d/%n/home

mail_location = maildir:/vmail/%d/%n

mail_plugins = notify replication

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

ihave duplicate

namespace {

  inbox = yes

  location =

  prefix =

  separator = /

  type = private

}

passdb {

  args = /etc/dovecot/dovecot-mysql.conf

  driver = sql

}

plugin {

  mail_log_fields = box msgid from flags

  mail_replica = tcp:sub.domain.org:1234

  sieve = /vmail/%d/%n/home/.dovecot.sieve

  sieve_dir = /vmail/%d/%n/home/sieve

}

protocols = imap pop3 lmtp sieve

service aggregator {

  fifo_listener replication-notify-fifo {

mode = 0600

user = vmail

  }

  unix_listener replication-notify {

mode = 0600

user = vmail

  }

}

service auth {

  unix_listener /var/spool/postfix/private/auth {

group = postfix

mode = 0660

user = postfix

  }

  unix_listener auth-master {

group = vmail

mode = 0660

user = vmail

  }

  unix_listener auth-userdb {

mode = 0660

user = vmail

  }

  user = root

}

service doveadm {

  inet_listener {

port = 1234

  }

}

service imap-login {

  process_min_avail = 3

  service_count = 0

  vsz_limit = 0

}

service managesieve-login {

  inet_listener sieve {

port = 4190

  }

  process_min_avail = 0

  service_count = 1

  vsz_limit = 64 M

}

service replicator {

  process_min_avail = 1

  unix_listener replicator-doveadm {

mode = 0600

  }

}

ssl_cert = lrwxrwxrwx   1 rootroot   25 Aug 26 16:50 dovecot.conf -> 
/etc/dovecot/dovecot.conf


drwxr-xr-x.  2 rootroot 4096 Aug 22 09:39 empty

srw-rw-rw-   1 rootroot0 Aug 27 11:42 imap-urlauth

srw---   1 dovecot root0 Aug 27 11:42 imap-urlauth-worker

srw-rw-rw-   1 rootroot0 Aug 27 11:42 indexer

srw---   1 dovecot root0 Aug 27 11:42 indexer-worker

srw---   1 rootroot0 Aug 27 11:42 ipc

srw-rw-rw-   1 rootroot0 Aug 27 11:42 lmtp

srw---   1 rootroot0 Aug 27 11:42 log-errors

drwxr-x---.  2 rootdovenull 4096 Aug 27 11:42 login

-rw---   1 rootroot5 Aug 26 16:50 master.pid

-rw-r--r--   1 rootroot   22 Aug 26 16:50 mounts

srw---   1 vmail   root0 Aug 27 11:42 replication-notify

prw---   1 vmail   root0 Aug 27 11:42 replication-notify-fifo

srw---   1 dovecot root0 Aug 27 11:42 replicator

srw---   1 dovecot root0 Aug 27 11:42 replicator-doveadm

srw-rw-rw-   1 rootroot0 Aug 27 11:42 ssl-params

srw---   1 rootroot0 Aug 27 11:42 stats

prw---   1 rootroot0 Aug 27 11:42 stats-mail

drwxr-x---.  2 rootdovenull 4096 Aug 27 11:42 token-login

Dovecot Replication of Maildirs: Couldn't create lock file ... no such file or directory

[Asai]

Greetings,

I'm setting up replication and am getting this error from the server 
where the replicated mails are being initially created:


Aug 27 11:03:53 molecular dovecot: dsync-server(u...@domain.org): Error: 
Couldn't create lock /vmail/domain.org/user/home/.dovecot-sync.lock: No 
such file or directory


Can anyone shed some light on this?

Here's the Replicator config of the server which is being replicated to 
(initially), and it is identical basically with the "master" server:


mail_plugins = notify replication

service doveadm {

inet_listener {

port = 1234

}

}

service replicator {

process_min_avail = 1

unix_listener replicator-doveadm {

mode = 0600

}

}

service aggregator {

fifo_listener replication-notify-fifo {

user = vmail

mode = 0600

}

unix_listener replication-notify {

user = vmail

mode = 0600

}

}

plugin {

mail_replica = tcp:sub.domain.org:1234

}


And doveconf -n:

[root@molecular dovecot]# doveconf -n

# 2.2.13.16 (94835dd63163): /etc/dovecot/dovecot.conf

# OS: Linux 2.6.32-431.el6.x86_64 x86_64 Scientific Linux release 6.5 (Carbon) 
ext4

auth_mechanisms = plain login

auth_verbose = yes

auth_verbose_passwords = plain

deliver_log_format = msgid=%m: from=%f: %$

doveadm_password = secret

doveadm_port = 1234

mail_debug = yes

mail_home = /vmail/%d/%n/home

mail_location = maildir:/vmail/%d/%n

mail_plugins = notify replication

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
ihave duplicate

namespace {

  inbox = yes

  location =

  prefix =

  separator = /

  type = private

}

passdb {

  args = /etc/dovecot/dovecot-mysql.conf

  driver = sql

}

plugin {

  mail_log_fields = box msgid from flags

  mail_replica = tcp:sub.domain.org:1234

  sieve = /vmail/%d/%n/home/.dovecot.sieve

  sieve_dir = /vmail/%d/%n/home/sieve

}

protocols = imap pop3 lmtp sieve

service aggregator {

  fifo_listener replication-notify-fifo {

mode = 0600

user = vmail

  }

  unix_listener replication-notify {

mode = 0600

user = vmail

  }

}

service auth {

  unix_listener /var/spool/postfix/private/auth {

group = postfix

mode = 0660

user = postfix

  }

  unix_listener auth-master {

group = vmail

mode = 0660

user = vmail

  }

  unix_listener auth-userdb {

mode = 0660

user = vmail

  }

  user = root

}

service doveadm {

  inet_listener {

port = 1234

  }

}

service imap-login {

  process_min_avail = 3

  service_count = 0

  vsz_limit = 0

}

service managesieve-login {

  inet_listener sieve {

port = 4190

  }

  process_min_avail = 0

  service_count = 1

  vsz_limit = 64 M

}

service replicator {

  process_min_avail = 1

  unix_listener replicator-doveadm {

mode = 0600

  }

}

ssl_cert =  
/etc/dovecot/dovecot.conf

drwxr-xr-x.  2 rootroot 4096 Aug 22 09:39 empty

srw-rw-rw-   1 rootroot0 Aug 27 11:42 imap-urlauth

srw---   1 dovecot root0 Aug 27 11:42 imap-urlauth-worker

srw-rw-rw-   1 rootroot0 Aug 27 11:42 indexer

srw---   1 dovecot root0 Aug 27 11:42 indexer-worker

srw---   1 rootroot0 Aug 27 11:42 ipc

srw-rw-rw-   1 rootroot0 Aug 27 11:42 lmtp

srw---   1 rootroot0 Aug 27 11:42 log-errors

drwxr-x---.  2 rootdovenull 4096 Aug 27 11:42 login

-rw---   1 rootroot5 Aug 26 16:50 master.pid

-rw-r--r--   1 rootroot   22 Aug 26 16:50 mounts

srw---   1 vmail   root0 Aug 27 11:42 replication-notify

prw---   1 vmail   root0 Aug 27 11:42 replication-notify-fifo

srw---   1 dovecot root0 Aug 27 11:42 replicator

srw---   1 dovecot root0 Aug 27 11:42 replicator-doveadm

srw-rw-rw-   1 rootroot0 Aug 27 11:42 ssl-params

srw---   1 rootroot0 Aug 27 11:42 stats

prw---   1 rootroot0 Aug 27 11:42 stats-mail

drwxr-x---.  2 rootdovenull 4096 Aug 27 11:42 token-login

--
--Asai

Re: Dovecot EE on SciLinux 6.5: No Config Files in /etc

[Asai]

On 16 Jul 2014, at 18:24, Asai  wrote:


I tried installing Dovecot EE on Scientific 6.5 yesterday, but there was no 
repo under that release version, so I hardcoded the release version to 6 in 
yum.repos.d/dovecot.repo.

That worked, but when I installed, it didn't install any default configuration 
files.  /etc/dovecot was empty.

Is that to be expected for EE?

It's expected, although I guess maybe there could be some README file. The main 
problem I've noticed with some other RPMs have been that if I add a new file to 
/etc/dovecot/conf.d/ it gets included when upgrading the RPM. But if that new file 
depends on changes that were made to other config files, then adding the file 
breaks the whole configuration completely. This is what happened in v2.0 -> 
v2.1 atrpms RPM upgrade. I don't want that ever to happen with dovecot-ee. Maybe 
there would be some other ways to solve that, but the simplest solution was to 
have no config files.
Thanks for the info.  Perhaps you could put a README in /etc/dovecot 
where the configs would normally be?

Re: Dovecot Replication: First Run

[Asai]

If what I wrote is a little cryptic, I am talking about using doveadm to 
sync between two servers.


--Asai

On 7/17/14 8:47 AM, Asai wrote:

Greetings,

I'm working on building a redundant Dovecot server which will be 
replicated with my original.  I would like to know if there's any 
potential problems I could run into in running this for the first 
time. For example, during an initial sync is it possible for the new 
server to sync improperly with the original and delete all of the 
emails on the original?


Are there any gotchas that I should be aware of when doing a first run?

Dovecot Replication: First Run

[Asai]

Greetings,

I'm working on building a redundant Dovecot server which will be 
replicated with my original.  I would like to know if there's any 
potential problems I could run into in running this for the first time. 
For example, during an initial sync is it possible for the new server to 
sync improperly with the original and delete all of the emails on the 
original?


Are there any gotchas that I should be aware of when doing a first run?

--
--Asai

Dovecot EE on SciLinux 6.5: No Config Files in /etc

[Asai]

Greetings,

I tried installing Dovecot EE on Scientific 6.5 yesterday, but there was 
no repo under that release version, so I hardcoded the release version 
to 6 in yum.repos.d/dovecot.repo.


That worked, but when I installed, it didn't install any default 
configuration files.  /etc/dovecot was empty.


Is that to be expected for EE?

--
--Asai

Re: Android Sync Doesn't Work Too Good

[Asai]

Am 01.07.2014 21:02, schrieb Asai:

Greetings,

I'm getting reports from a user who's reading and deleting mail on
Thunderbird, but read flags and deletions don't show up in his Android
phone.  He's using the native Android mail app with the newest Android OS.

in imap mode ?

Yes

My question is, where do I start with troubleshooting this kind of
issue?  Thanks for anyone's insight here. We're using Dovecot 2.2.13.


look at the verbose logs, and dont expect android app to be a good imap
client
( i never tried it that kind ) , better use k9 Mail with imap on Android


https://code.google.com/p/k9mail/


Thanks, Robert.  This user did once use K9, but they like the native app
better...  I suggested to them that they double check the syncing in K9
rather than native.

If it's the look of K9 they don't like, can I recommend K-@ Mail. K-@
Mail uses K9Mail's mail engines, but puts a modern interface on the top.

Thanks for the recommendation, I've passed it on to the user.

Re: Android Sync Doesn't Work Too Good

[Asai]

Am 01.07.2014 21:02, schrieb Asai:

Greetings,

I'm getting reports from a user who's reading and deleting mail on
Thunderbird, but read flags and deletions don't show up in his Android
phone.  He's using the native Android mail app with the newest Android OS.

in imap mode ?

Yes



My question is, where do I start with troubleshooting this kind of
issue?  Thanks for anyone's insight here. We're using Dovecot 2.2.13.


look at the verbose logs, and dont expect android app to be a good imap
client
( i never tried it that kind ) , better use k9 Mail with imap on Android


https://code.google.com/p/k9mail/

Thanks, Robert.  This user did once use K9, but they like the native app 
better...  I suggested to them that they double check the syncing in K9 
rather than native.

Android Sync Doesn't Work Too Good

[Asai]

Greetings,

I'm getting reports from a user who's reading and deleting mail on 
Thunderbird, but read flags and deletions don't show up in his Android 
phone.  He's using the native Android mail app with the newest Android OS.


My question is, where do I start with troubleshooting this kind of 
issue?  Thanks for anyone's insight here. We're using Dovecot 2.2.13.


--
--Asai

Re: [Dovecot] 2.2.12 RPM Needed

[Asai]

I found that there's a commercial Dovecot repo, which we're more than 
happy to pay for access to. Thanks, Timo!


--Asai

On 4/24/14 12:23 PM, Reindl Harald wrote:


Am 24.04.2014 19:37, schrieb Asai:

I'm not very experienced in building Source RPMs and we're in need of a Dovecot 
RPM for version 2.2.12 for CentOS
5.  It seems that the  ATRPMs repo maintained by Axel Thimm hasn't seen much 
activity lately and the task of
updating a source RPM is more than I have time for as a busy developer who does 
systems admin on the side.

Could anybody recommend another repo where there would be the latest Dovecot 
binaries?  Or perhaps tell me of any
gotchas and catches which might arise if I go ahead and build 2.2.12 from 
source over the RPM I currently have
installed (2.2.10)?

you only need to replace the tarball and the version in the SPEC
and rebuild the package - for monir updates you don't need anything
else if upstream has no broken release strategy, dovecot's is fine

i am building dovecot the last two years without any SPEC change
except version and changelog - but you won't be happy with my
stripped down SPEC following our infrastructure (no configs etc.)

[Dovecot] 2.2.12 RPM Needed

[Asai]

Greetings,

I'm not very experienced in building Source RPMs and we're in need of a 
Dovecot RPM for version 2.2.12 for CentOS 5.  It seems that the  ATRPMs 
repo maintained by Axel Thimm hasn't seen much activity lately and the 
task of updating a source RPM is more than I have time for as a busy 
developer who does systems admin on the side.


Could anybody recommend another repo where there would be the latest 
Dovecot binaries?  Or perhaps tell me of any gotchas and catches which 
might arise if I go ahead and build 2.2.12 from source over the RPM I 
currently have installed (2.2.10)?


Thanks.

--
--Asai

Re: [Dovecot] Dsync Errors

[Asai]

Timo, you're amazing.  Thank you.

--Asai

On 2/7/14 1:07 PM, Timo Sirainen wrote:

On 30.1.2014, at 11.06, Asai  wrote:


Maybe this error sheds some light on it:

Panic: file dsync-brain-mailbox-tree-sync.c: line 111 
(dsync_brain_mailbox_tree_sync_change): assertion failed: 
(brain->no_backup_overwrite)

Fixed by http://hg.dovecot.org/dovecot-2.2/rev/fbc8fe46dfce

Re: [Dovecot] Dsync Errors

[Asai]

I see Timo addressed this problem with this reply ( from thread 
"[Dovecot] reproducible dsync backup panic (dovecot 2.2.7)/Fri Dec 20 
00:37:21 EET 2013")/, but basically I don't understand how to go about 
doing this:


Can you get it to dump core and use

gdb /usr/bin/doveadm core
bt full
fr 5
p *change


/  The command I'm using to back up individual user's mail is something like:
/>/  
/>/  sudo -u vmail dsync -v -uuser at server.com    -R backup ssh -i sshid-filelogin at server.com    sudo -u vmail dsync -v -uuser at server.com  

/
Probably an easier way would be if you could copy the local and remote mdboxes 
to e.g. /tmp/mdbox-local and /tmp/mdbox-remote. Then you should be able to do:

gdb --args doveadm -o mail=mdbox:/tmp/mdbox-local backup -R 
mdbox:/tmp/mdbox-remote
run
bt full
fr 5
p *change

Re: [Dovecot] Dsync Errors

[Asai]

Maybe this error sheds some light on it:

Panic: file dsync-brain-mailbox-tree-sync.c: line 111 
(dsync_brain_mailbox_tree_sync_change): assertion failed: 
(brain->no_backup_overwrite)

Re: [Dovecot] Dsync Errors

[Asai]

The first thing to do when experiencing problems like this is make 
sure you are on the current version of whatever point release you are 
running. In your case that would be 2.2.10. Then if you still 
experience the problem, come back and re-ask...


OK, I upgraded to 2.2.10.  Same thing.  Is there some kind of debug 
routine I can run?

[Dovecot] Dsync Errors

[Asai]

Greetings,

I've seen something like this in another thread, about a month ago, but we're 
running into this error pretty frequently when we run dsync backup.

Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0 [0x39ccc5f1c0] -> 
/usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x35) [0x39ccc5f2a5] -> 
/usr/lib64/dovecot/libdovecot.so.0 [0x39ccc5ebb3] -> dsync(dsync_brain_mailbox_tree_sync_change+0x41c) 
[0x42cc0c] -> dsync(dsync_brain_recv_mailbox_tree_deletes+0x10a) [0x42be7a] -> 
dsync(dsync_brain_run+0x4fc) [0x429cdc] -> dsync [0x42885b] -> dsync [0x4119ff] -> 
dsync(doveadm_mail_try_run+0x269) [0x411e09] -> dsync(main+0x358) [0x41a2c8] -> 
/lib64/libc.so.6(__libc_start_main+0xf4) [0x3f4281d994] -> dsync [0x4111c9]

We're running Dovecot 2.2.4 and the dsync command is this:
dsync -u  backup maildir:/mnt/backups///

When this happens to a particular users account I delete the backup and let it 
rebuild, which works for awhile, but then it happens again, and it seems to 
happen to particular users.

Can you point me in the right direction to start troubleshooting this?

Thanks.

--
--Asai

Re: [Dovecot] Sieve-storage: couldn't find storage root directory

[Asai]

For some reason, this error has disappeared.  Maybe I forgot to restart 
Dovecot or something after I changed the config.


--Asai

On 8/12/13 11:56 AM, Timo Sirainen wrote:

On 12.8.2013, at 18.16, Asai  wrote:


Using Dovecot 2.2.4.  In my DSync logs, I'm getting the error message:

Error: sieve-storage: couldn't find storage root directory; sieve_dir was left 
unconfigured and autodetection failed

What/how/where are you dsyncing?


However, I have the following configuration set:

plugin {
  sieve = /vmail/%d/%n/sievescript
  sieve_dir = /vmail/%d/%n/
}

Maybe the other side of dsync doesn't have it?

Re: [Dovecot] Sieve-storage: couldn't find storage root directory

[Asai]

Using Dovecot 2.2.4.  In my DSync logs, I'm getting the error message:

Error: sieve-storage: couldn't find storage root directory; sieve_dir was left 
unconfigured and autodetection failed

What/how/where are you dsyncing?


However, I have the following configuration set:

plugin {
  sieve = /vmail/%d/%n/sievescript
  sieve_dir = /vmail/%d/%n/
}

Maybe the other side of dsync doesn't have it?

I am doing daily, weekly, and monthly backups of all maildirs to a 
backup server using this command:


dsync -u u...@domain.tld backup maildir:/mnt/backups/monthly>//

Re: [Dovecot] Sieve-storage: couldn't find storage root directory

[Asai]

# 2.2.4: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.18-194.32.1.el5xen x86_64 CentOS release 5.5 (Final) ext3
auth_mechanisms = plain login
mail_home = /vmail/%d/%n/home
mail_location = maildir:/vmail/%d/%n
mail_plugins = " notify"
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 ihave

namespace {
  inbox = yes
  location =
  prefix =
  separator = /
  type = private
}
passdb {
  args = /etc/dovecot/dovecot-mysql.conf
  driver = sql
}
plugin {
  sieve = /vmail/%d/%n/sievescript
  sieve_dir = /vmail/%d/%n/
}
service auth {
  unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0660
user = postfix
  }
  unix_listener auth-master {
group = vmail
mode = 0660
user = vmail
  }
  unix_listener auth-userdb {
mode = 0660
user = vmail
  }
  user = root
}
service imap-login {
  process_min_avail = 3
  service_count = 0
  vsz_limit = 0
}
ssl_cert = 
Please provide output of
doveconf -n

Regards
Daniel

[Dovecot] Sieve-storage: couldn't find storage root directory

[Asai]

Greetings,

Using Dovecot 2.2.4.  In my DSync logs, I'm getting the error message:

Error: sieve-storage: couldn't find storage root directory; sieve_dir was left 
unconfigured and autodetection failed

However, I have the following configuration set:

plugin {
  sieve = /vmail/%d/%n/sievescript
  sieve_dir = /vmail/%d/%n/
}

Please, if you have a moment, tell me what I'm doing wrong here.

Thank you.

--
--Asai

Re: [Dovecot] Lowering Log Levels Back to Defaults

[Asai]

Thank you for that simple answer.

--Asai

On 8/2/13 5:24 AM, Timo Sirainen wrote:

On Wed, 2013-07-31 at 08:21 -0700, Asai wrote:

Greetings,

I'm sorry for asking what may be a really obvious question, but I'm
having a hard time turning off logging, or at least getting less verbose
logging.  My dsync logs are about 7 MB daily, and I'm trying to get that
switched off.  At one point I had it on a lower level of verbosity, and
I turned it up for debugging purposes, but now I cannot seem to turn it
back down, which is something I did many times before.  For example the
logs are getting tons of Info level messages.

dsync(a...@globalchangemusic.org): Info: expunge: box=Trash, uid=61625, 
msgid=, size=9586

Disable mail_log plugin.

[Dovecot] Lowering Log Levels Back to Defaults

[Asai]

Greetings,

I'm sorry for asking what may be a really obvious question, but I'm 
having a hard time turning off logging, or at least getting less verbose 
logging.  My dsync logs are about 7 MB daily, and I'm trying to get that 
switched off.  At one point I had it on a lower level of verbosity, and 
I turned it up for debugging purposes, but now I cannot seem to turn it 
back down, which is something I did many times before.  For example the 
logs are getting tons of Info level messages.


dsync(a...@globalchangemusic.org): Info: expunge: box=Trash, uid=61625, 
msgid=, size=9586

In dovecot.conf I have commented out the following include, which used 
to lower the log levels back to the defaults, but I've upgraded Dovecot 
recently to 2.2.4 from 2.1 something:


#!include conf.d/10-logging.conf

I had the default levels raised in that config file.

I'm not sure this helps but:

[vmail@triata ~]# doveconf -n
# 2.2.4: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.18-194.32.1.el5xen x86_64 CentOS release 5.5 (Final) ext3
auth_mechanisms = plain login
mail_home = /vmail/%d/%n/home
mail_location = maildir:/vmail/%d/%n
mail_plugins = " mail_log notify"
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 ihave

namespace {
  inbox = yes
  location =
  prefix =
  separator = /
  type = private
}
passdb {
  args = /etc/dovecot/dovecot-mysql.conf
  driver = sql
}
plugin {
  sieve = /vmail/%d/%n/sievescript
}
service auth {
  unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0660
user = postfix
  }
  unix_listener auth-master {
group = vmail
mode = 0660
user = vmail
  }
  unix_listener auth-userdb {
mode = 0660
user = vmail
  }
  user = root
}
service imap-login {
  process_min_avail = 3
  service_count = 0
  vsz_limit = 0
}
ssl_cert = 

[Dovecot] Upgrading from 2.0 to 2.2

[Asai]

Greetings,

Is this possible to upgrade directly from 2.0 to 2.2?  If so, is there a 
guide for doing this?


Thank you.

--
--Asai

Re: [Dovecot] Restoring Mails via DSync

[Asai]

Awesome, Ben.  Thanks.

--Asai

On 3/29/2013 9:37 AM, Ben Morrow wrote:

At  7AM -0700 on 29/03/13 you (Asai) wrote:

Can anyone give me a quick pointer to the right command to use for
restoring backups made by dsync?  I have our whole mail server backed up
with it, but not sure how to restore...  Any help would be greatly
appreciated.

I would have thought you want to use exactly the dsync command you used
to take the backup, but with -R (or without it, if you were using it
before).

Ben

[Dovecot] Restoring Mails via DSync

[Asai]

Greetings,

Can anyone give me a quick pointer to the right command to use for 
restoring backups made by dsync?  I have our whole mail server backed up 
with it, but not sure how to restore...  Any help would be greatly 
appreciated.


--

--Asai

Re: [Dovecot] SSL Warnings in Debug Logs

[Asai]

Thank you, Timo.

On 07/28/2012 09:57 AM, Timo Sirainen wrote:

On 24.7.2012, at 21.27, Asai wrote:


Greetings,

In doing some debugging of authentication issues, I'm wondering if these SSL 
warnings are anything to be investigating?

Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x10, ret=1: 
before/accept initialization [192.168.70.101]
Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: 
before/accept initialization [192.168.70.101]

They should be debug messages, not warnings. Fixed in hg.

[Dovecot] SSL Warnings in Debug Logs

[Asai]

Greetings,

In doing some debugging of authentication issues, I'm wondering if these 
SSL warnings are anything to be investigating?


Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x10, 
ret=1: before/accept initialization [192.168.70.101]
Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2001, 
ret=1: before/accept initialization [192.168.70.101]
Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2002, 
ret=-1: SSLv2/v3 read client hello A [192.168.70.101]
Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2001, 
ret=1: SSLv3 read client hello A [192.168.70.101]
Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2001, 
ret=1: SSLv3 write server hello A [192.168.70.101]
Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2001, 
ret=1: SSLv3 write certificate A [192.168.70.101]
Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2001, 
ret=1: SSLv3 write key exchange A [192.168.70.101]
Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2001, 
ret=1: SSLv3 write server done A [192.168.70.101]
Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2001, 
ret=1: SSLv3 flush data [192.168.70.101]
Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2002, 
ret=-1: SSLv3 read client certificate A [192.168.70.101]
Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2002, 
ret=-1: SSLv3 read client certificate A [192.168.70.101]
Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2001, 
ret=1: SSLv3 read client key exchange A [192.168.70.101]
Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2001, 
ret=1: SSLv3 read finished A [192.168.70.101]
Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2001, 
ret=1: SSLv3 write change cipher spec A [192.168.70.101]
Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2001, 
ret=1: SSLv3 write finished A [192.168.70.101]
Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2001, 
ret=1: SSLv3 flush data [192.168.70.101]
Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x20, 
ret=1: SSL negotiation finished successfully [192.168.70.101]
Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2002, 
ret=1: SSL negotiation finished successfully [192.168.70.101]



[root@triata ~]# doveconf -n
# 2.0.14: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.18-194.32.1.el5xen x86_64 CentOS release 5.5 (Final) ext3
auth_debug = yes
auth_debug_passwords = yes
auth_mechanisms = plain login
auth_verbose = yes
auth_verbose_passwords = plain
mail_debug = yes
mail_home = /vmail/%d/%n/home
mail_location = maildir:/vmail/%d/%n
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

namespace {
  inbox = yes
  location =
  prefix =
  separator = /
  type = private
}
passdb {
  args = /etc/dovecot/dovecot-mysql.conf
  driver = sql
}
plugin {
  mail_log_fields = uid box msgid size from
  sieve = /vmail/%d/%n/sievescript
}
protocols = imap pop3 lmtp sieve sieve
service auth {
  unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0660
user = postfix
  }
  unix_listener auth-master {
group = vmail
mode = 0660
user = vmail
  }
  unix_listener auth-userdb {
mode = 0660
user = vmail
  }
  user = root
}
service imap-login {
  process_min_avail = 3
  service_count = 0
  vsz_limit = 0
}
service managesieve-login {
  inet_listener sieve {
port = 4190
  }
  process_min_avail = 0
  service_count = 1
  vsz_limit = 64 M
}
ssl_cert = 

Re: [Dovecot] v2.1.5 released

[Asai]

Let me also thank you, Timo, for your selfless excellence in developing 
Dovecot.


--asai


On 4/23/2012 6:49 AM, Timo Sirainen wrote:

http://dovecot.org/releases/2.1/dovecot-2.1.5.tar.gz
http://dovecot.org/releases/2.1/dovecot-2.1.5.tar.gz.sig

A few announcements first:

I'm now going to start being more strict about not answering Dovecot questions 
sent to me privately (especially support requests, but also bug reports, 
feature requests, etc). Often those questions could be answered by other people 
in the mailing list as well, so they just waste my time. Even if you're sure 
that I'm the only person who can possibly answer it, it may be something that 
others are interested of as well and replying privately denies them the 
possibility of reading about it. If you really do not want to send something 
publicly, you still have an option for private communication: just buy one of 
the Dovecot support packages.

This is also the first Dovecot release that has run through automated release 
testing. I've been planning on doing that for last 5 years at least, and 
finally it's done. The testing includes running a lot of tests to verify that 
the IMAP server gives proper responses, stress testing doesn't break it, memory 
isn't leaked and several other things. The tests are run for many different 
kinds of configurations.

Some bugs show up only for some specific combination of settings, but 
unfortunately because there's such a large number of them it's impossible to 
test every combination. So here's another advantage that Dovecot support 
customers have: they can have their specific configuration included in the 
automated tests. This release already fixes one bug I found only after testing 
a customer's config.

Oh, and looks like I got accepted as a speaker to LinuxTag 2012. The plan is to 
talk about some new things in Dovecot and dsync replication (looks like I have 
to hurry up with the dsync rewrite).

And finally, the most important changes since v2.1.4:

* IMAP: When neither the session nor the mailbox has modseq tracking
  enabled, return the mailbox as having NOMODSEQ in SELECT/EXAMINE
  reply. Old versions in this situation always simply returned
  HIGHESTMODSEQ as 1, which could have broken some clients.

+ dict file: Added optional fcntl/flock locking (default is dotlock)
+ fts-solr: doveadm fts rescan now resets indexes, which allows
  reindexing mails. (This isn't a full rescan implementation like
  fts-lucene has.)
+ doveadm expunge: Added -d parameter to delete mailbox if it's
  empty after expunging.
- IMAP: Several fixes related to mailbox listing in some configs
- director: A lot of fixes and performance improvements
- v2.1.4 didn't work without a mail home directory set
- mbox: Deleting a mailbox didn't delete its index files.
- pop3c: TOP command was sent incorrectly
- trash plugin didn't work properly
- LMTP: Don't add a duplicate Return-Path: header when proxying.
- listescape: Don't unescape namespace prefixes.

Re: [Dovecot] Dsync Error Can't Delete Mailbox

[Asai]

OK, thank you very much for this wonderful application.

--asai


On 12/29/2011 6:11 AM, Timo Sirainen wrote:

On 27.12.2011, at 17.46, Asai wrote:


I'm getting this error in the dsync logs:

Warning: Destination mailbox INBOX has been modified, need to recreate it 
before we can continue syncing
dsync(f...@bar.org): Error: Can't delete mailbox INBOX: INBOX can't be deleted.

In this situation, what should I do to remedy the problem?  Just delete the 
backup and rebuild?

Yes, that's the only solution currently.

[Dovecot] Dsync Error Can't Delete Mailbox

[Asai]

Greetings,

I'm getting this error in the dsync logs:

Warning: Destination mailbox INBOX has been modified, need to recreate 
it before we can continue syncing
dsync(f...@bar.org): Error: Can't delete mailbox INBOX: INBOX can't be 
deleted.


In this situation, what should I do to remedy the problem?  Just delete 
the backup and rebuild?


--
--asai

Re: [Dovecot] Backing Up To Windows File Server

[Asai]

On 12/13/2011 5:34 PM, Jerry wrote:

On Tue, 13 Dec 2011 16:21:09 -0700
Asai articulated:


Working with dsync and setting up backups to a Windows file server.
Problem seems to be that Windows is renaming the dovecot mail files
(maildir) to Windows friendly filenames, and losing the Dovecot name.
For example,
1323817925.M36368P32049.triata.globalchangemultimedia.net,S=2255,W=2318:2,S
becomes 1AETPH~X.

Does anyone have any ideas about how to tell Windows to not do this?
Or is it not possible?

I have backed up files to a Windows server before but have never
experienced the problems you are describing. Could you please list the
Windows Server specifics, ie. version, etc.
This is a Win 2008 R2 server with NFS shares enabled. I initially copied 
the backups from my former backup server to this Windows box, and that's 
when I noticed the file names had been changed.

[Dovecot] Backing Up To Windows File Server

[Asai]

Greetings,

Working with dsync and setting up backups to a Windows file server.  
Problem seems to be that Windows is renaming the dovecot mail files 
(maildir) to Windows friendly filenames, and losing the Dovecot name. 
For example,
1323817925.M36368P32049.triata.globalchangemultimedia.net,S=2255,W=2318:2,S 
becomes 1AETPH~X.


Does anyone have any ideas about how to tell Windows to not do this?  Or 
is it not possible?


--
--asai

[Dovecot] Dsync Removing Subscriptions Entries

[Asai]

Greetings,

In learning to get Dsync to work, I see a lot of this type of warning in 
the logs:


dsync-remote(u...@domain.org): Warning: Subscriptions file 
/vmail/domain/user/subscriptions: Removing invalid entry: INBOX/SOME folder


When I ran a test this morning on the backed up emails on the remote 
server with Thunderbird, I did indeed see that many of the subscribed 
folders were not present in TB, although the directories and data were 
indeed present on the remote server.  The subscriptions file on the 
remote server had the omissions which Dsync warned about.  These maildir 
folders seem to work fine on the main server.  Can someone help me to 
understand how to make the sync without omissions in the subscriptions file?


--

*Asai*
Global Change Multi-Media
Internet Application Development
IT and Networking Services
520-398-2542

Re: [Dovecot] Using Dsync for Incremental Sync

[Asai]

Thanks, Timo.  Maybe I misunderstood then that Dsync will only add or 
remove the changed email items on the remote server?  Basically we're 
just trying to keep the mailboxes stored and backed up on the remote 
server, without having to transfer 26 GB every night.  We're using 
version 2.0.14 right now.  So we'd need 2.1 to do that?


*Asai*
Global Change Multi-Media
Internet Application Development
IT and Networking Services
520-398-2542

On 9/23/2011 9:13 AM, Timo Sirainen wrote:

On 21.9.2011, at 22.56, Asai wrote:


We have about 26 GB of email which we're trying to sync nightly to a remote 
server, but what I just read from a post from Timo awhile back is that it's not 
possible because dsync relies on message GUIDs which aren't available in the 
IMAP protocol.  It seems that this is still the case, is there anything on the 
horizon for this to change?

You mean you want one way Dovecot ->  some other IMAP server? Then GUIDs don't really 
matter and "dsync backup" should work fine. You'll need Dovecot v2.1 of course.

Re: [Dovecot] Using Dsync for Incremental Sync

[Asai]

So maybe a better question would be, "What can I use for incremental 
syncing of Dovecot maildirs?"


On 9/21/2011 12:56 PM, Asai wrote:

Greetings,

We have about 26 GB of email which we're trying to sync nightly to a 
remote server, but what I just read from a post from Timo awhile back 
is that it's not possible because dsync relies on message GUIDs which 
aren't available in the IMAP protocol.  It seems that this is still 
the case, is there anything on the horizon for this to change?

[Dovecot] Using Dsync for Incremental Sync

[Asai]

Greetings,

We have about 26 GB of email which we're trying to sync nightly to a 
remote server, but what I just read from a post from Timo awhile back is 
that it's not possible because dsync relies on message GUIDs which 
aren't available in the IMAP protocol.  It seems that this is still the 
case, is there anything on the horizon for this to change?

--

*Asai*
Global Change Multi-Media
Internet Application Development
IT and Networking Services
520-398-2542

Re: [Dovecot] mail_max_userip_connections=10

[Asai]

Thanks for the insight, Tom.  Yeah, it was a different problem, and we 
solved it.



On 9/20/2011 1:15 AM, Tom Clark wrote:

If it is the same problem with K9 (although Timo doesn't think it is) we
fixed it on the K9 machine by turning off PUSH mail folders.

Tom

-Original Message-
From: dovecot-boun...@dovecot.org [mailto:dovecot-boun...@dovecot.org] On
Behalf Of Timo Sirainen
Sent: 19 September 2011 7:12 PM
To: Asai
Cc: Dovecot Mailing List
Subject: Re: [Dovecot] mail_max_userip_connections=10

On 19.9.2011, at 20.43, Asai wrote:


If you figure it out, please post the solution, because we're running into

a similar issue right now with K9 mail where it's causing us to get this
error:imap-login: Disconnected: Connection queue full

That's a different problem. You need to increase number of login processes /
connections. http://wiki2.dovecot.org/LoginProcess

Re: [Dovecot] mail_max_userip_connections=10

[Asai]

On 9/19/2011 5:36 AM, Tom Clark wrote:

Hi Paul,

It's coming from the same IP address through his ADSL. Hence he gets the
problem with max_userip_connections.

I think I tracked down the problem. He's been using K9 mail which seems to
have a problem where it doesn't release a connection and has 1 connection
per subscribed folder

Ta,

Tom


If you figure it out, please post the solution, because we're running 
into a similar issue right now with K9 mail where it's causing us to get 
this error:imap-login: Disconnected: Connection queue full

Re: [Dovecot] Dsync Permissions Issue

[Asai]

Thank you for your assistance, I have changed permissions on the remote 
server and all is well.



On 9/16/2011 6:09 AM, Timo Sirainen wrote:

On Wed, 2011-09-14 at 09:04 -0700, Asai wrote:


[root@triata ~]# dsync -v -u a...@globalchangemusic.org backup ssh
-p2 vm...@xx.xxx.xx.xxx dsync -u a...@globalchangemusic.org
vm...@xx.xxx.xx.xxx's password:
dsync(vmail): Error: userdb lookup:
connect(/var/run/dovecot/auth-userdb) failed: Permission denied
(euid=1001(vmail) egid=1001(vmail) missing +r perm:
/var/run/dovecot/auth-userdb, euid is not dir owner)

..

service auth {
unix_listener auth-userdb {
  group = vmail
  mode = 0666
  user = vmail
}
user = root
}

So clearly you've given more than necessary permissions in here. 0600
with user=vmail should be enough. But the permission problem isn't on
the server where you ran this "doveconf -n". The problem is on your
remote server's Dovecot config.

BTW:


unix_listener auth-master {
  group = vmail
  mode = 0660
  user = vmail
}

There's no reason to change this from defaults.

[Dovecot] Dsync Permissions Issue

[Asai]

Greetings,

I recently upgraded Dovecot from 1.2 to 2.0.14, for purposes of using 
Dsync to migrate emails from one server to another.  I'm using MySQL for 
authentication.  However I get this error message when I try to run 
Dsync, and after looking around for an answer, I'm at a bit of a loss:


[root@triata ~]# dsync -v -u a...@globalchangemusic.org backup ssh 
-p2 vm...@xx.xxx.xx.xxx dsync -u a...@globalchangemusic.org

vm...@xx.xxx.xx.xxx's password:
dsync(vmail): Error: userdb lookup: 
connect(/var/run/dovecot/auth-userdb) failed: Permission denied 
(euid=1001(vmail) egid=1001(vmail) missing +r perm: 
/var/run/dovecot/auth-userdb, euid is not dir owner)
dsync(vmail): Fatal: User lookup failed: Internal error occurred. Refer 
to server log for more information.
dsync-local(a...@globalchangemusic.org): Error: read() from worker 
server failed: EOF


Config as follows:

[root@triata ~]# doveconf -n
# 2.0.14: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.18-92.1.10.el5.xs5.0.0.39xen x86_64 CentOS release 5 
(Final) ext3

auth_mechanisms = plain login
mail_home = /vmail/%d/%n/home
mail_location = maildir:/vmail/%d/%n
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

namespace {
  inbox = yes
  location =
  prefix =
  separator = /
  type = private
}
passdb {
  args = /etc/dovecot-mysql.conf
  driver = sql
}
plugin {
  sieve = /vmail/%d/%n/sievescript
}
service auth {
  unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0660
user = postfix
  }
  unix_listener auth-master {
group = vmail
mode = 0660
user = vmail
  }
  unix_listener auth-userdb {
group = vmail
mode = 0666
user = vmail
  }
  user = root
}
ssl_cert = 

[Dovecot] Authentication a la Postfix's Mynetworks

[Asai]

 Is it possible to automatically authenticate Dovecot users using the 
same type of mechanism which makes Postfix able to simply check SMTP 
users using the  mynetworks variable?


Basically I would like to be able to authenticate users on my designated 
networks automatically, and require a password for those outside this 
network.


Is this possible?

--
--asai

Re: [Dovecot] User Can't Access Public Folder

[Asai]

Thank you. 


Pascal Volk wrote:

On 06/18/2010 11:44 PM Asai wrote:
  

Greetings,

Jun 18 14:38:23 triata dovecot: IMAP(u...@mydomain.com): Panic: file 
maildir-uidlist.c: line 1242 (maildir_uidlist_records_drop_expunges): 
assertion failed: (recs[i]->uid < rec->uid)



Please update your dovecot 1.2.[78], 1.2.11 is the current version.


Regards,
Pascal
  


--
asai

[Dovecot] User Can't Access Public Folder

[Asai]

Greetings,

I have set up some public folders for Thunderbird, and one user in 
particular cannot access the shared folders.  This is the message I get 
from /var/log/maillog (I should add that the domain name is over 35 
characters long!):


Jun 18 14:38:23 triata dovecot: IMAP(u...@mydomain.com): Panic: file 
maildir-uidlist.c: line 1242 (maildir_uidlist_records_drop_expunges): 
assertion failed: (recs[i]->uid < rec->uid)
Jun 18 14:38:23 triata dovecot: IMAP(u...@mydomain.com): Raw backtrace: 
imap [0x49ec70] -> imap [0x49ecd3] -> imap [0x49e336] -> imap [0x440ced] 
-> imap(maildir_uidlist_sync_finish+0x28a) [0x44183a] -> imap [0x43c9c1] 
-> imap(maildir_storage_sync_init+0x14e) [0x43ce2e] -> 
imap(mailbox_sync+0x30) [0x467250] -> imap(cmd_select_full+0x1ae) 
[0x41e00e] -> imap(cmd_select+0xb) [0x41e8eb] -> imap [0x42086c] -> imap 
[0x420922] -> imap(client_handle_input+0x3f) [0x420a5f] -> 
imap(client_input+0x5f) [0x4215af] -> imap(io_loop_handler_run+0xf8) 
[0x4a6af8] -> imap(io_loop_run+0x1d) [0x4a5c0d] -> imap(main+0x620) 
[0x428e50] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x3c8861d8a4] -> 
imap [0x419ac9]
Jun 18 14:38:23 triata dovecot: dovecot: child 5272 (imap) killed with 
signal 6 (core dumps disabled)


--
asai

Re: [Dovecot] Sieve Plugin Help

[Asai]

Read the fine documentation: http://wiki.dovecot.org/LDA

  

Thanks for pointing me in the right direction.

--
--asai

Re: [Dovecot] Sieve Plugin Help

[Asai]

On 12/17/2009 06:39 PM Asai wrote:
  
Thank you, Pascal.  I have enabled this, but I'm still not seeing 
anything related to sieve in the logs.  Could someone review my config 
and see if there's something wrong here?  By the way, I'm using maildirs 
with virtual users and MySQL authentication.


# 1.2.8: /etc/dovecot.conf
# OS: Linux 2.6.18-92.1.6.el5.centos.plusxen x86_64 CentOS release 5 
…

lda:
  mail_debug: yes
  postmaster_address: postmas...@globalchangemultimedia.net
  hostname: triata.globalchangemultimedia.net
  mail_plugins: sieve
  mail_plugin_dir: /usr/lib64/dovecot/lda
…
plugin:
  sieve: ~/.dovecot.sieve
  sieve_dir: ~/sieve



Looks OK. Are you using Dovecot's deliver for virtual mail delivery?
When you are using Postfix and deliver, you will find something like
the following in your logs:
postfix/pipe … to=, relay=dovecot, … (delivered via dovecot service)
Then deliver should log something like:
deliver(user): Loading modules from directory: /usr/…


Regards,
Pascal
  
OK, here's the thing, it says relay=virtual.  So, I guess I'm not using 
deliver.  How do I set it up to use deliver?


--
--asai

Re: [Dovecot] Sieve Plugin Help

[Asai]

On 12/16/2009 10:30 PM Asai wrote:
  

OK, so I got the sieve plugin built, but how do I test whether it's
working?  Is there debug output anywhere I can check?




Please stop top posting.

Enable mail_debug, at least in the protocol lda {…} section, and watch
your log file.


Regards,
Pascal
  
Thank you, Pascal.  I have enabled this, but I'm still not seeing 
anything related to sieve in the logs.  Could someone review my config 
and see if there's something wrong here?  By the way, I'm using maildirs 
with virtual users and MySQL authentication.


# 1.2.8: /etc/dovecot.conf
# OS: Linux 2.6.18-92.1.6.el5.centos.plusxen x86_64 CentOS release 5 
(Final) ext3
ssl_cert_file: 
/etc/ssl/triata.globalchangemultimedia.net/mailserver/smtpd.pem
ssl_key_file: 
/etc/ssl/triata.globalchangemultimedia.net/mailserver/smtpd.pem

login_dir: /var/run/dovecot/login
login_executable(default): /usr/libexec/dovecot/imap-login
login_executable(imap): /usr/libexec/dovecot/imap-login
login_executable(pop3): /usr/libexec/dovecot/pop3-login
mail_location: maildir:/vmail/%d/%n
mail_executable(default): /usr/libexec/dovecot/imap
mail_executable(imap): /usr/libexec/dovecot/imap
mail_executable(pop3): /usr/libexec/dovecot/pop3
mail_plugin_dir(default): /usr/lib64/dovecot/imap
mail_plugin_dir(imap): /usr/lib64/dovecot/imap
mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3
namespace:
 type: private
 separator: /
 inbox: yes
 list: yes
 subscriptions: yes
namespace:
 type: public
 separator: /
 prefix: public/
 location: maildir:/vmail/public:INDEX=/vmail/%u/public
 list: yes
lda:
 mail_debug: yes
 postmaster_address: postmas...@globalchangemultimedia.net
 hostname: triata.globalchangemultimedia.net
 mail_plugins: sieve
 mail_plugin_dir: /usr/lib64/dovecot/lda
auth default:
 mechanisms: plain login
 passdb:
   driver: sql
   args: /etc/dovecot-mysql.conf
 userdb:
   driver: passwd
 userdb:
   driver: sql
   args: /etc/dovecot-mysql.conf
 socket:
   type: listen
   client:
 path: /var/spool/postfix/private/auth
 mode: 432
 user: postfix
 group: postfix
   master:
 path: /var/run/dovecot/auth-master
 mode: 432
 user: vmail
 group: vmail
plugin:
 sieve: ~/.dovecot.sieve
 sieve_dir: ~/sieve

--
--asai

Re: [Dovecot] Sieve Plugin Help

[Asai]

OK, so I got the sieve plugin built, but how do I test whether it's
working?  Is there debug output anywhere I can check?

Oli Schacher wrote:

Asai wrote:

Thanks, Oli.  So, what about the ATrpms Dovecot-Sieve plugin?
http://atrpms.net/dist/el5/dovecot-sieve/

Is this different?
AFAIK this is the CMU Sieve (Cyrus) plugin for dovecot 1.1.  I don't 
think there are atrpm packages for the dovecot sieve version.




--
--asai

[Dovecot] Sieve Plugin Help

[Asai]

When I run # dovecot --build-options

I get:
Build options: ioloop=epoll notify=inotify ipv6 openssl
Mail storages: cydir dbox maildir mbox raw shared
SQL driver plugins: mysql postgresql sqlite
Passdb: checkpassword ldap pam passwd passwd-file shadow sql
Userdb: nss ldap(plugin) passwd passwd-file prefetch sql static

I don't see anything here mentioning Sieve.  Does this mean that Sieve 
is not enabled in this build?


--
--asai

[Dovecot] MySQL Access

[Asai]

This may be a stupid question, but here goes.

Does the current RPM offered by ATrpms version 1.2.8 come with MySQL 
enabled?


--
--asai

Re: [Dovecot] Auth Fails, But Can Still Get Mail

[Asai]

OK, thank you, Timo.

Timo Sirainen wrote:

On Tue, 2009-12-15 at 13:03 -0700, Asai wrote:
  

I guess. Or something else running on localhost trying to log in as
other users?
  
  

What method would I use to debug this?  Does Dovecot have a debug console?



Does Squirrelmail log when it attempts to authenticate a user? That
would be the easiest way. The other possibility that I can think of
would be to catch the process in netstat -pn output, but running that at
the correct time could be a bit difficult. Or I suppose you could just
make a script that runs it every second and saves the output and current
time and ps output. Then when you see a log failure, look up the correct
netstat output and see which process has a connection to Dovecot.

  


--
--asai

Re: [Dovecot] Auth Fails, But Can Still Get Mail

[Asai]

I guess. Or something else running on localhost trying to log in as
other users?
  


What method would I use to debug this?  Does Dovecot have a debug console?

--
--asai

Re: [Dovecot] Auth Fails, But Can Still Get Mail

[Asai]

Timo Sirainen wrote:

On Tue, 2009-12-15 at 11:53 -0700, Asai wrote:
  
I've recently upgraded from version .97 to v. 1.2.  Everything seems to 
be working OK, but I'm wondering why I'm getting authentication failure 
messages in /var/log/maillog.  Like this:


Dec 15 11:02:41 triata dovecot: imap-login: Disconnected (auth failed, 1 
attempts): user=, method=PLAIN, rip=140.9.5.1, lip=140.9.5.1, 
secured



Although that user can log in to the server and get email no problem.  



Maybe the user has multiple clients, or multiple accounts in one client
and one of them doesn't work? Anyway seems like a user/client problem.

  

Thank you for your help here.

Well, the strange thing is, I'm getting logs like this for every user I 
have. Some of which arent even on-line at the time of the logs. The rid 
is the same as the lid which is weird as it's on the same server as 
dovecot.  I have SquirrelMail installed on this server as well.  Could 
that be the source of this?


--
--asai

[Dovecot] Auth Fails, But Can Still Get Mail

[Asai]

Greetings,

I've recently upgraded from version .97 to v. 1.2.  Everything seems to 
be working OK, but I'm wondering why I'm getting authentication failure 
messages in /var/log/maillog.  Like this:


Dec 15 11:02:41 triata dovecot: imap-login: Disconnected (auth failed, 1 
attempts): user=, method=PLAIN, rip=140.9.5.1, lip=140.9.5.1, 
secured



Although that user can log in to the server and get email no problem.  
Config file follows:


# 1.2.8: /etc/dovecot.conf
# OS: Linux 2.6.18-92.1.6.el5.centos.plusxen x86_64 CentOS release 5 
(Final) ext3
ssl_cert_file: 
/etc/ssl/triata.globalchangemultimedia.net/mailserver/smtpd.pem
ssl_key_file: 
/etc/ssl/triata.globalchangemultimedia.net/mailserver/smtpd.pem

login_dir: /var/run/dovecot/login
login_executable(default): /usr/libexec/dovecot/imap-login
login_executable(imap): /usr/libexec/dovecot/imap-login
login_executable(pop3): /usr/libexec/dovecot/pop3-login
mail_location: maildir:/vmail/%d/%n
mail_executable(default): /usr/libexec/dovecot/imap
mail_executable(imap): /usr/libexec/dovecot/imap
mail_executable(pop3): /usr/libexec/dovecot/pop3
mail_plugin_dir(default): /usr/lib64/dovecot/imap
mail_plugin_dir(imap): /usr/lib64/dovecot/imap
mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3
namespace:
 type: private
 separator: /
 inbox: yes
 list: yes
 subscriptions: yes
namespace:
 type: public
 separator: /
 prefix: public/
 location: maildir:/vmail/public
 list: yes
lda:
 postmaster_address: postmas...@globalchangemultimedia.net
 hostname: triata.globalchangemultimedia.net
 mail_plugins: sieved
 mail_plugin_dir: /usr/lib64/dovecot/lda
auth default:
 mechanisms: plain login
 passdb:
   driver: pam
 passdb:
   driver: sql
   args: /etc/dovecot-mysql.conf
 userdb:
   driver: passwd
 userdb:
   driver: sql
   args: /etc/dovecot-mysql.conf
 socket:
   type: listen
   client:
 path: /var/spool/postfix/private/auth
 mode: 432
 user: postfix
 group: postfix
   master:
 path: /var/run/dovecot/auth-master
 mode: 432
 user: vmail
 group: vmail

--
--asai