[Dovecot] Installing Dovecot v2.0.3 from binary files problem
Hi, I've installed dovecot v2.0.13 from binary files.dovecote starts ok,but I get some errors in /var/run/mail.log : dovecot: anvil: Fatal: Error reading configuration: read(/var/run/dovecot/config) failed: EOF dovecot: master: Error: service(anvil): command startup failed, throttling dovecot: master: Error: service(config): child 8606 killed with signal 11 (core dumps disabled) dovecot: master: Error: service(config): command startup failed, throttling dovecot: ssl-params: Fatal: Error reading configuration: read(/var/run/dovecot/config) failed: Connection reset by peer And I've just used example configure files of dovecot. Regards, Meisam Navaki. System Programmer, Bayan Co.
[Dovecot] Dovecot 1.2.16 -> Dovecot 2.0.13 Performance?
Hello list, Currently running dovecot-1.2.16 as pop, imap, and deliver (with sieve). All on Solaris 10u9, on NFSv4 backends. All is working great. But occasionally, the system gets rather loaded, not entirely sure what part yet, but as part of researching that; If we were to start the upgrade path to dovecot 2.0.13, are there any known areas of performance increase which should encourage us to do this? Since we have a stable system, there is hesitation in changing any part of it :) Each NFS server hosts about 92,381 mailboxes, LDAP as authentication and ZFS user quotas. What sort of numbers do others manage generally? Cheers, Lund -- Jorgen Lundman | Unix Administrator | +81 (0)3 -5456-2687 ext 1017 (work) Shibuya-ku, Tokyo| +81 (0)90-5578-8500 (cell) Japan| +81 (0)3 -3375-1767 (home)
Re: [Dovecot] Virtual Servers
I think we all know who the troll is here On Tue, 2011-06-28 at 07:14 -0400, Charles Marcus wrote: > On 2011-06-27 9:06 PM, Noel Butler wrote: > > On 2011-06-27 9:21 PM, Jonathan Tripathy wrote: > >> I hope this is a lightly used server and does not do any real level > >> of mail traffic else you'll soon regret running in any VM :) > > > Don't mean to start a flame war, but your statement above is just > > simply inaccurate. > > Please don't feed the troll... > > > Noel: I tried to reply to your email off list, but it bounced :( > > That's what you get for replying to trolls... Noel uses brain-dead > anti-spam measures. I plonked him long ago... >
[Dovecot] Exim and Dovecot2 SASL: 435 Unable to authenticate at present
Hi. I had working Exim 4.71 and Dovecot 1.2.9 SASL configuration on
Ubuntu Lucid, but needed some features from dovecot2, so I installed
2.0.13 from
https://launchpad.net/~carsten-uppenbrink-net/+archive/dovecot2 . Now I
get Subj error while trying to authenticate via dovecot auth-client
socket. However IMAP auth works fine with 2.0.13 and smtp auth worked
fine until upgrade, so I think there is something wrong with dovecot2.
Dovecot logs stay empty even with auth_debug*, just one string "auth:
Debug: Loading modules from bla...". But here is another information
that may help. And if it's needed I can build dovecot myself to ensure
that ppa-build isn't guilty. Or debug some another way.
Thanks.
dovecot -n:
# 2.0.13: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-31-server x86_64 Ubuntu 10.04.2 LTS
auth_debug = yes
auth_debug_passwords = yes
auth_mechanisms = plain login apop
auth_verbose = yes
disable_plaintext_auth = no
first_valid_gid = 8
first_valid_uid = 8
hostname = mail.domain.lan
last_valid_gid = 8
last_valid_uid = 8
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
listen = *
mail_gid = mail
mail_location = maildir:~/
mail_plugins = " quota trash"
mail_privileged_group = mail
mail_uid = mail
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
passdb {
args = scheme=CRAM-MD5 username_format=%n
/etc/dovecot/passwd.d/%d.passwd
driver = passwd-file
}
plugin {
autocreate = Trash
autocreate2 = Junk
autocreate3 = Drafts
autocreate4 = Templates
autocreate5 = Sent
autosubscribe = Trash
autosubscribe2 = Junk
autosubscribe3 = Drafts
autosubscribe4 = Templates
autosubscribe5 = Sent
quota = maildir:user quota
quota_rule = *:storage=200M
sieve = ~/dovecot.sieve
sieve_dir = ~/sieve
trash = /etc/dovecot/dovecot-trash.conf.ext
}
postmaster_address = postmas...@domain.lan
protocols = " imap sieve pop3 sieve"
service auth {
unix_listener auth-client {
mode = 0600
user = Debian-exim
}
unix_listener auth-userdb {
mode = 0600
user = mail
}
}
service managesieve-login {
inet_listener sieve_deprecated {
port = 2000
}
}
ssl_cert = imap_client_workarounds = delay-newmail tb-extra-mailbox-sep
tb-lsub-flags
mail_plugins = " quota trash imap_quota"
}
protocol pop3 {
pop3_client_workarounds = outlook-no-nuls oe-ns-eoh
}
##
swaks --to t...@domain.lan --from=t...@domain.lan --auth
--auth-user=t...@domain.lan --auth-password=11 --server 127.0.0.1
-tlsc: (the same without tls, apop)
=== Trying 127.0.0.1:465...
=== Connected to 127.0.0.1.
=== TLS started w/ cipher DHE-RSA-AES256-SHA
<~ 220 mail.domain.lan, ESMTP ready
~> EHLO mail.domain.lan
<~ 250-mail.domain.lan Hello mail.domain.lan [127.0.0.1]
<~ 250-SIZE 26214400
<~ 250-PIPELINING
<~ 250-AUTH PLAIN LOGIN
<~ 250 HELP
~> AUTH LOGIN
<~* 435 Unable to authenticate at present
~> AUTH PLAIN AHRlc3RAZG9tYWluLmxhbgAxMTExMTE=
<~* 435 Unable to authenticate at present
*** No authentication type succeeded
~> QUIT
<~ 221 mail.domain.lan closing connection
=== Connection closed with remote host.
#
exim -d+auth output:
Exim version 4.71 uid=0 gid=0 pid=29270 D=fbb95cfd
Berkeley DB: Berkeley DB 4.8.24: (August 14, 2009)
Support for: crypteq iconv() IPv6 PAM Perl Expand_dlfunc GnuTLS
move_frozen_messages Content_Scanning DKIM Old_Demime
Lookups: lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmnz dnsdb
dsearch ldap ldapdn ldapm mysql nis nis0 passwd pgsql sqlite
Authenticators: cram_md5 cyrus_sasl dovecot plaintext spa
Routers: accept dnslookup ipliteral iplookup manualroute queryprogram
redirect
Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp
Fixed never_users: 0
Size of off_t: 8
GnuTLS compile-time version: 2.8.5
GnuTLS runtime version: 2.8.5
changed uid/gid: forcing real = effective
uid=0 gid=0 pid=29270
auxiliary group list:
seeking password data for user "root": cache not available
getpwnam() succeeded uid=0 gid=0
configuration file is /etc/exim4/exim4.conf
log selectors = cefe 00233821
cwd=/ 4 args: /usr/sbin/exim4 -bd -q30m -d+auth
trusted user
admin user
seeking password data for user "Debian-exim": cache not available
getpwnam() succeeded uid=103 gid=105
seeking password data for user "Debian-exim": using cached result
getpwnam() succeeded uid=103 gid=105
seeking password data for user "mail": cache not available
getpwnam() succeeded uid=8 gid=8
originator: uid=0 gid=0 login=root name=root
29270 LOG: MAIN
29270 IPv6 socket creation failed: Address family not supported by
protocol
29270 LOG: MAIN
29270 Failed to create IPv6 socket for wildcard listening (Address
family not supported by protocol): will use IPv4
29270 listening on all interfaces (IPv4) port 25
29270 LOG: MAIN
29270 IPv6
Re: [Dovecot] what to expect from changing index location
On 2011-06-28 12:13 PM, Davide Vaghetti wrote: > mail_location = mdbox:/var/vmail/%-1.1u/%u/mdbox > > and I want to switch to > > mail_location = > mdbox:/var/vmail/%-1.1u/%u/mdbox:INDEX=/var/indexes/%-1.1u/%u/ > > But I cannot figure out a pair of things: > > - - do the switch trigger the rebuilding of the index files? > > - - can I get rid of all the old index files? I'm by no means an expert, but with that many users I think if you did this in one shot (all indexes being rebuilt simultaneously as users logged in) your system would slow to a crawl... I would first rsync the existing indexes over live, then stop dovecot, do another quick rsync of the indexes, then make the change and restart dovecot... That will minimize the impact (rebuilding of indexes)... -- Best regards, Charles
[Dovecot] mirate to dovecot 2.0.13
Hi, I have in my system dovecot 1.2.11 and i want migrate to dovecot 2.0.13. I have 2 Frontend that proxy all request to Backend and i want migrate first FE and after the BE. Can i install dovecot 2.0.13 in FE that proxy all request to BE with dovecot 1.2.11? Thanks
[Dovecot] what to expect from changing index location
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello everybody, I have one thousand virtual users with mdbox mailbox format and 10 GByte quota. I have noticed some performance problem related to I/O (the mailbox disk is a 6TB raid1+0 on ISCSI), so I want to put the index files on a different disk. My actual mail_location is: mail_location = mdbox:/var/vmail/%-1.1u/%u/mdbox and I want to switch to mail_location = mdbox:/var/vmail/%-1.1u/%u/mdbox:INDEX=/var/indexes/%-1.1u/%u/ But I cannot figure out a pair of things: - - do the switch trigger the rebuilding of the index files? - - can I get rid of all the old index files? - - how much the index files (no fts squat) can grow? thanks in advance bye davide - -- Dott. Davide Vaghetti Centro Servizi Informatici Facolta' di Ingegneria Universita' di Pisa PGP: http://keys.keysigning.org:11371/pks/lookup?op=get&search=0x7A1B3BA18C4E0A4D -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk4J/Z4ACgkQehs7oYxOCk3QagCfd+yVvR2Ps6hbjZOCumn2Wx2W 6cgAnjOvQDfe1O9jDOAbp4k0deEmytd3 =ZJFQ -END PGP SIGNATURE-
Re: [Dovecot] permissions for dbox attachment directory
> On Sat, 2011-06-25 at 03:58 -0400, i...@tnde.org wrote: >> I am running dovecot 2.0.13 on CentOS5, set up with only local system >> users, and single instance store set up in a single directory. >> >> e.g. >> mail_attachment_dir = /var/mail/attachments > > Currently you can't. I was a bit lazy in implementing this code not to > preserve permissions. The idea would be anyway that you could > make /var/mail/attachments 02770 and e.g. group=mail. Then set > mail_access_groups=mail to Dovecot. Now the code should have created new > directories under that with the same permissions and the files as 0660, > but looks like it doesn't. The code is in src/lib-fs/fs-posix.c if you > want to fix it yourself. You could as a workaround simply change all > 0600 -> 0660 and 0700 -> 0770 and I guess it would work. > Ok, if I understand you correctly, I would need to chmod to 660/770, but it would only work on existing folders, and every new item will be created as 600/700? I guess the best way is setting up virtual users, presumably these work under a single system account? (for the time being this is running on a test server, using the simplest setup with system users) Thanks for your help!
[Dovecot] Sendmail + dovecot-lda + LDAP
Hi, I experince some problems with setting up Sendmail with the LDAP database for virtual mail accounts. Why i'm not writing to the LDAP mailing list? I believe, that the reason of my problem is in configuring dovecot-deliver. What i have: - FreeBSD 8.2-RELEASE - sendmail (Version 8.14.4 with LDAP support installed from ports) - Dovecot LDA + dovecot (as pop3/imap) - 1.2.16 - Cyrus Sasl (authdaemon for authentification) 1. Following http://wiki.dovecot.org/LDA/Sendmail i've set up deliver as LDA. Everything worked fine. 2. Following http://wiki.dovecot.org/HowTo/DovecotOpenLdap i've set up Dovecot to work with tha ldap. Now i can authorize through the client or web interface and get to my maildir. 3. Now, i want my sendmail to accept mail for the account in LDAP database. sendmail.mc: ++ FEATURE(`local_procmail', `/usr/local/libexec/dovecot/deliver',`/usr/local/libexec/dovecot/deliver -d $u') MODIFY_MAILER_FLAGS(`LOCAL', `-f') .. define(`confLDAP_DEFAULT_SPEC', `-h "localhost" -b "dc=mydomain,dc=ru" -d "cn=dovecot,ou=accounts,dc=mydomain,dc=ru" -MLDAP_AUTH_SIMPLE -P /etc/mail/ldap_pass')dnl LDAPROUTE_DOMAIN(`mydomain.ru')dnl FEATURE(`ldap_routing', `null -T', `ldap -1 -T -v mail -k (&(objectclass=posixaccount)(mail=%0))', `passthru')dnl .. MAILER(procmail) ++ After re-making the sendmail: ++ [root@test2 /etc/mail]# sendmail -bv -d60.1 test_u...@mydomain.ru map_lookup(dequote, test) => NOT FOUND (0) map_lookup(host, mydomain.ru) => mydomain.ru. (0) map_lookup(dequote, test_user) => NOT FOUND (0) map_lookup(ldapmra, test_u...@mydomain.ru) => test_u...@mydomain.ru (0) map_lookup(ldapmh, test_u...@mydomain.ru) => NOT FOUND (68) map_lookup(host, mydomain.ru) => mydomain.ru. (0) map_lookup(dequote, test_user) => NOT FOUND (0) map_lookup(virtuser, test_u...@mydomain.ru) => NOT FOUND (0) map_lookup(virtuser, @mydomain.ru) => NOT FOUND (0) test_u...@mydomain.ru... User unknown ++ It's the problem of the local delivery, i believe. Why? Because after sendmail getting an email it passes it to the LDA, which must check the LDAP (not the passwd!) database for the user, to which this email is send to. Are there some possibilities to solve this problem? I appreciate any help... --- Best regards, Vasily Yakovlev --
Re: [Dovecot] Virtual Servers
On 2011-06-27 9:06 PM, Noel Butler wrote: > On 2011-06-27 9:21 PM, Jonathan Tripathy wrote: >> I hope this is a lightly used server and does not do any real level >> of mail traffic else you'll soon regret running in any VM :) > Don't mean to start a flame war, but your statement above is just > simply inaccurate. Please don't feed the troll... > Noel: I tried to reply to your email off list, but it bounced :( That's what you get for replying to trolls... Noel uses brain-dead anti-spam measures. I plonked him long ago... -- Best regards, Charles
Re: [Dovecot] hide sieve folder from imap clients
2011/6/27 Thomas Leuxner :
>> new config (hide sieve folder)
>>
>> mail_home = /var/vmail/%d/%n
>> maildir_stat_dirs = yes
>>
>> plugin {
>> sieve_dir = /var/vmail/%d/%n/sieve/
>> sieve = /var/vmail/%d/%n/.dovecot.sieve
>> }
>
> All the examples look a bit overcomplicated. Why not go with the "defaults"?
>
> mail_location = maildir:~/maildir
> sieve = ~/.dovecot.sieve
>
> However this relies on home dirs being returned from the user lookups which
> has not been revealed in the OP's partial config post.
Okay, here is my new config:
mail_home = /var/vmail/%d/%n/
mail_location = maildir:/var/vmail/%d/%n/maildir
plugin {
sieve_dir = /var/vmail/%d/%n/.sieve
sieve = /var/vmail/%d/%n/.dovecot.sieve
}
How should I configure mysql?
user_query = SELECT CONCAT('maildir:/var/vmail/',maildir) AS mail,
6000 AS uid, 6000 AS gid FROM mailbox WHERE username = '%u' AND active
= '1'
or
user_query = SELECT maildir, 6000 AS uid, 6000 AS gid FROM mailbox
WHERE username = '%u' AND active = '1'
mysql query return:
maildir: domain.com/user/
Thank you for your help.
--
Christopher
Re: [Dovecot] Question about "Storage keeps breaking" in logs
This dovecot box (RHEL 5.6 x64, dovecot 2.0.13, ext4) is a VM over vmware vsphere. The remote SAN disks are presented via iSCSI to the ESX hosts, and the ESX host show them as "local storage" /dev/sdX We have several VM sharing that datastore, no I/O contention detected. I will try with imaptest but this a production enviroment, I will take a couple of weeks to get a "mainteneance window" for this. Any other idea about this? Maybe this problem is load-related? Regards Maria - Original Message - From: Timo Sirainen Sent: 06/28/11 01:33 AM To: Maria Arrea Subject: Re: [Dovecot] Question about "Storage keeps breaking" in logs On Wed, 2011-06-22 at 19:32 +, Maria Arrea wrote: > Jun 6 17:03:23 buzon dovecot: imap(juanan): Warning: mdbox /buzones/18/66/juanan/storage: rebuilding indexes Problem 1: It doesn't log the reason for this rebuild. I can find only one place in code why that could happen, fixed: http://hg.dovecot.org/dovecot-2.0/rev/028b953e7040 > Jun 6 17:03:26 buzon dovecot: imap(juanan): Error: mdbox /buzones/18/66/juanan/mailboxes/P7.Bielorrusia/cd-eslpod-enviado/dbox-Mails: Storage keeps breaking Problem 2: It apparently can't fix that error. But in my tests it gets fixed fine.. > Jun 6 17:03:27 buzon dovecot: imap(juanan): Error: Recent flags state corrupted for mailbox Deleted Messages Probably related to the index rebuild. So this is a local disk with ext4 filesystem, nothing special? It shouldn't be breaking.. How often do these happen? Can you reproduce these by running imaptest against a test account? http://imapwiki.org/ImapTest
[Dovecot] Problem accessing Dovecot mailing lists via IMAP
I recently tried to look at the Dovecot mailing lists through an already-configured IMAP profile, which had worked fine in the past. But it failed saying that the authentication method was not supported. http://www.dovecot.org/mailinglists.html says: "You can get access to the IMAP archives by using *dovecot.org* as the hostname, *anonymous* as the username and an empty password. It's also possible to use ANONYMOUS authentication mechanism if your client supports it (few do)." I noticed that my e-mail client was configured to use the server "imap.dovecot.org", so I changed it to "dovecot.org". But it still complains that the authentication method is not supported. I am using Thunderbird 3.1 over Windows 7 64-bit. Thunderbird was configured for "Password, Transmitted insecurely" (and this option was not working). I have tried the other authentication options available in Thunderbird. "Encrypted password": Does not work; same problem "Kerberos / GSSAPI": Does not work; same problem "NTLM": Does not work; same problem Any ideas? Bill
Re: [Dovecot] ACLs: Group ACL adds empty ACL for user of same name, why?
On Tuesday 28 Jun 2011 00:55:02 Timo Sirainen wrote: > On Mon, 2011-06-27 at 14:40 +0100, Jim Hague wrote: > > If I set an ACL for a group 'developers' [...] > > The dovecot-acl file for INBOX.Trash then contains a group setting for > > the group, and a user setting for a user of the same name, giving it no > > permissions. > > Looks like a bug. I see it's fixed in v2.0 already. You can't get it > fixed to Debian stable .deb anyway, so I don't think there's much point > in trying to backport the fix. Thanks very much. I was worried that there was something subtle I'd missed; I was hoping it would turn out to be a Plain Old Bug. You're right about Squeeze. I'll start looking at 2.0 and backports. -- Jim Hague - jim.ha...@acm.org Never trust a computer you can't lift.
Re: [Dovecot] Denying user won't work as expected
On 06/28/2011 02:11 AM, Timo Sirainen wrote:
On Mon, 2011-06-27 at 09:50 +0200, Frank Bonnet wrote:
passdb {
driver = ldap
deny = yes
# File contains a list of usernames, one per line
args = /usr/local/etc/dovecot/deny-users
}
I have tested writting one user (me) in the
/usr/local/etc/dovecot/deny-users
You have driver=ldap there, which means that LDAP tries to read the
deny-users file as its configuration file.
and the result is the login is denied for ALL users ...
I'm surprised that it even starts up..
If replacing driver=ldap with driver=passwd-file doesn't help, show your
actual dovecot -n output.
If I do that the denying does not work , I'we written my login in
/usr/local/etc/dovecot/deny-users and I am still able to log in ( after
restarting dovecot of course )
see attached the dovecot -n output
Thanks
# 2.0.12: /usr/local/etc/dovecot/dovecot.conf
# OS: FreeBSD 7.4-RELEASE amd64
auth_verbose_passwords = plain
auth_worker_max_count = 100
debug_log_path = /var/log/dovecot/debug.log
default_client_limit = 6144
default_process_limit = 1024
disable_plaintext_auth = no
info_log_path = /var/log/dovecot/info.log
log_path = /var/log/dovecot/dovecot.log
mail_location =
mbox:%h/:INDEX=/raid/cache/dovecot/index/%u:INBOX=/raid/var/mail/%u
mail_temp_dir = /var/tmp
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
mbox_lock_timeout = 3 mins
mbox_write_locks = fcntl
mmap_disable = yes
passdb {
args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext
driver = ldap
}
plugin {
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
}
postmaster_address = postmas...@esiee.fr
protocols = imap pop3
sendmail_path = /usr/local/sbin/sendmail
service auth {
client_limit = 7169
}
service imap-login {
inet_listener imap {
port = 143
}
inet_listener imaps {
port = 993
ssl = yes
}
process_min_avail = 10
service_count = 1
vsz_limit = 1 G
}
service imap {
process_limit = 2048
vsz_limit = 1 G
}
service managesieve-login {
inet_listener sieve {
port = 4190
}
inet_listener sieve_deprecated {
port = 2000
}
}
service pop3-login {
inet_listener pop3 {
port = 110
}
inet_listener pop3s {
port = 995
ssl = yes
}
}
ssl_ca = /etc/ssl/RENATER/chain-1828-mail.esiee.fr.pem
ssl_cert =
Re: [Dovecot] Dovecot 2.0.13 problem with LMTP
Hello Timo, so far I've seen this happening when proxying a mail for one recipient; I've never seen this happening for multiple recipients. The other thing I've noticed is that if I reload dovecot, the mail usually gets delivered. Once, it remained stuck in the queue, but after a few hours, when I checked postfix's queue again, it got delivered. Let me know if you need further information. Regards, CINZIA INNOCENZI Technical Consulting HP Enterprise Services Telephone +39 06.6542.5758 Email cinzia.innoce...@hp.com Via Achille Campanile, 85 / Rome, Italy 00143 -Original Message- From: Timo Sirainen [mailto:t...@iki.fi] Sent: martedì 28 giugno 2011 2.04 To: Innocenzi, Cinzia Cc: dovecot@dovecot.org; Del Coiro, Maria Giacinta Subject: Re: [Dovecot] Dovecot 2.0.13 problem with LMTP On Wed, 2011-06-22 at 10:31 +, Innocenzi, Cinzia wrote: > Hello, > > we have dovecot 2.0.13 installed in our RHEL5 servers. We use dovecot > as a lmtp proxy on the front end mail relays and dovecot for back end > lmtp/pop/imap. All our servers have RHEL5.6 64-bit and dovecot 2.0.13 > installed, and the back end has also an ext3 mbox file-system mounted. > > Sometimes we have mails that get stuck on our postfix queue with the > following error: Remote server not answering (timeout in DATA input) > (in reply to end of DATA command) .. > It doesn't happen for every single mail, it's random. My guess is there's a bug somewhere in the LMTP proxy code. It's a bit annoyingly complex code.. Do you see this happening when proxying only a single mail (one RCPT TO per DATA, not multiple)? And I would guess that when attempting to deliver the same mail again it works fine (at least in a few tries)?
Re: [Dovecot] LMTP returncode 450?
On 2011-06-28 01:58, Timo Sirainen wrote: On Mon, 2011-06-27 at 14:55 +0200, Peter Mogensen wrote: How do I get the LMTP-server to know which mailbox's are locally hosted and return SMTP code 450 if delivery is attempted to a non local user? You can't, at least that way. Why are you trying to deliver mails to a non-local mailbox? You could anyway use Dovecot as LMTP proxy to the remote LMTP server and it would deliver the mail there without an error. I was wondering if I could skip running a Postfix or other MTA along with dovecot and just let mail be delivered directly to the final host by LMTP. It's no problem to have Postfix do a virtual_mailbox_domains lookup before handing it to local LMTP, but it would be simpler with only Dovecot. I can see that a lookup in the userdb is done, but now matter what I return (1/111) from my checkpassword script I just get: Set lmtp_proxy=yes and have passdb lookup return proxy=y and host=1.2.3.4. But how does the LMTP proxy deal with temporary errors? It has no queue like the SMTP-server ? /Peter
[Dovecot] Dovecot communication with sasl in dovecot source code
Hi all, I'm reading dovecot source codes(2.0.13),and I need to know how dovecot communicate with sasl? I traced the source code from cmd_login function,and found out something about sasl_callback. but i never found where this function called and also I couldn't understand how sasl inform the dovecot from authentication result. I'll be thankful if someone could help me out.
[Dovecot] Hi
Hi all, I'm reading dovecot source codes(2.0.13),and I need to know how dovecot communicate with sasl? I traced the source code from cmd_login function,and found out something about sasl_callback. but i never found where this function called and also I couldn't understand how sasl inform the dovecot from authentication result. I'll be thankful if someone could help me out.
