Re: Dovecot LDA errors
Hi Larry, all. My problem is in fact with the LDA, the issue is fixed in
the current nightly build, so I assume will be in the next stable
release. I've updated my system with the fix and deliveries are now
working normally. Thanks Martin for letting me know,
thanks, Andy.
PS Larry, attached is the patch in case you want to include it in the
FreeBSD package--- src/lda/main.c.orig 2018-06-01 19:24:10 UTC
+++ src/lda/main.c
@@ -330,7 +330,9 @@ int main(int argc, char *argv[])
case 'f':
/* envelope sender address */
if (smtp_address_parse_path(ctx.pool, optarg,
-SMTP_ADDRESS_PARSE_FLAG_BRACKETS_OPTIONAL,
+SMTP_ADDRESS_PARSE_FLAG_BRACKETS_OPTIONAL |
+ SMTP_ADDRESS_PARSE_FLAG_ALLOW_LOCALPART |
+ SMTP_ADDRESS_PARSE_FLAG_ALLOW_EMPTY,
_from, ) < 0) {
i_fatal_status(EX_USAGE,
"Invalid -f parameter: %s", errstr);
Re: Dovecot LDA errors
Ok thanks Larry, I'll have a look at LTMP on Monday and give you a shout if I want to see your configs, thanks a lot for the reply, Andy.
Dovecot LDA errors
Hi list, I'm having an issue on a server thats been running ok for years, its running Exim 4.91 onto of FreeBSD 10.4 with Dovecot 2.3.1. Recently I've started seeing messages getting stuck in the queue for local delivery and upon checking the Exim log I see this: 2018-06-01 17:31:09.339 [48228] 1fOmxJ-000CXp-3s : dovecot_delivery transport output: lda(a.smith): Fatal: Invalid -f parameter: Path is empty string 2018-06-01 17:31:09.339 [48228] 1fOmxJ-000CXp-3s == a.sm...@ldexgroup.co.uk R=virtual_localuser T=dovecot_delivery defer (0): Child process of dovecot_delivery transport returned 64 (could mean usage or syntax error) from command: /usr/local/libexec/dovecot/dovecot-lda I'm using this line for the LDA in my exim config: command = /usr/local/libexec/dovecot/dovecot-lda -d $local_part@$domain -f "$s ender_address" -a $original_local_part@$original_domain I haven't changed any of the config, but I have updated both Exim and Dovecot. So obviously the reason seems to be that $sender_address is null, the obvious place to look I suppose is Exim but I'm seeing this particularly for things like sieve out of office, which are generated by the LDA itself and then give this error when trying to deliver the out of office message to a local user. I'll post a question also to the Exim forum, but wondered if this problem rings any bells for anyone on here? thanks in advance! Andy.
offtopic: Solr compatible IMAP client
Hi, not sure if I'm allowed to go this off topic on here, sorry if not! I've just installed Solr FTS for Dovecot and its great, as is Dovecot! ;) It works perfectly for fast searches using Roundcube, but can anyone suggest any Windows and/or Linux mail clients that work well with IMAP searches rather than doing their own searches on local copies of mails? I've had a look at Thunderbird and you can use IMAP search, buy you have to manually select it from an advanced search dialogue and it seems you cannot make this the default behaviour. I also tried OperaMail but it doesn't appear to work at all (only header is searchable without downloading local copies). I'm pretty sure Outlook will only use its own search engine on its local copy of data. thanks a lot, Andy. PS this guide was really helpful for setting up Solr FTS with a recent release of Solr (I'm using 6.5), might be worth including a link somewhere on the Dovecot wiki?: http://mor-pah.net/2016/08/15/dovecot-2-2-with-solr-6-or-5
[Dovecot] Dovecot 2.0 config bug with SSL certificate per protocol?
Hi,
yesterday I upgraded Dovecot from 1.2 to 2.0.11. I'd seen that there was
a config file converter to make the upgrade smooth so was expecting it to
be pretty quick and easy. In the end I spent a long time trying to get it
working as it just wouldn't listen on the ssl ports, imaps and pop3s. I am
using per portocol SSL certificates, as I was in version 1.2. The part of
my config is as follows (as generated by doveconf):
protocol imap {
imap_client_workarounds = delay-newmail tb-extra-mailbox-sep
mail_plugins = fts fts_squat
ssl = yes
ssl_cert = /usr/local/etc/ssl.crt/imap.crt
ssl_key = /usr/local/etc/ssl.key/imap.key
}
protocol pop3 {
pop3_client_workarounds = outlook-no-nuls oe-ns-eoh
pop3_uidl_format = %08Xu%08Xv
ssl = yes
ssl_cert = /usr/local/etc/ssl.crt/pop3.crt
ssl_key = /usr/local/etc/ssl.key/pop3.key
}
But when I started dovecot it was only listening on the non SSL ports for
IMAP and POP3. I went through many things, adding in a service imap-login
section with the SSL port set via inet_listener and spent ages googling
for how to get it to work. In the end it turns out it was that the global
ssl setting was set to no, but I hadn't enabled this previously as this
requires that there are global SSL certificates, which I don't have; I
have specific certs for IMAP and for POP3. Also this isn't how dovecot 1.2
worked, there I specificed the protocols (pop3, pop3s, imap, imaps) and
specificed the protocol certs and it worked.
Anyway, I ended up just specifiing my pop3 certs as the global certs, this
is then redefined in the pop3 protcol section etc. The config seems to
work, but to me all this doesn't seem logical and doesn't work like in
dovecot 1.2.
Maybe this is something that can be cleaned up in the next version?
thanks Andy.
Re: [Dovecot] New install authentication probs (Solved)
Update on this problem, seems the only issue I had was that the telnet method of verifying IMAP authentication that works on Courier just doesnt work with Dovecot. I tried connected to Dovecot with an IMAP client (IMP webmail) and I get a load of info logged about authenitaction. Duno why I cant test via telnet but anyway, now I have fixed my config probs and have a working Dovecot server, thanks Andy.
[Dovecot] New install authentication probs
Hi, Im attempting to configure dovecot for the first time, Im trying to use a MySQL DB that is currently used by tpop3d as Ive read they support the same password format. My main prob currently, apart from that it doesnt work lol, is that Ive enabled the following debugging in dovecot.conf auth_debug = yes auth_debug_passwords = yes auth_verbose = yes But Im getting basically zero info on why my authentication is failing. In my log (which for testing Ive defined as a file in /tmp to make sure Im getting all the info logged to one place) I see just: Mar 31 19:00:17 dovecot: Info: Dovecot v1.2.10 starting up Mar 31 19:00:17 auth-worker(default): Info: mysql: Connected to localhost (ukgri d_vmail) Mar 31 19:00:18 auth(default): Info: new auth connection: pid=64188 Mar 31 19:00:18 auth(default): Info: new auth connection: pid=64186 Mar 31 19:00:18 auth(default): Info: new auth connection: pid=64187 each time I attempt to connect via IMAP it adds another new auth connection line to the log but doesnt tell me anything else :(. So Im stuck debugging my authentication due to lack of info. BTW Im testing IMAP via telnet, telnet to IMAP port and attempt LOGIN (I have this working to a courier IMAP installation). Have I done something wrong? Any help appreciated! thanks Andy.
Re: [Dovecot] New install authentication probs
Hi Brad, thanks for the reply, here is the output: dovecot -n # 1.2.10: /usr/local/etc/dovecot.conf # OS: FreeBSD 6.1-RELEASE i386 nfs log_path: /tmp/dovecot.log protocols: imap ssl: no disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 1000 mail_privileged_group: mail mail_location: maildir:/var/spool/mail/%d/%u mail_debug: yes imap_client_workarounds: delay-newmail netscape-eoh tb-extra-mailbox-sep lda: sendmail_path: /usr/sbin/sendmail auth default: mechanisms: plain digest-md5 cram-md5 username_format: %Lu verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: passwd args: blocking=yes userdb: driver: sql args: /usr/local/etc/dovecot-sql.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384
Re: [Dovecot] New install authentication probs
Ola Daniel, thanks for the idea, but actually within the config file the settings are not within the auth default section, its just shown that way from the output of dovecot -n cheers Andy. Quoting Daniel Gomes daniel.go...@ist.utl.pt: Hey Andy, I might be way over my head here, but unlike you, in my setup I set auth_debug, auth_verbose and auth_debug_password to yes outside the auth default section. Try that and see if you get the verbose logging you're looking for! Cheers, On 31-03-2010 19:46, Andy Smith wrote: Hi Brad, thanks for the reply, here is the output: dovecot -n # 1.2.10: /usr/local/etc/dovecot.conf # OS: FreeBSD 6.1-RELEASE i386 nfs log_path: /tmp/dovecot.log protocols: imap ssl: no disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 1000 mail_privileged_group: mail mail_location: maildir:/var/spool/mail/%d/%u mail_debug: yes imap_client_workarounds: delay-newmail netscape-eoh tb-extra-mailbox-sep lda: sendmail_path: /usr/sbin/sendmail auth default: mechanisms: plain digest-md5 cram-md5 username_format: %Lu verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: passwd args: blocking=yes userdb: driver: sql args: /usr/local/etc/dovecot-sql.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 -- Daniel Gomes, 55350
