Mail nots being sent because of SMTP?

Hey all I had to reset my Mail which caused my Server Ports to all go default. Does anybody know what the server port should be for the SMTP so that it will send mail out. Mine is set at 25 and I got help once with it and changed it and it fixed my problems. So if anybody knows of any server ports to try I would greatly appreciate it. Thanks again

Is this email account and SMTP server provided by your internet service provider or other?

Similar Messages

Email not being sent because recipient %@ rejected

IN the past 12 hours all my emails are going to my outbox and not being sent. The error message I am getting is " The Reciepient "%@" was rejected by the server because it does not allow relaying" How does one fix this

This problem has nothing to do with her hardware or the Mail application.
If a message cannot be successfully sent for whatever reason, it will remain in the Outbox mailbox and not be sent.
A message moved to the account's Sent mailbox indicates the message was successfully sent by the SMTP server used to send messages with the account but is no guarantee the message will be delivered to the recipient's incoming mail server or be accepted by the recipient's incoming mail server.
Generally, this type of problem is at the recipient's incoming mail server - the recipient's incoming mail server may be blocking all messages received from the domain for the sender's email account/address (the portion of the email address after the @ sign or blocking a range of IP addresses for which the sender is included, etc.
The next place to check is the provider for the sender's SMTP server used to send messages with this account which is usually the email account provider but not always.
My .Mac account is my primary email account but I use my ISP's SMTP server to send messages with my .Mac account when connected to the internet at home - not .Mac's SMTP server.

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.

Mail not being sent by phone

My iPhone is giving me a pop-up that says, "Cannot send mail" and says that "the sender address was invalid."
I've sent mail without problems with my iPhone for a year now and this just began to happen.
Whats up?
Jeremy

Hello all
I've had the same problems not being able to send (and sometimes receive) mail as well. I have three email accounts set up on my phone, and I noticed that one of the accounts worked, but not the other two. That tells me that it's not a defective iPhone as I first suspected. What I found out is that on the account that works, the SMTP Server Port Setting is set to 25. On the two accounts that weren't working, the Server Port was set to 587 and that's why I couldn't send out email. After changing the settings on both non-working email accounts, everything now works perfectly.
So, if you go to Settings>Mail, Contacts, Calendars>Accounts>Outgoing Mail Server SMTP>Primary Server>Server Port: 25
This worked for me. Hopefully it'll work for all of you here and anyone else with this problem.
Good Luck!
Warmest Regards,
Mike.

Mail not being sent

Every day this debacle gets worse, mail says its sending my mail but it isnt, sent box is empty, I sent email to myself at Yahoo address and guess what it never arrived. I sent quite a few and none got through. So I logged into me.com and checked my mail there. My mail box there was at least a month out of date. None of my test messages were showing and the messages showing I had deleted weeks ago. Good effort Apple.

