Sending to external address: 550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found

Hi. We are using now two systems of Exchange. 2010 SP3 on-premises as part of SBS 2011 and Exchange Online. Two yaers 2010 works good. But 2-3 month ago one user began to receive error when he send email from 2010 to Exchange Online:
550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found
IMCEAEX-_O=EXCHANGELABS_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=RECIPIENTS_CN=6FB07FEC5205488CBDFDC30357EFDEF8-TOBIAS@domain.local
#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##
Ursprüngliche Nachrichtenköpfe:
Received: from MX.domain.local ([XXX.XXX.XXX.XXX]) by MX.domain.local
([XXX.XXX.XXX.XXX]) with mapi id 14.03.0174.001; Tue, 11 Mar 2014 10:16:10 +0100
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: David David<[email protected]>
To: =?Windows-1252?Q?Tobias_Tobias_?= <[email protected]>
Subject: AW: radar bilder
Thread-Topic: radar bilder
Thread-Index: AQHPPGR6TwWhAAAOtEWIAnQvTY5AzprbnBRr
Date: Tue, 11 Mar 2014 10:16:10 +0100
Message-ID: <[email protected]>
References: <CF437C4B.22C52%[email protected]>
In-Reply-To: <CF437C4B.22C52%[email protected]>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator: <[email protected]>
MIME-Version: 1.0
I have read Internet about this case. And this solutions help to us, but only for one month... But it comes again and again. I
have read information about X500 address, but these all cases involved
a local user. When error comes description is about wrong X500 for local user. Why my Exchange 2010 SP3 doesn't send email to external domain, but looking in local database? Of course this address absent in database, because it is
external address.
Can be this is due to the fact that the user stores more than 30,000 messages in one folder and OAB always crushed?
This problem has only one user, and only while he write to Exchange Online domain.
Thank you!

Hello,
Please try to use owa to send a message to exchange online user to check the result.
Because there are many messages, I recommend you set retention policy, and then apply it to the user's mailbox.
Cara Chen
TechNet Community Support

Similar Messages

Remote Server returned '550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found'

Hi all,
having the following issue that started today,everything been working fine until now.
When Office 365 users send e-mail to some on premise users they get the following error in Return.
Remote
Server returned '550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found'
On premis users (Exchange 2013) can send to the same contact just fine.So for 365 users that failed we have tested the following:
Using OWA,says recepient cannot be found.
All 365 users fails to same recepients,for now a dosen People.
Address that fail,mailboxes are spread accross different databases.
Cannot see any error in event Viewer related to this.
Any tips?
thanks!
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

Hi Ed,
thanks for reply and sorry for late reply,been alot to do lately With lots if migrations and errors.
YEs you are correct that the problem is caused by useraccount was in wrong OU and was not sync to the "Cloud".
Move users Object to correct OU and all was working fine.Strange this is that it have worked before,so does it mean that if user is not in the OU defined to synced,it will be removed from the cloud?
Br
Ill put it as resolved :)
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##

We have a distribution list with 3 external users set up as custom contacts and two internal domain users.
When you send to the dist list the three external users fail and we receive
The e-mail address you entered couldn't be found. Please check the recipient's e-mail address and try to resend the message. If the problem continues, please contact your helpdesk.
Exchange 2010 Standard SP3 RU3
Server 2008 R2 Standard
Was messily upgraded sometime ago from Exchange 2003.
Could be a legacy Issue?
Any assistance would be greatly appreciated.

Hi,
Thanks for your response. It's great to hear the good news.
Best regards,
Amy
Amy Wang
TechNet Community Support

Smtp;550 5.1.1 RESOLVER.ADR.RecipNotFound; not found

