Mail not being triggered in background

Hi Experts,
I am using the function module SO_NEW_DOCUMENT_ATT_SEND_API1 to send a mail with attachments to the user. The program in which the FM is used is scheduled in background. The problem is in my dev system, the mail is getting triggered without any issues but in Quality system, the mail is not getting triggered but the job runs successfully. I got some expection with sy-subrc = 2 , sy-msgid = SO ,sy-msgtyp=A ,sy-msgno=013,sy-msgvi=ADDR_PERS_COMP_COMM_GET in QA . When i tried to debug the background job, mail gets triggered successfully.
Can you please share your valuable suggestions in this regard.
Regards,
Vijayalakshmi

Hi Vijayalakshmi..
Can you please check whether the mail is reaching your sap outbox using tcode sbwp..
From what i understood if it is working fine in DEV and not in quality then it could be the mail configuration issue in QA.
You can also try one more thing. just got to sbwp and send a mail to the email id.
Regards
Ansari

Similar Messages

Mail not being sent for background job spool

Hello All,
I have created a back ground job by adding a mail id in the spool receipient list. The job has finished successfully and spool is created but the mail has not been sent I have checked SOST transaction and no mail has been sent to this mail id.
This is only happening for some jobs other jobs are able to successfully send the spool as mails to the mail id's mentioned in spool receipient list.
I would like to know why this is happening only for some jobs and how can I check the whether mail has been generated or not.
Your replies will be greatly appreciated.
Thankyou,
Ranjan

Hi
To check whether mail is generated you can create dynamic break-point with SAAB transaction.
Using this transaction you create a memory area for your jobs where you can load any data value of your report..
Probably something goes wrong with COMMIT of Mail Function module system.
Hope to help..

Why wont my mail open? The mail not being able to open is making me not be able to shut down my laptop.

Why wont my mail open? The mail not being able to open is making me not able to shut down my macbook.

Press power button down and hold up to 30 secs to force shut down and then start up and see how u goes on ur mail....

E mail not being received

Hi, I use BT yahoo mail through outlook 2010, sent mails show as sent in outbox, i get no error message but they are not going to recipients. I have deleted account and re set up in outlook i am using the IMAP settings as on the BT web site. When i send mail from my apple devices using same e mail account they are recieved ok? Any ideas ? Thanks in advance.I should add when i set up account in outlook and hit test message that gets received ok . In additon I can send myself emails using outlook.

I suspect that you may have the same issue as
https://community.bt.com/t5/Email/One-particular-recipient-not-receiving-my-Outlook-mail-but-can/td-...
https://community.bt.com/t5/Email/e-mail-not-being-received/td-p/1343373
https://community.bt.com/t5/Email/Cannot-send-emails/td-p/1343253
One solution may be to temporarily change your SMTP server to
smtp.mail.yahoo.co.uk

Rules in Mail not being applied after Mavericks update

Hi everyone, I know there are a lot of threads already discussing similar issues, but so far I've been unable to find one that helps resolve my particular issue. Ever since upgrading to Mavericks my rules are not being applied in Mail. I will give you a screenshot of one of my rules:
I have about five rules that follow the same pattern: search for particular string in the FROM field and mark it with a color if the string is present. These rules all worked fine in Snow Leopard. All of my rules are still present after the upgrade and all checked as active. When I "select all" messages in my inbox and press Option-Cmd-L the rules are applied properly. However, the rules are not applying themselves when new mail comes in. As far as I can tell this does not have anything to do with the mail not being recognizes “as a new message” like, for example, because the mail was already read on my phone. It happens even if my other devices are offline and the only thing I am using to check mail is my laptop.
I am using a MacBook Pro 2.3 GHz Intel Core Duo with OS X 10.9.1, in case that matters.
Thanks for any advice!

