APO DP Linerar regression strategy 94 with Trend dampening profile

Hi every body
We want to use linear regression combined with trend dampening profile. I expected to get corrected forecast corrected by Trend dampening profile but , after statistical run, by clicking on Trend Dampening in interactive planning book / planning view , we see the time series of dampening , but the corrected forecast is not corrected by dampening time series. Do we need to maintain a macro to get correction ?
Kind regards

Hi.
Will you please elaborate further ?
In Linear regression,the only parameter that we can enter is a trend dampening profile.
The system performs an ex-post forecast so that we can compare the results with other methods.
Regards
Datta

Similar Messages

ISE with Trend Micro OfficeScan supported version

Hi.
My customer have plan to install ISE with Trend Micro OfficeScan 10.5 as NAC solution.
I confirmed below supported AV/AS Products list.
Server side Trend Micro OfficeScan Corporate Edition 10.x is not included.
But Client side Trend Micro OfficeScan Client 10.x is incduled.
What this means?
Trend Micro OfficeScan Client 10.x 4.9.0.28 / 3.4.21.1 4.9.0.28 / 3.4.21.1 yes
Trend Micro OfficeScan Client 5.x 4.9.0.28 / 3.4.21.1 4.9.0.28 / 3.4.21.1 yes
Trend Micro OfficeScan Client 6.x 4.9.0.28 / 3.4.21.1 4.9.0.28 / 3.4.21.1 yes
Trend Micro OfficeScan Client 7.85.x 4.9.0.28 / 3.4.21.1 4.9.0.28 / 3.4.21.1 -
Trend Micro OfficeScan Client 7.x 4.9.0.28 / 3.4.21.1 4.9.0.28 / 3.4.21.1 yes
Trend Micro OfficeScan Client 8.x 4.9.0.28 / 3.4.21.1 4.9.0.28 / 3.4.21.1 yes
Trend Micro OfficeScan Corporate Edition 5.x 4.9.0.28 / 3.4.21.1 4.9.0.28 / 3.4.21.1 yes
Trend Micro OfficeScan Corporate Edition 6.x 4.9.0.28 / 3.4.21.1 4.9.0.28 / 3.4.21.1 yes
Trend Micro OfficeScan Corporate Edition 7.x 4.9.0.28 / 3.4.21.1 4.9.0.28 / 3.4.21.1 yes
Cisco Identity Services Engine Supported Windows AV/AS Products Compliance Module Version 3.5.2221.2
http://www.cisco.com/en/US/docs/security/ise/ComplianceModule/win-avas-3_5_2221_2.pdf
Regards,
Miyazaki

http://support.mozilla.com/en-US/kb/Installing+a+previous+version+of+Firefox
http://www.mozilla.com/en-US/firefox/all-older.html

Relase Strategy with different Currency

My Organisation has 3 plants - Plant1 is having currency SGD , Plant2 is having currency SGD and Plant3 is having currency USD.
My release strategy is having characteristics - Plant, PR Value and Material Group.This same strategy is being used for all 3 plants.
Characteristics PR Value is created with currency SGD.Now when we are creating PR in Plant3 system is taking currency USD which is correct.
I have defined strategy with PR value as below -
> 0 and less than 3000 SGD - A
>3000 and less than 15000 SGD - B
Now when we are creating PR in Plant3 with value 2999 USD system is taking strategy as B as 2999 USD is greater than 3000 SGD and 15000 SGD, whereas we want the system to take strategy A becuase user is entering amount as 2999.
Is it possible to have this with same release group and release class.

Hi
I doubt you will achive the the reslut with a char. in different currency as you can not have two different classes , so similarly a char can not have two different currencies. You can have higher range of the third after muliplying the usd with conversion factor as one more value range. My suggestion for you to have the char valuess in CoCd currency and during PR creation you can enter the PR valuation price in usd and the currency USD, you can achieve the same result as system will convert the usd into CoCd currency and try to match the new value range you have created.
Regards

Compatibility of Firefox 6 with Trend Micro titanium - how can I make them work together? My OS is Win XP (service pack 2 & 3)

Compatibility of Firefox 6 with Trend Micro titanium - how can I make them work together?
I have not downloaded FF6 yet because it is not compatible with my virus software - has this changed? If not, is there a simple "fix" or workaround?
Thanks.

Found the following on the TrendMicro forum:
*TrendMicro forum: http://community.trendmicro.com/
*Found fix in this thread: http://community.trendmicro.com/t5/Home-and-Home-Office-Forum/Firefox-6-amp-TM-Firefox-Extension-6-5-0-1234/td-p/43735 (posted by PartyJetsetGo, Customer Service Manager)
*[Hot Fix] B1306: http://esupport.trendmicro.com/solution/en-us/1059243.aspx
'''If this reply solves your problem, please click "Solved It" next to this reply when <u>signed-in</u> to the forum.'''

Creating Roles for Purchase Req. release strategy with classification

