Not send mail for external domains

Hi,
I have installed OCS 10g(10.1.2) in linux. All components ok, but i not send mail for external domain.
Att,
Mesti

I remember in version 9.0.2 that i configure in SMTP_OUTBOUND the IP of DNS external to send mail for other domains.
Mesti

Similar Messages

Outlook does not send mail to extern domains

It says that "[550] 5.7.1 Rcpt command failed: Mail denied due to site's policy".
Web Access Client at the same time send mail to outside without any problems.
Outlook connector and Collaboration Suite ver. - 10.1.2.
Where is problem?

you should change the next value in smtp inbound
Enable Routing Control : active
allow message relay : true
allow message relay domain : *
flag process: -l
Recipient Rewriting Rules: $*@your host target smtp,$1@your domain target smtp,
example:
$*@mail.sinux.com.pe,$[email protected],
you should change the next value in smtp outbound
rele smtp : ip of your source mail or relay :port smtp
flag process: -l
Atte.
Yuri Garcia S.

Failed to send mail to external domain via portal

Hi Gurus,
By following the configuraion instructions in SAP library - Collaboration - Groupware - Installing and Configuring E-Mail Connectivity, I managed to send mail to recipients who reside in same domain e.g. [email protected] via portal.
However, I failed to send mail to external domain e.g. [email protected]. I got the following error message:
The mail could not be sent to the specified recipients com.sap.ip.collaboration.gw.impl.transport.javamail.exception.MailSendException: The mail could not be sent to the specified recipients
 at com.sap.ip.collaboration.gw.impl.transport.javamail.JavaMailTransport.sendMail(JavaMailTransport.java:183)
--------- exception is chained. Original exception ------------
javax.mail.SendFailedException: Invalid Addresses;
nested exception is:
 javax.mail.SendFailedException: 553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)
 at com.sun.mail.smtp.SMTPTransport.rcptTo(SMTPTransport.java:804)
 at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:320)
Please help.
Thanks alot.

Hi Ajey,
Thanks for your reply. I had tried your suggestion but same problem occurred with same error output.
Actually, I encounterred this error message before in my Microsoft Outlook, where System Admin returned me a mail saying that, my mail was undeliverable with the same error message. But this can be solved by applying the Internet Email Account Setting - Outgoing Server - My outgoing server (SMTP) require authentication.
So I am wondering,
1) This problem is caused by SMTP server?
2) Is there any workaround (like the Outlook Setting) I can configure in Portal?
Do you have any idea?
Thanks,
HauChee

Sending Mails to external domains

Hi,
Scenario:
--I am having OCS 10g 10.1.2.3.0 on a singlebox RHEL ES Rel3 (taroon update4)
--I have an Exchange Server on another box with Microsft Exchange Server
--There is one more Proxy Server Box with firewalls having a proxy port to access the internet
I was able to send mails from Oracle Workspaces to the OCS local domain but not to the external domains like yahoo.com, hotmail.com
I was not able to ping the yahoo mail server or hotmail mail server, since the intenet connection is not a direct connection.
Can i have any workaround for this.. or how can i configure the current system to facilitate sending mails from OCS to other email domains also..?
Many Thanks in advance..,
Regards,
Prasant

Hi,
We are having the same problems (mail to external domains). I didn't catch what was done to correct the problem. Could you please repeat what was set.
Thanks much,
Kim

Setting Up Mailserver to received and Send Mail for external Network

I have a G5 currenty running 10.3.9 Server with Mail services run and working fine, we are upgrading to 10.4 Server and would like our Sales Reps the ability to send and Receive mail from outside the office. How do I configure my server, Router, ISP and/or Mail clients to do this??? we are currently able to recieve mail from outside just not send.

