sending email
in [Visual Basic]
|
From: kpg on 11 May 2010 21:49 I think I've figured it out. http://en.wikipedia.org/wiki/POP_before_SMTP A security technique used by some mail servers is to have the user first connect to the pop server before the smtp server will allow access. I'll give it a try tomorrow and follow up. "Mayayana" wrote: > > | No. I get the same error. > | > | Error 421: Sorry, You must login before using this server. > > 421 usually means "come back later". As far > as I know it's sent in response to EHLO, which > is the initial server connection. That happens > before you get to the password part. > > http://email.about.com/cs/standards/a/smtp_error_code_2.htm > > You might try asking in the VBScript group, > where a lot of people use CDO, and post > the actual code. There may be something you > can do. > > Another possibility -- I don't know whether > this will help, but you might be able to debug > the connection with it: > > http://www.jsware.net/jsware/scripts.php5#mailer > > It's an ActiveX EXE that comes with a sample > script and an HTA. If you use debug settings to > send mail with the EXE, the HTA will report the > actual server conversation. > > Also, you might visit cox.net and find out exactly > what settings you need to send email through them. > But if you're not sending from your home machine > that's connected through cox.net you may have a > problem. They may be checking the IP addess to > make sure it's one of theirs. > > > . >
From: Mayayana on 11 May 2010 23:10 |I think I've figured it out. | | http://en.wikipedia.org/wiki/POP_before_SMTP | | A security technique used by some mail servers is to have the user first | connect to the pop server before the smtp server will allow access. | | I'll give it a try tomorrow and follow up. | Possible, but I'd guess that's an outdated method. Most SMTP servers didn't used to require authentication. In that scenario the "POP before SMTP" would make sense to provide flexibility with the sending IP. But when the SMTP server requires a password, POP before SMTP would be redundant.
From: Tony Toews [MVP] on 12 May 2010 01:10 "MikeD" <nobody(a)nowhere.edu> wrote: >The other thing >you can do is use an SMPT server that DOESN'T require logging in. Most >likely, this WON'T be the user's SMTP server. You can use any SMTP server. >It doesn't HAVE to be the user's. But in order to avoid providing >credentials, it's probably one that you need to provide and it'd be open >(meaning ANYONE could theoretically use it if they know about it). This probably won't work for many consumer level users, and possibly corporate ones too, as many ISPs are requiring you to send out going email via thier SMTP server. They've blocked port 25 access to other SMTP servers other than their own. Tony -- Tony Toews, Microsoft Access MVP Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ For a convenient utility to keep your users FEs and other files updated see http://www.autofeupdater.com/ Granite Fleet Manager http://www.granitefleet.com/
From: Jim Mack on 12 May 2010 06:55 Tony Toews [MVP] wrote: > "MikeD" <nobody(a)nowhere.edu> wrote: > >> The other thing >> you can do is use an SMPT server that DOESN'T require logging in. >> Most likely, this WON'T be the user's SMTP server. You can use any >> SMTP server. It doesn't HAVE to be the user's. But in order to >> avoid providing credentials, it's probably one that you need to >> provide and it'd be open (meaning ANYONE could theoretically use >> it if they know about it). > > This probably won't work for many consumer level users, and possibly > corporate ones too, as many ISPs are requiring you to send out going > email via thier SMTP server. They've blocked port 25 access to > other SMTP servers other than their own. Correct. These days any 'open relay' would be quickly discovered and become a spam gusher. You must authenticate, and possibly use a port other than 25, to send mail in a system of any size today. Whether this is done using "POP first" (becoming rare), plain text (PW), or secure auth, etc., you still need to get authorized. -- Jim Mack Twisted tees at http://www.cafepress.com/2050inc "We sew confusion"
From: Tony Toews [MVP] on 12 May 2010 22:49 "Jim Mack" <jmack(a)mdxi.nospam.com> wrote: >>> The other thing >>> you can do is use an SMPT server that DOESN'T require logging in. >>> Most likely, this WON'T be the user's SMTP server. You can use any >>> SMTP server. It doesn't HAVE to be the user's. But in order to >>> avoid providing credentials, it's probably one that you need to >>> provide and it'd be open (meaning ANYONE could theoretically use >>> it if they know about it). >> >> This probably won't work for many consumer level users, and possibly >> corporate ones too, as many ISPs are requiring you to send out going >> email via thier SMTP server. They've blocked port 25 access to >> other SMTP servers other than their own. > >Correct. These days any 'open relay' would be quickly discovered and >become a spam gusher. Actually my paragraph had nothing to do with a mail server being an open relay. >You must authenticate, and possibly use a port other than 25, to send >mail in a system of any size today. Whether this is done using "POP >first" (becoming rare), plain text (PW), or secure auth, etc., you >still need to get authorized. Not possibly but almost certainly use a port other than 25. Even then I vaguely recall one ISP doing some kind of packet inspection and not allowing me to connect on port 2525 to a mail server. Tony -- Tony Toews, Microsoft Access MVP Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ For a convenient utility to keep your users FEs and other files updated see http://www.autofeupdater.com/ Granite Fleet Manager http://www.granitefleet.com/
First
|
Prev
|
Pages: 1 2 Prev: How can I convert a subtitle file into a cue file? Next: Groups Gone Wild |