'SO_DOCUMENT _SEND_AP1' and CC recipients

In 'SO_DOCUMENT SENDAP1' is there a parameter to flag to send e-mail to CC recipients (instead of primary recipient ) ?
Thanks in advance
Andrew

Hi ,
In the receiver we have one option that type of sending TO , CC or BCC.. ireceivers-notif_del = 'X'. make this as field has the X.
For your reference...
If u r in the 4.7 version use this FM , If u r in ECC 6 use the oops concept , there will be problem with this FM ...
For the better example refer the Programs BCS_EXAMPLE1 to BCS_EXAMPLE7.
Regards,
Bharani
Edited by: SeethaRamaiah Bharani on May 9, 2010 10:59 PM

Similar Messages

Why does the smiley images in iChat on my Macbook Pro come across as symbols to my iPad and iPhone recipients? example: 3 comes across instead of a "Heart" image

Why does the smiley images in iChat on my Macbook Pro come across as symbols to my iPad and iPhone recipients? example: <3 comes across instead of a "Heart" image

Those chat images only work with iOS based devices. If they're being sent to someone without an iOS device, it will go through as an ASCII character.

How do I NOT send attachments to CC and BC recipients

I used to be able to do it in Entourage. I want to forward and email with attachments, but not have the attachments go to CC and BC recipients. Looked everywhere in preferences. I'm stuck. Is this possible?

Mail doesn't support that.
According to the RFCs that cover e-mail, the Cc and Bcc are simply headers that control the copy and deliver of the message. They should all receive the same body of the message. The behavior of Entourage was dependent on a feature of MS exchange that subverted the normal rules for how e-mail is transferred and would strip the attachments if requested to do so. Standard mail client software wouldn't do this.

Send mail with attachment and more recipients

Hi to all,
I have this procedure :
PROCEDURE SPEDISCI_MAIL
Mittente IN VARCHAR2,
Destinatario IN VARCHAR2,
Oggetto IN VARCHAR2,
Messaggio IN VARCHAR2
IS
mailhost VARCHAR2(40) := 'pippo.com';
conn utl_smtp.connection;
crlf VARCHAR2( 2 ):= CHR( 13 ) || CHR( 10 );
mesg VARCHAR2( 1000 );
local_mittente VARCHAR2(2000) := mittente;
BEGIN
conn := utl_smtp.open_connection (mailhost,25);
mesg:='Date:'||TO_CHAR(SYSDATE,'dd mon yy hh24:mi:ss')||crlf||
'From:<'||mittente||'>'||crlf||
'Subject:'||Oggetto||crlf||
'To:'||destinatario||crlf||''
||crlf||messaggio;
utl_smtp.helo(conn, mailhost);
utl_smtp.mail(conn,local_mittente);
utl_smtp.rcpt(conn,destinatario);
utl_smtp.data(conn, mesg);
utl_smtp.quit(conn);
END;
Can I send mail with attachment and more recipients?
Thank you
Silvia

