Having issues with Lync meetings with external partners

This is basically a new concept for us because Lync was used mostly for internal use. The last couple of times we tried to have a meeting with a non-Federated partner like a reseller giving a demo, they would send us a Lync invite and when I try to connect
to the meeting by clicking the Lync invite in the email, my locally installed Lync 2013 client opens a window and I hear a series of beeps, about 20-30 like its trying to connect. It makes a connection for a few seconds (I enter the virtual lobby) and then
it disconnects.
This has happened with two different corporations, one of them being Microsoft. The companies are not Federated with us so I guess the questions are this:
Does the company have to be Federated with us just to have a meeting?
Should I enable partner domain discovery under Access Edge Configuration in Control Panel? (Seems like this is something you don't want)
I have Centralized logging running and I extracted the logs for the time the meeting was trying to start. I used Snooper to review the logs.
I am seeing two errors which are below:
SIP/2.0 403 Forbidden
ms-diagnostics: 1027;reason="Cannot route this type of SIP request to or from federated partners";source="sip-edge.ourdomain.com" (the source is our Edge)
SIP/2.0 504 Server Time-out
ms-diagnostics: 1017;reason="Cannot route From and To domains in this combination";summary="Cannot route between the source and destination domains because partner discovery is not enabled";external-domain="theirdomain.com";external-type="domain-type-remote";internal-domain="ourdomain.org";internal-type="domain-type-local";source="sip-edge.ourdomain.com"
504 is a bit confusing because it implies that you have to be Federated with a partner just to have a meeting.

Hi shadowtuck,
I reviewed your last post (https://social.technet.microsoft.com/Forums/en-US/40422065-9244-4d65-a538-b702315d6727/cant-share-desktop-in-lync-meeting-with-microsoft?forum=lyncdep
), and I did some more research.
You have two choices:
1. Enable open federation.
2. Join the meeting as a guest by using Lync Web App.
The diagram for your reference.
If you do not want to enable open federation, you have to join the meeting as a guest by using Lync Web App.
Best regards,
Eric

Similar Messages

Having issues on macbook pro with maverick

Am having issues after downloading Maverick the system is becoming very slow. The pinwheel keeps spinning. Any suggestions how to deal with this issue

I have the same issue and this started only after upgrading to Mavericks..
MacBook Pro
Retina, Mid 2012
OS X 10.9.1 (13B42)

Having issues making GarageBand work with iPad and line 6 midi mobilizer. Any suggestions?

I am having issues making the line 6 midi mobilizer for keyboard work with GarageBand for ipad2.

Check out the iRig Midi iRig MIDI

If you are having issues connecting to wifi with your Ipad, READ THIS

My son recently could not connect to the home wifi. After almost a year of having no issues, it came on overnight sort-of-speaking. I spent over three hours doing all the resets and tried anything that was talked about online. This could be your issue too. WHEN YOU SET UP YOUR ROUTER, IT WILL HAVE A PASSCODE/PASSWORD/PASSPHRASE (different routers may call it differently), this is usually a series of letters and numbers. YOU WILL ALSO SET UP A PASSWORD TO ACCESS YOUR HOME NETWORK FROM ANY OF YOUR DEVICES. THE TWO ARE VERY DIFFERENT, THE PASSWORD THAT THE IPAD WANTS IS NOT THE NETWORK PASSWORD, IT IS THE PASSWORD OF THE ROUTER.
This makes no sense to me, but it worded. I have a CISCO router and Mercury Net for an Internet provider. As I was working on getting my issue solved, I ran across a post that said this same thing about a different router and provider, so I thought why not try it, nothing to lose. IF IT WORKED FOR TWO DIFFERENT ROUTERS AND PROVIDERS, THIS COULD BE YOUR PROBLEM AS WELL.
To start with, I did not know the passphrase to my roouter. I reset the router to factory default and followed a few steps for security and other things. Along the reset, there was a page that showed the passphrase. If you do not have your router passphrase, this may be your best bet. I am by no means a professional when it comes to computers, but I am not affraid to try a few things when needed. This was not too hard and it will not be for you either.
Good Luck
If you need more information, let me know, I will try to help.
Thanks for reading

I'm glad you had luck with this. I have the same issue, and i've replaced the droid turbo 4 times. I've tried it on 4 or 5 different wifi networks and it doesn't give me any type of speed at all.

Having issues configuring DHCP and with Redundant router

Hello everyone
I am new to Cisco and I am having few problems in configuring my topology in Packet tracer.
I am having redundancy in router and swithes both,
I have assigned one layer2 2960 switch as a VTP server and asssigned VLANs from that switch then assigned ports to the hosts in access layer switches.
Problem 1: If I take my Router1 off I am unable to ping so the pupose of having redundant router does not serve the pupose.
Problem 2 : I need to assign DHCP server for the users who will be connecting wirelessly with Access Points, so can I configure DHCP on Access Points which I am unable to do so in Packet tracer any idea how? / Or shall I configure the DHCP on Router1 and Router2 and exclude the addresses I have assigned to all the hosts connected using ethernet.
Also how can I configure Email server in this tolpolgy and where?
Thank you
A.K

Hi Asif, Jeff is right.
(1) You need to configure either HSRP (Hot standby routing protocol) or VRRP (Wirtual routing redundancy protocol), or GLBP (Gateway load balancing protocol).
With either of this config, you will be able to configure 1 logical IP address, which will act as a gateway on your computers. However, both routers will need different IP's (all within the same subnet). You will also need to create multiple HSRP groups to support all your VLAN's. So one HSRP group per VLAN. The logical IP in the HSRP group will act as the default gateway on computers within the VLAN.
Though I don't think packet tracer supports any of the above configs - FYI it's part of the CCNP Switch sylabus. So the above explaination will make sense after you've got a good understanding of HSRP, VRRP and/or GLBP.
(2) I would recommend setting both the Router as a DHCP server, and configure the Access Point (AP) with a static IP (disable NAT and DHCP on the AP)
(3) In packet tracer, choose the Server icon and check it's properties. You should find an option to enable EMAIL server. Connect it to any of the Distribution layer switches.
Hope this helps get you started on the learning curve :-)

Having issues connecting to folders - with a twist!

Hi there
Im new to the world of macs, and quite frankly loving it so far, however i have a small problem which i would love some hlep with please.
anyway, my problem i see is well documented on a lot of forums and websites, but ive yet to find a solution in the past couple of hours that works for me, so i thought id come ask the people that know best.
Ok so i have my xp machine, which i want to connect to my mac, nothing odd there i hear you say, well, ive gone through the usual steps, tried to map network drive to \\192.168.0.103\grahammasters <-- my "short" name on the mac lol
and not a thing, well thats not true, i get an error message about not finding it, funny thing is if i go to view network computers i see it, so i click it and it says something about not being accessable, and the path could not be found
So where is this different from everyone else then?
well, i go to the other room, sit down, pick up my mac keyboard, click "network" and voilla, i can access the stuff from my pc no problem.
So im stumped, sorry if im just being a complete noob, but i just cant crack this.
Information that may be useful:
- both PC and mac are on the same workgroup
- windows file sharing is enabled on the mac and an account selected
- tried turning firewall off on pc in case that made a difference, but it may be my wireless routers firewall?
- when using personal web site thing, i can connect to the original webpage on the mac from the xp machine.
As far as i can see everything "should" be ok, so any light shed on this would be sweet.
Cheers in advance

An update to the OS was made availible a few days ago which corrected the windows -> mac mini (intel) communications.

Having issues exporting to .FLV with QT conversion

Hi, my client needs an FLV file at 221x165pixels for his website.
i have had no trouble in the past creating FLV files using the QT conversion method, but at this size the file plays flipped diaganolly, with a diaganol line through the picture.
any ideas of what im doing wrong?
cheers

A 221x165 raster is the wrong aspect ratio, and it isn't an integer divisor of anything. Explain to your client that video doesn't work that way.

I'm having issues connecting my database with the OTT utility

I run this command:
ott userid=username/password intype=object.typ outtype=objectOut.typ code=cpp hfile=temp.h cppfile=temp.cpp mapfile=tempmapfile.cpp
and i get this output:
O2T-1118, Unable to register the connection
O2T-102, ERROR: Unable to connect to schema "username"
I can't find any documentation on how to properly register my connection. Can someone help shed some light on what else I need to do to get this to work. I have the correct JDK installed and i've set the

Please indicate the version of OTT (client). Is the database running with the same ORACLE_HOME? Does sqlplus username/password work in that setup?

Anyone having issues syncing iPhone with Microsoft Outlook 2007? iTunes says it is syncing but it will not update calendar or contacts. It just stopped working a few weeks ago.

Anyone having issues syncing iPhone 3GS with Microsoft Outlook 2007? iTunes says it is syncing but it will not update calendar or contacts. It just stopped working a few weeks ago.

I'm glad to hear that I'm not the only person struggling with exact issue. I've rebooted, upgraded, re-installed, pulled all my hair out as nothing works.
The biggest dissapointment with this thread is that nobody seems to have responded with a solution.
And yes I've managed to pull together enough intellegence to tick the box "sync to outlook" in iTunes - still nothing man.
Definately does not sync from phone to PC and is very hit and miss on PC to Phone. In other words now running 2 seperate calendars - Not helpful Jan.

Lync Edge Server External Private Certificate

