similar to: bug with rsh/ssh connections

Background: I'm new to dovecot (although with many years Washington IMAP behind me). We're considering migrating from Washington IMAP to dovecot on the main service here, and have just started trying dovecot, using RC7. Washington, IMAP has the usual(-ish) "/var/spool/mail" shared area for the INBOX (trad. UNIX "From " format); a user's folders default to being

Anyone had any thoughts on the item below? If the problem is with my config, I'd like to be guided towards how I might resolve it. If it is a bug in rc7, it would be good to fix it, and I'd be happy to beta-test. -- : David Lee I.T. Service : : Senior Systems Programmer Computer Centre : :

Timo: As discussed over the last couple of days. Please could the attached patch be applied to "deliver.c" so that it can log (syslog etc.) final delivery into the destination mailbox. This completes a hitherto missing part in logging an email's progress; it is useful (for example) to diagnose "my email wasn't delivered" problems. Thanks. -- : David Lee

(OS: Fedora Core 5; dovecot: 1.0 rc7) On a typical UNIX-like OS, the INBOXes are in "/var/spool/mail/" using the user identifier: so user 'fred' has INBOX "/var/spool/mail/fred". We have a well-established different convention which subdivides this, based on the last two digits of the uid: "/var/spool/mail/12/fred" (for fred's uid as something ending

Could someone confirm, please, that this bug report and its proposed fix are being checked? 1. Is my analysis (message below) about right? 2. Is my proposed patch (attached) about right? 3. Is this being addressed for "rc8" (or whatever) and its successors? Many thanks. -- : David Lee I.T. Service : : Senior Systems Programmer

Filed as a bug, as suggested by Brian R., Jonathan. Jonathan Rougier Science Laboratories Department of Mathematical Sciences South Road University of Durham Durham DH1 3LE tel: +44 (0)191 374 2361, fax: +44 (0)191 374 7388 http://www.maths.dur.ac.uk/stats/people/jcr/jcr.html ---------- Forwarded message ---------- Date: Wed, 11 Apr 2001 09:15:26 +0100

I'd need "04" including its leading "0". ("1200"->"00" etc.) > Depending on what other tools you use, you could also use the hash (H) > modifier, but maybe your delivery agent can't do that (unless of course > you plan to use dovecot-lda too) With our UW set-up, everything goes through UW's c-client library (sendmail local

valid incoming email. It is rare, but it does occasionally happen on large, busy systems. Clearly it is fundamentally an "nscd" bug. But that bug is nevertheless out there, in the wild, on such systems, potentially affecting dovecot's delivery of valid user email. We have had a source code hack since October (in "deliver.c", simply replacing a "return ret"

Does "dovecot" have anything similar to the UW IMAP "mailadm" group operation? From near the end of: http://www.washington.edu/imap/documentation/RELNOTES.html 'Support for SASL authentication identity vs. authorization identity in the IMAP and POP3 servers. If the user indicated by the authentication identity is in the "mailadm" group, he may

(Using dovecot 1.0 RC7 on Fedora Core 5) <scene set> Hitherto we have used UW-IMAP on a "farm" of Linux machines mounting NFS from a NetApp. (The UW-IMAP author doesn't like use of NFS, but with careful use of NFS mount arguments ('noac,actimeo=0' etc.) and trying to ensure that all activity for a given user takes place within one machine in the farm, we seem to

We do some routine logfile (syslog) gathering and analysis. I've been looking at extending this to parse the syslog output of dovecot. Hmmm... Ignoring the leading 'date hostname' prefix, some sample lines are: dovecot: imap-login: Login: user=<uuuuuu>, method=PLAIN, rip=dd.dd.dd.dd, lip=dd.dd.dd.dd dovecot: IMAP(uuuuuu): Disconnected: Logged out dovecot:

We have for many years been a UW-IMAP site, with users having their own traditional, private, mbox-format INBOX and folders: almost (but not quite) no complications of shared or simultaneous access. We have just completed a transparent transition to dovecot (official 1.0.0 release). But we have one residual issue affecting one important user account. UW-IMAP specifically only allows single

Picture: A set of very similar UN*X IMAP servers all NFS-mounting their INBOX area (traditional Unix format) from a common "/var/spool/mail" area; activity for any given user ought to be within one box although this cannot be 100% guaranteed. There is the risk of multiple simultaneous access (e.g. simultaneous LDA/delivers; simultaneous LDA/deliver and user-driven IMAP update; etc.).

Yesterday I gave a status report about 10.rc8 in production, which mentioned a problem about "Login process died too early..." Timo suggested a patch for logging error messages. I've applied this. Others suggested increasing "login_max_processes_count". That was already way above our likely maximum, but I've doubled it anyway. Today, I've just repeated the

Whilst debugging a problem in dovecot LDA over the last few days, I came across two different issues in coding techniques. (Note: Please don't take this negatively; my intent is both positive and constructive!) The front page of the website www.dovecot.org says: "it uses several coding techniques to avoid most of the common pitfalls" So I hope it is OK to follow the spirit of

(Complete newbie to dovecot. I hope what follows isn't something I've missed in some FAQ somewhere...) On a traditional UNIX filesystem with UW-IMAP several years ago, we encountered major performance problems when "/var/spool/mail/" got big (we would currently be ~20,000 entries). This was due to the inefficiency of the UNIX filesystem when creating and deleting the lockfiles

Hi Everyone, I have modified my version of R-1.4.1 to include choleski with pivoting (like in Splus). I thought R-core might consider including this in the next version of R, so I give below the steps required to facilitate this. 1. Copied Linpack routine "dchdc.f" into src/appl 2. Inserted line F77_SUBROUTINE(dchdc) in src/appl/ROUTINES 3. Inserted "dchdc.f" into

A quick status report on how 1.0rc8 behaved in service for a few hours with several hundred simultaneous users, at a site very new to dovecot. Oh, and a question at the end. Summary: Reasonable for a first shot but one significant problem, requiring backing off. Background: We have a long-established UW-IMAP service for a user population of about 20,000 based on a few Linux (Redhat) machines

I have just noticed that the last several versions of R that I have compiled all have the problem that functions which use regular expressions (gsub, sub and anything which depends on them) do not work. In particular, methods(print) either gives an error message or causes a segmentation fault. The problem is actually in gsub/sub which either return character(0) or cause a segmentation fault.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello I'm currently running dovecot-1.0.alpha4-1 on my production system, dovecot-1.0.alpha4-1where I am making use of namespaces. I have downloaded 1.0-beta3 and have installed it on a test system. I have customised the configuration for local use, however when I inserted the namespace settings into my configuration file dovecot refuses to