Mail server parameters in MDIS.ini
Hi Guru's,
To get mails through workflow..Can anybody tell me where in MDIS .Ini file do i maintain Mail server parameters...?
I mean do i need to put
Mail server parmeter:-................
OR
Just key in Mail server parameters any where in mdis.ini file...
Regards
Vikrant M Kelkar
Hi Vikrant,
As far as I know,the Mdis.ini file is the system configuration file that determines the settings to be done for enabling automatic Importing the parameters to be set in the mdis are:
[Global]
Version
Server
Interval
Verbose1
Log Dir
SLD Registration
[Repository_Name]
Chunk Size2
No. Of Chunks Processed In Parallel1
Login
Password
PasswordE
Log Protocol Transactions
Inter-Chunk Delay MS3
There is no option to set the mail server details here.
However in the Mds.ini file we have:
Mail server:
Mail SMTP time out:
These parameters will enable the mail settings for sending mail through MDM.
I may be wrong, but this is what the sap guide talks about and also the blog speaks about the settings required in the mds.ini file
If theres somthing different you've done, we can discuss it futher
Hope It Helped
Thanks & Regards
Simona Pinto
Similar Messages
-
MDIS.ini : no repository entries
Dear All
The MDM server is running on UNIX. MDIS is on the same server as MDS.
When i checked the MDIS.ini there are no repsoitory entries in it.(I have 3 repos with remote systems and ports configured)
Initially the server name was mentioned incorrectly in the MDIS.ini. I changed it (<sever name>:59750) and restarted the MDIS.
Shouldnt the repository entries appear automatically in MDIS.ini when the repositories are created?
Files are not getting picked up from the Reday folder. Port is in status "Has data".
But there is no files in the Status, log or exception folders.
However the log files in MDIS is having the error:
Connection to MDS server failed with error: The function ID returned did not match the expected function ID
What am i missing?
Regards
DeepikaHi SwarnaDeepika,
Yes parameters should appear automatically after restart.
Please recheck the passwords of MDIS from console level.
There is a good blog by Shambhunath here,this should be of help to you
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0391579-0654-2c10-89b6-ae6e96aa7d99?quicklink=index&overridelayout=true
Thanks,
Ravi
Edited by: Ravi Verma on Aug 30, 2011 11:56 AM -
Hi Friends,
I am looking for the mdis.ini and importmanagerbatch.exe files.I couldnt trace those files. I want to run the batch job.
Please guide me
regards
ShankarHi Shankar,
To run batch job you will have to first install the batch clients (ImportmanagerBatch and SyndicatorBatch). Download these file and install them onto your machine.
Once you install Importmanager Batch , it will create following directory structure:
C:\Program Files\SAP MDM 5.5\Importmanger Batch\ImportmanagerBatch.exe
Now you will have to configure the "mdis.ini" file as in you need to populate few of the parameters. e.g. Map Name . Server Name (IP / Host name),Repository Name , Port number.
You are now ready to run the batch job. Just create a batch file and type in ImportmanagerBatch command and execute it.
Regards,
Amol. -
Need to have mail1 play nice with upstream mail server....
Switched to new mail server and hitting a problem. We have a debian linux box doing SPAM filtering further upstream from the mail server and then sending down to the new leopard mail1 box.
On the debian box we're seeing:
2009-04-03 09:14:08 H=216-174-222-148.atgi.net (email.wdcsc.org) [216.174.222.148] F=<[email protected]> temporarily rejected RCPT <[email protected]>: remote host address is the local host
2009-04-03 09:14:08 1Lpfar-0004fh-Ku ** [email protected] R=dnslookup T=remote_smtp: SMTP error from remote mail server after RCPT TO:<[email protected]>: host nescosrv.nesco.ee [194.204.28.195]: 550 5.1.1 <[email protected]>: Recipient address rejected: User unknown in local recipient table
And mail isn't piping thru to the mail1 box. Here's the main.cf
sh-3.2# cat main.cf
# Global Postfix configuration file. This file lists only a subset
# of all parameters. For the syntax, and for a complete parameter
# list, see the postconf(5) manual page (command: "man 5 postconf").
# For common configuration examples, see BASIC_CONFIGURATION_README
# and STANDARD_CONFIGURATION_README. To find these documents, use
# the command "postconf html_directory readme_directory", or go to
# http://www.postfix.org/.
# For best results, change no more than 2-3 parameters at a time,
# and test if Postfix still works after every change.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
#soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /private/var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = _postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
# Note: you need to stop/start Postfix when this parameter changes.
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4
# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain.
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see VIRTUAL_README).
# Do not specify the names of domains that this machine is backup MX
# host for. Specify those names via the relay_domains settings for
# the SMTP server, or use permit_mx_backup if you are lazy (see
# STANDARD_CONFIGURATION_README).
# The local machine is always the final destination for mail addressed
# to user@[the.net.work.address] of an interface that the mail system
# receives mail on (see the inet_interfaces parameter).
# Specify a list of host or domain names, /file/name or type:table
# patterns, separated by commas and/or whitespace. A /file/name
# pattern is replaced by its contents; a type:table is matched when
# a name matches a lookup key (the right-hand side is ignored).
# Continue long lines by starting the next line with whitespace.
# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
#mydestination = $myhostname, localhost.$mydomain, localhost
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
mydestination = $myhostname,localhost.$mydomain,localhost,mail1.stanwood.wednet.edu,stanwood.we dnet.edu
# mail.$mydomain, www.$mydomain, ftp.$mydomain
# REJECTING MAIL FOR UNKNOWN LOCAL USERS
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination, $inet_interfaces or $proxy_interfaces.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown local users. This parameter is defined by default.
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery. You need to update the
# local_recipient_maps setting if:
# - You define $mydestination domain recipients in files other than
# /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
# For example, you define $mydestination domain recipients in
# the $virtual_mailbox_maps files.
# - You redefine the local delivery agent in master.cf.
# - You redefine the "local_transport" setting in main.cf.
# - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
# feature of the Postfix local delivery agent (see local(8)).
# Details are described in the LOCAL_RECIPIENT_README file.
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify a bare username, an @domain.tld
# wild-card, or specify a [email protected] address.
#local_recipient_maps = unix:passwd.byname $alias_maps
local_recipient_maps = proxy:unix:passwd.byname $alias_maps
#local_recipient_maps =
# The unknown_local_recipient_reject_code specifies the SMTP server
# response code when a recipient domain matches $mydestination or
# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
# and the recipient address or address local-part is not found.
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# local_recipient_maps settings are OK.
unknown_local_recipient_reject_code = 550
# TRUST AND RELAY CONTROL
# The mynetworks parameter specifies the list of "trusted" SMTP
# clients that have more privileges than "strangers".
# In particular, "trusted" SMTP clients are allowed to relay mail
# through Postfix. See the smtpd_recipient_restrictions parameter
# in postconf(5).
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this does works correctly only with interfaces specified
# with the "ifconfig" command.
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network. Instead, specify an explicit
# mynetworks list by hand, as described below.
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
#mynetworks_style = class
#mynetworks_style = subnet
#mynetworks_style = host
# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
# Specify an explicit list of network/netmask patterns, where the
# mask specifies the number of bits in the network part of a host
# address.
# You can also specify the absolute pathname of a pattern file instead
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side is not used).
#mynetworks = 168.100.189.0/28, 127.0.0.0/8
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table
# The relay_domains parameter restricts what destinations this system will
# relay mail to. See the smtpd_recipient_restrictions description in
# postconf(5) for detailed information.
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
# subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces or $proxy_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace. Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction description in postconf(5).
#relay_domains = $mydestination
# INTERNET OR INTRANET
# The relayhost parameter specifies the default host to send mail to
# when no entry is matched in the optional transport(5) table. When
# no relayhost is given, mail is routed directly to the destination.
# On an intranet, specify the organizational domain name. If your
# internal DNS uses no MX records, specify the name of the intranet
# gateway host instead.
# In the case of SMTP, specify a domain, host, host:port, [host]:port,
# [address] or [address]:port; the form [host] turns off MX lookups.
# If you're connected via UUCP, see also the default_transport parameter.
#relayhost = $mydomain
#relayhost = [gateway.my.domain]
#relayhost = [mailserver.isp.tld]
#relayhost = uucphost
#relayhost = [an.ip.add.ress]
# REJECTING UNKNOWN RELAY USERS
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a [email protected] address.
#relay_recipient_maps = hash:/etc/postfix/relay_recipients
# INPUT RATE CONTROL
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 100 SMTP server process
# limit, this limits the mail inflow to 100 messages a second more
# than the number of messages delivered per second.
# Specify 0 to disable the feature. Valid delays are 0..10.
#in_flow_delay = 1s
# ADDRESS REWRITING
# The ADDRESS_REWRITING_README document gives information about
# address masquerading or other forms of address rewriting including
# username->Firstname.Lastname mapping.
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
# The VIRTUAL_README document gives information about the many forms
# of domain hosting that Postfix supports.
# "USER HAS MOVED" BOUNCE MESSAGES
# See the discussion in the ADDRESS_REWRITING_README document.
# TRANSPORT MAP
# See the discussion in the ADDRESS_REWRITING_README document.
# ALIAS DATABASE
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
# It will take a minute or so before changes become visible. Use
# "postfix reload" to eliminate the delay.
#alias_maps = dbm:/etc/aliases
#alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases
# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi". This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
#alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
# ADDRESS EXTENSIONS (e.g., user+foo)
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5) 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,
# unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned
# as undeliverable.
# The following expansions are done on luser_relay: $user (recipient
# username), $shell (recipient shell), $home (recipient home directory),
# $recipient (full recipient address), $extension (recipient address
# extension), $domain (recipient domain), $local (entire recipient
# localpart), $recipient_delimiter. Specify ${name?value} or
# ${name:value} to expand value only when $name does (does not) exist.
# luser_relay works only for the default Postfix local delivery agent.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must specify "local_recipient_maps =" (i.e. empty) in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#luser_relay = [email protected]
#luser_relay = [email protected]
#luser_relay = admin+$local
# JUNK MAIL CONTROLS
# The controls listed here are only a very small subset. The file
# SMTPD_ACCESS_README provides an overview.
# The header_checks parameter specifies an optional table with patterns
# that each logical message header is matched against, including
# headers that span multiple physical lines.
# By default, these patterns also apply to MIME headers and to the
# headers of attached messages. With older Postfix versions, MIME and
# attached message headers were treated as body text.
# For details, see "man header_checks".
#header_checks = regexp:/etc/postfix/header_checks
# FAST ETRN SERVICE
# Postfix maintains per-destination logfiles with information about
# deferred mail, so that mail can be flushed quickly with the SMTP
# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
# See the ETRN_README document for a detailed description.
# The fast_flush_domains parameter controls what destinations are
# eligible for this service. By default, they are all domains that
# this server is willing to relay mail to.
#fast_flush_domains = $relay_domains
# SHOW SOFTWARE VERSION OR NOT
# The smtpd_banner parameter specifies the text that follows the 220
# code in the SMTP server's greeting banner. Some people like to see
# the mail version advertised. By default, Postfix shows no version.
# You MUST specify $myhostname at the start of the text. That is an
# RFC requirement. Postfix itself does not care.
#smtpd_banner = $myhostname ESMTP $mail_name
#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
# PARALLEL DELIVERY TO THE SAME DESTINATION
# How many parallel deliveries to the same user or domain? With local
# delivery, it does not make sense to do massively parallel delivery
# to the same user, because mailbox updates must happen sequentially,
# and expensive pipelines in .forward files can cause disasters when
# too many are run at the same time. With SMTP deliveries, 10
# simultaneous connections to the same domain could be sufficient to
# raise eyebrows.
# Each message delivery transport has its XXX_destination_concurrency_limit
# parameter. The default is $default_destination_concurrency_limit for
# most delivery transports. For the local delivery agent the default is 2.
#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 20
# DEBUGGING CONTROL
# The debug_peer_level parameter specifies the increment in verbose
# logging level when an SMTP client or server host name or address
# matches a pattern in the debug_peer_list parameter.
debug_peer_level = 2
# The debug_peer_list parameter specifies an optional list of domain
# or network patterns, /file/name patterns or type:name tables. When
# an SMTP client or server host name or address matches a pattern,
# increase the verbose logging level by the amount specified in the
# debug_peer_level parameter.
#debug_peer_list = 127.0.0.1
#debug_peer_list = some.domain
# The debugger_command specifies the external command that is executed
# when a Postfix daemon program is run with the -D option.
# Use "command .. & sleep 5" so that the debugger can attach before
# the process marches on. If you use an X-based debugger, be sure to
# set up your XAUTHORITY environment variable before starting Postfix.
debugger_command =
PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
xxgdb $daemon_directory/$process_name $process_id & sleep 5
# If you can't use X, use this to capture the call stack when a
# daemon crashes. The result is in a file in the configuration
# directory, and is named after the process name and the process ID.
# debugger_command =
# PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
# echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
# >$config_directory/$process_name.$process_id.log & sleep 5
# Another possibility is to run gdb under a detached screen session.
# To attach to the screen sesssion, su root and run "screen -r
# <id_string>" where <id_string> uniquely matches one of the detached
# sessions (from "screen -list").
# debugger_command =
# PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
# -dmS $process_name gdb $daemon_directory/$process_name
# $process_id & sleep 1
# INSTALL-TIME CONFIGURATION INFORMATION
# The following parameters are used when installing a new Postfix version.
# sendmail_path: The full pathname of the Postfix sendmail command.
# This is the Sendmail-compatible mail posting interface.
sendmail_path = /usr/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
# html_directory: The location of the Postfix HTML documentation.
html_directory = no
# manpage_directory: The location of the Postfix on-line manual pages.
manpage_directory = /usr/share/man
# sample_directory: The location of the Postfix sample configuration files.
# This parameter is obsolete as of Postfix 2.1.
sample_directory = /usr/share/doc/postfix/examples
# readme_directory: The location of the Postfix README files.
readme_directory = /usr/share/doc/postfix
mydomain_fallback = localhost
message_size_limit = 52428800
myhostname = mail1.stanwood.wednet.edu
mailbox_transport = cyrus
mydomain = stanwood.wednet.edu
mailbox_size_limit = 0
enable_server_options = yes
inet_interfaces = all
mynetworks = 127.0.0.0/8,172.16.0.0/17,169.204.240.0/25,172.29.1.22,169.204.240.2
smtpd_use_tls = yes
smtpd_enforce_tls = no
smtpd_tls_cert_file = /etc/certificates/mail1.stanwood.wednet.edu.crt
smtpd_tls_key_file = /etc/certificates/mail1.stanwood.wednet.edu.key
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 = gssapi,cram-md5,login,plain
content_filter = smtp-amavis:[127.0.0.1]:10024
mydestination = $myhostname,localhost.$mydomain,localhost,mail1.stanwood.wednet.edu,stanwood.we dnet.edu
owner_request_special = no
recipient_delimiter = +
alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
# 02/02/09 Server Checkup by Alex
bounce_queue_lifetime = 6h
delay_warning_time = 6h
maximal_queue_lifetime = 2d
# Topicdesk Frontline Defense
disable_vrfy_command = yes
smtpd_client_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_rbl_client zen.spamhaus.org, permit
smtpd_helo_required = yes
smtpd_helo_restrictions = permit_sasl_authenticated, permit_mynetworks, check_helo_access hash:/etc/postfix/helo_access, reject_non_fqdn_hostname,reject_invalid_hostname, permit
smtpd_sender_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_non_fqdn_sender, permit
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination,permit
smtpd_data_restrictions = permit_mynetworks, reject_unauth_pipelining, permit
virtual_transport = virtual
virtual_mailbox_domains =
sh-3.2#Right, what was happening is that it was a big loop. We had to modify our DNS and some other settings on the spam bucket... but... wondering if there's another solution...
mail1:~ admin$ postconf -n
alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
bouncequeuelifetime = 6h
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = smtp-amavis:[127.0.0.1]:10024
daemon_directory = /usr/libexec/postfix
debugpeerlevel = 2
delaywarningtime = 6h
disablevrfycommand = yes
enableserveroptions = yes
html_directory = no
inet_interfaces = all
localrecipientmaps = proxy:unix:passwd.byname $alias_maps
mail_owner = _postfix
mailboxsizelimit = 0
mailbox_transport = cyrus
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
maximalqueuelifetime = 2d
messagesizelimit = 52428800
mydestination = $myhostname,localhost.$mydomain,localhost,mail1.stanwood.wednet.edu,stanwood.we dnet.edu
mydomain = stanwood.wednet.edu
mydomain_fallback = localhost
myhostname = mail1.stanwood.wednet.edu
mynetworks = 127.0.0.0/8,172.16.0.0/17,169.204.240.0/25,172.29.1.22,169.204.240.2
newaliases_path = /usr/bin/newaliases
ownerrequestspecial = no
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
recipient_delimiter = +
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = _postdrop
smtpdclientrestrictions = permitsaslauthenticated, permit_mynetworks, rejectrblclient zen.spamhaus.org, permit
smtpddatarestrictions = permit_mynetworks, rejectunauthpipelining, permit
smtpdenforcetls = no
smtpdhelorequired = yes
smtpdhelorestrictions = permitsaslauthenticated, permit_mynetworks, checkheloaccess hash:/etc/postfix/helo_access, rejectnon_fqdn_hostname,reject_invalidhostname, permit
smtpdpw_server_securityoptions = gssapi,cram-md5,login,plain
smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
smtpdsasl_authenable = yes
smtpdsenderrestrictions = permitsaslauthenticated, permit_mynetworks, rejectnon_fqdnsender, permit
smtpdtls_certfile = /etc/certificates/mail1.stanwood.wednet.edu.crt
smtpdtls_keyfile = /etc/certificates/mail1.stanwood.wednet.edu.key
smtpduse_pwserver = yes
smtpdusetls = yes
unknownlocal_recipient_rejectcode = 550
virtualmailboxdomains =
virtual_transport = virtual
mail1:~ admin$ -
Mail server is too slow to deliver the mail to internal domain
Hi,
My mail server faster enough to send the mails to other domains, but when i try to send mail to my own domain it too slow some time it take 30 t0 40 minutes to deliver the mail.
Please help
Thanks,
Gulab PashaYou should use statspack to check what are the main waits.
Some indicators to check :
- too many fts/excessive IO => check sql statements (missing index, wrong where clause)
- explain plan for most important queries : using cbo or rbo ? If cbo, statistics should be up to date. If rbo, check acces path.
-excessive logfile switch (> 5 per hour) : increase logfile or disable logging
- undo waits => not enough rollback segments (if you don't set AUM)
- data waits => alter initrans, pctfree, pctused
- too many chaining rows => rebuild set of datas or rebuild table
- too many levels in indexes => rebuild index
- excessive parsing : use bind variable or alter parameter cursor_sharing
- too many sort on disks => increase sort_area_size and create others temporary tablespace on separate disks
- too many blocks reads for a row => db_block_size too few or too many chaining rows
- too many lru contention => increase latches
- OS swapping/paging ?
Too improve performance :
- alter and tune some parameters : optimizer_mode, sort_area_size, shared_pool_size, optimizer_index_cost_adj, db_file_multiblock_read_count...
- keep most useful packages in memory
- gather regularly statistics (if using cbo)
How do your users access to the db ?
Jean-François Léguillier
Consultant DBA -
Setting up yahoo mail server as the outgoing mail server
pls how do i set up the yahoo mail server as the outgoing(smtp) mail server for in the enterprise manager for email notfications?
i entered the following values
Outgoing(SMTP)mail server : smtp.mail.yahoo.com
Identify Sender as: Sysman
Sender's email address: [email protected]
After clicking the Test mailserver button, the test failed.
i got the following error message below
smtp.mail.yahoo.com: Test failed with message: "Sending failed; nested exception is: javax.mail.MessagingException: 530 authentication required - for help go to http://help.yahoo.com/help/us/mail/pop/pop-11.html
i have visited the link but i dont seem to get any meaningful help.
pls can anyone help me?user536860 wrote:
it should works, if you use the following parameters:
Smtp server: smtp.mail.yahoo.com:465
User Secure connection: SSL
I'll bet you it will NOT work & even give you 10 to 1 odds that it will fail.
Yahoo won't relay your spam; which is why your messages will be rejected.
What is the difference between your message & a message from a spammer? -
SAPCONNECT - RFC between SAP BW system and Mail Server
Hello Everybody,
Iam trying to enable <b>Information Broadcasting</b> feature in SAP BW System i.e; i want the queries to be send to users from BW system to their Email Ids for which i have made configurations for SMTP node in SICF and SCOT transactions.My problem is that do i need to create an RFC between BW system and Mail Server ,if yes iam not getting the way to do this and wt all parameters need to be set there .If somebody can plz guide me with the parameters that need to be set for SAPCONNECT or send me some good guide which details the creation of RFC ,I shall be highly obliged.Iam struggling with this issue since many days,You can send the guide to me on my email Id [email protected] .Your help shall be of gr8 support.Kindly revert at earliest.
regards,
SaumyaHi,
My understanding is -
you need to following setting to send mails-
http://help.sap.com/saphelp_nw04/helpdata/en/66/9c25413fabef23e10000000a155106/content.htm
Need this, if planning to use fax, SMs etc-
http://help.sap.com/saphelp_nw04/helpdata/en/2b/d925bf4b8a11d1894c0000e8323c4f/content.htm
hope it helps
regards
Vikash -
Where to configure the mail server of GRC access control 5.3?
We changes our SMTP server in SAP and we need to configure also the mail server in Virsa but i dont know how. Can someone help me how to change the SMTP server in VIRSA/SAP GRC.
Thank you and have a good day ahead.Hi topnnehj,
In GRC 5.3 the log reports for firefighter access are sent from the back-end system. So, if you´re using the firefighter module, after a mail server change you have to set the parameters in tx. SCOT acordingly. Also you have to change in CUP if you´re using CUP workflow notifications via e-mail.
Regards,
Diego. -
Upgrade from Lion Server to ML 10.8.1 Broke Mail server!
....10.8.1 OD seems to work, files and AFP available, but Mail server not working correctly. Now users don't see mail, postfix issues numerous errors about missing system_user_maps and delivers no mail? Must recover mails! Help! Where should I look, and what to read for Diagnosis ?
After upgrade in place from SL to Lion to ML. most services did not work correctly; except for Mail and DNS and OD. Reinstalled. Now most everything seems to work including Card Services, Calendars, Wiki, Web, DNS, OD. But Mail is off and missing??? No delivery of INcoming mail, No Sending Mail, no IMAP Mail login for users.
On Mail configuration in Server.App: Turned off All Filtering. Have rebooted Server several times, Restarted Mailserver from Server,app and Terninal. Same Results. Somewhere along the line from Server 10.5 to SL to Lion to 10.8 incoming Maill started going to [email protected] rather than simply [email protected].
Is it possible that virtual domains are fuzzing up the works? The error logs use the longer virtual domain (with the sevrer name prefix) rather than the domain name?
Here are some sample Log messages:
From SYStem Log:
Sep 7 19:33:56 plg1.plg-law.com postfix/cleanup[1998]: warning: 8273B199E3F8: recipient_canonical_maps map lookup problem for [email protected]
Sep 7 19:33:56 plg1.plg-law.com postfix/pickup[1324]: warning: maildrop/ECF3A196A4FE: error writing 8273B199E3F8: queue file write error
Sep 7 19:33:58 plg1.plg-law.com postfix/pickup[1324]: warning: E5AC9199E3F9: message has been queued for 1 days
Sep 7 19:33:58 plg1.plg-law.com postfix/cleanup[1998]: warning: hash:/etc/postfix/system_user_maps is unavailable. open database /etc/postfix/system_user_maps.db: No such file or directory
Sep 7 19:33:58 plg1.plg-law.com postfix/cleanup[1998]: warning: hash:/etc/postfix/system_user_maps lookup error for "[email protected]"
Sep 7 19:33:58 plg1.plg-law.com postfix/cleanup[1998]: warning: E5AC9199E3F9: recipient_canonical_maps map lookup problem for [email protected]
Sep 7 19:33:58 plg1.plg-law.com postfix/pickup[1324]: warning: maildrop/ED4AB196A4FF: error writing E5AC9199E3F9: queue file write error
Sep 7 19:33:59 plg1.plg-law.com postfix/cleanup[1998]: warning: hash:/etc/postfix/system_user_maps is unavailable. open database /etc/postfix/system_user_maps.db: No such file or directory
Sep 7 19:33:59 plg1.plg-law.com postfix/cleanup[1998]: warning: hash:/etc/postfix/system_user_maps lookup error for "[email protected]"
Sep 7 19:33:59 plg1.plg-law.com postfix/cleanup[1998]: warning: 385DD199E3FB: recipient_canonical_maps map lookup problem for [email protected]
Sep 7 19:33:59 plg1.plg-law.com postfix/pickup[1324]: warning: maildrop/EE2A9199B211: error writing 385DD199E3FB: queue file write error
From SMTP Log:
Sep 7 19:35:24 plg1.plg-law.com postfix/pickup[1324]: 3652E199E487: uid=78 from=<_mailman>
Sep 7 19:35:24 plg1.plg-law.com postfix/cleanup[1998]: warning: hash:/etc/postfix/system_user_maps is unavailable. open database /etc/postfix/system_user_maps.db: No such file or directory
Sep 7 19:35:24 plg1.plg-law.com postfix/cleanup[1998]: warning: hash:/etc/postfix/system_user_maps lookup error for "[email protected]"
Sep 7 19:35:24 plg1.plg-law.com postfix/cleanup[1998]: warning: 3652E199E487: recipient_canonical_maps map lookup problem for [email protected]
Sep 7 19:35:24 plg1.plg-law.com postfix/pickup[1324]: warning: maildrop/8E82B199AD06: error writing 3652E199E487: queue file write errorhere's my configured postfix main.cf file from /etc/postfix/main.cf (mountain lion server 10.8.1)
Server.app should have somewhat configured it correctly for you in someways, but something got messed up in the import script I guess.
Hope this helps...
# Global Postfix configuration file. This file lists only a subset
# of all parameters. For the syntax, and for a complete parameter
# list, see the postconf(5) manual page (command: "man 5 postconf").
# For common configuration examples, see BASIC_CONFIGURATION_README
# and STANDARD_CONFIGURATION_README. To find these documents, use
# the command "postconf html_directory readme_directory", or go to
# http://www.postfix.org/.
# For best results, change no more than 2-3 parameters at a time,
# and test if Postfix still works after every change.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
#soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /Library/Server/Mail/Data/spool
# 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
# The data_directory parameter specifies the location of Postfix-writable
# data files (caches, random numbers). This directory must be owned
# by the mail_owner account (see below).
data_directory = /Library/Server/Mail/Data/mta
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = _postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
# Note: you need to stop/start Postfix when this parameter changes.
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4
# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain.
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see VIRTUAL_README).
# Do not specify the names of domains that this machine is backup MX
# host for. Specify those names via the relay_domains settings for
# the SMTP server, or use permit_mx_backup if you are lazy (see
# STANDARD_CONFIGURATION_README).
# The local machine is always the final destination for mail addressed
# to user@[the.net.work.address] of an interface that the mail system
# receives mail on (see the inet_interfaces parameter).
# Specify a list of host or domain names, /file/name or type:table
# patterns, separated by commas and/or whitespace. A /file/name
# pattern is replaced by its contents; a type:table is matched when
# a name matches a lookup key (the right-hand side is ignored).
# Continue long lines by starting the next line with whitespace.
# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
#mydestination = $myhostname, localhost.$mydomain, localhost
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain,
# mail.$mydomain, www.$mydomain, ftp.$mydomain
# REJECTING MAIL FOR UNKNOWN LOCAL USERS
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination, $inet_interfaces or $proxy_interfaces.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown local users. This parameter is defined by default.
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery. You need to update the
# local_recipient_maps setting if:
# - You define $mydestination domain recipients in files other than
# /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
# For example, you define $mydestination domain recipients in
# the $virtual_mailbox_maps files.
# - You redefine the local delivery agent in master.cf.
# - You redefine the "local_transport" setting in main.cf.
# - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
# feature of the Postfix local delivery agent (see local(8)).
# Details are described in the LOCAL_RECIPIENT_README file.
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify a bare username, an @domain.tld
# wild-card, or specify a [email protected] address.
#local_recipient_maps = unix:passwd.byname $alias_maps
#local_recipient_maps = proxy:unix:passwd.byname $alias_maps
#local_recipient_maps =
# The unknown_local_recipient_reject_code specifies the SMTP server
# response code when a recipient domain matches $mydestination or
# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
# and the recipient address or address local-part is not found.
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# local_recipient_maps settings are OK.
unknown_local_recipient_reject_code = 550
# TRUST AND RELAY CONTROL
# The mynetworks parameter specifies the list of "trusted" SMTP
# clients that have more privileges than "strangers".
# In particular, "trusted" SMTP clients are allowed to relay mail
# through Postfix. See the smtpd_recipient_restrictions parameter
# in postconf(5).
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this does works correctly only with interfaces specified
# with the "ifconfig" command.
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network. Instead, specify an explicit
# mynetworks list by hand, as described below.
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
#mynetworks_style = class
#mynetworks_style = subnet
#mynetworks_style = host
# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
# Specify an explicit list of network/netmask patterns, where the
# mask specifies the number of bits in the network part of a host
# address.
# You can also specify the absolute pathname of a pattern file instead
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side is not used).
#mynetworks = 168.100.189.0/28, 127.0.0.0/8
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table
# The relay_domains parameter restricts what destinations this system will
# relay mail to. See the smtpd_recipient_restrictions description in
# postconf(5) for detailed information.
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
# subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces or $proxy_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace. Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction description in postconf(5).
#relay_domains = $mydestination
# INTERNET OR INTRANET
# The relayhost parameter specifies the default host to send mail to
# when no entry is matched in the optional transport(5) table. When
# no relayhost is given, mail is routed directly to the destination.
# On an intranet, specify the organizational domain name. If your
# internal DNS uses no MX records, specify the name of the intranet
# gateway host instead.
# In the case of SMTP, specify a domain, host, host:port, [host]:port,
# [address] or [address]:port; the form [host] turns off MX lookups.
# If you're connected via UUCP, see also the default_transport parameter.
#relayhost = $mydomain
#relayhost = [gateway.my.domain]
#relayhost = [mailserver.isp.tld]
#relayhost = uucphost
#relayhost = [an.ip.add.ress]
# REJECTING UNKNOWN RELAY USERS
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a [email protected] address.
#relay_recipient_maps = hash:/etc/postfix/relay_recipients
# INPUT RATE CONTROL
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 100 SMTP server process
# limit, this limits the mail inflow to 100 messages a second more
# than the number of messages delivered per second.
# Specify 0 to disable the feature. Valid delays are 0..10.
#in_flow_delay = 1s
# ADDRESS REWRITING
# The ADDRESS_REWRITING_README document gives information about
# address masquerading or other forms of address rewriting including
# username->Firstname.Lastname mapping.
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
# The VIRTUAL_README document gives information about the many forms
# of domain hosting that Postfix supports.
# "USER HAS MOVED" BOUNCE MESSAGES
# See the discussion in the ADDRESS_REWRITING_README document.
# TRANSPORT MAP
# See the discussion in the ADDRESS_REWRITING_README document.
# ALIAS DATABASE
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
# It will take a minute or so before changes become visible. Use
# "postfix reload" to eliminate the delay.
#alias_maps = dbm:/etc/aliases
#alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases
# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi". This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
#alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
# ADDRESS EXTENSIONS (e.g., user+foo)
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5) 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,
# unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned
# as undeliverable.
# The following expansions are done on luser_relay: $user (recipient
# username), $shell (recipient shell), $home (recipient home directory),
# $recipient (full recipient address), $extension (recipient address
# extension), $domain (recipient domain), $local (entire recipient
# localpart), $recipient_delimiter. Specify ${name?value} or
# ${name:value} to expand value only when $name does (does not) exist.
# luser_relay works only for the default Postfix local delivery agent.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must specify "local_recipient_maps =" (i.e. empty) in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#luser_relay = [email protected]
#luser_relay = [email protected]
#luser_relay = admin+$local
# JUNK MAIL CONTROLS
# The controls listed here are only a very small subset. The file
# SMTPD_ACCESS_README provides an overview.
# The header_checks parameter specifies an optional table with patterns
# that each logical message header is matched against, including
# headers that span multiple physical lines.
# By default, these patterns also apply to MIME headers and to the
# headers of attached messages. With older Postfix versions, MIME and
# attached message headers were treated as body text.
# For details, see "man header_checks".
#header_checks = regexp:/etc/postfix/header_checks
# FAST ETRN SERVICE
# Postfix maintains per-destination logfiles with information about
# deferred mail, so that mail can be flushed quickly with the SMTP
# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
# See the ETRN_README document for a detailed description.
# The fast_flush_domains parameter controls what destinations are
# eligible for this service. By default, they are all domains that
# this server is willing to relay mail to.
#fast_flush_domains = $relay_domains
# SHOW SOFTWARE VERSION OR NOT
# The smtpd_banner parameter specifies the text that follows the 220
# code in the SMTP server's greeting banner. Some people like to see
# the mail version advertised. By default, Postfix shows no version.
# You MUST specify $myhostname at the start of the text. That is an
# RFC requirement. Postfix itself does not care.
#smtpd_banner = $myhostname ESMTP $mail_name
#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
# PARALLEL DELIVERY TO THE SAME DESTINATION
# How many parallel deliveries to the same user or domain? With local
# delivery, it does not make sense to do massively parallel delivery
# to the same user, because mailbox updates must happen sequentially,
# and expensive pipelines in .forward files can cause disasters when
# too many are run at the same time. With SMTP deliveries, 10
# simultaneous connections to the same domain could be sufficient to
# raise eyebrows.
# Each message delivery transport has its XXX_destination_concurrency_limit
# parameter. The default is $default_destination_concurrency_limit for
# most delivery transports. For the local delivery agent the default is 2.
#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 20
# DEBUGGING CONTROL
# The debug_peer_level parameter specifies the increment in verbose
# logging level when an SMTP client or server host name or address
# matches a pattern in the debug_peer_list parameter.
debug_peer_level = 2
# The debug_peer_list parameter specifies an optional list of domain
# or network patterns, /file/name patterns or type:name tables. When
# an SMTP client or server host name or address matches a pattern,
# increase the verbose logging level by the amount specified in the
# debug_peer_level parameter.
#debug_peer_list = 127.0.0.1
#debug_peer_list = some.domain
# The debugger_command specifies the external command that is executed
# when a Postfix daemon program is run with the -D option.
# Use "command .. & sleep 5" so that the debugger can attach before
# the process marches on. If you use an X-based debugger, be sure to
# set up your XAUTHORITY environment variable before starting Postfix.
debugger_command =
PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
xxgdb $daemon_directory/$process_name $process_id & sleep 5
# If you can't use X, use this to capture the call stack when a
# daemon crashes. The result is in a file in the configuration
# directory, and is named after the process name and the process ID.
# debugger_command =
# PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
# echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
# >$config_directory/$process_name.$process_id.log & sleep 5
# Another possibility is to run gdb under a detached screen session.
# To attach to the screen sesssion, su root and run "screen -r
# <id_string>" where <id_string> uniquely matches one of the detached
# sessions (from "screen -list").
# debugger_command =
# PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
# -dmS $process_name gdb $daemon_directory/$process_name
# $process_id & sleep 1
# INSTALL-TIME CONFIGURATION INFORMATION
# The following parameters are used when installing a new Postfix version.
# sendmail_path: The full pathname of the Postfix sendmail command.
# This is the Sendmail-compatible mail posting interface.
sendmail_path = /usr/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
# html_directory: The location of the Postfix HTML documentation.
html_directory = /usr/share/doc/postfix/html
# manpage_directory: The location of the Postfix on-line manual pages.
manpage_directory = /usr/share/man
# sample_directory: The location of the Postfix sample configuration files.
# This parameter is obsolete as of Postfix 2.1.
sample_directory = /usr/share/doc/postfix/examples
# readme_directory: The location of the Postfix README files.
readme_directory = /usr/share/doc/postfix
#======================================================================
# dovecot
dovecot_destination_recipient_limit = 1
# default mailbox size limit set to no limit
mailbox_size_limit = 0
# List of ciphers or cipher types to exclude from the SMTP server cipher
# list at all TLS security levels.
smtpd_tls_exclude_ciphers = SSLv2, aNULL, ADH, eNULL
# Protect SSL/TLS encryption keys
tls_random_source = dev:/dev/urandom
# (APPLE) Credentials for using URLAUTH with IMAP servers.
imap_submit_cred_file = /Library/Server/Mail/Config/postfix/submit.cred
# (APPLE) The SACL cache caches the results of Mail Service ACL lookups.
# Tune these to make the cache more responsive to changes in the SACL.
# The cache is only in memory, so bouncing the sacl-cache service clears it.
use_sacl_cache = yes
# sacl_cache_positive_expire_time = 7d
# sacl_cache_negative_expire_time = 1d
# sacl_cache_disabled_expire_time = 1m
#======================================================================
mydomain_fallback = localhost
message_size_limit = 104857600
biff = no
mynetworks = 127.0.0.0/8,www.yourvirtaldomain.com
smtpd_client_restrictions = permit_mynetworks permit_sasl_authenticated reject_rbl_client zen.spamhaus.org permit
recipient_delimiter = +
smtpd_tls_ciphers = medium
inet_protocols = all
mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
recipient_canonical_maps = hash:/etc/postfix/system_user_maps
smtpd_use_pw_server = yes
smtpd_sasl_auth_enable = yes
content_filter = smtp-amavis:[127.0.0.1]:10024
inet_interfaces = loopback-only
smtpd_helo_required = yes
smtpd_pw_server_security_options = cram-md5,gssapi
header_checks = pcre:/etc/postfix/custom_header_checks
smtpd_tls_CAfile = /etc/certificates/computer.yourdomain.com.D800DD955D66179EEA4321DAA0617A19FFCD1 5C1.chain.pem
smtpd_helo_restrictions = reject_invalid_helo_hostname reject_non_fqdn_helo_hostname
relayhost =
smtpd_recipient_restrictions = permit_sasl_authenticated permit_mynetworks reject_unauth_destination check_policy_service unix:private/policy permit
smtpd_enforce_tls = no
smtpd_use_tls = yes
enable_server_options = yes
smtpd_tls_key_file = /etc/certificates/computer.yourdomain.com.D800DD955D66179EEA4321DAA0617A19FFCD1 5C1.key.pem
smtpd_tls_cert_file = /etc/certificates/computer.yourdomain.com.D800DD955D66179EEA4321DAA0617A19FFCD1 5C1.cert.pem
mydomain = yourdomain.com
virtual_alias_maps = $virtual_maps hash:/etc/postfix/virtual_users
virus_db_update_enabled = 1
mailbox_transport = dovecot
postscreen_dnsbl_sites = zen.spamhaus.org*2
maps_rbl_domains =
virtual_alias_domains = $virtual_alias_maps hash:/etc/postfix/virtual_domains
config_directory = /Library/Server/Mail/Config/postfix -
REP-50138: mail : Mail server is not available in eBiz R12 Advanced Distrib
Hi,
I am trying to get Reports Advanced Distribution working in eBiz 12.1.1 for custom reports but get concurrent job failures with the following messages in the job log:-
REP-57054: In-process job terminated:Executed successfully but there were some errors when distribute the output
REP-50159: Executed successfully but there were some errors when distribute the output
REP-50138: mail : Mail server is not available
The <distribution>.xml has 2 steps:-
1. create pdf report output in the file system [works correctly]
2. email the report as a pdf attachment [fails]
(The xml appears to validate)
I have configured the <rwservlet>.conf "mailServer" pluginparam;
I can telnet from apps host (Win2003) to mailserver host smtp port (Linux) from the appserver environment.
Is there something else I should have done or am I trying the impossible in the eBiz environment?
Regards,
MichaelThanks Hussein.
As I said originally, the apps host OS is Win2003. We know mail works from the database layer on this apps host but this is the first time we have tried from the appserver layer.
However, it is impractical in EBS to execute reports from the command line because of the complex cross-schema relationships, embedded profile_options and temporary data requirements setup by a calling form in this case.
Some of the rwrun command line options can be included in a concurrent job but many of the common ones cause job failures
e.g. Tracing and over-rides of the more common report 'system parameters'.
I have already covered the issues raised in the notes you mentioned in the pluginparam setting so I am wondering whether eBiz has some restrictions on Advanced Distribution. I am waiting on Metalink but they don't seem to have any interest in responding to my SR which basically just asks the question 'does eBiz support Advanced Distribution'.
I'll wait on their response and post the result when I know what's possible unless somebody else has a suggestion. -
Hello everyone,
We tried several combinasions in order to run the import server automatically but still it does not work. Can anybody tell us where we did a mistake?
In advance thanks,
Aklilu
Our mdis.ini
[SERVICE]
Server=seaman305
Interval=30
Automap unmapped value=True
Unmapped Value Handling=True
Always use unmapped Value Handling=1
[GLOBAL]
Server=seaman305
Interval=30
Automap unmapped value=True
Unmapped Value Handling=True
Always use unmapped Value Handling=1
String Resource Dir=C:\PROGRA1\SAPMDM1.5\IMPORT~2\LangStrings\
Log Dir=Logs
SLD Registration=False
Verbose=0x0000
VXR_MAX=25000
[Material_1seaman305MSQL_8_8_4_3]
Login=Admin
Password=
Chunk Size=50000
No. Of Chunks Proccessed In Parallel=5
[mdm_demoseaman305MSQL_19_8_4_3]
Login=Admin
Password=
Chunk Size=50000
No. Of Chunks Proccessed In Parallel=5
[Vendor_55310seaman305MSQL_12_4_4_3]
Login=Admin
Password=
Chunk Size=50000
No. Of Chunks Proccessed In Parallel=5Hi Aklilu,
just a copy & paste of my reply in the other thread
> We are trying to parameter the mdis.ini and until now it does not work.
Could you specify this? In addition, I've got a few hints:
MDIS has to have the same build version as the MDM Server. In addition, MDIS has to be running (in Windows, you can check this in the Services Screen). Furthermore you should have a look at the Console's port definition (select your repository, go to Admin -> Ports in the menu tree). The port has to be configured correctly (XML Scheme, which map to be used, and so on). Very important: you have to set the port to automatic processing.
Here's a sample for the MDIS.ini:
[GLOBAL]
Version=5540
Server=WDFD00146633A
Interval=30
Automap Unmapped Value=True
Unmapped Value Handling=Add
Always Use Unmapped Value Handling=False
VXR_MAX=25000
Verbose=0xFFFF
-- Verbose OFF: 0x0000
-- Verbose ON: 0xFFFF
-- FI Verbose: 0x0001
-- XML Verbose: 0x0002
-- MAP Verbose: 0x0004
-- THRD Verbose: 0x0008
-- PARSER Verbose: 0x0010
-- STRUCTX Verbose: 0x0020
-- VALUEX Verbose: 0x0040
-- IMPORTX Verbose: 0x0080
String Resource Dir=C:PROGRA~1SAPMDM~1.5IMPORT~2LangStrings
Log Dir=Logs
SLD Registration=False
[SP04_BUSINESS_PARTNERWDFD00143366AMSQL_21_13_4_3]
Login=Admin
Password=
Chunk Size=50000
No. Of Chunks Proccessed In Parallel=5
Using the Verbose parameter you can define which errors, issues, messages and so on should be written into the MDIS log. You can find the logs directly in the port's log folder and in the log folder of your MDIS installation directory. If MDIS is not working or the import fails, these files contain some helpful information.
Kind regards
Michael -
Incoming Mail Server Not Responding
Hi from a Mac Newbie...
I am trying to set up multiple email acounts to be accessed by Mail, and keep getting the "The POP server “mail.hotmail.com” is not responding. Check your network connection and that you entered the correct information in the “Incoming Mail Server” field. If it still doesn’t respond, the server might be temporarily unavailable". The same for just hotmail.com. Once I get this to work I need to set up gmail, too.
Am I typing something in wrong?
ThanksHas it worked before on the pad. If it has in the past, and does not now that means either the server is down or busy, just wait a while. or some how you have altered you name or password or some other server parameter inadvertently.
Third choice is you have dropped your Internet connection. Is anything else on the Internet working?
Try the same account from safari using web,ail, or from another computer. If it is down, it will be down there as well. If it works there, but not from the pad, recheck the parameters and your connection again. -
Incoming Mail Server Password Disappears
Suddenly I'm unable to receive mail.
I check the account settings.
Under "Incoming Mail Server", next to "password", I see "Required". Well, duh.
I re-enter the password and exit Settings. The password is still there.
I send myself a test mail. I wait about 3 minutes for the internets.
I start mail on the iPhone.
I receive the notification: "Cannot Get Mail > The connection to the server "mail.mydomainname.com" failed."
I return to mail settings and find my password has been erased.
I am able to retrieve the test mail from another computer with the same account setting.
Help is appreciated.
Don't know if this is part of the problem, but under "Mailboxes" I now only see "Inbox" and not "Sent" and "Trash". Also, I have no problem sending mail to the same mail server.I resolved this by:
A) doing a memory consolidation restart;
B) deleting the mail account;
C) doing a memory consolidation restart;
D) re-creating a mail account with exactly the same information as that deleted in B);
E) restarting the iPhone.
As the parameters in D match the parameters in B, this has to be a bug. -
Which mail server is used in a webapp?
Hi all,
I have a Webapp where the users can send an email
to me including the parameters of a form
( <form action="mailto:[email protected])....>
<input type="hidden" name="param1" value="xx"/>
Now depending on which mail client the user has on his machine the resulting email differs, sometimes the parameters as 1 attachment, sometimes xx attachments.
So I want to implement it with javamail-api.
MY question: I have to tell the API the name of the mailserver. How can I know what mail-server the user uses? Or are all these emails processed through my own mail-server?
Please help me to understand it. Thanks a lot in advance,
PeterHey ho.
You have to hardconde the mail servers in your code to point to the mail server you use (= your ISP's server) or host (= Your own mailserver). All the mails are then processed through that specified server. -
Hello,
I have checked to activate SMTP in Server Manager.
Ben when I want to add : enable inbound email, it takes a lot of time to save, the checkbox uncheckes itself, and in the system.log, I have this error :
May 27 20:45:13 tmachinix servermgrd[13357]: Exception in doCommand for module servermgr_mail: *** -[NSCFString appendString:]: nil argument
May 27 20:45:13 tmachinix servermgrd[13357]: --request was {\n command = writeSettings;\n configuration = {\n imap = {\n configdirectory = "";\n };\n postfix = {\n "enable_smtp_in" = 1;\n "virus_db_update_enabled" = 1;\n };\n };\n optionalArguments = {\n parameters = (\n "imap:configdirectory",\n "imap:enable_imap",\n "imap:enable_pop",\n "imap:enable_pop",\n "imap:enable_quota_warnings",\n "imap:enable_sieve",\n "imap:imap_auth_clear",\n "imap:imap_auth_cram_md5",\n "imap:imap_auth_gssapi",\n "imap:imap_auth_login",\n "imap:imap_auth_plain",\n "imap:log_level",\n "imap:lmtp_luser_relay",\n "imap:lmtp_luser_relay_enabled",\n "imap:lmtp_over_quota_perm_failure",\n "imap:max_imap_connections",\n "imap:notification_server_enabled",\n "imap:notification_server_address",\n "imap:notification_server_username",\n "imap:notification_server_password",\n "imap:notification_server_port",\n "imap:partitions",\n "imap:partition-default",\n "imap:pop_auth_apop",\n "imap:quotawarn",\n "imap:quota_custom_error",\n "imap:quota_custom_warning",\n "imap:quota_warn_frequency_days",\n "imap:servername",\n "imap:tls_server_options",\n "imap:tls_cert_file",\n "imap:tls_key_file",\n "imap:tls_ca_file",\n mailman,\n "postfix:always_bcc",\n "postfix:always_bcc_enabled",\n "postfix:auto_learn",\n "postfix:bayesian_enabled",\n "postfix:disable_vrfy_command",\n "postfix:enable_smtp",\n "postfix:enable_smtp_in",\n "postfix:enable_smtp_out",\n "postfix:enable_var_mail",\n "postfix:enable_virtual_domains",\n "postfix:full_reporting",\n "postfix:log_level",\n "postfix:log_rolling_days",\n "postfix:log_rolling_days_enabled",\n "postfix:luser_relay_enabled",\n "postfix:mailbox_transport",\n "postfix:black_hole_domains",\n "postfix:maps_rbl_domains_enabled",\n "postfix:message_size_limit",\n "postfix:message_size_limit_enabled",\n "postfix:msg_body_checks_enabled",\n "postfix:msg_header_checks_enabled",\n "postfix:mydestination",\n "postfix:mydomain",\n "postfix:myhostname",\n "postfix:mynetworks",\n "postfix:mynetworks_enabled",\n "postfix:mynetworks_style",\n "postfix:reject_invalid_host_enabled",\n "postfix:reject_unknown_host_enabled",\n "postfix:reject_non_FQDN_enabled",\n "postfix:reject_unknown_client_enabled",\n "postfix:reject_unauth_piplining_enabled",\n "postfix:relayhost",\n "postfix:relayhost_enabled",\n "postfix:smtp_sasl_auth_enable",\n "postfix:smtp_auth_relay_dict",\n "postfix:required_hits",\n "postfix:safe_reporting",\n "postfix:smtp_reject_list",\n "postfix:smtp_reject_list_enabled",\n "postfix:smtp_body_checks",\n "postfix:smtp_uce_controlls",\n "postfix:smtpd_pw_server_security_options",\n "postfix:spam_action",\n "postfix:spam_domain_name",\n "postfix:spam_log_level",\n "postfix:spam_notify_admin",\n "postfix:spam_notify_admin_email",\n "postfix:spam_ok_languages",\n "postfix:spam_ok_locales",\n "postfix:spam_quarantine",\n "postfix:spam_rewrite_subject",\n "postfix:spam_scan_enabled",\n "postfix:spam_subject_tag",\n "postfix:strict_rfc821_envelopes",\n "postfix:smtpd_helo_required",\n "postfix:text_only_attachments",\n "postfix:tls_server_options",\n "postfix:smtpd_tls_cert_file",\n "postfix:smtpd_tls_key_file",\n "postfix:smtpd_tls_CAfile",\n "postfix:virus_scan_enabled",\n "postfix:virus_action",\n "postfix:virus_scan_enabled",\n "postfix:virus_db_update_enabled",\n "postfix:virus_db_update_days",\n "postfix:virus_db_last_update",\n "postfix:virus_notify_admin",\n "postfix:virus_notify_admin_email",\n "postfix:virus_notify_recipients",\n "postfix:virus_notify_remote_recipients",\n "postfix:virus_quarantine",\n "postfix:virtual_domains",\n "postfix:group_expansion",\n nil\n );\n };\n}
(END)
And if I want to use the assistant to configure the email module, I get this error :
« NIL_RESPONSE_ERR (*** -[NSCFString appendString:]: nil argument) » during « writeSettings »
Please, help me.Hello arnobeck, I would start with the basics, can you receive emails?
Everything bellow refers to settings under the mail service.
Are your Domain and Host names set to what you want? - General tab
Make sure Kerberos or CRAM-MD5 are checked. - Advanced tab
Check you have certificates selected for both SMTP SSL: and IMAP and POP SSL:. - Advanced tab
Check the certificates match the domain name set in the General tab. - Advanced tab
P.S. I'm not the most advanced with mail server service, but hopefully I can help.
Regards,
Graham
Maybe you are looking for
-
Hi, My client requirement is to compare the price with following pricing elements before creating the PO we are not creating RFQ's here ,when we enter below values for each vendor, it should dispay the report as it shows in ME49 Basic Value Less disc
-
Help needed in writting Customer exit - ABAP Code
Hi Friends, I have a scenario in one of the query and need to write a customer exit for the same. Here is the scenario: I am using one input variable XXX to get input from user which feeds value to one of the charateristic lets say "CHAR1" in query.
-
Have you a simple client for send message on oc4j 9.0.2.0.0 ?
Hi to All! Have you a simple client to send message on a queue in OC4J 9.0.2 ? Can you show me how is possible to write the config file to connect to oc4j application server? thanks very much Andrea
-
Lacp port channel shows down on one 5k
I got one side of my lacp port channel down. the topology is shown but the left side is showing down 20 Po20(SD) Eth LACP Eth1/5(s) Eth1/6(s) # sh int port-channel 20 port-channel20 is down (No operational members) Hardware: Por
-
Hi Gurus, i have a simple questions to you (hopefully). At the moment i am working with SOAP AXIS Receiver Adapter because i need to add <wsse> Tags to my SOAP Header. (according to blog: /people/pravesh.puria/blog/2009/08/26/adding-usernametoken-tim