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 connector properties, 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 PM
To: MS-Exchange Admin Issues
Subject: 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 PM
To: MS-Exchange Admin Issues
Subject: 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 AM
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 SOOOOOO 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
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

Reply via email to