SMTP for external address

Hi!
I'm using was 620 and with transaction SCOT I have setup the node for SMTP. If I try to send a mail for a internal outlook address the system work fine, but if I try to send a mail for an external address (address with external internet provider) the system dosn't work and the error message is:
"802 = 550 5.7.1 Unable to replay for [email protected]"
[email protected] is an example.
How I can send mail with SCOT for external address?
Thank you very mutch,
Gianluca

Hi,
When you create a node in SCOT, you can choose HTTP or RFC. with HTTP type node, you can only communicate over http (like sending SMS) as the description says there. To use an internet mail functionality, you need to define an RFC type node.
With RFC type node, you will need to specify a RFC destination in the definition of the node (you can check the definition of some other nodes in SCOT by double-clicking them). This RFC Destination is nothing but a program (or a script) that is triggered from SAP for mail-send. This RFC destination must then have already been created using SM59, and must point to the right mail-send program.
Essentially, to be able to send emails outside to public email-ids, you need to have some way of connecting to the public mail network. The exe progra (like sendmail.exe) that is configured as an RFC destination enables this on SAP. Once you send a mail from SAP, it is sent to this configured RFC destination, which runs the corresponding OS level exe to connect to the public mail network and send the mail.
SAP doesn't provide such exe programs so you will need to procure it on your own (as far as I know). Once you have such a program, it should be possible to do the rest of the setup to have an RFC type node.
cheers,
Message was edited by: Ajay Das

Similar Messages

Delivery report shows status of Pending for external address. Email sent to both internal and external addresses.

We have an Exchange 2013 on-premise server and seem to have an issue with emails sent to internal and external users at the same time.
The issue came to light because someone sent an email to 44 recipients, of which one was internal. None of the external recipients received the email. I checked the delivery report in the EAC and found the internal email marked as 'Delivered' and all of
the external ones marked as 'Pending'. I checked the queues and there were none. I did some testing and sent an email to just one of the external addresses on the list, it arrived. I tried sending the email again to all of the recipients, the external ones
all showed 'Pending'. I tried it again, but this time excluded the internal email address and all of the 43 external emails were immediately delivered.
So it seems that the issue only arises when we are sending to both internal and external addresses.
I then tried a test email to one internal address and one external address. The Delivery report says that the internal address was delivered immediately, while the external address is 'Pending' and gives more information saying: 'Message delivery is taking
longer than expected. There may be system delays. For more information, contact your helpdesk.'. To add further mystery to this, the email was actually delivered.
So, I have two concerns:
First is seems that some emails sent both internally and externally are only arriving internally. This is a huge problem because I don't know how many have been affected. There may be many lost emails we don't know about.
Second, it looks like I can't trust the delivery report. It says pending for some emails which didn't arrive, but it also says pending for some which did arrive. That is no good at all.
For info the server is running Windows Server 2012. I have run a Microsoft Update to check if there are any to apply and the only Exchange one is a spam filter update, which I doubt has any bearing but I will apply when I get chance.

Hi Neil,
According to the description, I find a related KB on Exchange 2010:
https://support.microsoft.com/kb/2694474?wa=wsignin1.0
It has the similar situation as yours.
This issue occurs because a function in a message tracking component tries to obtain the information for the recipient instead of the external recipient.
Please try to upgrade to the latest Exchange update to check whether this issue can be solved.
Also please check whether Throttling has been set.
Please run "Get-TransportService | fl" to check the MaxOutboundConnections parameter value.
More details to see:
Message throttling
http://technet.microsoft.com/en-us/library/bb232205(v=exchg.150).aspx
Thanks
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

SMTP for external IMAP users

When I try to send through any e-mail or phone app from outside the network I get an error on the GWIA stating - IP connection refused. I have a generic setup for the GWIA and the port open through the firewall.
What can be missing?

Check your GWIA settings. Are you allowing anonymous connections to port 25? Generally, that is a bad thing, so it probably is not.
Otherwise I would blame the firewall, but if the erro shows on the GWIA, then it is a GWIA issue.
--El
Originally Posted by jtdb2011
When I try to send through any e-mail or phone app from outside the network I get an error on the GWIA stating - IP connection refused. I have a generic setup for the GWIA and the port open through the firewall.
What can be missing?

