{"id":16,"date":"2008-06-10T01:39:49","date_gmt":"2008-06-09T17:39:49","guid":{"rendered":"http:\/\/blog.lolyco.com\/sean\/?p=16"},"modified":"2008-10-22T22:37:45","modified_gmt":"2008-10-22T14:37:45","slug":"streamyx-smtp-server-authentication-problem","status":"publish","type":"post","link":"https:\/\/blog.lolyco.com\/sean\/2008\/06\/10\/streamyx-smtp-server-authentication-problem\/","title":{"rendered":"Streamyx SMTP server authentication problem"},"content":{"rendered":"<p><img decoding=\"async\" class=\"alignright alignnone\" style=\"float: right; padding-left: 12px; padding-bottom: 12px;\" src=\"http:\/\/www.tm.com.my\/images\/global\/main-logo.gif\" alt=\"TM logo\" \/><\/p>\n<p>The SMTP AUTH settings in this post have been <a title=\"Streamyx SMTP AUTH again\" href=\"http:\/\/blog.lolyco.com\/sean\/2008\/10\/22\/streamyx-smtp-auth-mail-proxy\/\">updated in a later article<\/a>.<\/p>\n<p>It has been a busy few days. I&#8217;d noticed a couple of funny <strong>messages in the maillog<\/strong> generated by our <strong>sendmail<\/strong> daemon, but put them to the back of my mind. Here&#8217;s an example:<\/p>\n<p style=\"padding-left: 30px;\"><code>Jun 10 00:29:16 box0043 sm-mta[9729]: m59GTFu0009727: to=&lt;someone@somewhere.com&gt;, ctladdr=&lt;someone@domain.com&gt; (1000\/100), delay=00:00:01, xdelay=00:00:01, mailer=relay, pri=120489, relay=smtp.streamyx.com. [202.188.0.212], dsn=5.7.1, stat=Service unavailable<br \/>\nJun 10 00:29:16 box0043 sm-mta[9729]: m59GTFu0009727: m59GTGu0009729: DSN: Service unavailable<\/code><\/p>\n<p>In retrospect, the log entries don&#8217;t seem so benign. In actual fact, the <strong>emails were not delivered<\/strong>. DSN is a Delivery Service Notification, which can be used to <strong>notify<\/strong> a sender <strong>by email<\/strong> when there&#8217;s a problem. It seems I had two problems on my mail server setup, as I didn&#8217;t get any email notifications of the failures. Most of the outgoing emails were sent by a PHP program running on our webserver, so may have been sent to the webserver&#8217;s non-interactive user.<\/p>\n<p>The cause of this problem might have been harder to find, if it were not for a dim recollection of seeing a message somewhere that TM were planning to <strong>block mail<\/strong> from users who had never changed their <strong>default Streamyx password<\/strong>. I&#8217;m one of those people, and when I saw the recent message thought once again &#8220;Oh, I must get round to doing that&#8221;.<\/p>\n<p>Well it seems they must have put their plan into action. To test my suspicion, I tried to <strong>log in<\/strong> to my <strong>mail account<\/strong> at <a title=\"TM Net Webmail\" href=\"http:\/\/webmail.tm.net.my\" target=\"_blank\">http:\/\/webmail.tm.net.my<\/a> &#8211; no joy. You can <strong>change a Streamyx password<\/strong> at the <a title=\"TM Billing site\" href=\"https:\/\/tmbill.tm.net.my\/SelfCare\/Maintenance\/selfcareLogin.jsp\" target=\"_blank\">TM Billing sit<\/a>e. Once I&#8217;d done that, webmail login worked just fine, I reset my ADSL router after changing the Streamyx password, and updated my <strong>sendmail auth file<\/strong>.<\/p>\n<p>To make sure sendmail is logging in to the Streamyx SMTP proxy, you must edit your auth\/client-info file and make sure the AuthInfo line is up to date:<\/p>\n<blockquote><p><code>AuthInfo:smtp.streamyx.com \"U:USERNAME@streamyx.com\" \"I:USERNAME@streamyx.com\" \"P:PASSWORD\"<\/code><\/p><\/blockquote>\n<p>Then execute the following commands to compile your sendmail settings:<\/p>\n<blockquote><p><code>makemap hash client-info &lt; client-info<\/code><\/p>\n<p><code><br \/>\n\/etc\/rc.d\/rc.sendmail restart<\/code><\/p><\/blockquote>\n<p>That&#8217;s it! I may have imagined the threat from TM regarding default passwords and the SMTP proxy, but I don&#8217;t think I did. If you can <strong>track down that message<\/strong>, I&#8217;d love to see it again &#8211; it bothers me that it has disappeared.<\/p>\n<p><strong>Update<\/strong>: thanks to mylinear at <a title=\"WebmasterMalaysia.com forum thread\" href=\"http:\/\/www.webmastermalaysia.com\/website-programming\/14276-tm-net-blocking-smtp-proxy-access.html#top\" target=\"_blank\">WebmasterMalaysia.com<\/a>, who pointed out that it&#8217;s the message on the TM Helpline (1300-88-9515)! Here she is:<\/p>\n<p><object classid=\"clsid:d27cdb6e-ae6d-11cf-96b8-444553540000\" width=\"400\" height=\"15\" codebase=\"http:\/\/download.macromedia.com\/pub\/shockwave\/cabs\/flash\/swflash.cab#version=6,0,40,0\"><param name=\"name\" value=\"xspf_player\" \/><param name=\"bgcolor\" value=\"#e6e6e6\" \/><param name=\"align\" value=\"middle\" \/><param name=\"src\" value=\"http:\/\/blog.lolyco.com\/xspf\/slim\/xspf_player_slim.swf?song_url=http:\/\/blog.lolyco.com\/sean\/wp-content\/uploads\/2008\/06\/tmnodefaultpassword.mp3&amp;player_title=TM No default password for email&amp;song_title=TM No default password for email\" \/><embed type=\"application\/x-shockwave-flash\" width=\"400\" height=\"15\" src=\"http:\/\/blog.lolyco.com\/xspf\/slim\/xspf_player_slim.swf?song_url=http:\/\/blog.lolyco.com\/sean\/wp-content\/uploads\/2008\/06\/tmnodefaultpassword.mp3&amp;player_title=TM No default password for email&amp;song_title=TM No default password for email\" align=\"middle\" bgcolor=\"#e6e6e6\" name=\"xspf_player\"><\/embed><\/object><\/p>\n","protected":false},"excerpt":{"rendered":"<p>The SMTP AUTH settings in this post have been updated in a later article. It has been a busy few days. I&#8217;d noticed a couple of funny messages in the maillog generated by our sendmail daemon, but put them to the back of my mind. Here&#8217;s an example: Jun 10 00:29:16 box0043 sm-mta[9729]: m59GTFu0009727: to=&lt;someone@somewhere.com&gt;, [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17,14,20],"tags":[29,16,15],"class_list":["post-16","post","type-post","status-publish","format-standard","hentry","category-broadband","category-broken","category-fixed","tag-email","tag-streamyx","tag-tm-net"],"_links":{"self":[{"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/posts\/16","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/comments?post=16"}],"version-history":[{"count":3,"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/posts\/16\/revisions"}],"predecessor-version":[{"id":165,"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/posts\/16\/revisions\/165"}],"wp:attachment":[{"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/media?parent=16"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/categories?post=16"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/tags?post=16"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}