Messaging Gateway

Hello,

My case is:
Aliase: a@company.com
emails address: a@company.com, b@hotmail.com

the result is: the email can only be deliveried to b@hotmail.com

if emails address is change to "c@gmail.com, b@hotmail", the email can be delivered to c and b.

Can't set this config at Brightmail? This config is work at Mail Security....

From pages 222-223 of the administrator's guide:

Inbound address masquerading has precedence over aliases. If the same original
email address or domain exists in both the address masquerading list and the
aliases list, but the new address or domain is different, the message is routed
to the new address or domain in the address masquerading list, not the aliases
list.

In this situation, you would want to consider making a compliance rule to accomplish this since one of the actions you can use is "Forward a copy of the message."

Here is a link to the administrator's guide if you need help making a compliance policy:

ftp://ftp.symantec.com/public/english_us_canada/products/symantec_mail_security/8200_8300_series/manuals/sms_administration_guide.pdf

NO....
My masquerading list is empty....

And i check the guide, it never said alias's destination address can't be as same as source address, example, source: "a@company.com" and destination: "a@company.com", "b@hotmail.com".

Try changing one of the letters in the address to be aliased to to uppercase. The Brightmail software can't alias an address to itself in version 8.


Title: 'Message rejected by MTA due to alias transformation'
Document ID: 2009042211325354
> Web URL: http://service1.symantec.com/SUPPORT/ent-gate.nsf/docid/2009042211325354?Open&seg=ent

Your solution is not work...

And the Document's solution is not solution, it just tell me not to use it.

Will symantec fix it?

As I said before, you should not be trying to accomplish this sort of thing with an alias, you should be able to do this with a compliance policy. I do not have confirmation at this time that we are going to change this behaviour in a future release.

Hi,

This is how it works. An alias translates one address into one or more destination addresses by rewriting the inbound recipient's envelope address.
So "a" can be translated into "b" but same source and destination will not work.

- a to b & c = b & c

- a to a & b =  b

Regards,

Federico

As I have more than 100 aliases, it does not make sense to create compliance policy one by one.....

If Aliase can't tanslate to sourse address, it should not allow people to configure it from Mail Security version. (And in SBG guide, I can't find a word which mention I can't do it ..)

Now, I feel symantec trapped users into using it....

I am sorry you feel that way. We offer all of our latest versions of the brightmail product as a 30-day trial so there is no reason this should be a suprise. This is not something that people normally do. You are more than welcome to submit an Idea to the forums here and our engineers will look at that. They are working hard on version 9 and will be offering up a beta soon. You should also join that if possible, here is the information for that:

https://www-secure.symantec.com/connect/blogs/brightmail-gateway-90-beta