, reliability, etc.) and therefore are stuck
RAhaving to use NFS whether they like it or not.
To an extent, but keep in mind that the maildir/nfs solution is _simple_.
Now, you can do things to make it more "robust" (read: complex) to add
functionality, but if you want "simple and scalable&qu
On Tue, Jan 18, 2000 at 03:26:49PM -, Anthony DeBoer wrote:
Bruce Guenter [EMAIL PROTECTED] writes:
The needs I am aware of include:
- hierarchical multiple mailbox support
That should include something that makes sense for a host that's behind a
firewall and/or NAT and/or dynamic-IP
On Sat, Jan 15, 2000 at 12:25:09PM -0500, Greg Owen wrote:
1) Integrate support for some sort of calendaring. I've run both IMAP and
Exchange based environments, and for all its faults, the integrated
calendaring that Exchange does is extremely useful. None of the web-based
calendaring
On Sun, Jan 16, 2000 at 10:35:09AM -0600, Tim Tsai wrote:
What do you guys do for backup's? Do you put two NIC cards in each
server and maintain a separate network for that?
We actually use a couple Storagetek 9710 tape libraries. 10 DLT 7000 drives
and something like 800 slots for tapes.
Warning: opinions, little to do with qmail or maildir.
Bruce Guenter wrote:
On Sat, Jan 15, 2000 at 12:25:09PM -0500, Greg Owen wrote:
1) Integrate support for some sort of calendaring. I've
run both IMAP and Exchange based environments, and for all
its faults, the integrated
On Wed, Jan 19, 2000 at 01:22:11PM -0500, Greg Owen wrote:
Warning: opinions, little to do with qmail or maildir.
Indeed. I should start up a list just to discuss this.
As much as I would like scheduling, this is an "mailbox"
program, which handles email. I believe t
On Wed, Jan 19, 2000 at 12:36:05PM -0600, Bruce Guenter wrote:
A good calendaring system requires that users receive requests for
meetings and can answer them, and have trouble screwing them up (i.e.
putting the metainfo in the subject line is easy to screw up). Email is the
ideal
Bruce Guenter [EMAIL PROTECTED] writes:
On Tue, Jan 18, 2000 at 03:26:49PM -, Anthony DeBoer wrote:
[ protocol wishlist ]
That should include something that makes sense for a host that's behind a
firewall and/or NAT and/or dynamic-IP dialup to authenticate and download
mail for
On Wed, Jan 19, 2000 at 01:22:11PM -0500, Greg Owen wrote:
Warning: opinions, little to do with qmail or maildir.
Indeed. I should start up a list just to discuss this.
Bruce,
If you start up such a list, let me know.
You are asking good questions, questions
On Wed, Jan 19, 2000 at 10:53:09AM -0600, Bruce Guenter wrote:
Do you have an URL for a specification of ACAP or IMSP? I've never
heard of them, but what you've described is a good idea.
Actually, the ACAP chapter of O'Reillys "Programming Internet Email" (ISBN
1-56592-479-7) is free!
A few people have responded to my earlier query/rant/whatever about
writing high-quality software. A couple of these have asked me to
keep them notified about what I learn, if possible. Another identified
the starting-point of a resource.
I put up a web page on my site on this topic, which I
There is a new GNU project starting up called GLUE that seems to be concerned
with at least some of the same things you are (plus other stuff). You
can start looking at their goals at:
http://www.gnu.org/software/glue/glue.html
On Wed, Jan 19, 2000 at 12:46:16PM -0600,
Bruce Guenter [EMAIL
On Wed, Jan 19, 2000 at 03:31:57PM -0500, Greg Owen wrote:
Indeed. I should start up a list just to discuss this.
If you start up such a list, let me know.
I have started up two lists, actually:
[EMAIL PROTECTED]
[EMAIL PROTECTED]
The first is to discuss an
On Tue, Jan 18, 2000 at 12:11:16AM -0600, Bruce Guenter wrote:
On Tue, Jan 18, 2000 at 12:53:37AM -0500, Russell Nelson wrote:
Um, am I missing something? I thought the whole point of the "info"
portion of the filename of the message in the maildir?
Right, and do you want th
On Fri, Jan 14, 2000 at 03:07:09PM -0500, Russell Nelson wrote:
Right, and any scalable email system is going to use NFS. Therefore
No. We scale with pop-proxies, and do without NFS at all. We rely heavily on
LDAP to achieve this.
Regards,
bert.
--
+---+ |
Bruce Guenter [EMAIL PROTECTED] writes:
The needs I am aware of include:
- the basics of POP3 plus...
[snip]
- hierarchical multiple mailbox support
That should include something that makes sense for a host that's behind a
firewall and/or NAT and/or dynamic-IP dialup to authenticate and
On Fri, 14 Jan 2000, Russell Nelson wrote:
One way to do that would be for Dan to change the
Maildir specification so that a Maildir may have multiple "cur"
directories. Then, keep a CDB containing a subset of the message
headers.
Why multiple "cur" direct
Jeff Hayward writes:
On Fri, 14 Jan 2000, Russell Nelson wrote:
One way to do that would be for Dan to change the
Maildir specification so that a Maildir may have multiple "cur"
directories. Then, keep a CDB containing a subset of the message
headers.
Why mul
ion boxes. Failover is just a special case
of load balancing. Scales well for us (about 6.5 million messages stored
in maildirs) with no limits on the horizon.
That said, maildir indexing would help latency in application response
quite a bit.
Oh, we've also been down the AFS path. Not rec
Try /etc/skel ...
The name says it all...
Good Luck
JP
On Fri, 14 Jan 2000, Kevin Waterson wrote:
In the qmail/doc/INSTALL.maildir it says to edit /var/qmail/rc
and replace ./Mailbox with ./Maildir/
and "by creating a maildir in the new-user template directory"
Where is this
up. Load balancing happens automatically, not by
adding/moving users to application boxes. Failover is just a special case
of load balancing. Scales well for us (about 6.5 million messages stored
in maildirs) with no limits on the horizon.
That said, maildir indexing would help latency in
On Tue, Jan 18, 2000 at 10:15:31AM -0600, Jeff Hayward wrote:
On Fri, 14 Jan 2000, Russell Nelson wrote:
One way to do that would be for Dan to change the
Maildir specification so that a Maildir may have multiple "cur"
directories. Then, keep a CDB containing a subset of t
On Tue, Jan 18, 2000 at 06:41:23PM +0100, [EMAIL PROTECTED] wrote:
Well the CDB (in my idea, at least) will be indexed to the unchanging part
of a message filename (without new/ or cur/ in front), and contain the headers
that mutt normally reads from the file itself while opening. [Yes, I am
Jose Pedro Pereira wrote:
Try /etc/skel ...
The name says it all...
hmm, there is nothing in this dir?
What should be there?
Could I be missing something?
Kind regards
Kevin
* Kevin Waterson ([EMAIL PROTECTED]) [18 Jan 2000 15:40]:
Try /etc/skel ...
The name says it all...
hmm, there is nothing in this dir?
What should be there?
Could I be missing something?
If you put a Maildir in this area, then every new account
will be automatically set up with one
On 19-Jan-2000, Kevin Waterson wrote:
Jose Pedro Pereira wrote:
Try /etc/skel ...
The name says it all...
It says nothing to me at first, until I read 'man useradd'.
skel stands for skeleton, I guess.
hmm, there is nothing in this dir?
What should be there?
Could I be missing
Bruce Guenter writes:
On Sat, Jan 15, 2000 at 10:57:00PM -0500, Russell Nelson wrote:
I wonder if that couldn't be handled by the Maildir code writing
Status: XXX as the very first line in each message?
Um, am I missing something? I thought the whole point of the "
On Tue, Jan 18, 2000 at 12:53:37AM -0500, Russell Nelson wrote:
Um, am I missing something? I thought the whole point of the "info"
portion of the filename of the message in the maildir?
Right, and do you want the filename changing all the time? Instead of
a simple "op
On Sat, Jan 15, 2000 at 09:41:48AM -0600, Tim Tsai wrote:
Russ, what is your definition of a "large" installation? 10k, 100k, 1m
users? Just exactly how many lighter-weight servers is practical to
manage and upkeep before it's cheaper to buy NetApp's?
As someone who has purchased and
Bruce Guenter [EMAIL PROTECTED] schrieb/wrote:
First place to start is to figure out what is actually necessary. In a
lot of cases, POP3 with a few extensions should be perfectly adequate,
but it is necessary to know what the needs actually are.
I don't think it's a good idea to overload the
What do you guys do for backup's? Do you put two NIC cards in each
server and maintain a separate network for that?
Thanks, from a guy that's about to take that big plunge into a scalable
mail design.
Tim
On Sun, Jan 16, 2000 at 02:56:59AM -0800, Tracy R Reed wrote:
On Sat, Jan 15,
What do you guys do for backup's? Do you put two NIC cards in each
server and maintain a separate network for that?
Do you have *a lot* of pc-hardware around? What failed, last time? And
before that?
No, that wasn't why I asked. The main reason for two NIC's is to keep
the backup
On Sat, 15 Jan 2000, Bruce Guenter wrote:
On Sat, Jan 15, 2000 at 01:20:05AM -0500, Russell Nelson wrote:
What about asynchronous commands and
notifications? I'd nuke 'em, myself.
Which of course begs the question about what kinds of events are really
necessary for a mailbox access
Greetings.
Does anybody have any experience with using the Coda distributed
filesystem with maildir file storage?
I am in a situation where we want to have a pair of mail servers such
that if any one dies, the other can take its place, complete with its
contents. Distributing mail to two
We decided against NetApp for the same reasons, and went with Metastor. Performance
is great, easy to upgrade, and it fit our needs for a reasonable price vs using
seperate file stores for each mail server. I'm sure there are other brands out
there of similar price/performance (we spent maybe 15k
Ruben van der Leij [EMAIL PROTECTED] writes:
On Sun, Jan 16, 2000 at 10:35:09AM -0600, Tim Tsai wrote:
What do you guys do for backup's? Do you put two NIC cards in each
server and maintain a separate network for that?
We just back up over the same network as we do everything else, early in
Bruce Guenter [EMAIL PROTECTED] writes:
I am in a situation where we want to have a pair of mail servers such
that if any one dies, the other can take its place, complete with its
contents. Distributing mail to two servers simultaneously is not a big
deal, but ensuring that those two
On Sun, Jan 16, 2000 at 02:09:00PM +0100, Claus Färber wrote:
Bruce Guenter [EMAIL PROTECTED] schrieb/wrote:
First place to start is to figure out what is actually necessary. In a
lot of cases, POP3 with a few extensions should be perfectly adequate,
but it is necessary to know what the
On Sun, Jan 16, 2000 at 05:47:50PM +, [EMAIL PROTECTED] wrote:
And even if you didn't mind doing that, then
events of interest could be reported using a prompt which conveyed the
same information as "You have a pending event". So you'd either be
executing a command, or else you'd
Bruce Guenter writes:
- message state storage (read, replied to, forwarded, flagged, etc.)
seperate from content delivery (a "Status:" header line)
I wonder if that couldn't be handled by the Maildir code writing
Status: XXX as the very first line in each message? Then,
On Sat, Jan 15, 2000 at 10:57:00PM -0500, Russell Nelson wrote:
I wonder if that couldn't be handled by the Maildir code writing
Status: XXX as the very first line in each message? Then, you
could change the status by opening the message file, read in the first
N bytes, modify one
On Sat, Jan 15, 2000 at 10:57:00PM -0500, Russell Nelson wrote:
Bruce Guenter writes:
- message state storage (read, replied to, forwarded, flagged, etc.)
seperate from content delivery (a "Status:" header line)
I wonder if that couldn't be handled by the Maildir code writi
eader line)
I wonder if that couldn't be handled by the Maildir code writing
Status: XXX as the very first line in each message? Then, you
could change the status by opening the message file, read in the first
N bytes, modify one of those characters to set the status, and write
out those b
On Sun, Jan 16, 2000 at 12:09:13AM -0600, Bruce Guenter wrote:
Good thought, especially with the tunneling options, but unless things
have changed, SSH still requires shell access -- something that should
not be required for mailbox access.
Not really. It only spawns a shell because sshd's
On Sat, Jan 15, 2000 at 10:26:22PM -0800, Peter C. Norton wrote:
Good thought, especially with the tunneling options, but unless things
have changed, SSH still requires shell access -- something that should
not be required for mailbox access.
Not really. It only spawns a shell because
On Fri, Jan 14, 2000 at 05:54:51PM +1100, Kevin Waterson wrote:
In the qmail/doc/INSTALL.maildir it says to edit /var/qmail/rc
and replace ./Mailbox with ./Maildir/
and "by creating a maildir in the new-user template directory"
Where is this directory?
It's usually /usr/share/sk
On Fri, Jan 14, 2000 at 05:54:51PM +1100, Kevin Waterson wrote:
I noticed something weird in your headers:
Received: (qmail 7501 invoked by uid 1002); 14 Jan 2000 07:47:54 -
Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
Precedence: bulk
Delivered-To: mailing list [EMAIL
Anand Buddhdev writes:
Received: from unknown (HELO oceania.net) (@203.41.132.67)
Normally, qmail-smtpd records the IP address of the client in that
field. Why does yours have an '@' in it?
They probably have an ident
On Fri, Jan 14, 2000 at 08:27:12AM -0500, Russell Nelson wrote:
Received: from unknown (HELO oceania.net) (@203.41.132.67)
Normally, qmail-smtpd records the IP address of the client in that
field. Why does yours have an '@' in it?
They probably have an ident server which returns
In the qmail/doc/INSTALL.maildir it says to edit /var/qmail/rc
Apparently, you did not believe me when in an earlier message I told
you that /var/qmail/rc is *not* used by the qmail-run scripts. Please
take a look at
ftp://moni.msci.memphis.edu/pub/qmail-run/README.qmail-run
You will see,
[EMAIL PROTECTED] wrote:
From libc-client4.7 documentation:
--strip--
The Maildir format used by qmail has all of the performance
disadvantages of mh noted above, with the additional problem that the
files are renamed in order to change their status so you end up
having to rescan
Ondrej Surý [EMAIL PROTECTED] wrote on Fri, 14 Jan 2000:
From libc-client4.7 documentation:
--strip--
The Maildir format used by qmail has all of the performance
disadvantages of mh noted above, with the additional problem
snip
Could someone comment this?
Well, I can say something
On Wed, 12 Jan 2000, Kristina wrote:
[...]
Do I need a .qmail file to configure the maildir format. If so, how do I
configure it. Please let me know.
Yes. Just tell qmail where to put incoming mail's (echo "./Maildir/"
.qmail).
Anyway, to create Maildir/new, Maildir/cur, Maildir
From libc-client4.7 documentation:
--strip--
The Maildir format used by qmail has all of the performance
disadvantages of mh noted above, with the additional problem that
the
files are renamed in order to change their status so you end up
having
to rescan the directory frequently the current
=?iso-8859-2?Q?Ond=F8ej=20Sur=FD?= writes:
Could someone comment this?
Yeah. Mark Crispin doesn't like Dan Bernstein; therefore anything Dan
Bernstein does has technical problems which "don't scale" and are "a
support nightmare." Mark doesn't want to hear what I have to say
about IMAP
Mikko Hänninen writes:
But, the commentary completely misses the good points and the purpose
of Maildirs: that they're ideal for incoming mail delivery, especially
when the folder is accesses over NFS (whether "access" delivery or
reading or both). Maildir format is not som
way to do that would be for Dan to change the
Maildir specification so that a Maildir may have multiple "cur"
directories. Then, keep a CDB containing a subset of the message
headers.
Doesn't the CDB file then require some trickery to avoid the necessity of
locks for multiple wri
Anand Buddhdev wrote:
On Fri, Jan 14, 2000 at 05:54:51PM +1100, Kevin Waterson wrote:
I noticed something weird in your headers:
--
See complete headers for more infl
I am moving our mail behind a firewall and our local network.
The IP of the machine I am sending from is 192.168.0.9
the
tead "What must be done to make Maildirs
more efficient"? One way to do that would be for Dan to change the
Maildir specification so that a Maildir may have multiple "cur"
directories. Then, keep a CDB containing a subset of the message
headers.
Doesn't the CDB f
Mate Wierdl wrote:
This is so important that I repeat it: if you want to change where
and how qmail delivers local mail, you need to change
/var/qmail/defaultdelivery/rc, and not /var/qmail/rc. In this
respect, qmail-run's setup is different from the default; the
scripts in
aildirs
more efficient"? One way to do that would be for Dan to change the
Maildir specification so that a Maildir may have multiple "cur"
directories. Then, keep a CDB containing a subset of the message
headers.
Doesn't the CDB file then require some trickery to
[EMAIL PROTECTED] writes:
Note that I don't really see the benefit in multiple cur-directories, apart
from the performance advantages on sub-optimal [most] filesystems, for which
same reason the queue directories are split up.
Right, me neither.
| 'C makes it easy to shoot yourself in
Russ Allbery writes:
Russell Nelson [EMAIL PROTECTED] writes:
Right, and any scalable email system is going to use NFS.
Why do you think that?
Because every such installation I've ever seen has used NFS. I'm not
talking about what's good, or what's right. I'm talking about what's
On Fri, 14 Jan 2000, Ondøej Surý wrote:
From libc-client4.7 documentation:
--strip--
The Maildir format used by qmail has all of the performance
disadvantages of mh noted above, with the additional problem that
the
files are renamed in order to change their status so you end up
On Fri, 14 Jan 2000, Russell Nelson wrote:
=?iso-8859-2?Q?Ond=F8ej=20Sur=FD?= writes:
Could someone comment this?
Yeah. Mark Crispin doesn't like Dan Bernstein; therefore anything Dan
Bernstein does has technical problems which "don't scale" and are "a
support nightmare." Mark
reading or both). Maildir format is not something you should be using
for email archival, or for very large mail folders. However, the lack
of locking requirement is a big win over NFS.
Right, and any scalable email system is going to use NFS. Therefore
the question in my mind is
Hi,
I'm facing an installation of FirstClass in our company, and while I've
been told that FC has an excellent mail service, I'd still like to use
our current qmail-server for recieving mail which FirstClass can then
retrieve from the mail server (perhaps through pop3.)
I don't know much about
Hi Henrik,
Haven't heard of FirstClass. I'm going to presume that the client
machines (Windows? Mac? Does it matter?) run some sort of proprietary
FirstClass client software to talk to the serveras such, your qmail
machine is likely to be working only as an MX host, and/or outgoing mail
In the qmail/doc/INSTALL.maildir it says to edit /var/qmail/rc
and replace ./Mailbox with ./Maildir/
and "by creating a maildir in the new-user template directory"
Where is this directory?
Kind regards
Kevin
Life-with-qmail talks says that the Maildir format has less
MUA support. Which MUA's are not compatible with the
Maildir format?
Thankyou,
Kristina
The question you should ask is which MUA isnt supported :)
The popular ones are :
Pine is supported via patches
Elm is supported via looping formats
Mutt has native support
Mew has native support
--Stephen
On Wed, 12 Jan 2000, Kristina wrote:
Life-with-qmail talks says that the Maildir
But if you're using POP3, you just need to use qmail-pop3d to
interface with Maildir and you can use any MUA and access your
e-mail thru POP3.
On Wed, Jan 12, 2000 at 10:18:59PM +1100, Stephen Mills wrote:
The question you should ask is which MUA isnt supported :)
The popular ones
Sorry, forgot to mention that (!)
--Stephen
On Wed, 12 Jan 2000, Benjamin de los Angeles Jr . wrote:
But if you're using POP3, you just need to use qmail-pop3d to
interface with Maildir and you can use any MUA and access your
e-mail thru POP3.
Kristina [EMAIL PROTECTED] wrote:
Which MUA's are not compatible with the Maildir format?
Stephen Mills mentioned pine, elm, mutt and mew. He missed pgnus, and
maybe other MUAs.
But "MUA support of Maildir" can mean two things. It can mean that the
mailer allows _folders_ to b
Kristina [EMAIL PROTECTED] wrote:
Do I need a .qmail file to configure the maildir format.
No. If you make "./Maildir/" the default delivery instruction, then
it will work even if nobody has a .qmail file.
BUT! qmail can _deliver to_ a maildir. It can't _create_ a maildir.
For exis
On the qmail list [EMAIL PROTECTED] wrote:
On the other hand, I have thought maildir a _good_ folder format; it
It is deathly slow on big folders. When you want to get the
subject of all the mails, for example, it still has to open and
read every single mail. I think a seperate index file
On Wed, Jan 12, 2000 at 12:38:55PM -, Lorens Kockum wrote:
On the qmail list [EMAIL PROTECTED] wrote:
On the other hand, I have thought maildir a _good_ folder format; it
It is deathly slow on big folders. When you want to get the
subject of all the mails, for example, it still has
[EMAIL PROTECTED] wrote:
On Wed, Jan 12, 2000 at 12:38:55PM -, Lorens Kockum wrote:
On the qmail list [EMAIL PROTECTED] wrote:
On the other hand, I have thought maildir a _good_ folder format; it
It is deathly slow on big folders.
True. Then again, many mbox clients are also
Len Budney writes:
FWIW, Dan once argued that maildirs are good as spools, but not great as
folders.
What if you want mail to be deliverable into folders, using extensions?
--
-russ nelson [EMAIL PROTECTED] http://russnelson.com
Crynwr sells support for free software | PGPok | "Ask not
Russell Nelson [EMAIL PROTECTED] wrote:
Len Budney writes:
FWIW, Dan once argued that maildirs are good as spools, but not great as
folders.
Misquote alert! My fault! Dan didn't say that maildirs are "not great
as folders". I don't have the exact quote, but what he said was th
On Wed, 12 Jan 2000 [EMAIL PROTECTED] wrote:
read every single mail. I think a seperate index file would be
a good idea, shouldn't be too hard to do correctly.
That would require locking, which goes against the Maildir-philosophy.
No locking required. Think of the index file
On Wed, Jan 12, 2000 at 06:27:59PM -0500, Sam wrote:
On 12 Jan 2000, (Lorens Kockum) wrote:
On the qmail list [EMAIL PROTECTED] wrote:
On the other hand, I have thought maildir a _good_ folder format; it
It is deathly slow on big folders. When you want to get the
subject of all
"s" == Sam [EMAIL PROTECTED] writes:
s On Wed, 12 Jan 2000, Len Budney wrote:
For asynchrony, maildir rules the world. But uses space and inodes,
and scans slowly.
s Perhaps that's true on some some platform that uses a substandard
s filesystem. The default allocation of the
I thought that configuring the /var/qmail/control/defaultdelivery file
and /var/qmail/rc files was all you needed for the maildir format.
However, as I was not getting tmp, cur and new directories created
I rechecked the Life with Qmail documentation again to find out that
I may need the .qmail
On 0, Sam [EMAIL PROTECTED] wrote:
On Tue, 21 Dec 1999, Subba Rao wrote:
I am in the process of moving my mail from a OS/2 box. The mail client
here is PMMail. Each email is stored in a seperate file, like in Maildir.
I have moved these files to linux, but cannot read them using Mutt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22 Dec 99, at 5:46, Frederik Lindberg wrote:
They are just the message, but in dos/CRLF format. There are several ways
to convert them. The easiest if to ftp from the OS/2 box to the unix box
into the ~Maildir/new/ folder using "ascii&
he easiest if to ftp from the OS/2 box to the unix
box
into the ~Maildir/new/ folder using "ascii" mode.
Huh? FTP the easiest? On my PC, the easiest was
tr -d "\r" input output
Putting it into a for... cycle is left to the reader as an excercise.
Exactly this is why
I am in the process of moving my mail from a OS/2 box. The mail client
here is PMMail. Each email is stored in a seperate file, like in Maildir.
I have moved these files to linux, but cannot read them using Mutt to
convert them to Maildir named files. The PMMail files are named in 7.3 format
text
How do you convert these files into mbox or Maildir format? I want to be able
to read these messages using Mutt MUA.
Well, if you're using qmail as your MTA, something like the following should
be a quick 'n' dirty way to do it. Just set the two addresses in the
script below to both be your
On Tue, Dec 21, 1999 at 09:09:11AM -0500, Subba Rao wrote:
I am in the process of moving my mail from a OS/2 box. The mail client
here is PMMail. Each email is stored in a seperate file, like in Maildir.
I have moved these files to linux, but cannot read them using Mutt to
convert them
On Thu, 16 Dec 1999, Sam wrote:
Casual browse of CPAN does not reveal any existence of maildir Perl
modules. Has anyone heard of anything like that?
I found this link on www.qmail.org, its a perl module to deliver to
Maildirs.
ftp://triceratops.com/pub/software/john/Qmail-Maildir-0.31
Once upon a time Sam shaped the electrons to say...
Casual browse of CPAN does not reveal any existence of maildir Perl
modules. Has anyone heard of anything like that?
Yes, a maildir interface exists in the Mail::Folder modules.
-D
--
The revolution will be documented.
hi all!
i've got troubles and a question :)
i can't manage to install procmail. currently i am using qmail-local to
deliver mails. i also use the /Maildir format and vpopmail. i couldn't find
a howto or documentation how to install procmail with
qmail+maildir+vpopmail. hope you can help me!
thx
-lists/qmail/1998/04/msg00487.html.
Also, procmail doesn't deliver directly to maildir-format
mailboxes. There's a patch available that implements maildir delivery
in procmail. (See http://www.qmail.org/top.html#maildir) Another
approach is safecat, a program that writes a message on standard input
to
On 12-Dec-1999, J. Ivan Juanes Prieto wrote:
Also, procmail doesn't deliver directly to maildir-format
mailboxes.
Maildir delivery is built-in since procmail 3.14 (released recently).
--
Ronny Haryanto
On Sun, 12 Dec 1999, J. Ivan Juanes Prieto wrote:
Also, procmail doesn't deliver directly to maildir-format
mailboxes. There's a patch available that implements maildir delivery
in procmail.
Procmail 3.14 can allegedly deliver to maildirs. The code, however, is
completely unreadable, just
I like to migrate from sendmail to qmail
and in qmail i like to used the Maildir format
well anyone can guide me to the URL that contains this stuf
or show me how to do it
Thanks
--
Yamin Prabudy
[EMAIL PROTECTED]
StarNET
ps you get Qmail up and keeping it up..
Philip
From: Yamin Prabudy [EMAIL PROTECTED]
Date: Sat, 11 Dec 1999 11:20:12 +0700
To: "[EMAIL PROTECTED]" [EMAIL PROTECTED]
Subject: sendmail -- qmail (Maildir)
I like to migrate from sendmail to qmail
and in qmail i like to used the
Why do I have old messages (as in 3-4 days old) in Maildir/tmp?
Shouldn't these be moved to Maildir/new at delivery? If this isn't
always the case, can someone please explain why they haven't been moved
and also when, if ever, they will be.
Cheers
Fred
Fred Backman writes:
Why do I have old messages (as in 3-4 days old) in Maildir/tmp?
Shouldn't these be moved to Maildir/new at delivery? If this isn't
always the case, can someone please explain why they haven't been moved
and also when, if ever, they will be.
Stuff in tmp is partially
601 - 700 of 1015 matches
Mail list logo
