similar to: [RFC] FreeBSD port for dovecot 1.1 series

Displaying 20 results from an estimated 200 matches similar to: "[RFC] FreeBSD port for dovecot 1.1 series"

2011 Jun 08
4
On-delivery deduplication?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, A feature of Cyrus-IMAPd I really missed after migrated to Dovecot is their optional "duplicate suppression", which eliminates duplicate message at deliver time, if their envelope sender, recipient and message-id matches. For example, if one subscribes to a mailing list, and someone hit "Reply All" to reply to him, there
2015 May 16
4
charset_to_utf8 assertion of remaining src_size
On 16 May 2015, at 09:39, Xin Li <delphij at delphij.net> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Hi, > > On 5/15/15 10:58, Xin Li wrote: >> Hi, >> >> I have seen the following assertion fails on my own mail server >> (indexer-worker): >> >> Panic: file charset-iconv.c: line 132 (charset_to_utf8):
2015 May 22
1
charset_to_utf8 assertion of remaining src_size
On 05/22/15 13:18, Cassidy Larson wrote: > We're using FreeBSD 10.1 I see. Yes that's the same problem I have seen. There is a behavioral difference (I think it's a FreeBSD bug) between FreeBSD's iconv(3) and GNU implementation, and there is arguably a bug with Dovecot that iconv(3) state should be reset for each multipart part. The two together would trigger the problem
2015 May 15
2
charset_to_utf8 assertion of remaining src_size
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi, I have seen the following assertion fails on my own mail server (indexer-worker): Panic: file charset-iconv.c: line 132 (charset_to_utf8): assertion failed: (*src_size - pos <= CHARSET_MAX_PENDING_BUF_SIZE) However, when charset_to_utf8_try returns FALSE (e.g. iconv() got EINVAL or EILSEQ), the for loop in charset_to_utf8 may end earlier,
2005 Jul 03
2
bind() on 127.0.0.1 in jail: bound to the outside address?
Dear folks, It seems that doing bind() inside a jail (whose IP address is an outside address), will result in some wierd behavior, that the actual bind is done on the outside address. For example, binding to 127.0.0.1:6666 inside a jail addressed 192.168.1.1, will finally result in a bind to 192.168.1.1:6666. With this in mind, it is possible that some formerly secure configuration fail in jail
2007 Jul 25
3
dovecot-1.1 + dovecot-sieve-1.1 deliver backtraces
Hi, I am trying dovecot-1.1 with dovecot-sieve-1.1. First, dovecot -n do not report about deliver settings. They are: --- protocol lda { postmaster_address = postmaster at parkheights.dyndns.org hostname = parkheights.dyndns.org mail_plugins = cmusieve mail_plugin_dir = /usr/lib64/dovecot11/modules/lda sendmail_path = /usr/lib/sendmail auth_socket_path = /var/run/dovecot11/auth-master
2008 Dec 02
8
RELENG_7_1: bce driver change generating too much interrupts ?
Since last upgrade, I see much more CPU time "eated" by interrupts (at least 10% cpu in top) (see http://dgeo.perso.ec-marseille.fr/cpu-week.png) The server behave correctly (Or seems to?), and high interrupt number seems to come from bce cards (source: systat -vmstat) I just upgraded from "RELENG_7 Mon Sep 8 12:33:06 CEST 2008" to "RELENG_7_1 Sat Nov 29 16:20:35 CET
2004 Nov 10
2
Is there any way to know if userland is patched?
Dear folks, I'm recently investigating large scale deployment and upgrading FreeBSD RELEASE. It's our tradition to bump "RELEASE-pN" after a security patch is applied, however, it seems that there is less method to determine whether the userland is patched, which is somewhat important for large site managements. So is "uname -sr" the only way to differencate the
2004 Aug 10
3
[PATCH] Tighten /etc/crontab permissions
Hi folks, While investigating OpenBSD's cron implementation, I found that they set the systemwide crontab (a.k.a. /etc/crontab) to be readable by the superuser only. The attached patch will bring this to FreeBSD by moving crontab out from BIN1 group and install it along with master.passwd. This change should not affect the current cron(1) behavior. Cheers, -- Xin LI <delphij frontfree
2008 Jan 23
1
FreeBSD 6.3-Release + squid 2.6.17 = Hang process.
Hi: We have a machine running 6.2-R-p10 and squid 2.6.17, and upgrade it to 6.3R yesterday, but squid will hang and eat 100% cpu time after restart about 1 hour later, machine still alive, and no response from squid. downgrade to 6.2-R-p10, everything ok again.. here is some infomations: machine type: FreeBSD 6.3-RELEASE #0: Wed Jan 23 01:58:39 CST 2008 CPU: Intel(R) Xeon(TM) CPU 2.40GHz
2009 Sep 15
3
FreeBSD bug grants local root access (FreeBSD 6.x)
Hi, Any info on this subject on http://www.theregister.co.uk/2009/09/14/freebsd_security_bug/ -- Frederique
2013 Jul 24
4
[Bug 2129] New: [PATCH] sftp chroot regression
https://bugzilla.mindrot.org/show_bug.cgi?id=2129 Bug ID: 2129 Summary: [PATCH] sftp chroot regression Product: Portable OpenSSH Version: 6.2p1 Hardware: Other OS: FreeBSD Status: NEW Severity: normal Priority: P5 Component: sftp Assignee: unassigned-bugs at mindrot.org
2015 May 22
0
charset_to_utf8 assertion of remaining src_size
We're using FreeBSD 10.1 Thanks On Thu, May 21, 2015 at 4:56 PM, Xin Li <delphij at delphij.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On 05/21/15 15:47, Cassidy Larson wrote: > > I've been seeing this same error as well now: > > > > Fatal: master: service(indexer-worker): child 20979 killed with > > signal 6 (core not
2008 Dec 15
1
bce reporting fantom input errors?
Hi, After changing cables,switches,ports, I came to the conclusion that bce is reporting input errors that are not there, or creating them. I checked this with 3 different boxes, all Dell-2950/Broadcom NetXtreme II BCM5708 1000Base-T (B2), and one of them, while running Solaris, reported 0 errors after a week, and freebsd after a few minutes its count was > 100. The errors appear under
2008 Oct 08
3
Something weird happening...
Hi to all, I use Dovecot dovecot11-1.1.3-5.1 from OpenSuSE 11, when i send a mail from the logs i read: Oct 8 10:36:31 mail postfix/pipe[17934]: A360A851: to=<mediatest at atpss.net>, relay=dovecot, delay=0.22, delays=0.18/0/0/0.04, dsn=4.3.0, status=deferred (temporary failure. Command output: Can't open log file /var/log/dovecot-err.log: Permission denied ) But, log files seems ok:
2008 Apr 08
4
ZFS deadlock
Hello A box of mine running RELENG_7_0 and ZFS over a couple of disks (6 disks, 3 mirrors) seems to have gotten stuck. From Ctrl-T: load: 0.50 cmd: zsh 40188 [zfs:&buf_hash_table.ht_locks[i].ht_lock] 0.02u 0.04s 0% 3404k load: 0.43 cmd: zsh 40188 [zfs:&buf_hash_table.ht_locks[i].ht_lock] 0.02u 0.04s 0% 3404k load: 0.10 cmd: zsh 40188 [zfs:&buf_hash_table.ht_locks[i].ht_lock]
2009 Mar 31
1
Intel Integrated Raid (iir) relevance
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 (It would be probably good idea to redirect this discussion to -stable@, redirected) Hi, Danny, Danny Braniss wrote: > It's no longer working (for me) under 7.2, and so far > I am not getting any feedback, so since it seems that > this particular hardware has reached EOL, I was wondering > if, > a) it's true, > b) drop
2011 Jul 29
1
Using Dovecot with ZFS
Hi all, I'm testing Dovecot version 1.2.17 on FreeBSD 8.2-RELEASE using ZFS as filesystem. Searching on google I've ridden about some problem concerning indexes and mmap. I wold like to know if this problem persists on the latest releases. Thanks in advance. Roberto Giuliani.
2006 Jan 13
1
FreeBSD Errata Advisory FreeBSD-SA-06:03.cpio
Hi there, I'm following the security advisory to patch the cpio vulnerability (update to 6_0_0 RELENG p2, make obj, make depend), yet when it comes to make, it shows some error message as follows: /usr/src/gnu/usr.bin/cpio/../../../contrib/cpio/copyin.c:536: error: redefinition of 'safer_name_suffix' /usr/src/gnu/usr.bin/cpio/../../../contrib/cpio/copyin.c:488: error: previous
2004 May 02
1
What's our current policy on ports FORBIDDEN knob?
Greetings, I'm a little curious about the way FORBIDDEN knob is used in ports system. Traditionally, we use it to mark a port which have known security issue, with the new vuxml mechanism, are we still doing the same thing when necessary? Or, only the "critical" ones, for example, remote exploitable buffer overruns, etc? If the second assumption (only critical ones are marked