On Thu, 2006-08-31 at 09:52 +0200, Josip Rodin wrote:
> On Wed, Aug 30, 2006 at 10:59:12PM -0400, Greg Folkert wrote:
> > BTW, local users are supposed to be force into a $HOMEDIR/Maildir
> > delivery setup. So no mail goes into any files-system other than /home.
> 
> On related note, is $HOME/Maildir a maildir rather than a mbox?
> If so, does it get maildirmake'd before delivering to it?

Yes, when exim is defaulted (as I have it) to deliver to $HOME/Maildir
it does create it period. The directory is created as part of the user
creation, an e-mail is sent as a welcome, causing exim4 to create it if
it doesn't exist. also it is a part of the template skel directory.

> > The rest of the users I have are virtual and are not able to
> > use .mailfilter or any other dot files.
> 
> Ah, so their $HOME doesn't have .mailfilter, and so the Exim router never
> gets triggered due to require_files.

All of the virtual users don't have a home, only the domain does.

No triggering is possible.

> > Getting back to the point though, I can install "maildrop" and see what
> > still occurs. This would be on Sarge currently.
> > 
> > I might be able to force a different newer version if you think it might
> > help. I'd have to give a heads up to my users, to allow them to cope.
> 
> I wouldn't insist on it, given that it's a production system. And since
> sarge still has the old 1.5.x version, if we found anything concrete,
> you'd still have to upgrade half of etch/sid to get an updated maildrop.
> So I'm thinking - let's close this as an unreproducible bug, and next
> time you upgrade your system and have an already announced downtime,
> try maildrop and see how it works out, and file a new bug report.
> Would that be okay?

That would be fine. I'd just assume to reduce the long-term bug count as
to go through the pain right now of doing a half upgrade. So yeah, file
it as unreproducible/"more info" type of thing.

I am installing a new machine Friday that will be a SID+Experimental
machine. It will be mainly for personal use but in production... but
still, I might be able to move a few trusted users to the machine for
testing.

If I find problems, I'd rather file a new report, as I could get more
info for it, maybe even let you have a login to do some testing or
forensics.

Once again, thanks for your efforts with Debian, I really appreciate the
hard work.
-- 
greg, [EMAIL PROTECTED]

The technology that is
Stronger, better, faster:  Linux

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to