I think I've found at least a partial solution to the Mail - Rules Don't Work problem:
In "Mail" go to the menu Mailbox and click on Rebuild.
If you have a lot of stuff, this will take several minutes to finish.
I also reviewed all my rules and made a few minor changes.
Mixed results: I found that running "Apply Rules" didn't work on email already received; but new mail did. I don't quite understand that, but I call it a partial success.

Overhead user exit (COOM0001) not being triggered for specific plant

Hello all,
I was wondering if anyone came across this situation before. I activated user exit COOM0001 for overhead calculation. This user exit is triggered when I create PCE for plant A but not plant B.
I can't figure out why it is not being triggered for plant B at all. I put a break point in function module EXIT_SAPLKASC_001, EXIT_SAPLKASC_002 and EXIT_SAPLKASC_003 and the system didn't stop in anyone of these function module.
Any help is greatly appreciated.
Regards,
Cassandra

Hi
It seems that you are a Functional Consultant.
Please follow the following simple step for any userexit to see where all its been called.
1. Go To T. Code SMOD
2. Enter the Exit name COOM0001
3. Click on the COMPONANTS RADIO BUTTON and DISPLAY
4. U get Function Modules
EXIT_SAPLKASC_001
EXIT_SAPLKASC_002
EXIT_SAPLKASC_003
5. Now individually double click on each FM and put a break point ther.
6. Open a new session and see wheather it stop at the break-points of the T. code you are looking for.
I havent used this user exit, so no comments on how it ll be use ful.
Reward points if useful
Thank-You
regards
vinsee

Solved Problem - mail not being sent and kept in Outbox....

I've posted a few messages here about mail not being able to be sent and kept in the Outbox.
It is solved. I believe.
Everything seems to be back to normal. I guess it was a problem of me over stepping limitations for .Mac e-mail, and getting locked out for a 24 hour period. So, I will be more care next time I need to e-mail large files to numbers of people ! Probably will invest in something like Stuffit and use there compression facility to reduce the size of files I want to send over the internet and via e-mail.
Thanks to those who took interest and gave advice.

You don't have to invest in Stuffit.
Built-in compression is included with the Finder.
To compress files before sending them, use the Archive command in the Finder's File menu. Select the file or files you want to compress, then choose File > Create Archive.
A compressed archive of the files is created. If you archive a single item, the archived file has the name of the original item with a ".zip" extension. If you archive multiple items at once, the archived file is named Archive.zip.
Recipients can open the archive by double-clicking regardless the platform - Windows or OS X.

Lion Server postfix mail not being delivered to mailboxes. "SMTP restriction `reject_invalid_helo_hostname' after `permit' is ignored" and "connect to private/policy: Connection refused" errors.

All, Im stumped. In fact I have been on the phone with Apple Support and this has been escalated to the top engineers, as I think its got them too..
Anyway, here is my problem..
I'm running an Mac Mini with OS X 10.7.4 Server. I have had mail running on it for 2 months or so, without any issues. The mail was actually migrated from 10.6 in March, and It actually went smoothly. I have 3 domains which all recieve mail and they all work (or did up until 2 weeks ago)..
So the story is this.. I can send mail from my domains, without issue. imap and dovecot must be working.. cause all the stored mail, can be read with the mail IMAP client.. I can even transfer mail messages from one mailbox to another with Mail client. Sending mail is a breeze, it still works and the recipients still recieve their mail. But I noticed I wasnt getting any mail at all from those mailboxes... no mail, no spam, nothing.. which is unusal. I fired up Server admin and checked out the SMTP log, and this is what it showed for every email recieved: (xxxxxx is just me hiding sensitive info)
Jul 21 14:25:20 xxxxxxxx postfix/postscreen[65857]: CONNECT from [17.158.233.225]:41909
Jul 21 14:25:26 xxxxxxxx postfix/postscreen[65857]: PASS OLD [17.158.233.225]:41909
Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: connect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: warning: restriction `reject_invalid_helo_hostname' after `permit' is ignored
Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: NOQUEUE: reject: RCPT from nk11p03mm-asmtp994.mac.com[17.158.233.225]: 451 4.3.5 Server configuration problem; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<nk11p99mm-asmtpout004.mac.com>
Jul 21 14:25:28 azathoth postfix/smtpd[65858]: disconnect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
Ok, now what is odd, is these rejected messages are not even appearing in the mail queue in Server Admin. I have no idea why there are not being delivered
Ive checked my postfix main.cf file and master.cf files they both look ok.. Ive even replaced them with the main.cf.defualt.10.7 and master.cf.default.10.7 files and to no avail... same problem..
So in summary
I can send mail out
IMAP is working on the client end (thus dovecot is) exsisting stored emails can be accessed, read, moved unread etc..
mail is coming into the sever, but its being rejected. there is NO rejection email sent back to the sender.
mail is recieved by postfix, but cyrus isnt doing anything with it.. I have no idea where it goes...
Could anyone shed light on this...
my main.cf file:
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
# The general format of each line is: parameter = value. 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,
azathoth:postfix root#
azathoth:postfix root# less main.cf
azathoth:postfix root# more main.cf
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
# The general format of each line is: parameter = value. 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 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

