LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices

Reply
 
Search this Thread
Old 01-13-2005, 09:34 PM   #1
padawan05
LQ Newbie
 
Registered: Jan 2005
Posts: 1

Rep: Reputation: 0
Exim configuration file errors


I'm working on a bootable distro of morphix... and trying to integrate spamassassin 2.20 into exim as part of it. However, I keep getting an error during boot... then, I'll change somthing in the config file, and it will go to a different error. My current problem is a real_local: error, but I can't, for the life of me figure out the problem. Any suggestions are welcome.

Adrienne
 
Old 01-13-2005, 11:11 PM   #2
foo_bar_foo
Senior Member
 
Registered: Jun 2004
Posts: 2,553

Rep: Reputation: 51
i don't know exactly what you are doing but you can just have exim use procmail and then have ~/.procmailrc use spammassassin
if you want to try that

all i can think of is to give you my config from the directors section down to retry it's for exim4
Code:
######################################################################
#                      DIRECTORS CONFIGURATION                       #
#             Specifies how local addresses are handled              #
######################################################################
#                          ORDER DOES MATTER                         #
#   A local address is passed to each in turn until it is accepted.  #
######################################################################

# This allows local delivery to be forced, avoiding alias files and
# forwarding.

real_local:
#!!# prefix renamed local_part_prefix
  driver = accept
  check_local_user
  local_part_prefix = real-
  transport = local_delivery

# This director handles aliasing using a traditional /etc/aliases file.
# If any of your aliases expand to pipes or files, you will need to set
# up a user and a group for these deliveries to run under. You can do
# this by uncommenting the "user" option below (changing the user name
# as appropriate) and adding a "group" option if necessary.

system_aliases:
  driver = redirect
  allow_defer
  allow_fail
  data = ${lookup{$local_part}lsearch{/etc/aliases}}
  file_transport = address_file
  pipe_transport = address_pipe
  retry_use_local_part
# user = list
# Uncomment the above line if you are running smartlist


# This director handles forwarding using traditional .forward files.
# It also allows mail filtering when a forward file starts with the 
# string "# Exim filter": to disable filtering, uncomment the "filter" 
# option. The check_ancestor option means that if the forward file 
# generates an address that is an ancestor of the current one, the 
# current one gets passed on instead. This covers the case where A is 
# aliased to B and B has a .forward file pointing to A.

# For standard debian setup of one group per user, it is acceptable---normal
# even---for .forward to be group writable. If you have everyone in one
# group, you should comment out the "modemask" line. Without it, the exim
# default of 022 will apply, which is probably what you want.

userforward:
#!!# filter renamed allow_filter
  driver = redirect
  allow_filter
  check_ancestor
  check_local_user
  file = $home/.forward
  file_transport = address_file
  modemask = 002
  pipe_transport = address_pipe
  reply_transport = address_reply
  no_verify

# This director runs procmail for users who have a .procmailrc file

procmail:
  driver = accept
  check_local_user
  require_files = ${local_part}:+${home}:+${home}/.procmailrc:+/usr/bin/procmail
  transport = procmail_pipe
  no_verify
    
# This director matches local user mailboxes.

localuser:
  driver = accept
  check_local_user
  transport = local_delivery



######################################################################
#                      TRANSPORTS CONFIGURATION                      #
######################################################################
#                       ORDER DOES NOT MATTER                        #
#     Only one appropriate transport is called for each delivery.    #
######################################################################

# This transport is used for local delivery to user mailboxes. On debian
# systems group mail is used so we can write to the /var/spool/mail
# directory. (The alternative, which most other unixes use, is to deliver
# as the user's own group, into a sticky-bitted directory)

begin transports

local_delivery:
  driver = appendfile
  envelope_to_add
  file = /var/mail/${local_part}
#  group = mail
  group = exim
  mode = 0660
  no_mode_fail_narrower
  return_path_add

# This transport is used for handling pipe addresses generated by
# alias or .forward files. If the pipe generates any standard output,
# it is returned to the sender of the message as a delivery error. Set
# return_fail_output instead if you want this to happen only when the
# pipe fails to complete normally.

address_pipe:
  driver = pipe
  path = /usr/bin:/bin:/usr/local/bin
  return_output

# This transport is used for handling file addresses generated by alias
# or .forward files.

address_file:
  driver = appendfile
  envelope_to_add
  return_path_add

# This transport is used for handling file addresses generated by alias
# or .forward files if the path ends in "/", which causes it to be treated
# as a directory name rather than a file name. Each message is then delivered
# to a unique file in the directory. If instead you want all such deliveries to
# be in the "maildir" format that is used by some other mail software,
# uncomment the final option below. If this is done, the directory specified
# in the .forward or alias file is the base maildir directory.
#
# Should you want to be able to specify either maildir or non-maildir
# directory-style deliveries, then you must set up yet another transport,
# called address_directory2. This is used if the path ends in "//" so should
# be the one used for maildir, as the double slash suggests another level
# of directory. In the absence of address_directory2, paths ending in //
# are passed to address_directory.

address_directory:
#!!# prefix renamed message_prefix
#!!# suffix renamed message_suffix
#!!# no_from_hack replaced by check_string
  driver = appendfile
  check_string = 
  message_prefix = ""
  message_suffix = ""
# maildir_format

# This transport is used for handling autoreplies generated by the filtering
# option of the forwardfile director.

address_reply:
  driver = autoreply

# This transport is used for procmail

procmail_pipe:
#!!# suffix renamed message_suffix
  driver = pipe
  command = "/usr/bin/procmail"
  delivery_date_add
  envelope_to_add
  message_suffix = ""
  return_path_add
# check_string = "From "
# escape_string = ">From "


# This transport is used for delivering messages over SMTP connections.

remote_smtp:
  driver = smtp
# authenticate_hosts = smarthost.isp.com

# To use SMTP AUTH when sending to a particular host, such as your ISP's
# smarthost, uncomment and edit the above line, and also the example
# client-side authenticators at the bottom of the file
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
exim configuration question greg.hellings Linux - Software 0 11-05-2004 04:15 PM
Exim mail configuration in Debian lupus9537 Linux - Newbie 1 07-05-2004 05:31 PM
exim is failed !!! error:package exim is not installed apache Linux - Software 0 06-24-2004 05:55 AM
Exim Configuration for local mail. Greymist Linux - Software 0 06-06-2004 07:16 AM
Fetchmail & Exim pop3 configuration sebyte Debian 1 03-17-2004 09:29 PM


All times are GMT -5. The time now is 01:33 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration