Hi,
I am having Exchange Server 2013 installed in my network. Suddenly It stopped receiving external emails, while users are able to send and receive internal emails and can send emails to external domains.
I have restarted all the services one by one but no luck.
Any idea please.
Hi,
I have a 2013 installed and working - both with incoming mail and outgoing mail when using Outlook and similar clients.
No problems sending mail from and to either internal or external domains. However, I want to authenticate with the standard SMTP server with a username + password and send e-mail using "standard clients".
I cannot get this to work. In code, when I authenticate through SMTP (user/pass) and tries to send an email from "user@mydomain.com" to "user@anotherdomain.com", I get the error:
Mailbox unavailable. The server response was: 5.7.1 Unable to relay.
I don't really know how to set this up to get it working. In an existing Exchange 2007, I had no problem setting this up, but I cannot get it to work in 2013. If I add "*" to accepted domain, it works, of course, but that gives me an Open Relay.
I have a default send connector, mapped to the SMTP domain "*".
How do I configure so that all authenticated users can relay freely?
Hi,
E2K13CU1 with default settings added to working existing E2K10SP3 organization.
Mail doesn't leave Drafts folder (sent form OWA).
Telnet to server at port 25 responds after MAIL FROM: with:
421 4.3.2 Service not active (exactly - didn't found anything like this anywhere)
I checked DNS (also set custom DNS config in E2K13 ecp, all services are running, no custom AV, no low disk space, no events.
Thank you
Richard
Hey all, I am hoping someone could shed some light on this issue.
Long story short, (I know this is a 2013 forum but I am doing this on 2003, I still hope someone can help)
I created an email alias for one user (intern) when that user was finished I tried removing it from that user and adding it to another user....exchange allowed me to do this and did not give any errors.
However,
Now it seems exchange thinks that alias is still attached to the old user and as such does not route to the new intern and does not give any error when sent to that address. Is there any way I could fix this?
Thanks a lot!
JD
Help !
recently moved to exchnage 2010. Is there a way of stopping an ndr being sent and the mail being accepted to users whos mailbox is full. We have critical staff that are filling their boxes up and not getting critical mail because a ndr is sent out!
any help would be appreciated
thanks
S
New 2013 implementation... Two Servers (Front End and Back End) both running Exchange 2013.
I am having trouble sending a local AD Exchange mailbox mail to external SMTP address. I have tried several options.. I have created an "contact" as was required in previous versions. I have created new AD accounts with external SMTP addresses, I have also attempted to use the scriptlet:
Set-Mailbox -Identity "%AD-USER%" -DeliverToMailboxAndForward $true -ForwardingSMTPAddressexternaluser@mail.com (%AD-USER% was actual AD Username/mailbox) andexternaluser@mail.com was actual receipient SMTP address (username@gmail.com)
Local AD Mailbox receives the mail appropriately however I have enabled forwarding everyway I know how and nothing seems to work. If I send mail straight from my account to the destination SMTP address, they get it; just not if it is sent to the local AD account then forwarded via -DeliverToMailboxAndForward command...
Please help.. I have several users that I need to have their mail CC'd to an external SMTP address.. Previous versions of Exchange required a "Contact" to be created and then the mailbox forwarded to that contact, which had a SMPT mail address...
Im not adverse to implementing via powershell if I can just get it to work... Any suggestions are greatly appreciated and needed.
My company is getting migrated(abc) to another company(xyz) and its name also gonging to be change. We have a exchange 2010 server , and each user have 2 email ID
i.e. Robert@abc.com and Robert@xyz.com
my primary email address is robert@xyz.com but still there are so many people sending email to robert@abc.com. Now @abc.com will be no more after some time.
I want to set rule on server that if some one sends mail to @abc.com he will get auto reply saying “pls send mail to @xyz.com instead of @abc.com as it will be no more exist.”
Hi,
We have more than 50 Exchange servers in our environment and now need to renew my Exchange 2010 certificate on the all the servers.
Please suggest me on the number of entries can be added in the SAN entries.
Regards
Neeraj Mehra
Neeraj Mehra
Benjilafouine
Hello,
I have a little problem with our Exchange Environment. Every server in our setup has three roles (CAS,MBX,HUB) but only on one server action descriptions in Transport Rules are in ...russian language. It's really weird, because we have only English version on servers. Regional setting are Polish (our native language). We don't have any admin who use other language except polish or english. All rules are affected on this server (old one or if I start create new one) but all rules are working fine.
Any ideas what is going on?
Regards
Arek
In my research Attachment Size Limit and Message Size Limit appear to be referenced the same...frankly speaking there is no difference and Exchange 2010 doesn't explicitly state "Attachment Size Limit" anywhere in EMC.
And one other question, does Exchange inflate an attachment up to 30%? I have 10MB Message Size Limits in place for all users but when they attach a file smaller than 10MB they are rejected
Hello,
I have a question about the protocol used by the Exchange Mail forwarding ( ForwardingAddress)
If I disable my mailbox's protocols ActiveSync, OWA, IMAP, POP and MAPI, could the mail transfer still work?
Thank you.
I have a Windows Server 2012 Server with Exchange 2013 CU2, Revision 2.
I can send mail from Exchange 2013 to users on Exchange 2013, I can send mail from Exchange 2013 to people on the Internet.
I can send mail from Exchange 2007 to users on Exchange 2007, I can send mail from Exchange 2007 to users on Exchange 2013, I can send mail from Exchange 2007 to the Internet.
I cannot send mail from Exchange 2013 users to Exchange 2007 users. The message is stuck in SMTP Relay to Mailbox Delivery Group, and it receives a 421 4.4.2 Connection dropped due to socket error.
I have verified that there are MX records for each server in the domain. The two servers are next to one another and connected to the same Gigabit switch.
Looking at the receive connector logs it gets to passing the allowed forms of Authentication, the Exchange 2013 server sends back X-ANONYMOUSTLS - the Exchange 2007 server passes the certificate, last line shows - LOCAL and that is all. I can see 3 attempts in the log during each retry to send the mail from Exchange 2013.
I have tried to enable Verbose logging on the Exchange 2013 Send connector, and have not been able to see a log created for this delivery from Exchange 2013 to Exchange 2007.
Exchange 2013, has been upgraded to CU1, CU2, and CU2 Revision 2. Exchange 2007 has the latest SP and updates.
I created a self signed certificate and assigned that to SMTP on Exchange 2013 in case it did not like one of the names of that server being missing from the Certificate created during install. That did not help.
Hi Experts,
At what criteria IP's or Domains are getting black listed? since i have an meeting with my manager. he requested me to collect the the possible criteria. Can i have the reasons ASAP.
Thanks, Venkatesh. "Hardwork Never Fails"
Can you tell when an email address was set to begin forwarding?
Here is the scenario - I have a hosted email environment with a couple thousand users on rackspace
- I am migrating all the users to a new dedicated service also on rackspace. using the same exact email address.
the migration will last a couple of weeks. My problem is that if I repoint autodiscover to the new environment I get a certificate error on my (old) hosted email and the clients will not connect to exchange.
Is there a way to have both systems using autodiscover? or can I rename autodiscover to something else on the new system?
Hi,
Hoping someone can help me with a little issue I have please?
Our Exchange admin has left the firm and I have picked this up with very little experience of Exchange.
In short we have moved our internal SMTP relay from 2003 to 2010 and come up against some issues, all of which I have overcome bar one, our Finance team send various emails from their billing system to users and themselves in various ways, Anonymous, sending as an internal user to the same internal user but relaying with an admin account etc etc.
They also send emails to internal users as a completely different made up but relavant name to the actual firms domain, for example, our internal domain is company.com and all in internal users SMTP address is company.com, however they need their finance system to relay to users as an address from finance.com, this isn't a mailbox it's just a name their system uses and sends via our internal smtp relay/receive connectors.
I have setup a new internal receive connector that applies to only their finance subnet allowing anonymous, however I'm at a loss as to how to allow the finance.com domain to relay to our internal users, I'm assuming I need to create an authoritative domain or similar but do not just want to go playing around on a live environment.
Any help would be greatly received.
Many Thanks
Steve
Hi there,
I am struggling with understanding security implication of the anonymous permission on the default receive connector. I am looking for a steer in the right direction:)
I have exchange 2010 SP3 stand alone server with hub transport behind a firewall (no edge). We do have a 3rd party service (spam filter) that relays clean emails to our exchange server.
Currently i have a default setup receive connector that is configured to receive emails for any IP and a rule in the firewall to relay traffic on port 25 to the exchange server.
Recently i came to realization that all of my internal devices such as multi functional printers, UPS, NAS, etc are able to send notification emails to me without any authentication involved. That would mean, if say a virus hit any of my client computers, it would have a green light to spam everyone internally or externally without much effort!
Is this correct?
Obviously, if i uncheck anonymous permission in default receive connector, my server won't be able to receive anything at all.
Are there any best practices to secure this flaw? limit which anonymous INTERNAL devices can use my exchange as a relay? how about External anonymous clients, is it a concern?
Silvio Tavares - Analista de Sistemas
