Re: [EXIM] a few questions from a newbie

Top Page
Delete this message
Reply to this message
Author: Philip Hazel
Date:  
To: Random Junk
CC: exim-users
Subject: Re: [EXIM] a few questions from a newbie
On Mon, 29 Dec 1997, Random Junk wrote:

> i've got my own machine, and i'd like unqualified mail by default to
> go to the local domain (gamespot.com). unless, of course, the
> unqualified name is mine (jsd) or root. with sendmail you could use
> the local users class to set this up. i don't see anything similar in
> exim. how do i achieve this?


Not quite sure what you are asking here. Do you want jsd and root to be
delivered locally, and everything else to get forwarded somewhere? If
so, you could pick off the everything else with a smartuser director
that contains the option

except_local_parts = jsd:root

and then let jsd and root fall through to other directors to handle them
locally.

> i can't get delivery to procmail via a .forward file to work
> properly. the .forward file reads:
>
>    /usr/local/bin/procmail -f-

>
> this is what shows up in the exim log:
>
> 1997-12-29 16:53:26 0xmpvy-0000nf-00 == /usr/local/bin/procmail -f- <jsd@???> T=address_file defer (13): Permission denied: creating lock file hitching post /usr/local/bin/procmail -f-.lock.hudsucker.gamespot.com.34a84606.00000c09
>
> i'm running exim setuid root. shouldn't it be able to create lock
> files at will? i'm not even sure where it's trying to write, given
> that the pathname isn't given in the log entry.


Exim always runs a local delivery as some specific uid, *not* as root.
In this case, it will be running the delivery under your own uid/gid,
and presumably you do not have permission to write to the directory
/usr/local/bin, which is where it is trying to write a file. You need to
tell it to write to a pipe, which means starting the item with a |
character.

> finally, is there a way to write to a separate queue directory and
> then have an exim queue runner periodically process it? i have a
> large mailing list and ideally i'd like to queue up all the messages
> for it first, then start exim running on it.


Call exim with -odq or set queue_only to prevent it delivering.
Actually, it sounds as if you would do better to set -odqs or
queue_smtp, which causes it to do the routing but not the delivery. In
that case, several messages routed to the same remote host will go down
the same SMTP connection.

-- 
Philip Hazel                   University Computing Service,
ph10@???             New Museums Site, Cambridge CB2 3QG,
P.Hazel@???          England.  Phone: +44 1223 334714



--
*** Exim information can be found at http://www.exim.org/ ***