defaria.com/blogs/Status/archives/000521.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
   2    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" id="sixapart-standard">
   4 <head>
   5    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
   6    <meta name="generator" content="Movable Type 5.2.3" />
   7
   8    <link rel="stylesheet" href="http://defaria.com/blogs/Status/styles-site.css" type="text/css" />
   9    <link rel="alternate" type="application/atom+xml" title="Atom" href="http://defaria.com/blogs/Status/atom.xml" />
  10    <link rel="alternate" type="application/rss+xml" title="RSS 2.0" href="http://defaria.com/blogs/Status/index.xml" />
  11
  12    <title>Status for Andrew DeFaria: More CQ Web Email Problems (GetSMTPHost)</title>
  13
  14    <link rel="start" href="http://defaria.com/blogs/Status/" title="Home" />
  15    <link rel="prev" href="http://defaria.com/blogs/Status/archives/000520.html" title="CQ Web Email Problem" />
  16    <link rel="next" href="http://defaria.com/blogs/Status/archives/000522.html" title="PQA Email issue/Mobile Multimedia" />
  17
  18
  19
  20
  21
  22    <script type="text/javascript" src="http://defaria.com/blogs/Status/mt-site.js"></script>
  23 </head>
  24 <body class="layout-one-column" onload="individualArchivesOnLoad(commenter_name)">
  25    <div id="container">
  26       <div id="container-inner" class="pkg">
  27
  28          <div id="banner">
  29             <div id="banner-inner" class="pkg">
  30                <h1 id="banner-header"><a href="http://defaria.com/blogs/Status/" accesskey="1">Status for Andrew DeFaria</a></h1>
  31                <h2 id="banner-description">Searchable status reports and work log</h2>
  32             </div>
  33          </div>
  34
  35          <div id="pagebody">
  36             <div id="pagebody-inner" class="pkg">
  37                <div id="alpha">
  38                   <div id="alpha-inner" class="pkg">
  39
  40                      <p class="content-nav">
  41                         <a href="http://defaria.com/blogs/Status/archives/000520.html">&laquo; CQ Web Email Problem</a> |
  42                         <a href="http://defaria.com/blogs/Status/">Main</a>
  43                         | <a href="http://defaria.com/blogs/Status/archives/000522.html">PQA Email issue/Mobile Multimedia &raquo;</a>
  44                      </p>
  45
  46                      <a id="a000521"></a>
  47                      <div class="entry" id="entry-521">
  48                         <h3 class="entry-header">More CQ Web Email Problems (GetSMTPHost)</h3>
  49                         <div class="entry-content">
  50                            <div class="entry-body">
  51                               <ul>
  52   <li>Implemented and tested GetSMTPHost</li>
  53 </ul>
  54                            </div>
  55                            <div id="more" class="entry-more">
  56                               <p>Actually I was on vacation but still trying to work on the problem. Sorry but the ski cabin in Vermont didn't have Internet access...</p>
  57
  58 <p>We are very sensitive to the critical nature of this bug. <a href="/blogs/Status/archives/000520.html#more">Here's what I found out on Friday</a>.</p>
  59
  60 <p>I've implemented a solution to option #2 and have tested it. However, the way it works is to use ipconfig to get the IP address of the current machine then nslookup to change that to a hostname. After that I've found that nbu-cqweb is actually known as nt-irva-1521.broadcom.com. So I have it hard coded to return an SMTP host of mms.broadcom.com if it's running on nt-irva-1521.broadcom.com otherwise return smtphost.broadcom.com. There are a couple of things I don't like about this solution:</p>
  61
  62 <ol>
  63   <li>Hard coding of machine names. Will nbu-cqweb always be known as nt-irva-1521.broadcom.com? Also, such a fix will break if we implement a new web server for you which will presumably have a different machine name...</li>
  64
  65   <li>I'm not sure how this works in the context of CQ Web as opposed to CQ Client. It seems to work on p4test's Web Server.</li>
  66
  67   <li>I've only addressed the Submit notify action. Turns out there are other notify actions (e.g. Assign, Resolve, Verify) which are still using the older PAINET object. I would have thought that all of the email sending would be done through one routine but it turns out the code was essentially duplicated in many places. (Note PAINET is an object that IBM/Rational cooked up for CQ only). I have not changed these and I would assume that they are as likely as Submit to send email with a send date of 2001. Again, we've never determined why the old code stopped working correctly.</li>
  68 </ol>
  69
  70 <p>I have this fix ready to go but I'll wait for your OK before applying it to production.</p>
  71                            </div>
  72                         </div>
  73                         <p class="entry-footer">
  74                            <span class="post-footers">Posted by  on January 23, 2006 11:00 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000521.html">Permalink</a>
  75                         </p>
  76                      </div>
  77
  78
  79
  80
  81                   </div>
  82                </div>
  83             </div>
  84          </div>
  85       </div>
  86    </div>
  87 </body>
  88 </html>