Hi Hermann,
First of all, please keep the discussion to the list. I have added a Cc:
to the exim-users mailing list. That way, other people can also
contribute to the problem. I don't want to be come your personal support
engineer.
Hermann Flacke wrote:
>>>My problem: I'm running my fetchmail on SuSE as well as on
>>>Debian Sarge. So I would like to set a new user's spool
>>>directory. Setting the value "spool_directory = /suse/var/spool/mail"
>>>in the /etc/exim4/configure + dpkg-reconfigure exim4-config
>>>doesn't work because the incoming mail still is put into
>>>/var/spool/mail/<user>.
>>
>>You're confused. The spool_directory setting in exim defines where exim
>>keeps messages temporarily while it delivers them. It is NOT the
>>directory where the user mailboxes are located.
>
> Isn't there any way to determine the spool directory by some
> configuration item like this one - /etc/exim4/configure.
> But this one doesn't work out either. Probably I'm still confused? :-)
>
> local_delivery:
> driver = appendfile
> file = /suse/var/spool/mail/$local_part
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> # original version: file = /var/mail/$local_part
> delivery_date_add
> envelope_to_add
> return_path_add
> # group = mail
> # mode = 0660
Well, this looks ok to me. Exim should be delivering to
/suse/var/spool/mail. However, if you say that deliveries are still
happening to /var/spool/mail on the debian partition, then it may be
that your fetchmail is NOT calling exim, but a mail delivery agent such
as procmail. Check your fetchmail configuration to see if it has an
option called 'mda' anywhere. Additionally, you should run fetchmail
with the '-v' option to see what exactly it is doing.
If you find that fetchmail is not calling an mda, but exim, then it may
be that you have simply forgotten to restart exim after making this
change. You need to restart exim to for it to notice the changed
configuration.