I cannot find the Line #submission inet n - n -- smtpd in the Main.CF file...here is what I get when I open it
# Global Postfix configuration file. This file lists only a subset
# of all 250+ parameters. See the sample-xxx.cf files for a full list.
# The general format is lines with parameter = value pairs. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
# POSTFIX STILL WORKS AFTER EVERY CHANGE.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
#soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /private/var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
# Note: you need to stop/start Postfix when this parameter changes.
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4
# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain.
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see sample-virtual.cf).
# 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
# sample-smtpd.cf).
# 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
#mydestination = $myhostname, localhost.$mydomain $mydomain
#mydestination = $myhostname, localhost.$mydomain, $mydomain,
# mail.$mydomain, www.$mydomain, ftp.$mydomain
# REJECTING MAIL FOR UNKNOWN LOCAL USERS
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination and $inet_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 sample-local.cf).
# 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
# $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
unknown_local_recipient_reject_code = 450
# 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 file sample-smtpd.cf.
# 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 restriction in the
# file sample-smtpd.cf 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,
# - 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 in the file sample-smtpd.cf.
#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 = uucphost
#relayhost = [an.ip.add.ress]
# REJECTING UNKNOWN RELAY USERS
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a [email protected] address.
#relay_recipient_maps = hash:/etc/postfix/relay_recipients
# INPUT RATE CONTROL
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 50 SMTP server process
# limit, this limits the mail inflow to 50 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
# Insert text from sample-rewrite.cf if you need to do address
# masquerading.
# Insert text from sample-canonical.cf if you need to do address
# rewriting, or if you need username->Firstname.Lastname mapping.
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
# Insert text from sample-virtual.cf if you need virtual domain support.
# "USER HAS MOVED" BOUNCE MESSAGES
# Insert text from sample-relocated.cf if you need "user has moved"
# style bounce messages. Alternatively, you can bounce recipients
# with an SMTP server access table. See sample-smtpd.cf.
# TRANSPORT MAP
# Insert text from sample-transport.cf if you need explicit routing.
# ALIAS DATABASE
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
# It will take a minute or so before changes become visible. Use
# "postfix reload" to eliminate the delay.
#alias_maps = dbm:/etc/aliases
#alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases
# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi". This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
#alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
# ADDRESS EXTENSIONS (e.g., user+foo)
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5) 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".
#mailbox_transport = lmtp:unix:/file/name
#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
# and unknown@[$inet_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. See the file
# sample-smtpd.cf for an elaborate list of anti-UCE controls.
# 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 the sample-filter.cf file.
#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".
# By default, Postfix maintains deferred mail logfile information
# only for destinations that Postfix is willing to relay to (as
# specified in the relay_domains parameter). For other destinations,
# Postfix attempts to deliver ALL queued mail after receiving the
# SMTP "ETRN domain.tld" command, or after execution of "sendmail
# -qRdomain.tld". This can be slow when a lot of mail is queued.
# The fast_flush_domains parameter controls what destinations are
# eligible for this "fast ETRN/sendmail -qR" service.
#fast_flush_domains = $relay_domains
#fast_flush_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 = 10
# 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
xxgdb $daemon_directory/$process_name $process_id & sleep 5
# If you don't have X installed on the Postfix machine, try:
# 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
# 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/sbin/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
# 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.
sample_directory = /usr/share/doc/postfix/examples
# readme_directory: The location of the Postfix README files.
readme_directory = /usr/share/doc/postfix
# THE FOLLOWING DEFAULTS ARE SET BY APPLE
# bind to localhost only
inet_interfaces = all
# turn off relaying for local subnet
mynetworks_style = host
# mydomain_fallback: optional domain to use if mydomain is not set and
# myhostname is not fully qualified. It is ignored if neither are true.
mydomain_fallback = localhost
myhostname = jamestownpress.com
mailbox_transport = cyrus
enable_server_options = yes
luser_relay =
maps_rbl_domains = dun.dnsrbl.net
message_size_limit = 0
mydestination = $myhostname,localhost.$mydomain
smtpd_use_tls = no
smtpd_enforce_tls = no
smtpd_tls_loglevel = 0
smtpd_sasl_auth_enable = yes
smtpd_use_pw_server = yes
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination,permit
smtpd_pw_server_security_options = plain
server_enabled = 1
relayhost =
smtpd_client_restrictions = permit_mynetworks reject_rbl_client dun.dnsrbl.net permit
always_bcc =
mynetworks = 127.0.0.1/32,192.168.0.0/16,192.168.1.98,192.168.1.3,192.168.1.13,192.168.1.5,1 92.168.1.22,192.168.1.18,192.168.1.41
content_filter = smtp-amavis:[127.0.0.1]:10024
so what do I need to change

