>If a server requires STMP authentication, can't I do that by manually >Getting mail and then quickly manually Sending?
No, what you are thinking of is refered to as POP Authentication (which just to really confuse you is not the same thing as logging into your POP account to get your mail). SMTP Auth is a style where authentication info is sent to the mail server when you connect to send mail, but before you actually start sending it. Emailer does not support SMTP Authentication... but it can do POP Auth (which, like you think above, is basically just check your mail right before sending mail). However, not all mail servers support POP Auth (nor do all support SMTP Auth, and some support both). >My dial-up ISP just gave me some new phone numbers to try out because of >a problem with the existing ones. I connect fine with the new numbers, >but cannot send, getting the error: >> ** 550 5.7.1 <recipient's e-mail address>... Relaying denied >> ** SMTP server error "503 5.0.0 Need RCPT (recipient)" Yup, that is an authentication problem. The easiest is to try POP Auth and see if you can then send. If not, you need to look into other options (different mail server, different email software, or Baton Mail among choices). >It's a little complicated. The new provider [of our new phone numbers] >has not given us specific IP numbers for our dial-up modems. Without the >IP numbers, the WGN server does not know who you are. That's why I >suggested to have the outgoing mail authentication. That actually makes perfect sense. The ISP would LIKE to make your life easy and simply set their mail server to accept mail from anyone connected at a certain range of IP addresses. But if the new dialup provider won't (or can't) give them a list of possible IPs, then the ISP can't set the server to look for them. So to keep spammers at bay, they are forced to resort to other authentication methods. >More in depth, my provider was recently taken over by a new company. When >that happened, I was getting the same error, and it was eventually fixed >by their giving me new name server addresses to enter in the TCP/IP >panel. Otherwise, I didn't have to change any settings. For reasons I >don't understand, it (apparently) was only Macs who needed these new >addresses, and who were experiencing these errors. Apparently PCs got the >info automatically, or something like that. The take over probably included new mail servers. Again, the ISP was being nice, and simply altered the DNS records to point to the new mail servers, making your transition transparent. This would be 100% transparent to windows users, because windows gets the DNS server info along with the DHCP lease (ie: when they connect to the dialup, a DHCP server tells the windows machine what IP address to use, what DNS servers to use, and what routers to look to). The Mac up thru OS 9.x will get everything EXCEPT the DNS servers with a DHCP lease. As as result, you needed to manually update the DNS servers. (OS X will also grab the DNS info with the DHCP lease... as well as I might be off on if OS 9 grabs the DNS info... I don't recall now that I am thinking about it) >The old versions I have of Eudora and Netscape also give me the same >error and I was hoping to easily test whether STMP authentication was the >problem Older versions of those programs also don't support SMTP Authentication, so they wouldn't do you any good. Your best bet is to try the POP Auth, failing that, you need to look into other options. -chris <http://www.mythtech.net> ___________________________________________________________________________ To unsubscribe send a mail message with a SUBJECT line of "unsubscribe" to <[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
