Hi,
It seems that fastforward's order for matching appears screwey. It appears
that records in the form "user@" match after the wildcard "@domain" records,
while fully specified "user@domain" records match before the wildcard
"@domain" records. Seems to me that the wild-card records should match last,
after bot the "user@domain" and "user@" records have had a chance to match.
Is there a reason for the way it is, or am I missing something?
Here are the tests that I've done:
The "user@" records match after the wildcard "@domain" records:
-----
[morgan@w1 morgan]$ printforward < .domains.cdb
multiple@:
, &[EMAIL PROTECTED]
, &[EMAIL PROTECTED]
;
@westegg.com:
, &[EMAIL PROTECTED]
;
@westegg2.com:
, &[EMAIL PROTECTED]
;
[morgan@w1 morgan]$ [EMAIL PROTECTED]; export RECIPIENT
[morgan@w1 morgan]$ fastforward -n .domains.cdb
from <original envelope sender>
to <[EMAIL PROTECTED]>
[morgan@w1 morgan]$
-----
Fully specified records "user@domain" do match before the wildcard "@domain"
records:
-----
[morgan@w1 morgan]$ printforward < .domains.cdb
[EMAIL PROTECTED]:
, &[EMAIL PROTECTED]
, &[EMAIL PROTECTED]
;
@westegg.com:
, &[EMAIL PROTECTED]
;
@westegg2.com:
, &[EMAIL PROTECTED]
;
[morgan@w1 morgan]$ [EMAIL PROTECTED]; export RECIPIENT
[morgan@w1 morgan]$ fastforward -n .domains.cdb
from <original envelope sender>
to <[EMAIL PROTECTED]>
to <[EMAIL PROTECTED]>
[morgan@w1 morgan]$
-----
When I remove the wildcard address, the "username@" records work just fine:
-----
[morgan@w1 morgan]$ printforward < .domains.cdb
multiple@:
, &[EMAIL PROTECTED]
, &[EMAIL PROTECTED]
;
[morgan@w1 morgan]$ [EMAIL PROTECTED]; export RECIPIENT
[morgan@w1 morgan]$ fastforward -n .domains.cdb
from <original envelope sender>
to <[EMAIL PROTECTED]>
to <[EMAIL PROTECTED]>
[morgan@w1 morgan]$
-----
- David Harris
Principal Engineer, DRH Internet Services
