If you are in fact a customer of MSN and not working from them, and you
need to use their 'outgoing mail server' (which you probably do, and is
called smarthosting), then it appears from your mail headers the
'email.msn.com' is the correct host.. See below for exactly where to
put that..
On Thu, 10 Aug 2000, Dave C. wrote:
>
>
> See comments inline in your config file..
>
>
> On Thu, 10 Aug 2000, davidturetsky wrote:
>
> > When I run exim -bt davidturetsky@???
> >
> > I get:
> >
> > david@
> > <---davidturetsky@???
> > deliver to david@
> > router-smarthost, transport=remote_smtp
> > host msn.com [207.46.176.152]
> > host msn.com [207.46.185.39]
> >
> > I added in 'email' to the address and a similar entry to resolv.conf (as
> > well as smtp.email.msn.com)
> >
> > Rerunning the attempt to flush the spool with the domain nomenclature change
> > to @email.msn.com or @smtp.msn.com produced the same result as originally
> > posted
> >
> > I made a few modifications to exim.conf (which follows):
> >
> > added entry for local_domains=free:email.msn.com (for list application)
> >
> > removed entry after qualify_domain = (leaving rhs blank)
> >
> > added .com to route_list in smarthost section (to resolve 'lookup of host
> > "msn" failed in smarthost router')
> >
> > Here is exim.conf, with most comments removed (except pending section for
> > mailing list)
>
>
> # See my comment below, this is the MAIN config section
>
> >
> > qualify_domain =
> > local_domains = free:email.msn.com
> > local_domains_include_host = true
> > local_domains_include_host_literals = true
> > never_users = root
> > host_lookup_nets = 0.0.0.0/0
> > sender_host_reject_relay = *
> > trusted_users = mail
> > smtp_verify = false
> > gecos_pattern = ^([^,:]*)
> > gecos_name = $1
> >
> > received_header_text = "Received: \
> > ${if def:sender_fullhost {from ${sender_fullhost} \
> > ${if def:sender_ident {(${sender_ident})}}\n\t}\
> > {${if def:sender_ident {from ${sender_ident} }}}}\
> > by ${primary_hostname} \
> > ${if def:received_protocol {with ${received_protocol}}} \
> > (Exim ${version_number} #${compile_number} (Debian))\n\t\
> > id ${message_id}"
> > end
> >
>
> # See my comment below, this is the TRANSPORTS config section
>
> > local_delivery:
> > driver = appendfile
> > group = mail
> > mode = 0660
> > mode_fail_narrower = false
> > file = /var/spool/mail/${local_part}
> >
> > address_pipe:
> > driver = pipe
> > return_output
> >
> >
> > address_file:
> > driver = appendfile
> >
> > address_directory:
> > driver = appendfile
> > no_from_hack
> > prefix = ""
> > suffix = ""
> >
> > address_reply:
> > driver = autoreply
> >
> > remote_smtp:
> > driver = smtp
> >
> > end
>
> # See my comment below this is the DIRECTORS section
>
> >
> > real_local:
> > prefix = real-
> > driver = localuser
> > transport = local_delivery
> >
> > system_aliases:
> > driver = aliasfile
> > file = /etc/aliases
> > search_type = lsearch
> >
> > userforward:
> > driver = forwardfile
> > no_verify
> > check_ancestor
> > file = .forward
> > modemask = 002
> > filter
> >
> > localuser:
> > driver = localuser
> > transport = local_delivery
> >
> > end
>
> # See my comment below, this is the ROUTERS section
>
> > smarthost:
> > driver = domainlist
> > transport = remote_smtp
> > route_list = "* msn.com bydns_a"
>
Change 'msn.com' to be 'email.msn.com' in this line. That will at least
get your outgoing mail working.
It wont do anything for free.email.msn.com, which wont work without
some arrangements with the MSN.COM mail/dns administrators. (Which they
probably wont do unless you either pay them for the subdomain, or
unless you are setting this up on their behalf)
> ^^^
> Here's the problem. You are telling exim to take all remote mail, and
> smarthost it to the host 'msn.com' - the problem is that that host is
> not running an MTA at port 25. Perhaps you should be using smtp.msn.com
> or something like that?
>
> If you are an administrator at msn.com, do you really need this machine
> to smarthost mail to another, or could it just deliver mail
> normally? If it needs to smarthost, I would think you would know what
> machine the smarthost was (and it definately isn't 'msn.com')
>
> If you aren't an administrator, do you have some arrangement with them
> to transmit mail for free.email.msn.com to your server? If not, then it
> won't be delivered to you, so unless this is something you are
> implenting on a private network it wont serve any useful purpose. I
> will note that there currently isn't and record in the DNS for that
> domain.
>
> If you are receiving mail for just one address at that domain and want
> to filter your incoming mail by address, you arent really using the
> right tool - you should use filters or procmail or a MUA-based tool.
>
>
>
> >
> > end
> > * * F,2h,15m; G,16h,2h,1.5; F,4d,8h
> >
> > end
> >
>
> The entire below are in the wrong config file section. This is the
> 'retry' section. This appears to be a director, and should be in the
> appropriately commented section (The comments in the config file
> normally indicate which is which - I've added notes here so you can
> tell which is which..
>
> > # Handle mail to free@???
> >
> > #lists:
> > # driver = forwardfile
> > # domains = free.email.msn.com
> > # no_more
> > # require_files = /etc/exim/lists/${local_part}
> > # file = /etc/exim/lists/${local_part}
> > # no_check_local_user
> > # errors_to = #{local_part}-request
> >
> > end
> >
> > # End of Exim configuration file
> >
> > ----- Original Message -----
> > From: "Philip Hazel" <ph10@???>
> > To: "davidturetsky" <davidturetsky@???>
> > Cc: "exim-users" <exim-users@???>
> > Sent: Thursday, August 10, 2000 4:48 AM
> > Subject: Re: [Exim] New exim user
> >
> >
> > > On Thu, 10 Aug 2000, davidturetsky wrote:
> > >
> > > > I am trying to make first use of exim to handle a list application and
> > have queued a few messages using elm and exim as a test. These messages and
> > a bunch of mail from vim were sitting seemingly stuck at /var/spool/exim. I
> > deleted the vim messages and following notes from the exim website, issued:
> > > >
> > > > /usr//sbin/exim -d9 -M 13MhR6-00007I-00 and got the following output:
> > > >
> > > > .
> > > > .
> > > > remote_smpt transport entered
> > > > davidturetsky@???
> > > > locked /var/spool/exim/db/retry.lockfile
> > > > opened DB file /var/spool/exim/db/retry: flags=0
> > > > dbfn_read key=T:msn.com: 207.46.176.152
> > > > no retry record
> > > > msn.com [207.46.176.152] status=usable
> > > > delivering 13MhR6-00007I-00 to msn.com [207.46.176.152]
> > (davidturetsky@???)
> > > > set_process_info: 204 2.05 delivering 13MhR6-00007I-00 to msn.com
> > [207.46.176.152] (davidturetsky@???)
> > > > Connecting to msn.com [207.46.176.152] ...
> > > >
> > > > and then the system seemingly is sitting there accepting tty input
> > >
> > > Is 207.46.176.152 a running system? I cannot ping it from here. Did you
> > > modify the default configuration? I see that msn.com has lots of MX
> > > records pointing to hosts *other* than msn.com [207.46.176.152]. Maybe
> > > that host doesn't listen. What does
> > >
> > > exim -bt davidturetsky@???
> > >
> > > say? For me, it says
> > >
> > > davidturetsky@???
> > > deliver to davidturetsky@???
> > > router = lookuphost, transport = smtp
> > > host cpimssmtpe07.msn.com [207.46.181.46] MX=30
> > > host cpimssmtpe10.msn.com [207.46.181.47] MX=30
> > > host cpimssmtpe09.msn.com [207.46.181.40] MX=30
> > > host cpimssmtpe04.msn.com [207.46.181.25] MX=30
> > > host cpimssmtpe12.msn.com [207.46.181.59] MX=30
> > > host cpimssmtpe13.msn.com [207.46.181.61] MX=30
> > > host cpimssmtpe06.msn.com [207.46.181.45] MX=30
> > > host cpimssmtpe11.msn.com [207.46.181.56] MX=30
> > > host cpimssmtpe08.msn.com [207.46.181.39] MX=30
> > >
> > > Note: it does not include the host you refer to.
> >
> >
> >
> >
> > --
> > ## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at http://www.exim.org/ ##
> >
>
>
--
