1
Domain Alias Event
Question asked by SpamHurts - July 25, 2015 at 8:09 PM
Unanswered
So I have two domains. abc.com and xyz.com. The second is an alias of abc.com. (so abc is the primary.)
 
I am trying to create a rule, and when someone sends email to user1@xyz.com it will "add recipient" and deliever that message also to user2@abc.com
 
In creating the rule, I selected that if the recipient contains the domain xyz.com, the "add recipient" to user2@abc.com. It failed. Then I tried to specify the user, so the rule is, the to field, "contains" user1@xyz.com, then add recipient, user2@abc, and it also failed.
 
So I thought maybe my company disabled events. I have even hear that SM made changes to events, So i did another test.
 
I made a rule that when the message is delivered to user1@abc.com, the "add recipient" to user2@abc.com, and it worked.
 
I tried actually 10 different combinations of the recipient and it just didn't work. If I use the primary domain in the condition of the rule, it works fine, but nothing will work with the aliased domain.
 
Do events not work with an alias?
 
I do not want every message that goes to user1@abc.com to be delivered to user2@abc.com, only the messages that are intended for user1@xyz.com. I know that I could create a unique user (lets call it user3)and use that for xyz.com, and have it be an email alias to user1 and use2, but it really needs to be the same user name, user1. Any suggestions.
 
 
Remember kids, every time a spam message gets blocked, a nerd gets their glasses. spamhurts/July 15

3 Replies

Reply to Thread
0
SpamHurts Replied
July 29, 2015 at 4:44 PM
Bump: anyone?
Remember kids, every time a spam message gets blocked, a nerd gets their glasses. spamhurts/July 15
0
SpamHurts Replied
August 22, 2015 at 9:29 PM
Bump: anyone?
Remember kids, every time a spam message gets blocked, a nerd gets their glasses. spamhurts/July 15
0
Robert Emmett Replied
August 25, 2015 at 12:41 PM
Employee Post
SpamHurts, I was able to successful accomplish your scenario using two different methods:
 
1. Set up a server event.  You cannot create a domain event or user event to handle this.  These latter two event types add a "To Domain" condition (abc.com) that will fail if the message if is sent to (xyz.com).  However, setting up the event at the server level, you can specify or omit the "To Domain" condition.
 
2. Set up a domain level content filtering.  I used "Copy To" in replace of "Add Recipient"
 
Using either of those methods properly added "user2@abc.com" as a recipient whenever "user1@xyz.com" received a message.  Hopefully, this helps.
Robert Emmett
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com

Reply to Thread