hello All,
I am getting the above error when i send a mail from external domain. I have exchange server 2010 on and O365 account. From last 2 months i am not using O365 account and even active sync is also not working. And recently O365 subscription was over. So now
non -synced users are not getting mails from external domain. Please find the below complete error.
The email address you specified couldn't be found or is invalid. It may be due to a bad entry in your Outlook or Outlook Web App recipient AutoComplete cache. Use the steps below to delete the entry from the cache:
Click New mail.
In the To field start typing the recipient's name or email address until the recipient appears in the drop-down list.
Use the DOWN ARROW and UP ARROW keys to select the recipient, and then press the DELETE key.
Then resend your message – delete and retype the recipient’s name or e-mail address before sending it.
For more tips on how to resolve this issue see DSN code 5.1.1 in Exchange Online.
Diagnostic information for administrators:
Generating server: DM2PR08MB368.namprd08.prod.outlook.com
[email protected]
Remote Server returned '550 5.1.1 RESOLVER.ADR.RecipNotFound; not found'
Original message headers:
Received: from BLUPR08CA0072.namprd08.prod.outlook.com (10.141.200.52) by
DM2PR08MB368.namprd08.prod.outlook.com (10.141.55.154) with Microsoft SMTP
Server (TLS) id 15.0.1010.18; Wed, 20 Aug 2014 16:55:58 +0000
Received: from BN1AFFO11FD021.protection.gbl (2a01:111:f400:7c10::118) by
BLUPR08CA0072.outlook.office365.com (2a01:111:e400:88d::52) with Microsoft
SMTP Server (TLS) id 15.0.1010.18 via Frontend Transport; Wed, 20 Aug 2014
16:55:56 +0000
Received: from mail-vc0-f171.google.com (209.85.220.171) by
BN1AFFO11FD021.mail.protection.outlook.com (10.58.52.81) with Microsoft SMTP
Server (TLS) id 15.0.1010.11 via Frontend Transport; Wed, 20 Aug 2014
16:55:56 +0000
Received: by mail-vc0-f171.google.com with SMTP id hq11so9516889vcb.30
for <[email protected]>; Wed, 20 Aug 2014 09:55:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=mime-version:date:message-id:subject:from:to:content-type;
bh=UIg592euC1okrJydwvvU1ssSy4p+p3l+Nh+vpxrcn/Y=;
b=yhVCdHhs616U6+U4K7UqoQwm+eUrFgIJMKqmEUzREUgdgcgFtoM9+5MABnFeEjW7Cz
RT7vVTlH+v7nH/iW+nntxCRi4I3cqLUcAY8AgM5kGVoGBURCqo66dVbxWghB0HMDiZ7D
1AMDv1gez/PG8pmOpSVtkg1xmp0a/19vlPcqJ5ZRBlU/HdAuEYRp9M8ZBZLXgYF9RfDg
PphDqDLqDZ+Y7yNVIbAoC3gHA9kqfqAgWp3HOqRWb5TcRWI7sb9pj5ifYPQBVDJ6ozAS
jGfhzvxWHnbBPzVKqcCmkgrUVcSX8cUCrZqBjSk6c616nHSjVy6fRHnPdyIJ0Nzd6cnk
FR5Q==
MIME-Version: 1.0
X-Received: by 10.52.136.196 with SMTP id qc4mr15358922vdb.22.1408553755439;
Wed, 20 Aug 2014 09:55:55 -0700 (PDT)
Received: by 10.52.178.168 with HTTP; Wed, 20 Aug 2014 09:55:55 -0700 (PDT)
Date: Wed, 20 Aug 2014 22:25:55 +0530
Message-ID: <CA+GyOUV7n1V35=GRmzciyuocnAFngUN1Kba0XUbbT2QjEUb4Cg@mail.gmail.com>
Subject:
From: sai siva kumar <[email protected]>
To: <[email protected]>
Content-Type: multipart/alternative; boundary="bcaec51b12bd3d78fb0501127a3a"
Return-Path: [email protected]
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:209.85.220.171;CTRY:US;IPV:NLI;EFV:NLI;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;UriScan:;
Final-Recipient: rfc822;[email protected]
Action: failed
Status: 5.1.1
Diagnostic-Code: smtp;550 5.1.1 RESOLVER.ADR.RecipNotFound; not found
Thanks