Hi friends,
Since I have created Purchase req rel strategy where I have four release strategy
1. For Plant 1 When value <= 5000 (Officer) will release , release code 01 release release strategy r1 and rel code L1
2 For Plant 1 When value >= 5000 (Manager) will release , release code 01 release release strategy r2and rel code L2
Now the manager will have 2 release code,if officer is absent he could release the requisition.
Same has to be done for plant 2
The release Group and code needs to be assigned to the Roles , could anybody tell me where i could know about roles and will be able to create roles and assign authorisation objects to the Roles , and release group and code to the enduser.
though its a basis job , since I have no idea , I mean I have never worked with Roles ,as now I have created the Release strategy with classification I need to assign authorisation objects to the Roles as I have four release strategy
1. For Plant 1 lower value of requisition 1 codeL1(Officer)
2 For higher value of requisition 2 code say Li and L2(Manager)
Manager should have 2 codes if officer is absent he could release
Same has to be done for Plant 2
Thanks N Regards
Siddhartha

Hii,
Steps:
1) Create a Role
2) Add the authorization Object M_EINK_FRG by taking the manual option
3) Assign Release Code and Release Grp
4) Assign the Role to the User ID which has the authorization of the Release Code and Grp.
Regards,
Kumar

Create a purchase order strategy with four release steps.

Hi all,
how can I create a purchase order release strategy with 4 release steps?
The steps have to be the following:
AC (Buyer);
CO (Controller);
FI (Finance);
AD (CEO).
I couldn't configure and add entries in "Release prerequisites" (trx.OMGS).
Best regards

Hi ,
The implemantation steps as follows ;
Materials Management -- Purchasing -- Purchase Order --Release Procedure for Purchase Orders
1 . Edit Characteristic ; You must create characteristics that related your strategy first . IN additonal data screen use "CEKKO " as table and appropriate field as field name .
2. Edit Class ; Create your class with class type - 032 . And enter your characteristics that created first step .
3. Define Release Procedure for Purchase Orders
                a.Create Release Groups and enter your class
                b.Create release codes related with Buyer , controller etc.
                c.Create Release indicator
                d. Create Release Strategies ; Enter your release codes and in classificaiton area , you must enter your values that related with characteristics that created step 1.

Kanban Replenishment Strategy with Reporting Points

I am trying to implement a SAP kanban system with repetitive manufacturing using reporting points. My problem is that when I change the status from empty to full I get error RM086 - GR with backflush not for reporting point logic with automatic GR option. I get this error regardless of control key (auto GR or not auto GR) setting on the routing. I reading SAP help on the subject; I see there is a page discussing replenishment strategy with reporting points which would infer that there should be a strategy with a similar name in configuration for replinishment strategies for in-house prodution. We are on ECC 6.0 and this option is not available in our system. What am I missing???

Hi,
As you are using In House production Replenishment Strategy , You must define Replenishment strategy for reporting points in Configuration as below:
SPRO->Production>KANBAN>Replenishment Strategies>Define In-house Production Strategies>Working With Reporting Points Replenishment strategy you need to define.
Then assigned this defined strategy in KANBAN Control Cycle in PKMC-->Replenishment Strategy->
Choose In-house Production Radio Button and in front of that select the above defined replenishment strategy to work with reporting points.
Hope this helps.
Regards,
Tejas

Tranposrt - Purchase Requisition Release Strategy with Classification

Gurus!
Tell me if I want to Transport the Purchase Requisition release strategy with classification. The Data in each charisteristics in each PR Strategy that I have set in Dev is not getting transported to Quality.
Do I have to enter the data in characteristics again in Quality and the same procedure I have to apply for Production.
If yes, in this scenario, Can I make Production modifiable.
Regards
Sajid

Hello,
Create a special ID in PRD with access to change characteristics. This ID should be released for specific purposes and with approval (project manager/SAP support manager). You can also turn on auditing so that all activites performed are logged which can be used to satify auditors.
Cheers !

PR overall release strategy with acc. assignment category characteristics

Hi,
Here is my issue : i created an Overall release strategy but the characteristic is on item level. In some precise cases, no release is generated.
see below more details :
I have created the following PR release strategy with classification.
PR type concerned " NB": overall release
Rlease group concerned : overall release
In this release group i have 1 class
in this class i have 2 characteristics : PR type and Account assignement category.
Release strategy 1 :
PR type = NB
Acc. assignment cat = P, W
Release strategy 2:
PR type = NB
Acc. assignment cat = K, V
TEST 1 : PR type NB, 1 item with P category
OK the release strategy 1 is generated
TEST 2 : PR type NB, 1 item with W category
OK the release strategy 1 is generated
TEST 3 : PR type NB, 2 items with P category
OK the release strategy 1 is generated
TEST 4 : PR type NB, 2 items with P and W category
TEST KO, no release strategy is generated
=> what should i do to solve this issue ?
Thank you in advance for your quick answers,
Isabelle