Ok 1st one. The warning restriction message relates to this line in main.cf:
smtpd_helo_restrictions = permit_sasl_authenticated permit_mynetworks check_helo_access hash:/etc/postfix/helo_access reject_non_fqdn_hostname reject_invalid_hostname permit reject_invalid_helo_hostname
The last reject occurs after the single word "permit" and is ignored.
However, that's not the problem.
I'm not exactly sure what's happening, but this might be a clue.
It would appear that either postfix is not being able to create the socket for private/policy or it's somehow created with the wrong permissions. You might need to ramp up the debug level to get a better idea.
You could check if it's being created by "netstat -a | grep private/policy" in terminal.
My guess is that it's not being created because there is no setup statement in your master.cf file, but I don't understand why postfix would be looking for it if it isn't set up. Private/policy I think relates to grey listing. Maybe gives you a hint.

E-mail not being delivered - AGAIN!!!

This *****!!! You guys are really ruining my e-mail ability...since I do pay for this service!!! Stop blocking my e-mail! I'm really ******!!!!
This is the second week my e-mail has been rejected by the server and I've not been able to finish sending out my mail to people. I organize a class reunion. I e-mail about 200 people once a week. For some reason there was a change to a setting somewhere along the line and 2 weeks ago my mail stopped being delivered. I stated in my last contact that I would switch to a free service that would allow me to send my mail. I don't use all the .Mac services and I can get web space much cheaper.
Either fix this or consider me (a member for 4+ years) cancelled. I don't have time to write to you guys every week about this. Did I mention I was ******?
[email protected]
It's not like I am sending out huge files or something like that. See below.
This is what I am sending.
Hello Class of 1992,
Okay, you can stop waiting now. You've got to make your move and send in your money for tickets. Get them before the May 15 deadline and save yourself $40 dollars!
I've heard from so many of you over the past 5 years of working on this project and there has been a great deal of interest over this period of time. So...here we are...it's almost happening and you need a ticket to get in the door.
We had a meeting this weekend in the space rented for the 15 year reunion and we've got such a great location chosen for you guys. We'll be right on the beach which we have access to during the day for those who want to show up with coolers and beach chairs to relax, meet and greet. Bring your kids, spouses and spirit of fun to the afternoon beach time.
You are going to have a great time during the evening. We've got plenty of food available, drinks, music and how many reunions do you know of that have a tower to overlook the entire beach at their disposal?
It's gonna be awesome! And guess what...YOU ARE INVITED!!!
Get your ticket ordered early....save some $$$ and start off your summer right with old friends, fantastic times and new memories.
For a single person it's only $85.00 dollars. If you bring your spouse or date; only $125.00 per couple. And heck, if you've got anyone else you'd like to bring it's only $45.00 for each additional person. You can't beat it for an awesome time.
Make your check payable to Bill (Billy) Owens (Reunion Treasurer).
Mail to:
3765 Silina Drive
Virginia Beach, VA 23452
See you on June 16!
www.kempsville1992.com

