Time
is not the most important IT commodity. The point of IT is not to
stand around and thump your chest and declare yourself king. Your job is
to do what you can to alleviate a problem as simply, quickly and cost
effectively as possible. If you're any good, most of the time you
can. Sometimes you can't. That's why you ask questions on these
lists.
That
being said, I think it's about time for Kevin Snook to chime in:
"I
have a utility (how many messages do I start like
this)...."
-----Original Message-----
From: Rick Ward - HQ [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 23, 2001 2:11 PM To: MS-Exchange Admin Issues Subject: RE: Relay - from: address issue Unfortunately Michele you don't get it IMHO...
To
almost all IT professionals time is the MOST important commodity. If you did get
it, then why would you spend spare time(that is rare and almost non-existent in
the 10+ years I've been doing this) fixing a problem you've already corrected at
the Exchange level. Seems like duplication of effort.
I
understand it's still "not right" as the scripts should be corrected. But why
would the IT professional need to do this??? He/She didn't write the bad
code??
I'd
make THEM fix it while I spent my precious "spare time" doing something more
constructive like exploring XP, Learning MSI, etc...
<end of session>
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 23, 2001 2:01 PM To: MS-Exchange Admin Issues Subject: RE: Relay - from: address issue No, I get it now.
thankyouverymuch. and I agree that a workaround is appropriate in this
case.
but, knowing that they're
wrong would irritate me enough that I'd fix it anyway, even while using the
workaround in the meantime.
*shrug* that's just
me.
Immigration site: http://LadySun1969.tripod.com Our new 2001 Miata: http://members.cardomain.com/bpituley Tiggercam: http://www.tiggercam.co.uk --------------------------------------------------------- I love deadlines. I especially love the swooshing sound they make as they go flying by. --------------------------------------------------------- -----Original Message-----
From: Rick Ward - HQ [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 23, 2001 4:56 PM To: MS-Exchange Admin Issues Subject: RE: Relay - from: address issue It's
okay Michael... from the last response sent.. Michele isn't getting
it..
-Rick
-----Original Message-----
From: Michael Morisoli [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 23, 2001 1:54 PM To: MS-Exchange Admin Issues Subject: RE: Relay - from: address issue The problem is that we
have over 100 different clients sites with over 20
different programmers with over 10 different managers. Do you get the idea now. It is going
to take me weeks just to get the info out to the field of what they have been
doing wrong in the past. Then I
will have to justify why it's wrong to use a first and last name instead of an
email address, so on and so on. I am just trying to
find a way to force Exchange to misbehave long enough for me to fix the real
problem, ignorance. Otherwise, I have to
dust off my Linux and sendmail books which I really,
really, really don't want to do... -----Original
Message----- You're right that the P2 and P1
stuff will probably solve his problems, but why wouldn't it be possible for the
forms to be coded to generate correct
addresses? -Michèle -----Original
Message----- don't
think that's possible Michele... Michael -
In 5.5 there are a whole set of new P2 and P1 resolve settings you can add into
the registry(Q174755). In Exchange 2000 check out
Q288635. This
should resolve your problem. -Rick -----Original
Message----- why not require them to use properly
formatted emails in the FROM field? -Michèle -----Original
Message----- This is a bit off the wall, but here
goes. Recently I replaced an older Linux +
SendMail server that died with an Exchange 2000 server. This server is used primarily as a relay
host for a web farm we have. The
problem has to do with malformed from addresses. For some reason, there are many forms on
the web farm that generate email messages with improper [EMAIL PROTECTED] address in the from:
field. Instead, they use first
name, last name. It appears that the sendmail server
did not care about the from address and would happily send out this type of
malformed email message. The
problem is that Exchange will not send this type of
message. Given the large number of forms and
the weeks of time it will take to fix this properly, does anybody know of a way
to have Exchange turn off from address validation? This would give me some breathing room
till a real solution is worked on. Thanks ahead of time for any
help. Mike 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: Relay - from: address issue msharik
- RE: Relay - from: address issue Rick Ward - HQ
- RE: Relay - from: address issue msharik
- RE: Relay - from: address issue Michael Morisoli
- RE: Relay - from: address issue Rick Ward - HQ
- RE: Relay - from: address issue msharik
- RE: Relay - from: address issue Rick Ward - HQ
- RE: Relay - from: address issue Michael Morisoli
- RE: Relay - from: address issue Michael Morisoli
- RE: Relay - from: address issue Drewski
- RE: Relay - from: address issue RZorz
- RE: Relay - from: address issue Robert.Fish
- RE: Relay - from: address issue msharik
- RE: Relay - from: address issue Rick Ward - HQ
- RE: Relay - from: address issue Don Ely
- RE: Relay - from: address issue RZorz
- RE: Relay - from: address issue Rick Ward - HQ
- RE: Relay - from: address issue Rick Ward - HQ
- RE: Relay - from: address issue msharik
- RE: Relay - from: address issue Lefkovics, William
- RE: Relay - from: address issue Schutte, Keith [EPT/FLO]