<br><br><div class="gmail_quote">On Jan 7, 2008 11:56 AM, Tom Phoenix <<a href="mailto:rootbeer@redcat.com">rootbeer@redcat.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Jan 6, 2008 7:23 PM, Ching de la Serna <<a href="mailto:ching.dls@gmail.com">ching.dls@gmail.com</a>> wrote:<br><br>> > I hope you didn't really bother the nice people at <a href="http://mydomain.com" target="_blank">
mydomain.com</a>. You<br>> > did use your own SMTP server, didn't you?<br>><br>> Tom, I did send a support ticket in this regard asking for their help in<br>> accomplishing what i wanted to do which was to send emails from squeak. I
<br>> wanted to see if I could use their SMTP server since my account included<br>> email capability. I assumed that sending emails from squeak would be<br>> possible if I could find the mechanism for authenticating a session using my
<br>> account with their servers.<br><br></div>So, does that mean that you have some preexisting relationship with<br>them, and so <a href="http://mydomain.com" target="_blank">mydomain.com</a> wasn't being used as a placeholder, like
<br><a href="http://example.com" target="_blank">example.com</a>? At least, I hope your password isn't "passWord"!</blockquote><div><br>Yes, I have a pre-existing relationship with them. No, "<a href="http://mydomain.com">
mydomain.com</a>" is just a placeholder like "<a href="http://example.com">example.com</a>". my actual domain name, paid for by me, is registered and hosted by those nice people (i did not want to advertise the actual domain name) and no, the password is not "passWord". I was under the impression that I had some kind of rights to use the mail server for sending mails from squeak and not just using webmail or outlook express (manually emailing)
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><div class="Ih2E3d"><br>> Googling '503 AUTH command used when not advertised', I gathered that
<br>> certain steps needed to be be accomplished which included issuing the EHLO<br>> command before the AUTH command. I was wondering if anyone had any<br>> experience with this at all.<br><br></div>Sure; lots of folks. They hang out in forums whose topic is "SMTP", or
<br>something similar. Although some SMTP experts may also be found on the<br>Seaside list, they'll give you better answers faster in their own<br>forum.</blockquote><div><br>You're right there, Tom. I did find a lot of discussion regarding this particular topic but largely these discussions are specific to some mail servers they are using. I did find the RFC document that mentions the 503 AUTH error and it was a very general document. I was looking for something relating to Squeak and seaside because I am sure many Squeakers/Seasiders have successfully implemented emailing out from Squeak. I would like to know if anyone has been where I am now and would appreciate their input.
<br><br>Thanks<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><br>Cheers!<br><div><div></div><div class="Wj3C7c"><br>--Tom Phoenix
<br>_______________________________________________<br>seaside mailing list<br><a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br><a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br></div></div></blockquote></div><br>