As I've been newly having some Emailer sending problems, I've refreshed my memory on the situation: I think the following summary is approximately correct, for what it's worth!
Sending email with Emailer can present a combination of issues to do successfully, depending on circumstances of the ISP in question. First, the Incoming mail server and the Outgoing mail server settings have to be made correctly in Emailer on the Setup/Accounts/AccountInfo window. To do this, one has to ascertain from the particular ISP in question (your own, your work's, your hotel's, etc.) what name the ISP uses for these servers, respectively. There can be two different names, or in cases where the same server does both functions, the name will be the same. One would need a separate account setup for each different eddress one uses. Emailer has a separate field for the outgoing mail server, which is the SMTP server window. One simply enters the SMTP server name, and one should be able to SEND mail, all other things equal. And, if one is going to use, or must use, the SMTP server of one's hotel service while "on the road," I think one would have to set up a "temporary" set of settings in Emailer with the appropriate SMPT server name entered. For the incoming mail server, however, in Emailer, unlike most other email client programs, the POPserver name is entered in the "Email Account" field AFTER the "@" sign. (This means Emailer parses whatever is entered in this field and chooses the part after the "@" sign to use to connect to the ISP's POP server.) Actually, one could use this "Email Account" entry in this form as one's email address, as it is merely a more "precise" version of your "normal" email address which is completely understood by the internet email systems. The generic format is [EMAIL PROTECTED] This works just fine usually, as long as the ISP's Username scheme does NOT require a full email address as the USERNAME, i.e. "[EMAIL PROTECTED]" (rather than just "username").Since Emailer's POP server entry in its Email Account field has this parsing scheme to retrieve the POP server name, one ends up with 2 "@s" in the EmailAccount field, which isn't going to work ([EMAIL PROTECTED]@POP.isp.com), hence the suggestion to try other symbols in place of the first "@" in the hopes that the particular POP server in question will recognize and process the information correctly. Depending on the various ISPs, this may or may not be successful. (As I recall from a friend's Mac who used Comcast, the Comcast POP server would work with "%" substituted for the first "@".) However, there is a SECOND round of problems for sending any time, and those are the Authentication issues, again which various ISPs treat differently. Authentication basically means the ISP wants to verify who you are before allowing you to use their services. Once upon a time, initially providing one's username and password at log in to the ISP was enough, but those days are long gone what with spammers, identity thieves, etc. As near as I can tell, there are at least three versions of authenticating going on as regards your email (in addition to logging onto your ISP in the first place.) 1. When you go to COLLECT your mail, before the ISP's POPserver will send it to you, it has to have your username and password. Usually, the POPserver will acquire this automatically from your login server's authentication, and you do not have to provide it a "second" time; if it doesn't, you may have to log in a "second" time to the POPserver. 2. When you go to SEND mail, it is now becoming most common that you also have to log into the SMTPserver before it allows you to send mail, this "log in" being called "SMTP authenticaion." Typically, this is something one's email client can do automatically, EXCEPT for Claris Emailer, which was written before SMTP authentication existed and thus does NOT do SMTP authentication, i.e., "pure" (my term) SMTP authenticaion natively done by one's email client program. 3. SMTP Authentication Solution #1. "SMTP authentication via POP authentication." It may NOT make a difference that Emailer doesn't do "pure" SMTP authentication, IF your ISP's SMTP authentication scheme is also tied to its POPserver authentication scheme automatically. Some (but not all)ISPs, provided you have first COLLECTED (and thus POP authenticated) your email, the SMTP server notes this automatically and provides a "window of time" in which you are now SMTP authenticated to SEND email (this window of time varies with the setting of the particular ISP.) [Until a couple weeks ago, my ISP (www.themacisp.net) used this scheme, but turned it off due to problems catching a spammer. I'm hoping they restore it.] SMTP Authentication Solution #2. Use a different email client program which does SMTP authentication natively. SMTP Authentication Solution #3. Use Chris's Baton Mail program which will provide "semi-pure" SMTP authentication for Emailer (as well as other email programs which might not do smpt authentication.) To use Chris's Baton Mail, the EmailerCustomSettings file also has to be acquired from his ftp site and dropped into the Emailer Folder. SMTP Authentication Solution #4. Use webmail. Often one's ISP also provides webmail which mirrors your POP mail account, so you can send mail just the same as you can with Emailer when on the road. ___________________________________________________________________________ To unsubscribe send a mail message with a SUBJECT line of "unsubscribe" to <[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
