External mail routing issues
Hi,
I have installed Ex2013 on a separate box. Over the weekend I have switched the 2010 CAS role to my new CAS server. I update the external url's on the virtual directories on the new CAS server swapped out the ip's of my 2010 exchange putting
it on the new one (as I don't have to make any changes to my public dns records) and set a new ip for my 2010 cas box with mailboxes. Last, I updated the internet connector to include my new CAS server as a source server. Basiscally, everything
works fine except the now we can't send any external emails. We got an undeliverable message saying that "client host x.x.x.x blocked using block list 1, mail from IP banned............
Hi Joe,
Based on your NDR, it indicates that your IP address 4.30.210.34 is blocked in the BlockList . If you want to remove your address from the list, you need send a message to
[email protected] with your IP address.
Additionally, if you want to send external message from Exchange 2013 server, it is recommended to
change the primary host names, such as mail.contoso.com, autodiscover.contoso.com, and owa.contoso.com (if used) to
point to the external, publically-accessible, IP address of the Exchange 2013 Client Access server with your public DNS provider
instead of an external IP of your original Exchange 2010.
In other words, you might need to make changes to your firewall to support the new Exchange 2013 server. You might need to add new firewall rules, add an external IP address for your Exchange 2013 server, or make other configuration
changes. For more information about configuring DNS records, we can refer to:
http://technet.microsoft.com/en-us/library/dn307232(v=exchg.150).aspx
Checklist: Upgrade from Exchange 2010
http://technet.microsoft.com/en-us/library/ee332309(v=exchg.150).aspx
Thanks,
Winnie Liang
TechNet Community Support
Similar Messages
-
External mail routing not working both inbound and outbound
Hello there,
I installed AD 2008 R2 including the Exchange 2010 in my lab. I also use the DNS on the same server. I am able to send emails internally via OWA with other users, but I cannot send email externally nor receive one. When I tried to send email from my external
account it says no MX or A record, but when I use the nslookup tool it finds the mx record. I have my send connectors ok and also I created accepted domain. the smtp domain I am using is corp.contoso.net. I am new to Exchange and configuring mail routing.
I am sure I probably just mis-configured the server. I also use the mxtool and of course it did say no mx or A record exists. Any ideas that you can toss around is greatly appreciated please.
thanks
Lotusmail1
Franz GarciaDo you have A record and MX record created in your external DNS?
Without MX record you won't be able to receive external emails.
Make sure "Anonymous Users" ticked in the default receive connector properties.
Check this
If send connector created please make sure it has internet and tick "use the external dns lookup settings on the transport server" and add external DNS IP in your transport server properties using this command .
Set-TransportServer Hub01 -ExternalDNSAdapterEnabled $false -ExternalDNSServers {192.168.1.1, 192.168.1.2}
Check this for details
MAS -
VLAN routing on Catalyst plus external WAN router issue......
Hi,
Bit of advice if possible.
I've got a project to implement VLAN's on a MAN, which is easy enough, using CAT4506 and a mixture of 3750 and 2950 switches. The Vlan aspect is OK but I'm a bit unsure as to how to integrate the WAN into the design.
I have two core WAN access sites each with 2 * cat4506 switches of which one at each site attach to a WAN router (3725)
The CAT4506 switches will be doing the vlan routing but the 3725 routers (one at each site in a HSRP group) will be routing the WAN. Obviously these need to be attached to the catalysts for WAN access. As I have seperate routers for vlan routing and wan routing, what is the best way to configure this ?????
Is configuring a seperate VLAN for the routers the best idea ? or is it best to use the sub interface option on the router ethernet ports ?
Do I just use a static route of last resort on the Catalyst pointing to the routers ?
Help :-)When you arte still in the design-phase, I want to strongly discourage you from designing a network with vlans that span multiple sites.
You will always run int STP issues in one way or another. The following link will give some sensible information on this subject:
http://www.cisco.com/en/US/netsol/ns340/ns394/ns147/ns17/networking_solutions_white_paper09186a00800a3e16.shtml
I hope that it will point you to the right (or at leats an optimal) solution for your specific design.
Regards,
Leo -
Send External mail with Attchment from SAP
Hi All,
OUR REQUIREMENT: We need to send EXTERNAL MAIL with ATTACHMENT(Excel) form SAP .
We have developed a function module which converts the internal table data into Excel Format and sends it as an attachment to External Mail.
ISSUE : But our issue is we are unable to open that document using GOOGLE DOCS Could any one help me how to do this.
it was thriughing error like
Error log is .
''Sorry, we are unable to generate a view of the document at this time. Please try again later.
You can also try to download the original document by clicking here. Alternatively, you can view the plain HTML (automatically redirecting).
Regards
Venkat .
Edited by: venkata pradeep on Mar 5, 2012 10:26 AM
Edited by: venkata pradeep on Mar 5, 2012 10:28 AMIs the excel file recognized by MS Excel? If not, then issue is you have wrongly converted your attachment and/or your FM to create an excel file was wrongly coded or you have passed it wrongly to your mail code.
If you consider an OOP approach in sending external mail, refer to this link:
http://wiki.sdn.sap.com/wiki/display/Snippets/SendingmailwithattachmentusingObjectOriented+Approach -
[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 -
Inter site mail routing on AD site Link issue
Hi All,
1, we are facing issue between mail routing between two AD site normal mail routed via AD site Link but when put an attachment it stuck in to site queue.
we have two AD site Site "A" has exchange 2007 SP-3 and Site "B" has exchange 2010 SP-3.
2, when we are migrating 2007 user's mailbox 2010 after mailbox migration user get a popup " Administrator has made some changes ......................." after this when user restart his outlook client user can not connected as his mail server
settings are still older.
this is working properly for sites having Exchange, rest 2 sites not having any exchange, there we are getting this issue.
Please help.......
Thank You
Vinod
Vinod Kumar DhimanHi Vinod,
Thank you for your question.
We could run the following command to check if the issue persist:
Set-SendConnector –Identity <SendConnectorname> -IgnoreStartTLS $false
You could also send NDR to [email protected] for our troubleshooting.
Ans:- between AD site mail rout via AD site Link and i have checked the size limit is "Unlimited"..
Did you mean you have checked the limited of send connector?
There are following limitation on Exchange server, we could check it by command:
Global/Organizational Limit: Get-TransportConfig
Send Connector: Get-SendConnector <send connector name>
Receive Connector: Get-ReceivConnector<receive connector name>
Active Directory SiteLink Limit:( you have check)
Server Limits(transport rule: 15M in this case)
User Level Limits: Get-Mailbox “User Name” | Format-Table Name,*Max*
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support -
E-mail router (On-premise) to CRM 2015 (On-line) connectivity issue
Hello Experts,
I was trying to configure e-mail router on my location environment (working on domain administrator credentials :)) to connect to CRM 2015 Online server (TRIAL version).
Unfortunately during "Load data" process ("Users, Queues and Forward Mailboxes" tab in E-mail Router Configuration Manager) I'm still getting "Access is denied" error.
"CRM Server address" I'm using is: “https://disco.crm.dynamics.com/orgname” ("orgname" is 100% correct, I've also tried "DEV" instead of "DISCO" address option) and "Access credentials"
specified are also correct (this is System Administrator user in my CRM organization).
I assume that the problem is somehow connected with user account, because when I’m trying to use some fake one (ex. "[email protected]") the error message is different ("GetAuthStateEx(), Request Status: ").
I was trying to use Fiddler to see problem source and I found that "Access denied" is return during accessing "https://disco.crm.dynamics.com/XrmServices/2011/Discovery.svc" URL.
Am I missing something? Should CRM account used by e-mail router have some additional permissions except "System administrator" role in CRM?
Any help will be really appreciated.
Kind regards,
PiotrI've checked unique organization name on developer resources page many times (this is very common reason of many problems with e-mail router deployments).
Actually I'm looking at this name right now and it is 100% correct (only lowercase letters, no "strange" characters :)).
Today - the error message looks a little different.
I've checked above mentioned web service address ( https://disco.crm.dynamics.com/XrmServices/2011/Discovery.svc ) in IE and there is no problem with accessing it.
I'm wondering should this error be somehow connected with fact that our CRM online organization is TRIAL version or that it is 7.0.1 version (our e-mail router is 7.0.0)?
Any other ideas?
Best regards,
PG -
Sending from Business workplace to External mail ID
Hi,
Please Some help me on this issue am getting below error when am trying to send mail from Business Workplace to External Mail
Cannot process message , no route from SAPUSER TO abc123 at gmail dot com
I done configuration by refereeing below.
Please follow these steps:
1.) tcode = SCOT
2.) double click SMTP
3.) under "SMTP Connection" section, fill in your mail host IP(ex: webmail.sap.com) and the port number(25) and code page = No conversion.
4.) under "Supported address types", make sure Internet is checked, and click on "Set". The Address area has to be *
5.) To test route,
SCOT -->Utilities --> Routing test
RecipientAddr.type = INT
Recipient addr. = abc.xyz at sap dot com
6.) You also need to set the Default Domain.
SCOT --> Settings --> Default Domains (webmail.sap.com)
7.)Now go to tcode SBWP,compose a mail and in the recipient address,enter abc.xyz at sap dot com and send.
8.) Come back to SCOT and click on Utilities-->Start send process(CtrlF7) and execute.+
Thanks,
GALHi
Same problem with me.
Mails are not sending to external mail id.
Pls help me out!
Regards. -
Exchange 2013 Mail Receiving Issues
Hi everybody,
Yesterday I configured a new DC and Exchange on Hyper-V (Server 2012 and Exchange 2013)
All functions and rolls are configured and installed but i am having issues receiving external e-mails.
Almost all of the external mails are being deliverd a half hour to a hour after being sent.
To start of on the first level.
I got a Siemens Fiber modem with an external address connected to the WAN of my Draytek 2995 router.
Alle the needed ports are forwarded to the Draytek (80,443,25,1723).
The Draytek DHCP function is set to off.
192.168.168.2 (DC) -> 80 (HTTP IIS)
192.168.168.2 (DC) -> 1723 (RRAS)
192.168.168.3 (Exchange) -> 25 (SMTP)
192.168.168.3 (Exchange) -> 443 (SSL)
My Draytek router is connected through LAN1 to a HP switch (unmanaged).
The physical server has 3 NIC's, all of these are connected to the HP Switch
I Disabled Hyper-V Queuing on the NIC's because this causes an issue with slow network connections.
The network has been configured as following.
I configured the Server 2012 R2 on the hardware(physical server) with only the Hyper-V roll.
NIC1is setup for the physical server,
IP Address: 192.168.168.1
Subnet: 255.255.255.0
Gateway: 192.168.168.254 (Draytek address)
DNS: 192.168.168.254 (Draytek address)
The Server software firewall has been set to a private network through the local security policy.
I have setup 2 VM's through the Hyper-V roll.
The first VM is the Server 2012 R2 Domain controller.
For this VM I created a virtual switch connected to my second NIC(2).
I unchecked the box where my host can communicate with the NIC(2).
The DC has been configured as following:
Hostname: SERVER
IP Address: 192.168.168.2
Subnet: 255.255.255.0
Gateway: 192.168.168.254
DNS: 127.0.0.1
I can ping to all the adresses from this server (internal and external).
The server has been promoted to domain controller with the following rolls.
ActiveDirectory, Certificate Autohority, DHCP, DNS, RRAS, RDP.
Alle these rolls have been set and working. (all have been tested)
DHCP has all options configured (scope, router-192.168.168.254, dns-192.168.168.2)
A DNS simple and recursive test work fine.
I did no configuration on the DNS after the DC PROMO.
So i created users in the AD.
After that I created a second VM, this one is used for the Exchange.
I setup a second virtual switch connected to NIC3 and installed Server 2012 R2 with the following config.
Hostname: SERVER
IP Address: 192.168.168.3
Subnet: 255.255.255.0
Gateway: 192.168.168.254
DNS: 192.168.168.2 (pointing to the DC)
I joined this server to the domain, everything is working fine.
Both servers have internet and network.
Running portscans on 1723 and 80 all work like a charm.
No its time to install Exchange.
I ran all the prerequisits and PowerShell commands (IAcceptLicense. etc.)
Installed de needed API and filters.
Installed Frameworks 3.5 on both servers.
And the Exchange installation was succesfull.
CU3 is also installed.
I configured the send connector, accepted domains etc.
Created all needed certificates (self signed)
Did a portscan on 433 and 25 and they work.
All the hosting records are set mail.domain.nl etc. and MX records.
I created inboxes for the users and was able to connect them to the users in the Active Directory on the DC without any problems.
Connecting through the internet to OWA works perfect and i can login with users.
Sending e-mail internally works perfect, the messages are being deliverd in an instant.
Sending e-mail externally also works perfect, i receive mails in a few seconds on a person email address.
But when i reply or send e-mail to my new Exchange it can take up to hours to receive the mails!
I did online SMTP checks and e-mail checks, the all come out like it should.
One message from MX TOOLBOX on the SMTP:
SMTP Transaction Time
8.408 seconds - Not good! on Transaction Time
I have nog other receive connectors setup, just the standard connectors.
So i got into the Exchange ECP and under "server" i setup the DNS to listen to 192.168.168.2 (DC).
I've read that when this is set to all ip addresses it can cause mail delay, but no luck.
I ran the best practices analyzer and get about 23 errors and 20 warnings.
A lot of services are unhealt like the "ExchangeTransport).
I have no idea what is causing the issues and read almost every forum.
Does anyone have a clue what is going on?
Did i miss something, is there a misconfiguration?
Best regards,
TimThe mailserver did not receive any e-mails in this timespan, it was not an issue with the connector to the user mailboxes.
The internal e-mail also works flawless.
The entire Exchange server just not received this mail in time.
I sent an e-mail from my personal accout with the option in my outlook to receive a delivery-reply.
I got the reply as soon as the mail was deliverd, this took about a half hour to a hour.
After you asked me about the firewall, i got a hunch..
It had to be on the incomming connection, so i checked every single firewall on the network and disabled them.
Still the same problem...
But there was still one ethernet device that could have a firewall, the internet modem!
This ATM modem receives multiple external IP's from the ISP, so I figured there was no firewall on this device. (Just like all the cable modems that are deliverd in our area by Ziggo(ISP).
But I was wrong, there was a firewall enabled on the modem!
All the ports in the modem had been forwarded but somehow the modem-firewall filtered the traffic,
creating the issue on the incomming e-mail.
I disabled the firewall and all the external e-mails are being received in an instant!
Re-enabled all the software firewalls on the servers and re-enabled the malware filter through powershell, after these steps I did another test, and everything still works like a charm!
Many thanks for your help Kjartan! -
Outlook 2010 and 2013 are unable to connect but OWA (and mail routing) works fine
Hi-
Not sure why but this past Sunday (just after DST adjustment) outlook clients (using 2010 and 2013) were unable to connect to an Exchange 2013 server. OWA and mail routing (internal and external) is working fine. I've even tried on multiple machines
and all of them experience the same issue. On a new machine with a fresh version of outlook 2013 installed here is what happens:
Click on Outlook 2013
Click Next until the account setup is displayed.
Name and email is auto-populated
Established network connection is good
Searching for email address settings is good (once the self-signed exchange 2013 cert is accepted)
And then the logging onto the mail server fails. The first pop-up is:
The Connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
Clicking "OK" is followed up with a window with the Microsoft Exchange connection info.
It lists Microsoft Exchange server which is populated with: GUID@<domain suffix>
Mailbox which is populated with: =SMTP:<Valid Email address>
On the Exchange Server I have noticed that the Web Management Service (WMSVC) is stopped and will not start. Starting the service outputs:
EventID 7024
"The Web Management Service terminated with the following service-specific error: Unspecified error"
Not really helpful :)
Since this is only happening with Outlook on multiple clients I'm expecting something with Exchange or the ability for outlook to connect to exchange.
Thanks in advance!Hi
I know this is an old post, but I'm having a very similar issue. I have CU6 installed and all other client connectivity apart from internal Outlook connectivity is working fine. I have distributed the new Self-Signed Certificate and the tested to verify
the clients trust it. I have tried on multiple machine with multiple accounts and none of them connect.
I'm at the stage of reinstalling, but I would rather troubleshoot the problem, just in case ever hit the same wall in the future. I have run Test-OutlookConnectivity with the following output;
RunspaceId : 71f8d740-c499-4bbe-8baf-9cbb12566fb8
Server : PW-SC-01.companyname.local
MonitorIdentity : Outlook.Protocol\OutlookRpcDeepTestProbe\NEW2013
RequestId : 75641e34-aa49-4fce-aad7-181b56dd7b29
ExecutionStartTime : 10/11/2014 13:50:03
ExecutionEndTime : 10/11/2014 13:50:03
Error : Error 0x6ba (The RPC server is unavailable) from ClientAsyncCallState.CheckCompletion:
RpcAsyncCompleteCall
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 2
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1710
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: 0 (0x00000000)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 13
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1352
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: -1073606646 (0xC002100A)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0xC002100A
EEInfo: Detection location: 1380
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 12175 (0x00002F8F)
EEInfo: prm[1]: Unicode string: /rpc/rpcproxy.dll?PW-SC-01.companyname.local:6001
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0x00010000
EEInfo: Detection location: 1385
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 8 (0x00000008)
EEInfo: prm[1]: Binary Buffer: [48-1263-10248-1262-126-9632122164676121-3988104-118-11373-61-94
-111-112-98-1217048136942-12272-122-91311550483449324830638543192311910198979999101115115461121199
91111091091154699111461171074830231349524949485349505348484990231349574949485349505348484990483449
324830638543192311910198979999101115115461121199911110910911546991114611710748-12613448136942-1227
2-122-913111503-126115048-1261102-126110-22103-15-109-16-121-119-3121-4-106119-119-9369122-5779121
719-98-24-67-32918-98-236-19-10715326827-76102-61100108-12718-438331-37109-102-57-9942-11389-10374
-77-5-4-107109-11847342222-63-48-7468-17-1067033-56111-33-54-16-105-62-76-1282011-1664-12158-4915-
88-53-9-29-2994-49-54-5211-1364-212121-12396-127-353-396185117-681229-434246070-109818119-4858-128
-106-1279248-49110-44-81-121494199-118-17-106-71106828294-93-110-110-106-415084-127126-45-12331421
-61-2757-24-128-28-25111-52113121-56-98-5821527282-47255245104-111-55-1099747-115-11172-287-12526-
79-12430-119421360-107-6430-5410282-52-51-128533354-116672757-77-75-111-72-118-10114-84484825-40-1
8-70-24-9111-61-5391-8034125-12632-16-19-128112030-8-427523101-93-127-5348-127-5648146385291511-14
4325-9648-127-110638529174-127-11848-127-121-12623119101989799991011151154611211999111109109115469
911146117107-1262211211945115994548494611211999111109109115461081119997108-12626651171161116810511
59911111810111446808767111109109115461081119997108-12626651171161116810511599111118101114468087671
11109109115469911146117107-12613808767111109109115461081119997108-12613808767111109109115469911146
11710748196385293741248106843615573148126385291911-14248048136942-12272-122-913115503-12611081-930
6613-74953718-12745-14-25-94107-80-5-45-2231536-1728-12897-8587577-1252765-892896-83-10267-7926-20
-9841-1079-12-29-4315671111357-684036-40-5129-91-24-461066-12306-65-9118-89115191071-30-20-1067161
-83-91-74105-931649-48-96126-13-71-118-8967567-40-64-104-113-31-51-102357125100-50113-103-113123-9
873-627067-25-908-10131118125122-71-115-37-1850-1055851-31410-77-7312-36848124-26104-10711043-2048
-48-12666611759121127-2960-1571-9-95-98-1036911610-74221-32-25114-108749933-7147562114-3635-101-81
-1058-73108-61-78-128-116-715155112714-37-18-84-8331-2716-1174257-76-5-1598-15-12875-98-7329632178
-10714-123-6312212-1028359-56-76-683-873987-2120-845954-7617-71-57999828110], size=926
Exception : Microsoft.Exchange.Rpc.ServerUnavailableException: Error 0x6ba (The RPC server is unavailable)
from ClientAsyncCallState.CheckCompletion: RpcAsyncCompleteCall
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 2
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1710
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: 0 (0x00000000)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 13
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1352
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: -1073606646 (0xC002100A)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0xC002100A
EEInfo: Detection location: 1380
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 12175 (0x00002F8F)
EEInfo: prm[1]: Unicode string: /rpc/rpcproxy.dll?PW-SC-01.companyname.local:6001
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0x00010000
EEInfo: Detection location: 1385
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 8 (0x00000008)
EEInfo: prm[1]: Binary Buffer: [48-1263-10248-1262-126-9632122164676121-3988104-118-11373-61-94
-111-112-98-1217048136942-12272-122-91311550483449324830638543192311910198979999101115115461121199
91111091091154699111461171074830231349524949485349505348484990231349574949485349505348484990483449
324830638543192311910198979999101115115461121199911110910911546991114611710748-12613448136942-1227
2-122-913111503-126115048-1261102-126110-22103-15-109-16-121-119-3121-4-106119-119-9369122-5779121
719-98-24-67-32918-98-236-19-10715326827-76102-61100108-12718-438331-37109-102-57-9942-11389-10374
-77-5-4-107109-11847342222-63-48-7468-17-1067033-56111-33-54-16-105-62-76-1282011-1664-12158-4915-
88-53-9-29-2994-49-54-5211-1364-212121-12396-127-353-396185117-681229-434246070-109818119-4858-128
-106-1279248-49110-44-81-121494199-118-17-106-71106828294-93-110-110-106-415084-127126-45-12331421
-61-2757-24-128-28-25111-52113121-56-98-5821527282-47255245104-111-55-1099747-115-11172-287-12526-
79-12430-119421360-107-6430-5410282-52-51-128533354-116672757-77-75-111-72-118-10114-84484825-40-1
8-70-24-9111-61-5391-8034125-12632-16-19-128112030-8-427523101-93-127-5348-127-5648146385291511-14
4325-9648-127-110638529174-127-11848-127-121-12623119101989799991011151154611211999111109109115469
911146117107-1262211211945115994548494611211999111109109115461081119997108-12626651171161116810511
59911111810111446808767111109109115461081119997108-12626651171161116810511599111118101114468087671
11109109115469911146117107-12613808767111109109115461081119997108-12613808767111109109115469911146
11710748196385293741248106843615573148126385291911-14248048136942-12272-122-913115503-12611081-930
6613-74953718-12745-14-25-94107-80-5-45-2231536-1728-12897-8587577-1252765-892896-83-10267-7926-20
-9841-1079-12-29-4315671111357-684036-40-5129-91-24-461066-12306-65-9118-89115191071-30-20-1067161
-83-91-74105-931649-48-96126-13-71-118-8967567-40-64-104-113-31-51-102357125100-50113-103-113123-9
873-627067-25-908-10131118125122-71-115-37-1850-1055851-31410-77-7312-36848124-26104-10711043-2048
-48-12666611759121127-2960-1571-9-95-98-1036911610-74221-32-25114-108749933-7147562114-3635-101-81
-1058-73108-61-78-128-116-715155112714-37-18-84-8331-2716-1174257-76-5-1598-15-12875-98-7329632178
-10714-123-6312212-1028359-56-76-683-873987-2120-845954-7617-71-57999828110], size=926
at Microsoft.Exchange.Rpc.ClientAsyncCallState.CheckCompletion()
at Microsoft.Exchange.Rpc.ExchangeClient.ClientAsyncCallState_Connect.End(IntPtr&
contextHandle, TimeSpan& pollsMax, Int32& retryCount, TimeSpan& retryDelay, String& dn
PoisonedCount : 0
ExecutionId : 63105129
SampleValue : 33.5194
ExecutionContext : Mailbox logon verification
EMSMDB.Connect()
Task produced output:
- TaskStarted = 10/11/2014 13:50:03
- TaskFinished = 10/11/2014 13:50:03
- Exception = Microsoft.Exchange.Rpc.ServerUnavailableException: Error 0x6ba (The RPC
server is unavailable) from ClientAsyncCallState.CheckCompletion: RpcAsyncCompleteCall
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 2
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1710
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: 0 (0x00000000)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 13
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1352
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: -1073606646 (0xC002100A)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0xC002100A
EEInfo: Detection location: 1380
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 12175 (0x00002F8F)
EEInfo: prm[1]: Unicode string: /rpc/rpcproxy.dll?PW-SC-01.companyname.local:6001
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0x00010000
EEInfo: Detection location: 1385
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 8 (0x00000008)
EEInfo: prm[1]: Binary Buffer: [48-1263-10248-1262-126-9632122164676121-3988104-118-11373-61-94
-111-112-98-1217048136942-12272-122-91311550483449324830638543192311910198979999101115115461121199
91111091091154699111461171074830231349524949485349505348484990231349574949485349505348484990483449
324830638543192311910198979999101115115461121199911110910911546991114611710748-12613448136942-1227
2-122-913111503-126115048-1261102-126110-22103-15-109-16-121-119-3121-4-106119-119-9369122-5779121
719-98-24-67-32918-98-236-19-10715326827-76102-61100108-12718-438331-37109-102-57-9942-11389-10374
-77-5-4-107109-11847342222-63-48-7468-17-1067033-56111-33-54-16-105-62-76-1282011-1664-12158-4915-
88-53-9-29-2994-49-54-5211-1364-212121-12396-127-353-396185117-681229-434246070-109818119-4858-128
-106-1279248-49110-44-81-121494199-118-17-106-71106828294-93-110-110-106-415084-127126-45-12331421
-61-2757-24-128-28-25111-52113121-56-98-5821527282-47255245104-111-55-1099747-115-11172-287-12526-
79-12430-119421360-107-6430-5410282-52-51-128533354-116672757-77-75-111-72-118-10114-84484825-40-1
8-70-24-9111-61-5391-8034125-12632-16-19-128112030-8-427523101-93-127-5348-127-5648146385291511-14
4325-9648-127-110638529174-127-11848-127-121-12623119101989799991011151154611211999111109109115469
911146117107-1262211211945115994548494611211999111109109115461081119997108-12626651171161116810511
59911111810111446808767111109109115461081119997108-12626651171161116810511599111118101114468087671
11109109115469911146117107-12613808767111109109115461081119997108-12613808767111109109115469911146
11710748196385293741248106843615573148126385291911-14248048136942-12272-122-913115503-12611081-930
6613-74953718-12745-14-25-94107-80-5-45-2231536-1728-12897-8587577-1252765-892896-83-10267-7926-20
-9841-1079-12-29-4315671111357-684036-40-5129-91-24-461066-12306-65-9118-89115191071-30-20-1067161
-83-91-74105-931649-48-96126-13-71-118-8967567-40-64-104-113-31-51-102357125100-50113-103-113123-9
873-627067-25-908-10131118125122-71-115-37-1850-1055851-31410-77-7312-36848124-26104-10711043-2048
-48-12666611759121127-2960-1571-9-95-98-1036911610-74221-32-25114-108749933-7147562114-3635-101-81
-1058-73108-61-78-128-116-715155112714-37-18-84-8331-2716-1174257-76-5-1598-15-12875-98-7329632178
-10714-123-6312212-1028359-56-76-683-873987-2120-845954-7617-71-57999828110], size=926
at Microsoft.Exchange.Rpc.ClientAsy
FailureContext :
ExtensionXml :
ResultType : Failed
RetryCount : 0
ResultName : 75641e34aa494fceaad7181b56dd7b29-OutlookRpcDeepTestProbe/NEW2013
IsNotified : False
ResultId : 1748063
ServiceName : InvokeNow
StateAttribute1 : Momt
StateAttribute2 : UnknownIssue
StateAttribute3 : PW-SC-01.companyname.local
StateAttribute4 : Unknown
StateAttribute5 : {C54AD38D-1E00-4F53-ABAE-26518C3FF82F}
StateAttribute6 : 0
StateAttribute7 : 0
StateAttribute8 : 0
StateAttribute9 : 0
StateAttribute10 : 0
StateAttribute11 : Momt
StateAttribute12 :
StateAttribute13 : VgEAVAdXaW5kb3dzQwBBCEtlcmJlcm9zTA9QV0NPTU1TXG5hdGhhbmhVLlMtMS01LTIxLTIwNTc0OTEwMzItMzE4NDA2NDk3OC
0xNTQ2MTE0ODM1LTI2MzJHHQAAAAcAAAAtUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtNTEzBwAA
AAdTLTEtMS0wBwAAAAdTLTEtNS0yBwAAAAhTLTEtNS0xMQcAAAAIUy0xLTUtMTUHAADAE1MtMS01LTUtMC0zNDc3ODcxMTMHAA
AALlMtMS01LTIxLTIwNTc0OTEwMzItMzE4NDA2NDk3OC0xNTQ2MTE0ODM1LTQxODcHAAAALVMtMS01LTIxLTIwNTc0OTEwMzIt
MzE4NDA2NDk3OC0xNTQ2MTE0ODM1LTUxMgcAAAAuUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtND
E3NAcAAAAuUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtMzU3MAcAAAAuUy0xLTUtMjEtMjA1NzQ5
MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtNDEyMgcAAAAuUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMT
Q4MzUtMTE2NAcAAAAuUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtMTE0MQcAAAAuUy0xLTUtMjEt
MjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtNDE1MwcAAAAuUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LT
E1NDYxMTQ4MzUtNDE0NQcAAAAtUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtNTE4BwAAAC5TLTEt
NS0yMS0yMDU3NDkxMDMyLTMxODQwNjQ5NzgtMTU0NjEx
StateAttribute14 :
StateAttribute15 :
StateAttribute16 : 0
StateAttribute17 : 0
StateAttribute18 : 0
StateAttribute19 : 0
StateAttribute20 : 0
StateAttribute21 : /o=companyname/ou=first administrative group/cn=Recipients/cn=NathanH
StateAttribute22 : EMSMDB.Connect()
StateAttribute23 : https://pw-sc-01.companyname.local:444/rpc/rpcproxy.dll?PW-SC-01.companyname.local:6001
StateAttribute24 : Negotiate
StateAttribute25 : [33]10/11/2014 13:50:03 [FAILED!] EMSMDB.Connect();
Identity : fcd6159dd8fe42aebf10100cc4934356
IsValid : True
ObjectState : New -
Mails not going from SOST to external mail ids
Hi all,
I have to send mails to external mail ids in workflow.
when my workflow triggers, mails are coming in SOST transaction.
But, when i try any mail to send further to its respective mail id, its giving the following error:-
" no route available from WF-BATCH to mail-id"
i tried sending mails manually as well as by using RSCONN01 also, but no results.
Our BASIS consultant has already done SCOT configuration. Please guide me what is the issue?
Is some configuration pending from Workflow side or BASIS side?
Regards
Navjot.Hello Navjot,
if you have some basis background you can check TCode SCOT there you can see if the mail connect for external mails is configured correctly. There shoud be at least a node for SMTP communication. If there is such node check that sending s not restricted to certain adresses. Furthermore you could check over the menu if the default domain is set properly.
Kind Regards
Roman -
Internal and External Mail Exchange servers server not communicating with IronPort
Hello Support Community,
I have setup external mail exchange server and an internal mail exchange server to test out ironport, those two are not communicating via IronPort neither are they both recieving eachothers sent messages in their inbox, i have setup a smart host in both of those servers to point to ironport but thats still of no help. I have two smtp routes setup as well one's recieving domain: dummy.local which is external and its destination host: softheon.local which is internal which means its smart host is pointing to ironport's data 1. Is there something that im missing which is not letting these two mail exchange servers connect to each other as well as connect with the ironport to catch the msgs being sent
thanksAre you trying to relay through the appliance, or just email the appliance?
If trying to relay through the appliance, make sure the IP address of your exchange server is added to the RELAYLIST under the HAT (host access table) located under Mail Policies Tab - Host Access Table. Click on the RELAYLIST and add the IP - submit and commit changes.
If you are just trying to email the appliance, you may be getting dropped at the handshake level based on reputation (or lack thereoff).
From your exchange boxes, open up a command prompt and telnet to the ironport on port 25 and initiate a command line email.
So:
telnet IP-OF-IRONPORT 25 (hit enter, you should connect up and see the IronPort banner)
helo (type helo - from here you'll probably get dropped by the IronPort)
mail from: [email protected] (if you dont get dropped put in your email address)
rcpt to: [email protected] (put in the other email address)
data (type data and hit enter)
This is a test. (type anything, this is the message body)
. (when done typing, type a single . (period) and hit enter. The email should send if you got that far.
You most likely need to add the IP addresses of your exchagne boxes to the WHITELIST under the HAT to resolve any reputation issues from your test exchange boxes.
Regards,
Chris -
Sending external mail using SO_NEW_DOCUMENT_ATT_SEND_API1
When i use this RFC by appending the internal table receiver with receiver: sapuser name and rec_type B it triggers mail to the sap user login .But when i give external email address for receiver with rec_type 'U' it is not triggering any mail.Can anyone please tell me how to use this RFC in sending external mails??
I went back and you are right "INT" was not the REC_TYPE it was the COM_TYPE.
Sorry for any confusion caused.
However,
I suggest 2 more tests and then I give up and can not think about anything else.
Try:
#1
REC_TYPE = 'X'.
if it does not work.
#2
REC_TYPE = 'R'.
Hope that will do the trick. I was trying a lot when I had to get that working some time ago.
And surely the other colleagues point to something which must be setup as well. Transaction SCOT the SMTP settings.
Furthermore there could be another issue. I remember that I worked at a client who had turned off the send settings on their email server. So SAP finished everything and handed the emails on to a mail server. The mail server had a setting to block any emails from the development environment.
So that might be another cause of your issue. -
Can't receive from external mail
I has look through the forum but unable to find a solution to my problem, so I hope someone here can help.
I just upgrade one of our server from Tiger 10.4.11 to Leopard Server 10.5.5, now we only can send and receive inside our lan, but only can send, can't receive from outside our lan.
As far as I can tell all our MX, and PTR are fine and we are not in any of the RBL.
I think the problem might have something to do with NAT, but not sure where to check.
Here is the postconf output
xserve:~ root# postconf -n
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = smtp-amavis:http://127.0.0.1:10024
daemon_directory = /usr/libexec/postfix
debugpeerlevel = 2
enableserveroptions = yes
html_directory = no
inet_interfaces = all
mail_owner = _postfix
mailboxsizelimit = 0
mailbox_transport = cyrus
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
mapsrbldomains =
messagesizelimit = 10485760
mydestination = $myhostname,localhost.$mydomain,localhost,douglaspark.school.nz,mail.douglaspar k.school.nz
mydomain = douglaspark.school.nz
mydomain_fallback = localhost
myhostname = mail.douglaspark.school.nz
mynetworks = 127.0.0.0/8,10.0.1.0/24,202.174.163.117
newaliases_path = /usr/bin/newaliases
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = _postdrop
smtpdclientrestrictions = permit_mynetworks zen.spamhaus.org permit
smtpdenforcetls = yes
smtpdpw_server_securityoptions = cram-md5,plain,login
smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
smtpdsasl_authenable = yes
smtpdtls_certfile = /etc/certificates/mail.douglaspark.school.nz.crt
smtpdtls_keyfile = /etc/certificates/mail.douglaspark.school.nz.key
smtpduse_pwserver = yes
smtpdusetls = yes
unknownlocal_recipient_rejectcode = 550
Here is the Delivery Notification.
This report relates to a message you sent with the following header fields:
Message-id: <1222931212.48e4730c39ea4@www.*.net.nz>
Date: Thu, 02 Oct 2008 20:06:52 +1300 (NZDT)
From: *@paradise.net.nz
To: Sochet Ly <***@douglaspark.school.nz>
Subject: Re: test
Your message cannot be delivered to the following recipients:
Recipient address: ****@douglaspark.school.nz
Reason: Server rejected MAIL FROM address.
Diagnostic code: smtp;530 5.7.0 Must issue a STARTTLS command first
Remote system: dns;mail.douglaspark.school.nz
(TCP|203.97.33.68|59550|202.174.163.117|25)
Reporting-MTA: dns;smtp5.clear.net.nz (tcp-daemon)
Original-recipient: rfc822;*@douglaspark.school.nz
Final-recipient: rfc822;*@douglaspark.school.nz
Action: failed
Status: 5.0.0 (Server rejected MAIL FROM address.)
Remote-MTA: dns;mail.douglaspark.school.nz
(TCP|203.97.33.68|59550|202.174.163.117|25)
Diagnostic-code: smtp;530 5.7.0 Must issue a STARTTLS command first
Thanks in advance.
<edited by host>Hi pterobyte,
I set logging level to information, and then send myself an email inside our lan, send and receive ok, also sent an email to my external email address, then reply from external mail address here is the mail.log
Oct 3 12:18:53 xserve postfix/smtpd[37952]: connect from xserve.douglaspark.school.nz[202.174.163.117]
Oct 3 12:18:54 xserve postfix/smtpd[37952]: 147EC26C229: client=xserve.douglaspark.school.nz[202.174.163.117], sasl_method=CRAM-MD5, sasl_username=sochetly
Oct 3 12:18:54 xserve postfix/cleanup[37958]: 147EC26C229: message-id=<[email protected]>
Oct 3 12:18:54 xserve postfix/qmgr[84]: 147EC26C229: from=<*@douglaspark.school.nz>, size=647, nrcpt=1 (queue active)
Oct 3 12:18:57 xserve postfix/smtpd[37966]: connect from localhost[127.0.0.1]
Oct 3 12:18:57 xserve postfix/smtpd[37966]: 59AD026C246: client=localhost[127.0.0.1]
Oct 3 12:18:57 xserve postfix/cleanup[37958]: 59AD026C246: message-id=<096B6230-9CCE-4451-B018-A509BFAD7DBC@**.school.nz>
Oct 3 12:18:57 xserve postfix/qmgr[84]: 59AD026C246: from=<**@douglaspark.school.nz>, size=1306, nrcpt=1 (queue active)
Oct 3 12:18:57 xserve postfix/smtpd[37966]: disconnect from localhost[127.0.0.1]
Oct 3 12:18:57 xserve postfix/smtp[37959]: 147EC26C229: to=<*@douglaspark.school.nz>, relay=127.0.0.1[127.0.0.1]:10024, delay=3.4, delays=0.09/0.17/0.03/3.1, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 59AD026C246)
Oct 3 12:18:57 xserve postfix/qmgr[84]: 147EC26C229: removed
Oct 3 12:18:57 xserve postfix/pipe[37969]: 59AD026C246: to=<*@douglaspark.school.nz>, relay=cyrus, delay=0.53, delays=0.01/0.07/0/0.45, dsn=2.0.0, status=sent (delivered via cyrus service)
Oct 3 12:18:57 xserve postfix/qmgr[84]: 59AD026C246: removed
Oct 3 12:19:33 xserve postfix/smtpd[37952]: 5DFD426C264: client=xserve.douglaspark.school.nz[202.174.163.117], sasl_method=CRAM-MD5, sasl_username=sochetly
Oct 3 12:19:33 xserve postfix/cleanup[37958]: 5DFD426C264: message-id=<[email protected]>
Oct 3 12:19:33 xserve postfix/qmgr[84]: 5DFD426C264: from=<*@douglaspark.school.nz>, size=618, nrcpt=1 (queue active)
Oct 3 12:19:35 xserve postfix/smtpd[37966]: connect from localhost[127.0.0.1]
Oct 3 12:19:35 xserve postfix/smtpd[37966]: 84FFE26C28B: client=localhost[127.0.0.1]
Oct 3 12:19:35 xserve postfix/cleanup[37958]: 84FFE26C28B: message-id=<[email protected]>
Oct 3 12:19:35 xserve postfix/qmgr[84]: 84FFE26C28B: from=<**@douglaspark.school.nz>, size=1099, nrcpt=1 (queue active)
Oct 3 12:19:35 xserve postfix/smtpd[37966]: disconnect from localhost[127.0.0.1]
Oct 3 12:19:35 xserve postfix/smtp[37959]: 5DFD426C264: to=<*@paradise.net.nz>, relay=127.0.0.1[127.0.0.1]:10024, delay=2.3, delays=0.03/0.01/0.04/2.2, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 84FFE26C28B)
Oct 3 12:19:35 xserve postfix/qmgr[84]: 5DFD426C264: removed
Oct 3 12:19:36 xserve postfix/smtp[38021]: 84FFE26C28B: to=<**@paradise.net.nz>, relay=mx.paradise.net.nz[203.97.33.212]:25, delay=0.86, delays=0.01/0.02/0.58/0.26, dsn=2.0.0, status=sent (250 ok: Message 551665631 accepted)
Oct 3 12:19:36 xserve postfix/qmgr[84]: 84FFE26C28B: removed
Oct 3 12:20:14 xserve postfix/smtpd[38034]: connect from smtp5.clear.net.nz[203.97.33.68]
Oct 3 12:20:17 xserve postfix/smtpd[38034]: disconnect from smtp5.clear.net.nz[203.97.33.68]
I can see it connected from my ISP server, but then in disconnect straight away.
and here is some recent mailaccess.log
ct 3 12:14:04 xserve pop3s[37852]: starttls: TLSv1 with cipher AES128-SHA (128/128 bits new) no authentication
Oct 3 12:14:04 xserve pop3s[37852]: login: [10.0.1.83] supportstaff APOP+TLS User logged in
Oct 3 12:18:27 xserve imaps[37939]: TLS server engine: cannot load CA data
Oct 3 12:18:27 xserve imaps[37939]: starttls: TLSv1 with cipher AES128-SHA (128/128 bits new) no authentication
Oct 3 12:18:29 xserve imaps[37939]: login: xserve.douglaspark.school.nz [202.174.163.117] sochetly CRAM-MD5+TLS User logged in
Oct 3 12:18:29 xserve imaps[37943]: TLS server engine: cannot load CA data
Oct 3 12:18:29 xserve imaps[37943]: starttls: TLSv1 with cipher AES128-SHA (128/128 bits reused) no authentication
Oct 3 12:18:29 xserve imaps[37943]: login: xserve.douglaspark.school.nz [202.174.163.117] sochetly CRAM-MD5+TLS User logged in
Oct 3 12:18:29 xserve imaps[37943]: skiplist: recovered /var/imap/user/s/sochetly.seen (2 records, 2848 bytes) in 0 seconds
Oct 3 12:18:29 xserve imaps[37944]: TLS server engine: cannot load CA data
Oct 3 12:18:29 xserve imaps[37944]: starttls: TLSv1 with cipher AES128-SHA (128/128 bits reused) no authentication
Oct 3 12:18:29 xserve imaps[37944]: login: xserve.douglaspark.school.nz [202.174.163.117] sochetly CRAM-MD5+TLS User logged in
Oct 3 12:18:32 xserve imaps[37939]: starttls: TLSv1 with cipher AES128-SHA (128/128 bits reused) no authentication
Oct 3 12:18:32 xserve imaps[37939]: login: xserve.douglaspark.school.nz [202.174.163.117] sochetly CRAM-MD5+TLS User logged in
Oct 3 12:18:32 xserve imaps[37946]: TLS server engine: cannot load CA data
Oct 3 12:18:32 xserve imaps[37946]: starttls: TLSv1 with cipher AES128-SHA (128/128 bits reused) no authentication
Oct 3 12:18:32 xserve imaps[37946]: login: xserve.douglaspark.school.nz [202.174.163.117] sochetly CRAM-MD5+TLS User logged in
Oct 3 12:18:37 xserve imaps[37946]: Expunged 10 messages from user.sochetly.Sent Messages
Oct 3 12:18:57 xserve lmtpunix[37971]: Delivered: <[email protected]> to mailbox: user.sochetly
Oct 3 12:19:03 xserve imaps[37943]: Expunged 9 messages from user.sochetly
Oct 3 12:19:04 xserve pop3s[37977]: TLS server engine: cannot load CA data
Oct 3 12:19:04 xserve pop3s[37977]: starttls: TLSv1 with cipher AES128-SHA (128/128 bits new) no authentication
Oct 3 12:19:04 xserve pop3s[37977]: login: [10.0.1.83] supportstaff APOP+TLS User logged in
Oct 3 12:24:04 xserve pop3s[38238]: TLS server engine: cannot load CA data
Oct 3 12:24:04 xserve pop3s[38238]: starttls: TLSv1 with cipher AES128-SHA (128/128 bits new) no authentication
Oct 3 12:24:04 xserve pop3s[38238]: login: [10.0.1.83] supportstaff APOP+TLS User logged in
Can you tell me what is this message mean.
TLS server engine: cannot load CA data.
Thanks.
Jet
<edited by host> -
Send notification to external mail id when work item reach users inbox
hi all ,
i would like to know wat are all the settings required for sending an external mail when a user recieves a work item. i think it can be done by running the program rswuwfml .but wat are all the settings required to be done before running the program .....
Useful answers will be rewarded.......What the??!!!! I totally missed this before and actually found it quite acidentally....
>Yep true! Totally agree with Kjtetil, it adds to an already noisy forum and I am >afraid if others start aping it will be brought down on level with the XYZ forum. >And we don't want that!
>Anyone volunteering to have the 'M' flag?
Though I cannot comprehend what you are trying to get at or say I will, attempt to set the record straight.
Yes I have said that on another thread. I am not asking for points anywhere, I am happy to receive and happier to solve someone's problem.
The issue with this thread is the author obviously has not bothered to do any investigation. I am not for spoon feeding just for the sake of some points, I am willing to help those who do some bit from their end as well who encounter a genuine stumbling block.
My reference to "reward" was with a bit of sarcasm, if you know what that means.
Maybe you are looking for
-
Can I use a USB hub to connect more than 1 hard drive/flash drive device to the EA4500?
Can I use a USB hub to connect more than 1 hard drive/flash drive device to the EA4500?
-
Applying transaction log corrupted database?
Hi experts, Symptoms: I built a standby system this Monday and I completed a full DB restore without errors. I used log shipping to apply logs but an error occurred: SQL Server detected a logical consistency-based I/O error: incorrect pageid (expec
-
Hi guys, I have to use a Vector object to store a growable array of objects,but I have an implementative question : I have to create the Vector only the first time the class cointaining it will be extecuted , then I have to add elements , without del
-
Property Inspector Help Please!!
I am running Dreamweaver MX Educator version in OSX 10.4.7 - everything works - except I am unable to get the full display in property inspector - I don't have the ability to center tables. What's up? And how do I fix? Thanks, Steve
-
Ruleauthor.ear and rulehelp.ear for Oracle Business Rules
I'm following the instructions for installing Oracle Business Rules in Standalone OC4J. The instructions say you need to get files (in the subject line of this thread) from the full Oracle App Server install. This was a bit of a surprise because I'm