[ Converted text/html to text/plain ]
This is definatly an issue with how exim-4.x works. I have been
doing testing on a RedHat 7.2 server with the mailspool mounted over
NFS. Exim-3.35 works just fine (just as you found), but any of the
exim-4.x builds do not. The all give the same error when exim tries
to deliver mail (exim -v user@domain):
LOG: MAIN
Message abandoned: spool file directory sync error while receiving
from root: Invalid argument
LOG: MAIN
Message abandoned: spool file directory sync error while receiving
from exim: Invalid argument
LOG: MAIN
Child mail process returned status 1
or (exim -d -v user@domain):
Data file written for message 177Izp-0007NT-00
calling local_scan(); timeout=300
local_scan() returned 0 NULL
Writing spool header file
LOG: MAIN
Message abandoned: spool file directory sync error while receiving
from root: Invalid argument
exec /usr/exim/bin/exim -d=0xfff7577f -t -oem -oi -f <> -E177Izp-
0007NT-00
Child process 28364 for sending message
Exim version 4.04 uid=57 gid=12 pid=28364 L=834cd8 D=fff7577f
Berkeley DB: Sleepycat Software: Berkeley DB 3.2.9: (January 24,
2001)
changed uid/gid: forcing real = effective
uid=0 gid=12
auxiliary group list: <none>
trusted user
admin user
changed uid/gid: privilege not needed
uid=57 gid=12
auxiliary group list: <none>
originator: uid=57 gid=12 login=exim name=
sender address =
set_process_info: 28364 accepting a local non-SMTP message from <>
Sender:
search_tidyup called
>>Headers received:
From: Mail Delivery System <Mailer-Daemon@domain>
To: root@domain
Subject: Mail failure - system failure
rewrite_one_header: type=F:
From: Mail Delivery System <Mailer-Daemon@domain>
rewrite_one_header: type=T:
To: root@domain
search_tidyup called
>>Headers after local additions:
P Received: from exim by mail.domain with local (Exim 4.04)
id 177Izv-0007NU-00
for root@domain; Mon, 13 May 2002 11:48:31 -0500
F From: Mail Delivery System <Mailer-Daemon@domain>
T To: root@domain
Subject: Mail failure - system failure
I Message-Id: <E177Izv-0007NU-00@???[1]>
Date: Mon, 13 May 2002 11:48:31 -0500
Data file written for message 177Izv-0007NU-00
calling local_scan(); timeout=300
local_scan() returned 0 NULL
Writing spool header file
LOG: MAIN
Message abandoned: spool file directory sync error while receiving
from exim: Invalid argument
search_tidyup called
>>>>>>>>>>>>>>>>>> Exim pid=28364 terminating with rc=1
>>>>>>>>>>>>>>>>>>
LOG: MAIN
Child mail process returned status 1
search_tidyup called
>>>>>>>>>>>>>>>>>> Exim pid=28363 terminating with rc=1
>>>>>>>>>>>>>>>>>>
And yes, exim-4.x does deliver to non NFS mounts just fine. So, I
do not know what has changed between the exim-3.x builds and the
exim-4.x builds, but something has.
Until I saw this posting, I thought that I was just doing something
wrong, but I do not believe so, as I do not believe that this is a
NFS issue, I believe this is a exim-4.x NFS issue.
Does anybody have exim-4.x delivering mail to a NFS mounted
mailspool?
--- In exim-users@y..., Troy Engel <tengel@f...> wrote:
> Matthew Byng-Maddick wrote:
> >
> > Almost certainly. NFS's locking gives no guarantees, operations
are not
> > atomic etc. You do NOT want to be using NFS for your spool. Move
your
> > spool to somewhere local to the mailhost.
>
> Thanks for confirming my suspicion -- I moved the spool in the
middle of
> the night this weekend to a local filesystem, and that problem went
> away. I'm just curious why Exim3 works fine with it, and Exim4
> doesn't.... *shrug*
>
> -te
>
> --
> Troy Engel, Systems Engineer
> Hockey. Kinda like Figure Skating in a War Zone.
>
>
> --
>
------------------------------------------------------------------------------
MSN Photos is the easiest way to share and print your photos: Click Here[2]
===References:===
1.
http://lw7fd.law7.hotmail.msn.com/cgi-bin/compose?curmbox=F000000001&a=a7f064fb1accc62a44dc0b55fc5d5199&mailto=1&to=E177Izv-0007NU-00@mail.domain&msg=MSG1021311520.11&start=114381&len=5909&src=&type=x
2.
http://g.msn.com/1HM105401/46
