Transport permissions

Is there any way to transport KM content with permissions? The KM content here refers to the WPC and all itu2019s related content along with the documents ( images, document libraries, etc).

Hi,
You can use: ICE Protocol to transport: documents, folders and permissions. You can do delta o full transport.
1. System Administration->System Configuration->KM->CM->Repository Manager
->Advanced Options->Content Exchange Repository->ice repository->Advanced Options->Hide in Root Folder: unmark
2. Content Administration->KM Content->choose ice repository->Syndicator->Global Offer->using
context menu choose->Folder->new->Link  (you have to create a link to the folder that you need to export, you can not mark a complete repository (it is not working).
3. After that, in Global Offer you have Complete Package link, click it. In this way you create a fullupdate.zip file
4. Once you have this zip file, you enter in destination portal and navigate to:
Content Management->Content Exchange->Package Upload-> and choose the file before created.
http://help.sap.com/saphelp_nw70/helpdata/EN/63/42aa17425c514f85ad5ecd45988509/frameset.htm
Patricio.

Similar Messages

  • Return Standard Permissions to Portal Content Objects

    Hello experts,
    I was changing the Permissions of some portal content objects and accidentally I've modified the permissions of all the Portal Content Objects (including the standard objects). I clicked the "Reset child permissions" button of the Permission Editor of the "Portal Content" folder. Do you know any way to return the standard permissions?
    Best regards and thanks in advance

    Hi,
    If you have another portal then you can transport permissions from the first to the seccond portal.
    Cheers,
    Benjamin Houttuin

  • Transport/Export/Import Role Assignments

    Hi all,
    it´s possible to transport, export or import role assignments from one portal to another?
    we implement a testsystem for our customer and want to copy all role assignments from all users from productive to testsystem.
    best regards
    Christian

    Here´s the guide to transport permissions
    http://help.sap.com/saphelp_nw04/helpdata/en/a9/76bd3b57743b09e10000000a11402f/frameset.htm

  • Moving DC from one Track to another track in NMDI??

    Hi,
    we need a hint if (and, of course, which way)  we can move a DC between two tracks in NWDI??
    I had developed a DC in the wrong track, so  i have to move it to another.
    It  is a WebDynpro-Project...
    Regards
    Bernhard

    hi,
    between tracks you can transport SCs (by transporting them with the CMS - with the 'forward' button) but in your case in both tracks should be defined the SC which contains the DC, and after u transport the SC, you should delete the DC in the source track
    more tricky is if you want to move a DC from SC to SC, because when u try to create the DC in the new compartment, the SLD will fail with error like "dc name exists", and in this case you can use the dctool which can be found in the NWDS/eclipse/tools/dc/
    N.B! - if you transport a SC between tracks, all other changes made in this SC in the source track ll be transported also to the target track
    hmm, there's another way, if you can remember the activities which creates this DC, and if their imports into "Consolidation" don't contain other activities (if the activities for the DC are not released together with other acts), you can use the cmstool (NWDS/eclipse/tools/cmstool) to transport only these activities, but you should not use this if these activities have predecessors.
    and remember that for these transports you need cms transport permissions & checkin dtr permissions
    best regards
    atanas

  • Exchange 2010.SP3: Spam in Outbound Mail Queue (mail.que) - How can this be prevented?

    I have been suffering from SPAM being generated from a series of sources (this looks internally generated):
    Identity: XXXX-Exchange\7\10
    Subject: Undeliverable: Daily Health News
    Internet Message ID: <[email protected]>
    From Address: <>
    Status: Ready
    Size (KB): 12
    Message Source Name: DSN
    Source IP: 255.255.255.255
    SCL: -1
    Date Received: 15/01/2014 09:00:22
    Expiration Time: 17/01/2014 09:00:22
    Last Error:
    Queue ID: XXXX-Exchange\7
    Recipients: 
    [email protected];2;2;;0;CN=Exchange Internet Connector,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=XXXX,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=XXXX,DC=local
    XXXX: Refers to domain and naming convention.
    Why are these messages being generated? I know these are NDR's.
    What can I do about it? Already checked the Recipient filtering is enabled and refreshed it.
    I have already cleared down the mail.que file and checked that the Endpoint Protection is in place and up to date.
    The anti-spam option is enabled on the Hub Transport of the Organisational Configuration.
    This has led to Backscatter.org blacklisting the IP address.
    What else can I do about this situation as I have used all Microsoft KB and TechNet solutions to no avail?
    Thanks
    Paul
    Paul.B

    Hello,
    I think you can also consider the using the Transport Permissions to control the spams:
    HOW TO: Prevent annoying spam from your own domain
    http://exchangepedia.com/2008/09/how-to-prevent-annoying-spam-from-your-own-domain.html
    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality,
    safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
    Thanks,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • Exchange 2010 Edge server shows previous version

    I have an Exchange 2010 environment with the Edge role installed on TMG and its working fine.  All servers have had SP3 installed and rebooted.
    I am trying to introduce my first Exchange 2013 server into the environment but the readiness check tells me not all the servers have SP3.  On the Edge server it shows SP3 is installed but from all other Exchange servers it shows SP2.
    Any ideas?
    Thanks

    For anyone else wondering.  I've done this in my lab, and I didn't have to remove the old subscription, just export the file from your edge server, copy it to any server running emc internally and import it, then force a sync and the version should
    update.
    On edge server open exchange
         powershell and run New-EdgeSubscription -FileName
         "C:\EdgeSubscriptionInfo.xml"
    Import edge file
         into new server
    You
    need to be assigned permissions before you can perform this procedure. To see
    what permissions you need, see the "EdgeSync" entry in the
    Transport
    Permissions topic.
    In the console tree, navigate
         to Organization Configuration >
    Hub Transport.
    In the result pane, click the
         Edge
         Subscriptions
         tab.
    In the action pane, click
    New Edge
         Subscription. On
         the New Edge Subscription page, complete the following fields:
    Active
          Directory site   Click
          Browse, and then select an Active
          Directory site in the drop-down list. This field identifies the Active
          Directory site where the Hub Transport server is connecting to the Edge
          Transport server for which the Edge Subscription exists.
    Subscription
          file   Click
          Browse, and then select an Edge
          Subscription file.
    Automatically
          create a Send connector for this Edge Subscription   Select
          this check box to automatically create a Send connector that routes
          messages from the Exchange organization to the Internet. The Edge
          Subscription is configured as the source server for the Send connector.
          The Send connector is configured to route messages to all domains by
          using Domain Name System (DNS) MX resource records.
    Click
    New to create the new Edge
         Subscription.
    On the
    Completion page, review the following,
         and then click Finish to close the wizard:
    A status of
    Completed indicates that the wizard
          completed the task successfully.
    A status of
    Failed indicates that the task
          wasn't completed. If the task fails, review the summary for an
          explanation, and then click Back to make any configuration changes.
    Start-EdgeSynchronization
         -Server Hub01 -TargetServer Edge03 -ForceFullSync

  • Wrong email header encoding, how to modify it?

    Hi, I have a 3rd party server that sends out automated alerts via exchange to external addresses. Emails all get sent out fine except the ones sent to a specific domain. I talked with the external domain provider and was told that our system is sending out
    8bit emails but the header specifies 7bit and because of that the emails were rejected. I then talked to our vendor for the automated system and was told that they were aware of the problem but weren't going to do anything about it.
    So..... is it possible to modify the header for emails sent from that server to that domain to force it to use 8bit? I tried playing around with transport rules and setting the content-transfer-encoding but although the rule is applied is doesn't seem to
    help. I figure I'm missing another setting or I'm doing something wrong. I've been reading up on email encoding but it's a little confusing.
    Thank you.

    Hi,
    Please refer to the following article:
    Change the Method for 7-bit Transfer Encoding
    Use Windows Explorer and Notepad to change the method for transfer encoding
    You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Hub Transport server" entry in the
    Transport Permissions topic.
    On the Exchange 2010-based server running the Hub Transport server role, start Windows Explorer.
    Locate the following folder, in which <drive> represents the actual installation drive:
    <drive>:\Program Files\Microsoft\Exchange Server\V14\Bin.
    Make a backup copy of the EdgeTransport.exe.config file, and name the backup file copy
    EdgeTransport.exe.config.old.
    Start Notepad, and then open the EdgeTransport.exe.config file.
    Locate the following line between the <appsettings> tag and the
    </appsettings> tag.
    Copy
    <add key="ByteEncoderTypeFor7BitCharsets" value="1" />
    If this line doesn't exist in this location, insert the line between the <appsettings> tag and the
    </appsettings> tag.
    Change the value described in the line to an appropriate value from the table in "Values to Change the Method for Transfer Encoding" later in this topic. This value controls the MIME encoding behavior.
    Save the changes, and then exit Notepad.
    Start the Microsoft Exchange Transport service.
    Hope this helps!
    Thanks.
    Niko Cheng
    TechNet Community Support

  • Transporting KM content and permissions...

    Hi,
    Could someone please tell me how to transport KM permissions?
    I know that KM content can be transported using ICE and WebDev methodologies.Is there anyother means to trans port KM content other than ICE and WebDev?
    Could someone please help me with this?
    Thanks in advance,
    Sudha.

    To perform the transport manually by using the commands which can be integrated in the Configuration iView. If you have implemented the Change and Transport System (CTS), you can perform the export and import of the configuration data automatically. Generate a transport package in the following formats:
    ●  Config Archive: Format with the file extension .configarchive
    The configuration data in XML format are available in this file compressed as a ZIP file.
    ●  PAR Archive: Format with the file extension .par - This format is used in the portal environment. The generated PAR file contains the configuration data as a compressed ZIP file in the format .configarchive. In addition, the PAR file contains the files MANIFEST.MF and portalapp.xml.
    The transport of configuration data comprises the following steps:
           1.  Creation of the transport package
           2.  Export of the transport package
           3.  Import of the transport package
    To create a transport package, proceed as follows:
           1. Start the export function.
    a.In the portal, choose System Administration - System Configuration -Knowledge Management-  Content Management.
    b.In the menu bar, choose Actions - Export - Start.
           2.  Put together the transport package.
    a.In the configuration, navigate to the object that you want to export.
    b.Select the required instances and choose Export.
    From the options, you can choose whether referenced configuration objects are to be exported as well. If you have activated this option, you can use another option to specify whether invalid references are also to be exported. Alternatively, you can use the menu bar to put the export package together. Choose Actions - Export - Add. This allows you to choose not only individual instances
          3.  Check what you have put together.
    In the menu bar, choose Actions - Export - Edit Export Package. You can check here which entries the transport package currently contains. You can remove configuration objects by deselecting the checkbox in front of the object and choosing OK.
         4.  Generate the transport package and complete the export.  
    CTS transport: Work through the following steps for the transport with CTS.
         a. Specify a name for the transport package. Optionally, you can enter a comment for this   transport. The selected configuration objects are listed and, if necessary, the configuration objects that they reference.
         b.Choose Start Export to CTS. On the next screen, you can find information about the transport to   CTS.
         c.Choose Close to exit the transport mode.
    Import of a Transport Package in the Format .par
           1. Upload the PAR file to the portal. In the portal, choose System Administration - Support -     Portal Runtime - Administration Console.
           2. Select the file in the input field beneath Upload Archive and then choose Upload.
           3. To activate the imported configuration data in the system, you must restart the application server.
    Access permissions allow users to display, change, or delete items. You can define these permissions for both folders and documents or other items.
    ● Service permissions allow users to use certain functions, . defining the permissions only for folders:
    Permissions in access control lists (ACLs). An entry in an access control list grants a specific access permission, for example, read permission, to a user, group, or role. There are two separate access control lists for permissions and service permissions. An administrator can set up the system in such a way that it can be defined the permissions in the NTFS file system.

  • Transport KM ACL permissions without content

    Hallo
    Is it possible to transport ACL KM permissions without transporting the content in the KM folders?
    As fare as I can see, it is only possible to transport the ACL permission if I select the import mode u201CDelete Conflicting Data Firstu201D. Thus that our solution is in production, this is not an option.
    I have a situation where I need to change a significant number of KM folder permissions and I would like to avoid doing this manually in all 3 portal environments (development, test and production).
    I have looked at the u201CPropagation of ACLsu201D report but I can not define a single template folder u2013 I have around 40 different settings, which have to be applied in 3 different repositories.
    We are on NW 7, SP16.
    Thanks in advance,
    Henrik Andersen

    Hi Henrik,
    I have the exact same query, although I envy you as you only have 40 setting  (I have 30 times 160).
    The reply from Julian is correct altough needs custom development.
    Hopefully SAP will introduce a ACL Export / Import function soon... They already have something similair for assinging roles as you can export assignments to text and import them again OR like the PCD objects XML import/export...
    Only thing I can do is share my current workaround I did (note this action needs to be done in planned downtime as the content will be unavailible for a while).
    on the source system
    1. run KM toolbox > Report >  Mass copy with ACL to a temp repository
    (only copy the elements that where changed)
    2. Transport this temp copy to the target system
    on the target system:
    3. MOVE your content from the actual location to the temp structure
    result is old content in new structure with new permissions
    4. REMOVE the old structure
    5. MOVE the complete structure and content from the temp location back to the original location
    Please do a complete backup and test for that you do it for real as all systems are different and cannot be commpared.
    But again I hope that sombody has a real solution (I hope SAP in SP17 or so)
    Cheers,
    Benjamin Houttuin

  • UNIX permissions to NFS transport directory

    I have upgraded lately to ERP 6.0 on HPUX /Oracle 10.
    I have installed a NFS directory /usr/sap/trans .
    When I release a transport request the owner is unknown (110) and the group (109).
    The Productive system can see the file but has no access to it.
    If I change the owner (chown) everything works fine.
    What I have to do fix it ?
    It sounds to me , there is a UNIX file that allows to insert shared users.
    Thank you.

    Hi,
    the SIDadm user of DEV need to be domain user where you can provide him necessary access on the usr/sap/trans and same should be with Production, if the user was local only to DEV/PRD system then the DEV/PRD system trans directory cannot recognize and validate the permissions of SIDadm user.
    You have to mount the usr/sap/trans of PRD onto usr/sap/trans of DEV so that what ever releases happens they will come and sits PRD trans directory and can be accessed by PRD.
    Even when you mount the transport directory of PRD onto DEV, you should include the DEV system as trusted in PRD and viceversa.
    Then this should work.
    Regards...........
    Edited by: Sita Rr Uppalapati on Jan 13, 2009 1:06 PM

  • Permissions missing in transports

    Hi
    I created a transport, selected "resolving references" and also selected "data and acl". I have permissions on the folder levels and after importing the package these permissions seems to lost. Permissions are based on Roles and all these Roles are already present in the transport. Any idea? Any help highly appreciated! Thanks a bunch
    - Ashish

    Hi,
    Go with below link its help you.
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/ep/transporting%252bpermissions
    Regards,
    Naresh

  • Lion Server postfix mail not being delivered to mailboxes. "SMTP restriction `reject_invalid_helo_hostname' after `permit' is ignored" and "connect to private/policy: Connection refused" errors.

    All, Im stumped. In fact I have been on the phone with Apple Support and this has been escalated to the top engineers, as I think its got them too..
    Anyway, here is my problem..
    I'm running an Mac Mini with OS X 10.7.4 Server. I have had mail running on it for 2 months or so, without any issues. The mail was actually migrated from 10.6 in March, and It actually went smoothly. I have 3 domains which all recieve mail and they all work (or did up until 2 weeks ago)..
    So the story is this.. I can send mail from my domains, without issue.  imap and dovecot must be working.. cause all the stored mail, can be read with the mail IMAP client.. I can even transfer mail messages from one mailbox to another with Mail client. Sending mail is a breeze, it still works and the recipients still recieve their mail. But I noticed I wasnt getting any mail at all from those mailboxes... no mail, no spam, nothing.. which is unusal. I fired up Server admin and checked out the SMTP log, and this is what it showed for every email recieved: (xxxxxx is just me hiding sensitive info)
    Jul 21 14:25:20 xxxxxxxx postfix/postscreen[65857]: CONNECT from [17.158.233.225]:41909
    Jul 21 14:25:26 xxxxxxxx postfix/postscreen[65857]: PASS OLD [17.158.233.225]:41909
    Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: connect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
    Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: warning: restriction `reject_invalid_helo_hostname' after `permit' is ignored
    Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
    Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
    Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
    Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
    Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: NOQUEUE: reject: RCPT from nk11p03mm-asmtp994.mac.com[17.158.233.225]: 451 4.3.5 Server configuration problem; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<nk11p99mm-asmtpout004.mac.com>
    Jul 21 14:25:28 azathoth postfix/smtpd[65858]: disconnect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
    Ok, now what is odd, is these rejected messages are not even appearing in the mail queue in Server Admin. I have no idea why there are not being delivered
    Ive checked my postfix main.cf file and master.cf files they both look ok.. Ive even replaced them with the main.cf.defualt.10.7 and master.cf.default.10.7 files and to no avail... same problem..
    So in summary
    I can send mail out
    IMAP is working on the client end (thus dovecot is) exsisting stored emails can be accessed, read, moved unread etc..
    mail is coming into the sever, but its being rejected. there is NO rejection email sent back to the sender.
    mail is recieved by postfix, but cyrus isnt doing anything with it.. I have no idea where it goes...
    Could anyone shed light on this...
    my main.cf file:
    # Global Postfix configuration file. This file lists only a subset
    # of all 300+ parameters. See the postconf(5) manual page for a
    # complete list.
    # The general format of each line is: parameter = value. Lines
    # that begin with whitespace continue the previous line. A value can
    # contain references to other $names or ${name}s.
    # NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
    # POSTFIX STILL WORKS AFTER EVERY CHANGE.
    # SOFT BOUNCE
    # The soft_bounce parameter provides a limited safety net for
    # testing.  When soft_bounce is enabled, mail will remain queued that
    # would otherwise bounce. This parameter disables locally-generated
    # bounces, and prevents the SMTP server from rejecting mail permanently
    # (by changing 5xx replies into 4xx replies). However, soft_bounce
    # is no cure for address rewriting mistakes or mail routing mistakes.
    # soft_bounce = no
    # LOCAL PATHNAME INFORMATION
    # The queue_directory specifies the location of the Postfix queue.
    # This is also the root directory of Postfix daemons that run chrooted.
    # See the files in examples/chroot-setup for setting up Postfix chroot
    # environments on different UNIX systems.
    queue_directory = /private/var/spool/postfix
    # The command_directory parameter specifies the location of all
    # postXXX commands.
    command_directory = /usr/sbin
    # The daemon_directory parameter specifies the location of all Postfix
    # daemon programs (i.e. programs listed in the master.cf file). This
    # directory must be owned by root.
    daemon_directory = /usr/libexec/postfix
    # QUEUE AND PROCESS OWNERSHIP
    # The mail_owner parameter specifies the owner of the Postfix queue
    # and of most Postfix daemon processes.  Specify the name of a user
    # account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
    # AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM.  In
    # particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
    # USER.
    mail_owner = _postfix
    # The default_privs parameter specifies the default rights used by
    # the local delivery agent for delivery to external file or command.
    # These rights are used in the absence of a recipient user context.
    # DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
    #default_privs = nobody
    # INTERNET HOST AND DOMAIN NAMES
    # The myhostname parameter specifies the internet hostname of this
    # mail system. The default is to use the fully-qualified domain name
    # from gethostname(). $myhostname is used as a default value for many
    # other configuration parameters.
    #myhostname = host.domain.tld
    #myhostname = virtual.domain.tld
    # The mydomain parameter specifies the local internet domain name.
    # The default is to use $myhostname minus the first component.
    # $mydomain is used as a default value for many other configuration
    # parameters.
    #mydomain = domain.tld
    # SENDING MAIL
    # The myorigin parameter specifies the domain that locally-posted
    # mail appears to come from. The default is to append $myhostname,
    # which is fine for small sites.  If you run a domain with multiple
    # machines, you should (1) change this to $mydomain and (2) set up
    # a domain-wide alias database that aliases each user to
    # [email protected].
    # For the sake of consistency between sender and recipient addresses,
    # myorigin also specifies the default domain name that is appended
    # to recipient addresses that have no @domain part.
    #myorigin = $myhostname
    #myorigin = $mydomain
    # RECEIVING MAIL
    # The inet_interfaces parameter specifies the network interface
    # addresses that this mail system receives mail on.  By default,
    azathoth:postfix root#
    azathoth:postfix root# less main.cf
    azathoth:postfix root# more main.cf
    # Global Postfix configuration file. This file lists only a subset
    # of all 300+ parameters. See the postconf(5) manual page for a
    # complete list.
    # The general format of each line is: parameter = value. Lines
    # that begin with whitespace continue the previous line. A value can
    # contain references to other $names or ${name}s.
    # NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
    # POSTFIX STILL WORKS AFTER EVERY CHANGE.
    # SOFT BOUNCE
    # The soft_bounce parameter provides a limited safety net for
    # testing.  When soft_bounce is enabled, mail will remain queued that
    # would otherwise bounce. This parameter disables locally-generated
    # bounces, and prevents the SMTP server from rejecting mail permanently
    # (by changing 5xx replies into 4xx replies). However, soft_bounce
    # is no cure for address rewriting mistakes or mail routing mistakes.
    # soft_bounce = no
    # LOCAL PATHNAME INFORMATION
    # The queue_directory specifies the location of the Postfix queue.
    # This is also the root directory of Postfix daemons that run chrooted.
    # See the files in examples/chroot-setup for setting up Postfix chroot
    # environments on different UNIX systems.
    queue_directory = /private/var/spool/postfix
    # The command_directory parameter specifies the location of all
    # postXXX commands.
    command_directory = /usr/sbin
    # The daemon_directory parameter specifies the location of all Postfix
    # daemon programs (i.e. programs listed in the master.cf file). This
    # directory must be owned by root.
    daemon_directory = /usr/libexec/postfix
    # QUEUE AND PROCESS OWNERSHIP
    # The mail_owner parameter specifies the owner of the Postfix queue
    # and of most Postfix daemon processes.  Specify the name of a user
    # account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
    # AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM.  In
    # particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
    # USER.
    mail_owner = _postfix
    # The default_privs parameter specifies the default rights used by
    # the local delivery agent for delivery to external file or command.
    # These rights are used in the absence of a recipient user context.
    # DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
    #default_privs = nobody
    # INTERNET HOST AND DOMAIN NAMES
    # The myhostname parameter specifies the internet hostname of this
    # mail system. The default is to use the fully-qualified domain name
    # from gethostname(). $myhostname is used as a default value for many
    # other configuration parameters.
    #myhostname = host.domain.tld
    #myhostname = virtual.domain.tld
    # The mydomain parameter specifies the local internet domain name.
    # The default is to use $myhostname minus the first component.
    # $mydomain is used as a default value for many other configuration
    # parameters.
    #mydomain = domain.tld
    # SENDING MAIL
    # The myorigin parameter specifies the domain that locally-posted
    # mail appears to come from. The default is to append $myhostname,
    # which is fine for small sites.  If you run a domain with multiple
    # machines, you should (1) change this to $mydomain and (2) set up
    # a domain-wide alias database that aliases each user to
    # [email protected].
    # For the sake of consistency between sender and recipient addresses,
    # myorigin also specifies the default domain name that is appended
    # to recipient addresses that have no @domain part.
    #myorigin = $myhostname
    #myorigin = $mydomain
    # RECEIVING MAIL
    # The inet_interfaces parameter specifies the network interface
    # addresses that this mail system receives mail on.  By default,
    # the software claims all active interfaces on the machine. The
    # parameter also controls delivery of mail to user@[ip.address].
    # See also the proxy_interfaces parameter, for network addresses that
    # are forwarded to us via a proxy or network address translator.
    # Note: you need to stop/start Postfix when this parameter changes.
    #inet_interfaces = all
    #inet_interfaces = $myhostname
    #inet_interfaces = $myhostname, localhost
    # The proxy_interfaces parameter specifies the network interface
    # addresses that this mail system receives mail on by way of a
    # proxy or network address translation unit. This setting extends
    # the address list specified with the inet_interfaces parameter.
    # You must specify your proxy/NAT addresses when your system is a
    # backup MX host for other domains, otherwise mail delivery loops
    # will happen when the primary MX host is down.
    #proxy_interfaces =
    #proxy_interfaces = 1.2.3.4
    # The mydestination parameter specifies the list of domains that this
    # machine considers itself the final destination for.
    # These domains are routed to the delivery agent specified with the
    # local_transport parameter setting. By default, that is the UNIX
    # compatible delivery agent that lookups all recipients in /etc/passwd
    # and /etc/aliases or their equivalent.
    # The default is $myhostname + localhost.$mydomain.  On a mail domain
    # gateway, you should also include $mydomain.
    # Do not specify the names of virtual domains - those domains are
    # specified elsewhere (see VIRTUAL_README).
    # Do not specify the names of domains that this machine is backup MX
    # host for. Specify those names via the relay_domains settings for
    # the SMTP server, or use permit_mx_backup if you are lazy (see
    # STANDARD_CONFIGURATION_README).
    # The local machine is always the final destination for mail addressed
    # to user@[the.net.work.address] of an interface that the mail system
    # receives mail on (see the inet_interfaces parameter).
    # Specify a list of host or domain names, /file/name or type:table
    # patterns, separated by commas and/or whitespace. A /file/name
    # pattern is replaced by its contents; a type:table is matched when
    # a name matches a lookup key (the right-hand side is ignored).
    # Continue long lines by starting the next line with whitespace.
    # See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
    #mydestination = $myhostname, localhost.$mydomain, localhost
    #mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
    #mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain,
    #       mail.$mydomain, www.$mydomain, ftp.$mydomain
    # REJECTING MAIL FOR UNKNOWN LOCAL USERS
    # The local_recipient_maps parameter specifies optional lookup tables
    # with all names or addresses of users that are local with respect
    # to $mydestination, $inet_interfaces or $proxy_interfaces.
    # If this parameter is defined, then the SMTP server will reject
    # mail for unknown local users. This parameter is defined by default.
    # To turn off local recipient checking in the SMTP server, specify
    # local_recipient_maps = (i.e. empty).
    # The default setting assumes that you use the default Postfix local
    # delivery agent for local delivery. You need to update the
    # local_recipient_maps setting if:
    # - You define $mydestination domain recipients in files other than
    #   /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
    #   For example, you define $mydestination domain recipients in   
    #   the $virtual_mailbox_maps files.
    # - You redefine the local delivery agent in master.cf.
    # - You redefine the "local_transport" setting in main.cf.
    # - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
    #   feature of the Postfix local delivery agent (see local(8)).
    # Details are described in the LOCAL_RECIPIENT_README file.
    # Beware: if the Postfix SMTP server runs chrooted, you probably have
    # to access the passwd file via the proxymap service, in order to
    # overcome chroot restrictions. The alternative, having a copy of
    # the system passwd file in the chroot jail is just not practical.
    # The right-hand side of the lookup tables is conveniently ignored.
    # In the left-hand side, specify a bare username, an @domain.tld
    # wild-card, or specify a [email protected] address.
    #local_recipient_maps = unix:passwd.byname $alias_maps
    #local_recipient_maps = proxy:unix:passwd.byname $alias_maps
    #local_recipient_maps =
    # The unknown_local_recipient_reject_code specifies the SMTP server
    # response code when a recipient domain matches $mydestination or
    # ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
    # and the recipient address or address local-part is not found.
    # The default setting is 550 (reject mail) but it is safer to start
    # with 450 (try again later) until you are certain that your
    # local_recipient_maps settings are OK.
    unknown_local_recipient_reject_code = 550
    # TRUST AND RELAY CONTROL
    # The mynetworks parameter specifies the list of "trusted" SMTP
    # clients that have more privileges than "strangers".
    # In particular, "trusted" SMTP clients are allowed to relay mail
    # through Postfix.  See the smtpd_recipient_restrictions parameter
    # in postconf(5).
    # You can specify the list of "trusted" network addresses by hand
    # or you can let Postfix do it for you (which is the default).
    # By default (mynetworks_style = subnet), Postfix "trusts" SMTP
    # clients in the same IP subnetworks as the local machine.
    # On Linux, this does works correctly only with interfaces specified
    # with the "ifconfig" command.
    # Specify "mynetworks_style = class" when Postfix should "trust" SMTP
    # clients in the same IP class A/B/C networks as the local machine.
    # Don't do this with a dialup site - it would cause Postfix to "trust"
    # your entire provider's network.  Instead, specify an explicit
    # mynetworks list by hand, as described below.
    # Specify "mynetworks_style = host" when Postfix should "trust"
    # only the local machine.
    #mynetworks_style = class
    #mynetworks_style = subnet
    #mynetworks_style = host
    # Alternatively, you can specify the mynetworks list by hand, in
    # which case Postfix ignores the mynetworks_style setting.
    # Specify an explicit list of network/netmask patterns, where the
    # mask specifies the number of bits in the network part of a host
    # address.
    # You can also specify the absolute pathname of a pattern file instead
    # of listing the patterns here. Specify type:table for table-based lookups
    # (the value on the table right-hand side is not used).
    #mynetworks = 168.100.189.0/28, 127.0.0.0/8
    #mynetworks = $config_directory/mynetworks
    #mynetworks = hash:/etc/postfix/network_table
    # The relay_domains parameter restricts what destinations this system will
    # relay mail to.  See the smtpd_recipient_restrictions description in
    # postconf(5) for detailed information.
    # By default, Postfix relays mail
    # - from "trusted" clients (IP address matches $mynetworks) to any destination,
    # - from "untrusted" clients to destinations that match $relay_domains or
    #   subdomains thereof, except addresses with sender-specified routing.
    # The default relay_domains value is $mydestination.
    # In addition to the above, the Postfix SMTP server by default accepts mail
    # that Postfix is final destination for:
    # - destinations that match $inet_interfaces or $proxy_interfaces,
    # - destinations that match $mydestination
    # - destinations that match $virtual_alias_domains,
    # - destinations that match $virtual_mailbox_domains.
    # These destinations do not need to be listed in $relay_domains.
    # Specify a list of hosts or domains, /file/name patterns or type:name
    # lookup tables, separated by commas and/or whitespace.  Continue
    # long lines by starting the next line with whitespace. A file name
    # is replaced by its contents; a type:name table is matched when a
    # (parent) domain appears as lookup key.
    # NOTE: Postfix will not automatically forward mail for domains that
    # list this system as their primary or backup MX host. See the
    # permit_mx_backup restriction description in postconf(5).
    #relay_domains = $mydestination
    # INTERNET OR INTRANET
    # The relayhost parameter specifies the default host to send mail to
    # when no entry is matched in the optional transport(5) table. When
    # no relayhost is given, mail is routed directly to the destination.
    # On an intranet, specify the organizational domain name. If your
    # internal DNS uses no MX records, specify the name of the intranet
    # gateway host instead.
    # In the case of SMTP, specify a domain, host, host:port, [host]:port,
    # [address] or [address]:port; the form [host] turns off MX lookups.
    # If you're connected via UUCP, see also the default_transport parameter.
    #relayhost = $mydomain
    #relayhost = [gateway.my.domain]
    #relayhost = [mailserver.isp.tld]
    #relayhost = uucphost
    #relayhost = [an.ip.add.ress]
    # REJECTING UNKNOWN RELAY USERS
    # The relay_recipient_maps parameter specifies optional lookup tables
    # with all addresses in the domains that match $relay_domains.
    # If this parameter is defined, then the SMTP server will reject
    # mail for unknown relay users. This feature is off by default.
    # The right-hand side of the lookup tables is conveniently ignored.
    # In the left-hand side, specify an @domain.tld wild-card, or specify
    # a [email protected] address.
    #relay_recipient_maps = hash:/etc/postfix/relay_recipients
    # INPUT RATE CONTROL
    # The in_flow_delay configuration parameter implements mail input
    # flow control. This feature is turned on by default, although it
    # still needs further development (it's disabled on SCO UNIX due
    # to an SCO bug).
    # A Postfix process will pause for $in_flow_delay seconds before
    # accepting a new message, when the message arrival rate exceeds the
    # message delivery rate. With the default 100 SMTP server process
    # limit, this limits the mail inflow to 100 messages a second more
    # than the number of messages delivered per second.
    # Specify 0 to disable the feature. Valid delays are 0..10.
    #in_flow_delay = 1s
    # ADDRESS REWRITING
    # The ADDRESS_REWRITING_README document gives information about
    # address masquerading or other forms of address rewriting including
    # username->Firstname.Lastname mapping.
    # ADDRESS REDIRECTION (VIRTUAL DOMAIN)
    # The VIRTUAL_README document gives information about the many forms
    # of domain hosting that Postfix supports.
    # "USER HAS MOVED" BOUNCE MESSAGES
    # See the discussion in the ADDRESS_REWRITING_README document.
    # TRANSPORT MAP
    # See the discussion in the ADDRESS_REWRITING_README document.
    # ALIAS DATABASE
    # The alias_maps parameter specifies the list of alias databases used
    # by the local delivery agent. The default list is system dependent.
    # On systems with NIS, the default is to search the local alias
    # database, then the NIS alias database. See aliases(5) for syntax
    # details.
    # If you change the alias database, run "postalias /etc/aliases" (or
    # wherever your system stores the mail alias file), or simply run
    # "newaliases" to build the necessary DBM or DB file.
    # It will take a minute or so before changes become visible.  Use
    # "postfix reload" to eliminate the delay.
    #alias_maps = dbm:/etc/aliases
    #alias_maps = hash:/etc/aliases
    #alias_maps = hash:/etc/aliases, nis:mail.aliases
    #alias_maps = netinfo:/aliases
    # The alias_database parameter specifies the alias database(s) that
    # are built with "newaliases" or "sendmail -bi".  This is a separate
    # configuration parameter, because alias_maps (see above) may specify
    # tables that are not necessarily all under control by Postfix.
    #alias_database = dbm:/etc/aliases
    #alias_database = dbm:/etc/mail/aliases
    #alias_database = hash:/etc/aliases
    #alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
    # ADDRESS EXTENSIONS (e.g., user+foo)
    # The recipient_delimiter parameter specifies the separator between
    # user names and address extensions (user+foo). See canonical(5),
    # local(8), relocated(5) and virtual(5

    Ok 1st one. The warning restriction message relates to this line in main.cf:
    smtpd_helo_restrictions = permit_sasl_authenticated  permit_mynetworks  check_helo_access hash:/etc/postfix/helo_access  reject_non_fqdn_hostname  reject_invalid_hostname  permit reject_invalid_helo_hostname
    The last reject occurs after the single word "permit" and is ignored.
    However, that's not the problem.
    I'm not exactly sure what's happening, but this might be a clue.
    It would appear that either postfix is not being able to create the socket for private/policy or it's somehow created with the wrong permissions.  You might need to ramp up the debug level to get a better idea.
    You could check if it's being created by "netstat -a | grep private/policy" in terminal.
    My guess is that it's not being created because there is no setup statement in your master.cf file, but I don't understand why postfix would be looking for it if it isn't set up.  Private/policy I think relates to grey listing.  Maybe gives you a hint.

  • Error message while importing transport request using STMS_IMPORT

    Hello SAP gurus
    I have created Transport Request files (K and R files_ and have placed Transport request files in  trans and data directories of a target system.
    On target system I started transaction code  STMS_IMPORT and then selected
    Extras -> Other Requests -> Add
    Then selected the transport request number adn clicked on OK.  I have done this before and had not seen the problem that I am seeing now.
    At this point I get an error message 
    Transport control program tp ended with error code 0212
    Errors: could not access file as supposed (see dev_tp or S
    What am I doing wrong? Any suggestion or feedback will be highly appreciated.
    Thanks
    Ram

    Thanks a lot Friends
    I followed your instructions and so far here is what I have done.
    Since this is just a test server, I have given full permissions to /usr directory and all the files and directories below that.
    The user account is a copy of J2EE_ADMIN. I have also added   'SAP_ALL', 'S_TMW_IMPORT' Profiles.
    I am attaching the log which still indicates that there is permission problem.
    Any other suggestion will be highly appreciated.
        File: 
    TESTSERV\sapmnt\trans\log\SLOG1045.ERM                               08.11.2010 07:32:39
    System Log Entries
    HALT 20101107074318
    ERROR:
    TESTSERV\sapmnt\trans\cofiles\K900082.DEM : cant open
    : Permission denied
    ERROR: EXIT(16) -> process ID is: 4204
    HALT 20101107080535
    ERROR:
    TESTSERV\sapmnt\trans\cofiles\K900082.DEM : cant open
    : Permission denied
    ERROR: EXIT(16) -> process ID is: 2984
    HALT 20101108065543
    ERROR:
    TESTSERV\sapmnt\trans\cofiles\K900082.DEM : cant open
    : Permission denied
    ERROR: EXIT(16) -> process ID is: 3428
    HALT 20101108071027
    ERROR:
    TESTSERV\sapmnt\trans\cofiles\K900083.DEM : cant open
    : Permission denied
    ERROR: EXIT(16) -> process ID is: 1256
    HALT 20101108071725
    ERROR:
    TESTSERV\sapmnt\trans\cofiles\K900083.DEM : cant open
    : Permission denied
    ERROR: EXIT(16) -> process ID is: 4192
    HALT 20101108072313
    ERROR:
    TESTSERV\sapmnt\trans\cofiles\K900083.DEM : cant open
    : Permission denied
    ERROR: EXIT(16) -> process ID is: 3904
    HALT 20101108073220
    ERROR:
    TESTSERV\sapmnt\trans\cofiles\K900083.DEM : cant open
    : Permission denied
    ERROR: EXIT(16) -> process ID is: 5252

  • Transport control program tp ended with error code 0211

    Dear Experts,
    I have a problem in doing the import after the client export was successfully done.
    I am actaully tring to do a client import/export from the PRD server to DEV server.
    On PRD the client is 900 and on the DEV the client is 240.
    I have manually copied the transport requests created into the
    /usr/sap/trans/cofiles and /usr/sap/trans/data folders to the same on the DEV server.
    After coping them,
    I have tried to add these transport requests to the DEV server queue, i get the following error message
    Transport control program tp ended with error code 0211
    Message no. XT200
    Diagnosis
    An error occurred when executing a tp command.
      Command: ADDTOBUFFER RT2KT00014 RT1 pf=/usr/sap/trans/bin/T
      Return code: 0211
      Error text: no info about transport request found
      Request: RT2KT00014
    System Response
    The function terminates.
    Procedure
    Correct the error and execute the command again if necessary.
    After this I have tried to add the transports to the buffer at the OS level using the command
    ./tp pf=TPPARAM addtobuffer "RT2KT00014" RT1 U18 by going to the folder
    /usr/sap/trans/bin
    But it says that the tp is not found.
    I have also checked the permissions for the TRANS folder, it has full access i.e 777
    This is where i am struck, and the client has to be imported asap as the requirement for the SUPPORT TEAM is very urgent.
    We are on AIX, Oracle 10G and ECC6
    Thanks and regards
    Harry

    Dear Imtiaz,
    Thanks for your quick fire reply...
    The link helped me but it could not resolve my issue..
    Infact i found it my self that the transport requests had to be given full FILE PERMISSIONS at the OS level
    I logged in as ROOT
    and changed directory to /usr/sap/trans/cofile and gave the command
    chmod 777 RT00014.RT2 and
    chmod 777 RX00014.RT2
    and then went to STMS>SYSTEMS>Import View>Extras>Other requests--> Add ..
    Here i added the request nos and then it added up in the queue and then i started the import.
    Anyway thank you very for your reply..
    Awareded points to you.
    Thanks and regards
    Harry...

  • Test call of transport control program (tp) ended with return code 0249

    Hi,
    When i release a TR i get the following error
    Pls let me know of what can be the reason for the same
    I did a kernel upgrade 2 days back
    Test call of transport control program (tp) ended with return code 0249
    Message no. TK094
    Diagnosis
    Your transport request could not be exported, since all requirements were not fulfilled.
    Calling the transport control program tp
       "tp EXPCHK BWDK900308 pf=
    WDBSSAPBWD01\sapmnt\trans\bin\TP_DOMAIN_BWD.PFL -Dtransdi"
    which checks the export requirements, returned the following information:
    Return code from tp: 0249
    Error text from tp: ERROR: No connect due to DbSl Load Lib Failure
    System Response
    Further processing is terminated.
    Procedure
    Check the following points:
    u2022     Feasibility of the transport control program tp
    u2022     Parameter settings in the transport profile
    u2022     Availability of the transport directory and the subdirectories (cofiles, data, log, sapnames, bin)
    u2022     Write authorization for the subdirectories
    u2022     Write authorization for the files of the subdirectories cofiles, data, log, sapnames
    Release the request again when the error has been removed

    Hi Balaji,
    End of your question contains the areas to be varified.
    Your SAP seems to be installed in windows environment
    Check transport profile paramater and file permissions.
    Try to browse the directory
    WDBSSAPBWD01\sapmnt\trans\bin\ from start->run
    Check with tp connecting to DB  with tp connect <SID>
    chceck file permission to datafile and cofiles (in case of OS UNIX)
    Regards,
    Ganesh

Maybe you are looking for