search for: yeagers

In running the various 1.0.n versions of Dovecot's LDA with the instructions in the wiki for using LDA with Postfix [on OS X 10.4] things went well using the instructions as-is (no setuid problems). This changed in moving over to the 1.1 beta. The LDA refused to work failing with the error "setgroups() failed: Operation not permitted" as I mentioned in a previous message.

On Jan 20, 2008, at 12:15 PM, dovecot-request at dovecot.org wrote: > > Message: 5 > Date: Sun, 20 Jan 2008 15:48:09 +0200 > From: Timo Sirainen <tss at iki.fi> > Subject: [Dovecot] v1.1.beta14 released > To: dovecot at dovecot.org > Message-ID: <1200836889.12450.99.camel at hurina> > Content-Type: text/plain; charset="us-ascii" > >

Some preamble information? OS X 10.4.10 (all updates) Power Mac Dual G5, 2.0 Postfix with Dovecot SASL, Dovecot LDA, Dovecot imaps (openssl) Mail clients Apple Mail v 2.1 SquirrelMail v 1.4.10a Thunderbird v 2.0.0.6 Mulberry v 4.06 For various versions of Dovecot, from 0.9m up through 1.0.3 things went well, no memorable big problems, with one exception: Mulberry v 4.0.8 would/will not

I've got Redhat 6.2 kernel 2.2.18 and have been running samba 2.07. When I try to configure samba 2.2.0, the configure bombs out with an error ERROR: No locking available. Running Samba would be unsafe with what I think relevant lines from the configure output are: checking for Linux kernel oplocks... no checking for fcntl locking... no Is there something I have to enable in the Kernel for

Hi list, I understand that dovecot's deliver does a little more than deliver: it also updates the dovecot metadata stored with each Maildir. Thus, if I use deliver as opposed to procmail's internal Maildir delivery, it seems that the IMAP server later has less work to do since the metadata is can use are up to date. Doing this, however, incurs an extra process for each mail delivered. I

So when I try starting up the Steam version of Borderlands, it says this... Code: fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported fixme:gameux:GameExplorerImpl_VerifyAccess (0x1cd930d0, L"c:\\program files\\steam\\steamapps\\common\\borderlands\\Binaries\\Borderlands.exe", 0x32d4ec) err:setupapi:do_file_copyW Unsupported style(s) 0x144

Is it possible to suspend this user from getting mail for a week otherwise we are going to get loads of "out of office" reports??????? Cheers -----Original Message----- From: brian.casey@mscsoftware.com [mailto:brian.casey@mscsoftware.com] Sent: 22 January 2003 13:34 To: samba@lists.samba.org Subject: [Samba] I am out of the office. I will be out of the office starting 01/21/2003

Perhaps I'm trying to do something that is not allowed, but I have found no such restriction in the documentation. To limit the contact of my Linux boxes with the "products of Bill & Co.", I have mounted a Windows share on my Linux server. When I try to export that same share from the Linux server (as a plain old NFS volume), it mounts without error, but the mountpoint

Anyone have experience with exporting to other Linux boxes a Windows share mounted on one Linux box? I have successfully mounted the Windows share on the Linux server box, but when I edit /etc/exports to include the new mount and run exportfs, I get error messages regarding the new export. For example, if I add this line to /etc/exports: /mnt/windows_share somebox(rw) I will get the

Christopher and the list: Gee... I wish it would! My probelm currently is the fact that if I add this line to /etc/exports: /mnt/MountedSambaShare somebox(nohide) I get: somebox:/mnt/MountesSambaShare: Invalid argument This happens whether /etc/exports says "somebox(nohide)" or "somebox(ro)" or "somebox()". Note that /mnt/MounteSambaShare is in fact

Everyone could setup an auto-responder to send replies to his E-mail address that contains instructions on how to properly setup his mail filters to skip the auto reply to this and any other mailing lists he is associated with. Perhaps when his company sees the incredible slow-down on their mail server and investigates the issue. They could unplug his machine from their network,

...start + 68 Dec 22 11:33:58 mac-g5 postfix/pipe[28415]: 251EE4D094C: to=<jerry at scene-naturally.dyndns.org >, relay=dovecot, delay=0.38, delays=0.02/0.04/0/0.32, dsn=5.3.0, status=bounced (Command died with signal 6: "/usr/local/libexec/ dovecot/deliver") Dec 22 11:33:58 jerry-yeagers-power-mac-g5 postfix/qmgr[67]: 251EE4D094C: removed Switching to using the Postfix deliver works and it seems everything else in the new beta 12, so far, is fine. Running on OS X 10.5.1 Jerry -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s...

(Yes, Really .... w/ gcc v4.2.1, like i said in the first place) > Actually, the 1.1 beta v9 builds just fine under Tiger (PPC and > PPC64) if you use the official Apple sanctioned gcc v 4.01 they ship > with both Tiger and Leopard. If you do download and use gcc 4.2.1 from > the GNU folks you might want to pass along the error / bug reports to > them instead of Apple, but I

On Dec 9, 2007, at 1:48 PM, dovecot-request at dovecot.org wrote: > > > Message: 7 > Date: Sun, 09 Dec 2007 20:29:49 +0200 > From: Timo Sirainen <tss at iki.fi> > Subject: [Dovecot] v1.1.beta11 released > To: dovecot at dovecot.org > Message-ID: <1197224989.922.405.camel at hurina> > Content-Type: text/plain; charset="us-ascii" > >

Deliver from latest 1.1 HG with sieve also from latest 1.1 HG is dying with an assertion failure when it delivers to my mailbox. Other mailboxes on the same system are unaffected, but I can read my mailbox fine through IMAP. Dovecot and sieve were compiled with -march=nocona -pipe -ggdb I've commented out my entire sieve script and the problem still occurs. file index-mail-headers.c: line

From the digest: On Aug 14, 2007, at 1:04 PM, dovecot-request at dovecot.org wrote: other messages cut out? > > > Message: 9 > Date: Tue, 14 Aug 2007 19:03:58 +0200 > From: martin f krafft <madduck at madduck.net> > Subject: Re: [Dovecot] use of deliver from procmail advisable? > To: dovecot at dovecot.org > Message-ID: <20070814170358.GA17390 at

Hello list, while fiddling around with the configuration so Dovecot's LDA "deliver" can be used by multiple users by means of Getmail (you can read about that in [1]) I always end up running into the error message posted in the subject line: Jan 15 00:00:02 HOSTNAME deliver(USERID): Can't connect to auth server at /usr/local/var/run/dovecot/auth-master: Permission denied

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Package: logcheck-database Version: 1.2.41 Severity: wishlist Tags: patch Hi, here is one line for the imp4 package and one (I don't have more) line from the log file. Same as with the horde3 file: I've tested it and CC this mail to the maintainer. by, Martin - -- Powered by Debian GNU / Linux -----BEGIN PGP SIGNATURE----- Version: GnuPG

Package: logcheck Version: 1.2.41 Severity: minor man (8) logcheck says: For hints on how to maintain rules, see README.logcheck-database.gz, but this file is not included in /usr/share/doc/logcheck. micah -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel:

http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta1.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta1.tar.gz.sig Alpha6 seemed to finally work quite well, so I think it's time for a feature freeze (except for dbox changes). I started a new wiki page to list incompatibilities between v1.0 and v1.1: http://wiki.dovecot.org/Upgrading/1.1 Fixes since alpha6: - deliver + maildir