Groupwise not send mails to external users

Hello everyone.
I did a clean install of SBE with eDirectory, iManager, and Groupwise. Just when the installation can send emails to a user outside the domain (external user), but after restarting the mail server does not come to any external users, but if I receive them.

Originally Posted by amoron
Hello everyone.
I did a clean install of SBE with eDirectory, iManager, and Groupwise. Just when the installation can send emails to a user outside the domain (external user), but after restarting the mail server does not come to any external users, but if I receive them.
Did you setup internet addressing? Currently you have to manually setup internet addressing in Console One when setting up groupwise8 (see the docs for a how-to, its very easy). Without internet addressing, you'll be able to send emails to internal users, but not to external users, which seems to be the problem you are having.
Just FYI, this internet addressing problem is being addressed in the next patch, which is currently in testing.
-Hart

Problem in workflow sending mails to external domains like yahoo,gmail etc.

hi
i have one probs in my workflow that when i am sending mail to an external id it is not going to gmail,yahoo or hotmail etc.
it is being send to a particular domain say XYZ
but outside it ,no mail is send
and error is coming that recepient is unknown
we have firewalls being placed on smtp
and each and every setting in SCOT has been checked thorughly
but still mail except to one domain is not going outside
i have came across the info that since SAP doesn have any user id authentication but SMTP does has ,so when mail is being send outside the mail sending is failed,one option could be to disable the authentication at SMTP but thats doesn come inside the policy of client
so i think there must be a way out in SAP to deal with this
please suggest how can i send the mails externally,i ahve checked each and every thing inside my SMTP configuration ,adress is defined as * here but still mail is being send to internal domain of the client in which i am working ,but not at all to the external domains like gmail,yahoo etc.
any help will be highly appreciated
best regards
ashish

Hi Ashish,
I think you will need to check with your exchange guys because probably the exchange server will not relay the messages form the SAP server to external e-mail domains.
Regards,
Martin

Postfix will not send mail to external

Hi there!
I have a problem with postfix: i cannot send any mail to an external domain.
the message always appears in the mail queue with an MX-Lookup-Error
some information about the system:
The server has 2 NIC's :
eth0 : ip via dhcpcd from router, connects to the internal network
eth1 : ip via dhcpcd from router, the hot wire to the internet
i can reach any known (by me) mailserver via telnet on port 25 as normal user
i can ping every ip/tcp/whateveryouwant as normal user
but no mai delivery to any external mail server.
So what can be the problem?
Has anyone an idea?

ok, the postfix is running now for some weeks.
I'd solved the problem by reading and learning the postfix-configuration.
There's also a nice book (in german only) that has helped :
"Das Postfix-Buch" written by Per Heinlein.
It's written in a funny style, spiced up with real-live situations.
syl querdenker

Email Activity not sending emails for one domain - 10.1.3.4 MLR#10