Hi,
Have you tried deleting the bad entry in your Outlook or Outlook Web App recipient AutoComplete cache as the error message suggested? If not, please have a try on it.
In addition, this issue may also occur if the on-premises mail-enabled user who represents the moved mailbox isn't stamped correctly with the target address. The Exchange server generates an NDR message because the on-premises Active Directory Domain Services
(AD DS) can't locate the user in order to route the mail correctly. To resolve it, please refer to this KB article:
http://support.microsoft.com/kb/2685437
Also have a look at the following article regarding 5.1.1 error:
http://technet.microsoft.com/en-us/library/dn479208(v=exchg.150).aspx
Since this forum is for questions and feedback related to Office Client side issue, you can also post a question in Exchange Online forum for further assistance:
http://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
Thank you for your understanding.
Best Regards,
Steve Fan
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

550 5.1.1 RESOLVER.ADR.RecipNotFound; not found

Exchange 2013 to Office 365
Delivery has failed to these recipients or groups:
[email protected]<mailto:[email protected]>
The email address you entered couldn't be found. Please check the recipient=
's email address and try to resend the message. If the problem continues, p=
lease contact your helpdesk.
Diagnostic information for administrators:
Generating server: EX-01.asianpaintsbd.com
[email protected]
Remote Server returned '550 5.1.1 RESOLVER.ADR.RecipNotFound; not found'
Original message headers:
Received: from EX-01.asianpaintsbd.com (192.168.0.8) by
EX-01.asianpaintsbd.com (192.168.0.8) with Microsoft SMTP Server (TLS) id
15.0.620.29; Sat, 1 Mar 2014 12:43:43 +0600
Received: from mailgate.asianpaints.com (192.168.0.254) by
EX-01.asianpaintsbd.com (192.168.0.8) with Microsoft SMTP Server id
15.0.620.29 via Frontend Transport; Sat, 1 Mar 2014 12:43:43 +0600
Received: from appolicy.asianpaints.com (appolicy.asianpaints.com
[172.25.30.13])        by mailgate.asianpaints.com (Postfix) with ESMTP id
6BC55201D3     for <[email protected]>; Sat, 1 Mar 2014 12=
:17:23
+0530 (IST)
Received: from mail pickup service by appolicy.asianpaints.com with Microso=
ft
SMTPSVC;        Sat, 1 Mar 2014 12:13:13 +0530
thread-index: Ac81GYSiNf8cxYe8ThegGiLPANUKMQ=3D=3D
Content-Transfer-Encoding: 7bit
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
Received: from cmail.asianpaints.com ([192.168.40.3]) by
appolicy.asianpaints.com with Microsoft SMTPSVC(6.0.3790.3959); Sat, 1 Mar
2014 12:13:13 +0530
Received: from ibu.asianpaints.com (ibu.asianpaints.com [192.168.40.2]) by
cmail.asianpaints.com (Postfix) with ESMTP id 261C919E42 for
<[email protected]>; Sat, 1 Mar 2014 12:13:13 +0530 (IST)
Received: from apbl17 (unknown [116.68.197.114]) by ibu.asianpaints.com
(Postfix) with SMTP id DD14814D7FD; Sat, 1 Mar 2014 12:13:09 +0530 (IST)
Message-ID: <36F973864DEF41E985442FF4DABA2B2D@apbl17>
From: "Md. Mahmudul Hasan" <[email protected]>
To: Bhabotosh Mukharjee <[email protected]>, "'Md.
Salehuddin'" <[email protected]>, 'mridul kumar mazumder'
        <[email protected]>
CC: 'Anjan Sir' <[email protected]>, 'Saifur rahman Rahman'
        <[email protected]>, 'Mohammad Ullah Khan'
        <[email protected]>, 'FARUQUE-UL ISLAM Boss'
        <[email protected]>, <[email protected]=
om>,
        ''Aroop Chatterjee'' <[email protected]>,
        <[email protected]>, ''Mohammad Fuad Khan''
        <[email protected]>, <[email protected]>
