Mail delivery receipt
Is there a way to generate an automatic receipt to your mailbox when a sent message has been received?
It seems there used to be an easy way to do this, but maybe I'm thinking of using Outlook at work.
I've checked the Mail "Help", but we all know how "helpful" Apple's "Help" is.
Outlook, and its descendents, will do that but Mail will not. Unless you are using a mail provider that has that capability you cannot get it from Apple's Mail application itself.
Similar Messages
-
E-mail Delivery receipts cannt be received.
Hi All,
I have a small query regarding JavaMail. I cannot receive e-mail delivery receipts. I have set the property Return-Receipt-To to the header of the email. Please find the email header of the email bellow. What can be the problem? I checked my mail server, It sends delivery receipts to the mail sent thought mail clients (outlook)
Further , I have set read-receipts for the mail. I works fine :). Please help me to solve this.
Microsoft Mail Internet Headers Version 2.0
Received: from ms-mailsvr.****.com ([10.5.69.15]) by cs-mailsvr04.*****.com with Microsoft SMTPSVC(6.0.3790.3959);
Thu, 18 Jun 2009 18:50:35 +0530
Received: from MTMISTEAM.tipptase.com ([10.5.69.35]) by ms-mailsvr.****.com with Microsoft SMTPSVC(6.0.3790.3959);
Thu, 18 Jun 2009 18:50:32 +0530
X-TM-IMSS-Message-ID:<[email protected]>
Received: from ****.****.com (****.*****.com [*.*.*.*]) by mtmisteam.tipptase.com ([******]) with ESMTP (TREND IMSS SMTP Service 7.0) id 7ce60b9700006581 ; Thu, 18 Jun 2009 18:43:50 +0530
Message-ID: <22869314.1245330204034.JavaMail.root@***.*****.com>
Date: Thu, 18 Jun 2009 18:33:24 +0530 (IST)
From: mymail@*****.com
To: rcvrmail@****.com
Subject: FAQ: Submit a new question
Mime-Version: 1.0
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: 7bit
Disposition-Notification-To: mymail@*****.com
Return-Receipt-To: mymail@*****.com
X-TM-AS-Product-Ver: IMSS-7.0.0.6298-5.6.0.1016-16710.007
X-TM-AS-Result: No--15.865-5.0-31-1
X-imss-scan-details: No--15.865-5.0-31-1
X-TM-AS-User-Blocked-Sender: No
Return-Path: mymail@*****.com
X-OriginalArrivalTime: 18 Jun 2009 13:20:32.0460 (UTC) FILETIME=[8EA100C0:01C9F017]I tried with the options you have provided in the SMTPMessage class. But still i cannot receive the delivery status notifications.
I can get the read recipt. The Destination server is configured properly. Is there a technical limitation? I tried to use javax.mail.internet.MimeMessage too. it does not work properly too.
If this is a technical limitation or any other issue can you please give me a reference for that :) ? -
Delivery Receipt After Sending Mail Using JavaMail ?
Hi Friends,
I have written an application using JavaMail which would be used to send mail
using my organisation's SMTP Server.I would like to include the following functionality in it.Just as
Microsoft's Outlook has an option to get Delivery Receipt of the mail and Read Receipt of the mail sent
(Provided the email Client supports it) i would like to have a similar option in my application to.I would like to of how i can do it using JavaMail.I heard that basically we need to set some SMTP properties which the Mail Transfer Agent would recognize and send us the Delivery and Read Receipts.But,i am not sure of what those properties.Can anyone help me regarding this ?You might look into creating a custom header that provides a return reciept to the email address you specify. I'm not 100% sure that all mail servers support this but you might want to look into it as a solution.
-Dave -
How can I receive email delivery receipts or read receipts on Mail, OS X?
How can I receive email delivery receipts or read receipts on Mail, OS X?
Thanks!See here: http://email.about.com/od/macosxmailtips/qt/et_request_recp.htm
Not sure if it works in Mountain Lion.
Note that those only work if your recipients have allowed it to happen.
Also, Mail will not respond to them at all. -
Is there a way to receive delivery receipts for email sent from iphone IOS8.1
Had a couple of cases when emails haven't arrived for some reason so would be good to get a message to say it's been delivered OK
CheersThat would depend on using a mail service that offers it, as well as an app that supports it. In many cases, even though your service may support it, the recipient's may not. For what its worth, Microsoft's OWA app doesn't even support it (even though it is a function of Exchange Mail Services).
And frankly, most recipients find it - at best - an annoyance. -
How do i enable read or delivery receipt for Mail?
how do i enable read or delivery receipt for Mail?
I entered this code into terminal replacing "your name" with my email address:
defaults write com.apple.mail UserHeaders '{"Return-Receipt-To" = "[email protected]"; "Disposition-Notification-To" = "[email protected]"; }'
I've read it worked for some, but I could not get it to work. Does Mail automatically override this? -
HT5361 Can I use send and delivery receipts when composing mail?
Does anyone know if I can ask for read receipts and delivery receipts when composing mail?
Additionally (to BobtheFisherman):
And his suggested method will work just as well as any send/read receipt since many recipients will not allow such a receipt be sent. If it is important enough to require a receipt, send it via USPS return receipt requested, or FedEx, etc. -
Witch plug-in for mail delivery recipient
Hello,
does enyone know witch plug-in, delivery recipient, i have to download for "mail"? I'm looking for it on www.pure-mac.com and www.hawkwings.net/plugins, but i don't know what to look for to get a delivery recipient when i send an email...
thxWelcome to the discussions, goliat.
It is, I think, a plug-in to add a delivery receipt request to your emails that you are looking for. (A recipient is a person who receives Try Hawk Wings » Blog Archive » AppleScript for Return Receipts
AK -
My account sending SPAM e-mails but i can't find it in sent folder, i receive only undelivered message response for messages which i didn't send and problem is not on provider server i checked it out.
Examples of server response:
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
[email protected]
SMTP error from remote mail server after end of data:
host mx1.optonline.net [167.206.4.77]: 554 5.7.1 Spam detected by Cloudmark content scanner. Message rejected.
------ This is a copy of the message, including all the headers. ------
Return-path: <[email protected]>
Received: from [181.64.16.205] (helo=kiwqdljpf)
by smtp2.neobee.net with esmtpa (Exim 4.74)
(envelope-from <[email protected]>)
id 1WPiCY-0004IY-2G
for [email protected]; Tue, 18 Mar 2014 01:48:20 +0100
Subject: FirmViagra
Date: Mon, 17 Mar 2014 18:41:36 -0700
To: <[email protected]>
From: "Sleb Icap" <[email protected]>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-7
X-Spam-Score: 1.2 (+)
X-Scan-Signature: 05e778587fdac215ad5fe7047e8f78ed
http://holzstark.at/opportune.htm?la
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
[email protected]
SMTP error from remote mail server after RCPT TO:<[email protected]>:
host mx.coxmail.com [68.99.120.4]: 550 5.1.1 <[email protected]> recipient rejected
------ This is a copy of the message, including all the headers. ------
Return-path: <[email protected]>
Received: from [181.64.16.205] (helo=kiwqdljpf)
by smtp2.neobee.net with esmtpa (Exim 4.74)
(envelope-from <[email protected]>)
id 1WPiCk-0004IY-B6
for [email protected]; Tue, 18 Mar 2014 01:48:32 +0100
Subject: SweetDrugs
Date: Mon, 17 Mar 2014 18:41:48 -0700
To: <[email protected]>
From: [email protected]
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
X-Spam-Score: 2.3 (++)
X-Scan-Signature: 05e778587fdac215ad5fe7047e8f78ed
http://selapak-cambodia.com/chic.html?zogyzeno
My configuration of Thunderbird is:
Application Basics
Name Thunderbird
Version 24.3.0
User Agent Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
Profile Folder
Show Folder
(Local drive)
Application Build ID 20140131124303
Enabled Plugins about:plugins
Build Configuration about:buildconfig
Crash Reports about:crashes
Memory Use about:memory
Mail and News Accounts
ID Incoming server Outgoing servers
Name Connection security Authentication method Name Connection security Authentication method Default?
account1 (pop3) pop3.neobee.net:110 plain passwordCleartext smtp.neobee.net:25 alwaysSTARTTLS passwordCleartext true
account2 (none) Local Folders plain passwordCleartext
account3 (pop3) pop.mail.yahoo.com:995 SSL passwordCleartext smtp.mail.yahoo.com:465 SSL passwordCleartext true
account4 (pop3) pop.mail.yahoo.com:995 SSL passwordCleartext smtp.mail.yahoo.com:465 SSL passwordCleartext true
account5 (pop3) pop.mail.yahoo.com:995 SSL passwordCleartext smtp.mail.yahoo.com:465 SSL passwordCleartext true
Extensions
Name Version Enabled ID
Test Pilot for Thunderbird 1.3.9 false [email protected]
Important Modified Preferences
Name Value
browser.cache.disk.capacity 358400
browser.cache.disk.smart_size.first_run false
browser.cache.disk.smart_size.use_old_max false
browser.cache.disk.smart_size_cached_value 358400
dom.max_chrome_script_run_time 0
extensions.lastAppVersion 24.3.0
font.internaluseonly.changed true
font.name.monospace.el Consolas
font.name.monospace.tr Consolas
font.name.monospace.x-baltic Consolas
font.name.monospace.x-central-euro Consolas
font.name.monospace.x-cyrillic Consolas
font.name.monospace.x-unicode Consolas
font.name.monospace.x-western Consolas
font.name.sans-serif.el Calibri
font.name.sans-serif.tr Calibri
font.name.sans-serif.x-baltic Calibri
font.name.sans-serif.x-central-euro Calibri
font.name.sans-serif.x-cyrillic Calibri
font.name.sans-serif.x-unicode Calibri
font.name.sans-serif.x-western Calibri
font.name.serif.el Cambria
font.name.serif.tr Cambria
font.name.serif.x-baltic Cambria
font.name.serif.x-central-euro Cambria
font.name.serif.x-cyrillic Cambria
font.name.serif.x-unicode Cambria
font.name.serif.x-western Cambria
font.size.fixed.el 14
font.size.fixed.tr 14
font.size.fixed.x-baltic 14
font.size.fixed.x-central-euro 14
font.size.fixed.x-cyrillic 14
font.size.fixed.x-unicode 14
font.size.fixed.x-western 14
font.size.variable.el 17
font.size.variable.tr 17
font.size.variable.x-baltic 17
font.size.variable.x-central-euro 17
font.size.variable.x-cyrillic 17
font.size.variable.x-unicode 17
font.size.variable.x-western 17
mail.openMessageBehavior.version 1
mail.winsearch.firstRunDone true
mailnews.database.global.datastore.id d3f7cbbc-ff7c-49f8-8265-081ff16f23e
network.cookie.prefsMigrated true
places.database.lastMaintenance 1394703331
places.history.expiration.transient_current_max_pages 104858
plugin.importedState true
plugin.state.flash 0
plugin.state.java 0
plugin.state.npauthz 0
plugin.state.npbrowserplugin 0
plugin.state.npctrl 0
plugin.state.npdeployjava 0
plugin.state.npgeplugin 0
plugin.state.npgoogleupdate 0
plugin.state.npnokiasuiteenabler 0
plugin.state.nppdf 0
plugin.state.npspwrap 0
plugin.state.npvlc 0
security.default_personal_cert Select Automatically
security.disable_button.openCertManager false
security.disable_button.openDeviceManager false
security.OCSP.require true
Graphics
Adapter Description Intel(R) HD Graphics Family
Vendor ID 0x8086
Device ID 0x0116
Adapter RAM Unknown
Adapter Drivers igdumd64 igd10umd64 igd10umd64 igdumdx32 igd10umd32 igd10umd32
Driver Version 8.15.10.2462
Driver Date 7-26-2011
Adapter Description (GPU #2) NVIDIA GeForce GT 630M
Vendor ID (GPU #2) 0x10de
Device ID (GPU #2) 0x0de9
Adapter RAM (GPU #2) 2048
Adapter Drivers (GPU #2) nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
Driver Version (GPU #2) 9.18.13.3165
Driver Date (GPU #2) 10-23-2013
Direct2D Enabled false
DirectWrite Enabled false (6.2.9200.16571)
ClearType Parameters ClearType parameters not found
WebGL Renderer false
GPU Accelerated Windows 0
AzureCanvasBackend skia
AzureFallbackCanvasBackend cairo
AzureContentBackend none
JavaScript
Incremental GC 1
Accessibility
Activated 0
Prevent Accessibility 0
Library Versions
Expected minimum version Version in use
NSPR 4.10.2 4.10.2
NSS 3.15.4 Basic ECC 3.15.4 Basic ECC
NSS Util 3.15.4 3.15.4
NSS SSL 3.15.4 Basic ECC 3.15.4 Basic ECC
NSS S/MIME 3.15.4 Basic ECC 3.15.4 Basic ECC
Please help me to solve this problem.By the way, some non-delivery receipts (NDRs) are themselves spam messages with malicious attachments designed to infect your computer, so be cautious about opening any of those.
-
Email read and delivery receipt
Hi,
I an sending a mail from SAP to the employees outlook and the sender is the common mail box which is entered on selction screen.
Our requirement is that the common email box should recieve read and delivery receipt for the mail.
Please tell me how to do it.
I am uisng the following code to send the mail.
DATA : lt_att_content_hex TYPE solix_tab,
lv_subject TYPE so_obj_des,
lv_async TYPE c,
" lx_email TYPE type_email,
lv_email TYPE adr6-smtp_addr.
DATA: lx_document_bcs TYPE REF TO cx_document_bcs VALUE IS INITIAL.
CLASS cl_bcs DEFINITION LOAD.
DATA: lo_send_request TYPE REF TO cl_bcs VALUE IS INITIAL.
Message body and subject
DATA: lt_message_body TYPE bcsy_text VALUE IS INITIAL,
lo_document TYPE REF TO cl_document_bcs VALUE IS INITIAL.
Create recipient
DATA: lo_recipient TYPE REF TO if_recipient_bcs VALUE IS INITIAL.
lo_send_request = cl_bcs=>create_persistent( ).
TRY.
lo_send_request->asynchronous(
RECEIVING
result = lv_async ).
CATCH cx_send_req_bcs .
ENDTRY.
CALL FUNCTION 'SCMS_XSTRING_TO_BINARY'
EXPORTING
buffer = pdf_xstring "PDF file from function module
TABLES
binary_tab = lt_att_content_hex.
CONCATENATE ': ' pn-begda+0(4) 'Benefit. Statement' INTO lv_subject
SEPARATED BY space.
DATA: lx_string TYPE string.
Message Body
APPEND ' Body' to lt_message_body.
lo_document = cl_document_bcs=>create_document( i_type = 'HTM'
i_text = lt_message_body
i_subject = lv_subject ).
TRY.
lo_document->add_attachment(
EXPORTING
i_attachment_type = 'PDF'
i_attachment_subject = lv_subject
i_att_content_hex = lt_att_content_hex ).
CATCH cx_document_bcs INTO lx_document_bcs.
ENDTRY.
Add attachment
Pass the document to send request
lo_send_request->set_document( lo_document ).
lo_recipient = cl_cam_address_bcs=>create_internet_address( 'XYZ@XYZ' ).
Set recipient
lo_send_request->add_recipient(
EXPORTING
i_recipient = lo_recipient
i_express = 'X' ).
lo_send_request->add_recipient(
EXPORTING
i_recipient = lo_recipient
i_express = 'X' ).
Create sender
DATA: lo_sender TYPE REF TO if_sender_bcs VALUE IS INITIAL,
l_send TYPE adr6-smtp_addr.
l_send = p_email.
lo_sender = cl_cam_address_bcs=>create_internet_address( l_send ).
Set sender
lo_send_request->set_sender(
EXPORTING
i_sender = lo_sender ).
TRY.
lo_send_request->set_status_attributes(
EXPORTING
i_requested_status = 'A'
i_status_mail = 'A' )
CATCH cx_send_req_bcs .
ENDTRY.
Send email
DATA: lv_sent_to_all(1) TYPE c VALUE IS INITIAL.
lo_send_request->send(
EXPORTING
i_with_error_screen = 'X'
RECEIVING
result = lv_sent_to_all ).
COMMIT WORK.
MESSAGE 'The form has been emailed to the Manager' TYPE 'S'.
CLEAR lt_message_bodyHi,
For reciepts to work the basis setting needs to be activated.
SCOT->Settings->Confirmation of Receipts -
Cannot turn off delivery receipts.
I turned on delivery receipts, accomplished my purpose, but cannot get them turned off. I unchecked the appropriate box Options/Mail/Tracking
to no avail. I am using Outlook 365 through a Exchange Server 2007 account.Hi,
"I am using Outlook 365 through an Exchange Server 2007 account." Could you please explain it furthermore?
If you don't want to receive these read receipts, you can create a transport rule to delete them. Here is the transport rule for your reference:
Apply this rule if the message type is Read receipt.
Do the following...Delete the message without notifying the recipient or sender.
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support -
Mail delivery fail but still received mail
hi
i keep receiving 2 messages straight after receipt of the original which is readable..
1st message: mail delivery fail
2nd message: undeliverable
i have no problem reading the original message
regards
kelThis is a problem with your recipients ISP not delivering the email, or with Comcast in not sending it once it reaches their mail servers. You should check with your recipients to find out if they use the same ISP, and have them check with the ISP to ask why mail sent from a Comcast account is not being delivered.
If this affects all your recipients (assuming there are many more than just the two you mentioned), then its a Comcast issue and you should call them and insist they make any necessary changes so everyone can receive email from you. If it only affects those two recipients, they would need to call their ISP and have them make the necessary changes. -
[Solved] postfix local mail delivery fails
Hi Guys,
on my home pc i use postfix (gmail as a smtp relay) and fetchmail for sending/receiving mails, this works very well, however sending a mail to a local user fails, I'm lost here and need your help guys.
if i send a mail like :
$>echo "Test" | mail -s "Test : local mail delivery" "andy"
The mail stays in the queue for ever...
$>mailq
-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
CC82513BCA* 455 Sun Aug 3 09:53:09 [email protected]
[email protected]
Sending to external addresses works without any problems.
Here some important info/config files :
$>whoami
andy
$>hostname
box
$>cat /etc/host.conf
# /etc/hosts
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost box
::1 localhost.localdomain localhost
192.168.1.3 lbox.localdomain lbox
$>cat /etc/postfix/main.cf
# Global Postfix configuration file. This file lists only a subset
# of all parameters. For the syntax, and for a complete parameter
# list, see the postconf(5) manual page (command: "man 5 postconf").
# For common configuration examples, see BASIC_CONFIGURATION_README
# and STANDARD_CONFIGURATION_README. To find these documents, use
# the command "postconf html_directory readme_directory", or go to
# http://www.postfix.org/.
# For best results, change no more than 2-3 parameters at a time,
# and test if Postfix still works after every change.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
#soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/bin
# 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/lib/postfix
# The data_directory parameter specifies the location of Postfix-writable
# data files (caches, random numbers). This directory must be owned
# by the mail_owner account (see below).
data_directory = /var/lib/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
#myhostname = mail.example.com
myhostname = localhost.localdomain
# 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
mydomain = localdomain
# 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
inet_interfaces = 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
#mydestination = localhost, localhost.localdomain
# 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 $pr/oxy_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]
relayhost = [smtp.gmail.com]
# 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
alias_maps = hash:/etc/postfix/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
alias_database = $alias_maps
# ADDRESS EXTENSIONS (e.g., user+foo)
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5) for the effects this has on
# aliases, canonical, virtual, relocated and .forward file lookups.
# Basically, the software tries user+foo and .forward+foo before
# trying user and .forward.
#recipient_delimiter = +
# DELIVERY TO MAILBOX
# The home_mailbox parameter specifies the optional pathname of a
# mailbox file relative to a user's home directory. The default
# mailbox file is /var/spool/mail/user or /var/mail/user. Specify
# "Maildir/" for qmail-style delivery (the / is required).
#home_mailbox = Mailbox
#home_mailbox = Maildir/
# The mail_spool_directory parameter specifies the directory where
# UNIX-style mailboxes are kept. The default setting depends on the
# system type.
#mail_spool_directory = /var/mail
mail_spool_directory = /var/spool/mail
# The mailbox_command parameter specifies the optional external
# command to use instead of mailbox delivery. The command is run as
# the recipient with proper HOME, SHELL and LOGNAME environment settings.
# Exception: delivery for root is done as $default_user.
# Other environment variables of interest: USER (recipient username),
# EXTENSION (address extension), DOMAIN (domain part of address),
# and LOCAL (the address localpart).
# Unlike other Postfix configuration parameters, the mailbox_command
# parameter is not subjected to $parameter substitutions. This is to
# make it easier to specify shell syntax (see example below).
# Avoid shell meta characters because they will force Postfix to run
# an expensive shell process. Procmail alone is expensive enough.
# IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
# ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
#mailbox_command = /some/where/procmail
#mailbox_command = /some/where/procmail -a "$EXTENSION"
mailbox_command = /usr/bin/procmail
# The mailbox_transport specifies the optional transport in master.cf
# to use after processing aliases and .forward files. This parameter
# has precedence over the mailbox_command, fallback_transport and
# luser_relay parameters.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
# Cyrus IMAP over LMTP. Specify ``lmtpunix cmd="lmtpd"
# listen="/var/imap/socket/lmtp" prefork=0'' in cyrus.conf.
#mailbox_transport = lmtp:unix:/var/imap/socket/lmtp
# Cyrus IMAP via command line. Uncomment the "cyrus...pipe" and
# subsequent line in master.cf.
#mailbox_transport = cyrus
# The fallback_transport specifies the optional transport in master.cf
# to use for recipients that are not found in the UNIX passwd database.
# This parameter has precedence over the luser_relay parameter.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#fallback_transport = lmtp:unix:/file/name
#fallback_transport = cyrus
#fallback_transport =
# The luser_relay parameter specifies an optional destination address
# for unknown recipients. By default, mail for unknown@$mydestination,
# unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned
# as undeliverable.
# The following expansions are done on luser_relay: $user (recipient
# username), $shell (recipient shell), $home (recipient home directory),
# $recipient (full recipient address), $extension (recipient address
# extension), $domain (recipient domain), $local (entire recipient
# localpart), $recipient_delimiter. Specify ${name?value} or
# ${name:value} to expand value only when $name does (does not) exist.
# luser_relay works only for the default Postfix local delivery agent.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must specify "local_recipient_maps =" (i.e. empty) in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#luser_relay = [email protected]
#luser_relay = [email protected]
#luser_relay = admin+$local
# JUNK MAIL CONTROLS
# The controls listed here are only a very small subset. The file
# SMTPD_ACCESS_README provides an overview.
# The header_checks parameter specifies an optional table with patterns
# that each logical message header is matched against, including
# headers that span multiple physical lines.
# By default, these patterns also apply to MIME headers and to the
# headers of attached messages. With older Postfix versions, MIME and
# attached message headers were treated as body text.
# For details, see "man header_checks".
#header_checks = regexp:/etc/postfix/header_checks
# FAST ETRN SERVICE
# Postfix maintains per-destination logfiles with information about
# deferred mail, so that mail can be flushed quickly with the SMTP
# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
# See the ETRN_README document for a detailed description.
# The fast_flush_domains parameter controls what destinations are
# eligible for this service. By default, they are all domains that
# this server is willing to relay mail to.
#fast_flush_domains = $relay_domains
# SHOW SOFTWARE VERSION OR NOT
# The smtpd_banner parameter specifies the text that follows the 220
# code in the SMTP server's greeting banner. Some people like to see
# the mail version advertised. By default, Postfix shows no version.
# You MUST specify $myhostname at the start of the text. That is an
# RFC requirement. Postfix itself does not care.
#smtpd_banner = $myhostname ESMTP $mail_name
#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
# PARALLEL DELIVERY TO THE SAME DESTINATION
# How many parallel deliveries to the same user or domain? With local
# delivery, it does not make sense to do massively parallel delivery
# to the same user, because mailbox updates must happen sequentially,
# and expensive pipelines in .forward files can cause disasters when
# too many are run at the same time. With SMTP deliveries, 10
# simultaneous connections to the same domain could be sufficient to
# raise eyebrows.
# Each message delivery transport has its XXX_destination_concurrency_limit
# parameter. The default is $default_destination_concurrency_limit for
# most delivery transports. For the local delivery agent the default is 2.
#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 20
# DEBUGGING CONTROL
# The debug_peer_level parameter specifies the increment in verbose
# logging level when an SMTP client or server host name or address
# matches a pattern in the debug_peer_list parameter.
debug_peer_level = 2
# The debug_peer_list parameter specifies an optional list of domain
# or network patterns, /file/name patterns or type:name tables. When
# an SMTP client or server host name or address matches a pattern,
# increase the verbose logging level by the amount specified in the
# debug_peer_level parameter.
#debug_peer_list = 127.0.0.1
#debug_peer_list = some.domain
# The debugger_command specifies the external command that is executed
# when a Postfix daemon program is run with the -D option.
# Use "command .. & sleep 5" so that the debugger can attach before
# the process marches on. If you use an X-based debugger, be sure to
# set up your XAUTHORITY environment variable before starting Postfix.
debugger_command =
PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
ddd $daemon_directory/$process_name $process_id & sleep 5
# If you can't use X, use this to capture the call stack when a
# daemon crashes. The result is in a file in the configuration
# directory, and is named after the process name and the process ID.
# debugger_command =
# PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
# echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
# >$config_directory/$process_name.$process_id.log & sleep 5
# Another possibility is to run gdb under a detached screen session.
# To attach to the screen sesssion, su root and run "screen -r
# <id_string>" where <id_string> uniquely matches one of the detached
# sessions (from "screen -list").
# debugger_command =
# PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
# -dmS $process_name gdb $daemon_directory/$process_name
# $process_id & sleep 1
# INSTALL-TIME CONFIGURATION INFORMATION
# The following parameters are used when installing a new Postfix version.
# sendmail_path: The full pathname of the Postfix sendmail command.
# This is the Sendmail-compatible mail posting interface.
sendmail_path = /usr/sbin/sendmail
# newaliases_path: The full pathname of the Postfix newaliases command.
# This is the Sendmail-compatible command to build alias databases.
newaliases_path = /usr/bin/newaliases
# mailq_path: The full pathname of the Postfix mailq command. This
# is the Sendmail-compatible mail queue listing command.
mailq_path = /usr/bin/mailq
# setgid_group: The group for mail submission and queue management
# commands. This must be a group name with a numerical group ID that
# is not shared with other accounts, not even with the Postfix account.
setgid_group = postdrop
# html_directory: The location of the Postfix HTML documentation.
html_directory = no
# manpage_directory: The location of the Postfix on-line manual pages.
manpage_directory = /usr/share/man
# sample_directory: The location of the Postfix sample configuration files.
# This parameter is obsolete as of Postfix 2.1.
sample_directory = /etc/postfix/sample
# readme_directory: The location of the Postfix README files.
readme_directory = /usr/share/doc/postfix
inet_protocols = ipv4
# Enable smtp auth
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/saslpass
smtp_sasl_security_options = noanonymous
# Enable tls
smtp_use_tls = yes
smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination
# Max message size limit
message_size_limit = 0
Please help
Last edited by Rumcajs (2014-08-05 06:16:11)I have solved it, and this was the problem (main.cf) message_size_limit = 0 i have set this to unlimited "0" so bigger mails not get rejected by postfix, the defualt value was 10240000 (~10 Mb) after finally checking the postfix log with journalctl -u postfix (because /var/log/mail.log) is not used anymore i found this line : "fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit" after setting mailbox_size_limit to unlimited "0" postfix starts to delivery local mail.
Last edited by Rumcajs (2014-08-05 06:17:23) -
My Blackberry Curve sends read and delivery receipts to the email sender and to my email. Many times I don't even open the message. In my BB email options, I have NO marked on confirm delivery, confirm read and send read receipts. Does anyone know how to make these stop sending?
open messages icon - menu - options - email settings - make sure it shows your email beside MESSAGE SERVICE
change CONFIRM DELIVERY and CONFIRM READ and READ RECEIPTS to NO -
Mail Delivery System Errors and Securing/Protecting agains spam
Good morning all.
This morning I started recieving these:
From: Mail Delivery System <[email protected]>
Subject: [It] Postfix SMTP server: errors from imr-mb02.mx.aol.com[64.12.207.163]
Date: November 18, 2011 8:51:23 AM EST
To: Postmaster <[email protected]>
Transcript of session follows.
Out: 220 mail.cotaoil.com ESMTP Postfix
In: EHLO imr-mb02.mx.aol.com
Out: 250-mail.cotaoil.com
Out: 250-PIPELINING
Out: 250-SIZE
Out: 250-VRFY
Out: 250-ETRN
Out: 250-AUTH LOGIN PLAIN CRAM-MD5 GSSAPI
Out: 250-AUTH=LOGIN PLAIN CRAM-MD5 GSSAPI
Out: 250-STARTTLS
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250 DSN
In: MAIL From:<[email protected]> SIZE=3485
Out: 250 2.1.0 Ok
In: RCPT To:<[email protected]> ORCPT=rfc822;[email protected]
Out: 451 4.3.5 Server configuration error
In: DATA
Out: 554 5.5.1 Error: no valid recipients
In: RSET
Out: 250 2.0.0 Ok
In: QUIT
Out: 221 2.0.0 Bye
How this started:
Over the past couple of days to approx a week, I have seen a massive influx of Spam on our server. Spam coming in on random ex employee names that no longer work for the company.
Previous to the spam, I turned on "forward un-deliverable mail to" and set to me. The CEO was missing emails because people were not spelling his name correctly. I have actually been able tyo catch a lot of employee emails some important, others not.
In trying to make the mail server more secure, one of the features I tried to turn on was SMTP Client Restrictions, Which broke SMTP for my users. Obviously the error is mine and I need to do more research, but love some feedback on what needs to be set on the server and clients for SMTP client restrictions to work.
I know THE HOFF (mr hoffman) had information at some point to help users secure postfix, can anyone point me in the right direction, as well as any tips here on how to stop the influx of spam?
pstconf -n is here:
alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
biff = no
body_checks = regexp:/etc/postfix/body_checks
broken_sasl_auth_clients = yes
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = smtp-amavis:[127.0.0.1]:10024
daemon_directory = /usr/libexec/postfix
debug_peer_level = 2
enable_server_options = yes
header_checks = pcre:/etc/postfix/custom_header_checks
html_directory = /usr/share/doc/postfix/html
inet_interfaces = all
local_recipient_maps =
mail_owner = _postfix
mailbox_size_limit = 0
mailbox_transport = dovecot
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
maps_rbl_domains =
maximal_queue_lifetime = 2d
message_size_limit = 0
mydestination = $myhostname, localhost.$mydomain, localhost, mail.cotaoil.com, cotaoil.com, $mydomain
mydomain = mail.cotaoil.com
mydomain_fallback = localhost
myhostname = mail.cotaoil.com
mynetworks = 127.0.0.0/8,192.1.1.10,192.1.1.11
newaliases_path = /usr/bin/newaliases
owner_request_special = no
queue_directory = /private/var/spool/imap/dovecot/mail
readme_directory = /usr/share/doc/postfix
recipient_delimiter = +
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = _postdrop
smtp_sasl_password_maps =
smtpd_client_restrictions = permit_mynetworks permit_sasl_authenticated hash:/etc/postfix/smtpdreject cidr:/etc/postfix/smtpdreject.cidr reject_rbl_client zen.spamhaus.org permit
smtpd_enforce_tls = no
smtpd_helo_required = yes
smtpd_helo_restrictions = reject_invalid_helo_hostname reject_non_fqdn_helo_hostname
smtpd_pw_server_security_options = cram-md5,gssapi,login,plain
smtpd_recipient_restrictions = permit_sasl_authenticated permit_mynetworks reject_unknown_recipient_domain reject_unknown_sender_domain reject_invalid_hostname reject_unauth_destination check_policy_service unix:private/policy permit
smtpd_sasl_auth_enable = yes
smtpd_tls_CAfile = /etc/certificates/mail.cotaoil.com.8F44026B8E7E908CEDAAD718F486D91C8FCD693E.cha in.pem
smtpd_tls_cert_file = /etc/certificates/mail.cotaoil.com.8F44026B8E7E908CEDAAD718F486D91C8FCD693E.cer t.pem
smtpd_tls_exclude_ciphers = SSLv2, aNULL, ADH, eNULL
smtpd_tls_key_file = /etc/certificates/mail.cotaoil.com.8F44026B8E7E908CEDAAD718F486D91C8FCD693E.key .pem
smtpd_tls_loglevel = 0
smtpd_use_pw_server = yes
smtpd_use_tls = yes
tls_random_source = dev:/dev/urandom
unknown_local_recipient_reject_code = 550
virtual_alias_maps =
mail:~ administrator$I am not certain what you mean by immediately removing the 192.1.1.10 and 192.1.1.11, AIX servers that I use to relay admin emails to an IT address here. Some sort of a gateway implemented on a pair of IBM boxes, I might presume.
192.1.1.0/24 is in a public address space that you don't have assigned (unless you're BBN). If that IP routing leaks out, then some folks can get cranky. Or should you eventially need to contact hosts within the address space of the "real" occupants of 192.1.1.0/24, routing won't necessarilt play nice. There may well be a static IP route here, depending on the details of the router configuration, as otherwise that IP traffic would be going to BBN and not to those servers. The Internet works because folks play by the rules, when working with IP routing and DNS services. And if your predecessor used this address space (and not the likely 192.168.0.0/16 block), I'd look around to see if there were other unusual network configuration choices.
TCP port 25 is the server-to-server mail port. That's the main connection used among mail servers. Blocking that has the effect that you've discovered.
It's the clients that can also use that port that need to be relocated off the port, as the clients don't have the reverse DNS and related tests that would allow them access to that port, with various common server security configurations.
Open TCP 587 at the firewall and ensure that this port is active at the mail server host, as a starting point. You can test that with (among other tools) with a remote "telnet your.mail.server.host.name 587" command or similar; that's a primitive (but effective) (common) port test.
With the Apple Mail client, make sure the SMTP server is configured to use the default SMTP ports. Mail > Preferences > Account > Account Information > Edit SMTP Server > select the target SMTP server > Advanced > select "use the default ports (25, 465, 587)" and consider using SSL and authentication. (Apple Mail tries a few ports automatically, so the set-up can be different than other clients.)
I don't have enough space here for a full write-up on how mail or IP works, and setting up an arbitrary mail client or an IP network can be an adventure; I assumed the Apple mail client in the above. See the user collaboration services disscussion of mail services in the Mac OS X Server Advanced Administration manual as some background. (And if this stuff all looks a little cryptic, that's understandable, and you might want to consider getting some set-up help or consider moving to hosted mail services and making this stuff somebody else's problem.)
Maybe you are looking for
-
Is it possible to make an interactive symbol?
I'm trying to make a relay for use in multisim, and I don't quite understand how the symbol editor works, but is it possible to make an interactive symbol, like a switch that opens/closes ? I think I should be able to use spice data from a relay(modi
-
HT1338 how come I cant get my notes app to open?
When ever I try and open the notes app in the launchpad a window pops up and a whole bunch of numbers come up and it says EXC_BAD_ACCESS. or something like EXC_I386_GPFLT, what do I do now?
-
How can I save my phone 5 battery life?
Hi! Can you give me some hints to save battery life with my iphone 5? thanks Raffaello
-
Get the session trace files and also the TKPROF reports for storedprocedure
Hi , I am trying to find out the bottlenecks on a storedprocedure, which does a insert into a table, where the target table has lot of indexes/constraints, so i want to see, which indexes/constraints is causing the problem. so in order to do I want t
-
Unproffessional Comments form moderators
Dear Moderators, I am member since 2006 and I used to participate in SDN fourum activiely in 2006 and 2007. That this I was the top contributer in From Priting. That time most of the members used to open threads and once get the answers they used to