Displaying 19 results from an estimated 19 matches for "medata".
2004 Feb 08
1
a newbie question.
Hi,
I'm a newbie.Sorry for my question.
I have RH9 & downloaded rpm of dovecot for RH9.
I installed it:
rpm -ivh nameOfthatrpm
& when i ran
#service dovecot start ,I recieved following lines:
Starting IMAP daemon (dovecot): Fatal: Can't use SSL
certificate /usr/share/ssl/certs/dovecot.pem: No such
file or directory
2004 Apr 19
2
Can't resolve address 127.0.0.1
Hi ,
I recently installed Fedora Core 1.
Installed postfix on it and that is running fine.
I am trying to get dovecot to run and I have changed only the following line
from the default dovecot.conf :
imap_listen = 127.0.0.1 since I'd like to install squirrelmail later on.
Now when I try to start dovecot I get "Starting Dovecot Imap: Fatal: Can't
resolve address
2004 Feb 10
4
UW-IMAP -> Dovecot : patch to remove nasty "internal messages" from UW-IMAP ?
Hello there,
We want to move from UW-IMAP to Dovecot (mbox format), works like a
charm, but UW-IMAP has that bloody habbit to make a stupid message in
all his mailbox files :
From MAILER-DAEMON Thu Apr 19 10:30:01 2001
Date: 19 Apr 2001 10:30:01 +0200
From: Mail System Internal Data <MAILER-DAEMON at mailhub2-vil.isdnet.net>
Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA
2004 Jan 24
0
Customflags problem?
...oes so upon exit.
I've reproduced it in 0.99.10-6 (fedora core 1) and 0.99.10.4-1 (fedora
devel) versions. I filed a Bugzilla report at bugzilla.redhat.com under
114230 (https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=114230).
-Rick
--
Rick Johnson, RHCE #807302311706007 - rjohnson at medata.com
Linux/Network Administrator - Medata, Inc. (from home)
PGP Public Key: https://mail.medata.com/pgp/rjohnson.asc
2004 Feb 12
1
dovecot-IMAP-SSL-StartUp
Hi everybody.
I downloaded RPM of dovecot for RH9.
& i installed it with "rpm -ivh ThatFILE.rpm"
then i ran "service dovecot start" & i receiving
following lines:
Starting IMAP daemon (dovecot): Fatal: Can't use SSL
certificate /usr/share/ssl/certs/dovecot.pem: No such
file or directory
[FAILED]
Then i go
2004 Feb 13
3
RE: Question on folders
I have read and read the dovecot docs on maildir folders and think that
this is what I want. However, the MUA programs that I use, SylpheedClaws,
Evolution, Mozilla seem to react differently to how I setup the folders.
Is there a good FAQ on this subject somewhere? I think that I want to
setup a virtual domain and am looking for documents.
Alex
2004 May 11
1
LDAP + passwd
Hello,
I'm in the process to choose between Courier and Dovecot.
I would like to know if it's possible to configure Dovecot in order to
use multiple user database (e.g. ldap+passwd) in order to have both
virtual user authenticated by LDAP and system user authenticated by
system password and with their own home directory.
Another question: at http://dovecot.org/doc/dovecot-example.conf
2004 Jun 28
1
Mailbox archiving
Hi all!
I have a strange problem with Dovecot - deleted messages never seem to get
deleted on the server! Deleted messages just seem to get a 'T' at the end of
them on the server and remain there, so user mail boxes continue to grow to
incredible sizes. Is this a setting I must change somewhere? Must I delete
these files manually?
Leslie
2004 Apr 08
1
(no subject)
Sorry if this question has been asked before I looked through some of the
archives before posting this.
I am considering using dovecot on a small 35 user enviorment (only around
6 gigs of email) that will be primarly be used with squirrelmail for the
MUA. I have been using dovecot for a few weeks now and really like it. It
is a big improvement over uw-imap thats for sure. I was wondering how many
2004 May 03
3
Maildir files in cur without info
Hi,
I have tried to use the same Maildir dovecot uses with
another program and encountered the problem that Dovecot
seems to move files from new to cur in
maildir-sync.c::maildir_scan_dir without adding an info
part. On the page http://cr.yp.to/proto/maildir.html is
written that mails have to be renamed to uniq:info when
moved to the cur directory.
Could this be a bug in dovecot?
--
2004 May 10
2
Is Dovecot ready for production use?
Hi!
I'm currently running RH 9 with postfix, uw-imap and MailScanner. I want to
install Fedora Core 2 (when it comes out next week) with postfix, dovecot
and amavisd. I'm unhappy with the problems I'm having with MailScanner,
with the difficulty I've had with authentication as I am currently
configured, and want to move to Maildir instead of mbox.
That being said, is dovecot
2004 Jan 29
2
SpamAssassin
--On Thursday, January 29, 2004 11:16 PM +0200 Timo Sirainen <tss at iki.fi>
wrote:
> I don't yet really even want Dovecot to be too well known, it's not
> ready yet. When 1.0 comes (this spring I hope) I'll start publicizing it
> more. After that I should only need to add new features - existing ones
> should be perfect and better than anyone else's ;)
Just a
2004 Jan 30
2
Dovecot dies on startup????
Trying to crank it up on our RedHat 8.0 system... I get the following..
I am sure it is something simple in the config.. just don't know what...
Any help would be greatly appreciated..
Here is from the log.. If there is a way to get more log info that might
help he as well..
Jan 29 14:30:34 smtp dovecot: Dovecot starting up
Jan 29 14:30:34 smtp dovecot: dovecot startup succeeded
Jan 29
2004 Feb 17
3
More Benchmarks, and a question about indexing
Hi,
We are thinking of converting to Dovecot to lighten our I/O load. I have done
some performace tests comparing UW-IMAP to Dovecot when using mbox format if
anyone is interested. They primarily examine the I/O improvements that can be
gained from using Dovecot over UW when staying with mbox format:
http://whizzo.uoregon.edu/public/src/mailperf/results.html
I had too much cached for this set
2013 Jan 16
0
[LLVMdev] RFC: auto-linking IR proposal
....
One can either add another module flag for "Named Libraries" in addition to
"Linker Options", which might be easier to implement. Or one can provide a
target-specific hook to the frontend, which converts #pragma comment(lib,
"blah.lib") to something like this:
!0 = medata !{ i32 6, "Linker Options",
metadata !{
!metadata { metadata !"/DEFAULTLIB:blah.lib" }
}
}
!llvm.module.flags = !{ !0 }
Your example is maybe more complicated where you need to convert libz to "-lz".
Regarding the ordering information of the libraries, I thin...
2017 Apr 03
4
Dereferenceable load semantics & LICM
2017-04-01 15:59 GMT+02:00 Piotr Padlewski <piotr.padlewski at gmail.com>:
>
>
> 2017-03-31 23:20 GMT+02:00 Sanjoy Das <sanjoy at playingwithpointers.com>:
>
>> Hi Piotr,
>>
>> On March 31, 2017 at 1:07:12 PM, Piotr Padlewski
>> (piotr.padlewski at gmail.com) wrote:
>> > [snip]
>> > Do I understand it correctly, that it is legal to
2009 Dec 28
0
[storage-discuss] high read iops - more memory for arc?
...data
> only once -
> so read cache is not of much use (except if it is a magic
> one,
> pre-reading guessed future-request addresses).
>
> So my idea would be to disbale the device read-ahead for
> the Oracle
> ZVOLS / folders by setting "primarycache" to "medata" and
> thus using the
> pressious main memory for metadata only (ZFS does a lot of
> metadata
> operastions, so having this in memory helps). If this does
> not help,
> secondarycache to "metadata" may be a good idea also.
>
> Maybe this helps,
> Robert...
2013 Jan 16
2
[LLVMdev] RFC: auto-linking IR proposal
...e frontend, which converts #pragma comment(lib,
> "blah.lib") to something like this:
>
I would vote that we have a target hook that lets us emit the code into the
"Linker Options" metadata, which would also be our handling of #pragma
comment(linker, ...)
>
> !0 = medata !{ i32 6, "Linker Options",
> metadata !{
> !metadata { metadata !"/DEFAULTLIB:blah.lib" }
> }
> }
> !llvm.module.flags = !{ !0 }
>
> Your example is maybe more complicated where you need to convert libz to
> "-lz".
>
> Regarding t...
2013 Jan 15
4
[LLVMdev] RFC: auto-linking IR proposal
Hi all,
We plan to add some auto-linking support for Mach-O, and need a scheme for
encoding this information in the LLVM IR. We would like the same scheme to
be able to support Microsoft's #pragma comment(lib,...) and #pragma
comment(library, ...) features eventually.
The current proposal is as follows:
--
#1. Extend module-level metadata flags (llvm.module.flags) to support two
new