References: <008401cf3505$2ac16620$6a80a8c0@Wearhouse>
<[email protected]>
Subject: Re: To Start Dispatch oparation To Demra Depot.
Date: Sat, 1 Mar 2014 12:43:27 +0600
MIME-Version: 1.0
Content-Type: multipart/alternative;
        boundary=3D"----=3D_NextPart_000_009B_01CF354B.D7F8CD60"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.3959
X-OriginalArrivalTime: 01 Mar 2014 06:43:13.0208 (UTC) FILETIME=3D[84989380=
:01CF3519]
Return-Path: [email protected]
Md. Ramin Hossain

Hi,
According to your description, I found that delivery failed when sent email from Exchange 2013 to Office 365. Following is my understanding, please correct me if there is any misunderstanding.
1. The sender Md. Mahmudul Hasan's mailbox holding in Exchange 2013 server.
2. The recipients' (in "To" and "Cc" field) mailboxes holding in Office 365.
3. When the sender Md send email to the recipients, delivery failed and got the NDR "Remote Server returned '550 5.1.1 RESOLVER.ADR.RecipNotFound; not found'".
If it is the case, please verify the recipients' email addresses.
If the recipients are all moved from Exchange 2013 to Office 365, this issue may occur if the on-premises mail-enabled user who represents the moved mailbox isn't stamped correctly with the target address.
The Exchange server generates an NDR message because the on-premises Active Directory Domain Services (AD DS) can't locate the user in order to route the mail correctly.
More details in the following KB:
"Delivery has failed" and "550 5.1.1 RESOLVER.ADR.RecipNotFound" NDR after a mailbox is moved to Office 365
http://support.microsoft.com/kb/2685437/en-us
Hope it is helpful
Thanks
Mavis
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

#550 5.1.1 RESOLVER.ADR.RecipNotFound; not found ## for all emails to one of my domains

Hi All
I can see this question has been asked allot, but none of the answers seem to be the same as my issue
Exchange 2007 / SBS 2008
I have 3x domain email addresses for all of my recipients
@domain1.com (default reply)
@domain2.com
@domain3. com
@domain4.com
all of a sudden, all emails getting sent to anyone with @domain2.com are bouncing, to start with there was no reponse, but the mail logs were showing "550 5.1.1 User unknown" in the logs
So I unticked "Block messages to recipients not listed in the GAL" on exhange anti spam, after this the messages were getting to the exchange server, but then getting bounced with the above message
I have tried removing domain2.com from the email address policy and the acceprted domains, and readding it, but it made no difference
all my other domains still work fine, its only this one
I'm at my wits end with this, if anyone can shed some light it would be appreciated
Let me know what other info i need to provide
Cheers

No issues related to the GAL in the event log
I have disabled all the anti spam features
first I restarted all the services, no change, then I booted the whole sever and that made no difference
all the domains are set up as authoritive
the domain2.com is a seccondary email address for all users, so
user1 has
[email protected], [email protected], [email protected], [email protected]
I can email successfully to user1 on all emails execpt for [email protected], that bounces, and the same issue occurs for everyone not just mail sent to user1, so its definitely related to domain2.com
it's really odd
any other ideas
Cheers

Where is the feature "Send using External Address" gone?

Did someone found the MobileMe feature "Send using External Address" in iCloud?

No, currently there is none. There is only the option to configure iCloud Aliases in the webinterface but no more external adresses and mail servers. So currently no possibility to use the Webmail interface with an external address.
In Lion Mail Programm it is easy to add the external email adress and use an alternative server for sending. On iOS devices you can also configure a IMAP account with the iCloud server as incoming server and your external address/server for sending.
Hope this will be added in the next weeks for the webmail interface. It was already there in MobileMe. No idea why they didn't port that feature to iCloud.

Exchange 2013 - Outlook 2010 - 550 5.1.0 RESOLVER.ADR.InvalidInSmtp; encapsulated INVALID address inside an SMTP address

Hello,
I have issue when sending email to some addresses. Server respond with:
Remote Server returned '550 5.1.0 RESOLVER.ADR.InvalidInSmtp; encapsulated INVALID address inside an SMTP address (IMCEAINVALID-)'
My enviroment: Exchange 2013, Outlook 2010 - no cached mode. Issue happend with two email addresses but not always.
Any suggestion, how to resolve issue?
Thx.

