SMTP on Windows/IIS update

Habers, Mark Habers at pbworld.com
Fri Aug 19 20:31:28 UTC 2005


Hi Steve,

This is probably a support issue that eventually one of the developers
here is going to request we take to that forum... I have a similar setup
as you though and would offer the following suggestion. Talk to your
exchange people and make sure that the SMTP server you are using is
trusted to relay email to Exchange. In all but the most insecure
environments, Exchange will not accept email from just any server on the
WAN that happens to be running SMTP. I have 30 different SMTP boxes
available here that I can use to relay my email from BugZilla. A
fraction of those servers are actually trusted by Exchange to route said
email to the corporate Exchange system. I also do not receive any errors
on the BugZilla side when I point to an SMTP box that is not trusted. I
believe you are having the same issue. I would start there before
rewriting anything... To test this theory, identify another SMTP box on
your network that is already able to send out email to your users,
employees, etc.. and piggy back on that one instead. If your email
starts working, the problem is at hand. If you don't have another SMTP
box available that you know is sending email successfully, you will have
to get your Exchange people to add your box as trusted and go from
there... You'll probably want to do that anyway just to stay out of
trouble and to keep from having to revisit this problem again down the
road. Just my 2 cents..

 

Mark

 

  _____  

From: Thomas, Steve [mailto:developers-owner at bugzilla.org] On Behalf Of
Thomas, Steve
Sent: Friday, August 19, 2005 1:46 PM
To: developers at bugzilla.org
Subject: SMTP on Windows/IIS update

 

Hey folks,

I'm still trying to get this to work. Since I am a PHP programmer
(actually my background includes almost everything *except* Perl), doing
what seems to be required--rewriting the SMTP code--is not a good option
for me. As such I wrote a PHP script to send an email (a one-liner) and
my plan is to have BugMail simply call the script using HTTP. 

I still have no clue as to why the original code doesn't work. When I
switch to using localhost directly and turn on the local SMTP server, I
do in fact see the mail messages gather in the outbound queue, but they
go nowhere from there. When I talk directly to the corporate SMTP server
(which is Exchange, which is probably the problem overall), it just
sucks up the mail message with no errors at all (or at least none that I
get to see given the SMTP code).

Thinking I could just drop in the open() call to the PHP script would be
easy is turning out to be wrong as well. Given the sendmail roots
(apparently) of the Bugzilla mail functionality deriving what you need
for a normal mail interface (from, to, subject, message) is actually
pretty hard for somebody with little Perl experience. Somebody that
actually knows what they are doing could probably write me such a
snippet in about 5 minutes, but oh well.

If anybody has any other tricks I might pull to get the current SMTP
code working with an MS exchange server, that would be splendid. Note
that (as implied above) PHP's built-in mailer seems to have no problem
sending mail to our servers.

Thanks,

 

Steve Thomas

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bugzilla.org/pipermail/developers/attachments/20050819/9170c811/attachment.html>


More information about the developers mailing list