Tag Info

Hot answers tagged

3

Yup, it's quite easy with a Receive Connector. I do this on Exchange 2010 at my organization, for example. Server Configuration -> Hub Transport -> Receive Connectors -> New Receive Connector Name it something like "Trusted IP's", leave the default "listen on all interfaces on port 25" rule, then finish the wizard with defaults. Right-click on the ...


2

It's not following RFCs for protocol negotiation at a guess. Perhaps it's attempting to use ESMTP commands without using EHLO or something. One of the better ways to figure out what it is trying to do is to turn on protocol-level logging for the connector that's generating the 500 error. Then retry the connection, and if it throws the error, dig into the ...


2

You likely only need one send connecter, and since your primary mail server is remote, I assume you want to send email through it (aka smarthost). That way you don't need to worry about DNS A records, MX, PTR, SPF, and all the other mail configuration stuff. Just set your send connector smarthost to your mail provider's SMTP server and ensure you are ...


2

I'd tweak the costs myself: "If you have multiple connectors, especially a connector that has a * in the address space (for sending email via your ISP) then you need to adjust the cost carefully. The wildcard SMTP connector with the * should have the highest cost, SMTP Connectors pointing to internal servers should have the lowest (so ...


1

You can't. Exchange 2010 will let you create send connectors for specific destination domains, but not for specific sender addresses. To solve your archiving limit problem, I suggest you setup an smtp server, e.g. Postfix or EXIM. Postfix is fairly easy to setup if all you're doing is routing mail to the internet. If your software is simply sending ...


1

The first question is where does the failure appear? Inside the exchange organisation or in emails sent outside the organisation? So the first question is does the error appear for internal emails, external emails, or both? OWA is obviously an exchange component in its own right, and so the emails are accepted by the exchange system the moment you click ...


1

Things to Try: 1) Stop and restart the SMTP connector. If you configured the exception without restarting this, then chances are the changes will not take affect. 2) From a telnet client like Putty or from the command line Telnet client try passing a SMTP conversation to it - first from the server, then on the PC your client is running on. I recommend ...


1

Are you coding your own client? If so, it's likely because you're not complying with section 2.3.7 of RFC 2821: Lines consist of zero or more data characters terminated by the sequence ASCII character "CR" (hex value 0D) followed immediately by ASCII character "LF" (hex value 0A). ... Conforming implementations MUST NOT recognize or ...


1

I think what you want is two send connectors for * (all domains) separating by permissions. The first would run at the higher priority, usable by all your users (but not anonymous). That connector will be configured to use the proxy program as a smarthost. The proxy program will submit things back to exchange through a receive connector allowing ...


1

If you are looking to do a test installation, then I would just put the Zimbra server on a sub-domain (me@zimbra.mydomain.com) or something for the duration of the test. For an 11-user deployment, I think you're giving yourself an unnecessarily hard time trying to migrate them piecemeal. Try the new system on a sub-domain and take the decision on whether ...



Only top voted, non community-wiki answers of a minimum length are eligible