Hi Tomas,
Does this issue occur in OWA? How is the impact, only one user or all users?
Please try to run Outlook under safe mode to avoid add-ins and AVs.
If there is any 3rd party add-ins, please try to disable them for testing.
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Mavis Huang
TechNet Community Support

SAP Inbox - Sending to external address

HI,
I'm sending a message from SAP Inbox via SBWP to a user ID. In SOST the status of the message stays RED indicating it did not go through. I have two users who are not receiving and one that is receiving. The one that is receiving in SOST has status of green indicating that the message went through. All three users have the same attributes in the email address field in SU01.
Any ideas why this is happening? Since there are no difference in the setup of all three users why is one receiving and the other not receiving?
Below is the error Iu2019m getting for the two user IDs not receiving.
Internal error: Recipient address not found. Return code:80
-Wes

Hi Wes and company!
Also notes 997428 and 1233095 could apply here.
In case the issue is that there is an missing or wrong entry in the address management tables (table ADR6), as Ganesh pointed out, it is possible to trigger a recipient change in SOST by setting the parameter SOST_REC_CHANGE to 'X' in table SXPARAMS as described in note 685164.
Find the general parameters (table SXPARAMS) in transaction SOST -> Utilities -> General Parameters.
Afterwards you will get a popup where you can decide to change the recipient before you resend a document from SOST. Here you decide to change the recipient before sending and enter the same e-mail address before. Now the address should be properly created.
Cheers!
-Jesú

Cfmail not sending to external address

Hello,
I have a new web server that I am testing before turning it on live. I have run into a cfmail issue. The server is
Windows 2008 R2, 64Gig ram, 64-bit, IIS 7.5, Coldfusion 9.0.2 multi server, clustering 2 CF instances, JDK1.7.0_71
We had a company setup CF and harden so this may be related to the hardening but I am not sure.
<cfmail is not sending email to recipients outside of our domain/work domain. The 1st <cfmail> tag below sends the email but the 2nd one does not. This is what I see when trying to send via the 2nd <cfmail> tag with external recipient email address domain
- no errors on the page I run in the browser
- email is not received at [email protected] (syntax is correct)
- attempt #2 shows up in mail/Undelivr folder
- mail.log has this error
"Error","scheduler-3","01/15/15","10:13:27",,"javax.mail.SendFailedException: Invalid Addresses;   nested exception is: com.sun.mail.smtp.SMTPAddressFailedException: 550 5.7.1 Unable to relay
- application.log - no error
- exception.log has same error in addition to stack trace
- server.log no error
Any help is appreciated
Joe
<cfmail to="[email protected]" from="[email protected]" subject="test" type="html">
    #DateFormat(now(),"mm/dd/yyyy")# #TimeFormat(now(),"HH:mm:ss")#<br />
</cfmail>
<cfmail to="[email protected]" from="[email protected]" subject="test" type="html">
    #DateFormat(now(),"mm/dd/yyyy")# #TimeFormat(now(),"HH:mm:ss")#<br />
</cfmail>

CFMAIL is just a wrapper for the underlying Java mail API methods, so there should not be any problem with it.
Seems like SMTP server is not registered to send mails out. So this is purly the problem with the SMTP server, not with the CFMAIL
HTH
Thanks
VJ

When I search using my address bar it comes up and say page not found jar file, how do I fix this?

File not found
Firefox can't find the file at jar:file:///C:/Program Files (x86)/Mozilla Firefox/omni.jar!/chrome/en-US/locale/browser-region
Check the file name for capitalization or other typing errors.
Check to see if the file was moved, renamed or deleted.

hello Kygirl, please install the search reset addon - it will revert the most common customziations those adware programs do in firefox back to the default (including the keyword search from the location bar): https://addons.mozilla.org/firefox/addon/searchreset/

New distribution groups results in Undeliverable "recipients address not found in recipients email system"

