RE: Looking for advice re HR Luser request
I concur with the DL suggestion. I have run into this issue, and it can be a headache. I solved it here in a somewhat small organization by using aliases for certain users and we did change the address people were sending resumes to, but as you can imagine, there was some swapping of messages which still needed to be done as some resumes went to the wrong individual... Force them somehow to use one address, I'm going to try that. -Original Message- From: Ray Zorz [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 7:13 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I had something similiar with about 50 different information type e-mail addresses that were published on a couple websites. I think you were right on with the DL idea. -Original Message- From: Martin Blackstone [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 2:36 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I agree. I don't like that idea either. But now they are reaping what they sew, and it sounds like they don't want to do THEIR jobs. Instead of doing any forwards or CRs, just create a single mailbox. Put everything in there, and tell them how to open it to read mail. Then they can do it at their convenience. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:22 PM To: MS-Exchange Admin Issues Subject: Looking for advice re HR Luser request Running Exchange 5.5, SP4 on NT4 SP6a. Our HR department currently has an email address set up for job postings so people can email their resume. They are getting so many that they no longer want to process them. What they want to do is create a new email address for each posting that would go to the appropriate person in the department with the opening. The do not wish to use the following suggestions I gave to them: 1. Just use the email of the person in the department you want to receive the resumes. 2. We could create a few distribution lists (for running multiple jobs at once) and they can add and remove users at will. 3. They could set up rules on the current mailbox to route based on job posting number or some other piece of information. I don't like the idea of creating an email address every time they do a job posting. So, I'm wondering if anyone else has had to deal with a similar situation and if you found a workable solution. TIA, MJ List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.343 / Virus Database: 190 - Release Date: 3/22/2002 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.343 / Virus Database: 190 - Release Date: 3/22/2002 List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Looking for advice re HR Luser request
What I find kinda weird was that HR didn't want to even see the resumes. But, regardless, maybe the company can designate various department heads (actually, probably the AA's) to receive them. Salesjobs, HRjobs, Techjobs, etc. @companyname.com. Hopefully they'll do that and actually tell the exchange admin. Since I'm unemployed, I've been sending out a buncha resumes. Amazing to me that companies put e-mail addresses out there, and I get errors that they're not active. Ironically, one was for a Exchange admin. -Original Message- From: Desiree Herrmann [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 27, 2002 8:43 AM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I concur with the DL suggestion. I have run into this issue, and it can be a headache. I solved it here in a somewhat small organization by using aliases for certain users and we did change the address people were sending resumes to, but as you can imagine, there was some swapping of messages which still needed to be done as some resumes went to the wrong individual... Force them somehow to use one address, I'm going to try that. -Original Message- From: Ray Zorz [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 7:13 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I had something similiar with about 50 different information type e-mail addresses that were published on a couple websites. I think you were right on with the DL idea. -Original Message- From: Martin Blackstone [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 2:36 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I agree. I don't like that idea either. But now they are reaping what they sew, and it sounds like they don't want to do THEIR jobs. Instead of doing any forwards or CRs, just create a single mailbox. Put everything in there, and tell them how to open it to read mail. Then they can do it at their convenience. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:22 PM To: MS-Exchange Admin Issues Subject: Looking for advice re HR Luser request Running Exchange 5.5, SP4 on NT4 SP6a. Our HR department currently has an email address set up for job postings so people can email their resume. They are getting so many that they no longer want to process them. What they want to do is create a new email address for each posting that would go to the appropriate person in the department with the opening. The do not wish to use the following suggestions I gave to them: 1. Just use the email of the person in the department you want to receive the resumes. 2. We could create a few distribution lists (for running multiple jobs at once) and they can add and remove users at will. 3. They could set up rules on the current mailbox to route based on job posting number or some other piece of information. I don't like the idea of creating an email address every time they do a job posting. So, I'm wondering if anyone else has had to deal with a similar situation and if you found a workable solution. TIA, MJ List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.343 / Virus Database: 190 - Release Date: 3/22/2002 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.343 / Virus Database: 190 - Release Date: 3/22/2002 List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.343 / Virus Database: 190 - Release Date: 3/22/2002 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.343 / Virus Database: 190 - Release Date: 3/22/2002 List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Looking for advice re HR Luser request
Title: RE: Looking for advice re HR Luser request Here's what I did for my HR dept. I set up a public folder for the HR dept and under that a folder for each type of resume they would get (we have 10 categories), i.e. HRjobs or ITjobs or Manufjobs, etc. Each folder has its corresponding smtp address that the department uses in its postings. The HR folder tree is restricted to allow access to only the HR personnel. You have to give the contributor permission to the default account in each folder so that anyone can post to the folder. The HR people responsible for looking at resumes are trained to look at the folders for new postings. It works great and I haven't had to do anything since it was set up, they even clean out the folders once in a while. Hope this helps. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 5:46 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I agree with you and that's how they are currently doing it - single mailbox that someone checks. I guess they are SOO overworked up there, that they just don't have the time to continue doing it this way. ;-) -Original Message- From: Martin Blackstone [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:36 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I agree. I don't like that idea either. But now they are reaping what they sew, and it sounds like they don't want to do THEIR jobs. Instead of doing any forwards or CRs, just create a single mailbox. Put everything in there, and tell them how to open it to read mail. Then they can do it at their convenience. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:22 PM To: MS-Exchange Admin Issues Subject: Looking for advice re HR Luser request Running Exchange 5.5, SP4 on NT4 SP6a. Our HR department currently has an email address set up for job postings so people can email their resume. They are getting so many that they no longer want to process them. What they want to do is create a new email address for each posting that would go to the appropriate person in the department with the opening. The do not wish to use the following suggestions I gave to them: 1. Just use the email of the person in the department you want to receive the resumes. 2. We could create a few distribution lists (for running multiple jobs at once) and they can add and remove users at will. 3. They could set up rules on the current mailbox to route based on job posting number or some other piece of information. I don't like the idea of creating an email address every time they do a job posting. So, I'm wondering if anyone else has had to deal with a similar situation and if you found a workable solution. TIA, MJ List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Looking for advice re HR Luser request
Title: RE: Looking for advice re HR Luser request I thought his problem was HR doesn't want to look at them anymore. They just want the resumes to go to the respective managers. -Original Message-From: Ulm, Jeff [mailto:[EMAIL PROTECTED]]Sent: Wednesday, March 27, 2002 12:09 PMTo: MS-Exchange Admin IssuesSubject: RE: Looking for advice re HR Luser request Here's what I did for my HR dept. I set up a public folder for the HR dept and under that a folder for each type of resume they would get (we have 10 categories), i.e. HRjobs or ITjobs or Manufjobs, etc. Each folder has its corresponding smtp address that the department uses in its postings. The HR folder tree is restricted to allow access to only the HR personnel. You have to give the contributor permission to the default account in each folder so that anyone can post to the folder. The HR people responsible for looking at resumes are trained to look at the folders for new postings. It works great and I haven't had to do anything since it was set up, they even clean out the folders once in a while. Hope this helps. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 5:46 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I agree with you and that's how they are currently doing it - single mailbox that someone checks. I guess they are SOO overworked up there, that they just don't have the time to continue doing it this way. ;-) -Original Message- From: Martin Blackstone [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:36 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I agree. I don't like that idea either. But now they are reaping what they sew, and it sounds like they don't want to do THEIR jobs. Instead of doing any forwards or CRs, just create a single mailbox. Put everything in there, and tell them how to open it to read mail. Then they can do it at their convenience. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:22 PM To: MS-Exchange Admin Issues Subject: Looking for advice re HR Luser request Running Exchange 5.5, SP4 on NT4 SP6a. Our HR department currently has an email address set up for job postings so people can email their resume. They are getting so many that they no longer want to process them. What they want to do is create a new email address for each posting that would go to the appropriate person in the department with the opening. The do not wish to use the following suggestions I gave to them: 1. Just use the email of the person in the department you want to receive the resumes. 2. We could create a few distribution lists (for running multiple jobs at once) and they can add and remove users at will. 3. They could set up rules on the current mailbox to route based on job posting number or some other piece of information. I don't like the idea of creating an email address every time they do a job posting. So, I'm wondering if anyone else has had to deal with a similar situation and if you found a workable solution. TIA, MJ List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Looking for advice re HR Luser request
Title: RE: Looking for advice re HR Luser request This may help them manage their resumes better. Our HR department has to review all resumes before they are sent on to the hiring manager. This solution can still be used instead of a routing solution, you just have to give the hiring managers access to the corresponding folders as well. If it's done by department then it's manageable. -Original Message- From: Ray Zorz [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 27, 2002 2:14 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I thought his problem was HR doesn't want to look at them anymore. They just want the resumes to go to the respective managers. -Original Message- From: Ulm, Jeff [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 27, 2002 12:09 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request Here's what I did for my HR dept. I set up a public folder for the HR dept and under that a folder for each type of resume they would get (we have 10 categories), i.e. HRjobs or ITjobs or Manufjobs, etc. Each folder has its corresponding smtp address that the department uses in its postings. The HR folder tree is restricted to allow access to only the HR personnel. You have to give the contributor permission to the default account in each folder so that anyone can post to the folder. The HR people responsible for looking at resumes are trained to look at the folders for new postings. It works great and I haven't had to do anything since it was set up, they even clean out the folders once in a while. Hope this helps. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 5:46 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I agree with you and that's how they are currently doing it - single mailbox that someone checks. I guess they are SOO overworked up there, that they just don't have the time to continue doing it this way. ;-) -Original Message- From: Martin Blackstone [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:36 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I agree. I don't like that idea either. But now they are reaping what they sew, and it sounds like they don't want to do THEIR jobs. Instead of doing any forwards or CRs, just create a single mailbox. Put everything in there, and tell them how to open it to read mail. Then they can do it at their convenience. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:22 PM To: MS-Exchange Admin Issues Subject: Looking for advice re HR Luser request Running Exchange 5.5, SP4 on NT4 SP6a. Our HR department currently has an email address set up for job postings so people can email their resume. They are getting so many that they no longer want to process them. What they want to do is create a new email address for each posting that would go to the appropriate person in the department with the opening. The do not wish to use the following suggestions I gave to them: 1. Just use the email of the person in the department you want to receive the resumes. 2. We could create a few distribution lists (for running multiple jobs at once) and they can add and remove users at will. 3. They could set up rules on the current mailbox to route based on job posting number or some other piece of information. I don't like the idea of creating an email address every time they do a job posting. So, I'm wondering if anyone else has had to deal with a similar situation and if you found a workable solution. TIA, MJ List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Looking for advice re HR Luser request
Title: Message see second email from Mjohnston on this point. -Original Message-From: Ulm, Jeff [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 27, 2002 11:48 AMTo: MS-Exchange Admin IssuesSubject: RE: Looking for advice re HR Luser request This may help them manage their resumes better. Our HR department has to review all resumes before they are sent on to the hiring manager. This solution can still be used instead of a routing solution, you just have to give the hiring managers access to the corresponding folders as well. If it's done by department then it's manageable. -Original Message-From: Ray Zorz [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 27, 2002 2:14 PMTo: MS-Exchange Admin IssuesSubject: RE: Looking for advice re HR Luser request I thought his problem was HR doesn't want to look at them anymore. They just want the resumes to go to the respective managers. -Original Message-From: Ulm, Jeff [mailto:[EMAIL PROTECTED]]Sent: Wednesday, March 27, 2002 12:09 PMTo: MS-Exchange Admin IssuesSubject: RE: Looking for advice re HR Luser request Here's what I did for my HR dept. I set up a public folder for the HR dept and under that a folder for each type of resume they would get (we have 10 categories), i.e. HRjobs or ITjobs or Manufjobs, etc. Each folder has its corresponding smtp address that the department uses in its postings. The HR folder tree is restricted to allow access to only the HR personnel. You have to give the contributor permission to the default account in each folder so that anyone can post to the folder. The HR people responsible for looking at resumes are trained to look at the folders for new postings. It works great and I haven't had to do anything since it was set up, they even clean out the folders once in a while. Hope this helps. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 5:46 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I agree with you and that's how they are currently doing it - single mailbox that someone checks. I guess they are SOO overworked up there, that they just don't have the time to continue doing it this way. ;-) -Original Message- From: Martin Blackstone [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:36 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I agree. I don't like that idea either. But now they are reaping what they sew, and it sounds like they don't want to do THEIR jobs. Instead of doing any forwards or CRs, just create a single mailbox. Put everything in there, and tell them how to open it to read mail. Then they can do it at their convenience. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:22 PM To: MS-Exchange Admin Issues Subject: Looking for advice re HR Luser request Running Exchange 5.5, SP4 on NT4 SP6a. Our HR department currently has an email address set up for job postings so people can email their resume. They are getting so many that they no longer want to process them. What they want to do is create a new email address for each posting that would go to the appropriate person in the department with the opening. The do not wish to use the following suggestions I gave to them: 1. Just use the email of the person in the department you want to receive the resumes. 2. We could create a few distribution lists (for running multiple jobs at once) and they can add and remove users at will. 3. They could set up rules on the current mailbox to route based on job posting number or some other piece of information. I don't like the idea of creating an email address every time they do a job posting. So, I'm wondering if anyone else has had to deal with a similar situation and if you found a workable solution. TIA, MJ List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htmList Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Looking for advice re HR Luser request
Title: RE: Looking for advice re HR Luser request That sounds like a really good idea. I think I'll suggest it and see if it sticks. Thanks. -Original Message-From: Ulm, Jeff [mailto:[EMAIL PROTECTED]]Sent: Wednesday, March 27, 2002 11:09 AMTo: MS-Exchange Admin IssuesSubject: RE: Looking for advice re HR Luser request Here's what I did for my HR dept. I set up a public folder for the HR dept and under that a folder for each type of resume they would get (we have 10 categories), i.e. HRjobs or ITjobs or Manufjobs, etc. Each folder has its corresponding smtp address that the department uses in its postings. The HR folder tree is restricted to allow access to only the HR personnel. You have to give the contributor permission to the default account in each folder so that anyone can post to the folder. The HR people responsible for looking at resumes are trained to look at the folders for new postings. It works great and I haven't had to do anything since it was set up, they even clean out the folders once in a while. Hope this helps. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 5:46 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I agree with you and that's how they are currently doing it - single mailbox that someone checks. I guess they are SOO overworked up there, that they just don't have the time to continue doing it this way. ;-) -Original Message- From: Martin Blackstone [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:36 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I agree. I don't like that idea either. But now they are reaping what they sew, and it sounds like they don't want to do THEIR jobs. Instead of doing any forwards or CRs, just create a single mailbox. Put everything in there, and tell them how to open it to read mail. Then they can do it at their convenience. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:22 PM To: MS-Exchange Admin Issues Subject: Looking for advice re HR Luser request Running Exchange 5.5, SP4 on NT4 SP6a. Our HR department currently has an email address set up for job postings so people can email their resume. They are getting so many that they no longer want to process them. What they want to do is create a new email address for each posting that would go to the appropriate person in the department with the opening. The do not wish to use the following suggestions I gave to them: 1. Just use the email of the person in the department you want to receive the resumes. 2. We could create a few distribution lists (for running multiple jobs at once) and they can add and remove users at will. 3. They could set up rules on the current mailbox to route based on job posting number or some other piece of information. I don't like the idea of creating an email address every time they do a job posting. So, I'm wondering if anyone else has had to deal with a similar situation and if you found a workable solution. TIA, MJ List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Looking for advice re HR Luser request
Title: RE: Looking for advice re HR Luser request This idea still didn't fly. I think what they really want is for someone else to do their job, but this is what my boss wants to do: Use another domain for all the job posting email addresses, like nhrajobs.com or whatever (maybe LazyPeople.com - haha). Anyway, we would have our ISP set up an MX record in their DNS for this domain and point it to a server that has the SMTP service installed. So far, fine, but here's where I can't figure out if this will work or not. ... Once the mail hits the SMTP server, he wants whatever addresses we have set up to route to specific users in the nhra.com (Exchange). As far as I can tell, you can't set up users with the Microsoft SMTP service like you can with Exchange. So, I don't think this idea will work. If I am correct, is there some other (cheap or free) SMTP program that will do what he wants? TIA, MJ -Original Message-From: Ulm, Jeff [mailto:[EMAIL PROTECTED]]Sent: Wednesday, March 27, 2002 11:09 AMTo: MS-Exchange Admin IssuesSubject: RE: Looking for advice re HR Luser request Here's what I did for my HR dept. I set up a public folder for the HR dept and under that a folder for each type of resume they would get (we have 10 categories), i.e. HRjobs or ITjobs or Manufjobs, etc. Each folder has its corresponding smtp address that the department uses in its postings. The HR folder tree is restricted to allow access to only the HR personnel. You have to give the contributor permission to the default account in each folder so that anyone can post to the folder. The HR people responsible for looking at resumes are trained to look at the folders for new postings. It works great and I haven't had to do anything since it was set up, they even clean out the folders once in a while. Hope this helps. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 5:46 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I agree with you and that's how they are currently doing it - single mailbox that someone checks. I guess they are SOO overworked up there, that they just don't have the time to continue doing it this way. ;-) -Original Message- From: Martin Blackstone [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:36 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I agree. I don't like that idea either. But now they are reaping what they sew, and it sounds like they don't want to do THEIR jobs. Instead of doing any forwards or CRs, just create a single mailbox. Put everything in there, and tell them how to open it to read mail. Then they can do it at their convenience. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:22 PM To: MS-Exchange Admin Issues Subject: Looking for advice re HR Luser request Running Exchange 5.5, SP4 on NT4 SP6a. Our HR department currently has an email address set up for job postings so people can email their resume. They are getting so many that they no longer want to process them. What they want to do is create a new email address for each posting that would go to the appropriate person in the department with the opening. The do not wish to use the following suggestions I gave to them: 1. Just use the email of the person in the department you want to receive the resumes. 2. We could create a few distribution lists (for running multiple jobs at once) and they can add and remove users at will. 3. They could set up rules on the current mailbox to route based on job posting number or some other piece of information. I don't like the idea of creating an email address every time they do a job posting. So, I'm wondering if anyone else has had to deal with a similar situation and if you found a workable solution. TIA, MJ List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Looking for advice re HR Luser request
Title: Message Why not add the second domain to your existing Exchange server (different container) and do the redirects from there? Otherwise, Sendmail and qMail will both do it though they are Linux solutions. I haven't messed with the MS SMTP service so can't say anything about that. -sp -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 27, 2002 3:54 PMTo: MS-Exchange Admin IssuesSubject: RE: Looking for advice re HR Luser request This idea still didn't fly. I think what they really want is for someone else to do their job, but this is what my boss wants to do: Use another domain for all the job posting email addresses, like nhrajobs.com or whatever (maybe LazyPeople.com - haha). Anyway, we would have our ISP set up an MX record in their DNS for this domain and point it to a server that has the SMTP service installed. So far, fine, but here's where I can't figure out if this will work or not. ... Once the mail hits the SMTP server, he wants whatever addresses we have set up to route to specific users in the nhra.com (Exchange). As far as I can tell, you can't set up users with the Microsoft SMTP service like you can with Exchange. So, I don't think this idea will work. If I am correct, is there some other (cheap or free) SMTP program that will do what he wants? TIA, MJ -Original Message-From: Ulm, Jeff [mailto:[EMAIL PROTECTED]]Sent: Wednesday, March 27, 2002 11:09 AMTo: MS-Exchange Admin IssuesSubject: RE: Looking for advice re HR Luser request Here's what I did for my HR dept. I set up a public folder for the HR dept and under that a folder for each type of resume they would get (we have 10 categories), i.e. HRjobs or ITjobs or Manufjobs, etc. Each folder has its corresponding smtp address that the department uses in its postings. The HR folder tree is restricted to allow access to only the HR personnel. You have to give the contributor permission to the default account in each folder so that anyone can post to the folder. The HR people responsible for looking at resumes are trained to look at the folders for new postings. It works great and I haven't had to do anything since it was set up, they even clean out the folders once in a while. Hope this helps. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 5:46 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I agree with you and that's how they are currently doing it - single mailbox that someone checks. I guess they are SOO overworked up there, that they just don't have the time to continue doing it this way. ;-) -Original Message- From: Martin Blackstone [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:36 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I agree. I don't like that idea either. But now they are reaping what they sew, and it sounds like they don't want to do THEIR jobs. Instead of doing any forwards or CRs, just create a single mailbox. Put everything in there, and tell them how to open it to read mail. Then they can do it at their convenience. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:22 PM To: MS-Exchange Admin Issues Subject: Looking for advice re HR Luser request Running Exchange 5.5, SP4 on NT4 SP6a. Our HR department currently has an email address set up for job postings so people can email their resume. They are getting so many that they no longer want to process them. What they want to do is create a new email address for each posting that would go to the appropriate person in the department with the opening. The do not wish to use the following suggestions I gave to them: 1. Just use the email of the person in the department you want to receive the resumes. 2. We could create a few distribution lists (for running multiple jobs at once) and they can add and remove users at will. 3. They could set up rules on the current mailbox to route based on job posting number or some other piece of information. I don't like the idea of creating an email address every time they do a job posting. So, I'm wondering if anyone else has had to deal with a similar situation and if you found a workable solution. TIA, MJ List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ
RE: Looking for advice re HR Luser request
Title: Message What I was hoping to avoid was getting any NDR email from the other domain. I figured I could add the domain to the IMS connectorproperties, but then any changes apply to both domains. I still need to get NDRs for nhra.com. Is there another way to add it so that the properties of that domain are independent of the nhra.com domain? -Original Message-From: Steven Peck DNET [mailto:[EMAIL PROTECTED]]Sent: Wednesday, March 27, 2002 4:05 PMTo: MS-Exchange Admin IssuesSubject: RE: Looking for advice re HR Luser request Why not add the second domain to your existing Exchange server (different container) and do the redirects from there? Otherwise, Sendmail and qMail will both do it though they are Linux solutions. I haven't messed with the MS SMTP service so can't say anything about that. -sp -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 27, 2002 3:54 PMTo: MS-Exchange Admin IssuesSubject: RE: Looking for advice re HR Luser request This idea still didn't fly. I think what they really want is for someone else to do their job, but this is what my boss wants to do: Use another domain for all the job posting email addresses, like nhrajobs.com or whatever (maybe LazyPeople.com - haha). Anyway, we would have our ISP set up an MX record in their DNS for this domain and point it to a server that has the SMTP service installed. So far, fine, but here's where I can't figure out if this will work or not. ... Once the mail hits the SMTP server, he wants whatever addresses we have set up to route to specific users in the nhra.com (Exchange). As far as I can tell, you can't set up users with the Microsoft SMTP service like you can with Exchange. So, I don't think this idea will work. If I am correct, is there some other (cheap or free) SMTP program that will do what he wants? TIA, MJ -Original Message-From: Ulm, Jeff [mailto:[EMAIL PROTECTED]]Sent: Wednesday, March 27, 2002 11:09 AMTo: MS-Exchange Admin IssuesSubject: RE: Looking for advice re HR Luser request Here's what I did for my HR dept. I set up a public folder for the HR dept and under that a folder for each type of resume they would get (we have 10 categories), i.e. HRjobs or ITjobs or Manufjobs, etc. Each folder has its corresponding smtp address that the department uses in its postings. The HR folder tree is restricted to allow access to only the HR personnel. You have to give the contributor permission to the default account in each folder so that anyone can post to the folder. The HR people responsible for looking at resumes are trained to look at the folders for new postings. It works great and I haven't had to do anything since it was set up, they even clean out the folders once in a while. Hope this helps. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 5:46 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I agree with you and that's how they are currently doing it - single mailbox that someone checks. I guess they are SOO overworked up there, that they just don't have the time to continue doing it this way. ;-) -Original Message- From: Martin Blackstone [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:36 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I agree. I don't like that idea either. But now they are reaping what they sew, and it sounds like they don't want to do THEIR jobs. Instead of doing any forwards or CRs, just create a single mailbox. Put everything in there, and tell them how to open it to read mail. Then they can do it at their convenience. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:22 PM To: MS-Exchange Admin Issues Subject: Looking for advice re HR Luser request Running Exchange 5.5, SP4 on NT4 SP6a. Our HR department currently has an email address set up for job postings so people can email their resume. They are getting so many that they no longer want to process them. What they want to do is create a new email address for each posting that would go to the appropriate person in the department with the opening. The do not wish to use the following suggestions I gave to them: 1. Just use the email of the person in the department you want to receive the resumes. 2. We could create a few distribution lists (for running
RE: Looking for advice re HR Luser request
I agree. I don't like that idea either. But now they are reaping what they sew, and it sounds like they don't want to do THEIR jobs. Instead of doing any forwards or CRs, just create a single mailbox. Put everything in there, and tell them how to open it to read mail. Then they can do it at their convenience. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:22 PM To: MS-Exchange Admin Issues Subject: Looking for advice re HR Luser request Running Exchange 5.5, SP4 on NT4 SP6a. Our HR department currently has an email address set up for job postings so people can email their resume. They are getting so many that they no longer want to process them. What they want to do is create a new email address for each posting that would go to the appropriate person in the department with the opening. The do not wish to use the following suggestions I gave to them: 1. Just use the email of the person in the department you want to receive the resumes. 2. We could create a few distribution lists (for running multiple jobs at once) and they can add and remove users at will. 3. They could set up rules on the current mailbox to route based on job posting number or some other piece of information. I don't like the idea of creating an email address every time they do a job posting. So, I'm wondering if anyone else has had to deal with a similar situation and if you found a workable solution. TIA, MJ List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Looking for advice re HR Luser request
I agree with you and that's how they are currently doing it - single mailbox that someone checks. I guess they are SOO overworked up there, that they just don't have the time to continue doing it this way. ;-) -Original Message- From: Martin Blackstone [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:36 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I agree. I don't like that idea either. But now they are reaping what they sew, and it sounds like they don't want to do THEIR jobs. Instead of doing any forwards or CRs, just create a single mailbox. Put everything in there, and tell them how to open it to read mail. Then they can do it at their convenience. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:22 PM To: MS-Exchange Admin Issues Subject: Looking for advice re HR Luser request Running Exchange 5.5, SP4 on NT4 SP6a. Our HR department currently has an email address set up for job postings so people can email their resume. They are getting so many that they no longer want to process them. What they want to do is create a new email address for each posting that would go to the appropriate person in the department with the opening. The do not wish to use the following suggestions I gave to them: 1. Just use the email of the person in the department you want to receive the resumes. 2. We could create a few distribution lists (for running multiple jobs at once) and they can add and remove users at will. 3. They could set up rules on the current mailbox to route based on job posting number or some other piece of information. I don't like the idea of creating an email address every time they do a job posting. So, I'm wondering if anyone else has had to deal with a similar situation and if you found a workable solution. TIA, MJ List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Looking for advice re HR Luser request
Title: RE: Looking for advice re HR Luser request Rules Find out what keywords(job description,etc..) they need routed to which person(s) and then set the rule(s) accordingly. I'm assuming this isn't a custom recipient. If it is, you'd have to create a mailbox and use OL2K to setup the server based rules. Either that or write a custom CDO to have logic in it to handle those emails. There maybe some 3rd party tools out there as well. -Rick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:22 PM To: MS-Exchange Admin Issues Subject: Looking for advice re HR Luser request Running Exchange 5.5, SP4 on NT4 SP6a. Our HR department currently has an email address set up for job postings so people can email their resume. They are getting so many that they no longer want to process them. What they want to do is create a new email address for each posting that would go to the appropriate person in the department with the opening. The do not wish to use the following suggestions I gave to them: 1. Just use the email of the person in the department you want to receive the resumes. 2. We could create a few distribution lists (for running multiple jobs at once) and they can add and remove users at will. 3. They could set up rules on the current mailbox to route based on job posting number or some other piece of information. I don't like the idea of creating an email address every time they do a job posting. So, I'm wondering if anyone else has had to deal with a similar situation and if you found a workable solution. TIA, MJ List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Looking for advice re HR Luser request
some thoughts in no particular odor ... - If they don't like the Exchange solutions you give them, then tell them to go setup their own email box ... (if only it would be that easy) - If the postings are numbered in some kind of pattern, maybe do a import of a month's worth of SMTP addresses in a single account. (i.e. [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], etc) At least that would lessen the pain. - You could set something up, but plead overwork and that they need to send someone over who could type each individual address into the system ... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 3:46 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I agree with you and that's how they are currently doing it - single mailbox that someone checks. I guess they are SOO overworked up there, that they just don't have the time to continue doing it this way. ;-) -Original Message- From: Martin Blackstone [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:36 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I agree. I don't like that idea either. But now they are reaping what they sew, and it sounds like they don't want to do THEIR jobs. Instead of doing any forwards or CRs, just create a single mailbox. Put everything in there, and tell them how to open it to read mail. Then they can do it at their convenience. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:22 PM To: MS-Exchange Admin Issues Subject: Looking for advice re HR Luser request Running Exchange 5.5, SP4 on NT4 SP6a. Our HR department currently has an email address set up for job postings so people can email their resume. They are getting so many that they no longer want to process them. What they want to do is create a new email address for each posting that would go to the appropriate person in the department with the opening. The do not wish to use the following suggestions I gave to them: 1. Just use the email of the person in the department you want to receive the resumes. 2. We could create a few distribution lists (for running multiple jobs at once) and they can add and remove users at will. 3. They could set up rules on the current mailbox to route based on job posting number or some other piece of information. I don't like the idea of creating an email address every time they do a job posting. So, I'm wondering if anyone else has had to deal with a similar situation and if you found a workable solution. TIA, MJ List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
Re: Looking for advice re HR Luser request
Title: RE: Looking for advice re HR Luser request Yah, why not have them post the job with the job number. Have them state they applicant must put the job number in the subject line and then route accordingly. This is very common on Workopolis, etc. Michael - Original Message - From: Rick Ward - HQ To: MS-Exchange Admin Issues Sent: Tuesday, March 26, 2002 5:27 PM Subject: RE: Looking for advice re HR Luser request Rules Find out what keywords(job description,etc..) they need routed to which person(s) and then set the rule(s) accordingly. I'm assuming this isn't a custom recipient. If it is, you'd have to create a mailbox and use OL2K to setup the server based rules. Either that or write a custom CDO to have logic in it to handle those emails. There maybe some 3rd party tools out there as well. -Rick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:22 PM To: MS-Exchange Admin Issues Subject: Looking for advice re HR Luser request Running Exchange 5.5, SP4 on NT4 SP6a. Our HR department currently has an email address set up for job postings so people can email their resume. They are getting so many that they no longer want to process them. What they want to do is create a new email address for each posting that would go to the appropriate person in the department with the opening. The do not wish to use the following suggestions I gave to them: 1. Just use the email of the person in the department you want to receive the resumes. 2. We could create a few distribution lists (for running multiple jobs at once) and they can add and remove users at will. 3. They could set up rules on the current mailbox to route based on job posting number or some other piece of information. I don't like the idea of creating an email address every time they do a job posting. So, I'm wondering if anyone else has had to deal with a similar situation and if you found a workable solution. TIA, MJ List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Looking for advice re HR Luser request
This is not so much a suggestion but a rant about ignorant users who seem to think that computers are somehow magical and can Nike (Just Do It) all by themselves (and why is it that HR seems to be the worst affected by this disease?:)). Probably the easiest solution is to have a person in their department with access to the Exchange administrator and restricted access to the mailboxes of the HR department so that they can create the new email addresses as required. HR should be able to be trusted with this ;). I believe there are also utilities out there which will enable users to modify their own settings in a granular way. In fact I think our hosts at Sunbelt sell a couple of different products which do just this. Unfortunately I have not used any of them so i cannot give you any guidance in this matter. As for the suggestion below, about setting up their own email box! Unfortunately in many organizations this would be taken literally and before you know it every man and his dog is setting up their own email server and causing all sorts of chaos on your network. NEVER suggest to a user that they should do their own thing. Before you know it, you are being called to fight fires on equipment that you have never seen or configured when something out of the ordinary happens. If you say that you do not support their gear, you get blamed because you suggested that they set it up themselves. Or even worse your users get the idea that they can do without your services and you get invited to hit the track :) Of course this is based on my experiences at a large Government department that had a number of scientists who believed that the only way to get anything done was to do it themselves. The benefit was that we harnessed their energies in an advisory committee so that we could look at their suggestions and come up with solutions that were reasonably cost effective and didn't cause a major disruption. -Original Message- From: Sanborn, John [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 27 March 2002 7:40 To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request some thoughts in no particular odor ... - If they don't like the Exchange solutions you give them, then tell them to go setup their own email box ... (if only it would be that easy) - If the postings are numbered in some kind of pattern, maybe do a import of a month's worth of SMTP addresses in a single account. (i.e. [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], etc) At least that would lessen the pain. - You could set something up, but plead overwork and that they need to send someone over who could type each individual address into the system ... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 3:46 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I agree with you and that's how they are currently doing it - single mailbox that someone checks. I guess they are SOO overworked up there, that they just don't have the time to continue doing it this way. ;-) -Original Message- From: Martin Blackstone [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:36 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I agree. I don't like that idea either. But now they are reaping what they sew, and it sounds like they don't want to do THEIR jobs. Instead of doing any forwards or CRs, just create a single mailbox. Put everything in there, and tell them how to open it to read mail. Then they can do it at their convenience. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:22 PM To: MS-Exchange Admin Issues Subject: Looking for advice re HR Luser request Running Exchange 5.5, SP4 on NT4 SP6a. Our HR department currently has an email address set up for job postings so people can email their resume. They are getting so many that they no longer want to process them. What they want to do is create a new email address for each posting that would go to the appropriate person in the department with the opening. The do not wish to use the following suggestions I gave to them: 1. Just use the email of the person in the department you want to receive the resumes. 2. We could create a few distribution lists (for running multiple jobs at once) and they can add and remove users at will. 3. They could set up rules on the current mailbox to route based on job posting number or some other piece of information. I don't like the idea of creating an email address every time they do a job posting. So, I'm wondering if anyone else has had to deal with a similar situation and if you found a workable solution. TIA, MJ List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ
RE: Looking for advice re HR Luser request
I had something similiar with about 50 different information type e-mail addresses that were published on a couple websites. I think you were right on with the DL idea. -Original Message- From: Martin Blackstone [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 2:36 PM To: MS-Exchange Admin Issues Subject: RE: Looking for advice re HR Luser request I agree. I don't like that idea either. But now they are reaping what they sew, and it sounds like they don't want to do THEIR jobs. Instead of doing any forwards or CRs, just create a single mailbox. Put everything in there, and tell them how to open it to read mail. Then they can do it at their convenience. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 1:22 PM To: MS-Exchange Admin Issues Subject: Looking for advice re HR Luser request Running Exchange 5.5, SP4 on NT4 SP6a. Our HR department currently has an email address set up for job postings so people can email their resume. They are getting so many that they no longer want to process them. What they want to do is create a new email address for each posting that would go to the appropriate person in the department with the opening. The do not wish to use the following suggestions I gave to them: 1. Just use the email of the person in the department you want to receive the resumes. 2. We could create a few distribution lists (for running multiple jobs at once) and they can add and remove users at will. 3. They could set up rules on the current mailbox to route based on job posting number or some other piece of information. I don't like the idea of creating an email address every time they do a job posting. So, I'm wondering if anyone else has had to deal with a similar situation and if you found a workable solution. TIA, MJ List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.343 / Virus Database: 190 - Release Date: 3/22/2002 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.343 / Virus Database: 190 - Release Date: 3/22/2002 List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
