Rewrite Rules with Domain Alias

Version:
iPlanet Messaging Server 5.2 HotFix 2.03 (built Nov 22 2004)
libimta.so 5.2 HotFix 2.03 (built 13:20:08, Nov 22 2004)
I am hosting 1 domain with an domain alias for the same hosted domain.
I would like all mail coming in as domain A to be rewritten as domain B. Same for all outgoing mail outgoing as domain A to rewritten as domain B
What should my rewrite rules look like?
domain.a $U%domain.b

That makes senses. I am using mailequivalentaddress with a domain alias. I also have the following rule in my imta.cnf:
domain.A $R$U%domain.B
domain.A $U%domain.B
There rewrites all of the mailheaders but I noticed the the envelope headers are not rewritten. Is it a good idea to rewrite the envelope headers although the domain beinging rewritten to is an alias? The mail headers on the to: and from: address are rewritten as domain.B but envelope headers show [email protected] for delivery.

Similar Messages

Apache rewrite rule working with whitespaces in portal URL

Hello,
we have a portal with several page groups. These are accessed through different virtual hosts in Apache. The rewrite rules look like:
RewriteRule ^/website1(.*)$ /portal/page/portal/website1/$1 [PT]
The problem is, it does not work when there is more than one space in URL (fe.: website1/subpage 1/subpage 2). The result is http error 413.
I guess, it is related to PT flag and escaping URI.
RewriteRule flag B would probably do the trick, but it is available in Apache 2.2 only.
We have tried following, as well:
RewriteMap escapemap int:escape
RewriteRule ^/website1(.*)$ /portal/page/portal/website1/${escapemap:$1} [PT]
That works for any number of spaces! On the other hand side, it does not work for Czech (accented; URI escaped) characters any more. :-(
Does anyone have a working rewrite rule? Any hints?
Thank you!
ViNiL

Hi Pratap
Check SAP Note 698329 this note give details for logon fails
U Need to enable SAPGUI for html
goto se80 give internet services (in the drop down box)
Below drop down give SYSTEM publish these service by right clicking system publish--complete service.
and also publish same way WEBGUI
and also enter ur server ip address and hostname in C:\WINDOWS\system32\drivers\etc-->hosts
Hope this helps you.
Regards
Krishna.

Still about domain alias and domain migration

Our company is under a domain name transition. Currently, our domain is lab.D.com, and we are moving to aaa.com.During the transition, we wish both domains could work for us for a long time.
I added a domain alias aaa.com for our domain lab.D.com, the ldif shows:
dn: dc=aaa, dc=com, o=internet
objectclass: alias
objectclass: inetDomainAlias
aliasedObjectName: dc=lab, dc=D, dc=com, o=internet
dc: aaa
after restarting msg server, I can send email to [email protected] which is acutually [email protected]
However, this is only half-way to my goal. I wish our emails at receivers' mailboxes were [email protected], not [email protected], if we send emails though loging in web mail typing [email protected] in the user ID box, or by creating [email protected] accounts in MS Outlook.
===> Is there any way to do it?
===> can [email protected] account be created in MS Outlook?
In another post about domain migration, you suggested:
If you want to stop using the old domain, and make the new domain your "default domain", that's a little harder. It involves several steps:
1. changing all the mail addresses.
2. changing the "default domain" settings everywhere.
===> I wonder, how to do it? is there any command? ldapmodify?
as an alternative approach, if we decide to change our email addresses to [email protected] first,
===> will emails sending to either [email protected] or [email protected] arrive at users who are still in the lab.D.com, if I only change all the mail addresses' domian part to aaa.com since I have added domain alias aaa.com?
and, I do not think sending emails from [email protected] to the internet would be a problem, right???
The iMS we use is iPlanet Messaging Server 5.2 (built Feb 21 2002), Directory Server is 4.16 which are very old versions :(
Thanks.

I make no claim to be a programmer, nor am I expert
with ldap commands.
I know of no easy way to change all, other than
export to ldif, and use a global change with a text
editor, and then re-import.So, db2ldif -> change in text editor -> ldif2db, right?
Another question here is about Direct LDAP.
I enabled Direct LDAP.
aaa.com is the domain alias to lab.oldD.com (our old domain).
I also have changed user alas' email addresss from alas@ lab.oldD.com to [email protected] and added mailAlternateaddress for alas as [email protected], as you instructed in previous posts.
However, whenever I click "send" either to aaa.com or lab.oldD.com, it shows errors, for examples, - "Returning unknown or illegal alias: [email protected]", "Returning unknown or illegal alias: [email protected]"
The log shows:
19:17:27.62: mmc_address_to_tree: Parsing address.
19:17:27.62: Address: "user@[127.0.0.1]" 0x00000000
19:17:27.62: Right default: honey.lab.oldD.com
19:17:27.62: Parsing address with null fixup.
19:17:27.62: mmc_address_to_tree: Returning.
19:17:27.62: Rewriting: Mbox = "user", host = "[127.0.0.1]", domain = "$*", literal = "", tag = ""
19:17:27.62: Rewrite: "$*", position 0, hash table -
19:17:27.62: Found: "$E$F$U%[email protected]"
// honey is our email server
19:17:27.62: Rewrite failed, not forward.
19:17:27.62: Rewrite: "$*", position 1, hash table -
19:17:27.62: Failed.
19:17:27.62: Rewrite: "$*", position 0, rewrite database -
19:17:27.62: Failed
19:17:27.62: Rewriting: Mbox = "user", host = "[127.0.0.1]", domain = "[127.0.0.1]", literal = "", tag = ""
19:17:27.62: Rewrite: "[127.0.0.1]", position 0, hash table -
19:17:27.62: Failed
19:17:27.62: Rewrite: "[127.0.0.1]", position 0, hash table -
19:17:27.62: Failed.
19:17:27.62: Rewrite: "[127.0.0.1]", position 0, rewrite database -
19:17:27.62: Failed
19:17:27.62: Rewriting: Mbox = "user", host = "[127.0.0.1]", domain = "[127.0.0.]", literal = "1", tag = ""
19:17:27.62: Rewrite: "[127.0.0.*]", position 0, hash table -
19:17:27.62: Failed
19:17:27.62: Rewrite: "[127.0.0.]", position 0, hash table -
19:17:27.62: Failed.
19:17:27.62: Rewrite: "[127.0.0.]", position 0, rewrite database -
19:17:27.62: Failed
19:17:27.62: Rewriting: Mbox = "user", host = "[127.0.0.1]", domain = "[127.0.]", literal = "0.1", tag = ""
19:17:27.62: Rewrite: "[127.0.*.*]", position 0, hash table -
19:17:27.62: Failed
19:17:27.62: Rewrite: "[127.0.]", position 0, hash table -
19:17:27.62: Failed.
19:17:27.62: Rewrite: "[127.0.]", position 0, rewrite database -
19:17:27.62: Failed
19:17:27.62: Rewriting: Mbox = "user", host = "[127.0.0.1]", domain = "[127.]", literal = "0.0.1", tag = ""
19:17:27.62: Rewrite: "[127.*.*.*]", position 0, hash table -
19:17:27.62: Failed
19:17:27.62: Rewrite: "[127.]", position 0, hash table -
19:17:27.62: Failed.
19:17:27.62: Rewrite: "[127.]", position 0, rewrite database -
19:17:27.62: Failed
19:17:27.62: Rewriting: Mbox = "user", host = "[127.0.0.1]", domain = "[]", literal = "127.0.0.1", tag = ""
19:17:27.62: Rewrite: "[]", position 0, hash table -
19:17:27.62: Found: "$E$R${INTERNAL_IP,$L}$U%[$L]@tcp_intranet-daemon"
19:17:27.62: Mapping: name = "INTERNAL_IP", input = "127.0.0.1".
19:17:27.62: Mapping 2 applied to 127.0.0.1
19:17:27.62: Entry #2 matched, pattern "127.0.0.1", template "$Y", match #0.
19:17:27.62: New target ""
19:17:27.62: Exiting...
19:17:27.62: Final result ""
19:17:27.62: Mapping result:
19:17:27.62: New mailbox: "user".
19:17:27.62: New host: "[127.0.0.1]".
19:17:27.62: New route: "tcp_intranet-daemon".
19:17:27.62: New channel system: "tcp_intranet-daemon".
19:17:27.62: Looking up host "tcp_intranet-daemon".
19:17:27.62: - found on channel tcp_intranet
19:17:27.62: mmc_winit('tcp_intranet','[email protected]','') called.
19:17:27.62: mmc_determine_url beginning with pattern , xadr , mbox , subaddress
19:17:27.62: Queue area size 18871794, temp area size 18871794
19:17:27.62: 4717948 blocks of effective free queue space available; setting d
isk limit accordingly.
19:17:27.62: mmc_address_to_tree: Parsing address.
19:17:27.62: Address: "[email protected]" 0x00000000
19:17:27.62: Right default: lab.oldD.com
19:17:27.62: Parsing address with local fixup.
19:17:27.62: mmc_address_to_tree: Returning.
19:17:27.62: Rewriting: Mbox = "alas", host = "newD.com", domain = "$*", literal
= "", tag = ""
19:17:27.62: Rewrite: "$*", position 0, hash table -
19:17:27.62: Found: "$E$F$U%[email protected]"
19:17:27.62: Rewrite failed, not forward.
19:17:27.62: Rewrite: "$*", position 1, hash table -
19:17:27.62: Failed.
19:17:27.62: Rewrite: "$*", position 0, rewrite database -
19:17:27.62: Failed
19:17:27.62: Rewriting: Mbox = "alas", host = "newD", domain = "newD.com", litera
l = "", tag = ""
19:17:27.62: Rewrite: "newD.com", position 0, hash table -
19:17:27.62: Failed.
19:17:27.62: Rewrite: "newD.com", position 0, rewrite database -
19:17:27.62: Failed
19:17:27.62: Rewriting: Mbox = "alas", host = "newD", domain = ".com", literal =
"", tag = ""
19:17:27.62: Rewrite: "*.com", position 0, hash table -
19:17:27.62: Failed
19:17:27.62: Rewrite: ".com", position 0, hash table -
19:17:27.62: Found: "$U%$H$D@TCP-DAEMON"
19:17:27.62: New mailbox: "alas".
19:17:27.62: New host: "newD.com".
19:17:27.62: New route: "TCP-DAEMON".
19:17:27.62: New channel system: "TCP-DAEMON".
19:17:27.62: Looking up host "TCP-DAEMON".
19:17:27.62: - found on channel tcp_local
19:17:27.62: mmc_address_to_tree: Parsing address.
19:17:27.62: Address: "[email protected]" 0x00000000
19:17:27.62: Right default: lab.oldD.com
19:17:27.62: Parsing address with null fixup.
19:17:27.62: mmc_address_to_tree: Returning.
19:17:27.62: Rewriting: Mbox = "alas", host = "newD.com", domain = "$*", literal
= "", tag = ""
19:17:27.62: Rewrite: "$*", position 0, hash table -
19:17:27.62: Found: "$E$F$U%[email protected]"
19:17:27.62: Rewrite failed, not forward.
19:17:27.62: Rewrite: "$*", position 1, hash table -
19:17:27.62: Failed.
19:17:27.62: Rewrite: "$*", position 0, rewrite database -
19:17:27.62: Failed
19:17:27.62: Rewriting: Mbox = "alas", host = "newD", domain = "newD.com", litera
l = "", tag = ""
19:17:27.62: Rewrite: "newD.com", position 0, hash table -
19:17:27.62: Failed.
19:17:27.62: Rewrite: "newD.com", position 0, rewrite database -
19:17:27.62: Failed
19:17:27.62: Rewriting: Mbox = "alas", host = "newD", domain = ".com", literal =
"", tag = ""
19:17:27.62: Rewrite: "*.com", position 0, hash table -
19:17:27.62: Failed
19:17:27.62: Rewrite: ".com", position 0, hash table -
19:17:27.62: Found: "$U%$H$D@TCP-DAEMON"
19:17:27.62: New mailbox: "alas".
19:17:27.62: New host: "newD.com".
19:17:27.62: New route: "TCP-DAEMON".
19:17:27.62: New channel system: "TCP-DAEMON".
19:17:27.62: Looking up host "TCP-DAEMON".
19:17:27.62: - found on channel tcp_local
19:17:27.62: Mapped return address: [email protected]
19:17:27.62: mmc_rrply: Return detailed status information.
19:17:27.62: mmc_rrply: Returning return address and channel OK
19:17:27.62: mmc_wadr(0x001abd40,'','[email protected]') called.
19:17:27.62: Copy estimate before address addition is 1
19:17:27.62: Parsing address [email protected]
19:17:27.62: mmc_address_to_tree: Parsing address.
19:17:27.62: Address: "[email protected]" 0x00000000
19:17:27.62: Right default: lab.oldD.com
19:17:27.62: Parsing address with local fixup.
19:17:27.62: mmc_address_to_tree: Returning.
19:17:27.62: Rewriting: Mbox = "alas", host = "lab.oldD.com", domain = "$*", l
iteral = "", tag = ""
19:17:27.62: Rewrite: "$*", position 0, hash table -
19:17:27.62: Found: "$E$F$U%[email protected]"
19:17:27.62: Match, pattern = "lab.oldD.com", current = "(*domaincheck*)"
19:17:27.62: old state = not checked.
19:17:27.62: Performing domainMap check on lab.oldD.com.
19:17:27.62: Added domainMap result 1 to cache for lab.oldD.com.
19:17:27.62: new state = succeeded.
19:17:27.62: New mailbox: "alas".
19:17:27.62: New host: "lab.oldD.com".
19:17:27.62: New route: "honey.lab.oldD.com".
19:17:27.62: New channel system: "honey.lab.oldD.com".
19:17:27.62: Looking up host "honey.lab.oldD.com".
19:17:27.62: - found on channel l
19:17:27.62: Routelocal flag set; scanning for % and !
19:17:27.62: Address [email protected] requires local processing.
19:17:27.62: Variant #1 = [email protected]
19:17:27.62: Variant #2 = *@lab.oldD.com
19:17:27.62: Checking for [email protected] in the system alias file
19:17:27.62: - not found
19:17:27.62: Checking for *@lab.oldD.com in the system alias file
19:17:27.62: - not found
19:17:27.62: - adding address [email protected] to headers.
19:17:27.62: Copy estimate after address addition is 1
19:17:27.63: mmc_rrply: Return detailed status information.
19:17:27.63: mmc_rrply: Returning unknown or illegal alias: [email protected]
I wonder why?
Thanks.

Setting up a Mail domain Alias

Hi
We are trying to set up a mail domain alias so that a user can receive mails on either [email protected] or [email protected], the default mail domain on which OCS has been installed is domainA.com
I've tried the rewrite rules for inbound SMTP as:
Pattern To Match
$[email protected]
Action
Apply Rewrite
Rewrite To Apply
$[email protected]
But it does not seem to work (I'm just not receiving any test mails and don't know where we can check for logs for any discarded mails)
Is there any simple way to set up this 'maildomain alias'?
Many thanks for your assistance
Rgds
Vicky

Marc,
In this situation, I think you only need to add the additional addresses, into the Email Address entry box in Mail Preferences/Accounts/Account Information. You put a comma after the existing address, and add another. Put a comma after the new, one, and you can add still another.
http://docs.info.apple.com/article.html?artnum=302215
and
http://docs.info.apple.com/article.html?path=Mail/2.0/en/ml1019.html
You will need to be sure to select the correct one, in each reply or new message. The latter link is also found in Mail Help.
Does this fulfill your need?
Ernie

LDAP Auth Rewrite Rule in Mapping file

Hi,
We are trying to set LDAP Auth Rewrite rule in mapping file to get users First Name & Last Name or Display name & Mail Address from LDAP Server instead of users individual client settings.
In Messaging 5.2 we had the follwoing setting, but it does not work any more for Messaging 6.2:
LDAP Auth Rewrite Entry in mapping file:
AUTH_REWRITE
*|*|*|*@* $]ldap:///dir1.domain.com:389/o=domain.com?cn?sub?(uid=$3)[$ <$]ldap:///dir1.domain.com:389/o=domain.com?mail?sub?(uid=$3)[>$Z
We are running:
Sun Java(tm) System Messaging Server 6.2-3.04 (built Jul 15 2005)
libimta.so 6.2-3.04 (built 01:43:03, Jul 15 2005)
SunOS mta 5.10 Generic_118833-03 sun4u sparc SUNW,Sun-Fire-V240
ll appreciate for any help or clue
Thanks

Thanks Jay,
Well, here is what we want to achieve.
We are looking for re-writing the FROM address of Sender against the LDAP Entry as cn <[email protected]>. This should solve problem of where users have entered wrong FROM information on their clients or trying to spoof FROM address to other users.
Currently, The system delivers e-mail with FROM headers as per client entry instead of re-writing it against AUTHENTICATED userid.
Following is the IMTA.CNF and MAPPINGS lines:
IMTA.CNF
! ims-ms
ims-ms defragment subdirs 20 notices 1 3 backoff "pt5m" "pt10m" "pt30m" "pt1h" "pt2h" "pt4h" maxjobs 2 pool IMS_POOL fileinto
$U+$S@$D
! tcp_local
tcp_local smtp mx single_sys remotehost inner switchchannel identnonenumeric subdirs 20 maxjobs 7 pool SMTP_POOL maytlsserver
maysaslserver saslswitchchannel tcp_auth missingrecipientpolicy 0 mailfromdnsverify dropblank vrfyhide
! tcp_intranet
tcp_intranet smtp mx single_sys subdirs 20 dequeue_removeroute maxjobs 7 pool SMTP_POOL maytlsserver allowswitchchannel sasls
witchchannel tcp_auth missingrecipientpolicy 4 mailfromdnsverify dropblank vrfyhide
! tcp_extranet
tcp_extranet smtp mx single_sys subdirs 20 noreverse maxjobs 7 pool SMTP_POOL mustsaslserver allowswitchchannel saslswitchcha
nnel tcp_auth vrfyhide dropblank mailfromdnsverify dropblank missingrecipientpolicy 4
! tcp_submit
tcp_submit submit smtp mx single_sys mustsaslserver maytlsserver missingrecipientpolicy 4
! tcp_auth
tcp_auth smtp mx single_sys mustsaslserver missingrecipientpolicy 4 authrewrite 3
MAPPINGS file
AUTH_REWRITE
*|*|*|*@* $]ldap:///dir.domain.edu:389/o=domain.edu,dc=domain,dc=edu?cn?sub?(uid=$3)[$ <$]ldap:///dir.domain.edu:389
/o=domain.edu,dc=domain,dc=edu?mail?sub?(uid=$3)[>$Z
Thanks for your help

I have created URL like sub domain. but URL which i have rewrite like sub-domain in that page This webpage is not available error showing.

Is that any one Help me, here,
i have created URL like aarti.domain.com using a particular code which i have add here,
sub-domain URL is creating but This webpage is not available i am getting this error in sub-domain URL page.
This is a code by which i have created a URL like sub-domain. its creating URL but page is not showing with data.
Any one can tell me whats Wrong here.
and how i can show data in my sub-domain url.
Your solution will help me To solve This Big Issue.
<rewrite>
<rules>
<rule name="Redirect to Subdomains" stopProcessing="true">
<match url="^xyzPage.aspx$" />
<conditions>
<add input="{QUERY_STRING}" pattern="^barvalue=(.+)$" />
</conditions>
<action type="Redirect" url="http://{C:1}.{HTTP_HOST}" appendQueryString="false" />
</rule>
</rules>
</rewrite>

Please post questions related to ASP.NET and web development in the ASP.NET forums (http://forums.asp.net ).

Rewrite rule and dinamic group

I have put the rewrite rule
domain.com $A$E$F$[email protected]
In Java Enterprise System.
This way, mails send to or from [email protected] are routed to mailhost and that is ok, but when I send a mail to a dinamic group, the message is not sent.
the command imsimta test -rewrite [email protected] reports this at the end:
Address list error -- 5.1.1 unknown or illegal alias: [email protected]
What could be happening?
Thanks,

Your original rule is not the best way to go about routing to "domain.com"
I would start by removing that rule.
Then I would look at what you're really trying to do, here.
If you're trying to route mails to users that are in your ldap server, then they should be automatically routed, based on the value of "mailhost" you're put in for them.
If you're trying to route users that are not in your ldap, then you need to create a
domain smarthost
documentation in our provisioning guide, here:
http://docs.sun.com/source/816-6018-10/domains.htm#29147
Using rewrite rules for routing outside the MTA is a Bad Idea, as you've found.

Changing sender email address via rewriting rules

My objective is to change my sender email address. For example, suppose my OCS email address is [email protected] and I would to send an email to [email protected]
John logs into yahoo mail and would see my mail. Upon opening my email, I would like John to see that the sender email address to be [email protected] so that whenever John replies my mail, the replied mail would go to [email protected] and not to [email protected]
I read the email admin guide and I configure the Sender rewriting rules within SMTP_OUT. I have key in the following within the Sender rewriting rules: $*@test.abc.com.my,$[email protected]
I restart the SMTP_OUT services and I check the log files in MIDTIER_HOME/oes/log/um_system/SMTP_OUT/12345
I found out that the rewriting rules have take effect on one of the lines.
Then I log into OCS as user Andrew with test.abc.com.my domain and send an email to yahoo.
I open my yahoo mail, which I receive the email.
However the sender email address remains unchanged which is [email protected]
How can I change the sender email domain?
thanks;
andrew

Your observation is very correct in terms of symptoms, not of behaviour. We have numerous ER's there enabling header rewriting, too. Obviously for you, envelope rewriting works well, without to achieve the target you want to address. Please forward your request to Support Services with an Enhancement Request for native header rewriting.
Otherwise 3 ways:
1 Milter C-SDK
2 Milter general
3 relay accomplishing this task.
On 2,3 we have samples ready, for 3 in particular for postfix.

Rewrite rules: how to forward all mails to the specific channel?

I have written an anti-virus plugin using the MTA SDK. Now I want to forward all the incoming messages to the channel, which is 'guarded' by my program (so my program is the channel's master).
I've added following to the end of imta.cnf, according to MTA SDK example:
! kav
x-kav master_debug logging
x-kav-daemon
And at the beginning of imta.cnf:
avp.ru $U%avp.ru@x-kav-daemon$Nx-kav
avp.ru $[email protected]
In this configuration, any incoming mail just miss my channel completely.
I changed it to this one:
$* $U%avp.ru@x-kav-daemon$Nx-kav
<2nd line removed>
in this case, mail is sent to our channel, but has host part '$*', and the message is failed to enqueue.
Also, it seems like this reqrite entry conflicts with ours:
! Rules to select local users
$* $A$E$F$U%$H$V$[email protected]
ultra5.avp.ru $U%$[email protected]
avp.ru $U%$[email protected]
As I understand, according to these rules, everything goes to @avp.ru or @ultra5.avp.ru goes to the local delivery channel ultra5.avp.ru. This is not what I want.
So, the questions are:
1. How to move all the messages (or just messages. which matched the specific domain) into my channel?
2. How to configure rewrite rules, so the message can leave the channel after processing, and continue the routing?

Still doesn't work.
We've downloaded and installed patch 116568-52, and configured the channels:
tcp_local aliasdetourhost tcp_scan smtp mx single_sys remotehost inner switchchannel identnonenumeric subdirs 20 maxjobs 7 pool SMTP_POOL maytlsserver maysaslserver saslswitchchannel tcp_auth missingrecipientpolicy 0
tcp-daemon
! tcp_intranet
tcp_intranet aliasdetourhost tcp_scan smtp mx single_sys subdirs 20 dequeue_removeroute maxjobs 7 pool SMTP_POOL maytlsserver allowswitchchannel saslswitchchannel tcp_auth missingrecipientpolicy 4 tcp_intranet-daemon
tcp_scan smtp mx single_sys subdirs 20 noreverse maxjobs 7 pool SMTP_POOL dequeue_removeroute
tcp_scan
After sending the message, it silently goes to tcp_scan channel, and handled by channel master program. After that the message stays in tcp_scan queue forever, with HELD extension.
Our channel master enqueues the processed message into the channel where it dequeues it, so the message seems to be looped. Here is the message:
t;1093881341
p;3
*;4
u;mailsrv
c;tcp_scan
s;tcp_scan.ultra5.avp.ru
n;f
h;<[email protected]>
m;[email protected]
d;20
j;rfc822
f;[email protected]
@tcp_scan:[email protected]
..Boundary_(ID_+ko348xG8vRKcadifuDhJg)
Received: from tcp_scan.ultra5.avp.ru by ultra5.avp.ru
(Sun Java System Messaging Server 6.1 HotFix 0.01 (built Jun 24 2004))
id <[email protected]> for [email protected] (ORCPT [email protected]
30 Aug 2004 19:55:41 +0400 (MSD)
Received: from tcp_scan.ultra5.avp.ru by ultra5.avp.ru
(Sun Java System Messaging Server 6.1 HotFix 0.01 (built Jun 24 2004))
id <[email protected]> for [email protected] (ORCPT [email protected]
30 Aug 2004 19:55:41 +0400 (MSD)
Received: from tcp_scan.ultra5.avp.ru by ultra5.avp.ru
(Sun Java System Messaging Server 6.1 HotFix 0.01 (built Jun 24 2004))
id <[email protected]> for [email protected] (ORCPT [email protected]
30 Aug 2004 19:55:41 +0400 (MSD)
Received: from tcp_scan.ultra5.avp.ru by ultra5.avp.ru
(Sun Java System Messaging Server 6.1 HotFix 0.01 (built Jun 24 2004))
id <[email protected]> for [email protected] (ORCPT [email protected]
30 Aug 2004 19:55:41 +0400 (MSD)
Received: from tcp_scan.ultra5.avp.ru by ultra5.avp.ru
(Sun Java System Messaging Server 6.1 HotFix 0.01 (built Jun 24 2004))
id <[email protected]> for [email protected] (ORCPT [email protected]
30 Aug 2004 19:55:40 +0400 (MSD)
Received: from tcp_scan.ultra5.avp.ru by ultra5.avp.ru
(Sun Java System Messaging Server 6.1 HotFix 0.01 (built Jun 24 2004))
id <[email protected]> for [email protected] (ORCPT [email protected]
30 Aug 2004 19:55:40 +0400 (MSD)
Received: from tcp_scan.ultra5.avp.ru by ultra5.avp.ru
(Sun Java System Messaging Server 6.1 HotFix 0.01 (built Jun 24 2004))
id <[email protected]> for [email protected] (ORCPT [email protected]
30 Aug 2004 19:55:40 +0400 (MSD)
Received: from tcp_scan.ultra5.avp.ru by ultra5.avp.ru
(Sun Java System Messaging Server 6.1 HotFix 0.01 (built Jun 24 2004))
id <[email protected]> for [email protected] (ORCPT [email protected]
30 Aug 2004 19:55:40 +0400 (MSD)
Received: from tcp_scan.ultra5.avp.ru by ultra5.avp.ru
(Sun Java System Messaging Server 6.1 HotFix 0.01 (built Jun 24 2004))
id <[email protected]> for [email protected] (ORCPT [email protected]
30 Aug 2004 19:55:40 +0400 (MSD)
Received: from tcp_scan.ultra5.avp.ru by ultra5.avp.ru
(Sun Java System Messaging Server 6.1 HotFix 0.01 (built Jun 24 2004))
id <[email protected]> for [email protected] (ORCPT [email protected]
30 Aug 2004 19:55:40 +0400 (MSD)
Received: from tcp_scan.ultra5.avp.ru by ultra5.avp.ru
(Sun Java System Messaging Server 6.1 HotFix 0.01 (built Jun 24 2004))
id <[email protected]> for [email protected] (ORCPT [email protected]
30 Aug 2004 19:55:40 +0400 (MSD)
Received: from localhost.localdomain ([172.16.0.35])
by ultra5.avp.ru (Sun Java System Messaging Server 6.1 HotFix 0.01 (bu
24 2004)) with ESMTP id <[email protected]> for test@avp.
(ORCPT [email protected]); Mon, 30 Aug 2004 19:55:39 +0400 (MSD)
Content-return: allowed
Date: Mon, 30 Aug 2004 19:55:39 +0400 (MSD)
Date-warning: Date header was inserted by ultra5.avp.ru
From: [email protected]
Subject: sent on Mon Aug 30 19:58:29 2004
To: Undisclosed recipients: ;
Message-id: <[email protected]>
..Boundary_(ID_+ko348xG8vRKcadifuDhJg)
How to avoid this loop? Should our master enqueue the processed messages into another channel? If yes, what channel should we enqueue to? If no, how to avoid this loop?

Create domain alias

I created domain alias using the following LDIF sentences:
A:
dn: dc=b, dc=a, dc=com, dc=cn, o=internet
changetype: add
objectclass: alias
objectclass: inetDomainAlias
aliasedObjectName: dc=x, dc=y, dc=com, o=internet
dc:b
Later, I also tried B::
dn: dc=b.a.com.cn, o=internet
changetype: add
objectclass: alias
objectclass: inetDomainAlias
aliasedObjectName: dc=x, dc=y, dc=com, o=internet
dc:b.a.com.cn
it seemed both works.
I wonder which way is right?
or, when should I use which?
thanks.

Let me clarify over the previous clarification:
my goal:
A. When users send emails to internal addresses
([email protected] and [email protected]), the senders' addresses
should be looks like [email protected] or
[email protected] at the recipients' mailboxes, in
another word, the "from" section of the email.
And,
B. When users send emails to external addresses
including [email protected] and other
address, e.g. [email protected], "from" sections of
senders' emails should be like [email protected], or
[email protected]
That is, users from the Internet will only see the [email protected]/[email protected] address.
>
So,
What I am thinking is:
1. apply rewrite rule at tcp_local to rewite the
"from" section of emails sent to the Internet
2. create domain alias b.a.com.cn and c.b.a.com.cn
for x.com and y.x.com respectly.
So emails sent to [email protected]/[email protected] will be delivered to [email protected]/[email protected]
>
I do not think I need to add mailalternateaddress to
each user's defination in ldif. Right?
Would this work?
Thanks.Thank you.

Rewrite Rules for Active X

I would like write rewriting ruleset for an ActiveX application... this the html
<object width=100% height=100% classid="CLSID:1EE104B2-B32A-43d2-8DF1-2FD84BD00B14"
codebase="/wi/ActiveX/WIPanelXIT.cab#Version=5,1,4,33">
<param name=Cookie value="ITwGzbHZkSQT0">
<param name=CacheKey value="c0">
<param name=RepositoryID value="13">
<param name=UniverseName value="Extracom">
<param name=UniverseID value="70">
<param name=HostURL value="/wi/bin/iswi.dll">
<param name=ResultsPageURL value="http://mydomain/docViewFrameTop.asp">
<param name=AllowRefresh value="-1">
<param name=AllowLOVRefresh value="-1">
<param name=AllowViewSQL value="-1">
<param name=AllowDrill value="-1">
</object>
I need that the gateway rewrites only the parameters ResultsPageURL and HostURL. The rewrite is applied only to the tag codebase.
With Portal Sun 3.0 I have implemented the rules but the ActiveX application doesn't work. Someone have a similar problem with ActiveX? Any suggestion?
Thank you in advance.
Best Regards
Fausto

Thanks a lot Jay. Everything is working fine.
I managed to make things work following your advice but without calling tech support.
I am using mailEquivalentAddress attributes for users with domain.nl addresses. In our case, some users have domain.com AND domain.nl addresses while others only have the domain.com.
All rewriting works like a charm. I have set up noreverse on channels to forbid rewriting of "from" addresses, and the mailEquivalentAddress attributes deny rewriting of the "to" when mail is sent to these particular users.
Could you explain why the noreverse is discouraged? Would there be a rewriting rule that would do the same?
I can see reasons why not having rewriting would be an issue. If I find a solution to not having something as "strict" as the noreverse, I will indeed go in that direction.
Thanks again for your help.
Hyde

URL Rewrite Rule: HTTP to HTTPS Not Working

Here is my problem. I cannot get HTTP to HTTPS redirect to work using the URL Rewrite module. I am using version 2, by the way, which I understand is the latest version. I've also enabled the "Proxy Server" and Application Request Routing"
features.
I've trolled through the Internet for 2 days now for solutions to my problem, including the ones provided by the TechNet forums and by MVP Scott Forsyth. I've tried over 30 solutions, and none have resolved my issue. Granted some of the solutions I've tried
may have been repeats of others. After trying so many, I have had a hard time discerning the differences. Does it really matter, for instance if the pattern match for the {HTTPS} input is specified as
"^off$" or just "off"? I see this discrepancy (among others) everywhere. It seems like there are so many variations out there. It is quite confusing for the uninitiated and the newbies like myself to the
URL Rewrite technology. I have enabled and consulted my "Failed Request Tracing Rules" logs but cannot make any sense of the cryptic information it is providing.
I just cannot get my reverse proxy server to redirect http requests from the Internet to https to my internal web server. When a user specifies "https://server1.xxxxx.com". he is able to access the internal server via the reverse proxy (IIS) server.
But when he specifies "http://server1.xxxxx.com" he receives "Server Error 500 - Internal server error.There is a problem with the resource you are looking for, and it cannot be displayed."
At this point I am at my wits end, and am even considering configuring the protocol translation on our firewall. But this not my preference as it presents another layer of complexity, and device to troubleshoot later on. Below I've pasted my entire web.config
file with my most current version of the rule in question (in bold) for your review. I started to paste just the specific rule, but thought you might need to see the entire file in case something else may be conflicting with the rule.
Thank you in advance for your help.
Dave Robinson
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.webServer>
        <rewrite>
              <rules>
                <clear />
<rule name="HTTP to HTTPS Redirect" enabled="true" stopProcessing="true">
                <match url="(.*)" />
             <conditions>
                  <add input="{HTTPS}" pattern="off" />
                </conditions>
                  <action type="Redirect" url="https://{HTTP_HOST}/{REQUEST_URI}" redirectType="Found" />
          </rule>
<rule name="ReverseProxyInboundRule1" stopProcessing="true">
                    <match url="(.*)" />
                    <conditions logicalGrouping="MatchAll" trackAllCaptures="false">
                        <add input="{CACHE_URL}" pattern="^(https?)://" />
                    </conditions>
                    <serverVariables>
                        <set name="HTTP_X_ORIGINAL_ACCEPT_ENCODING" value="{HTTP_ACCEPT_ENCODING}" />
                        <set name="HTTP_ACCEPT_ENCODING" value="" />
                </serverVariables>
                    <action type="Rewrite" url="{C:1}://server1.xxxxx.com/{R:1}" />
                </rule>
            </rules>
            <outboundRules>
                <rule name="RestoreAcceptEncoding" preCondition="NeedsRestoringAcceptEncoding">
                <match serverVariable="HTTP_ACCEPT_ENCODING" pattern="^(.*)" />
                <action type="Rewrite" value="{HTTP_X_ORIGINAL_ACCEPT_ENCODING}" />
                </rule>
                <rule name="ReverseProxyOutboundRule1" preCondition="ResponseIsHtml1">
                    <match filterByTags="A, Form, Img" pattern="^http(s)?://server1.xxxxx.com/(.*)" />
                    <action type="Rewrite" value="http{R:1}://server1.xxxxx.local/{R:2}" />
                </rule>
                <preConditions>
                    <preCondition name="ResponseIsHtml1">
                        <add input="{RESPONSE_CONTENT_TYPE}" pattern="^text/html" />
                    </preCondition>
                    <preCondition name="NeedsRestoringAcceptEncoding">
                        <add input="{HTTP_X_ORIGINAL_ACCEPT_ENCODING}" pattern=".+" />
                    </preCondition>
                </preConditions>
            </outboundRules>
        </rewrite>
        <tracing>
            <traceFailedRequests>
                <add path="*">
                    <traceAreas>
                        <add provider="ASP" verbosity="Verbose" />
                        <add provider="ISAPI Extension" verbosity="Verbose" />
                        <add provider="WWW Server" areas="Authentication,Security,Filter,StaticFile,CGI,Compression,Cache,RequestNotifications,Module,FastCGI,WebSocket"
verbosity="Verbose" />
                    </traceAreas>
<failureDefinitions timeTaken="00:00:00" statusCodes="404" />
                </add>
            </traceFailedRequests>
        </tracing>
        <httpErrors errorMode="Custom" />
        <httpRedirect enabled="false" destination="" exactDestination="false" childOnly="false" httpResponseStatus="Permanent" />
    </system.webServer>
</configuration>

On Wed, 28 Jan 2015 17:53:41 +0000, dwrobins2000 wrote:
Here is my problem. I cannot get HTTP to HTTPS redirect to work using the URL Rewrite module. I am using version 2, by the way, which I understand is the latest version. I've also enabled the "Proxy Server" and Application Request Routing"
features.
Web/IIS related issues are better posted where the IIS experts are:
http://forums.iis.net
Paul Adare - FIM CM MVP
"The equivalent of treating dandruff by decapitation"
-- Frank Zappa on the Parents Music Resource Center' censorship plans

Domain Alias approch - Best Practice Request

Hello,
I am managing a company that has many domains. We have been using standard sendmail for mail server.
I have set it up through relay-domains etc... such that a user can get mail at any of the listed domains (there are 76 of them!). So, if I have jdoe mail will route to that user if you send mail to [email protected], [email protected] etc... all 76 of them.
My question is how to best replicate this functionallity with minimal (one time?) administration in msgsrvr... imta.cnf? some other means?
Thanks for reading...
Mike

Mike, this question looks very much like the one that's been getting discussion in the ims-info forum. Please understand, I read that forum, daily. . .
The advise you get there should be considered totally authoratative.
Domain Alias is indeed the correct way to have our Messaging Server handle this task for you.

IAS 6.0 and Rewrite rules

Hi,
I have worked with Apache JServ in which you have the concept of Rewrite
rules in one of the property files.
How does the same concept work with iAS 6.0?
Thanks
Uzma

Based on my (limited) understanding of JServ rewrite rules, rewrite rules
are essentially a regex tool for URL modification that takes place at the
webserver tier before the servlet engine sees the request.
So, you should be able to implement something similar in an NSAPI plug-in at
the webserver tier. Or by using an ISAPI plug-in if you are using IIS, or
mod_rewrite if you are using Apache. (I don't know if anyone has already
implemented such a plug-in in NSAPI or ISAPI). Just make sure that the
re-write plug-in is before the iAS plug-in.
You could try to do something similar with servlet mapping at the iAS tier,
but that route is much more limited. Wildcards as opposed to regular
expresssions. And you ability to map servlets would be limited to URL's that
are already in the context of the webapp.
David
Uzma Siddiqui wrote:
Hi,
I have worked with Apache JServ in which you have the concept of Rewrite
rules in one of the property files.
How does the same concept work with iAS 6.0?
Thanks
Uzma

How to create anti-spoof rules with exception

Hello all,
I'm a beginner with Ironport and I need to create rules for specific cases.
I manage many mail domains and I want to create an anti-spoof rule with message filter. Easy to do with a dictionnary containing all my mail domains.
But I have some mail addresses with external applications that need to be send with my mail domains.
For example, I receive acknowledge mails sent with [email protected] address and example.com is an domain accepted and managed by my enterprise. So if I activate my anti-spoof rule, all external [email protected] mail will be dropped.
For example I tried this rule with no success :
Filter_AntiSpoofing: if (recv-listener == "IncomingMail") AND (mail-from-dictionary-match("My_Domains", 1)) AND (mail-from-dictionary-match("Bypass_Sender", 0)){
drop();
I tried this rule too :
Filter_AntiSpoofing: if (recv-listener == "IncomingMail") AND (mail-from-dictionary-match("My_Domains", 1)) AND ((mail-from !="^[email protected]$") OR (mail-from !="^[email protected]$") OR (mail-from !="@ack.mydomain.com$")){
drop();
Have you got any tips or advice to answer my funny case ?

Hello,
We use the following message filter to ear-mark spoofed messages with an X-Header (which we later use for reporting since we told Ironport to log this specific header)
Spoofed_Email_Filter: if (recv-listener == "IncomingMail") AND (mail-from-dictionary-match("dict_internaldomains", 1)) {
insert-header("X-Spoofed", "from[$EnvelopeFrom]_To[$EnvelopeRecipients]_IP[$RemoteIP]_rep[$Reputation]");
The one drawback is that we need to maintain the Dictionary "dict_internaldomains". If we forget to add a new domain to this list it will never be detected as spam.
A good new message filter functionality would be to be able to do a "mail-from-rat-match" which would allow you to use the RAT tables(s) as dictionary.
We plan to solve this by moving the RAT to LDAP and query that same LDAP as dictionary. (If only I had time to test it) :D
Good luck,
Steven

Rewrite Rules with Domain Alias

Similar Messages

Maybe you are looking for