Disable e-mail for cloned environments

All,
We periodically clone our production database for development and testing purposes. When we do this, we'd like to stop (block or remove) any process that sends an e-mail out. Pre-APEX, this was easy enough; we used a custom PL/SQL procedure which checked v$database.name before actually sending anything. For any process we build that sends e-mails in APEX, we can certainly do something similar (attach a condition to the process).
But what about subscriptions to interactive reports? Is there any way that we can configure APEX to check the database name before sending out subscribed e-mails? Or do we need to somehow clear out subscriptions when cloning our database--and, if so, how do we do that?
Thanks,
-David

Finally got some time to do a bit more digging. I'd rather not disable all e-mails, as it's possible (likely, even) that we'll want e-mails available for testing. But the APEX_APPLICATION_PAGE_IR_SUB view in the data dictionary seems to drive off of the wwv_flow_worksheet_notify table. Seems like it should be possible to truncate that table upon cloning to wipe out any and all IR subscriptions. Anyone know if this will work, or of specific reasons we shouldn't do it?
Thanks,
-David

Similar Messages

OTM - supported methods for Cloning Transportation Management environments?

Does anyone know if there are currently any supported methods for cloning entire OTM environments?
OTM Admin Guide only mentions supported methods for Database-related objects, but nothing for Web or App tiers.
Oracle Support Note 549353.1 (over a year old) states:
You can not clone the OTM Software, you must run the full installer on your new instance.
You can, however, clone the database portion so that you can have the same data content. This is
documented in Note 1313815.1 Cloning Oracle Transportation Management Database Schemas.
Not sure the above still applies to current OTM release 6.3.1.
Thanks,
Paul S.

i'm very glad to read, from the article you referenced, that there's no performance hit. but that's only 1 of 2½ issues. i have some follow-up questions. perhaps we should take this to a forum instead of the knowledge base?
-what about prior issue #2 (securely wiping the drive)? is this easily and instantly doable? we'll ignore #3 (relying on microsoft gets ½ a point).
-with the encryption keys stored on the controller, doesn't using third-party encryption software mean the keys themselves aren't encrypted by a user pw, making it that much easier for someone with physical access to the drive to extract them from the firmware?
-if the controller is doing the encryption, why bother with bitlocker? is it so slightly-more-savvy-than-average joe can easily enable it, or so you don't have to write it into the firmware? (i'm being serious, not snarky--i'm a software developer myself.) personally, i'm dual-booting win7* and ubuntu 14, which means i need 2 separate encryption methods instead of just supplying my credentials at boot to decrypt the hd and then choosing which os to load.
-also, if i upgrade the windows os, ms requires the os volume to be decrypted first. this would obviously not be the case if windows was unaware that it was encrypted.
*last, what about those poor silly saps who are running win7 (or earlier)? i just read that win7 bitlocker doesn't support self-encrypting drives--it was an update as of win8. we're just out of luck? i realize you can't support everything, but win7 is still a ms-supported os, and it seems like a better service to (more of) your customers to enable full-disk encryption all the time.
thank you!

Disable Mail for Exchange error notification

Hi,
I am using Mail for exchange 2.0.7.000 (shown as 2.7 on download page and 2.0.7.000 on MFE about) on E90 (300.34.8427-08)
It is giving error per minute that Error Syncing Calendar.
sometime "Error syncing email".
This started after I installed 2.0.7 on E90. it also hangs my phone every 3-4 hour and I have to restart my mobile.
I want to suppress these messages, I dont care if it does not sync for some time. how can I disable these message.
It is very weird that it keeps waiting for my input and blocks my working on phone.
the only way I see is to turn the MFE to manual sync.
any help?

Is it really so that there's noone with sam problem? Has anyone heard about the same errorcode?

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

How can I disable e-mail and text messages when I'm close to or over my data quota ?