External SMTP server, From address

I have googled a good number of postings about this but just couldn't quite find the right solution. Surely this can't be that hard. Running Leopard, here's what I'm trying to do:
Use Mail to read & send emails from my work server as well as my .Mac account.
Easy enough, you would think. Sorry if this is too obvious but I'm a new Mac devotee (though this has rocked my boat a bit!). So, here are the problems I've encountered:
1) Tried to add an External Server to MobileMe. Problem: Can't my external address as reply-to
2) Tried to add the account to Mail. The SMTP server doesn't seem to want to take the password that I know works for Outlook and keeps the account "Offline". When I try to send an email using this in the From, it gives me the outgoing email error, allows me to edit or select servers. Selecting it again gives the same erorr.
3) Tried to just use the default Mac SMTP server for this external account, but still get an error when trying to send.
Please help me get the right solution!
Thanks,
R

The MobileMe .mac/.me smtp can only be used when sending from a MobileMe address, and not any others.
What is the source of the SMTP you are trying to use with the other account? What Port are you presenting that SMTP on, and how have you selected to authenticate it?
Ernie

Lync 2013 - Address Book Synchronization Issues for External Users

I recently deployed Lync Server 2013 in my organization. Everything works fine except for the address book synchronizing issues and the mobility access. I would really appreciate if someone could share their knowledge as I have done lot of troubleshooting,
not sure if I have missed something. Please note my setup below for the External Web Services.
Lync Front End:
Listening: 8080 4443
Published: 80 443
I have published my External Web Services URL and the following ports are open: 4443, 443, 8080
When I look at the Lync Client Configuration, ABS Server External URL is pointing to https://lyncexternalweb.domain.com:443/abs/handler. However, GAL Status is still pointing to my internal Front End FQDN: https://internal.domain.com:443/abs/handler.
For machines that are joined to the domain, the address books synchronizes with no issues. For machines that are not joined to the domain and for external users, GALContacts and GALContacts.DB files are not event generated for the users profiles.

Hi Anthony,
Please note the findings below:
1. I was checking the Lync Client configuration on one of the PC that is not joined to the domain, still on the domain network via site to site VPN connection. I noticed that the Connected Lync Server varies: sipinternal.domain.com, sipexternal.domain.com,
lync.domain.com (Pointing to the Edge Server IP).
2. Edge Server External Settings: Single IP address with the FQDN set to lync.domain.com for all 3 services and the following ports configured. Access Edge Service: 5061, Web Conferencing Edge Service: 444, A/V Edge Service: 443 with NAT enabled public
IPv4 address. I have checked the replication status between the Front End and Edge Server, it is up to date.
3. In regard to the https://lyncdiscover.domain.com, I don't have the lyncdiscover.domain.com published, but it is pointing to the NAT enabled public IPv4 address which is assigned for A/V Edge Services.
4. For the port forwarding, I am using the Cisco Meraki router.
Please advise if there are there is something that I am missing.
Thanks!

Company's Address Book for external contacts

Hi all,
I'm currently deploying a new Exchange 2013 in a company who had a different email system, so far.
One of the achievement would be to have an address book for external names (so, not in AD) shared within the company but managed only by a restrict number of people.
As example, list of vendors contact. The list should be available read only for everyone, but only the IT Infrastructure and few other people in the management should be able to add/remove/change the items.
Whato would be, in your opinion, the best solution to achieve that?
I was thinking using Public Folder. Create a sub-PF of contact objects and restrict permission accordingly. The only issue I can see, so far, is that seems not possible grant permission on a group basis to PF. Am I missing something here? It's the first
time I'm working with PF in several years :)
However, if there's a different solution you may advice, I'm all ears.
Any suggestion would be highly appreciated!
Thanks in advance to everyone.
Alessandro.

I was able to solve this myself.
Security groups has to be enabled on Exchange before being used to assign permission to PFs:
Enable-DistributionGroup -identity <SecurityGroup>
Add-PublicFolderClientPermission -User "<SecurityGroup>" -AccessRights
'<AccessLevel>'
Hope this helps someone.
A.

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