I have four domains in my BPELConsole. My evey BPEL process has CatchAll block and I'm sending email notification with fault details.
Somehow, my BPEL processes from three domains are sending emails properly but myDomain4 is not sending emails even after successful execution of Email Activity.
1) I have compared the Email code with processes in other domain and they are similar.
2) orabpel.bpelnotification is not logging any error for this notification.
3) I never received any email from this domain. There was no error in logs during domain creation.
3) I am getting following in logs that sending email was successfully executed. It received Notification ID too
<2010-09-22 07:24:44,530> <DEBUG> <myDomain4.collaxa.cube.services> <oracle.bpel.services.notification.queue.QueueConnectionPool::QueueConnectionPool> Fetched a queue connection from pool java:comp/env/jms/Queue/NotificationSenderQueueConnectionFactory, available connections=4
<2010-09-22 07:24:44,534> <DEBUG> <myDomain4.collaxa.cube.services> <oracle.bpel.services.notification.queue.sender.Publisher::init> Start of send(type,caller,message) type = email caller = BPEL
<2010-09-22 07:24:44,534> <DEBUG> <myDomain4.collaxa.cube.services> <oracle.bpel.services.notification.queue.sender.Publisher::init> Notification ID 12834c63e81c20d0:-71064af1:42b35e5dab4:-7283
Please help/hint for any possible solution/debugging.

sometimes i have seen emails not being sent when the async invokes takes more time than the overall completion.. And yes, we might still see successful log as emails sent. FYI - I am with 10.1.3.3.1 MLR #8.
did you try just creating a email only process? switch off all other processes in that domain and initiate only this email process to see what happens..

CiscoWorks LMS 3.2 Not sending mail

HI,
I have got a CiscoWorks LMS which is not sending mail for HUM reports.
Here's the log that I receive when it is supposed to send the mail in smtp.log
[ Sun Oct 16 13:17:42 CAT 2011 ] INFO [MailUtility : isMailServerWorking] : The mail server [10.102.247.57] is responding
I can telnet to the server port 25. No authentication is required for sending mail to local domain.
There is a MacAfee Agent but it is configured to send mail.
I don't have a clue what is causing it.
Could you please help.
Thanks,
Ashley

Hi,
Are other email messages being sent as expected?
Do you have a size limit defined under CS > Server > Admin > System Preferences?
Have you verified the email leaves the LMS server?
Are there any related logs on you mail server?
Does the condition persist when you disable any host firewall and anti-virus agents?
Try some debugging:

N8 Mail for Exchange (can not send mails)

Hi guys,
I just got my new Nokia N8. I already setup Mail for Exchange via IMAP to sync the mails, contacts and the calendar of my private mailbox.
Everything runs alright. But I can not send mails via Mail for Exchange. If I push on "New Mail" the program say the command can not be executed and breaks down.
Does someone know how to fix that problem?
Thanks from Liechtenstein.
Phil

Hi,
I also had problems with unable to send emails.
I was getting error messages in the Mail for Exchange (MfE) log files such as
Setting DISK FULL status to false
Error occurred during sending mail. Setting status to waiting for reconnect
HTTP failure while sending messages.
I figured out a work around. The problem seemed to be with the certificate.
I ended up deleting the certificate and then only selecting "Accept this time only" which made everything work.
I am using a Nokia 5800.
To delete a certificate goto
Setting > Phone > Phone mgmt > Security > Certificate Management > Trusted site certificates
find the offending certificate and delete it.
The next time I tried to synchronize my emails with Mail for Exchange, I was asked to select whether to accept the certificate... press the option button.
Then select "accept this time only".
After doing that, the emails in the outbox were sent properly.
I have to figure out how to get this to work permanently, but for the moment it was a quick fix.
[I hope this helps. I tried to be as descriptive as possible and write with correct spelling so that search engines will collect it.]

Outlook and mail services/ can't send mail to external emails