Parsing through your rant which isn't directed at Apple, it seems you might be exceeding the sending limits included with a .Mac account which are not extreme by any means so take a deep breath and calm down.
All internet service providers and email account providers (even free ones) have sending limits or restrictions for non-business/personal email accounts.
These restrictions are in place as part of an overall effort to prevent spam emanating from an ISP's or email account provider's domain. In case you aren't aware, spammers make use of bulk spam mailings and these restrictions make it more difficult for a spammer to do his thing.
It makes no difference that you aren't a spammer or the content of your message is not spam since there is no way an ISP or email account provider can make this determination when you send a message but they can impose sending limits or restrictions.
Copied from the following link.
http://docs.info.apple.com/article.html?artnum=25301
.Mac has several safeguards in place to ensure that only .Mac members send messages with the Mac.com outgoing mail server. Among them are reasonable limitations on:
* The number of messages that can be sent each day (200 messages)
* The number of recipients that can be sent to each day (400 recipients)
* The number of recipients a message can be addressed to at one time (100 recipients)
* The size of outgoing messages
There is also a 10 MB maximum size for messages sent or received using the .Mac mail system.
.Mac Email has been designed primarily for personal use. Sending unsolicited bulk email messages through the .Mac email server is prohibited.
If your message is being rejected by a recipient's incoming mail server, what is the return email error message provided which is sent by the recipient's incoming mail server?
Regardless, this problem is with the recipient's email account provider. If the return email error message from the recipient's incoming mail server indicates the recipient has exceeded their allocated server storage space, this the recipient's problem.
So instead of ranting, how about providing more detailed information about the error message provided so someone here can help narrow down where the problem lies so you can direct your efforts there.
IMO - since you use your .Mac account for email only, you should cancel your account but keep in mind that even a "free" service includes sending restrictions which may not be identical to .Mac account restrictions but none are restriction free.

Samsung note II, known issue of aol mail not being received on phone

I spent hours on the phone with Customer Service this past Wednesday & Thursday because my aol mail is not being received on my new phone. I just did some research online, and found out this has been an issue with AOL and Verizon since December 2012. The Customer Service rep told me this just happened the past week! What a bold faced lie!
I purchased this phone on or about July 3, and the AOL mail was working fine until this past Wednesday.
This is a know issue, and yet the lie right to your face about it.
I had a C/S rep tell me he would call me back later in the day, before he left work. I told him, I have heard that before. Oh, no, I will call you. Of course he didn't call. Your C/S reps think they can say whatever they want, but the calls have been monitored or tracked someway by your computer system.
I see many others have the same problem with the Samsung Note II and their email accounts.
Since December this has been going on, don't you think it's time you fixed the problem?
Two years ago, when I spent $200 on a phone, I said never again. But yet I wanted a 5.5" screen so I paid up! Never again!

I FINALLY spoke to someone today who was able to solve my problem so far.
In the PLAY STORE....look for K9 email app.....and download that...put in your AOL email address and password. You should now be able to receive your aol email on your phone.
It seems he has a Note II also, and had the same problem.
You would think that MANAGEMENT would tell all their C/S reps how to solve the problem. I guess they would rather lose a customer who has been with them for 10 yrs.

Integration Process is not being Triggered

Hi Gurus,
I have a file to file scenario in which I am using BPM to make a synch call in between.
Everything appears to be fine in IR and ID.
But, Intergration Process is not being determined as a receiver and hence, IP is not getting triggered.
When I checked the trace.
At top it says.. 1 Recvr is determined.
<Trace level="2" type="T">O U T B O U N D - B I N D I N G</Trace>
<Trace level="2" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">determine OUTBOUND BINDING for:</Trace>
<Trace level="2" type="T">-SENDER_SYSTEM</Trace>
<Trace level="2" type="T">-IP_NAME</Trace>
At bottom it says.. no recr determined as shown below.
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
Could you please help me to resolve this issue..
Thanks in Advance..
Pushkar