For some reason, new distribution groups I have created result in Undeliverable with the following body, Other distribution groups created in the past work fine. I have tested this outside our organization using my gmail and it gets returned to my gmail
account as well. Users that belong to the group are chosen obviously from the exchange provided users. I have tried using OWA, deleting autoentry, using the full address of the distribution group, I am truly at a loss. Any help is appreciated thanks in advance!
-Steve
Delivery has failed to these recipients or distribution lists:
[email protected]
The recipient's e-mail address was not found in the recipient's e-mail system. Microsoft Exchange will not try to redeliver this message for you. Please check the e-mail address and try resending this message, or provide the following diagnostic text to your
system administrator.
Sent by Microsoft Exchange Server 2007
Diagnostic information for administrators:
Generating server: akmail.mydomain.COM
[email protected]
#550 5.1.1 RESOLVER.ADR.RecipNotFound; not found ##
Original message headers:
Received: from akmail.mydomain.COM ([::1]) by
AKMAIL.mydomain.COM ([::1]) with mapi; Tue, 8 Jul 2014 12:43:48 -0400
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: Steven Anderson <[email protected]>
To: "[email protected]" <[email protected]>
Date: Tue, 8 Jul 2014 12:43:47 -0400
Subject: test2
Thread-Topic: test2
Thread-Index: AQHPmsvJDOvU9vGSLkK1oPeNzIzatw==
Message-ID: <[email protected]>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator: <[email protected]>
MIME-Version: 1.0

Thank you very much for your response Akshay, here is the results from the Get-DistributionGroup:
Name                DisplayName         GroupType           P
techsupport         techsupport         Universal           t
info                info                Universal
i
*CallOut            *CallOut            Universal           _
AKwirelessorder     AKwirelessorder     Universal           A
*AllEmployees       *AllEmployees       Universal, Secur... _
casstb              casstb              Universal           c
albanytsg           albanytsg           Universal           a
ak911kyalarms       ak911kyalarms       Universal           a
Polk                Polk                Universal
P
Solatb              Solatb              Universal           S
kytechs             kytechs             Universal           k
AKDISTSolacom       AKDISTSolacom       Universal           A
NEFla               NEFla               Universal           N
RhodeIsland         RhodeIsland         Universal           R
NewYork             NewYork             Universal           N
bradsgroup          bradsgroup          Universal           b
petesgroup          petesgroup          Universal           p
mikesgroup          mikesgroup          Universal           m
test2               test2               Universal, Secur... t
So it does list it, I have 2 domain controllers at the same site one is also hosting the exchange server (we are a small business). I created the distribution group directly on the exchange management console. I will force AD replication, but I have looked
at the structure using ADSIedit and it does list it in the users section which is sort of why I am at a loss on this. Thanks very much for your help, -Steve

550 5.1.1 RESOLVER Error

We have an Exchange 2010 SP3 infrastructure. We synchronize our Active Directory with many other government agencies. All the external agencies mailboxes show up as mail-enabled contact. Were seeing lots of 550 5.1.1 RESOLVER.ADR.Ex.RecipNoFound errors when
our users try to send mail to any of the contacts. Our fix has been to create an x500 address for these contacts and then the mail flows correctly.
Each night when we sync directories, all the mail-enabled contacts are overwritten and we're back to square one. Do we need to specify that agencies sync a x500 address with all their contacts as well?
Orange County District Attorney

Hello,
The following article should explain the reason. (Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft.
Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.)
http://zahirshahblog.com/2012/03/06/gal-sync-issues-for-mail-enabled-contacts-legacyexchangedn-missing-from-contact-imceaex-_ont5_ou-the-e-mail-address-you-entered-couldnt-be-found-admodify-update-mail-contacts-for-legacyex-2/
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

