similar to: Solaris problem & exim. Please ignore it.

I've trying to get dovecot-auth to talk to exim and have been running debugging on both sides. I've added the line: i_info("auth_client_input: client disconnected: %s", strerror(errno)); just after the "case -1" in the first switch statement in: auth-client-connection.c: auth_client_input() and get this in the logs: dovecot: Feb 27 13:35:09 Info: auth(default):

So as to make sure that Dovecot Sieve's vacation system works Exim has to be forced to generate a "Reply-To:" header in the message (which it doesn't do by default). The current example for using the Dovecot LDA with Exim doesn't do this. Here is a replacement example for the local_delivery transport:- local_delivery: driver = pipe command =

Dovecot 2.1.16 fails to compile giving the following error under Solaris 10. Previously I had no problem compiling 2.1.12. The start of the config.log file contains: It was created by Dovecot configure 2.1.16, which was generated by GNU Autoconf 2.68. Invocation command line was $ ./configure ## --------- ## ## Platform. ## ## --------- ## hostname = luna uname -m = i86pc uname -r =

Seeing as many on this list are in the process of migrating their mailsystems not only to dovecot's IMAP/POP3 server but also using dovecot's deliver for delivering e-mail into users' folders I thought that it might be a good idea to share with you the perl script I've been labouring upon for the last few days which will translate a simple(ish) procmail recipe to an equivalent

Good day. I want to migrate from cyrus-imap to dovecot but I can not find replacement of one feauture presented in the cyrus-imap. It is LMTP. All mail users are virtual and mail works like: username at real-domain.com -> anotherusername at fake-domain.local. I whould like to check "delivery is possable" in the exim's ACL. In the exim+cirus scheme I use Callout verification from

Hello, When connecting to Exim 4.94, dovecot submission logs this warning: dovecot[25235]: submission(alec)<25347><QNydV8+t+oMKAgAF>: Warning: smtp-client: conn localhost:25 ([::1]:25) [1]: Received invalid EHLO response line: Unexpected character in EHLO keyword Looks like it doesn't like the underscore in "X_PIPE_CONNECT", since it's neither "isalnum"

3. Januar 2018 00:49, "Stephan Bosch" <stephan at rename-it.nl> schrieb: > Op 1/2/2018 om 10:48 PM schreef Daniel Kenzelmann: > >> Hi, >> >> I'm not entirely sure whether this issue is with exim or with dovecot. >> >> First some background: >> I'm using exim with dovecot-auth which in turn is using LDAP for >>

On Thu, 2016-06-02 at 13:27 +0100, Mike Brudenell wrote: > My point is that a busy sysadmin shouldn't have to rely on intimate > knowledge of Exim's internal behaviour and oddities when trying > tracing a message from the logs. Some of us, well at least 1, have written a simple PHP programme, run on Apache, which instantly searches the current log and the archived logs for

On 28/08/2020 01:11, Alec Moskvin wrote: > Hello, > > When connecting to Exim 4.94, dovecot submission logs this warning: > > dovecot[25235]: submission(alec)<25347><QNydV8+t+oMKAgAF>: Warning: smtp-client: conn localhost:25 ([::1]:25) [1]: Received invalid EHLO response line: Unexpected character in EHLO keyword > > Looks like it doesn't like the underscore

The Dovecot wiki [1] doesn't list either Exim, Postfix or anything else as supporting the dbox. I did some searching in the Exim archives and have found only one message mentioning dbox, sdbox or mdbox. [2] I think an RFC would go a long way towards getting the format supported. Has Timo, or anyone else, considered submitting an RFC to the IETF? My question was how are we going to use it

Op 1/3/2018 om 10:58 AM schreef Stephan Bosch: > Op 1/3/2018 om 8:31 AM schreef Daniel Kenzelmann: >> 3. Januar 2018 00:49, "Stephan Bosch" <stephan at rename-it.nl> schrieb: >> >>> Op 1/2/2018 om 10:48 PM schreef Daniel Kenzelmann: >>> >>>> Hi, >>>> >>>> I'm not entirely sure whether this issue is with exim

Hi. I'm using SMTP auth with Exim authenticating against Dovecot's auth socket. My (excellent) SMTP test tool "swaks" (http://jetmore.org/john/code/#swaks) tries multiple auth mechanismus consecutively which leads to the following message in Dovecot's log file: Error: auth(default): BUG: Authentication client gave a PID 6738 of existing connection I'm not sure where to

Op 1/3/2018 om 8:31 AM schreef Daniel Kenzelmann: > 3. Januar 2018 00:49, "Stephan Bosch" <stephan at rename-it.nl> schrieb: > >> Op 1/2/2018 om 10:48 PM schreef Daniel Kenzelmann: >> >>> Hi, >>> >>> I'm not entirely sure whether this issue is with exim or with dovecot. >>> >>> First some background: >>>

I am using exim via dovecot_deliver to store messages in Maildir in my $HOME. I am using kmail to retrieve stuff. Unfortunately, something in my data crashes dovecot. I was using 1.0.rc14 from opensuse, but downloaded and installed 1.0.8 from the site. Here is the crash: Dec 5 18:05:09 h743107 dovecot: IMAP(kris): file mail-index-transaction.c: line 629 (mail_index_update_flags_range):

Hello all, attached patch makes possible to use dovecot as an authentication backend for Exim 4. Reasons beyond this patch are simple: exim's authenticators require use of plaintext passwords and NTLM code in exim is quite outdated and hairy. Patch generated against Exim 4.43, but should apply to earlier versions too. Patch adds new 'dovecot' authenticator, which can be used as such:

Hi, I'm not entirely sure whether this issue is with exim or with dovecot. First some background: I'm using exim with dovecot-auth which in turn is using LDAP for authentication. When using AUTH PLAIN with the optional initial response argument, everything is fine. However when using AUTH PLAIN without the optional response argument, instead of getting an empty challenge ("334

On Mon, 21 Dec 2009 13:44:42 +0100 Joan <aseques at gmail.com> wrote: > > > > You need to check user's quota on routing stage, not transport. > > > It'd be much better, because I would allow me to mix overquota and > no-overquota recipients. > But the problem in my case is that I am using some hashing to > distribute the users' mailboxes, dovecot

Hi, I'm trying to set up exim (4.83) as a submission server, and need to set up the dovecot authentication in exim. I'm having an issue with that (documented at <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756258>) The problem is that exim doesn't follow the handshake as described here: <http://wiki2.dovecot.org/Design/AuthProtocol>. The wiki page says that the

hi, i'm running dovecot branch_10 cvs on OSX 10.4.7 w/ exim 4.63. i'd like to use Dovecot's SASL as an auth backend to exim, instead of Cyrus-SASL. @ dovecot's sasl page: http://wiki.dovecot.org/Sasl i know there's a patch against exim 4.43: http://www.exim.org/eximwiki/AuthenticatedSmtpUsingDovecot that, purportedly, enables EXIM to use dovecot's SASL as an

Hello, I am looking for some advice. I am trying to force dovecot to run to the same log as exim does. In dovecot.conf I put the exim log path /var/log/exim/mainlog. I restarted dovecot and the process worked fine. However at midnight exim log file is rotated and since then dovecot stops logging to this log. In syslog.conf I put: mail.*