jbaello wrote: I've enabled port forwarding on Port 25 (SMTP) and was able to test it via telnet, works fine... I also have a domain registered via godaddy.com - soggyrice.com, and already created my MX record.
jbaello wrote: Outbound at port 25 is fine on server and on LAN client. Result: 220 w2k3en64s03.soggyrice.com Microsoft ESMTP MAIL Service ready at Sun, 1 Jun 2008 15:01:56 -0700
royal wrote: I already told you how to enable event logging, go do it. Did you not even read my post?
jbaello wrote: I noticed that my Send Connectors\Outbound doesn't have a FQDN specified on the general tab, now I'm unsure if I setup the MX record FQDN for this, or my Exchange Server hostname FQDN.
jbaello wrote: royal wrote: I already told you how to enable event logging, go do it. Did you not even read my post? I checked the folder Exchange Server\TransportRoles\Logs\ProtocolLog\SmtpReceive and Send - no log was generated.
royal wrote: jbaello wrote: royal wrote: I already told you how to enable event logging, go do it. Did you not even read my post? I checked the folder Exchange Server\TransportRoles\Logs\ProtocolLog\SmtpReceive and Send - no log was generated. Hm, maybe someone changed the location of the logs. You should be able to do a Get-ransportServer Servername and see where the location is of the logs. You're sure you enabled verbose logging on the relevant connector, right? Here's some more info:http://technet.microsoft.com/en-us/library/bb124531.aspx
royal wrote: Message tracking doesn't write to the Event Logs. It writes to its own log files in which you can launch the Message Tracking portion of the TRA from the EMC Toolbox. SMTP Logs is different than Message Tracking Logs. SMTP logs you should open and import into Excel using the Text Import Wizard.
blargoe wrote: I think it's DNS... Internet DNS thinks the MX for soggy rice.com is at secureserver.net... which if I remember correctly is Go Daddy. You need to give your Exchange Server's Internet IP an A record on your Internet DNS (ie, manage your domain at go daddy and enter it there), and change the MX record at go daddy to that name. Go Daddy's SMTP server is the one that is bouncing you, this is the 64.x.x.x IP address in the NDR message that says that it didn't like the recipient address and it wouldn't relay you. It's never making it back to your Exchange server, the Internet thinks your mail server is Go Daddy. > set type=mx > soggyrice.com Server: dc1.domain.local Address: 10.137.50.10 Non-authoritative answer: soggyrice.com MX preference = 0, mail exchanger = smtp.secureserver.net soggyrice.com MX preference = 10, mail exchanger = mailstore1.secureserver.net