Re: Alias Problem

Hrm, maybe so... 

But my code matches what you have and doesn't do anything...

In looking at the database schema I have this (I eliminated clearly
unrelated fields):

localpart		myalias,myalias1
username		myalias,[email protected]
smtp			[email protected]
pop			[email protected]
type			alias
admin			0
on_avscan		1
on_blocklist	0
on_complexpass	0
on_forward		0
on_piped		0
on_spamassassin	1
on_vacation		0
enabled		1
flags			NULL
forward		NULL
unseen		0

I don't see anything in the code that takes into account whether the type is
set to alias or not, it only seems to care about the on_forward flag, which
when I set up an alias, is not set.  Is there something wrong with my
database schema then?  The vexim code (php part of things) was pulled
straight from the newest version available on the site.

Torry

-----Original Message-----
From: Avleen Vig [mailto:[email protected]] 
Sent: Sunday, March 29, 2009 10:33 AM
To: [email protected]; [email protected]
Subject: Re: [vexim] Alias Problem

Hi Torry,

It should be handled by the virtual_forward router:

virtual_forward:
  driver = redirect
  check_ancestor
  unseen = ${if eq {${lookup mysql{select unseen from users,domains \
                where localpart = '${quote_mysql:$local_part}' \
                and domain = '${quote_mysql:$domain}' \
                and users.on_forward = '1' \
                and users.domain_id=domains.domain_id}}}{1} {yes}{no}}
  data = ${lookup mysql{select forward from users,domains \
        where localpart='${quote_mysql:$local_part}' \
        and domain='${quote_mysql:$domain}' \
        and users.domain_id=domains.domain_id \
        and on_forward = '1'}}
  # We explicitly make this condition NOT forward mailing list mail!
  condition = ${if and { {!match {$h_precedence:}{(?i)junk}} \
                         {eq {${lookup mysql{select users.on_forward from
users,domains \
                                where localpart =
'${quote_mysql:$local_part}' \
                                and domain = '${quote_mysql:$domain}' \ 
                                and users.on_forward = '1' \
                                and users.domain_id=domains.domain_id}}}{1}
}} {yes}{no} }



On Sat, Mar 28, 2009 at 11:43:06AM -0500, Torry Crass wrote:
> Has anyone else ran into a problem with aliasing.  I've not really tried
to
> mess with it for a long time but I realized very quickly with this recent
> change over that I've made that apparently aliasing doesn't work.
> 
> I've looked through the router config and it appears that there is no
router
> for e-mail aliases.  Does anyone have this code from older versions or
> laying around anywhere?  I've looked in the vexim source all the way back
to
> 1.5 and can't seem to find code which determines how aliased addresses
> should be handled.  Catchall works just fine.
> 
> This is what mainlog in exim4 shows.
> 
> 2009-03-08 23:02:10 1LgWgl-00066S-PH ** [email protected]:
Unrouteable
> address
> 
> Any help would be appreciated.  Thanks!
> 
> ~Torry
> 
> 
> _______________________________________________
> Vexim mailing list
> [email protected]
> http://silverwraith.com/mailman/listinfo/vexim
> 

-- 
Avleen Vig
Systems Administrator
Personal: www.silverwraith.com