Exchange 2003, SBS2003 - email works, but aliases do not seem to work.

Working with SBS 2003, running Exchange 2003. This is sort of mixed up, I am just the one managing it now, not the one who initially created it.

The username is firstname but email is routed to [first inital][and last name]@domain.com

I created an SMtp alias of [firstname]@domain.com but when I send mail to it, it will not go. What am I missing, is it because of the mixed up username and email alias that already exists? How can I sort this out? Thanks!!
fecklessnessAsked:
Who is Participating?
 
Simon Butler (Sembee)ConsultantCommented:
Be aware that with Exchange, the default address (in bold) is the only one that you can send email from. All others are aliases for inbound email only.

So if you have an email address in bold of john@example.com, but also john.smith@example.com as an additional address, then you can receive on either, but you cannot send as john.smith@example.com.

If you cannot receive on the additional address, what happens when you try? Is there something between Exchange and the internet that needs to be updated?

Simon.
0
 
Simon Butler (Sembee)ConsultantCommented:
Where exactly did you create this alias?
If you look in ADUC, on the properties of the user then you will see the various email addresses that Exchange will accept email for.

Simon.
0
 
David Paris VicenteSystems and Comunications  Administrator Commented:
I think the best way is through recipient policies and not through alias. Specialy if you have a lot of user´s.


If you give it a try you could check -> Recipient Policies

Regards
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
wilkokCommented:
If you could clarify where you you created the e-mail alias.
If you have added the e-mail address through active directory to a specific user, then it should work correctly.
0
 
fecklessnessAuthor Commented:
Here are screen shots of where I went to see what the usernames were, created the aliases. I showed the difference between the two different users.

Alan can only receieve email at ALastname@domain.com but when he sends email it shows as being from "alan@domain.com"

Steve however sends mail and it shows as from "SLastname@domain.com" and neither one receives mail at firstname@domain.com
0
 
fecklessnessAuthor Commented:
thanks for that tip. now emails from alan send normally.

nothing happens. i get no bounce back error message at all. I feel like that would at least help inform my troubleshooting, but it just disappears into the data ether!
0
 
Simon Butler (Sembee)ConsultantCommented:
Try a telnet test in to the Exchange server directly and see if there any errors returned.
Message tracking might also help here as that will show if the email was seen by Exchange and what Exchange did with it.

Simon.
0
 
fecklessnessAuthor Commented:
sorry for my ignorance, but I don't know how to do a telnet test or what the results might mean.

message tracking appears to be off when i tried to use the message tracking center. how do i enable that?
0
 
fecklessnessAuthor Commented:
Also I did go into recipient policies and added what i thought was the correct way to add the first name alias? http://i.imgur.com/yPWYAEf.png?1
0
 
fecklessnessAuthor Commented:
I did enable message tracking, when I send email to "firstname@domain.com" it doesn't even show in the message tracking. when i search for emals to "firstname@domain.com" all that shows are emails going to "firstletter.lastname@domain.com"

how can i sort this from here or track it?
0
 
wilkokCommented:
Do you run any message filtering? Virus protection with spam filtering on the server?

If you send a message to Steve at the firstname@domain.com is he receiving the messages or is Alan the only one having the issue?
0
 
Simon Butler (Sembee)ConsultantCommented:
Telnet test:
http://exchange.sembee.info/network/telnet-test.asp

You need to send an email that you can track, so specific subject line etc. Then ensure that message tracking is set to log the subject name as well, so you can find the message easily.

Simon.
0
 
wilkokCommented:
On your server open the following and send a test message to alan@domain.com testing the inbound SMTP. please post your results.

https://testconnectivity.microsoft.com
0
 
fecklessnessAuthor Commented:
No there is no message filtering, as far as I am aware.

results from the inbound SMTP.

Testing inbound SMTP mail flow for domain 'alan@xxxxxxx.com'.
       Inbound SMTP mail flow was verified successfully.
       
      Additional Details
       
Elapsed Time: 2206 ms.
       
      Test Steps
       
      Attempting to retrieve DNS MX records for domain 'xxxxxxx.com'.
       One or more MX records were successfully retrieved from DNS.
       
      Additional Details
      Testing Mail Exchanger xxxxxxx.com.inbound10.mxlogic.net.
       This Mail Exchanger was tested successfully.
       
      Additional Details
       
      Test Steps
       
      Attempting to resolve the host name xxxxxxx.com.inbound10.mxlogic.net in DNS.
       The host name resolved successfully.
       
      Additional Details
      Testing TCP port 25 on host xxxxxxx.com.inbound10.mxlogic.net to ensure it's listening and open.
       The port was opened successfully.
       
      Additional Details
      Analyzing SMTP Capabilities for server xxxxxxx.com.inbound10.mxlogic.net:25
       The test passed with some warnings encountered. Please expand the additional details.
       
      Additional Details
       
Unabled to determine SMTP capabilities. Reason: Authentication failed to the SMTP server.
Elapsed Time: 85 ms.
      Attempting to send a test email message to alan@xxxxxxx.com using MX xxxxxxx.com.inbound10.mxlogic.net.
       The test email message was delivered successfully.
       
      Additional Details
      Testing the MX xxxxxxx.com.inbound10.mxlogic.net for open relay by trying to relay to user Admin@TestExchangeConnectivity.com.
       The Open Relay test passed. This MX isn't an open relay.
       
      Additional Details
0
 
fecklessnessAuthor Commented:
the thing i don't get is i don't know why mxlogic would come into play at all here... we do not use their services, though before i joined the company, they did....
0
 
Simon Butler (Sembee)ConsultantCommented:
If you are testing your own domain, then mxlogic must be in the MX records, which means their services are still being used. That would explain why the email doesn't work, as you probably have to update their systems.

Simon.
0
 
fecklessnessAuthor Commented:
Indeed, I've investigated and it appears you are right. Their previous IT provider still has control of this and we'll have to transfer domain and DNS control to our registrar to completely relieve the issue. It looks like MX logic should only control outgoing mail though, but I'm still learning Exchange apparently so maybe it intertwines in a way I do not realize yet.
0
 
Simon Butler (Sembee)ConsultantCommented:
If the MX records are going to MXLOGIC then they control inbound email as well. I would fail to see the point in using them for outbound email only.

Simon.
0
 
fecklessnessAuthor Commented:
I found the setting where the SMTP relay is set and pointed to MX logic... I right clicked on SmallBusiness SMTP connector, Properties, General Tab. I am not finding where I could see how MX Logic is involved with incoming mail, any suggestions where I should look? And is there somewhere else I should look for SMTP settings besides where I've already located it? Much appreciated as I deal with my steep learning curve administrating this functionality.
0
 
Simon Butler (Sembee)ConsultantCommented:
I have already said - it is the MX records. You will not see that in Excahnge, it is in the public DNS.

Simon.
0
 
fecklessnessAuthor Commented:
oh sorry. will check there as soon as we are able. thank you.
0
 
wilkokCommented:
MX logic is usually used by offsite mail filtering services like trend micro interscan messaging hosted security.

You will need to direct your MX record to your external IP address via your domain registrar.

hopefully with this change in affect the e-mails should work.

I would recommend getting the MX records changed and then waiting at least 24hrs and running the  testconnectivity tool again to ensure that the DNS has been updated correctly.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.