IPhone 3G iOS4: Sending mails from an external address

Hi!
Did anyone know if it is possible to send mails from an external address with the iPhone using MobileMe?
This was for me the most important feature Apple introduced with the last MobileMe update and it is working fine online and with Mail.app. But it seems not to work with the iPhone.
You can choose from your aliases when you write a mail but not the external address.
Is it not working with older iPhones or is it not working in general? In general would be a major drawback!
Regards, Stefan

You need to go to mail settings, open any account, then tap on SMTP. The gmail outgoing server is probably still in the server list, so delete it.
Also, you need to reboot after any email account changes. Hold HOME and SLEEP until an Apple logo appears.

Setting up MX Record for External email Access

To All,
I'm having trouble getting mail sent from external users to email accounts setup on my internally hosted server.
I have setup my server in a Standard Configuration using the following format for my FQDN:
server.mydomain.com (not real name)
I have checked both Primary Zone and Reverse Zone and both check fine.
I can send and receive email, while connected within my local domain, between users I have setup on my server using the format:
[email protected]
I can send email from inside the network to an outside email account, but cannot receive email from any users outside.
I have POP, IMAP, and SMTP ports (110, 143, and 25, respectively) all forwarded to my server thru my AEBS.
Consulting the setup guides, I have found these references to editing the MX record to allow for external email access using the [email protected] format:
+"If you don’t want to use your server’s fully qualified DNS name for users’ email addresses, the+
+DNS service must also include an MX record for your server. For example, if your server’s DNS+
+name is myserver.example.com and you want to have email addresses like [email protected],+
+the DNS service needs an MX record for your server."+....from the Installation and Setup Worksheet, page 15.
also
+"If you want users to be able to send and receive mail over the Internet, make sure DNS+
+service is set up with the appropriate MX records for Mail service:+
+A. If you have an ISP that provides DNS service to your network, contact the ISP and+
+have the ISP set up MX records for you. Your ISP needs to know your mail server’s+
+DNS name (such as mail.example.com) and your server’s IP address."+...from the Mail Service Admin page 22.
My question is...how does the MX record need to be set up?
Like this?
10 @ mydomain.com
Thanks for your help,
Steve

Camelot,
Thanks for replying.
1) What format do you want your users' email address in? (e.g. [email protected], >[email protected], [email protected], etc.)
I want my users to have a [email protected] email address.
I set up an A record as you suggested:
mail.mydomain.com A 1.2.3.4
My MX record was setup:
mydomain.com 10 mail.mydomain.com
However, I am still getting returned email from outside users. They are getting the following error:
+This is an automatically generated Delivery Status Notification+
+Delivery to the following recipient failed permanently:+
[email protected]
+Technical details of permanent failure:+
+Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 554 554 5.7.1 <[email protected]>: Relay access denied (state 14).+
Checking the Server Logs for IMAP I am getting these errors:
+Jan 21 12:11:34 server imap[44121]: AOD: user opts: get attributes for user: user failed with error: -14479+
+Jan 21 12:25:18 server imap[44236]: AOD: user opts: get attributes for user: user failed with error: -14479+
+Jan 21 12:31:46 server imap[44473]: AOD: user opts: get attributes for user: user failed with error: -14479+
+Jan 21 12:32:49 server imap[44499]: AOD: crypt authentication error: authentication failed for user: username (-14090)+
+Jan 21 12:37:06 server imap[44598]: AOD: user opts: get attributes for user: user failed with error: -14479+
+Jan 21 12:49:39 server imap[44520]: AOD: user opts: get attributes for user: user failed with error: -14479+
+Jan 21 13:01:51 server imap[45049]: AOD: user opts: get attributes for user: user failed with error: -14479+
+Jan 21 13:11:58 server imap[385]: AOD: user opts: get attributes for user: user failed with error: -14479+
When I try and use an online MX Record checker to check the MX record, it says the mail.mydomain.com record is invalid.
It's not until I change my MX record back to:
+@ 10 mydomain.com+
will the MX record show valid.
Network Utility scans show the following with the MX record set to @ 10 mydomain.com:
++; <<>> DiG 9.4.2-P2 <<>> mydomain.com mx +multiline +nocomments +nocmd +noquestion +nostats search+
++;; global options: printcmd++
++wekrugs.com. 3600 IN SOA server.mydomain.com. admin.mydomain.com. (++
++ 2009011900 ; serial++
++ 86400 ; refresh (1 day)++
++ 3600 ; retry (1 hour)++
++ 604800 ; expire (1 week)++
++ 3600 ; minimum (1 hour)++
++ )++
If I have it set up the way you suggested, the Network Utility and MX Checker reports that the NameServers don't respond to the entered MX record name.
Thanks again for your help,
Steve