Hi Bhavesh,
Thanks for a quick reply.. well.. cache refresh doesnt help me..
I created a couple of more scenarios.. n every where i m getting the same error..
When I check the IP in the process builder.. i.e. using transaction SXMB_MONI_BPE,
I find an extra container operation step "Initialize System Element" just after recieve step.
I am wondering about this step.. I have worked on BPM earlier but have never noticed this step..
Regards..
Pushkar...

Enhancement spot - Function module not getting triggered in background

Hello Experts,
I have implemented an explicit enhancement spot. In the code implementation, I am calling a Function Module.
When I call that FM in background, things are not working as expected. But if I am calling that FM in normal mode, things are working fine.
I am passing parameter to FM by 'Value'.
Can anybody please let me know what I am doing wrong?
Regards,
Ashish

Hi,
Enhancement not getting triggered in BDC
Regarding on your query, You would go through below link.
Screen Enhancement of Transaction CO11N
I hope, it helps to you.
Regards,
Sekhar

Exit Class for Inbound Mail not getting triggered

Hi Gurus,
I have created an exit class for processing the Inbound Mail that comes to SAP Inbox (SOIN).
I have set up the Inbound processing rule in transaction SO50 and set it to all recipients.
If i send a mail from any external id to the id configured in SAP then it is coming in SAP Inbox (SOIN) but the exit class for processing the email is not getting triggered.
I have made all the settings for SMTP.
Kindly guide me with the steps needed to be followed for triggering the Exit Class.

Hi
Check u have maintained ur outgoing mail server IP in SCOT transation.
Check link step to configure PO mail.
http://architectsap.com/blog/sap/sap-mm-purchasing-send-purchase-order-by-mail-to-vendor-in-sap/

WIA not being triggered

Hey all! We have Windows Integrated Authentication (WIA) working fine on our dev environment but for some reason can't duplicate it on our Prod servers.
By accessing the dev url it auto-authenticates me and I can see the SSO via the IIS log files.
However when I access our Prod URL the SSO files (SSOLogin.aspx) aren't being triggered.
I've checked that the SSO folder in IIS is set for Integrated Auth and anonymous access has been removed. Our config files look to be in sync and the auth service is set for SSO. I'm a little baffled why its not triggering.
Any ideas?

Assign the listener to the stage, not this...
stage.addEventListener(KeyboardEvent.KEY_DOWN, eventKeyDown);
and be sure to Disable Keyboard Shortcuts via the Flash Player's Control menu options

Dynamic Action not being triggered in Batch

Hi Gurus,
We have the below Dynamic Action that is not getting triggered when we run a Batch to Create IT2010. We are using TCode PTE1 to create the batch.
2010                   4     5     P     T001P-MOLGA='10'
2010                   4     10     P     PSPAR-TCLAS='A'
2010                   4     12     P     P2010-LGART='4023'
2010                   4     15     I     INS,2001,,,(P2010-BEGDA),(P2010-ENDDA)/D
2010                   4     20           **P2001-AWART='0100'
2010                   4     21     W     P2001-AWART='1300'
2010                   4     25     W     P2001-STDAZ=P2010-ANZHL
I have read a few posts on how this can be done, but not very clear as to whether it can even be achieved.
This Dynamic Action works fine when we manually Create an IT2010 record via PA30, it creates the IT2001 in the background.
Cheers,
Anil

Hello Anil,
Please check the following note, I think note should be helpful in this case.
386027   Dynamic actions
1564499 Processing initial values which are not valid in
Best Regards,
Deepak.

Mail not being triggered in background

Similar Messages

Maybe you are looking for