SMTP issues with XO

I am having trouble sending email using my concentric (xo) account when I am not using them as an ISP. I followed their instructions (http://hostinghelp.xo.com/email-macosx.php?id=xo.com) plus I have changed to port to 587.
When I try to send email I get an error message (The server response was: <[email protected]>: Sender address rejected: Domain not found).
The XO help desk told me, "Mac Mail 2.1 does not support the ability to specify @domain.com as part of authentication on the SMTP server. It will work on the incoming mail server, but causes errors with the application when tried for an SMTP server." They suggested Entourage as an alternative.
Is there a solution to this issue?
I'm running 10.4.8, Mail 2.1 on a 15" PowerBook.
BTW, I posted this on the OSX 10.3 and earlier > Mail &
Address Book thread by mistake. (http://discussions.apple.com/thread.jspa?threadID=868676)
Chuck

Hello Chuck.
If I'm reading the SMTP server settings correctly and
the error message provided which indicates your
domain is cnc, the settings should be as follows:
Outgoing Mail Server: smtp.cnc.com
Authentication: Password
User Name: [email protected]
Password: The account's password.
If I'm reading the SMTP server setting correctly, the
user name for the SMTP server is your entire email
address which the Mail.app does support.
I access an email account with an authenticated SMTP
server that requires the entire email address be used
as the SMTP server user name which works without any
problems.
I tried about every combination of what you suggested and what they suggest in their help (which is confusing and sometimes contradictory). I suspect that it must be possible, but I'm not figuring it out. Thanks for the help.

Similar Messages

Iphone SMTP Issues with Apple 10.6 server.

Hi!
I use multiple iphones and blackberries at my place of employment. On the iPhones, sometimes we get errors on sending email, the error saying "The recipient "......@...." was rejected by the server because it does not allow relaying".
I am wondering if this has something to do with the provider cell network. I say this because this is not a constant, dependable, consistent error. Additionally, I have multiple authentication methods set up on the server, and changing around the configuration (ie turn ssl off, change from md5 to password) etc will get the phone to work. Then you can change config back to what it was and it will work as well.
Right now I have 2 iphones, configured exactly the same for SMTP, 1 phone approx 1 mile away from where mine is. My phone works, the other does not. I am waiting for the user to bring his phone to me so I can do a side by side comparison.
BTW this is in Vermont and Edge is a Rampant disease here......(IE we are on edge more than 3G)

Allan,
I am not sure that I dont allow that, IE im not sure where to set that(this is for allowing an employee to use a personal account through the authenticated SMTP of the company server). I thought as long as the user was authenticating through SMTP, which IS required, then it would in fact allow you to send whether using a personal or company.
These security settings, for me, were set up out of the box, for the most part and have been pretty happy with the security level. I used common sense and logic when configuring my first Apple mail server, however I would have to go through it again and be more diligent about documenting in order to tell you what I set everything to. I had some help from Apple Support.
Anyway im not sure what the personal accounts settings are, we DO allow employees to set up their own accounts, as long as they provide the configuratiuon and can set up themselves.
This particular case seems to be more user created, not server side issue.
To re-iterate, no relaying here. I send emails to Comcast regularly abuse@ to tell them to stop allowing their business accounts in the US to blast out spam....

Incoming SMTP issue with an ASA5512-X

I have reviewed numerous support discussions on this particular issue, but I am still unable to properly configure my ASA 5512-X to receive SMTP email. I can send email, and have access to all other services that I setup. I did create a network object for my Mail server and I am fairly certain this issue has something to do with my static NAT setup.
My current configuration is listed below...any assistance would be greatly appreciated.
I am new to the Cisco ASA appliance, and I am learning CLI as I go. I also have ADSM setup.
CONFIGURATION:
: Hardware: ASA5512, 4096 MB RAM, CPU Clarkdale 2792 MHz, 1 CPU (2 cores)
ASA Version 9.3(1)
names
interface GigabitEthernet0/0
nameif Verizon
security-level 0
ip address 100.39.18.94 255.255.255.0
interface GigabitEthernet0/1
description Local Norco Domain
nameif Norco.local
security-level 100
ip address 10.0.0.10 255.255.255.0
dhcprelay server 10.0.0.1
interface GigabitEthernet0/2
description SCE-DRAS SERVER
nameif SCE-DRAS
security-level 0
ip address 192.168.10.1 255.255.255.0
interface GigabitEthernet0/3
shutdown
no nameif
no security-level
no ip address
interface GigabitEthernet0/4
shutdown
no nameif
no security-level
no ip address
interface GigabitEthernet0/5
shutdown
no nameif
no security-level
no ip address
interface Management0/0
management-only
nameif management
security-level 100
ip address 192.168.1.1 255.255.255.0
boot system disk0:/asa931-smp-k8.bin
boot system disk0:/asa912-smp-k8.bin
ftp mode passive
dns domain-lookup Verizon
dns domain-lookup Norco.local
dns server-group DefaultDNS
name-server 10.0.0.1
name-server 68.238.96.12
name-server 68.238.64.12
domain-name norco.local
same-security-traffic permit inter-interface
same-security-traffic permit intra-interface
object service HTTP-19560
service tcp destination eq 19560
object service HTTP-65535
service tcp destination eq 65535
object service HTTP-8933
service tcp destination eq 8933
object service HTTP-8943
service tcp destination eq 8943
object service RTP
service udp destination range 19560 65535
object service SIP-TCP-8943
service tcp destination range 8933 8943
description IPPHONE - SIP
object service SIP-UDP-8943
service udp destination range 8933 8943
description IPPHONE - SIP
object service smtp
service tcp destination eq smtp
object network SMTP-SERVER
host 10.0.0.1
object-group network IPHONE-SERVERS
description VERIZON IP-PHONE SERVERS
network-object 128.177.14.0 255.255.255.0
network-object 128.177.36.0 255.255.255.0
network-object host 199.19.195.241
network-object host 199.19.195.243
network-object host 199.19.195.250
object-group service GENERAL-ACCESS tcp
description GENERAL SERVICES ACCESS
port-object eq ftp
port-object eq www
port-object eq https
port-object eq smtp
object-group service IP-PHONE-SERVICE
description PHONE SYSTEM ACCESS RULES
service-object object HTTP-19560
service-object object HTTP-65535
service-object object HTTP-8933
service-object object HTTP-8943
service-object object RTP
service-object object SIP-TCP-8943
service-object object SIP-UDP-8943
service-object tcp-udp destination eq 1025
service-object tcp destination eq www
service-object tcp destination eq https
service-object udp destination eq domain
service-object udp destination eq ntp
service-object tcp-udp destination eq domain
service-object tcp-udp destination eq www
service-object tcp-udp destination eq sip
service-object tcp destination eq domain
service-object tcp destination eq smtp
service-object tcp destination eq ssh
service-object tcp destination eq telnet
service-object udp destination eq dnsix
service-object udp destination eq www
object-group service General-TCP-UDP-Access
service-object tcp-udp destination eq domain
service-object tcp-udp destination eq www
service-object tcp destination eq domain
service-object tcp destination eq ftp
service-object tcp destination eq www
service-object tcp destination eq https
service-object udp destination eq www
service-object udp destination eq ntp
service-object udp destination eq radius
access-list Verizon_access_in extended permit object-group IP-PHONE-SERVICE object-group IPHONE-SERVERS any
access-list Verizon_access_in extended permit tcp any object SMTP-SERVER eq smtp
access-list Verizon_access_out extended permit object-group IP-PHONE-SERVICE any object-group IPHONE-SERVERS
access-list Verizon_access_out extended permit object-group General-TCP-UDP-Access any any
access-list Verizon_access_out extended permit tcp any any eq smtp
access-list SCE-DRAS_access_out extended permit ip any any
access-list SCE-DRAS_access_in extended permit ip any any
pager lines 24
logging enable
logging asdm informational
mtu Verizon 1500
mtu Norco.local 1500
mtu SCE-DRAS 1500
mtu management 1500
ip verify reverse-path interface Verizon
no failover
icmp unreachable rate-limit 1 burst-size 1
asdm image disk0:/asdm-731-101.bin
no asdm history enable
arp timeout 14400
no arp permit-nonconnected
nat (Norco.local,Verizon) source dynamic any interface
nat (SCE-DRAS,Verizon) source dynamic any interface
object network SMTP-SERVER
nat (Norco.local,Verizon) static interface service tcp smtp smtp
access-group Verizon_access_in in interface Verizon
access-group Verizon_access_out out interface Verizon
access-group SCE-DRAS_access_in in interface SCE-DRAS
access-group SCE-DRAS_access_out out interface SCE-DRAS
route Verizon 0.0.0.0 0.0.0.0 100.39.18.1 1
route Norco.local 10.10.0.0 255.255.255.0 10.0.0.7 2
timeout xlate 3:00:00
timeout pat-xlate 0:00:30
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
timeout floating-conn 0:00:00
user-identity default-domain LOCAL
http server enable
http 192.168.1.0 255.255.255.0 management
http 10.0.0.0 255.255.255.0 Norco.local
no snmp-server location
no snmp-server contact
crypto ipsec security-association pmtu-aging infinite
crypto ca trustpoint _SmartCallHome_ServerCA
no validation-usage
crl configure
crypto ca trustpoint ASDM_Launcher_Access_TrustPoint_0
enrollment self
subject-name CN=10.0.0.10,CN=ciscoasa
crl configure
crypto ca trustpoint ASDM_Launcher_Access_TrustPoint_1
enrollment self
subject-name CN=10.0.0.10,CN=ciscoasa
crl configure
telnet timeout 5
ssh stricthostkeycheck
ssh timeout 5
ssh key-exchange group dh-group1-sha1
console timeout 0
dhcpd update dns both override
dhcpd address 192.168.10.2-192.168.10.5 SCE-DRAS
dhcpd dns 68.238.96.12 68.238.64.12 interface SCE-DRAS
dhcpd enable SCE-DRAS
dhcpd address 192.168.1.2-192.168.1.10 management
dhcpd enable management
dhcprelay information trust-all
threat-detection basic-threat
threat-detection scanning-threat
threat-detection statistics host
threat-detection statistics port
threat-detection statistics protocol
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
ssl encryption rc4-sha1 aes128-sha1 aes256-sha1 3des-sha1
ssl trust-point ASDM_Launcher_Access_TrustPoint_1 Norco.local
ssl trust-point ASDM_Launcher_Access_TrustPoint_1 Norco.local vpnlb-ip
webvpn
anyconnect-essentials
no error-recovery disable
dynamic-access-policy-record DfltAccessPolicy
class-map inspection_default
match default-inspection-traffic
policy-map type inspect dns preset_dns_map
parameters
message-length maximum client auto
message-length maximum 512
policy-map global_policy
class inspection_default
inspect dns preset_dns_map
inspect ftp
inspect h323 h225
inspect h323 ras
inspect rsh
inspect rtsp
inspect sqlnet
inspect skinny
inspect sunrpc
inspect xdmcp
inspect sip
inspect netbios
inspect tftp
inspect ip-options
class class-default
user-statistics accounting
service-policy global_policy global
smtp-server 10.0.0.1
prompt hostname context
service call-home

Hi Murali,
I ran the packet tracer routine...please let me know if I did this correctly...the results are below. The results indicate the traffic is denied by the implicit rule, but I'm not sure why....
ciscoasa(config)# packet-tracer input verizon tcp 209.85.213.176 smtp 100.39.18.94 smtp
Phase: 1
Type: ACCESS-LIST
Subtype:
Result: ALLOW
Config:
Implicit Rule
Additional Information:
MAC Access list
Phase: 2
Type: ROUTE-LOOKUP
Subtype: Resolve Egress Interface
Result: ALLOW
Config:
Additional Information:
in 100.39.18.94 255.255.255.255 identity
Phase: 3
Type: ROUTE-LOOKUP
Subtype: Resolve Egress Interface
Result: ALLOW
Config:
Additional Information:
in 0.0.0.0 0.0.0.0 via 100.39.18.1, Verizon
Phase: 4
Type: NAT
Subtype: per-session
Result: ALLOW
Config:
Additional Information:
Phase: 5
Type: ACCESS-LIST
Subtype:
Result: DROP
Config:
Implicit Rule
Additional Information:
Result:
input-interface: Verizon
input-status: up
input-line-status: up
output-interface: NP Identity Ifc
output-status: up
output-line-status: up
Action: drop
Drop-reason: (acl-drop) Flow is denied by configured rule

Smtp issues with 10.5.1

I'm using a .Mac email account on Cox internet service.
What should my smtp server settings look like?
Currently I am unable to send mail, I can receive mail fine.
Thanks in advanced.

My wife is witching to a Mac and just purchased a "gently used" iMac. The machine came with a fresh install of Tiger and I upgraded it to Leopard. She cannon send mail - but can receive mail. I upgraded my two Macs and do not have any problems - her settings are exactly like mine - what mystery.

Rochester/Roadrunner Issues with SMTP Server

Hello. New to Rochester and Roadrunner. I let Mac Mail setup the account but it couldn't resolve the SMTP server on Roadrunner. I can receive but not send. I've played with all of the port and SSL settings and still nothing. It shows my account as "offline". My Comcast account is still on there and a few emails went through, but using the Comcast server for some reason.
I know my password is correct as I've double checked it. I've also pinged the smtp-server.rochester.rr.com. Still won't go.
Any thoughts?

I'm having the same issue with the outgoing mailserver in Rochester. I didn't understand your resolution. Would you please explain further?
Thanks!

Keychain Issue with Entourage SMTP password or port attribute

I am posting this under Using OS X rather than Mail since I do not
use Apple's Mail. The problem is the Microsoft Entourage or something
may be sending bad information to the OS X keychain and this prevents me
from sending mail to my ATT/Yahoo account. The workaround I have
been using to send mail is use the OS X Keychain First Aid repair.
After the repair Entourage will send the message one or two times then
I get the following Keychain verification error note:
Item “pop.att.yahoo.com” has unspecified value for port attribute
Item “smtp.att.yahoo.com” has unspecified value for port attribute
Problems were found; you should choose the Repair option to fix them
Verification failed.
The Repair option corrects the problem until the next message is
sent. I have done everything I can think of to the Entourage v12.1.7
settings and something is still not right.
I am beginning to suspect a Keychain bug or error but have no idea
how to get the correct attribute written to the keychain.
Maybe someone could provide some terminal commands to the will
help me write the correct password and port attribute to the keychain.
I am open to any suggestions to clear being nagged every time I
need to send a message to enter my password. The POP mail works
fine. This seems to be an issue with the password that is required
by the ATT/Yahoo smtp server.

If you are sure your primary account is setup correct (per the above URLs), open
the Applications/Utilities/Keychain Access.app and go to Keychain Access/Keychain
First Aid and click on the Verify and Repair if necessary.
FYI, Entourage will write errors to the keychain if you have the account setup wrong.
My error (that cause the keychain errors) was I typed in the my ID and password in
the smtp option. Check the box to use the received and do NOT type in the address.
When you save the settings with nothing in the boxes, Entourage will do it for you
and it will work.
I don't know why but it will not work if you type in the info. Just follow the rules
and it will work
Try It!!
Message was edited by: aRKay

Issue with SMTP

Hi there,
I've got an issue with my SMTP server. Strange thing that it is no problem to send an original message (new message) but when I'm gonna to reply to a received mail (reply or reply to all), Mail is showing an pop up window with comment that it is not possible to send this message via SMTP.
Any clue on this?
Thanks for your help
-Pat

Thanks for answering so far. Here we go: The full message on the pop up is saying:
+Cannot send message using the server smtp+
+The server “smtp.hispeed.ch” cannot be contacted on the default ports.+
+Select a different outgoing mail server from the list below or click Try Later to leave the message in your Outbox until it can be delivered.+
The email provider is hispeed.ch (local provider in my hometown of Basel).
Settings as followed:
Incoming:
Account type: POP
Description: pop.hispeed.ch
email adress: [email protected]
Full Name: my name
Incoming mail server: smtp.hispeed.ch
Port: 110
SSL: none
Authentification: Password
Outgoing Mail Server (SMTP): SMTP
check at box +use only this server+
Descritption: smtp
Server Name: smtp.hispeed.ch
Using default ports (25, 465, 587)
Using SSL
Authentification: none
Hope this will help. Thanks again for your help
-Pat

SMTP relay authentication issue with DynDNS MailHop Outbound

Hi,
I'm trying to use the SMTP relay functionality of my OS X Server but I get following log message:
Apr 4 21:40:21 mydomain postfix/smtp[7629]: 4EE3686F529: to=<xxxx@xxxxx>, relay=outbound.mailhop.org[204.13.248.71]:465, delay=140731, delays=140130/0.06/600/0, dsn=4.4.2, status=deferred (conversation with outbound.mailhop.org[204.13.248.71] timed out while receiving the initial server greeting)
I configured the relay settings in Server-Admin for host: outbound.mailhop.org:465 and added my dyndns username and password.
I would appreciate if someone could help me to figure out what I'm missing.
Thanks

If you're getting a 550 error then it indicates an issue with the SMTP server you're using / how you're connecting to it. Either the mail server you've got configured for SMTP isn't setup to handle email for you, or in addition to setting the server address
in the SMTP settings, you also need to configure it to configure authentication on the email accounts. In the account settings you need to select More settings (I think, I don't have an Outlook 2007 copy to check on), then you'll see an Outgoing
Server tab, within which you can configure the required authentication. It will either be the same as the POP3 login, in which case you can select "Use same settings as my incoming mail server", or if they're different you can enter the specific details that
are required to send.

Issue with the presence indicator in list/library web part.

When viewing a user field (Created By, Modified By or a custom People column) through the list web part (either through the default page /Forms/AllItems.aspx or a custom web part page using a list/library) the presence indicator always says presence unknown.
However if I go to the Site Permissions on the same site, or My Site or a custom page using a modified core search results web part I wrote the presence indicator works fine. I can't find any errors being reported on the server.
Looking at the rendered code the list web part generates:
<IMG name=imnmark width=12 height=12 title="" class=ms-imnImg id=imn_48683,type=smtp alt="No presence information" src="/_layouts/images/blank.gif" border=0 sip="[email protected]">
Locations where the presence indicator works the code is:
<IMG name=imnmark width=12 height=12 title="" class=ms-imnImg id=imn{20140822-1752-098D-8C11-188AD0B8B8B6},type=sip alt=Available src="http://portal.mydomain.com/_layouts/images/imnon.png" border=0 sip="[email protected]" valign="middle">
It appears that the List web part is not detecting that the users have a sip address and they appear to be rendered using smtp instead. It's also odd that the list web part is pulling the correct sip address while the one that works is pulling the
email address, not the sip address stored in the user profile. I spent considerable time going through the xslt to try and figure how the tag is rendered but I haven't been able to figure it out.
We are using Cisco Jabber 9.2.3 for IM, I don't know if that should make a difference or not. It's working fine in other parts of SharePoint and in Outlook. Running SharePoint Dec 2011 CU (14.0.6114.5000) with MS Office 2010 SP2 installed on the client. Tested
in IE 9.0/10/11.
Any ideas?

We don't have a Lync server and I don't have the software available. Are you saying just having Lync installed even though it won't work might help?
I did some more digging and believe that this is an issue with the XsltListViewWebPart. If I go to the UserInformationList the web part used to render the list is the ListViewWebPart and the presence indicator works there. Also our environment
was migrated from 2007 and there are a number of pages that are using the old ListViewWebPart and the presence indicator works fine in this part. If edit the page and add the same list library to it, it's added as a XsltListViewWebPart and the presence
indicator does not work.
The presence control is not rendered by the xsl files used by the webpart. I modified the xsl to display the raw xml and the html code for the presence is part of the xml. I'm guessing this can't be changed and is part of how SharePoint is rendering
the data for the XsltListViewWebPart. You can see the Editor and CheckoutUser lines have the html code embedded in the data.
<Row
ID="60"
PermMask="0x7fffffffffffffff"
HTML_x0020_File_x0020_Type=""
File_x0020_Type="xlsx"
HTML_x0020_File_x0020_Type.File_x0020_Type.mapall="icxlsx.png|Microsoft Excel|SharePoint.OpenDocuments"
HTML_x0020_File_x0020_Type.File_x0020_Type.mapcon="SharePoint.OpenDocuments"
HTML_x0020_File_x0020_Type.File_x0020_Type.mapico="icxlsx.png"
serverurl.progid="1http://myparkersdev.domain.com/sites/BPIT/_layouts/xlviewer.aspx?id=/sites/BPIT/Shared%20Documents/Database%20Sizes.xlsx"
ile_x0020_Type.progid="SharePoint.OpenDocuments.3"
File_x0020_Type.url="FALSE"
FSObjType="0"
FileRef="/sites/BPIT/Shared Documents/Database Sizes.xlsx"
FileRef.urlencode="%2Fsites%2FBPIT%2FShared%20Documents%2FDatabase%20Sizes%2Exlsx"
FileRef.urlencodeasurl="/sites/BPIT/Shared%20Documents/Database%20Sizes.xlsx"
FileLeafRef="Database Sizes.xlsx"
FileLeafRef.Name="Database Sizes"
FileLeafRef.Suffix="xlsx"
CheckoutUser="<a href='javascript:;' onclick='IMNImageOnClick(event);return false;' class='ms-imnlink'><img name='imnmark' class='ms-imnImg' title='' border='0' height='12' width='12' src='/_layouts/images/blank.gif' alt='No presence information' sip='[email protected]' id='imn_77,type=smtp'/></a><a onclick="GoToLink(this);return false;" href="/sites/BPIT/_layouts/userdisp.aspx?ID=526">Ian Howe</a>"
CheckoutUser.id="526"
CheckoutUser.title="Ian Howe"
CheckoutUser.span="<a onclick="GoToLink(this);return false;" href="/sites/BPIT/_layouts/userdisp.aspx?ID=526">Ian Howe</a><img border="0" height="1" width="3" src="/_layouts/images/blank.gif"/><a href='javascript:;' onclick='IMNImageOnClick(event);return false;' class='ms-imnlink'><img name='imnmark' class='ms-imnImg' title='' border='0' height='12' width='12' src='/_layouts/images/blank.gif' alt='No presence information' sip='[email protected]' id='imn_78,type=smtp'/></a>"
CheckedOutUserId="526"
IsCheckedoutToLocal="0"
Created_x0020_Date="0;#2014-08-22 09:47:01"
Created_x0020_Date.ifnew=""
ContentTypeId="0x0101000AE0EC76CD0DB743B42D2FE022EAA6DC"
Modified="8/22/2014 10:51 AM"
Editor="<a href='javascript:;' onclick='IMNImageOnClick(event);return false;' class='ms-imnlink'><img name='imnmark' class='ms-imnImg' title='' border='0' height='12' width='12' src='/_layouts/images/blank.gif' alt='No presence information' sip='[email protected]' id='imn_79,type=smtp'/></a><a onclick="GoToLink(this);return false;" href="/sites/BPIT/_layouts/userdisp.aspx?ID=526">Ian Howe</a>"
Editor.id="526"
Editor.title="Ian Howe"
Editor.span="<a onclick="GoToLink(this);return false;" href="/sites/BPIT/_layouts/userdisp.aspx?ID=526">Ian Howe</a><img border="0" height="1" width="3" src="/_layouts/images/blank.gif"/><a href='javascript:;' onclick='IMNImageOnClick(event);return false;' class='ms-imnlink'><img name='imnmark' class='ms-imnImg' title='' border='0' height='12' width='12' src='/_layouts/images/blank.gif' alt='No presence information' sip='[email protected]' id='imn_80,type=smtp'/></a>"
ecb.dispex="return DispEx(this,event,'TRUE','FALSE','FALSE','SharePoint.OpenDocuments.3','0','SharePoint.OpenDocuments','','1http://myparkersdev.domain.com/sites/BPIT/_layouts/xlviewer.aspx?id=/sites/BPIT/Shared%20Documents/Database%20Sizes.xlsx','526','526','1','0','0x7fffffffffffffff','','')" />
I just find it strange that the old ListViewWebPart works. Our SP environment has not been patched to the latest version, I'll try that next and see if it makes a difference.

[SOLVED]Issue with Postfix sending to external mail addresses

I'm having a very silly issue with Postfix. I followed the wiki article at [link]https://wiki.archlinux.org/index.php/Postfix[/link], and everything seems to work properly, however I cannot send to emails outside of my domain.
I get the error:
550 5.1.1 <[email protected]>: Recipient address rejected: Local delivery only!
Here is what the logs say:
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: connect from localhost.localdomain[127.0.0.1]
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: 091E011E3C: client=localhost.localdomain[127.0.0.1]
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: 091E011E3C: reject: RCPT from localhost.localdomain[127.0.0.1]: 550 5.1.1 <[email protected]>: Recipient address rejected: Local delivery only!; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<sendingdomain.com>
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: lost connection after RCPT from localhost.localdomain[127.0.0.1]
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: disconnect from localhost.localdomain[127.0.0.1]
May 08 16:05:14 my.dns.stuff.org sudo[31476]: me : TTY=pts/0 ; PWD=/etc/postfix ; USER=root ; COMMAND=/usr/bin/journalctl
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/BASIC_CONFIGURATION_README.html etc.
# 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 = mail.sendingdomain.com
# 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 = www.sendingdomain.com
# 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
append_dot_mydomain = no
# 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 = loopback-only
#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
#mydestination = localhost
# 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]
default_transport = error: Local delivery only!
# 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"
# 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/bin/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
#virtual_mailbox_domains = sendingdomain.com
virtual_alias_maps = hash:/etc/postfix/virtual_alias, mysql:/etc/postfix/mysql_virtual_forwards.cf
virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_domains.cf
virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailboxes.cf
virtual_mailbox_base = /home/vmailer
virtual_uid_maps = static:5003
virtual_gid_maps = static:5003
virtual_minimum_uid = 5003
virtual_mailbox_limit = 51200000
Any help would be appreciated. Thank you.
Last edited by nadman10 (2014-05-14 14:36:10)

Your main.cf seems redundant.
For example:
if you specify:
virtual_alias_maps = hash:/etc/postfix/virtual_alias, mysql:/etc/postfix/mysql_virtual_forwards.cf
you don't need this:
alias_maps = hash:/etc/postfix/aliases
and i think you have a lot of more options you don't need.
This is my main.cf on my vps and everything works great (sending and receiving emails from/to most common mail server: gmail, hotmail etc etc)
smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
biff = no
# appending .domain is the MUA's job.
append_dot_mydomain = no
readme_directory = no
# TLS parameters
smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
smtpd_use_tls=yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
message_size_limit = 4194304
virtual_mailbox_domains = mysql:/etc/postfix/mysql-virtual-mailbox-domains.cf
virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-mailbox-maps.cf
virtual_alias_maps = mysql:/etc/postfix/mysql-virtual-alias-maps.cf
virtual_transport = dovecot
dovecot_destination_recipient_limit = 1
it is very simple (no dkim, no forced tls, no mailbox limits and so on) and it can be improved but it works..
as I suggested you just try spending some hour wiping postfix installation and giving a look to this guide

Issue with JAVA Mail API

Hi
We have a requirement to create a custom e mail. For the same I am trying to use Java Mail API.I am facing an issue with the following code:
session session1 = session.getInstance(properties, null);
System gives an error Sourced file: inline evaluation of: ``Properties props = new Properties(); session session1 = session.getInstance(prop . . . '' : Typed variable declaration : Class: session not found in namespace
Is there some specific API i need to import for session class. Kindly suggest.
Regards
Shobha

Hi Shobha,
I was also facing the same issue from last couple of weeks and just now i have achieved the working functionality.
Please find below working code and replace values as per your serveru2019s configuration.
import com.sap.odp.api.util.*;
import java.util.*;
import javax.mail.*;
import javax.mail.internet.*;
import javax.activation.*;
import java.io.File;
import java.net.*;
// SUBSTITUTE YOUR EMAIL ADDRESSES HERE!!!
String to =<email address>;
String from =<email address>;
// SUBSTITUTE YOUR ISP'S MAIL SERVER HERE!!!
String host = <smtp host name>;
String user = <smtp user name>;
// Create properties, get Session
// Properties props = new Properties();
Properties props = System.getProperties();
props.put("mail.transport.protocol", "smtp");
props.put("mail.smtp.host", host);
props.put("mail.debug", "false");
props.put("mail.smtp.auth", "false");
props.put("mail.user",user);
props.put("mail.from",from);
Session d_session = Session.getInstance(props,null);//Authenticator object need to be set
Message msg = new MimeMessage(d_session);
msg.setFrom(new InternetAddress(from));
InternetAddress[] address = {new InternetAddress(to)};
msg.setRecipients(Message.RecipientType.TO, address);
msg.setSubject("Test E-Mail through Java");
msg.setSentDate(new Date());
msg.setText("This is a test of sending a " +
"plain text e-mail through Java.\n" +
"Here is line 2.");
Transport.send(msg);
Deepak!!!

Can't Send Mail on OSX10.7 - No issues with iPad/iPhone

I've got an issue that has surfaced with OSX Lion Mail.App where i can receive, but cannot send email outside of my office network.
OS: 10.7.3
Location: In my office within my domain
Can send and receive emails via Mail.app (configured using imap default smtp port)
Can send and receive emails on iPhone (configured using exchange)
Location: Anywhere Else (or in my office on a different network)
Can receive but CANNOT send emails via Mail.app (configured using imap)
Can send and receive emails on iPhone/iPad (configured using exchange)
I'm able to verify connectivity via 'Connection Doctor'
I only have issues with 10.7 machines. In fact there are two other users in my office with brand new MB Airs with exactly the same issue.
Tia,
Mini

I've got an issue that has surfaced with OSX Lion Mail.App where i can receive, but cannot send email outside of my office network.
OS: 10.7.3
Location: In my office within my domain
Can send and receive emails via Mail.app (configured using imap default smtp port)
Can send and receive emails on iPhone (configured using exchange)
Location: Anywhere Else (or in my office on a different network)
Can receive but CANNOT send emails via Mail.app (configured using imap)
Can send and receive emails on iPhone/iPad (configured using exchange)
I'm able to verify connectivity via 'Connection Doctor'
I only have issues with 10.7 machines. In fact there are two other users in my office with brand new MB Airs with exactly the same issue.
Tia,
Mini

SMTP Issues - Apple Mail - VERY ANNOYING !

So.
On my iPhone I can connect to my office server, send mail no problem, using port 587, the server address, SSL turned on, with the proper credentials for username and password. When I try to mimic this using the same information on my client end of things, all I get with Apple Mail is the "Connecting to server <xxx.xxx.xxx>" OVER AND OVER AND OVER in the Activity window. All of the ports are properly configured on the router, firewall, etc.. as I am able to send using that SAME SERVER with my phone, and iPad. What gives ? I am pulling my hair out trying to sort this out as it is very frustrating. On the mail server side of things (Kerio Connect) really nothing had changed on the server setup for outgoing mail, and SMTP (port 25, 587, 465) services are configured and ready to go using authentication.
If ANYONE has an information on this, it would be greatly appreciated. Is this a timeout issue ? Is it a handshake issue with the server ? A bit stumped for ideas at this point. Thanks in advance.
I am running 10.7.2 - Mail v5.1 I get the same behaviour on a laptop running 10.6.8
Jeff.

One simple, no-risk thing to try is to click on your various mailboxes while in Mail, and do a Mailbox > Rebuild from the menu for each one.

Issue with sending message delay

Hi; Got an issue that has cropped up with Mail lately. Been on the phone all day with Apple Care. Every test on the planet hasn't found what's wrong. I would greatly appreciate knowing if anyone else has come across this issue.
Mail version 4.3 (1081) on a clean IMac OSX 10.6.4. All updates current as of today. ISP is RCN; all settings correct and no known issues with the RCN SMTP server according to them.
Issue is repeatable through all troubleshooting tests performed today. You name it; we did it :-))
Issue seems isolated to sending messages in Mail. Message can be composed normally, then when the send button is hit, I get a revolving wheel for between 30 and 45 seconds on the send folder, then the message clears normally and in the case of a test back to me, can be received normally.
What's strange is that I installed Thunderbird for the sole purpose of testing the send function there to isolate MAIL as the culprit and all messages instantly cleared in Thunderbird and received normally. This takes the RCN SMTP server out of the error equation as far as I can determine.
Anyone have any ideas on this issue. Apple has given up trying to find the problem.
Many thanks
Dudley Henriques

It is "Mail and Address Book" but it's a subset of 10.5
here...http://discussions.apple.com/forum.jspa?forumID=1338
edit: SL stands for snow leopard i.e. 10.6.x
Message was edited by: taylor.henderson

SMTP error with entourage 2004 on OS 10.5

I'm running Entourage 2004 on OS 10.5. For the last week we've had an issue with receiving emails. For several days it wouldn't download any, presenting the error "An operation on the server timed out. The server may be down, overloaded, or there may be too much net traffic." (-3259 )
" Halfway into this, it downloaded the bulk of the emails from the days it hadn't connected, but never finished and gave the same error again. Emails can still be sent fine. It's an AOL email account.
It's set up to receive from an IMAP server as imap.aol.com.
It's set up to send from smtp.aol.com, overriding default port with 587, password required.
I started to set up a new account with this email, and when it tried to verify the account settings, the IMAP settings verified fine, but the SMTP settings didn't.
I found one forum that said "smtp.aol.com" had to be changed to "smtp.aol.com:[email protected]"
That didn't work (couldn't find the server)
So...it's sending emails just fine and they even get received by other mail accounts in entourage, but unable to verify the smtp settings for receiving.
Yet it cannot receive emails and verifies imap settings just fine.

Hi Roy,
You have them swapped, SMTP is for Outgoing mail... usually!
For Incoming Mail Server, try: imap.aol.com.
http://macs.about.com/od/applications/qt/mailaol.htm

SMTP issues with XO

Similar Messages

Maybe you are looking for