What is the specific requirement for Overall release strategy?
Besides, once you go for Overall release strategy, you cannot have another release strategy at item level.
Every line item generates a PO, so logically should be set to a release strategy.
Bottomline is use release strategy at line item level Unless a specific reason exists.
Regards,
Sameer

Release Strategy with Workflow for PR & PO

Hi Experts,
I have configured the PR & PO Release strategy and it is working fine. My client wants the Workflow concept in Releases.
So User should get the information about the releases for PR & PO.
But I don't have much idea on Workflow, how it works for Release strategy. Can anybody give information on how to configure the Release strategy with Workflow in PR & PO.
Points will be awarded .
thanks & rgds
Swamy

Hi Swamy,
The release workflow is configured by MM functional consultant. As for the workflow determination (i.e. which level should approve first and so forth) depends solely/mainly on the Finance of the company. It differs from one company to another. And the level of approval also differ from one company to another. Hence, like you mentioned, this would be provided by the user, so it is okay. I have replied to someone on another thread asking about workflow, and this is how it works.
How it works? For example, for a PR release strategy, once the PR is raised by a user for a certain value, the PR raised that matched the classification of the release strategy configured will be triggered. In this sense, once the release strategy is triggered, the releaser holding the release code to release this PR will receive a workflow in their SAP inbox (Not Outlook) for their execution, which is sent automatically by SAP system. These is accessible via the t-code SBWP. Each releaser have a unique login ID and password.
Assuming the release strategy required 3 levels of release, for example A3, A2 and finally A1 (final release), A3 will first receive this workflow in his/her inbox. After A3 has released, A2 will subsequently receive workflow in his/her inbox for this same PR. In the PR, you will be able to see that A2 release is now possible. This flow will continue until the final releaser, A1 and then, the status of the PR will be unblocked for issuance of PO.
How is it configured in SPRO? In the Workflow for PR release strategy, you are able to assign a unique ID (usually employee ID) to a particular release code, which these release codes are tied to one or more release strategies. The workflow determines who is to release for a release strategy with that particular release code via the assignment of the ID to that particular release code. Each assignment is only possible for one Plant, and you have to assign the same for many other Plants for the same ID in the workflow if you want him/her to have the authority to release purchasing docs in more than one Plant.
How to configure?
Before that, you need to obtain the following information - User ID of the releaser for the specified release code, Plant to be released by the user, and finally of course the Group and Release code (which you already have).
For PR: IMG>MM>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Set Up Procedure with Classification-->Workflow
For PO: IMG>MM>Purchasing>Purchase Order>Release Procedure for Purchase Orders>Define Release Procedure for Purchase Orders>Workflow.
Maintain the details u already have in hand:
For PR: Group (PR or PO), Code (release code), Plant (you have to maintain the same details for each of the Plant that the same release code releases) Object (US) and Agent ID (the user's ID used to login to SAP system and SBWP).
For PO: Group (PR or PO), Code (release code), Object (US) and Agent ID (the user's ID used to login to SAP system and SBWP).
Please note that PO is not Plant specific, and is usually one releaser to release the PO for GR. It is the PR that during the initial stage has the most level of release (up to max. 8 level) before a PR can be converted to PO. After the PO is converted, it is usually deemed accepted, hence only one release code is usually required to release the PO.
Hope this will give you an idea how the workflow works and how to configure it.
Rgds.

PR release strategy with classification

As part of a rollout, we are migrating an instance of SAP to the template SAP. Both the SAP instances are following u2018PR release strategy with classificationu2019.
The limitation is that I can configure only two release group in PR release strategy with classification. One for overall release and one at item level release. Also, I cannot assign two different release class for the same release group. If I add additional characteristics in the existing class and keep other irrelevant characteristics as blank the release strategy doesnu2019t works. the release strategy does not triggers.
Any pointers to solve this will be highly appreciated.

Hi Ashish,
If your requirement is to have release strategy with more or different characteristics than in the existing system,you may create a new release group and assign the same to release class.There no restriction for having multiple release groups for same release class.Then create new release strategies for the newly created release group and so on.
Regards,
Edited by: Dayanandan Kamath on Oct 20, 2010 7:52 AM

MM Release Strategy with Cost Centre

My characteristics for the release strategy is Accnt Assigmnt (KNTTP), Cost Centre (KOSTL) and Amount (GSWRT). I link all to the ceban straucture, and for the cost centre, I entered in the value tab the cost centres that I am using, and I entered the cost centres in the release strategy. Everything seem OK for the release strategy, but the release strategy is only selecting the strategy according to the values and not considering the cost centre, what can I do let it consider the cost centre and the value. I have been struggleing with this problem more than a week now. I tried everything that I can think of. Can someone assit me in this matter. I am on ECC 6.
Thank you.

Refer OSS Note :: 52225
Solution ::
Summary
Symptom
Purchase requisition release strategy with classification does not work as expected when the characteristic for cost center KOSTL is included.
Message ME297 is displayed.
Additional key words
CEBAN-KOSTL, KOSTL, Cost center, Release strategy, OMGQ, ME297
ME51, ME52, ME53
Cause and prerequisites
Numeric values used for the cost center characteristic in the purchase requisition release strategy with classification is not recognized. CEBAN-KOSTL is a CHAR field of length 10.
Solution
Enter leading zeros for the cost center value in the release strategy. eg. If the cost center value is 123456, while entering this value for the cost center in the release strategy, enter it as 0000123456.
Cheers !!!!!!
Biswajit

Release Strategy With Classification

Hey All,
I would like to get some information about release strategy with classification for purchase requisation and purchase order.
Please send me some information regarding this.
Thanks
Kawal

hi,
To see the all the linkages firstly see the classifcation and class defined in the sap system at:
SAP easy access --> Cross application components --> classification system --> master data --> characteristics and classes(CT04 and CL02)...
TO see the customisation, check:
Spro --> MM --> Purchasing --> PO/PR etc --> Release procedure --> Rel procedure with classification --> Here check for all the different transactions...like Relase codes, release stategy, access sequence, schema etc...
Also one important point abt it is:
PR is possible to release at header as well as at item level...
But PO and other external docs are only possible to release at header level only...
In the customisation check all the linkages you will get best out of it....
Regards
Priyanka.P

Back up strategy with Maxtor OneTouch II

I just bought Maxtor OneTouch II 300GB. I need help with the backup strategy with or without Retrospect. The external Maxtor should be used for storage and backup.
My questions, since the instructions and Help in Retrospect are confusing:
When I want to first backup the entire startup disk can I simply drag it to Maxtor on the Desktop or should I use Retrospect?
In Retrospect, should I use "Removable Disk" or "File"?
How long does it take with Maxtor FW 800 ? I've got 70GB startup disk to copy. Is it hours?
Can the copied volume on external disk be used as startup disk?
I would appreciate your experience.
Milan

I suggest you use Disk utility to partition the drive so you have a space large enough for your boot drive. Then use carbon copy cloner, which you can find from versiontracker.com to "clone" your boot drive to the partition. you need to use a program like this, because various files needed to create a "boot drive" are hidden.
please note, the best back-ups are completely disconnected from all computers and power sources. Just something to consider.

Some scanning problems with Trend (iMSS) and iMS

Hi everyone!!!
I have been reading and learning a little, but at the moment I have a problem with Trend InterScan Messaging Security Suite and Mesaging Server.
I have follow the recommendations of example 2 in
http://docs.sun.com/source/819-0105/channel.html#wp100754
but I have some scaning problems.
My files are like................
[SERVICE=SMTP_SCANNING]
!INTERFACE_ADDRESS=127.0.0.1
PORT=10025
IMAGE=IMTA_BIN:tcp_smtp_server
LOGFILE=IMTA_LOG:tcp_smtp_server.log
STACKSIZE=2048000
PARAMETER=CHANNEL=tcp_scanner
! ims-ms
ims-ms defragment subdirs 20 notices 1 7 14 21 28 backoff "pt5m" "pt10m" "pt30m" "pt1h" "pt2h" "pt4h" maxjobs 2 pool IMS_
POOL fileinto $U+$S@$D aliasdetourhost tcp_scanner-daemon
ims-ms-daemon
! tcp_local
tcp_local smtp mx single_sys remotehost inner switchchannel identnonenumeric subdirs 20 maxjobs 7 pool SMTP_POOL maytlsse
rver maysaslserver saslswitchchannel tcp_auth missingrecipientpolicy 0 aliasdetourhost tcp_scanner-daemon
tcp-daemon
! tcp_intranet
tcp_intranet smtp mx single_sys subdirs 20 dequeue_removeroute maxjobs 7 pool SMTP_POOL maytlsserver allowswitchchannel s
aslswitchchannel tcp_auth missingrecipientpolicy 4 aliasdetourhost tcp_scanner-daemon
tcp_intranet-daemon
! tcp_auth
tcp_auth smtp mx single_sys mustsaslserver missingrecipientpolicy 4 aliasdetourhost tcp_scanner-daemon
tcp_auth-daemon
! tcp_scanner
tcp_scanner smtp nomx single_sys identnonenumeric subdirs 20 maxjobs 7 pool SCAN_POOL daemon 172.17.24.34 port 10024 enqu
eue_removeroute
tcp_scanner-daemon
bash-2.05# more mappings
! MTA mappings file
! for access control and other table lookups
PORT_ACCESS
*|*|*|*|* $C$|INTERNAL_IP;$3|$Y$E
* $YEXTERNAL
INTERNAL_IP
$(172.17.24.34/24) $Y
127.0.0.1 $Y
! 172.17.17.41 $Y
! 172.17.16.51 $Y
* $N
ORIG_SEND_ACCESS
tcp_local|*|tcp_local|* $N$D30|Relaying$ not$ allowed
tcp_*|*|native|* $N
tcp_*|*|hold|* $N
tcp_*|*|pipe|* $N
tcp_*|*|ims-ms|* $N
! Block "external" submissions of explicitly source-routed "internal" addresses
tcp_local|*|tcp_intranet|@*:*.* $N$D30|Explicit$ routing$ not$ allowed
tcp_local|*|tcp_intranet|*$%*@* $N$D30|Explicit$ routing$ not$ allowed
tcp_local|*|tcp_intranet|*.*!*@* $N$D30|Explicit$ routing$ not$ allowed
tcp_local|*|tcp_intranet|"*@*"@* $N$D30|Explicit$ routing$ not$ allowed
SEND_ACCESS
tcp_*|*|*|*@[127.*] $X5.1.2|$NBad$ destination$ system
tcp_*|*|*|*@localhost.* $X5.1.2|$NBad$ destination$ system
tcp_*|*|*|*@example.com $X5.1.2|$NBad$ destination$ system
tcp_*|*|*|*@example.net $X5.1.2|$NBad$ destination$ system
tcp_*|*|*|*@example.org $X5.1.2|$NBad$ destination$ system
tcp_*|*|*|*@*.test $X5.1.2|$NBad$ destination$ system
tcp_*|*|*|*@*.example $X5.1.2|$NBad$ destination$ system
tcp_*|*|*|*@*.invalid $X5.1.2|$NBad$ destination$ system
tcp_*|*|*|*@*.localhost $X5.1.2|$NBad$ destination$ system
CONVERSIONS
in-chan=tcp_scanner;out-chan=*;CONVERT No
in-chan=tcp_*;out-chan=tcp_local;CONVERT Yes,Channel=tcp_scanner
!IN-CHAN=tcp_scan;OUT-CHAN=*;CONVERT No
!IN-CHAN=tcp_*;OUT-CHAN=*;CONVERT Yes,Channel=tcp_scan
<IMTA_TABLE:mappings.locale
With this configuration, my iMSS only scan mails from internal to internal domain.
Mails sent via outlook:
10-Oct-2005 17:11:34.13 tcp_auth tcp_scanner EA 3 [email protected] rfc822;[email protected] [email protected]
10-Oct-2005 17:11:34.15 tcp_auth tcp_local EA 3 [email protected] rfc822;[email protected] [email protected]
10-Oct-2005 17:11:34.24 tcp_local D 3 [email protected] rfc822;[email protected] [email protected] dns;mail.out.com (mail.out.com xxxxxxxxxxxxx Mon, 10 Oct 2005 17:09:34 +0200 ) smtp;250 2.1.5 [email protected]
10-Oct-2005 17:11:34.53 tcp_scanner ims-ms E 4 [email protected] rfc822;[email protected] user1@ims-ms-daemon
10-Oct-2005 17:11:34.59 tcp_scanner D 3 [email protected] rfc822;[email protected] [email protected] dns;172.17.24.34 (TrendMicro IMSS SMTP proxy) smtp;250 2.1.5 [email protected] OK.
Mails that do not pass throw tcp_scanner channel are not scan by iMSS, but I don`t know why this outgoings mail don�t pass throw tcp_scanner ��???
And mails sent via webmail :
10-Oct-2005 17:28:42.05 tcp_intranet tcp_scanner E 2 [email protected] rfc822;user1@ in.com user1@ in.com
10-Oct-2005 17:28:42.08 tcp_intranet tcp_local E 2 user1@ in.com rfc822;[email protected] [email protected]
10-Oct-2005 17:28:42.75 tcp_scanner ims-ms E 2 user1@ in.com rfc822;user1@ in.com user1@ims-ms-daemon
10-Oct-2005 17:28:42.80 tcp_scanner D 2 user1@ in.com rfc822;user1@ in.com user1@ in.com dns;172.17.24.34 (TrendMicro IMSS SMTP proxy) smtp;250 2.1.5 [email protected] OK.
10-Oct-2005 17:28:42.87 tcp_local D 2 user1@ in.com rfc822;[email protected] [email protected] dns;mail.out.com (mail.out.com xxxxxxxxxxxxx Mon, 10 Oct 2005 17:26:42 +0200 ) smtp;250 2.1.5 [email protected]
10-Oct-2005 17:28:42.96 ims-ms D 2 [email protected] rfc822;[email protected] user1@ims-ms-daemon
Thanks in advance.

# ./imsimta test -rewrite -debug=level=4 -filter [email protected]
Initializing mm_.
Initializing mm_ submission.
Checking identifiers.
*** Debug output from initializing MM for submission:
16:21:04.24: mmc_winit('l','[email protected],'[email protected]) called.
16:21:04.24: mmc_determine_url beginning with pattern , xadr , mbox , subaddress
16:21:04.24: Empty URL specified.
16:21:04.24: Queue area size 38574770, temp area size 405486
16:21:04.24: 9643692 blocks of effective free queue space available; setting disk limit accordingly.
16:21:04.24: 202743 blocks of free temporary space available; setting disk limit accordingly.
16:21:04.24: mmc_address_to_tree: Parsing address.
16:21:04.24: Right default: in.com
16:21:04.24: Parsing address with null fixup.
16:21:04.24: mmc_address_to_tree: Returning.
16:21:04.24: Rewriting: Mbox = "postmaster", host = "projes.in.com", domain = "$*", literal = "", tag = ""
16:21:04.24: Rewrite: "$*", position 0, hash table -
16:21:04.24: Found: "$A$E$F$U%[email protected]"
16:21:04.24: Rewrite failed, not forward.
16:21:04.24: Rewrite: "$*", position 1, hash table -
16:21:04.24: Failed.
16:21:04.24: Rewrite: "$*", position 0, rewrite database -
16:21:04.24: Failed
16:21:04.24: Rewriting: Mbox = "postmaster", host = "projes", domain = "projes.in.com", literal = "", tag = ""
16:21:04.24: Rewrite: "projes.in.com", position 0, hash table -
16:21:04.24: Found: "$U%[email protected]"
16:21:04.24: New mailbox: "postmaster".
16:21:04.24: New host: "projes.in.com".
16:21:04.24: New route: "projes.in.com".
16:21:04.24: New channel system: "projes.in.com".
16:21:04.24: Looking up host "projes.in.com".
16:21:04.24: - found on channel l
16:21:04.24: Routelocal flag set; scanning for % and !
16:21:04.24: Checking reverse URL cache for: [email protected]
16:21:04.24: Applying reverse URL pattern ldap:///$V?$N?sub?$R to: [email protected]
16:21:04.24: mmc_determine_url beginning with pattern ldap:///$V?$N?sub?$R, xadr [email protected], mbox , subaddres
s
16:21:04.24: Get domain information for: projes.in.com
16:21:04.24: dmap_locate_domain called with domain projes.in.com
16:21:04.24: Performing LDAP search on baseDN dc=in,dc=es scope 2 filter (&(objectclass=sunManagedOrganization)(|(associ
atedDomain=projes.in.com)(sunPreferredDomain=projes.in.com)))
16:21:04.25: Search returned 'Success' (0)
16:21:04.25: 0 entries returned
16:21:04.25: Creating negative cache entry for projes.in.com
16:21:04.25: Get domain failed with status -1
16:21:04.25: Added tentative negative entry to domain match cache.
16:21:04.25: URL generation failed, status = 0
16:21:04.25: Mapped return address: [email protected]
16:21:04.25: from_access mapping check: ||MAIL|l|[email protected]|
16:21:04.25: Mapping -1 applied to ||MAIL|l|[email protected]|
16:21:04.25: No such mapping; performing simple copy.
16:21:04.25: - passed.
16:21:04.25: mmc_address_to_tree: Parsing address.
16:21:04.25: Right default: in.com
16:21:04.25: Parsing address with local fixup.
16:21:04.25: mmc_address_to_tree: Returning.
16:21:04.25: Rewriting: Mbox = "postmaster", host = "projes.in.com", domain = "$*", literal = "", tag = ""
16:21:04.25: Rewrite: "$*", position 0, hash table -
16:21:04.25: Found: "$A$E$F$U%[email protected]"
16:21:04.25: Rewrite failed, not forward.
16:21:04.25: Rewrite: "$*", position 1, hash table -
16:21:04.25: Failed.
16:21:04.25: Rewrite: "$*", position 0, rewrite database -
16:21:04.25: Failed
16:21:04.25: Rewriting: Mbox = "postmaster", host = "projes", domain = "projes.in.com", literal = "", tag = ""
16:21:04.25: Rewrite: "projes.in.com", position 0, hash table -
16:21:04.25: Found: "$U%[email protected]"
16:21:04.25: New mailbox: "postmaster".
16:21:04.25: New host: "projes.in.com".
16:21:04.25: New route: "projes.in.com".
16:21:04.25: New channel system: "projes.in.com".
16:21:04.25: Looking up host "projes.in.com".
16:21:04.25: - found on channel l
16:21:04.25: Routelocal flag set; scanning for % and !
*** Debug output from rewriting a forward header address:
16:21:04.25: mmc_sender_rewrite: Rewriting header line.
16:21:04.25: mmc_address_to_tree: Parsing address.
16:21:04.25: Right default: in.com
16:21:04.25: Parsing address with null fixup.
16:21:04.25: mmc_address_to_tree: Returning.
16:21:04.25: Parse successful.
16:21:04.25: Rewriting: Mbox = "ma", host = "out.com", domain = "$*", literal = "", tag = ""
16:21:04.25: Rewrite: "$*", position 0, hash table -
16:21:04.25: Found: "$A$E$F$U%[email protected]"
16:21:04.25: Rewrite failed, not envelope.
16:21:04.25: Rewrite: "$*", position 1, hash table -
16:21:04.25: Failed.
16:21:04.25: Rewrite: "$*", position 0, rewrite database -
16:21:04.25: Failed
16:21:04.25: Rewriting: Mbox = "ma", host = "out", domain = "out.com", literal = "", tag = ""
16:21:04.25: Rewrite: "out.com", position 0, hash table -
16:21:04.25: Failed.
16:21:04.25: Rewrite: "out.com", position 0, rewrite database -
16:21:04.25: Failed
16:21:04.25: Rewriting: Mbox = "ma", host = "out", domain = ".es", literal = "", tag = ""
16:21:04.25: Rewrite: "*.es", position 0, hash table -
16:21:04.25: Failed
16:21:04.25: Rewrite: ".es", position 0, hash table -
16:21:04.25: Found: "$U%$H$D@TCP-DAEMON"
16:21:04.25: New mailbox: "ma".
16:21:04.25: New host: "out.com".
16:21:04.25: New route: "TCP-DAEMON".
16:21:04.25: New channel system: "TCP-DAEMON".
16:21:04.25: Looking up host "TCP-DAEMON".
16:21:04.25: - Not found
16:21:04.25: Rewrite rules result: [email protected]
16:21:04.25: Checking reverse URL cache for: [email protected]
16:21:04.25: Applying reverse URL pattern ldap:///$V?$N?sub?$R to: [email protected]
16:21:04.25: mmc_determine_url beginning with pattern ldap:///$V?$N?sub?$R, xadr [email protected], mbox , subaddress
16:21:04.25: Get domain information for: out.com
16:21:04.25: dmap_locate_domain called with domain out.com
16:21:04.25: Performing LDAP search on baseDN dc=in,dc=es scope 2 filter (&(objectclass=sunManagedOrganization)(|(associ
atedDomain=out.com)(sunPreferredDomain=out.com)))
16:21:04.25: Search returned 'Success' (0)
16:21:04.25: 0 entries returned
16:21:04.25: Creating negative cache entry for out.com
16:21:04.25: Get domain failed with status -1
16:21:04.25: Added tentative negative entry to domain match cache.
16:21:04.25: URL generation failed, status = 0
16:21:04.25: mmc_sender_rewrite: Returning.
*** Debug output from rewriting a forward envelope address:
16:21:04.25: mmc_address_to_tree: Parsing address.
16:21:04.25: Right default: in.com
16:21:04.25: Parsing address with null fixup.
16:21:04.25: mmc_address_to_tree: Returning.
16:21:04.25: Rewriting: Mbox = "ma", host = "out.com", domain = "$*", literal = "", tag = ""
16:21:04.25: Rewrite: "$*", position 0, hash table -
16:21:04.25: Found: "$A$E$F$U%[email protected]"
16:21:04.25: Match, pattern = "out.com", current = "(*domaincheck*)"
16:21:04.25: old state = not checked.
16:21:04.25: Domain check on out.com.
16:21:04.25: dmap_locate_domain called with domain out.com
16:21:04.25: Negative cache entry found
16:21:04.25: new state = fail pending.
16:21:04.25: Rewrite failed due to prechannel mismatch.
16:21:04.25: Rewrite: "$*", position 1, hash table -
16:21:04.25: Failed.
16:21:04.25: Rewrite: "$*", position 0, rewrite database -
16:21:04.25: Failed
16:21:04.25: Rewriting: Mbox = "ma", host = "out", domain = "out.com", literal = "", tag = ""
16:21:04.25: Rewrite: "out.com", position 0, hash table -
16:21:04.25: Failed.
16:21:04.25: Rewrite: "out.com", position 0, rewrite database -
16:21:04.25: Failed
16:21:04.25: Rewriting: Mbox = "ma", host = "out", domain = ".es", literal = "", tag = ""
16:21:04.25: Rewrite: "*.es", position 0, hash table -
16:21:04.25: Failed
16:21:04.25: Rewrite: ".es", position 0, hash table -
16:21:04.25: Found: "$U%$H$D@TCP-DAEMON"
16:21:04.25: New mailbox: "ma".
16:21:04.25: New host: "out.com".
16:21:04.25: New route: "TCP-DAEMON".
16:21:04.25: New channel system: "TCP-DAEMON".
16:21:04.25: Looking up host "TCP-DAEMON".
16:21:04.25: - Not found
forward channel =
backward channel =
header To: address = [email protected]
header From: address = [email protected]
envelope To: address = (route (TCP-DAEMON,TCP-DAEMON)) (host out.com)
envelope From: address =
name =
mbox = ma
Extracted address action list:
[email protected]
Extracted 733 address action list:
[email protected]
Address list expansion:
*** Debug output from alias expansion:
16:21:04.25: Inner expand, level = 0, mailbox = [email protected]
16:21:04.25: mmc_address_to_tree: Parsing address.
16:21:04.25: Right default: in.com
16:21:04.25: Parsing address with null fixup.
16:21:04.25: mmc_address_to_tree: Returning.
16:21:04.25: Rewriting: Mbox = "ma", host = "out.com", domain = "$*", literal = "", tag = ""
16:21:04.25: Rewrite: "$*", position 0, hash table -
16:21:04.25: Found: "$A$E$F$U%[email protected]"
16:21:04.25: Match, pattern = "out.com", current = "(*domaincheck*)"
16:21:04.25: old state = not checked.
16:21:04.25: Domain check on out.com.
16:21:04.25: dmap_locate_domain called with domain out.com
16:21:04.25: Negative cache entry found
16:21:04.25: new state = fail pending.
16:21:04.25: Rewrite failed due to prechannel mismatch.
16:21:04.25: Rewrite: "$*", position 1, hash table -
16:21:04.25: Failed.
16:21:04.25: Rewrite: "$*", position 0, rewrite database -
16:21:04.25: Failed
16:21:04.25: Rewriting: Mbox = "ma", host = "out", domain = "out.com", literal = "", tag = ""
16:21:04.25: Rewrite: "out.com", position 0, hash table -
16:21:04.25: Failed.
16:21:04.25: Rewrite: "out.com", position 0, rewrite database -
16:21:04.25: Failed
16:21:04.25: Rewriting: Mbox = "ma", host = "out", domain = ".es", literal = "", tag = ""
16:21:04.25: Rewrite: "*.es", position 0, hash table -
16:21:04.25: Failed
16:21:04.25: Rewrite: ".es", position 0, hash table -
16:21:04.25: Found: "$U%$H$D@TCP-DAEMON"
16:21:04.25: New mailbox: "ma".
16:21:04.25: New host: "out.com".
16:21:04.25: New route: "TCP-DAEMON".
16:21:04.25: New channel system: "TCP-DAEMON".
16:21:04.25: Looking up host "TCP-DAEMON".
16:21:04.25: - Not found
-13 expansion total.
*** Debug output from submitting an envelope address:
16:21:04.25: mmc_wadr(0x0012b5e8,'[email protected]','[email protected]') called.
16:21:04.25: mmc_address_to_tree: Parsing address.
16:21:04.25: Right default: in.com
16:21:04.25: Parsing address with local fixup.
16:21:04.25: mmc_address_to_tree: Returning.
16:21:04.25: Copy estimate before address addition is 1
16:21:04.25: Parsing address [email protected]
16:21:04.25: mmc_address_to_tree: Parsing address.
16:21:04.25: Right default: in.com
16:21:04.25: Parsing address with local fixup.
16:21:04.25: mmc_address_to_tree: Returning.
16:21:04.25: Rewriting: Mbox = "ma", host = "out.com", domain = "$*", literal = "", tag = ""
16:21:04.25: Rewrite: "$*", position 0, hash table -
16:21:04.25: Found: "$A$E$F$U%[email protected]"
16:21:04.25: Match, pattern = "out.com", current = "(*domaincheck*)"
16:21:04.25: old state = not checked.
16:21:04.25: Domain check on out.com.
16:21:04.25: dmap_locate_domain called with domain out.com
16:21:04.25: Negative cache entry found
16:21:04.25: new state = fail pending.
16:21:04.25: Rewrite failed due to prechannel mismatch.
16:21:04.25: Rewrite: "$*", position 1, hash table -
16:21:04.25: Failed.
16:21:04.25: Rewrite: "$*", position 0, rewrite database -
16:21:04.25: Failed
16:21:04.25: Rewriting: Mbox = "ma", host = "out", domain = "out.com", literal = "", tag = ""
16:21:04.25: Rewrite: "out.com", position 0, hash table -
16:21:04.25: Failed.
16:21:04.25: Rewrite: "out.com", position 0, rewrite database -
16:21:04.25: Failed
16:21:04.25: Rewriting: Mbox = "ma", host = "out", domain = ".es", literal = "", tag = ""
16:21:04.25: Rewrite: "*.es", position 0, hash table -
16:21:04.25: Failed
16:21:04.25: Rewrite: ".es", position 0, hash table -
16:21:04.25: Found: "$U%$H$D@TCP-DAEMON"
16:21:04.25: New mailbox: "ma".
16:21:04.25: New host: "out.com".
16:21:04.25: New route: "TCP-DAEMON".
16:21:04.25: New channel system: "TCP-DAEMON".
16:21:04.25: Looking up host "TCP-DAEMON".
16:21:04.25: - Not found
16:21:04.25: Copy estimate after address addition is 1
Submitted address list:
Address list error -- 5.1.2 unknown host or domain: [email protected]
Submitted notifications list:

APO DP Linerar regression strategy 94 with Trend dampening profile

Similar Messages

Maybe you are looking for