[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

Sending mail to external address

Hi all,
I did a configuration for set up the gateway
1- Set up RFC in SM59. I tested this connection was working fine.
2- Created a node in SCOT under INT (Internet). Allowed all formats for processing.
3- I have set up conversion rules in SCOT.
4- After above When I send an email from Workplace to an external address like [email protected] I get an error that Cannot process message in node, parameters cannot be converted.
Message class XS message 821
Now I am not sure what parameters it has not been able to convert. Has anyone encountered this problem earlier?
Thanks in advance.
ViKaS.

Hai Vikas
Check the following Document
Here are the steps.
SM59 Transaction is used for Connection Establishment with Destination.
When you establish a connection to a client through a destination, the HTTP connection must first be entered in transaction SM59.
There are two types of HTTP connection in transaction SM59: Call transaction SM59 to display the different RFC destinations.
The HTTP connection to the external server (connection type G) and the HTTP connection to the R/3 system (connection type H) are different only in their logon procedures. Their technical settings are the same. To display the technical settings, double-click a connection.
You can choose from three tabs. Under Technical Settings, you can specify the following:
・ Target Host: The host to which you want to connect.
Note that if you are using HTTPS as a protocol, you have to specify the full host name (with domain).
・ Service No.: Here, you specify the port. The destination host must of course be configured in such a way that the specified port understands the corresponding protocol (HTTP or HTTPS). See Parameterizing the ICM and the ICM Server Cache.
・ Path Prefix: At the time when the connection to this destination is initiated, the system inserts this sub-path before ~request_uri.
・ HTTP Proxy Options: Here, you can configure a proxy for HTTP connections: You can determine the proxy host and service, as well as users and passwords for the HTTP connection.
The tab page Logon/Security will be different depending on whether you have selected a HTTP connection to an external server (connection type G) or a HTTP connection to an R/3 system (connection type H).
HTTP Connection to an External Server (Connection Type G)
Choose the connection you want to use. You can choose from the following logon procedures:
・ No Logon: The server program does not request a user or password.
・ Basic Authentication: The server program requests a user and password. Basic Authentication is a standard HTTP method for authenticating users. When a user logs on to the target system, he or she provides a user ID and password as authentication. This information is then sent in a header variable as a Base 64-encoded string to the server, through the HTTP connection.
・ SSL Client Certificate: If you use client certificates for authentication, the client authentication is performed through the Secure Sockets Layer (SSL) protocol. In this case, you must also select the SSL Client PSE of the SAP Web AS that contains the relevant certificate for the authentication. The target system must handle the issuer of the SAP Web AS client certificate as a trusted system.
Under Logon/Security, you can also activate SSL to ensure that HTTPS is the protocol used (if you select SSL, make sure that the correct port is entered under Technical Settings). In the security transaction STRUST you can determine which type of SSL client is used. (Getting Started with the Trust Manager, Trust Manager).
The field Authorization for Destination has been implemented as an additional level of protection. We recommend that you specify a user and password for the RFC destination.
HTTP Connection to an R/3 System (Connection Type H)
Here, you can specify more settings for authentication in the target system.
The settings under Technical Settings and Special Options are the same as for connection type G. Under Logon/Security, the connection type H has additional logon procedures. As with external servers, you can activate and deactivate SSL and specify an authorization.
Because the target system is an SAP system, you can set the client and language for the logon as well as the user name and password. If you check Current User, you have to specify the password.
The following authentication procedures are available: Basic Authentication, SAP Standard, and SAP Trusted System, and SSL Client Certificate.
・ HTTP Basic Authentication: Logon with user and password
・ SAP Standard: This procedure uses an RFC logon procedure. The RFC Single Sign-On (SSO) procedure is valid within the one system. The same SAP user (client, language, and user name) is used for logon.
・ SAP Trusted System: Trusted RFC logon to a different SAP system (see Trusted System: Maintaining Trust Relationships Between SAP Systems)).
・ SSL Client Certificate: The SSL protocol enables you to use client certificates for the logon.
Type G/H (SM59)
Timeout:
When sending a HTTP request, you can use this parameter to specify the maximum response time for the connection.
HTTP Setting:
You can use the HTTP version to specify the protocol version of the HTTP request (HTTP 1.0 or 1.1).
Regards
Sreeni

Sending to external address: 550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found

Similar Messages

Maybe you are looking for