DNS pointing to both internal and external addresses

I am currently going through the very helpful lynda.com OS X Server 10.5 videos to set up an Advanced Server from the ground up.
DNS was set up first and for the most part everything has gone for me just like Sean shows in the movies.
Our company's domain name is automaticduck.com so I have been setting up DNS records for our internal network to some of the machines, for example the Xserve I'm configuring is called duckxserve.automaticduck.com and it points to the proper internal IP address. I set up my MacBook Pro OS X Client system to use the new DNS server on duckxserve and while it works for getting around the internal network now I'm having problems connecting to outside addresses on our domain such as www.automaticduck.com and support.automaticduck.com. If I remove the internal Xserve from my client's DNS servers list I am able to get out again.
I thought I would be smart and add A NAME records to my internal DNS server with the external IP addresses, however this didn't change anything, I still couldn't get out to them.
We are NOT hosting our own web site and email etc., we have DNS set up through our web host with A NAME, C NAME and MX records for various servers that are exposed to the outside world.
My intention based on my understanding was that with the setup of this internal Xserve running DNS it would simply serve DNS records to the internal network. How can my set up my internal DNS to it does not conflict with my ability to get out to our outside public addresses?
Message was edited by: Wes Plate

Antonio Rocco wrote:
Add your ISP DNS Addresses to the forwarders section and that should be it.
Thank you for the reply, Tony.
If I set up the forwarders section* can I just not include information about our automaticduck.com servers that are not on our internal network? It seems to me (not that I know anything about this) that if our internal DNS server does not know about www.automaticduck.com or support.automaticduck.com then requests for those addresses should get passed on to our ISP's name servers*, right?
*68.238.128.12, 68.238.64.12
This doesn't work like I thought it would.
I have my client set up to use my new internal DNS server's IP address for a DNS server and I am able to get to the local machines defined therein (like http://wesworkg5/ ), however I cannot get to my outside sites... www.automaticduck.com or support.automaticduck.com (I can't even get to discussions.apple.com for some reason).
I can get to other outside sites that I've never been to before (so I know they have to get looked up), like whitehouse.gov or harvard.edu or almondjoy.com
The DNS log doesn't show me anything, maybe it isn't supposed to in a case like this.
Whatcha think? Thank you so much.

Configure a sharepoint 2013 site for external and internal access

I need to configure a local install of sharepoint 2013 so that users can access it internally and externally using windows/AD authentication. The internal and external addresses are different.
I have bound an external ip to the domain for external access.
I have created Alternate Access mapping, and bound the host header but I get a file not found message for external access.
Have I missed something here? why the error and how can it be fixed. Step by step process would be appreciated.

Hi Luis,
According to your description, my understanding is that the error occurred when accessing the site externally.
The most common cause for this is that the IIS host header is configured incorrectly. The 404 will appear because we are hitting a different IIS web site and not the one we are intended to.
Here is a similar issue for you to take a look:
http://stackoverflow.com/questions/14953322/sharepoint-2013-404-not-found-while-accessing-site-collection-from-outside
More references:
http://technet.microsoft.com/en-us/library/cc261814(v=office.15).aspx
http://technet.microsoft.com/en-us/library/cc263208(v=office.15).aspx
Best regards.
Thanks
Victoria Xia
TechNet Community Support

