Re: [Dovecot] %{session} does not work with deliver_log_format
Timo Sirainen wrote:
On 25.2.2013, at 23.34, Daniel Parthey
daniel.part...@informatik.tu-chemnitz.de wrote:
LMTP has a completely different session ID currently, which gets reset for
each mail delivery and is written to the Received: header that it writes.
It doesn't traverse through proxies, because each delivery gets a
different ID anyway.
So .. Why is it that you want this? For matching a log line with a
Received:
header? I guess that could be done, but the name should probably be
different
from %{session} so it won't get mixed up with what IMAP/POP3 uses it for.
I simply run an LMTP director/proxy to prevent NFS locking issues
and in error cases I want to investigate where the mail has gone
(through the director lmtp to the mailbox lmtp). I thought this
is what session IDs were intended for.
The SMTP server should log the delivery ID that the backend generates, and
you should be able to grep for it, right?
Ah ok, that's totally fine. I didn't expect the ID to be the backend IP :)
Obviously, the generated ID is a different one for director and mailbox,
looking at the Received: lines of a single message:
Received: from mail01.example.org ([10.129.3.193])
by mail01.example.org (Dovecot) with LMTP id vdSeD+CrK1HXZQAAiWCYmA
; Mon, 25 Feb 2013 19:25:02 +0100
Received: from mx01.example.org ([127.0.0.1])
by mail01.example.org (Dovecot) with LMTP id fu7aIn6sK1EMaQAAiWCYmA
; Mon, 25 Feb 2013 19:25:02 +0100
What would you suggest how to track an LMTP delivery through a
director proxy? Should one use the MessageID to correlate the
lmtp log entries in dovecot-director.log and dovecot.log?
I was first thinking about having LMTP proxy log the delivery ID, until I
noticed that LMTP proxy doesn't log anything about delivered mails currently.
I'm not really sure if that would be of any actual help?
Currently our lmtp proxy logs the following:
dovecot: lmtp(3538): Debug: none: root=, index=, control=, inbox=, alt=
dovecot: lmtp(3538): Connect from 127.0.0.1
dovecot: lmtp(3538): Debug: auth input: user=u...@example.org proxy
proxy_timeout=120 port=19024 host=10.129.3.193 proxy_refresh=86400
dovecot: lmtp(3538): Disconnect from 127.0.0.1: Client quit (in reset)
In combination with syslog timestamp, this is enough information
to track the user/backend assignment in the director,
also shown by doveadm director status u...@example.org.
Regards
Daniel
--
https://plus.google.com/103021802792276734820
Re: [Dovecot] Moving mail servers, moving mailboxes
On 16.4.2013, at 2.48, Gregory Sloop gr...@sloop.net wrote: In short, migrating a RHEL 5.9 server running the back-ported Dovecot 1.0.7 To: Ububtu 12.04 with 2.0.19, I believe. Dovecot v2.0 can use v1.0's mbox/maildir files including their metadata. v2.0 should also be able to read v1.0's index files without errors. In an ideal world, I'd like to simply copy all the mailboxes/dirs from one server to the other. [Local/LAN file copies are possible] You can do that. Or use rsync.
[Dovecot] imap Fatal: bzlib.read(~/mdbox/storage/m.317): Out of memory
Hi Timo, today I found a raw backtrace after the bzlib.read() out of memory message. Regards, Pascal Apr 17 10:41:44 imap(u...@example.com): Fatal: bzlib.read(/srv/mail/x/70004/70038/mdbox/storage/m.317): Out of memory Apr 17 10:41:44 imap(u...@example.com): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x7a1b6) [0x7ff6837791b6] - /usr/local/lib/dovecot/libdovecot.so.0(+0x7b4e1) [0x7ff68377a4e1] - /usr/local/lib/dovecot/libdovecot.so.0(i_error+0) [0x7ff683779662] - /usr/local/lib/dovecot/lib20_zlib_plugin.so(+0x4ef4) [0x7ff682731ef4] - /usr/local/lib/dovecot/libdovecot.so.0(i_stream_read+0xc9) [0x7ff683785812] - /usr/local/lib/dovecot/libdovecot.so.0(i_stream_read_copy_from_parent+0xa4) [0x7ff683785ba5] - /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xbba73) [0x7ff683aa8a73] - /usr/local/lib/dovecot/libdovecot.so.0(i_stream_read+0xc9) [0x7ff683785812] - /usr/local/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x61) [0x7ff683786707] - /usr/local/lib/dovecot/libdovecot.so.0(message_parse_header_next+0x109) [0x7ff683766b44] - /usr/local/lib/dovecot/libdovecot.so.0(message_parse_header+0x5e) [0x7ff6837678de] - /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xc838f) [0x7ff683ab538f] - /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xc9a2a) [0x7ff683ab6a2a] - /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xc9c6a) [0x7ff683ab6c6a] - /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xca206) [0x7ff683ab7206] - /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xca4c2) [0x7ff683ab74c2] - /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xca7f7) [0x7ff683ab77f7] - /usr/local/lib/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0x43) [0x7ff683ab784e] - /usr/local/lib/dovecot/lib90_stats_plugin.so(+0x3753) [0x7ff681efc753] - /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x49) [0x7ff683a857e2] - dovecot/imap [u...@example.com 192.0.96.113 UID SEARCH]() [0x421883] - dovecot/imap [u...@example.com 192.0.96.113 UID SEARCH]() [0x421bdf] - /usr/local/lib/dovecot/libdovecot.so.0(+0x914ba) [0x7ff6837904ba] - /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0x20) [0x7ff683790541] - /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xeb) [0x7ff68379210d] - /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x5e) [0x7ff683790644] - /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x2e) [0x7ff68372809e] - dovecot/imap [u...@example.com 192.0.96.113 UID SEARCH](main+0x2af) [0x4264a0]
Re: [Dovecot] Maildirs location migration
On Tue, Apr 16, 2013 at 02:00:38PM +0300, Timo Sirainen wrote: The worst that can happen is: 1) Client sees new mail 123 in old server 2) Client sees only mails up to 122 in the new server 3) Client again will see mail 123 after a while I'm actually not sure how clients will handle that. It is an IMAP protocol violation. Why is it a protocol violation ? if new was up to 122, nextuid would have been 123 so what's the problem, protocol wise, to see 123 come later ? Of course if a new mail is delivered in new as 123, there 's a conflict. But as you said dsync knows how to handle this and would assign new uids to both and the client, as you said, could get confused about what he thought was 123. But even in that case, wouldn't he see the message (as a new one with it's new uid) ? I mean, nothing would be lost ? Thanks -- Thomas Hummel | Institut Pasteur hum...@pasteur.fr | Groupe Exploitation et Infrastructure
Re: [Dovecot] Maildirs location migration
On 17.4.2013, at 13.19, Thomas Hummel hum...@pasteur.fr wrote: On Tue, Apr 16, 2013 at 02:00:38PM +0300, Timo Sirainen wrote: The worst that can happen is: 1) Client sees new mail 123 in old server 2) Client sees only mails up to 122 in the new server 3) Client again will see mail 123 after a while I'm actually not sure how clients will handle that. It is an IMAP protocol violation. Why is it a protocol violation ? if new was up to 122, nextuid would have been 123 so what's the problem, protocol wise, to see 123 come later ? Because client saw uidnext=124 on the old server, which shrank back to uidnext=123 on the new server. That shouldn't happen even temporarily. Of course if a new mail is delivered in new as 123, there 's a conflict. But as you said dsync knows how to handle this and would assign new uids to both and the client, as you said, could get confused about what he thought was 123. But even in that case, wouldn't he see the message (as a new one with it's new uid) ? I mean, nothing would be lost ? Yeah, when conflicts are fixed nothing gets lost. In that worst case I mentioned there's no conflict really, just a message that disappears and appears back. Hmm. Maybe Dovecot should keep track of what messages IMAP clients have seen, and automatically figure out when it should change UIDs in those cases.
Re: [Dovecot] Moving mail servers, moving mailboxes
On 17/04/2013 10:58, Timo Sirainen wrote: On 16.4.2013, at 2.48, Gregory Sloopgr...@sloop.net wrote: In short, migrating a RHEL 5.9 server running the back-ported Dovecot 1.0.7 To: Ububtu 12.04 with 2.0.19, I believe. Dovecot v2.0 can use v1.0's mbox/maildir files including their metadata. v2.0 should also be able to read v1.0's index files without errors. We've a similar wish, except that we were hoping to install 2.2 on a different box (intending in our case to run Debian Squeeze instead of Ubuntu LTS). Can 2.2 (or, if not, then 2.1) also read 1.0 metadata? (Or is 'only' 2.0 able to read 1.0 metadata? In which case we'd probably migrate through 2.0.x to 2.2, on Squeeze.) Note on the Wiki: The Migration page http://wiki2.dovecot.org/Migration is good at describing migration 'to' Dovecot from other systems, and does suggest that Dovecot will read existing files. I think there were earlier discussions on the list about Dovecot version changes which meant that newer versions could read older versions' data, but older versions could not read newer versions' data. These aspects are not relevant for 'migrating to' Dovecot, but are worth keeping in mind for 'upgrading' Dovecot. There is version to version upgrading advice, covering all aspects, not only which version can read what, here http://wiki2.dovecot.org/Upgrading What I can see, from the descriptions of each version change, is that V2.x can read V1.x, but V1.2.4 or lower cannot read V2.x data. Permissions for Maildir changed, though, in V2.0 and, then for all mailbox types (it says 'creating home directories', actually), in V2.2. This latter change in 2.2 seems to be relevant for any mailboxes that will be accessed by several different users who are actually 'system users', ie, a mail service where the mailbox is 'shared', and the installation is using 'system users' (not, therefore, using 'virtual users', if I have understood correctly). This info is (surely) fully understood already by all the serious mail-server users on the list, but I wonder if it might be helpful to spell it out for less confident users who are getting up to speed with these aspects. If the text I've written above is correct, shall I add it to the upgrading page of the Wiki, so that there is a definitive answer to the query which version(s) read what? regards, Ron
Re: [Dovecot] imap Panic: file index-attachment.c: line 231 (index_attachment_save_finish): assertion failed: (attach-input-eof)
On Tue, 2013-04-16 at 19:28 +0200, Pascal Volk wrote: On 04/15/2013 11:33 PM Pascal Volk wrote: OK, applied that patch. Lets see what will happen. Looks good. No crash in the last 20 hours. OK. Committed the patch a little bit differently: http://hg.dovecot.org/dovecot-2.2/rev/8a07a5f6fd54
[Dovecot] Dovecot connection problem - Too many invalid commands (no auth attempts) - v2.0.19
Hello.
This might be a silly problem, but I'm a bit a newbie at this, and the
internet didn't give me a solution to this yet.
I installed a mail server with postfix, dovecot, postfixadmin and a mysql DB
for authentification, using this tutorial :
http://www.exratione.com/2012/05/a-mailserver-on-ubuntu-1204-postfix-doveco
t-mysql/
http://www.exratione.com/2012/05/a-mailserver-on-ubuntu-1204-postfix-dovecot
-mysql/. Except step 4. The complete tutorial worked on a virtual machine,
but doesn't work here on a vps from ovh.net.
Connecting via telnet localhost 143 works, I can connect.
When I try to connect via thunderbird, the domain name is picked up, but
gives me a bad login/password combination. Mail.log, mail.err and error
don't show anything.
Via MS Outlook, I seem to get stuck on the connection page, and I get the
following errors in mail.log:
dovecot: imap-login: Disconnected: Too many invalid commands (no auth
attempts): rip=x, lip=y
dovecot: pop3-login: Disconnected (no auth attempts): rip=x, lip=y
dovecot: imap-login: Disconnected (no auth attempts): rip=x, lip=y, TLS:
Disconnected
dovecot: pop3-login: Disconnected (no auth attempts): rip=x, lip=y, TLS:
Disconnected
dovecot: pop3-login: Aborted login (no auth attempts): rip=x, lip=y
dovecot: imap-login: Disconnected (no auth attempts): rip=x, lip=y, TLS:
Disconnected
dovecot: imap-login: Disconnected (no auth attempts rip=x, lip=y
dovecot: imap-login: Disconnected (no auth attempts): rip=x, lip=y, TLS
handshaking: Disconnected
dovecot: pop3-login: Disconnected (no auth attempts): rip=x, lip=y, TLS
handshaking: Disconnected
And after a while asks to try to connect via plain method.
Doveconf -n gives me this
# 2.0.19: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-042stab068.8 x86_64 Ubuntu 12.04.2 LTS simfs
auth_mechanisms = plain login
first_valid_uid = 150
last_valid_uid = 150
mail_gid = mail
mail_location = maildir:/var/vmail/%d/%n
mail_uid = vmail
passdb {
args = /etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
protocols = imap pop3
service auth {
unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0660
user = postfix
}
unix_listener auth-userdb {
group = mail
mode = 0600
user = vmail
}
}
ssl_cert = /etc/ssl/certs/dovecot.pem
ssl_key = /etc/ssl/private/dovecot.pem
userdb {
args = /etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
Hope you guys can help me, and thanks in advance for it.
Greetings,
Thomas Standaert
Re: [Dovecot] Dovecot connection problem - Too many invalid commands (no auth attempts) - v2.0.19
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 17 Apr 2013, Thomas Standaert wrote: Did you enabled auth_debug in Dovecot ? When you use telnet ip 143 1 login user password does it work? MUAs do too much, when it does not work at once. It it works, try using TLS e.g.: gnutls-cli -p 143 --starttls localhost STARTTLS ^D 1 login user password - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUW6pqF3r2wJMiz2NAQJyCggAhNDwtOWw95OMs1UNNd9eK8qwc/3EZSZh uBEpRuMx4JyUzvpE5U8b51pmqwTFP+gsLokw2yMpX/9f1oD5/9MedKr8wsuGVq+G W3a4NnK2Go9MelD3Pk4brZv6QDDupFV3zugwePFpA8OM0Mzp93uq3kwK4cX6+BDu ePY4DMFdcT9zydtbXE3SJhx4eXIxJIMekH1y7QH6gaglfJ9+sapfN9AE4nVOtSkN Ydrk9TnJJ3e3i0UF1AknbMolWVF4Wa52RTcrZBkeTADz7Uv5Xn2bkVnG14zt4LN/ Vb9BIEqz2rJHJoSsBAamZU2pwkug3fbzIHs+bt6++5nneT/K3Vav9g== =H7z5 -END PGP SIGNATURE-
Re: [Dovecot] Moving mail servers, moving mailboxes
TS On 16.4.2013, at 2.48, Gregory Sloop gr...@sloop.net wrote: In short, migrating a RHEL 5.9 server running the back-ported Dovecot 1.0.7 To: Ububtu 12.04 with 2.0.19, I believe. TS Dovecot v2.0 can use v1.0's mbox/maildir files including their TS metadata. v2.0 should also be able to read v1.0's index files without errors. Thanks Timo for the answer - that helps a lot... Now, some follow-up. I assume this means that all version of 2.x (to current) can read 1.x files. [If I'm wrong, please correct me.] Is there a tool to convert/migrate the mailbox format from v1 to 2, or does v2 do it automagically or something? [I'm sure there must be a tool, but some searching wasn't finding it for me.] --- As long as I'm asking about mailbox formats, is it possible to use DBox with postfix - it appears on the Wiki that it's not, but then I find posts on the web that appear to indicate it *is* possible. [We're using Postfix as our MTA.] Thanks again all! -Greg In an ideal world, I'd like to simply copy all the mailboxes/dirs from one server to the other. [Local/LAN file copies are possible] TS You can do that. Or use rsync. -- Gregory Sloop, Principal: Sloop Network Computer Consulting Voice: 503.251.0452 x82 EMail: gr...@sloop.net http://www.sloop.net ---
[Dovecot] Problem with convert Plugin
Hello, I got a Problem with the convert Plugin. Trying to convert from mbox to maildir Format. OS: CentOS release 5.8 (Final) dovecot -version: 1.0.7 (Centos RPM) convert Plugin call: convert_mail = mbox:/opt/pop3/%u:INBOX=/var/spool/mail/%u When converting to maildir - POP3 works fine (except the lost UIDL - so every server-saved message is double downloaded - but did not find any fix for this problem with convert plugin) But the IMAP In-Boxes give me some headache . All Folders are converted correct - and displayed in Mail Client. But all Mails in the IMAP INBOX are lost (at least Mail Client won't show them anymore) Newly delivered Mails to the Inbox work - but all older ones are missing. When looking into this Folder: /var/maildata/USER/Maildir/cur/ I can see that newly delivered mails look like this: 1366122898.14776_0.SERVERNAME:2, And the old - converted ones like this: 1366119758.P14442Q12M682874.SERVERNAME:2, Can someone point me in the right direction why the converted Mails are missing? (It worked on other Servers - about 1 year ago - without any problem?!) Thank you Andreas Schnederle-Wagner Futureweb OG Innsbrucker Str. 4 6380 St. Johann schnede...@futureweb.at www.futureweb.at www.ortsinfo.at Fon: +43 (0) 5352 65335-0 Fax: +43 (0) 5352 65335-777 Gratis über Skype anrufen | Skype-ID: futureweb
Re: [Dovecot] Dovecot connection problem - Too many invalid commands (no auth attempts) - v2.0.19
Hey Steffen, thanks for the quick response! I enabled auth-debug now in dovecot. A normal telnet ip 143 works, after I put disable_plaintext_auth to no of course. I could connect, and see my folders. Mail.log didn't give me anything abnormal, and showed me neatly the connection and the sql querries. One abnormality though, just mentioning it, when I try to type in 1 login user password, I got a BAD Error in IMAP command received by server. Or when I copy pasted the same thing (from the localhost terminal where I tried it there) it worked. After that I tried gnutls-cli -p 143 --starttls localhost 1 STARTTLS ^D It gave me following error: The hostname in the certificate does NOT match 'localhost' It's probably a certificate error (I use a self-signed, planning on buying one maybe later). I'm now digging google again, and triple checking each conf file. I added the hostname to the localhost entry of /etc/hosts, but no positive response yet. Thank you again Greetings, Thomas Standaert -Original Message- From: dovecot-boun...@dovecot.org [mailto:dovecot-boun...@dovecot.org] On Behalf Of Steffen Kaiser Sent: woensdag 17 april 2013 16:55 To: Dovecot Mailing List Subject: Re: [Dovecot] Dovecot connection problem - Too many invalid commands (no auth attempts) - v2.0.19 On Wed, 17 Apr 2013, Thomas Standaert wrote: Did you enabled auth_debug in Dovecot ? When you use telnet ip 143 1 login user password does it work? MUAs do too much, when it does not work at once. It it works, try using TLS e.g.: gnutls-cli -p 143 --starttls localhost STARTTLS ^D 1 login user password - -- Steffen Kaiser
[Dovecot] qmail-ldap LDA Delivery and sieve
Hi,
I'm using dovecot 2.1.7 on debian Squeeze with ldap integration.
Almost everything is working fine and I would link to thank all
developers for this amazing piece of software.
But after changing my qmail-ldap to do LDA integration get all the
benefits from LDA and sieve, some emails return with failure like
this:
s...@mondialline.com.br:
lda(sar): Fatal: Unknown argument: sar
Usage: dovecot-lda [-c config file] [-a address] [-d username] [-p path]
[-f envelope sender] [-m mailbox] [-e] [-k]
It happens on messanges that could not be delivered and need to be
returned to the sender.
I'm using the configuration described on wiki to do qmail-ldap
integration: http://wiki.dovecot.org/HowTo/qmailldap
The relevant delivery command is:
| /usr/lib/dovecot/dovecot-lda -a $RECIPIENT -f $SENDER -d $USER
I also tried to use this way, as documented here:
http://wiki2.dovecot.org/LDA/Qmail
| /var/qmail/bin/preline -f /usr/lib/dovecot/dovecot-lda
But in that case, some sieve plugins can't detect the mail recipient,
like vacation plugin.
Finally, the vacation plugin also is not doing email forwarding when I
use the first delivery option above.
Follow my settings:
# LDAP
scope = subtree
user_attrs = uidNumber=11184,gidNumber=2110
user_filter = ((objectClass=qmailUser)(uid=%u)(accountStatus=active))
pass_attrs=uid=user,userPassword=password,mailHost=host,=proxy_maybe=y
pass_filter = ((objectClass=qmailUser)(uid=%u)(accountStatus=active))
iterate_attrs = uid=user
iterate_filter = ((objectClass=qmailUser)(accountStatus=active))
# dovecot -n output:
# 2.1.7: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-5-xen-amd64 x86_64 Debian 6.0.7 ext4
default_client_limit = 8000
default_process_limit = 2048
disable_plaintext_auth = no
hostname = mail.mondialline.com.br
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
lda_original_recipient_header = X-Original-To
mail_gid = vmail
mail_location = maildir:/dados/vmail/%u/Maildir
mail_plugins = zlib
mail_privileged_group = vmail
mail_uid = vmail
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 vacation-seconds
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 = INBOX.
separator = .
type = private
}
passdb {
args = /etc/dovecot/master-users
driver = passwd-file
master = yes
pass = yes
}
passdb {
args = /etc/dovecot/dovecot-ldap.conf.ext
driver = ldap
}
plugin {
sieve = /dados/vmail/%u/.dovecot.sieve
sieve_dir = ~/sieve
sieve_extensions = +vacation +vacation-seconds
sieve_global_dir = /var/lib/dovecot/sieve/global/
sieve_vacation_default_period = 1h
sieve_vacation_max_period = 30d
sieve_vacation_min_period = 0
}
postmaster_address = t...@mondialline.com.br
protocols = imap lmtp sieve
service dict {
unix_listener dict {
group = vmail
mode = 0600
user = vmail
}
}
service imap-login {
inet_listener imap {
port = 143
}
inet_listener imaps {
port = 993
ssl = yes
}
process_min_avail = 10
}
service imap {
process_limit = 2048
}
service managesieve-login {
inet_listener sieve {
port = 4190
}
}
shutdown_clients = no
ssl_cert = /var/qmail/control/cert.pem
ssl_key = /var/qmail/control/cert.pem
submission_host = mail.mondialline.com.br:25
userdb {
args = /etc/dovecot/dovecot-ldap.conf.ext
default_fields = uid=vmail gid=vmail home=/dados/vmail/%u
driver = ldap
}
protocol lmtp {
auth_socket_path = director-userdb
}
protocol lda {
mail_plugins = zlib sieve
}
protocol imap {
mail_max_userip_connections = 500
mail_plugins = zlib imap_zlib
}
protocol sieve {
mail_max_userip_connections = 100
managesieve_max_line_length = 65536
}
Best regards,
--
Rudá Porto Filgueiras
http://python-blog.blogspot.com
http://twitter.com/rudaporto
Re: [Dovecot] qmail-ldap LDA Delivery and sieve
Hi,
s...@mondialline.com.br:
lda(sar): Fatal: Unknown argument: sar
Usage: dovecot-lda [-c config file] [-a address] [-d username] [-p
path]
[-f envelope sender] [-m mailbox] [-e] [-k]
It happens on messanges that could not be delivered and need to be
returned to the sender.
I would think this indicates that lda is trying to deliver the message
to sar when it should be delivering to s...@mondialline.com.br. Probably
you need to adjust your ldap user_attrs and user_filters so it returns
what lda needs, but that is just a guess after a short look at your
mail...
I also tried to use this way, as documented here:
http://wiki2.dovecot.org/LDA/Qmail
| /var/qmail/bin/preline -f /usr/lib/dovecot/dovecot-lda
This is the way I did it, but I had to add the HOME variable like so:
|HOME=/home/mail/$USER /var/qmail/bin/preline
-f /usr/local/libexec/dovecot/dovecot-lda
I dont' see anything obviously wrong with your settings, but I am
connecting to an active directory instead of an openldap server, so your
setup is different than mine:
Follow my settings:
# LDAP
scope = subtree
user_attrs = uidNumber=11184,gidNumber=2110
user_filter = ((objectClass=qmailUser)(uid=%u)(accountStatus=active))
pass_attrs=uid=user,userPassword=password,mailHost=host,=proxy_maybe=y
pass_filter = ((objectClass=qmailUser)(uid=%u)(accountStatus=active))
iterate_attrs = uid=user
iterate_filter = ((objectClass=qmailUser)(accountStatus=active))
# dovecot -n output:
# 2.1.7: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-5-xen-amd64 x86_64 Debian 6.0.7 ext4
default_client_limit = 8000
default_process_limit = 2048
disable_plaintext_auth = no
hostname = mail.mondialline.com.br
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
lda_original_recipient_header = X-Original-To
mail_gid = vmail
mail_location = maildir:/dados/vmail/%u/Maildir
mail_plugins = zlib
mail_privileged_group = vmail
mail_uid = vmail
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 vacation-seconds
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 = INBOX.
separator = .
type = private
}
passdb {
args = /etc/dovecot/master-users
driver = passwd-file
master = yes
pass = yes
}
passdb {
args = /etc/dovecot/dovecot-ldap.conf.ext
driver = ldap
}
plugin {
sieve = /dados/vmail/%u/.dovecot.sieve
sieve_dir = ~/sieve
sieve_extensions = +vacation +vacation-seconds
sieve_global_dir = /var/lib/dovecot/sieve/global/
sieve_vacation_default_period = 1h
sieve_vacation_max_period = 30d
sieve_vacation_min_period = 0
}
postmaster_address = t...@mondialline.com.br
protocols = imap lmtp sieve
service dict {
unix_listener dict {
group = vmail
mode = 0600
user = vmail
}
}
service imap-login {
inet_listener imap {
port = 143
}
inet_listener imaps {
port = 993
ssl = yes
}
process_min_avail = 10
}
service imap {
process_limit = 2048
}
service managesieve-login {
inet_listener sieve {
port = 4190
}
}
shutdown_clients = no
ssl_cert = /var/qmail/control/cert.pem
ssl_key = /var/qmail/control/cert.pem
submission_host = mail.mondialline.com.br:25
userdb {
args = /etc/dovecot/dovecot-ldap.conf.ext
default_fields = uid=vmail gid=vmail home=/dados/vmail/%u
driver = ldap
}
protocol lmtp {
auth_socket_path = director-userdb
}
protocol lda {
mail_plugins = zlib sieve
}
protocol imap {
mail_max_userip_connections = 500
mail_plugins = zlib imap_zlib
}
protocol sieve {
mail_max_userip_connections = 100
managesieve_max_line_length = 65536
}
Best regards,
--
Rudá Porto Filgueiras
http://python-blog.blogspot.com
http://twitter.com/rudaporto
Re: [Dovecot] Dovecot 2.2 LEMONADE extensions
On 3/29/2013 12:48 AM, Stephan Bosch wrote: On 3/28/2013 11:10 PM, Timo Sirainen wrote: On 28.3.2013, at 22.44, Ed W li...@wildgooses.com wrote: Also there's a good chance that Dovecot v2.3 will have an SMTP submission server with BURL support (that will simply forward the mail to a real SMTP server). A few weeks back I gave this a look and I made a functional prototype of that already. I'll commit it to my patch repository in a week or so. You can track Dovecot SMTP submission developments in this Mercurial patch queue (mq extension): http://hg.rename-it.nl/dovecot-2.2-patches/ The core functionality works, but there is still much work to be done. Regards, Stephan.
[Dovecot] auth: passwd file (info): unknown user
Hello,
the problem is: The users are system users (by Confixx) say webxpy.
But behind it e-mail puts of course address like
i...@domain.de and so on. Everything functions perfectly,
nevertheless, is following in the log.
…
… dovecot: auth: passwd file (jk): unknown user
… dovecot: auth: passwd file (jim.knuth): unknown user
… dovecot: auth: passwd file (info): unknown user
… and so on
It is tried obviously, before the domain part in the passwd file
to find user info … However, there is in it only webxpy.
How can I solve this dilemma, by which does this come then?
auth_username_format = %n
Thanks in advance
as attached mine dovecot-n
--
Mit freundlichen Grüßen,
with kind regards,
Jim Knuth
# 2.2.0 (bafcb428167b): /etc/dovecot/dovecot.conf
# OS: Linux 2.6.29.4-default i686 Debian 7.0
auth_master_user_separator = *
auth_mechanisms = plain login
auth_username_format = %n
auth_verbose = yes
auth_worker_max_count = 50
disable_plaintext_auth = no
listen = *
login_greeting = Mailserver ready.
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 {
inbox = yes
list = yes
location = maildir:~/Maildir
mailbox Ablage {
auto = subscribe
}
mailbox Drafts {
special_use = \Drafts
}
mailbox Entwurf {
auto = subscribe
special_use = \Drafts
}
mailbox Gesendet {
auto = subscribe
}
mailbox Junk {
special_use = \Junk
}
mailbox Papierkorb {
auto = subscribe
special_use = \Trash
}
mailbox Sent {
special_use = \Sent
}
mailbox Sent Messages {
special_use = \Sent
}
mailbox Spam {
auto = subscribe
special_use = \Junk
}
mailbox Trash {
special_use = \Trash
}
prefix =
}
passdb {
args = username_format=%n
driver = pam
}
plugin {
quota = maildir:User quota
quota_grace = 5%%
quota_status_nouser = DUNNO
quota_status_overquota = 552 5.2.2 Sorry, but Mailbox is full|Mailbox ist voll
quota_status_success = DUNNO
sieve = ~/.dovecot.sieve
sieve_before = /etc/dovecot/sieve/global/global.sieve
sieve_dir = ~/sieve
sieve_global_dir = /etc/dovecot/sieve/global/
sieve_global_path = /etc/dovecot/sieve/global/global.sieve
trash = /etc/dovecot/dovecot-trash.conf.ext
}
postmaster_address = postmas...@art-domains.de
protocols = imap pop3 lmtp sieve
service auth {
unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0660
user = postfix
}
unix_listener auth-master {
mode = 0600
}
}
service imap-login {
client_limit = 128
process_limit = 256
service_count = 0
vsz_limit = 64 M
}
service lmtp {
unix_listener /var/spool/postfix/private/dovecot-lmtp {
group = postfix
mode = 0660
user = postfix
}
}
service managesieve-login {
inet_listener sieve {
port = 4190
}
service_count = 1
vsz_limit = 64 M
}
service pop3-login {
client_limit = 128
process_limit = 256
service_count = 0
vsz_limit = 64 M
}
service quota-status {
client_limit = 1
executable = quota-status -p postfix
inet_listener {
address = 127.0.0.1
port = 12340
}
}
ssl_cert = /etc/dovecot/certs/dovecot.pem
ssl_key = /etc/dovecot/private/dovecot.pem
userdb {
args = username_format=%n /etc/dovecot/passwd.quota
driver = passwd-file
}
verbose_proctitle = yes
protocol sieve {
mail_max_userip_connections = 10
managesieve_implementation_string = Dovecot Pigeonhole
managesieve_logout_format = bytes=%i/%o
managesieve_max_compile_errors = 5
managesieve_max_line_length = 65536
}
protocol imap {
imap_client_workarounds =
mail_fsync = never
mail_plugins = quota imap_quota trash
}
protocol pop3 {
mail_fsync = never
mail_plugins = quota trash
pop3_client_workarounds = outlook-no-nuls oe-ns-eoh
pop3_lock_session = yes
pop3_uidl_format = %v-%u
}
protocol lda {
mail_fsync = optimized
mail_plugins = quota sieve trash
postmaster_address = postmas...@art-domains.de
}
protocol lmtp {
mail_plugins = quota sieve trash
}
Re: [Dovecot] listen directive changed?
I do not get warnings, and,
listen = *, ::1, 2001:470:some:subnet::
_snip_
inet_listener imap {
address = *,[::]
port = 143
...
same with pop3
If I use 2001:470:some:subnet:: dovecot (2.1.16) answers
Sorry about previous direct message, darn gmail and darn bosses (
policy says cant use company email for public lists)
On 4/15/13, Timo Sirainen t...@iki.fi wrote:
On 13.4.2013, at 7.13, Nick Edwards nick.z.edwa...@gmail.com wrote:
Is the global listen directive supposed to be a governing directive,
like in apache? or is it there just in case you dont use it in
protocols?
I set a specific ipv6 address in global listen, but use [::] in proto
I don't understand what you mean by in proto. If you mean inside protocol
{} setting, that's a deprecated way and should log warnings about it.
Testing to a secondary IP, not in the global listen, it still
connects, so can I ask has the original use of global listen been
deprecated?
It's the default listen setting, which gets used by all services'
inet_listeners that don't override it.
