[nflug] Setting up local MTA as relay questions POSSIBLE REASON

JJ Neff jjneff at yahoo.com
Fri Sep 29 13:33:45 EDT 2006


I sent from another user to jjneff at elrey.jjn.com and it got renamed to jjneff

2006-09-29 12:30:48 1GTMCG-0008Ho-PU <= lgneff at jjn.com U=lgneff P=local S=467 id=20060929173048.GD30803 at jjn.com
2006-09-29 12:30:48 1GTMCG-0008Ho-PU => jjneff <jjneff at elrey.jjn.com> R=local_user T=mail_spool
2006-09-29 12:30:48 1GTMCG-0008Ho-PU Completed


THAT got delivered !  So it appears the default of jjn.com is not liked somehow or by appending manually teh FQDN of the serer it did not append the default and instead stripped it and delivered it - now to figure out where I'm going wrong with defaults...

JJN

----- Original Message ----
From: JJ Neff <jjneff at yahoo.com>
To: Niagara Frontier Linux Users Group <nflug at nflug.org>
Sent: Friday, September 29, 2006 12:28:08 PM
Subject: [nflug] Setting up local MTA as relay questions(More data)

It's important to note that the mail from local that is getting routed to gmail is NOT going out - it is freezing. (no real person to realy to and no real person to return bounce to :-(  darn 

And I figured you may want to see the router and transport that keeps picking up all mail!

.ifdef DCconfig_smarthost DCconfig_satellite
# configtype=smarthost or configtype=satellite
#
# Send all non-local mail to a single other machine (smarthost).
#
# This means _ALL_ non-local mail goes to the smarthost. This will most
# probably not do what you want for domains that are listed in
# relay_domains. The most typical use for relay_domains is to control
# relaying for incoming e-mail on secondary MX hosts. In that case,
# it doesn't make sense to send the mail to the smarthost since the
# smarthost will probably send the message right back here, causing a
# loop.
#
# If you want to use a smarthost while being secondary MX for some
# domains, you'll need to copy the dnslookup_relay_to_domains router
# here so that mail to relay_domains is handled separately.

smarthost:
  debug_print = "R: smarthost for $local_part@$domain"
  driver = manualroute
  domains = ! +local_domains
  transport = remote_smtp_smarthost
  route_list = * DCsmarthost byname
  host_find_failed = defer
  same_domain_copy_routing = yes
  no_more

.endif


# The "no_more" above means that all later routers are for
# domains in the local_domains list, i.e. just like Exim 3 directors.


TRANSPORT
### transport/30_exim4-config_remote_smtp_smarthost
#################################

# This transport is used for delivering messages over SMTP connections
# to a smarthost. The local host tries to authenticate and does some
# modification in headers and return-path.
# This transport is used for smarthost and satellite configurations.

remote_smtp_smarthost:
  debug_print = "T: remote_smtp_smarthost for $local_part@$domain"
  driver = smtp
  hosts_try_auth = ${if exists {CONFDIR/passwd.client}{DCsmarthost}{}}
  tls_tempfail_tryclear = false
  DEBCONFheaders_rewriteDEBCONF
  DEBCONFreturn_pathDEBCONF
#####################################################
### end transport/30_exim4-config_remote_smtp_smarthost


SO I assumed the ! +local_domains would see the jjn.com and then pass it to the local dfelivery router/transport...

JJN




_______________________________________________
nflug mailing list
nflug at nflug.org
http://www.nflug.org/mailman/listinfo/nflug



_______________________________________________
nflug mailing list
nflug at nflug.org
http://www.nflug.org/mailman/listinfo/nflug



More information about the nflug mailing list