Re: [Exim] Broken Aliases after upgrading from Exim3 to Exim…

Αρχική Σελίδα
Delete this message
Reply to this message
Συντάκτης: Dean Staff
Ημερομηνία:  
Προς: exim-users
Αντικείμενο: Re: [Exim] Broken Aliases after upgrading from Exim3 to Exim4
On 3 Nov 2003 at 9:38, Odhiambo G. Washington wrote:

From:               "Odhiambo G. Washington" <wash@???>
To:                 exim-users@???
Date sent:          Mon, 3 Nov 2003 09:38:26 +0300
Subject:            Re: [Exim] Broken Aliases after upgrading from Exim3 to Exim4


> * Dean Staff <dean@???> [20031102 21:14]: wrote:
> > Hi,
> > I recently upgraded from Exim 3 to Exim 4.2x
> > my problem is I have 1 e-mail account for my domain I treat as an


<snip - Edited to save bandwidth>

> have you tried exim -d -bt that@???. That will guide you
> towards solving the problem. It looks easy enough. All you have to
> verify is that mails addressed to remote addresses get delivered. If
> so, then the case of this particular address is special and has
> nothing to do with Exim itself.
>
>         cheers
>        - wash
> +----------------------------------+----------------------------------
> +-------+

Hi Wash,
I tried your suggestion,
I get no errors that I can see when I run
/usr/sbin/exim4 -d-bt john@<mydomain>.com

The output of which follows....
Exim version 4.22 uid=0 gid=0 pid=20959 D=fbb95cfd
Berkeley DB: Sleepycat Software: Berkeley DB 3.2.9: (June 16, 2003)
Support for: iconv() IPv6 PAM Perl GnuTLS
Authenticators: cram_md5 plaintext spa
Routers: accept dnslookup ipliteral iplookup manualroute queryprogram
redirect
Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp
changed uid/gid: forcing real = effective
uid=0 gid=0 pid=20959
auxiliary group list: <none>
configuration file is /var/lib/exim4/config.autogenerated
log selector = 040d99d8
trusted user
admin user
user name "root" extracted from gecos field "root"
originator: uid=0 gid=0 login=root name=root
sender address = root@<mydomain>.com
Address testing: uid=0 gid=8 euid=0 egid=8
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Testing john@<mydomain>.com
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Considering john@<mydomain>.com
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

routing john@<mydomain>.com
--------> dnslookup_relay_to_domains router <--------
local_part=john domain=<mydomain>.com
checking domains
<mydomain>.com in "@:<mydomain>.com:localhost:mail"? yes (matched
"@")
<mydomain>.com in "! +local_domains : +relay_to_domains"? no (matched
"! +local_domains")
dnslookup_relay_to_domains router skipped: domains mismatch
--------> dnslookup router <--------
local_part=john domain=<mydomain>.com
checking domains
cached yes match for +local_domains
cached lookup data = NULL
<mydomain>.com in "! +local_domains"? no (matched "! +local_domains" -
cached)
dnslookup router skipped: domains mismatch
--------> real_local router <--------
local_part=john domain=<mydomain>.com
real_local router skipped: prefix mismatch
--------> system_aliases router <--------
local_part=john domain=<mydomain>.com
R: system_aliases for john@<mydomain>.com
calling system_aliases router
rda_interpret (string): ${lookup{$local_part}lsearch{/etc/aliases}}
search_open: lsearch "/etc/aliases"
search_find: file="/etc/aliases"
key="john" partial=-1 affix=NULL starflags=0
LRU list:
8/etc/aliases
End
internal_search_find: file="/etc/aliases"
type=lsearch key="john"
file lookup required for john
in /etc/aliases
lookup yielded: john@???
expanded: john@???
file is not a filter file
parse_forward_list: john@???
extract item: john@???
system_aliases router generated john@???
errors_to=NULL transport=NULL
uid=unset gid=unset home=NULL
routed by system_aliases router
envelope to: john@<mydomain>.com
transport: <none>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Considering john@???
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

routing john@???
--------> dnslookup_relay_to_domains router <--------
local_part=john domain=otherdomain.com
checking domains
otherdomain.com in "@:<mydomain>.com:localhost:mail"? no (end of
list)
otherdomain.com in ""? no (end of list)
otherdomain.com in "! +local_domains : +relay_to_domains"? no (end of
list)
dnslookup_relay_to_domains router skipped: domains mismatch
--------> dnslookup router <--------
local_part=john domain=otherdomain.com
checking domains
cached no match for +local_domains
cached lookup data = NULL
otherdomain.com in "! +local_domains"? yes (end of list)
calling dnslookup router
dnslookup router called for john@???
  domain = otherdomain.com
DNS lookup of otherdomain.com (MX) succeeded
DNS lookup of smtp2.otherdomain.com (AAAA) gave NO_DATA
returning DNS_NODATA
DNS lookup of smtp2.otherdomain.com (A) succeeded
204.187.144.21 in "0.0.0.0 : 127.0.0.0/8 : 192.168.0.0/16
:172.16.0.0/12 : 10.0.0.0/8 : 169.254.0.0/16"? no (end of list)
DNS lookup of smtp.otherdomain.com (AAAA) gave NO_DATA
returning DNS_NODATA
DNS lookup of smtp.otherdomain.com (A) succeeded
209.87.239.70 in "0.0.0.0 : 127.0.0.0/8 : 192.168.0.0/16
:172.16.0.0/12 : 10.0.0.0/8 : 169.254.0.0/16"? no (end of list)
DNS lookup of smtp3.otherdomain.com (AAAA) gave NO_DATA
returning DNS_NODATA
DNS lookup of smtp3.otherdomain.com (A) succeeded
209.87.239.71 in "0.0.0.0 : 127.0.0.0/8 : 192.168.0.0/16
:172.16.0.0/12 : 10.0.0.0/8 : 169.254.0.0/16"? no (end of list)
fully qualified name = otherdomain.com
host_find_bydns yield = HOST_FOUND (2); returned hosts:
  smtp2.otherdomain.com 204.187.144.21 5
  smtp.otherdomain.com 209.87.239.70 5
  smtp3.otherdomain.com 209.87.239.71 5
set transport remote_smtp
queued for remote_smtp transport: local_part = john
domain = otherdomain.com
  errors_to=NULL
  domain_data=NULL localpart_data=NULL
routed by dnslookup router
  envelope to: john@???
  transport: remote_smtp
  host smtp2.otherdomain.com [204.187.144.21] MX=5
  host smtp.otherdomain.com [209.87.239.70] MX=5
  host smtp3.otherdomain.com [209.87.239.71] MX=5
john@???
    <-- john@<mydomain>.com
  router = dnslookup, transport = remote_smtp
  host smtp2.otherdomain.com [204.187.144.21] MX=5
  host smtp.otherdomain.com  [209.87.239.70]  MX=5
  host smtp3.otherdomain.com [209.87.239.71]  MX=5
search_tidyup called

>>>>>>>>>>>>>>>> Exim pid=20959 terminating with rc=0
>>>>>>>>>>>>>>>>


I have absolutely no problems sending message to any other remote
address, or to another local address that does have a physical
account.

Anything you can think of would help.
Thanks for your input
Regards
Dean

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dean Staff Kanata On. Canada
A+, MCP, MCSA, MCSE, CIW Security Analyst
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~