How can I disable e-mail and text messages when I'm close to or over my data quota ?
Is this possible? I don't see any options?
All I see is this:
Receive confirmations of many account transactions via Email and/or free Text Alerts delivered right to your cell phone. You can receive these confirmations for
   transactions done online, over the phone or from your handset. Account management Text Alerts do not count against any Messaging allowances.
      Your bill is ready for review.
     Payment Confirmations: Your payment has been received    Your credit/adjustment     has been applied.1
     Account Activity Confirmations     Plan changes     Feature changes1

What phone?
You would need to disable data on the phone itself. You wouldn't do it online on your account.
Note also that text messages do not count toward your data allowance.

[SOLVED] How to disable "No mail." message upon login?

This one's really stumping me. I disable the mail message a few months ago by creating a .hushlogin file in my home directory. That did the trick. Now, I am seeing the message again, and I don't know why. .hushlogin still exists in my home directory. Here's my /etc/login.defs:
# /etc/login.defs - Configuration control definitions for the login package.
# Three items must be defined: MAIL_DIR, ENV_SUPATH, and ENV_PATH.
# If unspecified, some arbitrary (and possibly incorrect) value will
# be assumed. All other items are optional - if not specified then
# the described action or option will be inhibited.
# Comment lines (lines beginning with "#") and blank lines are ignored.
# Modified for Linux. --marekm
# Delay in seconds before being allowed another attempt after a login failure
FAIL_DELAY 3
# Enable display of unknown usernames when login failures are recorded.
LOG_UNKFAIL_ENAB no
# Enable logging of successful logins
LOG_OK_LOGINS no
# Enable "syslog" logging of su activity - in addition to sulog file logging.
# SYSLOG_SG_ENAB does the same for newgrp and sg.
SYSLOG_SU_ENAB yes
SYSLOG_SG_ENAB yes
# If defined, either full pathname of a file containing device names or
# a ":" delimited list of device names. Root logins will be allowed only
# upon these devices.
CONSOLE /etc/securetty
#CONSOLE console:tty01:tty02:tty03:tty04
# If defined, all su activity is logged to this file.
#SULOG_FILE /var/log/sulog
# If defined, file which maps tty line to TERM environment parameter.
# Each line of the file is in a format something like "vt100 tty01".
#TTYTYPE_FILE /etc/ttytype
# If defined, the command name to display when running "su -". For
# example, if this is defined as "su" then a "ps" will display the
# command is "-su". If not defined, then "ps" would display the
# name of the shell actually being run, e.g. something like "-sh".
SU_NAME su
# *REQUIRED*
# Directory where mailboxes reside, _or_ name of file, relative to the
# home directory. If you _do_ define both, MAIL_DIR takes precedence.
# QMAIL_DIR is for Qmail
#QMAIL_DIR Maildir
MAIL_DIR /var/spool/mail
# If defined, file which inhibits all the usual chatter during the login
# sequence. If a full pathname, then hushed mode will be enabled if the
# user's name or shell are found in the file. If not a full pathname, then
# hushed mode will be enabled if the file exists in the user's home directory.
HUSHLOGIN_FILE .hushlogin
#HUSHLOGIN_FILE /etc/hushlogins
# *REQUIRED* The default PATH settings, for superuser and normal users.
# (they are minimal, add the rest in the shell startup files)
ENV_SUPATH PATH=/sbin:/bin:/usr/sbin:/usr/bin
ENV_PATH PATH=/bin:/usr/bin
# Terminal permissions
# TTYGROUP Login tty will be assigned this group ownership.
# TTYPERM Login tty will be set to this permission.
# If you have a "write" program which is "setgid" to a special group
# which owns the terminals, define TTYGROUP to the group number and
# TTYPERM to 0620. Otherwise leave TTYGROUP commented out and assign
# TTYPERM to either 622 or 600.
TTYGROUP tty
TTYPERM 0600
# Login configuration initializations:
# ERASECHAR Terminal ERASE character ('\010' = backspace).
# KILLCHAR Terminal KILL character ('\025' = CTRL/U).
# UMASK Default "umask" value.
# The ERASECHAR and KILLCHAR are used only on System V machines.
# The ULIMIT is used only if the system supports it.
# (now it works with setrlimit too; ulimit is in 512-byte units)
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
ERASECHAR 0177
KILLCHAR 025
UMASK 077
# Password aging controls:
# PASS_MAX_DAYS Maximum number of days a password may be used.
# PASS_MIN_DAYS Minimum number of days allowed between password changes.
# PASS_WARN_AGE Number of days warning given before a password expires.
PASS_MAX_DAYS 99999
PASS_MIN_DAYS 0
PASS_WARN_AGE 7
# Min/max values for automatic uid selection in useradd
UID_MIN 1000
UID_MAX 60000
# System accounts
SYS_UID_MIN 500
SYS_UID_MAX 999
# Min/max values for automatic gid selection in groupadd
GID_MIN 1000
GID_MAX 60000
# System accounts
SYS_GID_MIN 500
SYS_GID_MAX 999
# Max number of login retries if password is bad
LOGIN_RETRIES 5
# Max time in seconds for login
LOGIN_TIMEOUT 60
# Which fields may be changed by regular users using chfn - use
# any combination of letters "frwh" (full name, room number, work
# phone, home phone). If not defined, no changes are allowed.
# For backward compatibility, "yes" = "rwh" and "no" = "frwh".
CHFN_RESTRICT rwh
# List of groups to add to the user's supplementary group set
# when logging in on the console (as determined by the CONSOLE
# setting). Default is none.
# Use with caution - it is possible for users to gain permanent
# access to these groups, even when not logged in on the console.
# How to do it is left as an exercise for the reader...
#CONSOLE_GROUPS floppy:audio:cdrom
# Should login be allowed if we can't cd to the home directory?
# Default in no.
DEFAULT_HOME yes
# If defined, this command is run when removing a user.
# It should remove any at/cron/print jobs etc. owned by
# the user to be removed (passed as the first argument).
#USERDEL_CMD /usr/sbin/userdel_local
# Enable setting of the umask group bits to be the same as owner bits
# (examples: 022 -> 002, 077 -> 007) for non-root users, if the uid is
# the same as gid, and username is the same as the primary group name.
# This also enables userdel to remove user groups if no members exist.
USERGROUPS_ENAB yes
Please help.
Last edited by nbtrap (2012-07-14 21:59:46)

