Sharing Contacts in Outlook

[NogginBoink]

I dont have time to get into all of this right now, but as stated

1. Outlook is the client software
2. Exchange is added to the client via the normal email accounts wizard "add exchange server"
3. I know for a FACT that Exchange is intercepting emails because as stated, the System Administrator message comes back with an undeliverable message with the information from an email sent through an ISP SMTP (totally different email account). It doesn't do it all the time, its kinda here and there. Sometimes it just all the sudden sends back like 10 undeliverables. Then it waits like 2 days, and sends an system administrator email. But the emails do reach their said destination right after being sent. It would seem to me, regardless of how exchange was set up, it should NOT be seeing emails sent from outlook through a totally different SMTP.

Thanks anyway

Who's getting the undeliverable messages? Local clients, or remote people sending emails to your domain?

Did you read the Exchange logs to find out where the error was coming from? Do you still have those logs?

 

[LikeLinus]

Originally posted by: NogginBoink

I dont have time to get into all of this right now, but as stated

1. Outlook is the client software
2. Exchange is added to the client via the normal email accounts wizard "add exchange server"
3. I know for a FACT that Exchange is intercepting emails because as stated, the System Administrator message comes back with an undeliverable message with the information from an email sent through an ISP SMTP (totally different email account). It doesn't do it all the time, its kinda here and there. Sometimes it just all the sudden sends back like 10 undeliverables. Then it waits like 2 days, and sends an system administrator email. But the emails do reach their said destination right after being sent. It would seem to me, regardless of how exchange was set up, it should NOT be seeing emails sent from outlook through a totally different SMTP.

Thanks anyway

Who's getting the undeliverable messages? Local clients, or remote people sending emails to your domain?

Did you read the Exchange logs to find out where the error was coming from? Do you still have those logs?

Local clients are getting the logs back. I'm not at the actual place to see/send you the log files, but they were kind of odd. They only said "System Administror, this email was undeliverable to xx@xx.com" They also had an attachment icon, but nothing attached. Never did figure that out either

The odd thing is 2 other people get it off and on, but 1 guy inpeticular gets them everytime he sends out a group email. The circumstances are whats confusing. Cause some people can do the same thing, and not get errors, and other people get back errors. So it's not uniform across the board of how the errors happen.

 

[Rogue]

Is he use the GAL (Global Address List) in Exchange to pick the names for these "group e-mails" or is he typing their external ISP provided e-mail address? If he's picking the names off of the Exchange GAL, then that's what's happening. Exchange will choose the shortest, quickest route for delivery of the message, in which case, the shortest route is directly over the server rather than a round trip on the internet. The other users are probably typing the addresses manually or have a PAB that they're drawing the names from or something.

 

[DamageInc]

Okay, sorry for being so late here, but here's an answer, sorta.

qmail is our MTA. Our Linux server is 192.168.1.2 on the LAN. Our Windows 2000 Advanced Server computer is 192.168.1.99. As far as I know, you can't totally remove the MTA part of Exchange. However, there is an option in Outlook to choose how it sends messages. You will have that exchange mailbox thing in your sidebar on the left. It should show your Exchange Mailbox, your Internet Email Personal Folders, and the Public Folders. Somewhere, whether it's in options or services, but somewhere on the tools menu, there's an option to select and move around the order in which Outlook tries to send through different servers.

For example, in our situation, we had to put 192.168.1.2 up at the top and Exchange Server at the bottom. Also, in Active Directory, we made sure that each user's SMTP email address was whatever@domain.com, rather than ADUsername@domain.local.

I hope this clears up a little of your confusion about how we bypass Exchange for email, but I doubt it will, because I typed this quickly and haven't proofread it.

 

[Hossenfeffer]

1. Might try the software, os, or tech support forums (Best to just get into the habit)
2. Maybe ACT! is an option?