I have been setting up os x server as a mail server for my company. I bound open directory to active directory but could not manage mail for the active directory users that way, so I started creating new users through open directory.
I've hit a couple snags that I can't quite figure out. First, I can send and receive mail to other open directory accounts fine, but not externally. I've set up my MX records and a name records for my Internet domain.
I can receive emails from an external email address, I.e. Gmail, but cannot send to them. It gets stuck in the mail server's queue. Information logs says operation timed out for smtp.gmail.com and their ip address.
I forwarded the ports, 25, 993, etc from my dsl router to my firewall router, then from there to my mail servers static ip address. I'm at a loss. If it matters, I'm on a residential dsl currently, my ISP claims to block port 25, but in the log it looks like it goes through and sees gmails ip.
Secondly, this is all through the mail.app for my MBP. When I set up outlook 2003 on xp, I can send emails, but it doesn't download any. No errors in either the information log or outlook, outlook says it completed successfully. If it matters, I was getting an error from outlook previously, helo error for not a fqdn, but I deleted a line in the main.cf that required fqdns.
I appreciate any help.

***EDIT*** I have outlook working....now it is just the external email thing. Again...my ISP says they block port 25, but I went into /etc/postmail/master.cf and added to have SMTP go on port 2525 and still no go. Any help would be greatly appreciated!
***END EDIT***
I apologize...here is the SMTP information level log for sending to gmail
Jun 29 16:36:18 ANSENMSG postfix/smtp[17251]: 152CB659FA: to=<***@*******.***>, relay=127.0.0.1[127.0.0.1]:10024, delay=6.3, delays=0.03/0/0/6.3, dsn=2.0.0, status=sent (250 2.0.0 Ok, id=15055-04, from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as 582EA65A09)
Jun 29 16:36:18 ANSENMSG postfix/qmgr[15069]: 152CB659FA: removed
Jun 29 16:36:48 ANSENMSG postfix/smtp[17299]: connect to mail.*******.com[**.***.**.**]:25: Operation timed out

Can not send mail from PR Workflow to the approver

Dear all,
I have issues about send mail from PR Workflow to the approver.
Now when user create PR and the corresponding user can receive the workflow items in SBWP.
But no email from the user to approver.
If I assign authorization SAP_ALL to the user that create PR. The approver can recieve the workflow item PR in SBWP and email to their mail
Can you tell me about the authorization that can allow the user to send the workflow item PR in SBWP and email to the approver?
Now user can send mail to external and internal mail and I also configured the mail server in SCOT and can successfully send a mail to users in SO01 by manually creating a message.
Now the approver not receive any email but can receive a workflow item in SBWP
Regards,
Pannee

Dear all,
Thank you for all suppport, Now I can solve issues.
Regards,
Pannee

How to send mails to external maild like yahoo

I am using 'SO_NEW_DOCUMENT_ATT_SEND_API1'
funtion module to send mails to internal office mail ids and working correctly .
Not the requirement changed . I need to send mail to external mail id like
per at the rateyahoo dot com also.
What can I do to send mail to external mailids like yahoo.
Do I need to use flag some thing ?
THANSK IN ADVANCE.

Hi,
Hi,
It is posible to send the mail to external address usign the above FM . But some configurations have to be maitnaied in SCOT Tcode for INT (Internet) ->SMTP protocal. we need to give the Mail Host and Mail Port all this information is usually done by the BASIS. Please approach them for these settings and try again with the FM. Here we have to configure it to Yahoo so that we can send the mail.
Regards
Lekha

Problem while sending mail to external mail ids

Hi All,
while trying to send mail to external mail ids through some custom program, i'm facing an error as "recipient not in address management".
Can anyone giude me why this is occuring and actually what is this Address management?
Thanks & Regards,
Anil.

Hi,
Check this sample code..
http://www.sapdevelopment.co.uk/reporting/email/email_mbody.htm
* Add the recipients email address
clear it_receivers.
refresh it_receivers.
 it_receivers-receiver = p_email.
it_receivers-rec_type = 'U'.
it_receivers-com_type = 'INT'.
it_receivers-notif_del = 'X'.
it_receivers-notif_ndel = 'X'.
append it_receivers.
what Fm you are using..?are you specifying like above for e-mail address..
Regards
vijay

Not send mail for external domains

Similar Messages

Maybe you are looking for