orbisvicis wrote:see "pam_mail.so" in /etc/pam.d/* and "man pam_mail". You most likely need the nopen argument.
Thank you. I fixed it by changing a line in /etc/pam.d/system-login. Specifically, I changed
session optional pam_mail.so dir=/var/spool/mail standard
to
session optional pam_mail.so dir=/var/spool/mail nopen

Is there a way to disable push mail from Yahoo? It's draining my battery

I'm on the prepaid plan and every 10-15 minutes my iphone turns on with a "The last transaction cost $0.00" message. I don't mind the message (although it is a bit annoying) but my problem is that this turns the LCD on for about 2 minutes at a time.
I charged my battery to 100% last night, haven't used it at all today and after just turning it on a few minutes ago I had the "Your battery life is at 10%" message followed by a 5% remaining message a few minutes later.
I've heard that it's the yahoo push mail service thats causing the phone to give the message (since it connects to the internet). My Yahoo account is my main one and I'd hate to have to login to yahoo's site each time to check it (the email functionality was a big selling point for me with the iphone). ATT/Apple don't seem to want to disable this message/"Feature", so I'm guessing I would need to step in and do something on my end.
Is there any way to disable yahoo mail from "pushing" messages to my phone? I can hit the Check Mail button if I have to.

Hi Everyone,
To give an update on the situation: I disabled the Yahoo account and it seems to make a VERY NOTICEABLE difference in battery life - prior to this my battery would drain quite rapidly but since disabling it it's only lost about 15-20% over the past 24 hours (and thats with using the video/music/internet functions for about an hour and a half).. Prior to this it would have been close to drained under the same circumstances.
Also, to confirm, the "Your last transaction cost 0.00" messages only appear when accessing the internet manually now. before they appeared every 10-15 minutes with no interaction from myself at all (while it was sitting idle, while watching videos, while charging, while in my pocket, etc..)
I do have it set to only check Manually but Yahoo would seem to check on it's own even though this setting is checked (I'm guessing it has to do with the Push setting). Aside from draining the battery, it was quite annoying having 30 or so "Your transaction cost $0.00" messages to click through whenever I turned on the phone.
I did have the screen set to shut off after 1 min, but the 'your transaction cost..' messages would first wake the iphone up, the screen would stay bright for about 30 seconds, dim for about 30 seconds, then turn on bright again for 1 minute until it shut off. I'm guessing the screen (being on for about 10-15 minutes per hour due to this) and the fact that yahoo accesses the internet on such a frequent basis are what cut the battery life down.
I really wish I could make Yahoo work more like Gmail and have it manually search for new mail

Is there a way to temporarily disable voice mail

I am interested in knowing if I can temporarily disable the ability for someone to leave me voice mails?

Contact your carrier, Voicemail is a carrier feature & some carriers require it & will not disable it. But, contact yours to see what their polices are.

How to disable login mail checking?

I would like to disable the mail checking on each login: I am not interested in seeing "No new mail" or else each time I login in a console. In other distributions, there was a specific setting in /etc/login.defs:
MAIL_CHECK_ENAB = no
I do not find this option in the arch /etc/login.defs, nor it is mentioned in man login or man login.defs; trying to set it anyway results in login complianing about badformed configuration file.
I also tried to comment out both MAIL_DIR and QMAIL_DIR, but without success.
Is there an other method to get this result? Thanks in advance for your help.

I have finally solved this issue, after only 4 months (it was my first issue using archlinux). Since the most part of shadow functionality is managed by pam, /etc/login.defs is not used at all. I had to edit /etc/pam.d/login. I had to comment out this line in that file:
# session optional pam_mail.so dir=/var/spool/mail standard
I am very satisfied, I hated those unuseful "No new mail"

E71 Mail for Exchange System Error, try again late...

Hi,
Please Help!
I installed MfE 2.7 on my E71, but whenever I try to sync my email and calender, I get a system error.
It begins to sync the email but after that it doesn't sync the calender and I get the system error. Also each time it tries to sync emails, it retrieves all the mail each time.
If I sync only the calender, it retrieves all the items and I get a system error. I've pasted the admin log below.
27/10/2008 10:17:42 start Email sync
27/10/2008 10:17:53 sync died (11), collection=Email activity=handling commands from server
27/10/2008 10:22:36 PING Command Requested
27/10/2008 10:22:42 start Email sync
27/10/2008 10:23:01 sync died (47), collection=Email activity=handling commands from server
Does anyone know how to solve this?

OK - like many on the copius web discussions on this Nokia E71 model/MfE topic I have been getting terminally frustrated with an otherwise great phone.
A trawl through the websites gave me lots of things to try, but most didn't work.
Our large corporate IT dept also were left scratching their heads, and resorted to a full reset, which cured the problem briefly, but as with others' experience it soon returned (also having to fully reconfig is a pain in the proverbial). Things suggested on the discussion sites like disabling Tasks synch, or Secure Connection didn't have any effect.
The fact that most others with the same phone on our system hadn't experienced the problem seemed to hint at it not being a server issue, but something more localised. The apparent fact that 'Emails' did synch OK, but that the process hung on 'Calendar' synch suggested it was a Calendar issue
One post mentioned issues with no-finish-date recurring appointments in Calendar, so I investigated these. I found that one or two had no end date, so I gave these items one.
But interestingly, I also found a high proportion of appointments that had been created last year (09) had end dates like 'Wed 31/03/00' when clearly 'Wed 31/03/10' was intended - was this an odd default in Calendar, or just careless typing? The consequences were that Calendar was possibly wrestling with numerous recurring appts with either 100-year durations, or possibly just hanging on the date confusion - is '00' before or after '10'?.
Therefore, as a precaution, I checked all my recurring appts like this (the procedure may vary according to your browser):-
- In Calendar, open each recurring appt in turn;
- Open the series, not just the individual appointment;
- Check 'Recurrence';
- Check that an 'End By' date is there, and that it is not '00';
- Click OK;
- Click OK again if warned about exceptions;
- Cick 'Save & Close'.
Do this to absolutely all recurring appointments in your Calendar.
Then do a full resynch (Menu/MfE/Synch Mode/Full Resynch etc).
I didn't hold much hope of any effect, but Lo!, it did work, and now Emails, Contacts, Tasks, and Calendar all synch fine so far, using Menu/MfE/Mail for Exchange/Options/Synchronise.
I hope this works for others...let me know if it does.

Mail for Exchange 3.0.50 - doesn' t sync Gmail any...

I have been using successfully Mail for Exchange v. 2.9.158 on my Nokia N95-1 to access Gmail and Google Calendar. Yesterday I have upgraded to Mail for Exchange v.3.0.50 and now I am facing the following problems: 1.When running Full Resync Mail for Exchange has forced the set storage destination for message to be changed from Memory Card to Phone Memory When I tried to make Full Resync with Mail for Exchange it at the end it forced to switch from using Memory card for storing messages to Phone memory. According message has been displayed stating that Memory card can not be used to store emails and therefore it switched to Phone memory. However at that moment there was enough extra space on both kinds of memories , and that one on Memory card was larger than available space on Phone Memory. I do not want to use Phone memory to store my emails as N95 Phone memory is so small. So then after Mail for Exchange finished a synchronization cycle I have switched again to Memory card option as a destination of all my messages - and Mail for Exchange has created MfE on Memory card too. I made few attempts, by disabling Email sync and then running Full Resync again, the result was the same/ After that I started to experience problem with synchronization that I never had with version 2.9.158. 2. Synchronization of email except starting Full Sync and few cycles afterward doesn't work anymore and provides on each synchronization cycle an error message "sync failed. If that continues please contact your administrator". When I switch storage to Phone Memory, however, evn with such message sync work. When I switch storage to Memory Card then after sync cycle there are all IMAP folders in place but all empty. My configuration setting now set as following: Connection Exchange Server: m.google.com Secure Connection: Yes Access Point: DTAC-Internet Sync while roaming: No Use default port: Yes * Credentials Username: [my email] Password: [my password] Domain: [empty] *Sync schedule: Peak sync schedule: Every 15 minutes Off-peak sync schedule: Every 15 minutes Peak start time: 08:00 Peak end time: 17:00 Peak days Mo. Tu, We, Th, Fr In case of conflict erver Wins *Calendar Synchronize Calendar: Yes Sync Calendar back: 6 months Initial Sync: Keep items on phone * Tasks Synchronize Tasks: No * Contacts Synchronize Contacts: Disable Initial Sync: * E-mail Synchronize Email: Yes E-mail address : [my email address] Show new mail popup: Yes Use signature: No Signature: None When sending mail: Send immediately Sync messaged back : 1 day How I can resolve it problem?

UP!
I have absolutely the same trouble.
When I sync gmail for the first time everything goes clear. After that I CAN recieve NEW mail on my phone on next syncs. I mean NEW is the mail, that haven't been read before with any other client.
But if I read this mail on other client, say in browser, the synchronization doesn't work anymore. I recieve no mails from that point.
Regards.
P.S. went back to 2.9.158, everything works well

I can not disable lock code for n8

Decided to setup the mail for exchange on my N8 so I could see my work emails. Worked like a charm but after a couple of hours decided I didn't like being that contactable so deleted the mailbox.
Now to the problem, during setup I was forced to enable the phone lock and had to pick an 8 digit numeric code. Fair enough I thought and went ahead. When I removed the mailbox however the lock remained in place with the default auto time of 20 minutes. When I checked in Phone management there is no option to disable this lock so I thought I could at least change the default time to something bigger but when you try, it remains at 20 mins. You also can't disable the auto time as it pops up an error message saying can't unlock phone

Yes, that phonelock is very unpleasant - caused by Mail-for-exchange ; the Phonelock is my reason to Un-install Mail-for-Exchange [you can't type a Five-digit code into your phone everytime you want to start Maps : you would crash your car!] . . . I will have to find a Mail-client that doesn't annoy me

Mail for Exchange and allowed models of phone

Could somebody tell me why my Nokia 6120 classic is not allowed to use Mail for Exchange tool. From my point of view there is some stupid marketing policy. As a result the policy just makes me to use third party software on my phone such as Roadsync.
Roadsync soft is working perfectly but why I have no ability to use native software from Nokia. It's some strange situation.

What do you mean? Is there some hardware or software problem which makes my phone incompatible with Mail for Exchange? I think the problem is just software stub which is purposely embedded into Mail for Exchange code in order to disable the tool on my model of phone.
I would like just to remind you that Roadsync is working properly on my phone.
Roadsync and Mail for Exchange use the same scheme of data synchronizing (Microsoft ActiveSync protocol)

Disable Junk Mail Filtering on a Specific Account

Is there a way to disable junk mail filtering on a specific account?
My Mac at home is always running Mail, which checks my work email. When I am at work, Mail (at home) sometimes marks a message as junk, and therefore my work mail program (Thunderbird) never gets it.
I know I could just close Mail when I leave home, but then I'd have to open it again when I get home and that's too much trouble.
Thanks!
Powermac G5 Mac OS X (10.4.2) Mail 2.1

You're welcome.
I'm still interested though if this is possible...
I am almost 100% certain there is not a way to enaable/disable junk mail filtering by account with the Mail.app.
For now, I've disabled moving junk mail to a different folder,
so it just marks it as junk and doesn't move it.
There is no selection to move messages marked as junk to a different mailbox. When Junk Mail is set to Automatic, messages automatically or manually marked as junk are moved to the account's Junk mailbox automatically. When Junk Mail is set to Training, messages automatically or manually marked as junk remain in the account's Inbox mailbox.
You don't have Junk Mail set to Automatic with the Mail.app?
If not set to Automatic, messages marked as junk by the Mail.app will remain in the account's Inbox mailbox and will not removed from the server.
If set to Automatic, you can select "Store junk messages on the server" under the Mailbox Behaviors tab for the account preferences. This way, any messages automatically marked as junk by the Mail.app will be stored on the server when the message is automatically moved to the account's Junk mailbox which will allow access to the same message when using another email client on a different computer at work.
This is a benefit of an IMAP type account over a POP type account so you have two options here.
Set Junk Mail to Automatic and store Junk messages on the server with the Mail.app or quit the Mail.app when leaving home.

Email account occasionally disabled by Mail

I'm not sure why, but one of my mail accounts will occasionally get "disabled" by Mail, as though I'd gone to Preferences > Accounts > [Account Name] > Advanced, and unchecked "Enable this account". It always happens with the same account, and will just occur randomly--so unless there's some hidden keyboard shortcut for disabling an account, I'm at a loss as to why this is happening. Any ideas or suggestions?

V.K. wrote:
this usually happens when Mail can not to connect to the Mail server for that account. there is nothing you can do about it.
That's not true. If Mail cannot connect to the server, the account just temporarily grays out until it can access the account again. It doesn't disable it and make it disappear from view. This is an anomaly that is happening to me too.

Disable e-mail for cloned environments

Similar Messages

Maybe you are looking for