Hey GURUS!
Please help me out:
I'm having issues accessing Lync from external network.
Mobile clients login fine, but computer clients fail to login.
My current deployment consists in a single 2013 front-end and a single 2013 edge server.
All servers have certificates from my internal CA.
All servers have the root CA certificate installed in the trusted root certificate authority.
I have 2 sip domains, and the edge certificate has both sip domains.
However, when I test from test connectivity.microsoft.com, I get an error regarding the certificate chain.
I can't understand why lync requires a intermediate certificate, if I don't have any published in my organisation.
The certificate path goes: Root CA -> Certificate.
Also, the lync discover test runs with no errors what so ever.
This error on the edge didn't occur when I had lync 2010 running.
Does anyone know how to solve this?
Thanks!
Andrey Santana
edit: i forgot to upload the screenshot

Thiago,
The certificates from the Front End / Reverse Proxy are also from the internal CA and I don't get the error, it actually runs successfully.
Andrey
How did you test the certificates from the Front End and Reverse Proxy Server?
The public website connectivity.microsoft.com need a public certificate.
But if you use private certificate in lab, it could work as long as you install the Root CA certificate on client computer.
Lisa Zheng
TechNet Community Support

Failure to join lync meetings

I have installed the Lync web app to be able to connect to lync meetings with another company. Whenever i try to connect i keep getting "Loading Lync Web App Plug-in has timed out or failed." and it keeps asking me to rejoin. I have the same setup
as others in my office and it works for them so i am thinking there must be an issue with my system. Here is some information from the log file:
Version: 5.0.8308.301
Branch: lcs_w15_onprem
Architecture: x86
BuildType: fre
ProcessID, ThreadID, Timestamp, Level, Function, Component, Message
7184, 7208, 2014-10-01 15:00:34.928, TL_ERROR, <no file info>, PluginFx_AxControl_InProc, CoCreateInstance of outproc component failed with hr code: 80080005
7184, 7208, 2014-10-01 15:00:34.928, TL_INFO, <no file info>, PluginFx_AxControl_InProc, Unloading from release -
7184, 7208, 2014-10-01 15:00:34.928, TL_INFO, <no file info>, PluginFx_AxControl_InProc, Unloading from destructor -
7184, 7208, 2014-10-01 15:03:35.112, TL_ERROR, <no file info>, PluginFx_AxControl_InProc, CoCreateInstance of outproc component failed with hr code: 80080005
7184, 7208, 2014-10-01 15:03:35.112, TL_INFO, <no file info>, PluginFx_AxControl_InProc, Unloading from release -
7184, 7208, 2014-10-01 15:03:35.112, TL_INFO, <no file info>, PluginFx_AxControl_InProc, Unloading from destructor -
I can not find any information on the error code above related to Lync. Anyone have any ideas?

Hi,
You can try as following:
Make sure your browser is set up to allow downloads, and the downloading of encrypted files.
In the Windows Firewall security alert, it’s OK to select Cancel if you don’t have administrator privileges on your computer.
More details:
http://office.microsoft.com/en-001/lync-help/trouble-installing-the-plug-in-HA102900087.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Having issues opening attachments after Mountain Lion Update

Hello,
I am having issues opening up attachments with the correct application in mail. For instance, I received an email with a microsoft word attachment, even though, I have microsoft word installed on my mac it's telling me that it can't open it. So, I have to then open it through preview. Mail also doesn't want to print any attachments from the app itself. I have to open it in Preview first and then print it. I don't remember having to do that in Lion. Is anyone else having this problem or have a fix for this? Or am I just going crazy here? Thanks.

I'm having the same issue. So far all lion has done for me is make all my microsoft office documents un-readable until I upgrade (about $150) and lose my home share capabilities...can anyone assist with this?

I'm having issues with opening a file from an external hard drive

So I'm having issues opening a project which was saved from my friends computer, while when I tried to open the file with CS6 a message poped up saying it was damaged and can't be opened so I updated my premiere pro to CC but when I tried to open it with this version a message saying that the project was saved in a newer version of Premiere Pro and cannot be opened in this version. What can I do to solve this problem?

Update to the latest version. (There are several than can be called CC.)

Sign in issue with Lync Mobile client

Hi guys,
I'm trying to deploy a reverse proxy for mobile and external users, but I am having issues with the mobile client for android. It keeps saying "an unknown error occurred". Please try again.
I've got the log zip file outputted by the client here if someone could have a look and point me in the right direction? I've set
up server farms for the webservices, meet, and dialin.
Desktop clients can log in without any issue btw.
Cheers,
Gareth L. Armstrong

Verify from DNS Configuration and Check what is causing this issue from
Lync Connectivity analyzer
Also to troubleshooting Lync mobility, you can refer below link
http://blogs.technet.com/b/nexthop/archive/2012/02/21/troubleshooting-external-lync-mobility-connectivity-issues-step-by-step.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

[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

Having issues with Lync meetings with external partners

Similar Messages

Maybe you are looking for