Lyncdiscover reports HTTP 500 Internal Server Error for external users

Hello,
I have a problem providing lyncdiscover information for external Lync users. The same address works internal (prompts for file download) so I believe the problem is UAG/TMG providing the site which is not my cup of tea. I have a working external lyncdiscover
for other domain in the same Lync + UAG/TMG server environment. I have also checked the public DNS records few times and everything should be fine. Firewall also shouldn't be an issue since it reports the internal server error, right? Any suggestions what
should I check?

more information based on Lync Autodiscover Web Service Remote Connectivity Test.
Testing HTTP authentication methods for URL https://lyncdiscover.domain1.com/Autodiscover/AutodiscoverService.svc/root/user.
HTTP authentication methods successful.
Additional Details
Testing HTTP content for URL https://lyncdiscover.domain1.comi/?sipuri=[email protected] has
token="User".
HTTP content isn't verified.
<label for="testSelectWizard_ctl12_ctl06_ctl00_ctl04_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
HTTP 200 status received from server, but no token="User".
Elapsed Time: 203 ms.
The same result goes for the other domain that provides the lyncdiscover information correctly for external users. It doesn't seem to solve the root cause but might help to understand
the problem.

Limit PO :Combination of GR/IR is not allowed for external services

Hi,
we are working in SRM40 sp09 & back end ECC.50
In the Limit PO:
we are able to create Limit PO from a shopping cart.The follow on documents in ECC, it is creating a PO with Item category "B" and the "invoices" are only possible.
The Issue:
The Client wants the Confirmation/GR functionality to be enabled and the Invoices.
but for Limit PO, with follow on documents--"Confirmation" is checked, we have a error messagecombination of GR/IR is not allowed for external services".
Is there any addition configuration or steps involved.
Thanks and Regards,
RK.

Hi
<b>Please go through the links below, which address the same issue -></b>
Limit PO(Item category D instead of B)
SRM: Item category B/D for limit PO
Re: Problem with Unknown account assignment with limit order...reply soon...
Do let me know.
Regards
- Atul

The operation can't be completed because the original item for "EXTERNAL" can't be found.

After upgrading to Mountain Lion I can no longer access my exFat formatted USB drive that is connected to my iMac from my MBP. I can connect to the iMac, but when I try to mount the USB drive I get an error message saying "The operation can't be completed because the original item for "EXTERNAL" can't be found."
I have enabled only 'SMB' in sharing preference on all of my machines, and all are running Mountain Lion.
*I have since tried connecting directly with the IP address, same result, and also reformatting the USB drive to just FAT32, same issue. I need the drive formatted in a windows format so my home theatre system can connect to it.
Message was edited by: davea3323

Update, So I disassembled the external hard drive case and pulled the bare drive out and connected the drive directly to my motherboard and without change any settings on the PC, the MacBook can now access it over the network. What is it about externals that the Mac can't access them over networks?

Port forwarding for external access to VNC server on multiple machines

I will have 10 PCs connected to the WRT54GL wireless AP. I am testing with 1. It has a static addresses 10.155.22.51. It is running a VNC server at port 5951.
If I set my VNC client up to access 10.155.22.51:5951 it works through the WRT54GL wireless AP.
I set the WRT54GL port forwarding to 5951 - 5951, set the IP address to 10.155.22.51 and enable. The external address of the AP is 10.155.0.29 on the company LAN.
So I set the VNC client to access the AP address with the VNC port, i.e. 10.155.0.29:5951. I expect the AP to change the address to 10.155.22.51:5951. This does not work.
Note: the problem could be that the AP is going through NATting because I can also access it at 10.155.22.9 along with all the other PCs on that LAN, i.e. I can access the LAN directly from elsewhere on the company net.

You can try changing the IP of the AP manually ... connect it to the Computer ..... access the setup page using http://192.168.1.245 .... use password as admin ....
Configure the IP settings first ...
Again login with new IP address .... configure wireless settings .....
Power down the AP & then the router ....
Wait for few minutes .... then power on the router ...first then the AP ...

SMTP for external address

Similar Messages

Maybe you are looking for