-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 14 Jul 2010, Timo Sirainen wrote:
But /var/tmp exists, right?
So, just in case, the default could be:
/var/tmp, but /tmp if /var/tmp is missing.
Personally, I just would use /tmp, because these file do not need to
survive a machine rebo
On Thu, 2010-07-15 at 08:54 -0700, Daniel L. Miller wrote:
> "/var/spool contains data which is awaiting some kind of later
> processing. Data in /var/spool represents work to be done in the future
> (by a program, user, or administrator); often data is deleted after it
> has been processed."
On 7/15/2010 1:27 AM, Thomas Leuxner wrote:
On Wed, Jul 14, 2010 at 11:53:48PM -0500, Stan Hoeppner wrote:
Don't rely on an existing temp directory. Create /var/spool/dovecot/ and
/var/spool/dovecot/tmp/ with the installation script and assign the
appropriate permissions. This solves the c
On Thu, 2010-07-15 at 14:52 +0200, Edgar Fuß wrote:
> > The file size isn't known beforehand.
> I thought that because it's known to be >128k, it's known.
Dovecot reads 128 kB to memory first, then thinks this is beginning to
be too much and starts writing to disk instead.
> The file size isn't known beforehand.
I thought that because it's known to be >128k, it's known.
On 15.7.2010, at 10.02, William Blunn wrote:
> If know you are delivering to Maildir, and you know the folder you are
> delivering to,
But I don't. Sieve could do just about anything to the message.
> then surely you have a temporary directory in the "tmp" out of Maildir's
> {new,cur,tmp} ? A
On 15.7.2010, at 9.16, Christian Rohmann wrote:
Any thoughts?
>>> Could the location be made dependant on the file size?
>>
>> The file size isn't known beforehand.
>
> But it could be known if the SIZE extention of LMTP is used right?
It wouldn't be known with deliver. And I wasn't plann
On Wed, Jul 14, 2010 at 09:34:52PM +0100, Timo Sirainen wrote:
[...]
> So why was the move made in the first place? Because a) some people had
> small (maybe ramfs) /tmp and Dovecot was eating it all up and b) to
On Solaris, this is the situation, though it's not called ramfs but:
l...@hydra:/tmp
1.
If know you are delivering to Maildir, and you know the folder you are
delivering to, then surely you have a temporary directory in the "tmp"
out of Maildir's {new,cur,tmp} ? And also the potential benefit of being
able to rename the resulting file into the "new" directory.
2.
I would l
On Wed, Jul 14, 2010 at 11:53:48PM -0500, Stan Hoeppner wrote:
>
> Don't rely on an existing temp directory. Create /var/spool/dovecot/ and
> /var/spool/dovecot/tmp/ with the installation script and assign the
> appropriate permissions. This solves the current problem and gives you a
> dedicated
Hey all,
On 07/14/2010 11:02 PM, Timo Sirainen wrote:
> On Wed, 2010-07-14 at 22:55 +0200, Edgar Fuß wrote:
>>> Any thoughts?
>> Could the location be made dependant on the file size?
>
> The file size isn't known beforehand.
But it could be known if the SIZE extention of LMTP is used right?
T
Timo Sirainen put forth on 7/14/2010 3:34 PM:
> Any thoughts?
Don't rely on an existing temp directory. Create /var/spool/dovecot/ and
/var/spool/dovecot/tmp/ with the installation script and assign the
appropriate permissions. This solves the current problem and gives you a
dedicated dovecot s
On 14.7.2010, at 22.02, Steven King wrote:
>> So why was the move made in the first place? Because a) some people had
>> small (maybe ramfs) /tmp and Dovecot was eating it all up and b) to
>> avoid any potential security issues with storing per-user files to a
>> shared directory.
> I haven't seen
Den 14.07.2010 22:34, skrev Timo Sirainen:
In v1.0 .. v1.1 deliver was writing incoming>128k mail to /tmp file (to
avoid reading it all into memory). In v1.2 I moved it to user's home
directory. This slowed deliveries for NFS users. Also people with
filesystem quota had trouble since now user req
On Wed, 2010-07-14 at 22:55 +0200, Edgar Fuß wrote:
> > Any thoughts?
> Could the location be made dependant on the file size?
The file size isn't known beforehand. It's between 128 kB and whatever
the max. mail size is configured to be in your system.
On 7/14/10 4:34 PM, Timo Sirainen wrote:
> In v1.0 .. v1.1 deliver was writing incoming >128k mail to /tmp file (to
> avoid reading it all into memory). In v1.2 I moved it to user's home
> directory. This slowed deliveries for NFS users. Also people with
> filesystem quota had trouble since now u
> Any thoughts?
Could the location be made dependant on the file size?
My usual setup is mfs on /tmp and ffs on /var/tmp, so /tmp being smaller and
faster and /var/tmp being larger and slower.
17 matches
Mail list logo
