> >>
> >${local_part} is taken from the recipiant's email address. if someone
> >sent you an email (to: [EMAIL PROTECTED]) the exim splits up the address on
> >the @ and sets two variables:
> >
> >local_part: paul
> >domain: foo.com
> >
> What process does that substitution?
I'm not exactly sure, to be honest...
I tried a little experiment below
woody:/usr/src/linux# exim -d8 -bt david
Exim version 3.35 debug level 8 uid=0 gid=0
Berkeley DB: Sleepycat Software: Berkeley DB 2.7.7: (08/20/99)
Caller is an admin user
Caller is a trusted user
user name "root" extracted from gecos field "root"
address david@woody
local_part=david domain=woody
domain is local
system_aliases director: lsearch key=david
file="/etc/aliases"
system_aliases director declined for david:
userforward director: file = .forward
set uid=0 gid=0 euid=1000 egid=1000
successful stat of /home/david/.
/home/david/.forward not found
restored uid=0 gid=0 euid=8 egid=8
queued for local_delivery transport: local_part=david domain=woody
errors_to=NULL
domain_data=NULL local_part_data=NULL
localuser director succeeded for david
david@woody
deliver to david in domain woody
director = localuser, transport = local_delivery
I guess the debugging above indicates that it is set prior to any of the
delivery facilities configured in exim.conf...I dont know...is this
useful? maybe I'm not sure what info you are trying to find.
>
> >so if you were doing multiple domains on one box, you could do:
> >
> >file = /var/spool/mail/${domain}/${local_part}
> >
> >or some such.
> >
> That part was clear. I was just expecting local_part to be something
> that I set somewhere else in exim.conf.
I think those are set at delivery time. if you were able to set them in
the config file, it would seem to me that all your mail would get dumped
in one box.
davidc
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
