On Wed, Feb 03, 1999 at 11:39:07AM -0500, Jere Cassidy wrote:
> Sorry to get a little off topic for this particular thread, but...
>
> Jaye Mathisen wrote:
>
> > I did not save all my testdata unfortunately, but at one time, I had 2
> > FreeBSD P6 boxes, NFS mounting a Netapp F540, using Maildir for delivery,
> > and several boxes generating the email in front. The P6's were
> > loadbalanced with a Cisco LocalDirector.
>
> We are doing something very similar with an Alteon ACEDirector balancing to 4
> Alpha's running Redhat and qmail. Backend network is a Netapp F230 that is
> handling the Maildirs. I was wondering a few things.
>
> a) Almost all delivery (from sending client to remote client) takes 3 to 4
> minutes. However, If I look in the receiving client's Maildir/new after the
> sending client sends the message, it is there in 5 to 10 seconds. Any POP3
> connection simply does not notice the file is there even though it is present on
> all 4 servers (via the Netapp, of course). Most likely this is the result of
> some caching that the front end servers are doing, but we haven't been able to
> track it down exactly. I was curious if you, or anyone else running a similar
> setup, saw anything like this issue.
This came up a few days ago, and the problem was that the clocks on the NFS
server and the machine running qmail-pop3d were out of synch. For some reason,
qmail-pop3d won't retrieve a message for you if the modified time is in the
future. (To prove this to yourself, touch -t a file in your Maildir/new to some
time in the future.)
Chris
