Making a default 'Send' account OTHER than exchange.
Greetings! I've set up several Exchange servers and I have one which is a bit complicated, mixing POP/SMTP with exchange (never a great idea, but no choice here), and hence a problem i don't know the answer to:
The Scenario:
-Exchange 2003 on SBS 2003 (MX pointing to SBS) - 4 users
-Users were to initially 'share' one User's profile (all log in as USER and use same exchange mailbox) however the client wants each workstation to have independant 'read/unread' email. So in other words, if PERSON A on PC1 logs in as USER and reads the mail for the day, PERSON B wants to be able to log into PC2 as USER and have all the mail unread as well. (long story why...not worth the trouble). I don't think this can be done with everyone logging in as USER. (if any ideas on this, it would make things easier)
SO!...my solution was as follows:
1. Create USER1 which gets the 1 email address into its mailbox (which they all want to get)
2. Create USERS 2 - 5 in a distribution group (DG1)
3. Forward all mail from USER to DG1 - (this works)
4. Setup POP accounts as default on each workstation (as well as exchange) sending directly through the ISP so all users can appear to be sending from USER1's email address.
This was going nicely UNTIL i rememebered that if someone sends to USER1 on email@domainname.com, and then one of the users hits REPLY it wants to send out through Exchange. The user CAN select accounts and change it, but i'm wanting to know if there's a default way that it ALWAYS sends out through the POP account even if th email came in through exchange.
It seems crazy, i know...but it's what the client wants...
Thanks!
N.
The Scenario:
-Exchange 2003 on SBS 2003 (MX pointing to SBS) - 4 users
-Users were to initially 'share' one User's profile (all log in as USER and use same exchange mailbox) however the client wants each workstation to have independant 'read/unread' email. So in other words, if PERSON A on PC1 logs in as USER and reads the mail for the day, PERSON B wants to be able to log into PC2 as USER and have all the mail unread as well. (long story why...not worth the trouble). I don't think this can be done with everyone logging in as USER. (if any ideas on this, it would make things easier)
SO!...my solution was as follows:
1. Create USER1 which gets the 1 email address into its mailbox (which they all want to get)
2. Create USERS 2 - 5 in a distribution group (DG1)
3. Forward all mail from USER to DG1 - (this works)
4. Setup POP accounts as default on each workstation (as well as exchange) sending directly through the ISP so all users can appear to be sending from USER1's email address.
This was going nicely UNTIL i rememebered that if someone sends to USER1 on email@domainname.com, and then one of the users hits REPLY it wants to send out through Exchange. The user CAN select accounts and change it, but i'm wanting to know if there's a default way that it ALWAYS sends out through the POP account even if th email came in through exchange.
It seems crazy, i know...but it's what the client wants...
Thanks!
N.
In the outlook email accounts set the pop3 account as Default, that will set the pop3 account as the default email account that all message that get created will get sent with.
ASKER
Yep already done that - but pls see this paragraph:
This was going nicely UNTIL i rememebered that if someone sends to USER1 on email@domainname.com, and then one of the users hits REPLY it wants to send out through Exchange. The user CAN select accounts and change it, but i'm wanting to know if there's a default way that it ALWAYS sends out through the POP account even if th email came in through exchange.
This was going nicely UNTIL i rememebered that if someone sends to USER1 on email@domainname.com, and then one of the users hits REPLY it wants to send out through Exchange. The user CAN select accounts and change it, but i'm wanting to know if there's a default way that it ALWAYS sends out through the POP account even if th email came in through exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.