Consider using UTL_MAIL package:
http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14258/u_mail.htm
(Note: it's not installed and configured by default, but the scripts are supplied with the Oracle database, see documentation for instructions)

Mail "Reply All" and Bcc recipients

If I reply to an email and use "Reply All", will the Bcc recipients from the original author of the email be included in my reply?
I'm concerned that some people who I am not aware of may unintentionally receive my reply.
Thanks for any help.
Peter

Help please!!!
I am a new AppleMail user with a directory that along with individual email addresses, also has a 30 basketball players list in one group.
I tried to send out a blast to everyone asking if they are playing tomorrow? Everyone replies TO ALL with an "in" if they are playing, or "out" if they can not. That way everyone counts the amount of 'in's to see if we are playing or not.
They all got the email fine, but responded to me via email that there was no "reply to all" on my email blast.
That is a big problem.
I sent it from my directory, but it is like the system thinks that rather than having sent it to a group of thirty guys, it sent it to thirty persons individually. Perhaps it would not allow a 'reply to all' becuse of that.
I then tried something different.
As an experiment, I created a four person email group, dragged the group list icon to the address box for sending out emails, it accepted it, and I hit send.
It went.
My email was one of the four.
I got it, and it showed a 'reply to all' (which worked as I replied to all and I got the reply) but the other three did not get it.
So that clearly is not the answer.
By the way, I have a MacBook Pro using Mac OSX verson 10.5.8 with a 2.8 GHz Intel Core 2 Duo processing chip.
Memory 4gb 1067 MHz DDR3 if any of that means anything to you all.
Help!!!!
Any Apple Geniuses out there?
Brian

How to Improve Design for HTML, Plain Text and Multiple Recipients?

Hello there,
JavaMail programming is so fun! I first start off mixing the JavaMail code inside a servlet and then refactored it to two separate classes.
Mailer is the independent class which uses JNDI to look up config parameters, sends e-mails, and then closes the connection with the protocol.
public class Mailer {
     private Session mailSession;
     protected void sendMsg(String email, String subject, String body)
     throws MessagingException, NamingException {
          Properties props = new Properties();
          InitialContext ictx = new InitialContext(props);
          Session mailSession = (Session) ictx.lookup("java:/Mail");
          String username = (String) props.get("mail.smtps.user");
          String password = (String) props.get("mail.smtps.password");
          MimeMessage message = new MimeMessage(mailSession);
          message.setSubject(subject);
          message.setRecipients(javax.mail.Message.RecipientType.TO,
                    javax.mail.internet.InternetAddress.parse(email, false));
          message.setText(body);
          message.saveChanges();
          Transport transport = mailSession.getTransport("smtps");
          try {
               transport.connect(username, password);
               transport.sendMessage(message, message.getAllRecipients());
               Logger.getLogger(this.getClass()).warn("Message sent");
          finally {
               transport.close();
}MailController is just a simple Java servlet where a Mailer object is instantiated and a String is passed inside the Mailer.sendMsg() method.
public class MailController extends HttpServlet {
     /** static final HTML setting for content type */
     private static final String HTML = "text/html";
     myapp/** static final HTML setting for content type */
     private static final String PLAIN = "text/plain";
     public void doGet(HttpServletRequest request, HttpServletResponse response)
     throws ServletException, IOException {
          doPost(request, response);
     public void doPost(HttpServletRequest request, HttpServletResponse response)
     throws ServletException, IOException {
          response.setContentType(PLAIN);
          PrintWriter out = response.getWriter();
          String mailToken = TokenUtil.getEncryptedKey();
          String body = "Hello there, " + "\n\n"
                    + "Wanna play a game of golf?" + "\n\n"
                 + "Please confirm: https://localhost:8443/myapp/confirm?token="
                 + mailToken + "\n\n" + "-Golf USA";
          Mailer mailer = new Mailer();
          try {
               mailer.sendMsg("[email protected]", "Golf Invitation!", body);
               out.println("Message Sent");
          catch (MessagingException e) {
               e.printStackTrace();
          catch (NamingException e) {
               e.printStackTrace();
}Have some design issues...
If you can notice, I manually place the body of the e-mail (as a String) from inside the client (in this case, a Java Servlet). Also, I manually have to switch the content type inside the doPost().
Question(s):
(1) How can the Mailer class be set up, so it can send both HTML and plain text messages?
(2) How can the Mailer class be structured to send e-mail to multiple recipients or one user?
(3) Would both of these features / actions require writing two overloaded methods for sendMsg()?
Would appreciate it if someone could help me...
Happy programming,
Michael

Okay, I came up with this single method:
Mailer.java:
public class Mailer
     private Session mailSession;
     protected void sendMessage(String email, String recipient, String subject,
               String plainText, String htmlText)
        throws MessagingException, NamingException
          Properties props = new Properties();
          InitialContext ictx = new InitialContext(props);
          Session mailSession = (Session) ictx.lookup("java:/Mail");
          String username = (String) props.get("mail.smtps.user");
          String password = (String) props.get("mail.smtps.password");
          MimeMessage message = new MimeMessage(mailSession);
          InternetAddress from = new InternetAddress(email);
          InternetAddress to = new InternetAddress(recipient);
          message.setSubject(subject);
          message.setFrom(from);
          message.addRecipient(Message.RecipientType.TO, to);
          Multipart multipart = new MimeMultipart();
          BodyPart messageBodyPart = new MimeBodyPart();
          messageBodyPart.setText(plainText);
          multipart.addBodyPart(messageBodyPart);
          messageBodyPart = new MimeBodyPart();
          messageBodyPart.setContent(htmlText, "text/html");
          multipart.addBodyPart(messageBodyPart);
          message.setContent(multipart);
          Transport transport = mailSession.getTransport("smtps");
          try {
               transport.connect(username, password);
               transport.sendMessage(message, message.getAllRecipients());
               Logger.getLogger(this.getClass()).info("Message sent");
          catch (Throwable t) {
               Logger.getLogger(this.getClass()).error("Unable to Send Message");
               t.printStackTrace();
          finally {
               transport.close();
}Created a MailController class to instantiate and run the Mailer class.
public class MailController extends HttpServlet {
     // doPost() method()
     public void doPost(HttpServletRequest request, HttpServletResponse response)
     throws ServletException, IOException {
          response.setContentType(PLAIN);
          PrintWriter out = response.getWriter();
          String mailToken = TokenUtil.getEncryptedKey();
          String plainText = "Hello there, " + "\n\n"
                    + "I wanna invite you to a game of golf!" + "\n\n"
     + "Please confirm: https://localhost:8443/myapp/confirm?token="
                    + mailToken + "\n\n" + "-Golf USA";
          String htmlText = "<H1>Golfer Challenge!</H1>";
          Mailer mailer = new Mailer();
          try {
               String from = "[email protected]";
               String recipient = "[email protected]";
               String subject = "Golf Challenge";
               mailer.sendMessage(from, recipient, subject, plainText, htmlText);
               Logger.getLogger(
                           this.getClass()).info("Message Sent to: " + recipient
                                                          + " from: " + email);
               out.println("Message Sent to: " +
                                         recipient + "\n" + " from: " + email);
          catch (MessagingException e) {
               e.printStackTrace();
          catch (NamingException e) {
               e.printStackTrace();
}Question(s):
(1) How come the Multipart Alternative only supports HTML for the second part? Can I specify it to send HTML first and plainText second?
(2) How would I send in multiple recipients? Would I have to pass in an array reference (surrounded by a for loop) inside sendMessage() as follows:
mailer.sendMessage(from, myArray, subject, plainText, htmlText);
Thank you for all of your help!
-Michael

Message errors and mixed recipients

I recently updated my iPhone and in two separate cases, people who texted me actually got my daughters phone as well. She was able to see their text to me. They do not have my daughter's number so its very strange and in one case they initiated the text so they could not have had her number and I did not accidently pick a multi-party SMS. Anyone else with a similar problem? As a background, my daughter and I share the same icloud/itunes acct since she buys all the music and I pay for it. J..

I think I found the issue playing with the phone settings. I think I had imessage turned on and it syncronized all the phones [devices] on the same apple account. I wish there were a way to share itune accounts within the family with different apple id's....hope they figure it out.

Rules won't work? for TO and FROM recipients in 4.5 Mail?

ok, I have tried for the last 2 hrs to get a simple rule but its not working. All I want to do is IF an email comes in from a specific email recipient, place that email in a Folder.
Its fine for incoming but if I send to that email recipient, its not placing it in that folder?
what am I doing wrong?
Any ideas?

I've just confirmed here that it works for me.
What version of the OS are you using?
Have you other rules in place? If so, try it with them turned off.
Try changing the rule so there is just the "To contains" part.
Try changing the rule so that rather than move it just "set color of background" and see if that works.

IBots - "cc" and "bcc" recipients configuration

Hi,
I need to change the "cc" and "bcc" recepients configuration from an existing application. My understanding is that the setting from delivers applies only to "to" reciepients and I don't see any option for "cc" and "bcc".
I haven't seen neither any option like this in the administration tool.
Do you know how to change these setting?
Thanks in advance!
Adrian

Ok, I'll try that, thanks!
Is it possible to configure two different users, one for "to" and another ond for "bcc" at the same time?
Thanks again :)
Adrian

Send Email With Attachment And Recordset Recipients

When I try to send an email with an uploaded attachment, then attach it to the email being sent out to a recordset, my server tells me it has exhausted all its memory to send out the file. The pdf is 10 megs and the amount of ram allowed to be used is 256 megs.
The problem is that it seems to be that the way in which it is goign about sending the email to a recordset is that, it combines the attachment for all the email address. So say i have 35 people in the recordset with a 10 meg pdf, turns into 350 of ram.
Has anyone had any experience with this?

Consider using UTL_MAIL package:
http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14258/u_mail.htm
(Note: it's not installed and configured by default, but the scripts are supplied with the Oracle database, see documentation for instructions)

How Hit Reply, then switch the To: and CC: recipients via keystroke?

Hi,
SITCH:
I use Apple Mail. I work at a company where my boss will OFTEN CC me in a reply to someone saying, here's my guy, he'll' take it from here.
I hit Reply to All and , of course, He's in the TO field and the actual people I wish to be replying to are in the CC field still. I have to manually switch 'em, which is easy, but after 1,001 times makes me wonder...
Does anyone know a quick keystroke or Script that could switch the contents of those 2 fields (CC: and To:) ba da boom?
Thanks

there is definitely no built in way to do this. it might be possible to sort of do this by an apple script but you'll loose the reply formatting of the body of the message and it might not work well with html formatted messages or messages with attachments.

Address Book Contacts and Mail Previous Recipients Missing/Empty/Deleted

At one point yesterday, I was happily catching up on some email using Mail. All was well. I toggled a message as Junk and went to forward it to [email protected], which was, of course, in my Previous Recipients list. Only this time it wasn't. I noticed, too, in iChat, that all of my buddies had reverted to their IM screen names from their normal Address Book-based First Name/Last Name. So I opened Address Book (which had not been running), and it was empty!
To the best of my recollection, though I have a .Mac account, there was no syncing that occurred during any of this. Worse, when I did a manual Sync to see if .Mac would restore my contacts, it didn't. My Address Book remained empty. Fortunately, it didn't propagate its emptiness to .Mac, which I checked via the Web.
When I fired up my spare iBook, everything seemed fine, and a sync there didn't blow away anything.
I found a few posts that recommended replacing my now empty AddressBook.data file with AddressBook.data.beforesave, which was large enough to seem like it might still have a lot of my contacts. I did this, and my Address Book and Previous Recipients were partially restored. The only problem is that the beforesave file was dated June 2004 and is missing all contact information over the past year and a half.
What the heck happened?! Is there any better solution out there? Any thoughts on why .Mac wasn't able to restore the file? Also, what does Previous Recipients have to do with the Address Book data files?

Is your iBook the way you want it? all of your addresses? if so maybe you could back up that database and replace the old one thats fallen to pieces. If you try that though theres no real chance I think of rebuilding that old one as far as I know. My entouage database was an all in one type of deal. when it fell apart, you lost everything. I went to the mac mail and address book after that. everything is in seperate folders with that stuff. usually I've only seen this on older running installs of OS X. Like there is a bunch of directory probs. then things gradually get goofier over time.
Thats strange it doesn't want to import contacts to your computer.
I'll ask around

Report to be sent to a list of recipients in an e:mail (part of batch job)

Hi,
I need to generate a report using ALV functionality.
Currently my report requirement is to sent to a list of recipients in an e:mail (part of the batch job set-up) and the recipients just download the report in a spreadsheet format.
Could you please give me the suggestions the way which I need to follow and how I will be able to set this report as a part of batch job which will send the report details to the users in the form of Email.
Points will be rewarded for the answers.
Regards,
Ravi Ganji

Hi,
IN SM36..You will see a button for "Spool list recipient" which is next to the target server button..
press that button..
Give the email address in the recipient field..
GIve the steps and start condition and then release the job..
THanks,
Naren

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.

How can I create a slide show and insert it into an email

I created a slide show of some pictures I want to share with my sales associate but can't seem to figure out how to Email it. any help would be appreciated! Thank you!

You will need to export it as a QuickTime movie and share that.
That said, movies are big files and many recipients will be less than delighted to get large attachments that can cause them problems in their mailboxes. Better to upload the movie somewhere and then email them a link. Dropbox is an excellent way to do this.]
Regards
TD

'SO_DOCUMENT _SEND_AP1' and CC recipients

Similar Messages

Maybe you are looking for