Seems to be a perennial problem with Mail. I've posted this before, but it seems it may be needed again. Start at the top and work your way through the solutions. Hope it work...
There's been a lot of this around. I was composing a post on how to solve the problem of not sending out email, maybe to have it posted somewhere useful. It's not finished, but I'll paste it below. It's designed for the non-techie, so some of the advice is quite basic.
The Mail application seems to have bugs and be prone to corruptions after software updates have been installed. Being unable to send messages has crept up sporadically since January 2007, and a lot of people have offered advice - but it can take hours to trawl through. This is a distillation of some of that advice...
Some glitches can be solved by fiddling around with settings and preferences, some involve reinstalling Mail or switching to a new email software program.
If your email provider has a webmail service, log on to that and try sending a few messages. If they fail, contact your email provider. If they do get through, the problem is probably on your Mac, so it's time to start fiddling.
Before you do anything, close your Mail application and back up your Mail accounts and settings to a memory stick or CD.
To back up your messages and mailboxes:
Open a Finder window, click on the house icon which has the name of your computer or user name next to it. Then click Library, grab the folder called Mail and copy it to your memory stick.
To back up your Mail preferences (called a 'plist'): Look in Library for the folder called Preferences. To save the preferences of all applications, drag the whole folder to your memory stick. To back up just the Mail prefs, open the folder and copy the file named com.apple.mail.plist.
Eject your memory stick and then open the Mail program.
Start fiddling.
In Mail, select the menu Window, then Activity viewer. Now under the same menu, run Connection Doctor. Note down the results. Quit Mail.
Mail could go wrong because of problems glitches in other parts of the computer's software. The reason is that Macs seem to be programmed to repair themselves in the middle of the night and some diagnostic routines only run every few days and weeks, so you can't second guess when they are going to happen. So if you save the planet by turning off rather than leave the computer in sleep mode, the computer will never self-diagnose and repair itself. Try downloading a small free/shareware program that tells the computer to diagnose and repair when you power up. It doesn't slow you down and just adds a few clicks and whirs your first few minutes of computer use. I use Anacron, for no better reason than it was the first one I came across. The download page is at http://members.cox.net/18james/anacron.html, but I'm sure there are others available.
But to diagnose and repair immediately, go to your Utilities folder (it is in the Applications folder, or in Finder select the Go menu and click Utilities from near the bottom). Select Disc Utility. When that opens, select your hard disc in the left hand pane. Run Verify Disk Permissions. Then Repair Disk Permissions. Then Verify Disk and Repair Disk (you may have to start up using your Mac installation disk to do it). Open Mail.
Plain text
Try sending a message again. If it fails, delete it and compose a new message, then send it as plain text (look under the Format menu, fifth item down). Send message. If it works, you may have to reinstall Mail to get back the ability to send messages formatted as rich text.
Server settings
Open your Mail preferences and select the Server Settings in the Outgoing Mail Server pane. Write down the settings as you see them, or use the screen grab shortcut (use apple+tab to select Finder, then hold down apple+shift and press the number 3 to take a screen-shot, which will be saved to your desktop, then tab back to the Mail program). Then fiddle as follows...
Ports
Some internet service providers (ISPs) change the ports through which they will accept messages - and don't tell the users. Phone them up and ask if they've changed the server settings, and of they're blocking messages from certain ports. If no joy, try changing the port setting to one of the following, then quit and restart Mail before trying to send a message. Note, some of the ports may require you to tick the Use SSL box, some don't - so experiment. Possible ports: 25, 465, 587, 992, 995 (SSL).
Password authentication
Sometime passwords get corrupted, so you need to fiddle with it. Even if your ISP doen't require a password, turn on password and input the log on name and password your internet service provider gave you (possible those used for your POP settings). Mail will ask you for your password when you send a mesage. Enter the password but don't add to keychain. Do this for a while (hours, days - the option depends on success rate, not sure why) then turn off the password authentication. This removes the corrution and resets the preferences - so again save the Mail plist to memory stick (use a new location rather than over-writing the old plist).
Certificates
You may also get a message saying there is a certificate problem with your email connection. So solve this, open Mail's preferences and to Advanced. If the box Use SSL is checked, the por tnumber is anything other than 110, and the Authentication is set to anything other than Password, try this: Uncheck Use SSL. The port number should revert to 110 - if not, change it manually. Change Authentication to Password. Close and save preferences, quit Mail, restart Mail, send a message.
That's as far as I've got.

Campaign e-mails not being sent

Hi,
I am having a problem sending out e-mails from a Contacts List. The campaign report shows that all e-mails have been sent eg 5 when there are 5 contacts in the list. However the e-mails are not actually delivered. Strangely when I send a one off e-mail using the Send one copy to: function the e-mail is delivered. Are these methods using different services?
We are on SP1 Patch 1 and SAP B1 2007A patch 46
Can anyone help?
Regards Martin

We do have almost similar problem. This is on SQL 2008.
when sending a Marketing Campaign with contact list type Emailing List, the emails in the log file
of the campaign show as sent, but in reality no emails are received.
We have configuted the SMTP(from Config Settings), the port is open. We used different email servers
for a test, and none of them were able to solve the issue. All setup has been done according to
documentation. The DSN is configured as well.
As soon as we send the campaign, the email posts as send, the number of emails on the top of the
Campaign Screen on the Assign tab shows one email, and on the bottom is the time and date stamp of
sent emails. However, the Campaign REPORT shows no Sent messages and we have not received an email.
The client is using Microsoft Exchange with an outside provider.
Can someone helpout. We tried all the necessary steps can anyone help out on this issue.
Thanks.
Maddy

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..

E-mails NOT being sent by me!

Two e-mails have been sent out apparently by me (but not actually by me) recently to all in my address book. They are telling people to click on a link contained in the message (both different) links.
Could somebody tell me how I can stop this please? This seems to be spam in reverse!
Regards
Kathy

