May 2014 - dovecot - dovecot.org

Re: [Dovecot] LMTP error
by Reindl Harald 01 May '14

01 May '14

Am 01.05.2014 19:43, schrieb IT geek 31: > On 1 May 2014 19:41, Reindl Harald: > > that you are working with unix-accounts and the root uid 0 > is prohibited for (good) saftey reasons > > Okay, that sounds good. How do I deliver mail to the root account then, and stop this error/warning/message? As > mails are now backing up in the queue and cannot be delivered... keep your responses on the list! * set a alias on the postfix side to another mail-address * that way dovecot never see the root-address as destination * use "postsuper -d queue_id" to kill the messages from the queue ______________________________ cat /etc/aliases | grep root # Person who should get root's mail root: h.reindl(a)thelounge.net ______________________________ don't forget calling "newaliases" after changes in that file if you have implemented aliases on postfix in a different way follow the documentation

2 1

[Dovecot] LMTP error
by IT geek 31 01 May '14

01 May '14

Hi, I've recently switched to LMTP as I'm now using mdbox. However since switching, mails sent to the root account do not get delivered due to the following error: May 1 18:20:17 Server1 postfix/lmtp[13019]: CAEE91F851: to=<root(a)test.com>, relay=mail.test.com[private/dovecot-lmtp], delay=1097, delays=1096/0.45/0.43/0.46, dsn=4.3.0, status=deferred (host mail.test.com[private/dovecot-lmtp] said: 451 4.3.0 <root(a)test.com> Invalid user settings. Refer to server log for more information. (in reply to RCPT TO command)) This obviously fills up my mail queue. All other mails to all other mailboxes deliver fine. I'm obviously missing something in my config... any ideas? I'm using Dovecot 2.2.12 on NetBSD 5.2.2. Many thanks, -Mark dovecot -n # 2.2.12: /usr/pkg/etc/dovecot/dovecot.conf # OS: NetBSD 5.2.2 cobalt auth_username_format = %Ln doveadm_password = secret doveadm_port = 12345 first_valid_uid = 1010 last_valid_uid = 1020 listen = 192.168.1.1 login_greeting = test.com mail_location = mdbox:~/mdbox mail_plugins = " notify replication" 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 = } passdb { driver = passwd } passdb { driver = passwd } plugin { mail_replica = tcp:Server2.test.com } protocols = imap lmtp service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0600 } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = root } service imap-login { inet_listener imap { port = 0 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0777 } } ssl_cert = </etc/openssl/certs/mail.test.com.crt ssl_key = </etc/openssl/private/mail.test.com.key userdb { driver = passwd } userdb { driver = passwd } protocol lda { postmaster_address = postmaster(a)test.com }

3 7

[Dovecot] fts-lucene configuration
by Gregory Finch 01 May '14

01 May '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, Is there a configuration option to set where fts-lucene stores its indexes? I know it defaults to lucene-indexes in the mail root directory. I'm looking to store it in the home directory. Thank you, Greg -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTYmPZAAoJECD7Htp+IT9epBIQAKnR+cBtMZ8kkpvTefI/oVG6 ANu/gB/VGamrommOl0w+9/E0YwowdfqB3IqQuavR47KtPHE6X8gxyRf4p26p3dfC X13KCrdBvDQ0AArqi1RH4Blig2zFcLvC85QyBOvGKnYKg90wBKRODYdw9it8cU0P 1eJMkURCR5llIKUEnFQH1OBUr1rJ4c+tkke0fuxeikcoaS3DtW7LdPCQaJyYpUdS NmFehIG+n3jDQqx1jDJNBBQMlfSEz+svXFuHzAR/YCeQS8ETBQdQ7cC5ES5gBijy Z0f1bTRWhLOC9rcg3VzcbGm1ky+rAJeEVL1HGXluPOJjqLhjWvaDE+ola2cDHtNk IiVXtL4WdIAvSJ51kR8X3ubSWtHd+2mo93ryQqCE+AdhWh0lMNzxMB/r8LmVHMKY eMjFmu1QvC+W1Z20xUT5SZKFIIOnXzHZbzugkz2zKZEQbJw9AtdTrIwJ+CyxY+YN yREwPFJ2dGzglWtzk/lxAgRZUizAJEvmcLQ8n5ZPi4aX6SfZyYcD0t7nkAOVD3ff VsJdvYJeiPcoWLrQnemI4wAaClINw+7vLg4D+uiGLswyTtR4ccTg0wOUG6Bp8Jkv dMFRWLwJsK3dLYubLud9T2nlyMBG63hEyoDjgE8WxXXuIAYaYTTMUuGAf89fdwLN bgpfg40wgCfheu18qD9d =EDIQ -----END PGP SIGNATURE-----

1 0

[Dovecot] Problems with login_log_format (possible bug?)
by Trever L. Adams 01 May '14

01 May '14

login_log_format = %$: %s login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c session=<%{session}> These are the defaults, at least on a Fedora system. According to http://wiki2.dovecot.org/Variables, this should record for user@REALM when seeing the following Apr 30 18:08:40 TeaSet dovecot: auth: Debug: auth(user,...,<JhKid0v4bAAKAQG6>): username changed user -> user@REALM. If I wanted just user, user=<%u> should be changed to user=<%orig_user>. However, I only get user not user@REALME in imap-login log lines. I wouldn't mind this, but auth_username_format cannot be used in passed{} and I haven't been able to get pam_krb5 to uppercase the realm for it alone. (Everything else depends on it being lowercase.) I can make this work by just passing the user name part of username in the client, but then imap-login still doesn't have the required information for the same reason. Anyone have any suggestions? Thank you, Trever

1 0