[courier-users] maildrop and "Read-only file system" error

[J. P. <jpo...@co...>]

Hi List & Sam,

We had our NFS server choke up (ext3 journal error that dropped the  
exported filesystem to read-only state), which caused maildrop to hard  
bounce messages that it was attempting to write to the nfs mount with  
a "Read-only file system" error.

Is there a way to get maildrop to treat such a case as a soft failure,  
so that it holds the message in local delivery spool (under /var) and  
re-attempts the local delivery a while later? This would allow for  
more graceful degraded mode when a filesystem is in read-only mode.  
(Which, admittedly, is a problem, but a different issue.)

best,
Jeff