Displaying 14 results from an estimated 14 matches for "zehl".
2013 Aug 05
1
v2.2.5 released
...nding things to look into, but it's been too long since v2.2.4 so here are the fixes so far.
+ SSL: Added support for ECDH/ECDHE cipher suites (by David Hicks)
+ Added some missing man pages (by Pascal Volk)
+ quota-status: Added quota_status_toolarge setting (by Ulrich Zehl)
- director: Users near expiration could have been redirected to
different servers at the same time.
- pop3: Avoid assert-crash if client disconnects during LIST.
- mdbox: Corrupted index header still wasn't automatically fixed.
- dsync: Various fixes t...
2013 Aug 05
1
v2.2.5 released
...nding things to look into, but it's been too long since v2.2.4 so here are the fixes so far.
+ SSL: Added support for ECDH/ECDHE cipher suites (by David Hicks)
+ Added some missing man pages (by Pascal Volk)
+ quota-status: Added quota_status_toolarge setting (by Ulrich Zehl)
- director: Users near expiration could have been redirected to
different servers at the same time.
- pop3: Avoid assert-crash if client disconnects during LIST.
- mdbox: Corrupted index header still wasn't automatically fixed.
- dsync: Various fixes t...
2013 Aug 07
2
Override master service settigs with spaces
I'd like to override one setting for a master service in
conf.d/10-master.conf. Unfortunately, said setting contains spaces, and I
do not know how to escape them properly.
Here's what I've tried so far. (Note: This is just the easiest/silliest
test case I could come up with; not the actual setting or service I want to
overwrite.)
conf.d/10-master.conf:
service quota-status {
2009 Jan 20
2
Broken dovecot-uidlist files
I have just upgraded to 1.1.8, hoping to fix these types of errors:
Jan 20 10:39:27 laura deliver(xxxxxx at example.net): Broken file /srv/storage/mail/store/net/example/xx/xxxxxx/Maildir/dovecot-uidlist line 156: Invalid data:
Jan 20 10:41:19 laura dovecot: POP3(yy.yy at example.at): Broken file /srv/storage/mail/store/at/example/yy.yy/Maildir/dovecot-uidlist line 2: Invalid data:
2018 Apr 17
2
Postfix sendmail cannot be called from Sieve redirect
Sending (in my case: forwarding) messages from Sieve via sendmail does not
work with version 2.3.1.
I have narrowed it down to this simple test case:
# dovecot -n
# 2.3.1 (c5a5c0c82): /etc/dovecot/dovecot.conf
# OS: Linux 4.4.0-119-generic x86_64 Ubuntu 16.04.4 LTS
# Hostname: tuxi.topfen.net
first_valid_gid = 200
first_valid_uid = 200
mail_location = mbox:~/mail
passdb {
args =
2018 Apr 17
0
Postfix sendmail cannot be called from Sieve redirect
Am 17.04.2018 um 19:00 schrieb Ulrich Zehl:
> Sending (in my case: forwarding) messages from Sieve via sendmail does not
> work with version 2.3.1.
https://dovecot.org/pipermail/dovecot/2018-April/111482.html
[ ... ]
> Ulrich
Alexander
2008 Dec 09
1
Possible bug in Maildir++ quota?
While researching a possible bug in our custom-made Maildir++ expiration
script, I found the following in src/plugins/quota/quota-maildir.c.
| static const char *
| maildir_list_next(struct maildir_list_context *ctx, time_t *mtime_r)
| {
| [...]
| *mtime_r = st.st_size;
| return str_c(ctx->path);
| }
As far as I unterstand, this seems incorrect, because the value in mtime_r
is
2008 Jun 30
1
Multiple auth client sockets
I use two seperate Postfix instances as MSAs (so that different policies
are simpler to configure), and both of them require Dovecot SASL support.
Since Postfix' smtpd is chrooted (at least in the Debian package), the
client socket needs to be somewhere under the instance's queue_directory.
This means I need two different auth client socket paths.
When I simply specify two "client {
2013 Jan 12
1
[PATCH] LMTP: Permit user IDs containing recipient_delimiter
The Dovecot 2.1 LMTP server currently always strips the address extension
from a recipient address (if recipient_delimiter is set), meaning user IDs
cannot contain the recipient delimiter character, e.g. "user+foo" is not
supported.
This was surprising for me, as Postfix behaves differently in this regard:
It first looks up "user+foo", and only then "user".
The
2013 Aug 01
1
[PATCH] quota-status: allow different action for messages that are too large (over maximum quota)
This proposed patch to quota-status allows the administrator to return
different actions for messages that (a) cannot currently fit in the quota
(because there's not enough free space) and (b) are over the maximum quota
limit (and could not even be delivered if the mailbox was empty).
Configuration works like this:
plugin {
quota_status_overquota = DEFER_IF_PERMIT 4.2.2 Mailbox full
2005 Nov 22
1
[PATCH] Introducing Zero-Knowledge user authentication
...as identity files and in the authorized keys files. Currently,
the keygen cannot be used for changing the passphrase or other metadata in
the key file.
Please have a look at our patch and comment on it. We are interested in your
feedback.
Regards
Andreas Gaupmann
Christian Schausberger
Ulrich Zehl
[1] http://zk-ssh.cms.ac/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20051122/e8792bd5/attachment.bin
2009 Jan 14
2
Maildir++ quota: When is it recalculated?
We use Maildir++ quota, with the rules taken from our LDAP backend. We also
have an old expunge script that's not quota-aware; it removes old messages
from the maildir by simply deleting the files.
Sometimes, a mailbox is over quota before the script runs, but well under
quota after the old messages are deleted. This change does not seem to be
picked up, however: When I try to deliver a new
2013 Aug 01
0
[PATCH] quota-status: remove unnecessary newlines
Here's a trivial patch for quota-status.c that removes unecessary newlines
present in the default overquota message. It applies to 2.2 and 2.1.
Ulrich
--- a/src/plugins/quota/quota-status.c 2013-08-01 14:35:35.000000000 +0200
+++ b/src/plugins/quota/quota-status.c 2013-08-01 17:58:26.000000000 +0200
@@ -107,7 +107,7 @@
/* over quota */
value = mail_user_plugin_getenv(user,
2008 Apr 30
2
deliver: handling of quota_full_tempfail and -e
Hi,
while testing out dovecot 1.1, I found that when you set
quota_full_tempfail = yes in dovecot.conf and use the deliver -e command
line flag, no deferral reason is printed, thus breaking my fancy
quota_exceeded_message.
This appears to be because of the if() block in lines 1003-1009 in
src/deliver/deliver.c, and should be easily fixable (if it is indeed a bug,
and not intended behavior).