Creation of iObject issue with Address

Hello All,
As per the requirement, we are trying to create the iObjects as a component of existing iBase in the system.
We are using the FM 'CRM_ICSS_CREATE_COMPONENT'.
The iObject is getting created, but we are passing the address data to is_address_data.
But the component is not having the Address maintained.
Kindly share your thoughts if I am missing something or other way to create the component with the address.
Thanks in Advance.
Regards,
Ravi

Hi Thomas Wagner,
Thanks for your reply.
I have already tried to find out in the way mentioned by you, but while doing from standard this FM is not getting triggered,
Regards,
Ravi

Similar Messages

  • Creation of service order with address data.

    Hello community,
    I have the following requirement: create maintenance orders with order address data, the creation of these orders will be triggered by an interface with a legacy system.
    For order creation I intend to use BAPI_ALM_ORDER_MAINTAIN but this function does not provide the possibility to enter address information.
    I would not like to have to create a partner and assign it to the order as this address will be used only once.
    Does anyone have suggestions how to do it ?.
    Thanks.
    Roberto.

    Roberto,
    Try this:
    *& Report  ZPJA_ADDR_TX
    report  zpja_addr_tx.
    data: lt_adrc  type  standard table of adrc with header line.
    data: lt_adrc1 type  standard table of addr1_data with header line.
    * get address from first object
    call function 'ADDR_SELECT_ADRC_SINGLE'
      exporting
        addrnumber        = '0000033071'
      tables
        et_adrc           = lt_adrc
      exceptions
        address_not_exist = 1
        parameter_error   = 2
        internal_error    = 3
        others            = 4.
    loop at lt_adrc.
      move-corresponding lt_adrc to lt_adrc1.
      lt_adrc1-name1 = sy-timlo.   " write current time for testing
      append lt_adrc1.
    endloop.
    * update second address
    call function 'ADDR_UPDATE'
      exporting
        address_data        = lt_adrc1
        address_number      = '0000033205'
        date_from           = '00010101'
        language            = sy-langu
        check_empty_address = ' '
        check_address       = ' '
      exceptions
        address_not_exist   = 1
        parameter_error     = 2
        version_not_exist   = 3
        internal_error      = 4
        others              = 5.
    call function 'ADDR_MEMORY_SAVE'.

  • I have an issue with the address browser in mail in Yosemite

    I am using IOS 10.10.1 now on an iMac and have discovered an issue with the address browser in mail.
    Previously in my pending to send email toolbar there was a contacts icon which I clicked  on to display my contacts list. I could hold down the Command button and select as many contacts I wanted (often up to 100), then select the field to send (to, ccc, bcc) and the contact would appear.
    Now, I have to click the + sign at the end of the field line, and select recipients one at a time. Not only that, but I have to click twice to get to the email address, once on the name and then the email address drops down under the name and then I click on the email address. When I do that the drop down box disappears and the recipient's email address goes to the field. I have tried all combinations of buttons to be able to choose multiple addresses but haven't found the right one yet.
    An Apple Support guy told me to open my regular Address book, and hold down the command button to choose multiple recipients then drag them to the field on my already opened send email.
    This is one way around the issue (which wasn't an issue in Mavericks) but where some recipients have two or more email addresses listed in my contacts it means I have to manually go through the finished list on my emails to make sure the most desired one was selected. What a pain.
    Also, previously, where I was sending out many emails and wanted to stop say half way down my list, and send, I could come back to that list for the next email and see where I'd got up to.
    I don't want to make groups because my recipients vary depending on what I am sending so my lists change constantly.
    Any suggestions?
    Last point...who archives? On my regular email page I now have the Archive icon to the left of my Delete icon which I would prefer was to the left, first in the line as this is the icon I use mostly. With Folders, my Sent and Trash lists, who needs to archive?
    Cheers,

    Last point...who archives? On my regular email page I now have the Archive icon to the left of my Delete icon which I would prefer was to the left, first in the line as this is the icon I use mostly. With Folders, my Sent and Trash lists, who needs to archive?
    I can help you only with the placement of the icon placement -- if you right-mouse click on the toolbar, then select Customize Toolbar, you can move an icon to where you want it to be.

  • [SOLVED]Issue with Postfix sending to external mail addresses

    I'm having a very silly issue with Postfix. I followed the wiki article at [link]https://wiki.archlinux.org/index.php/Postfix[/link], and everything seems to work properly, however I cannot send to emails outside of my domain.
    I get the error:
    550 5.1.1 <[email protected]>: Recipient address rejected: Local delivery only!
    Here is what the logs say:
    May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: connect from localhost.localdomain[127.0.0.1]
    May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: 091E011E3C: client=localhost.localdomain[127.0.0.1]
    May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: 091E011E3C: reject: RCPT from localhost.localdomain[127.0.0.1]: 550 5.1.1 <[email protected]>: Recipient address rejected: Local delivery only!; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<sendingdomain.com>
    May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: lost connection after RCPT from localhost.localdomain[127.0.0.1]
    May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: disconnect from localhost.localdomain[127.0.0.1]
    May 08 16:05:14 my.dns.stuff.org sudo[31476]: me : TTY=pts/0 ; PWD=/etc/postfix ; USER=root ; COMMAND=/usr/bin/journalctl
    main.cf
    # Global Postfix configuration file. This file lists only a subset
    # of all parameters. For the syntax, and for a complete parameter
    # list, see the postconf(5) manual page (command: "man 5 postconf").
    # For common configuration examples, see BASIC_CONFIGURATION_README
    # and STANDARD_CONFIGURATION_README. To find these documents, use
    # the command "postconf html_directory readme_directory", or go to
    # http://www.postfix.org/BASIC_CONFIGURATION_README.html etc.
    # For best results, 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 = /var/spool/postfix
    # The command_directory parameter specifies the location of all
    # postXXX commands.
    command_directory = /usr/bin
    # 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/lib/postfix
    # The data_directory parameter specifies the location of Postfix-writable
    # data files (caches, random numbers). This directory must be owned
    # by the mail_owner account (see below).
    data_directory = /var/lib/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 = mail.sendingdomain.com
    # 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 = www.sendingdomain.com
    # 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
    append_dot_mydomain = no
    # 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 = loopback-only
    #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
    #mydestination = localhost
    # 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]
    default_transport = error: Local delivery only!
    # 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
    alias_maps = hash:/etc/postfix/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
    alias_database = $alias_maps
    # 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) for the effects this has on
    # aliases, canonical, virtual, relocated and .forward file lookups.
    # Basically, the software tries user+foo and .forward+foo before
    # trying user and .forward.
    #recipient_delimiter = +
    # DELIVERY TO MAILBOX
    # The home_mailbox parameter specifies the optional pathname of a
    # mailbox file relative to a user's home directory. The default
    # mailbox file is /var/spool/mail/user or /var/mail/user. Specify
    # "Maildir/" for qmail-style delivery (the / is required).
    #home_mailbox = Mailbox
    home_mailbox = Maildir/
    # The mail_spool_directory parameter specifies the directory where
    # UNIX-style mailboxes are kept. The default setting depends on the
    # system type.
    #mail_spool_directory = /var/mail
    #mail_spool_directory = /var/spool/mail
    # The mailbox_command parameter specifies the optional external
    # command to use instead of mailbox delivery. The command is run as
    # the recipient with proper HOME, SHELL and LOGNAME environment settings.
    # Exception: delivery for root is done as $default_user.
    # Other environment variables of interest: USER (recipient username),
    # EXTENSION (address extension), DOMAIN (domain part of address),
    # and LOCAL (the address localpart).
    # Unlike other Postfix configuration parameters, the mailbox_command
    # parameter is not subjected to $parameter substitutions. This is to
    # make it easier to specify shell syntax (see example below).
    # Avoid shell meta characters because they will force Postfix to run
    # an expensive shell process. Procmail alone is expensive enough.
    # IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
    # ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
    #mailbox_command = /some/where/procmail
    #mailbox_command = /some/where/procmail -a "$EXTENSION"
    # The mailbox_transport specifies the optional transport in master.cf
    # to use after processing aliases and .forward files. This parameter
    # has precedence over the mailbox_command, fallback_transport and
    # luser_relay parameters.
    # Specify a string of the form transport:nexthop, where transport is
    # the name of a mail delivery transport defined in master.cf. The
    # :nexthop part is optional. For more details see the sample transport
    # configuration file.
    # NOTE: if you use this feature for accounts not in the UNIX password
    # file, then you must update the "local_recipient_maps" setting in
    # the main.cf file, otherwise the SMTP server will reject mail for
    # non-UNIX accounts with "User unknown in local recipient table".
    # Cyrus IMAP over LMTP. Specify ``lmtpunix cmd="lmtpd"
    # listen="/var/imap/socket/lmtp" prefork=0'' in cyrus.conf.
    #mailbox_transport = lmtp:unix:/var/imap/socket/lmtp
    # Cyrus IMAP via command line. Uncomment the "cyrus...pipe" and
    # subsequent line in master.cf.
    #mailbox_transport = cyrus
    # The fallback_transport specifies the optional transport in master.cf
    # to use for recipients that are not found in the UNIX passwd database.
    # This parameter has precedence over the luser_relay parameter.
    # Specify a string of the form transport:nexthop, where transport is
    # the name of a mail delivery transport defined in master.cf. The
    # :nexthop part is optional. For more details see the sample transport
    # configuration file.
    # NOTE: if you use this feature for accounts not in the UNIX password
    # file, then you must update the "local_recipient_maps" setting in
    # the main.cf file, otherwise the SMTP server will reject mail for
    # non-UNIX accounts with "User unknown in local recipient table".
    #fallback_transport = lmtp:unix:/file/name
    #fallback_transport = cyrus
    #fallback_transport =
    # The luser_relay parameter specifies an optional destination address
    # for unknown recipients. By default, mail for unknown@$mydestination,
    # unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned
    # as undeliverable.
    # The following expansions are done on luser_relay: $user (recipient
    # username), $shell (recipient shell), $home (recipient home directory),
    # $recipient (full recipient address), $extension (recipient address
    # extension), $domain (recipient domain), $local (entire recipient
    # localpart), $recipient_delimiter. Specify ${name?value} or
    # ${name:value} to expand value only when $name does (does not) exist.
    # luser_relay works only for the default Postfix local delivery agent.
    # NOTE: if you use this feature for accounts not in the UNIX password
    # file, then you must specify "local_recipient_maps =" (i.e. empty) in
    # the main.cf file, otherwise the SMTP server will reject mail for
    # non-UNIX accounts with "User unknown in local recipient table".
    #luser_relay = [email protected]
    #luser_relay = [email protected]
    #luser_relay = admin+$local
    # JUNK MAIL CONTROLS
    # The controls listed here are only a very small subset. The file
    # SMTPD_ACCESS_README provides an overview.
    # The header_checks parameter specifies an optional table with patterns
    # that each logical message header is matched against, including
    # headers that span multiple physical lines.
    # By default, these patterns also apply to MIME headers and to the
    # headers of attached messages. With older Postfix versions, MIME and
    # attached message headers were treated as body text.
    # For details, see "man header_checks".
    #header_checks = regexp:/etc/postfix/header_checks
    # FAST ETRN SERVICE
    # Postfix maintains per-destination logfiles with information about
    # deferred mail, so that mail can be flushed quickly with the SMTP
    # "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
    # See the ETRN_README document for a detailed description.
    # The fast_flush_domains parameter controls what destinations are
    # eligible for this service. By default, they are all domains that
    # this server is willing to relay mail to.
    #fast_flush_domains = $relay_domains
    # SHOW SOFTWARE VERSION OR NOT
    # The smtpd_banner parameter specifies the text that follows the 220
    # code in the SMTP server's greeting banner. Some people like to see
    # the mail version advertised. By default, Postfix shows no version.
    # You MUST specify $myhostname at the start of the text. That is an
    # RFC requirement. Postfix itself does not care.
    #smtpd_banner = $myhostname ESMTP $mail_name
    #smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
    # PARALLEL DELIVERY TO THE SAME DESTINATION
    # How many parallel deliveries to the same user or domain? With local
    # delivery, it does not make sense to do massively parallel delivery
    # to the same user, because mailbox updates must happen sequentially,
    # and expensive pipelines in .forward files can cause disasters when
    # too many are run at the same time. With SMTP deliveries, 10
    # simultaneous connections to the same domain could be sufficient to
    # raise eyebrows.
    # Each message delivery transport has its XXX_destination_concurrency_limit
    # parameter. The default is $default_destination_concurrency_limit for
    # most delivery transports. For the local delivery agent the default is 2.
    #local_destination_concurrency_limit = 2
    #default_destination_concurrency_limit = 20
    # DEBUGGING CONTROL
    # The debug_peer_level parameter specifies the increment in verbose
    # logging level when an SMTP client or server host name or address
    # matches a pattern in the debug_peer_list parameter.
    debug_peer_level = 2
    # The debug_peer_list parameter specifies an optional list of domain
    # or network patterns, /file/name patterns or type:name tables. When
    # an SMTP client or server host name or address matches a pattern,
    # increase the verbose logging level by the amount specified in the
    # debug_peer_level parameter.
    #debug_peer_list = 127.0.0.1
    #debug_peer_list = some.domain
    # The debugger_command specifies the external command that is executed
    # when a Postfix daemon program is run with the -D option.
    # Use "command .. & sleep 5" so that the debugger can attach before
    # the process marches on. If you use an X-based debugger, be sure to
    # set up your XAUTHORITY environment variable before starting Postfix.
    debugger_command =
    PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
    ddd $daemon_directory/$process_name $process_id & sleep 5
    # If you can't use X, use this to capture the call stack when a
    # daemon crashes. The result is in a file in the configuration
    # directory, and is named after the process name and the process ID.
    # debugger_command =
    # PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
    # echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
    # >$config_directory/$process_name.$process_id.log & sleep 5
    # Another possibility is to run gdb under a detached screen session.
    # To attach to the screen sesssion, su root and run "screen -r
    # <id_string>" where <id_string> uniquely matches one of the detached
    # sessions (from "screen -list").
    # debugger_command =
    # PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
    # -dmS $process_name gdb $daemon_directory/$process_name
    # $process_id & sleep 1
    # INSTALL-TIME CONFIGURATION INFORMATION
    # The following parameters are used when installing a new Postfix version.
    # sendmail_path: The full pathname of the Postfix sendmail command.
    # This is the Sendmail-compatible mail posting interface.
    sendmail_path = /usr/bin/sendmail
    # newaliases_path: The full pathname of the Postfix newaliases command.
    # This is the Sendmail-compatible command to build alias databases.
    newaliases_path = /usr/bin/newaliases
    # mailq_path: The full pathname of the Postfix mailq command. This
    # is the Sendmail-compatible mail queue listing command.
    mailq_path = /usr/bin/mailq
    # setgid_group: The group for mail submission and queue management
    # commands. This must be a group name with a numerical group ID that
    # is not shared with other accounts, not even with the Postfix account.
    setgid_group = postdrop
    # html_directory: The location of the Postfix HTML documentation.
    html_directory = no
    # manpage_directory: The location of the Postfix on-line manual pages.
    manpage_directory = /usr/share/man
    # sample_directory: The location of the Postfix sample configuration files.
    # This parameter is obsolete as of Postfix 2.1.
    sample_directory = /etc/postfix/sample
    # readme_directory: The location of the Postfix README files.
    readme_directory = /usr/share/doc/postfix
    inet_protocols = ipv4
    #virtual_mailbox_domains = sendingdomain.com
    virtual_alias_maps = hash:/etc/postfix/virtual_alias, mysql:/etc/postfix/mysql_virtual_forwards.cf
    virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_domains.cf
    virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailboxes.cf
    virtual_mailbox_base = /home/vmailer
    virtual_uid_maps = static:5003
    virtual_gid_maps = static:5003
    virtual_minimum_uid = 5003
    virtual_mailbox_limit = 51200000
    Any help would be appreciated. Thank you.
    Last edited by nadman10 (2014-05-14 14:36:10)

    Your main.cf seems redundant.
    For example:
    if you specify:
    virtual_alias_maps = hash:/etc/postfix/virtual_alias, mysql:/etc/postfix/mysql_virtual_forwards.cf
    you don't need this:
    alias_maps = hash:/etc/postfix/aliases
    and i think you have a lot of more options you don't need.
    This is my main.cf on my vps and everything works great (sending and receiving emails from/to most common mail server: gmail, hotmail etc etc)
    smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
    biff = no
    # appending .domain is the MUA's job.
    append_dot_mydomain = no
    readme_directory = no
    # TLS parameters
    smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
    smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
    smtpd_use_tls=yes
    smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
    smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
    message_size_limit = 4194304
    virtual_mailbox_domains = mysql:/etc/postfix/mysql-virtual-mailbox-domains.cf
    virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-mailbox-maps.cf
    virtual_alias_maps = mysql:/etc/postfix/mysql-virtual-alias-maps.cf
    virtual_transport = dovecot
    dovecot_destination_recipient_limit = 1
    it is very simple (no dkim, no forced tls, no mailbox limits and so on) and it can be improved but it works..
    as I suggested you just try spending some hour wiping postfix installation and giving a look to this guide

  • How can I recover an old/disused iCloud account. I was having some issues with my apple id so I restored my iPad, I am now stuck on the activation screen as I no longer use the iCloud account i used to set up the iPad and can't remember the address or pas

    How can I recover an old/disused iCloud account. I was having some issues with my apple id so I restored my iPad, I am now stuck on the activation screen as I no longer use the iCloud account i used to set up the iPad and can't remember the address or pas

    I have the same problem - it is maddening. I rely on this iPad for work so this is not just an annoyance! The above solutions of changing the appleid on the device or on the website do not work.
    The old email address no longer exists - I haven't used it in a year probably and I no longer have the account.  I logged into the appleid website and there is no trace of the old email address so there is nothing that can be deleted or changed there.  On the iPad there is no trace of the old email address so nothing can be deleted there either. I have updated the iPad software and the same problem comes right back.  Every 2 seconds I am asked to log in using the old non-existent email.  The device is currently useless.
    The only recent change to anything was the addition of an Apple TV device, which was set up using the correct login and password.
    Does anyone have any ideas? The iPad has been backed up to the iCloud so presumably it now won't recognize the current iCloud account? So restoring may notbe an option?

  • Outlook 2013 Not Responding and Offline Address Book Issues with Office 365

    Around 3 months ago I setup a small business with Office 365 for email. They have 10 PCs, all running newly installed Windows 7 Professional 64-bit, eight with Office 2013 and two with Office 2010. All are connected to a local domain (Server Essentials
    2012) with a single internet connection through a new TP-LINK router. Each user logs into their own PC only.
    The network runs perfectly, internet connection is good but there seems to be RANDOM, INTERMITTENT issues with email not being SENT from Outlook every so often. Email will sit in the outbox for up to an hour sometimes before, eventually, being sent. Incoming
    email seems ok, although this is more difficult to tell. At others times, email will be sent instantly - the size of the message and any attachments makes no difference.
    The issue has happened at some point on every one of the PCs but no particular PC/user seems worse than any other. When email is stuck on one user's PC it can still be sent ok by other users at the same time - so the internet connection is not down. Users can
    can always login to the OWA service ok and iPhones etc. all sync ok even when email is stuck in the Outbox.
    To debug the issue I have worked on one particular user's PC and carried out the following changes - 
    Changes that made no difference
    I have checked the router. A SPI firewall is available on the router but this is switched off.
    I have changed the MTU on the router with no effect.
    There are no unsual add-ins to Outlook
    Outgoing email virus scanning is disabled
    Outlook is NOT integrated with Lync
    The OST file is around 1.7 GBytes is size.
    I have recreated the Outlook profile twice but this made no difference
    Switched OFF "Cached Exchange Mode" - this made things worse !
    The Outlook address book is set to \Offline Global Address List
    I have disabled with Windows firewall on the client PC - no change
    I have adjusted the KeepAliveTime for packets in the registry of the PC to 20 minutes
    Changes that reduced the frequency of "Not Responding"
    I have changed the Outlook automatic Send/Receive time from 30 to 10 minutes - this seemed to help 
    Possible Related Problem
    I have attempted to download the offline address book manually - this hangs at "Copying offline address book template file" in the Send/Receive dialog and there a NO OAB files in the data file location on the PC. 
    So the only measure that has so far "helped" has been the Outlook Send/Receive time change - now set to 10 minutes. Even so, Outlook will occasionally go "Not Responding" for 30 minutes or more (no windows active - only option
    is to close and reopen Outlook).
    There does seem to be a problem with the Offline Address book. I can download this ok for this user on my home PC (Outlook 2010) but this will not download manually on the work pc with Outlook 2013 (despite following all the debug steps above).
    On work PC I can see literally hundreds of "Schannel" errors in the Windows System event logs - 
    Error - Event 36888 Schannel
    The following fatal error was generated :10
    The internal error state is 10
    These errors occur every 2-4 minutes continually all the time Outlook is running. When Outlook is closed the "Schannel" errors stop !
    Can anyone suggest what else to try, please ?
    I have already investigated this issue on the Office 365 Community Forum, and the Outlook forum and they suggested that it was a client (i.e Outlook) issue and that I should post here for further information.
    Thanks for reading !

    An update to this problem.
    I brought one of the office PCs back to my home network and connected it up there. With no changes to the PC I was immediately able to download the Offline Address Book without errors.
    This suggests to me that there must be some problem with the internet connection or router setup in the office environment.
    The router is a TP-LINK W8970. The internet connection is PPPoA. I have seen some suggestion that an SPI firewall can cause issues. This router has an SPI firewall but this feature is disabled on the router.
    While investigating this issue I have frequently been connected remotely to an office PC - sometimes for up to an hour or more. During these periods I have not experienced any connection dropouts so the actual internet connection seems to be ok (i.e. it is
    not dropping out). 
    However, something seems to be preventing the Outlook client from connecting properly with the Office 365 Exchange server in the office environment - or something is dropping the connection to Outlook. Does anyone know of any router settings that might affect
    this ?
    I could try changing the office router but I do not have a spare available. Can anyone suggest a reasonably low cost, currenbtly available router that they know definitely works in the Office 365 environment so that I could buy this for test purposes ?

  • Best Buy DOES need to address all the negative issues with Citibank!

    Hi, I've read all the negative posts about Citibank.
    I have been a loyal customer of Best Buy for quite some time and have purchased products from washing machines to electric guitars.
    I have my own story:
    I've had nothing but issues with them since Best Buy went to them.  The last 5 bills I've received have been all messed up.  Each time it's been for at least 2 hours.  I never had problems until the switch to Citibank. 
    I have several deferred interest purchases.  I've taken each of those, divided them by the number of months the contract is for, thus determining how much to pay each month to pay them off by the expiration date.  Citibank has screwed them up every month. Distributing them differently than I had requested.  One time in "fixing" their mistake, they "mistakenly" added an additional charge of $130 to my account!  In reversing that they screwed up other distributions. That's why I've been on the phone with them so long each time.  Some of them they still haven't fixed. 
    One six month account isn't due to expire until 9/16/2014, but the way they are applying the distributions it will be paid off 6/15/2014.  A full 3 months before it is due.  It obviously saves them having that receivable for 3 months.
    Most of the customer Service reps have tried to be helpful but some of the time it is them that do the screw-ups.  When I ask to speak to a Supervisor they are usually not helpful or rude.  I was talking to one and he wasn't answering my questions, I challenged him and found out he wasn't even listening!  Sometimes they say "it was a change that didn't get into the computer right". I've spent my entire career in the computer industry (Retail chains, Discount Chains, Accounts Receivables, and Bank Systems)  You NEVER release a change until it has been completely tested.  Apparently they have someone totally incompetent that department.
    They apparently started a new policy 2 months ago that applied your minimum payment to the your revolving balance (non-promotional) first, if you only had Promotional balances it was applied to the one that would expire first.  Again, it's a way for the bank to relieve Receivables earlier than they should. To their benefit.
    I don't understand why so many of the Moderators and other responders have to be so rude and condescending to the people in this forum.  All we hear is this Mantra that Best Buy has nothing to do with the credit card. Yet, the Logo on the statement says "MY BEST BUY CREDIT CARD".  When you pay by mail the payment stub "Make checks payable to "BEST BUY CREDIT SERVICES".  When you call they answer "BEST BUY CREDIT SERVICES".  And you wonder why people think Best Buy owns the credit cards?
    You are correct that Citibank owns the credit cards and processes them.  But some Executive at Best Buy initiated having Citibank do this.  You talk about it's just a marketing thing to have Best Buy's name on everything.  Well I'll tell you. with all the complaints I've read here and horror stories that I have personally heard from customers, it is a very NEGATIVE marketing thing.
    Most of the customer Service reps have tried to be helpful but some of the time it is them that do the screw-ups.  When I ask to speak to a Supervisor they are usually not helpful or rude.  I was talking to one and he wasn't answering my questions, I challenged him and found out he wasn't even listening!  Sometimes they say "it was a change that didn't get into the computer right". I've spent my entire career in the computer industry (Retail chains, Discount Chains, Accounts Receivables, and Bank Systems.)  You NEVER release a change until it has been completely tested.  Apparently they have someone totally incompetent in that department.
    They apparently started a new policy 2 months ago that applied your minimum payment to your revolving balance (non-promotional) first, if you only had Promotional balances it was applied to the one that would expire first.  Again, it's a way for the bank to relieve Receivables earlier than they should. To their benefit.
    I also noticed that one of the Moderators posted a response to several complaints about no more 18 month deferred purchases that it was Citibank that discontinued them.  It seems to be a very popular "marketing thing" for Best Buy also.  Why keep a bank that dictates "marketing things" to your company?
    Have any of these many complaints been brought to the attention of Best Buy Management?  Do they even know about them?  If they have, then I would think they would be concerned enough to re-think their decision on a Bank Card Processor.
    Many have said they will quit buying from Best Buy.  I will not.  I like the stores, their merchandise and staff.  But I have serious concern that if this problem is not addressed thier may nit be a Best Buy to shop at in the future.
    For that reason I am sending a letter to the CEO and CFO regarding this.
    I would suggest each person that has complained dothe same.  Since the Moderators blocked out the executive's names on one of the posts, you can go to Best Buy.com main page at thew bottom under "Corporate Info/About Best Buy/About Best Buy (yellow Tab)/Executive Team  and you will find their names.  The Corporate address is one one of the posts in here.  The one the they deleted the names from.  Maybe all of our voices will be heard.
    P.S. - Check back to see if I'm blocked or this post is closed or deleted.  If so, another thing to comment to the Executives about...
    Best Regards Everybody!

    Hello GJT,
    Welcome to the forum, and thank you for being a loyal Best Buy customer! I'm very sorry to read of all the troubles you've been having with your My Best Buy credit card account. 
    If you made a purchase using one of our interest free financing offers, to avoid paying the interest, you would need to ensure you were making the minimum monthly payments and paid the full balance by the end of the financing term. For future reference, the promotion expiration will not be the same as the payment due date. The expiration is determined from the date of the purchase. This date would have been clearly marked on each of your billing statements.
    If you did make other purchases during the financing period, the payments would have been applied to the account according to the credit card laws as the others have mentioned. It is my understanding that any payments made to the account would first be applied to all minimum payments due for purchases on the account. Next, it would be applied to purchases that have interest charges due. Lastly, if funds remain from the payment, they will be applied to purchases with the financing promotions, in the order they are set to expire.
    As you may be aware, Citibank, N.A. is the issuer of your My Best Buy credit card account. Due to this, we have no influence, or access to their accounts or policies.  It is however, my goal to assist our valued customers as best as I can; therefore, I will be reaching out to Citibank on your behalf to look into your concerns. and they should be reaching out to you directly within the next 3-5 business days to discuss this further. If you do not hear from them within this timeframe please let me know.
    Thank you for posting your feedback here on the forum, and please do not hesitate to let me know if you have any further questions or concerns. 
    Sincerely, 
    Maria|Social Media Specialist | Best Buy® Corporate
     Private Message

  • Address Book and Sync Issues with Verizon Curve

    I got my first BB about a month ago and like it, for the most part.  I have three major issues with it now:
    1.  SYNC   I've downloaded and installed the latest software from pocket mac and my first sync went fine (I have a MacBook Pro running 10.4.11).  Every sync after that has failed.  I've tried the recommended solutions like cleaning out the sync history, re-installing, etc.  I've un-installed and re-installed several times with no change.  The sync begins fine and but never finishes.  One thing that could be a problem is the version - every time I download the software, I've clicked on the newest version, (PocketMacForBlackBerry4.1.25.dmg) but after it installs, it calls itself Version 1.2 (1.4).  Shouldn't it be 4.1?  I know there are issues with older versions, but I can't seem to get 4.1 installed.  
    2.  ADDRESS BOOK    Sinse my first and only sync, I've needed to add a LOT of contacts into my address book manually.  It doesn't work most of the time.  When I add a new contact and save, it won't exit the contact, but pops up this note:  "Address updated externally, changes will be lost and the viewer closed."  The same thing happens if I'm trying to create a new entry or edit an existing entry.  The real crazy part is that many of the numbers I've added show up when they are incoming calls - the name and correct phone number, but when I try to call out on my phone, the contact info will not show.  
    3.  GPS    Not a major deal, but none of the GPS services work.  I use the Google Maps mobile app, but the GPS does not work.  Neither does any of the other software I have installed for GPS.  I have gone into the preferences and enabled the GPS and saved the changes.  The logo even appears on the main screen, it just doesn't work.  *NOTE* I've found that Verizon has disabled the GPS unless you pay for the VZ Navigator service.  Typical Verizon marketing.  Is there any way to bypass Verizon's block?
    Needless to say, I'm not very impressed with Pocket Mac software of the RIM address book utility.  I've read over many of the posts in this forum and see many other frustrated users.  Makes me really think about throwing my money at an iPhone. 
    If anyone has any solutions to my problems/frustrations, I would be VERY grateful.
    thanks for your time,
    -marlowe
    Message Edited by marlowe on 11-19-2008 12:12 PM

    I cannot say I AGREE! any louder.
    This pocketmac people claim in the website to offer "solutions" but they have given me lots of headaches and I too would just go and buy an iphone. The only problem is that AT&T does not work in my house.
    No matter how many tricks I have tried I cannot make my 8330 accept the changes i make in my address book. It is absolutely a killer.
    Some previous user said that bluettoth could help but at any rate that was to over ride the address book with the 8330 data and in my case i was trying to do the opposite. 
    Any help on this would be greatly appreciated!

  • Is Apple going to address the issue with the IPhone 5 charger port?

    Hi all
    I have had an IPhone for about 4 years and have had my current iPhone 5 for just over a year,I never had any problems until recently. Just before Christmas I started having issues with my IPhone not charging, I bought a new charger and the problem continued so I went into the Apple store in Newcastle, they pulled some dust out of the charger port and the issue appeared to be resolved. However after Christmas it happened again, and again I went to the Apple store, they did the same thing and the phone worked fine for a month. However, this last week the problem has come back, this time when I took the phone into the store, they tried pulling dust out the port but the phone would still not charge, I was then told that as the phone is out of warranty there is nothing they can do other than charge me £209 to fix it!!
    What concerns me is that after speaking to other iPhone users and doing some online research I have discovered this is a seriously common problem. So now through no fault of my own, I am left with a phone, which doesn't work and costs me £48 a month. Another concern is that I originally took the phone to the store with this problem before my warranty ran out and was given a 'temporary fix', which made the phone last untill just after my warranty has ran out!
    I am angry and disappointed, this issue needs to be addressed as the Phones appear to be like a ticking time bomb waiting to break, and for those of you like me, who this happens to you after the warranty is up, you are elft with no solution other than to pay £209!!!!

    Or talk to the store manager or Apple Customer Relations and explain that you brought the phone in twice before the warranthy expired for the same problem and that there was no permanent solution, though if clearing out the debris fixed it previously, it's perhaps unlikely that they'll think it a defect. You can try, though. Just complaining here will accomplish nothing since we're all fellow users in these forums.
    Regards.

  • Issue with index creation of an infocube.

    Hi,
    I have an issue with creation of index's for a info cube in SAP BI. when i create index's using
    a process chain for the cube it is getting failed  in the process chain. when i try to check the index's  for this
    cube  manual the following below massage is shown.
    *The recalculation can take some time (depending on data volume)*
    *The traffic light status is not up to date during this time*
    Even i tried to repair the index's using the standard program "SAP_INFOCUBE_INDEXES_REPAIR" in SE38
    to repair the index so it is leading to dump in this case.
    Dear experts with the above issue please suggest. 
    Regards,
    Prasad.

    Hi,
    Please check the Performance tab in the Cube manage and try doing a repair index from there.
    This generates a job so check the job in SM37 and see if it finishes. If it fails, check the job log which will give you the exact error.
    These indices are F fact table indices so if nothing works, try activating the cube by the pgm 'RSDG_CUBE_ACTIVATE' and see if that resolves the issue.
    Let us know the results.

  • Issue with IP address resource

    Hi
    I have been having an issue on our file server cluster recently where an IP address for the backup LAN scope will not come online. This happened a few days ago and the IP address eventually went online, but now it has been failing for over of day with the
    following message in cluster logs (Client Identifying information removed):
    000040a8.000020c8::2014/05/15-11:19:42.768 WARN  [RES] IP Address <IP Address 10.*.*.*>: NetInterface *************-****-****-************ is not reachable. Wait & retry.
    000040a8.000020c8::2014/05/15-11:19:43.782 ERR   [RES] IP Address <IP Address 10.*.*.*>: Timed out waiting for NetInterface *************-****-****-************ to be available. Failing resource.
    I can not see any issue with network cards, and this issue occured even on another node. This single resource failing is also causing the networks in that scope to show as failed.
    Update:
    I have been able to get this issue to resolve by reapplying the Static Routes (even though they show as already existing when I put them in). The resource then goes online. Unfortunately this reoccurs on a daily basis.

    Hi DH84,
    I see what you say but when you can write static route please you use interface ID.
    It is a best practise for all cluster systems
    For example, here is my route table, the interface id 7 is my data nw. when i write a static route it must be;
    route add x.x.x.x mask 255.255.255.0 x.x.x.x if 7
    Regards

  • Issue with Delivery Address in PO

    Hi All,
    I have an Issue with Purchase order. PO created with delivery address ( # 27856 ) on 2007. PO item got deleted and address # 27856 also deleted from table ADRC. When I try to change or display the PO we got the message Address # 27856 doesn't exit and not able to do anything. We came out fom the PO screen.
    Please any one guide me how to fix the Issue WITHOUT creating an New PO.
    Regards,
    Senthil

    Hi,
    PO item got deleted means Deletion indicator has been set for the PO. PO was not archived.
    When I execute the ADRC table with the address number 27856 i didn't get any output. It shows no table entries available.
    The exact message i got was
    Address doesn't exist 27856  4500178450 00010
    Message no. AM010
    I can't do anything in the PO.
    Please guide,
    Regards,
    Senthil

  • Issue with electronic mail address in profile

    As a part of the conversion process, one of the electronic mail addresses I use was effectively 'burned in' to my profile. Clearly I can make it visible, or keep it hidden - but there is a problem. The public address I previously had listed for this purpose is not available - instead it's the private address that is displayed!
    Think of it like this:
    [email protected] [private address]
    [email protected] [public address]
    It was the public one previously visible - it's now the private one, currently set to hidden, which is the only one I can choose to display or hide. Can anything be done about this, or are we stuck with this 'converted' change to our profiles?

    I appreciate the thought, and am sure that for some users this would be a sufficient tactic. Unfortunately, I have historically had issues with the interlocking but thoroughly unreliable process of changing ones basic identity at…
    http://myinfo.apple.com
    This is aggravated by the fact that I have four such identities - though I only use one here in Apple Discussions - with varying levels of access to ADC, GSX and other generally non-public areas at Apple. Managing them, including my .Mac ID, is at times a challenge, and I hesitate to do anything at all to upset the delicate balance. Unless the Discussions profiles revert to a primary private electronic mail address with a secondary optional 'public' address, I suppose I will just have to use the previously non-public address that became the sole available address following the conversion.
    Thanks again for thinking about this, and offering a solution to the issue.

  • Issue with iCloud.. email address and responding

    Hi Everyone,
    Not sure why this is happening but I have encountered some recent issues with iCloud. A little history I restored my iphone 4s and have reinstalled and reset all my accounts, apps, and services. All was working well until this last week.
    1) Before (restoring my phone), I was able to reply to any email (icloud or other) on my phone AND select which ever 'from account' I had available, INCLUDING the icloud alaises. Now when I reply through the phone I do not get access to those alaises for some reason.
    2) Through the browser (Safari or Chrome), I can not reply to emails in iCloud. It crashes. I can however forward, but once I hit reply it generates an error.
    iCloud has also somehow merged my emails addresses into mail but again disregarding the alaises created. I don't sync my MacBook Mail with iCloud Mail documents (Thank God), but I do sync Calendars, and Contacts. (Btw it would be nice to select which Contact groups to sync with as on iTunes)
    Not sure what is going on but it has become quite annoying especially when it was working just fine about 2-3 weeks ago.
    Any ideas/solutions?
    Thanks

    Try going back to http://appleid.apple.com and changing the ID back to the original address. If you can get this accepted, then go to the iCloud preferences/settings pane, stop 'Find My ....', and then sign out. Do the same on any other devices or computers.
    Then go back to http://appleid.apple.com and change the ID to the new one. Sign in with that on all your devices.
    However as the address which forms the original ID is now not working it can't be validated and it's possible that you won't be able to revert to it. In this situation only Support can help you.
    To contact  iCloud Support: if you currently happen to have AppleCare, either because you recently bought Apple hardware or have paid to extend the inititial period, you can contact them here:
    http://www.apple.com/support/icloud/contact/
    You will need the serial number of the covered hardware.
    If you are not covered by AppleCare, then - in common with other free email services - there is no free support and you may be asked to pay a fee.

  • When is the next ios update and will it fix/address the issue with photos not being shown in chronilogical order?

    when is the next ios update and will it fix/address the issue with photos not being shown in chronological order?

    All of us here are users just like you. We have no inside info of when Apple products or operating system updates/upgrades will be released. The next iOS may not even change the issue you have.
     Cheers, Tom

Maybe you are looking for