kathypink wrote:
Two e-mails have been sent out apparently by me (but not actually by me) recently to all in my address book. They are telling people to click on a link contained in the message (both different) links.
Could somebody tell me how I can stop this please? This seems to be spam in reverse!
Regards
Kathy
Hi Kathy. Welcome to the forums.
Please can you go a alter the password for your account - my shortcuts option 3, or via option 12a takes you there.
Whilst you are in webmail, go to Options/Mail (or More) Options and click on POP & Forwarding, to make sure that nothing has been set to forward the BTYahoo! Mail.
It sounds like someone (a hacker) has managed to get the password to your account, hopefully you've not fallen for a phishing scam - where an email pretending to be from BT may have requested you to enter username/password.
http://www.andyweb.co.uk/shortcuts
http://www.andyweb.co.uk/pictures

Mail not being sent for a background job scheduled.

Hello all,
We have a report which is scheduled in background. The job runs for every 10 mins in development server and sends the status to various mail IDs. The job runs successfully and the status shows as 'FINISHED'. But users are not able to recieve the mail.
Mails are sent using the FM "SO_DOCUMENT_SEND_API1".
When the debug the report everything works fine and the user recieved the mail. Any pointers to this would be of great help.
I tried searching in SDN for existing posts but could not find any relevant thread.
Thanks in advance.
Regards,
Chandra.

Hello,
PFB piece of code showing how the FM is called.
CALL FUNCTION 'SO_DOCUMENT_SEND_API1'
         EXPORTING
              document_data       = wa_doc
              sender_address      = wf_sender
              sender_address_type = 'SMTP'
         TABLES
              packing_list        = it_paklist
              object_header    = it_obj_head
              contents_bin      = it_obj_bin
              contents_txt      = it_obj_txt
              receivers          = it_obj_rcv.
Also , please note that this report has been scheduled some time in last year i.e. 2008 and it was running successfully by sending mails. But from past 2 months the report is not sending mails.
Regards,
Chandra
Edited by: Chandra A on Sep 7, 2009 2:17 PM
Edited by: Chandra A on Sep 7, 2009 2:17 PM

E-Mails Not Being Sent

I have a process where users can click on a button that
should automatically generate an HTML file, attach it to an e-mail,
e-mail the customer with the attachment, and clear an alert.
Most of the time this works smoothly, but every so often the
e-mail won't get sent. The alert will be cleared, but no email.
It's not the same customer, just very random.
I am using CF 4.5, I don't know if that matters, but it
might. Does anyone know why this would be happening?
Thanks!

So this morning the hoopla really hit the fan.
All those missing e-mail were sent out at 3pm yesterday from
one of our servers. The server that didn't have the mailsent.log
file. All of a sudden it has the mailsent.log file.
It looks like a whole lot of this:
"Information","TID=1420","09/16/07","15:10:48","[email protected],j-johnston@suddenlin kmail.com"
"Information","TID=1420","09/16/07","15:10:48","[email protected],[email protected] "
"Information","TID=1420","09/16/07","15:10:48","[email protected],[email protected] "
"Information","TID=1420","09/16/07","15:10:48","[email protected],[email protected] "
"Information","TID=1420","09/16/07","15:10:48","[email protected],[email protected] m"
"Information","TID=1420","09/16/07","15:10:48","[email protected],[email protected] m"
"Information","TID=1420","09/17/07","08:08:30","[email protected],[email protected]"
And then in the mail.log file are some e-mail that didn't get
sent, it looks like this:
"Error","TID=1420","09/16/07","15:08:23","Failed to send the
spooled mail file, C:\CFUSION\MAIL\spool\AB4.cfmail. SMTP server
replied "Message is not RFC compliant" Moved file to
C:\CFUSION\MAIL\undelivr\10B1.cfmail."
"Error","TID=1420","09/16/07","15:08:23","Failed to send the
spooled mail file, C:\CFUSION\MAIL\spool\ABB.cfmail. SMTP server
replied "Message is not RFC compliant" Moved file to
C:\CFUSION\MAIL\undelivr\10B2.cfmail."
"Error","TID=1420","09/16/07","15:08:23","Failed to send the
spooled mail file, C:\CFUSION\MAIL\spool\AC2.cfmail. SMTP server
replied "Message is not RFC compliant" Moved file to
C:\CFUSION\MAIL\undelivr\10B3.cfmail."
"Error","TID=1420","09/16/07","15:08:24","Failed to send the
spooled mail file, C:\CFUSION\MAIL\spool\BBC.cfmail. SMTP server
replied "What? I don't understand that." Moved file to
C:\CFUSION\MAIL\undelivr\10B4.cfmail."
"Error","TID=1420","09/16/07","15:08:25","Failed to send the
spooled mail file, C:\CFUSION\MAIL\spool\BCA.cfmail. SMTP server
replied "Communication failure with mail server." Moved file to
C:\CFUSION\MAIL\undelivr\10B5.cfmail."
"Error","TID=1420","09/16/07","15:08:26","Failed to send the
spooled mail file, C:\CFUSION\MAIL\spool\C53.cfmail. SMTP server
replied "Communication failure with mail server." Moved file to
C:\CFUSION\MAIL\undelivr\10B6.cfmail."
"Error","TID=1420","09/16/07","15:08:27","Failed to send the
spooled mail file, C:\CFUSION\MAIL\spool\C5E.cfmail. SMTP server
replied "Communication failure with mail server." Moved file to
C:\CFUSION\MAIL\undelivr\10B7.cfmail."
And it gets better. When I look in the UNDELIVR folder, those
messages, that couldn't be sent at 3pm yesterday when all the other
ones were sent, have a modified date the same as the date they were
originally supposed to be sent out on. All the e-mails that were
supposed to be sent out last week and were finally sent out
yesterday have this same attribute.
Does anyone know what's going on?!
Thanks!

