Solved

Postfix relay to Office 365 external recipients not delivered

Posted on 2013-01-29
1
1,173 Views
Last Modified: 2013-02-19
I have an issue with Postfix relay to MS Office 365. I can send to internal addresses, but not external. I receive the following error message:

550 5.7.1 Client does not have permissions to send as this sender (in reply to end of DATA command))

I have setup a Microsoft SMTP server and it works fine, both internal and external, but Postfix will not deliver to external addresses. I know it has to be a configuration issue. I just can't pinpoint what it is. I really would prefer to use Postfix. I've used it before and never had any issues, but if I don't figure this out, I will have to go with MS

Here is my main.cf:

# See /usr/share/postfix/main.cf.dist for a commented, more complete version


# Debian specific: Specifying a file name will cause the first
# line of that file to be used as the name. The Debian default
# is /etc/mailname.
myorigin = /etc/mailname

smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu)
biff = no

# appending .domain is the MUA's job.
append_dot_mydomain = no

# Uncomment the next line to generate "delayed mail" warnings
#delay_warning_time = 4h

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

# See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for
# information on enabling SSL in the smtp client.

myhostname = mailrelay.mydomain.com
mydomain=mydomain.com
relay_domains=*
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
myorigin = /etc/mailname
mydestination = mailrelay.mydomain.com, localhost.mydomain.com, , localhost
relayhost = [pod51019.outlook.com]:587
mynetworks = 192.168.86.178, 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
mailbox_size_limit = 0
recipient_delimiter = +

inet_interfaces = all

smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_sasl_security_options = noanonymous
smtp_tls_CAfile = /etc/postfix/cacert.pem

smtp_generic_maps = hash:/etc/postfix/generic
smtp_sasl_mechanism_filter = login
smtp_tls_loglevel = 1
smtp_tls_security_level = may
smtp_send_dummy_mail_auth = yes
0
Comment
Question by:shart68
1 Comment
 
LVL 37

Accepted Solution

by:
ArneLovius earned 500 total points
ID: 38833680
I would guess that you had a username and password for the smarthost in the Microsoft SMTP relay.

Rather than relay through Office 365, why not just add your exit address to your SPF record and send direct ?
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains how to install and use the NTBackup utility that comes with Windows Server.
As tax season makes its return, so does the increase in cyber crime and tax refund phishing that comes with it
This video discusses moving either the default database or any database to a new volume.
This demo shows you how to set up the containerized NetScaler CPX with NetScaler Management and Analytics System in a non-routable Mesos/Marathon environment for use with Micro-Services applications.

773 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question