Private discoverer connections not visible in combobox in portal

We are using:
Oracle Portal Version: 10.1.2.0.2 (Build: 139)
Oracle AS BI & Forms: 10.1.2 (without any additional patches)
SSO has been enabled for discoverer using the mod_osso.conf configuration and works correctly. We are able to create private connections in the discoverer plus login screen that is shown after SSO authentication and we have checked that they get populated in the table orasso.wwsso_psex_user_info$.
Discoverer Portlets have been installed and the provider has been configured and we can correctly add the portlets to the portal page.
The problem we have is the following:
Even though in the portlet configuration we have chosen the option "Display different data by allowing users to customize database connection", when the user chooses to customize the portlet and choose his private connection, only the public connection shows up in the list.
Has anyone else encountered this problem and found a solution?
Thanks in advance

We encountered the same problem. Oracle had us reinstall AS with the middle-tier and BI-tier on the same port. After that we could see the private connections through Portal.
Follow-up with Oracle for more information -- I only know the solution overview, not the details.
Jeff Kanel

Similar Messages

  • Work items are not visible under UWL in portal ?

    Hi,
    We are upgrading from SRM 5.0 to SRM 7.0.
    We have observed one issue here. Workitems are not visible in UWL in portal.
    But workitems are available in SAP inbox. i.e SBWP.
    Completed items we can see in UWL.
    Could you please let me know any idea on this.
    Regards
    Venkatesh P
    Edited by: Venkatesh Padarti on Dec 9, 2010 8:28 AM
    Edited by: Venkatesh Padarti on Dec 9, 2010 8:29 AM

    Hi Venkatesh,
    Can you please share the solution? Which base URL was wrong and where did you correct that?
    Your help is really appreciated.
    I had post the same question at SRM workflow - work Item is not being displayed If you want to reply there. I will definitely, reward with points too.
    Thanks,
    Bhavik

  • Msmq private queue is not visible on windows 2008 r2

    Hello
    MSMQ privte queue are disappeared from the console. when i try to create a new queue with same name it says that entry is already there.
    I am able to see the msmq status on the event viewer ,we use vcs cluster
    is it some permission issue and or it configuration mismatch on the vcs cluster
    Regards

    Hi,
    Please see if this is the issue. Try the workaround provided by this KB:
    Some private queues may not appear or may disappear when you update the view in the Computer Management window
    http://support.microsoft.com/kb/839928/en-us
    And here is an article about the issue:
    "Where have my MSMQ messages gone?"
    http://blogs.msdn.com/b/johnbreakwell/archive/2010/01/22/why-does-msmq-keep-losing-my-messages.aspx?Redirected=true
    If you have any feedback on our support, please send to [email protected]

  • Discoverer report not visible

    Hello,
    i logged into discoverer plus using Sysadmin user but still i couldn't see some reports whose owner is some other user. How to see all the reports available in Discoverer Plus? Using which user and responsibility should i login for that?
    Your help is greatly appreciated.
    Thanks
    --Kumar                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

    Hi Rod,
    Like always, thanks for your help but here a consultant has created some discoverer reports last year using the login details of our users. Now he is not here anymore and if we want to change something in the report, we have to request the user to grant access of the report to SYSADMIN or our username which is really a frustrating. I'm surprised why we don't have any super user to have access to all the reports....
    Thanks
    --KK                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Wireless connection not visible on Vista laptop using Time capsule

    Change setup with Time capsule 1 TB, all MAC PC's work perfectly with wireless connection, except Vista laptop.
    Vista discovers all other wireless connections except the one from Time capsule.
    On advise from forum, changed Airport settings :
    - Radio mode = 802/a - 802/g"
    - Wireless security to "none"
    Which other setting on Vista prevents at least discovering the wireless signal ?
    Thanks for your support !
    Pascal

    I believe the problem has to do with some potential compatibility issue between the SP3 update and the currently installed Boot Camp drivers. Did you make sure that you (re)installed the latest Boot Camp drivers after you performed the SP3 update?
    (ref: Apple Support: Installing Boot Camp drivers)
    Also, the following firmware update may help as well: MacBook EFI Firmware Update 1.1

  • Document icon is not visible when run in portal.

    Dear Experts,
    I have a query and a character in query has been attached a document from BI Documents i am able to see the icon of document adjacent to the matching cell when i run the query in Bex Analyzer and also in RSRT1 transaction but not able to see the same when i see it i portal.
    What needs to be done inorder to see the same icon in [portal also.
    thanks and regards
    Neel

    Hi,
    In order to display the document icon in portal use Analysis, Single Document and Document List Web items properties.
    For reference please check this link:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.highlightedcontent?documenturi=%2fhelp%2fsdn_help_nw04s%2fsaphelp_nw04s%2fhelpdata%2fen%2f60%2f1c143bfaed272de10000000a11402f%2fcontent.htm
    Hope it helps.
    Regards,
    Mona

  • Work items are not visible  UWL task are visible in tracking in portal

    HI
    Friends
    i  am new from sap Ess/Mss implementation project...
    i am facing an Problem " Work items are not visible under UWL in portal overview page"
    but i am configured  all the ess/mss related things....and also Created for one user for Requester(send Leave Request)...and one more user for App-rover(Apporve an Leave)..
    Requestor send an Leave through portal send it successfully......but i am facing  a problem in uwl under work items are not showing in overview page...but in tracking work items are (Leave request)showing.....work items are not showing in uwl TASK(VERY PROBLEM)...
    i am configured and also registered UWL IN PORTAL..it is good..
    in sap ecc i can assigned UWL_SERVICE user to roles
    1.SAP_BC_BMT_WFM_UWL_ADMIN    
    2.SAP_BC_BMT_WFM_UWL_END_USER
    3.SAP_BC_ADMIN_USER
    4.SAP_BC_UWL_SERVICE
    PLEASE HELP ME.
    Tanks
    Shaik Rafi

    Hi All,
    In such cases, please try to check as below :
    1) Create Leave request work item from Employee and check the same under the UWL Tracking tab of employee.
    2) Log-in to swi5 transaction of the respective back end system and give "US" -> manager's UserID -> Choose Tasks to be completed from the drop down -> Remove any date if mentioned -> Execute.
    3) Here if you can see the Leave request created, but not on the portal, it reflects some portal issue like sync.
    4) If no leave request work item is seen here, then there is a problem in the employee manager mapping or the workflow setup.
    5) In such cases, you can try to check the Swi1 and check the log of that workflow to understand the current status of the Leave request.
    Revert if further help is needed with more info.
    Reward points if found useful.
    Regards,
    Shri vidya S

  • Portal Roles are not visible

    Hi,
    We have upgraged Portal (Nw 2004s) SP17 to SP18 ,But after upgradation portal roles are not visible for users and Portal adminstors (J2EE_ADMIN ) also.
    Standard roles like System ,user and Content Admin roles also not visible.It shows only blank screen after login to portal.
    It is critial issue .Please suggest how to solve this issue.
    Thanks
    Srikanth M

    Make sure there are no errors in the browser in the bottom left hand corner. Also, are you using a fully wualified name to access the portal? When you were on SP17 were you using standard roles or did you make your own copy of the roles and assign your users to the copied roles?
    If you navigate to the portal content studio directly, can you see the role contents?
    After launching /useradmin and authenticating, paste http://host:50000/irj/servlet/prt/portal/prtmode/preview/prtroot/pcd!3aportal_content!2fadministrator!2fcontent_admin!2fcontent_admin_role!2fcom.sap.portal.content_admin_ws!2fcom.sap.portal.portal_content?sap-config-mode=true into your browser and you are in the content studio.

  • Connecting a KM repository from another portal to KM via WebDAV - meda data

    Hello there,
    we are evaluating the option of connecting a KM repository from another portal to KM via WebDAV in our Federated Portal Scenario (in fact, we wish to get rid of the the remote roles as soon as possible).
    This can be accomplised as described here [Connecting a KM repository from another portal to KM via WebDAV|https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/2783].
    Or for BI as described in Note 969040 - Federated portal network and Information Broadcasting .
    One question : in case meta- data properties are set, where are these stored? In the consumer portal, or in the source system, the producer portal?
    I.e when I set properties on documents of the WebDav repository, and I go to the source system, will the same meta- data properties be set there?
    Many thanks!

    For testing I've integrated the remote KM repository as WebDAV and enabled the properties repository service :
    - custom meta- data defined on the source (producer) KM system is not visible in the consumer portal if no value has been set on the source system :
    Let's say you have a property 'country' on the source system, define a value for it + save, you can view the property in the consumer system.
    - if you define both the same properties in consumer & producser system, you can view the properties in both system, and the value set in either one of the systems is displayed in both of them.
    In short : the custom meta-data properties need to be defined on both systems

  • 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.

  • Old connections not showing on Discoverer Connections page after a REFRESH

    Hello all,
    I am having a weird issue with Discoverer connections after a recent refresh of our DEV AS environment from TST.
    Before I proceed further, let me give you some details on our environments.
    We have recently upgraded our version 9.0.4.1 AS DEV and TST environments to version 10.1.2.3. We also patched our Portal to version 10.1.4.2. Our Infrastructure, Middle Tier, and Metadata Repository Oracle Homes are on one host (AIX 5.3), and our Portal Repository (Customer) database is located on another host (AIX 5.3). Our Repository databases are version 9.2.0.8.
    That said, this is my first refresh attempt at version 10.1.2.3. I was able to complete the refresh (after troubleshooting some issues) fine and was able to bring our DEV Portal up and things looked fine. But when I get to the Discoverer Viewer connections page, I don't see any connections listed there.
    During the refresh I did an "ssomig -export" and "ssomig -import" successfully and the logs showed no errors. When I look in the ORASSO.WWSSO_PSEX_USER_INFO$ table, I can see the Connections data. But somehow from the Discoverer connections page nothing is visible. If I create a new connection, everything seems to be normal with the way Discoverer works. But I am not able to figure out how to make the old connections show up on the Connections page.
    I have tried doing an "ssomig -import" a couple of times with no luck. Can anyone help me out? I am not sure what is going on.
    Thanks.
    CV

    This is not a support site but a community forum. For direct help purchase a case on line

  • Why are shared files not visible when iPhone4S connected to iTunes?

    What makes this problem mysterious is that I have exactly the same settings on the same or eqivalent Apps on iPad2 and iTunes4S but when my iPhone is connected to my iTunes (running on my PC under Win7) it shows no files on Apps like Pages, iBooks, Keynote, and Print-n-share.  Each of these Apps has files and each shows files when  I connect my iPad2.   I cannot export or import filesto/from itunes and iphone because the list of files inside the Apps is not visible in itunes. 
    PS I CAN, btw, export and import files by using the amazing App and service "DropBox" which is the only route in and out of my iPhone (I am not ready to use iCloud).

    This is not a reply but an addition.  While searching for answers as to why "Shared" files in original Apps in my iPhone4S did not appear on itunes I came across a similar discussion on another Forum in which Jim described in some detail how to get the two devices (my iPhone 4S and my iPad2) to recognize similar embedded files in similar Apps.  https://discussions.apple.com/message/16690584#16690584
    I went through this promising procedure but it did not help.  Since the two devices are independent (I think -- they are on the same accoubt but ar different devices) I should be able to make them work the same way with regard to what is seem in iTune.

  • Hi every one if i connect wired headset to my new iPad it is not showing a headphone connected symbol .is it by default not visible or something happen thanks in advance

    Hi every one if i connect wired headset to my new iPad it is not showing a headphone connected symbol .is it by default not visible or something happen thanks in advance

    When you have kernel panics, the pertinent information is in the panic report.
    These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad and start typing the name.
    In the Console window, select
              DIAGNOSTIC AND USAGE INFORMATION ▹ System Diagnostic Reports
    (not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select
              View ▹ Show Log List
    from the menu bar.
    There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A panic report has a name that begins with "Kernel" and ends in ".panic". Select the most recent one. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.
    If you don't see any reports listed, but you know there was a panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
    In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
    Please don’t post other kinds of diagnostic report.
    I know the report is long, maybe several hundred lines. Please post all of it anyway.

  • Time Capsule not visible when connecting via range extender

    Hi,
    I have configured a TP-Link WA750RE to expand the range of my Time Capsule's wireless network. The range extender works fine for surfing the web etc., but the Time Capsule doesn't show up as my Time Machine backup device and the Time Capsule is not visible in my Airport Utility. What's even stranger is that when I click on "Configure other" (shift + command + o) in Airport Utility and type in my Time Capsule's IP-address and password, I can still access the devices' configuration menu.
    When I move my Macbook very close to my Time Machine to connect directly to the wireless network, leaving out the range extender, none of the above mentioned problems occur. The TP-Link range extender has no NAT or port configuration that could possibly cause this problem, so I'm out of ideas for a way to solve this problem.
    Thank you in advance for your help.

    A non-apple range extender is not passing the protocols that apple uses.. eg bonjour.. This is a standard problem and why you stick with using Apple's own routers for extensions.

  • AirPort Extreme USB Connected Disk Drive Not Visible To Time Machine

    My AirPort Extreme USB connected disk drive is visible in the Finder and desktop. It is not visible to Time Machine. When I open Time Machine and bring up the "Choose Backup Disk" the AirPort Extreme USB connected disk drive is not visible.
    What am I missing here?

    Hi Pete Mackie-
    Nope. You aren't missing anything.
    Mac OS X 10.5: Time Machine doesn't back up to AirPort Disks
    Luck-
    -DaddyPaycheck

Maybe you are looking for

  • F-30: posting with clearing a document with special G/L indicator and tax

    Hi All, by t.code F-02 I've posted a document with the follow items: PK     SG      Account Description 40                Bank G/L Account   u20AC 1200,00 19      A       Customer code         u20AC 1000,00-  (1000,00 amount and 200,00 tax amount) 50

  • HP Officejet Pro X476dw ink cartridge failure

    I have a new HP Officejet Pro X476dw . It gives me Ink Failure for the four cartridges when I shut it down and turn it on the next day it starts to print but after a while it gives the same message . and so on I check the cartridge when it is working

  • Has anyone experienced file extensions not being recognised by the right program?

    I'm using CC -- the whole show, Win 7 Pro and Win 8 Pro on a second PC. Only the Win 7 system is showing this issue but both systems have identical software. Click on an inDesign file and Acrobat tries to open it. Click on a Photoshop file and a HDR

  • Sudden increase in disk space?

    I've been working with 20 GB or so available on my startup disk for around 6 months now. A couple of days ago I got the Startup Disk almost full message. I saved my work and rebooted. That solved the problem and I gained 3-4 GB. Yesterday morning sud

  • How to delete user on OS X? please help

    I accidentally added this user when I first setup the laptop, I tried so many ways and still couldn't delete it. Please help me to delete it. It really bothers me! thank you so much !!