IPad 2, mails not being sent when using reply to all feature

Hi,
Under BYOD we have iPads being allowed in our office environment. We have Lotus Notes Traveler servers setup for email access.
We are facing an issue with one executive users iPad 2 in the mail app.
The issue is when user is on WIFI and uses a long signature in the iPad and does a "reply to all" to any mail the mail goes and stays in the outbox.
Single reply or composing a new mail works fine. If we remove long signature, then "reply to all" works fine.
This issue is only with Wi-Fi, on GPRS everything works fine with long signature or without.
The iPad is on iOs 6, we tried resetting and restoring the iPad but the issue still persists.
Would really appreciate if you all could help me solve his issue.'
Thanks

iOS: Unable to send or receive email
http://support.apple.com/kb/TS3899
Can’t Send Emails on iPad – Troubleshooting Steps
http://ipadhelp.com/ipad-help/ipad-cant-send-emails-troubleshooting-steps/
iPad Mail
http://www.apple.com/support/ipad/mail/
Try this: Delete the account in Mail and then set it up again.
 Cheers, Tom

Why is my e-mails not being sent or received?

Where are my e-mails?

Hi!
Most people have their email service provided a large company like Google (Gmail), Yahoo, Microsoft (Hotmail or Outlook) or similar.
Do you know which company provides your email service?
If not, could you please tell us the end portion of your email address (just the part from the @ symbol onwards).
Thanks!

Outgoing mail not being sent

when replying or sending a new mail, the outgoing sits there an doesn't go out

dubwhitt,
I am going to assume you're using Apple's mail client as it's on version 4 in Snow Leopard. The easiest thing I can point you to, is Apple's own site to give you a step-by-step walkthrough for trouble shooting those email addresses.
1. Go to this link http://www.apple.com/support/macosx/mailassistant/
2. Selecting Mac OS X Snow Leopard
3. Enter one of the email addresses that isn't working. I believe your gmail account is one of them.
4. Click continue on the bottom.
5. Follow the instructions Apple provides, then select the third option "I want to verify settings on an existing account"
6. Follow Apple’s instructions again.
See if this solves any issues.

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.

Batch Process mail notifications not being sent

Racking my brain on this. On our prod 9.3.1 server, we reconfigured the mail server/database. I logged in as the application owner to establish the mail in application settings. Under workspace/administer/notifications I am able to successfully send a test email.
The emails are not being sent for any of our workspace reporting batch processes. What log would be associated with this for further review?
JTS

FR_GLOBAL_PROPERTIES didn't have the smtp server populated..once populated and then the scheduler service restarted the emails are working..
JTS

Mail nots being sent because of SMTP?

Similar Messages

Maybe you are looking for