I use FutureQuest as a web host, and have been with them for over two years. Their service is extremely responsive, and their uptime is incredible. I recommend that you check out their Support/Discussion forums so that you can see for yourself. You will be amazed.
There seems to be a preponderance of highly theoretical books suggested so far. I guess, considering this is/. that one should expect that. But not everyone thinks of programming and networking when they think of computers.
What about people who are thinking about getting into web publishing? I would suggest Philip and Alex's Guide to Web Publishing
, which is a generic look at techniques for and design issues for putting together effective websites. Very common sense advice. The entire book is also available online.
I don't see any suggestions for the Numerical Recipes series, which are extremely practical books, and what a library patron is extremely likely to want:
A quick reference to a numerical algorithm to solve a task at hand.
You would have to select one of the languages that the book is written for, so probably at this point Numerical Recipes in C is the best choice. Even before I learned C, I found this a useful reference for understanding how to implement numerical algorithms. There is quite a bit of narrative. I see that there is a new edition coming out in August 2002. Of course, over a year to wait is quite a while.
Again, they haven't closed port 25 (which is a damn good thing). You should be using your own server to relay your email.
I am a Verizon DSL customer. I run my own mail server. About a week ago, my DSL was down for three days. I got temporary dial-up access from Verizon. Port 25 was blocked.
Actually, technically, you only have to set the From: field on the SMTP envelope to be an @verizon.net e-mail address. What address you actually have in the message header doesn't matter.
I know, because I've tested this out. What happens during a SMTP transaction, is you connect to Verizon's STMP server and tell it (1) Who the mail is from, (2) Who the mail recipient is (who you're sending to), and then the SMTP server decides whether to accept the mail or not. If it does, it issues a command for you to send the data across (the actual e-mail text, which includes the message headers and the message body), and SMTP servers just don't check the data at that point. They simply accept the e-mail.
So, if you got an e-mail program or script, that would allow you to set the message envelop From: to be different than the From: field in the message headers, at least you could send the message through their SMTP with the From: field in the message header that you desire.
I have an account with Verizon that already enforces this type of restriction (was formerly GTE.net and bought out by Verizon). I don't usually use their SMTP server (run my own and/or use my web host's), but I've tested this by writing my own Python mail scripts (which is quite easy to do).
One thing you have to be careful about, though, is that the From: address that you put in your SMTP envelope is the address to which all bounce messages and delivery failure notices will be sent. So, you should probably make it an actual address that you have access to. Otherwise, you will get no notification of failed deliveries.
Ideally you could set up a SMTP server, but that isn't always feasible in the real world, and if Verizon starts blocking outgoing SMTP
Sure, but is that what Verizon really wants to encourage? A lot of clueless newbies delving into running their own SMTP server out of frustration with their inability to send legitimate e-mail through Verizon's SMTP server? I don't think that is advisable. Lots of clueless people inadvertently set up open relays, and then the spammers find them and have a field day! As a matter of fact, this is what would most likely prompt Verizon to start blocking Port 25, is if many of their customers started setting up their own SMTP servers incorrectly such that spammers could relay through them.
I'm sure they will be verifying that the e-mail address specified belongs to the user that is logged in. They can tell to which user a connection belongs either by remembering the username in dial-up, or determining the LEN to which a DSL modem is connected. Verizon doesn't provide cable modems, so that's not their problem. Why is everyone complaining so much about someone trying to stop people from using their servers to spam/forge e-mails?
You're sure, are you? It would be easier for them to simply restrict use of their SMTP server by IP address than to do a verification like that. But, FYI, I am a Verizon customer, the part of the company that was acquired from GTE.net, and we have not been able to use their STMP server with a From: address other than [somestring]@gte.net for a long time now. However, I find that I can put ANYTHING in the [somestring] section, and it doesn't mind. Doesn't in any way check that I am using the UserID/e-mail that they issued me. I imagine, that the larger Verizon company is simply going to expand on this policy that certain parts of the customer base have already been dealing with for quite some time.
And you can relay through their server from any IP address, whether it is theirs or not, as long as you put [somestring]@gte.net or [somestring]@verizon.net in the From field of the e-mail message. At least, it was true a few months ago. I haven't had the opportunity to check recently.
If they are sincere in their efforts to stop SPAM relaying through their servers, then they should implement SMTP AUTH or implement POP before SMTP or something like that. This method they are choosing is incredibly annoying and not very effective.
They are not currently blocking Port 25 on the DSL service (knocking on wood), but my DSL was down for a few days a week or so ago, and they gave me temporary dial-up access, and Port 25 was blocked on that. So those customers are really screwed if they are hosting a website somewhere else. They can't send e-mail through Verizon's SMTP server with the correct From: address, and they can't access the server that their WebHost is providing for them.
Yes, please do send me the URL. I would like to check it out, as a possibility in the future.
Is that $5/month for the fixed IP address? That's the best mark-up I've seen anywhere, of the ones I've looked at in the Los Angeles area. Can I run my own (small) mail server? What's NAT? What is the recommended way, per your company, to hook up a home network via your DSL service?
Yeah, I have SoCal Verizon DSL. The service seems OK from my vantage point, but I see lots of people in the local Verizon newsgroups complaining about it all the time. Particularly, they complaint about the SMTP and POP mail service. Everyone thinks that the NNTP newsfeed is mediocre at best. The FTP for the websites seems to go down a lot. The only service I use from Verizon, besides the connection, is the NNTP. All other services, I get from my web host, or run off my own machine at home.
Anyhow, the thought of going with a local ISP has crossed my mind, because I might need a fixed IP address at some point, and the cost of getting THAT from Verizon is prohibitive (especially compared to the $39/month we're paying right now).
Can a small ISP provide reliable, dependable SMTP/POP/NNTP and website/FTP/TELNET ? If the service is quality, then I would consider going with them. It's just that I've been with two other small ISPs prior to getting Verizon DSL, and frankly, the service wasn't any better.
I have mixed feelings about this. Aside from the fact that it is next to impossible to verify the age of an online respondent, I do not like online sites trying to obtain my children's personal data.
I've spoken with my kids, of course, about NOT giving out phone numbers, addresses, etc... I only let them use the web browser when I'm in the room with them. But one really can't stand over teenagers and preteens every minute they are online. It's not enjoyable for either party, and you have to be able to teach your kids proper behavior and let them practice a bit on their own at some point before they turn 18.
But, I like seeing that someone is looking out for the kids. It is far more serious for a pre-teen to have someone get their real name, address, and so on, than it is for an adult. We try to train our children how to be safe and smart, but they aren't adults yet. And they aren't saavy.
Then again, how does one inform parents and get their permission? It's true, some kids could just sign up for some free e-mail throw-away account, enter it as their parents address, and then respond to the emails sent there, as though they were the parent. When my children have gone to online sites, such as Disney, or Mamamedia (?), I have cringed when they asked for my email address. I didn't want to give out my email and be getting spam. If the kids want to give out their email, and deal with spam, fine. But I don't want it in my mailbox!
In a perfect world, I'd like to see online companies held to such a restriction, that they can't collect or sell personal data on children. (Heck, I'd like to see that enforced for ALL Internet users, regardless of age, but for children especially.) But this isn't a perfect world. I don't see any easy solution.
Parent vigilance is the only way to deal with this at this point.
I agree, I'd like to see this, too. Boy, that would be great if the companies I do business with were not allowed to pass on my address, phone number, etc...
Well, it was nice dreaming, wasn't it?
Slashdot Mirror
I can't get to the third page. /. effect ?
I use FutureQuest as a web host, and have been with them for over two years. Their service is extremely responsive, and their uptime is incredible. I recommend that you check out their Support/Discussion forums so that you can see for yourself. You will be amazed.
Please, come out to my neighborhood and lay the cable for me, will you?
What about people who are thinking about getting into web publishing? I would suggest Philip and Alex's Guide to Web Publishing , which is a generic look at techniques for and design issues for putting together effective websites. Very common sense advice. The entire book is also available online.
A quick reference to a numerical algorithm to solve a task at hand.
You would have to select one of the languages that the book is written for, so probably at this point Numerical Recipes in C is the best choice. Even before I learned C, I found this a useful reference for understanding how to implement numerical algorithms. There is quite a bit of narrative. I see that there is a new edition coming out in August 2002. Of course, over a year to wait is quite a while.
I am a Verizon DSL customer. I run my own mail server. About a week ago, my DSL was down for three days. I got temporary dial-up access from Verizon. Port 25 was blocked.
I know, because I've tested this out. What happens during a SMTP transaction, is you connect to Verizon's STMP server and tell it (1) Who the mail is from, (2) Who the mail recipient is (who you're sending to), and then the SMTP server decides whether to accept the mail or not. If it does, it issues a command for you to send the data across (the actual e-mail text, which includes the message headers and the message body), and SMTP servers just don't check the data at that point. They simply accept the e-mail.
So, if you got an e-mail program or script, that would allow you to set the message envelop From: to be different than the From: field in the message headers, at least you could send the message through their SMTP with the From: field in the message header that you desire.
I have an account with Verizon that already enforces this type of restriction (was formerly GTE.net and bought out by Verizon). I don't usually use their SMTP server (run my own and/or use my web host's), but I've tested this by writing my own Python mail scripts (which is quite easy to do).
One thing you have to be careful about, though, is that the From: address that you put in your SMTP envelope is the address to which all bounce messages and delivery failure notices will be sent. So, you should probably make it an actual address that you have access to. Otherwise, you will get no notification of failed deliveries.
Sure, but is that what Verizon really wants to encourage? A lot of clueless newbies delving into running their own SMTP server out of frustration with their inability to send legitimate e-mail through Verizon's SMTP server? I don't think that is advisable. Lots of clueless people inadvertently set up open relays, and then the spammers find them and have a field day! As a matter of fact, this is what would most likely prompt Verizon to start blocking Port 25, is if many of their customers started setting up their own SMTP servers incorrectly such that spammers could relay through them.
You're sure, are you? It would be easier for them to simply restrict use of their SMTP server by IP address than to do a verification like that. But, FYI, I am a Verizon customer, the part of the company that was acquired from GTE.net, and we have not been able to use their STMP server with a From: address other than [somestring]@gte.net for a long time now. However, I find that I can put ANYTHING in the [somestring] section, and it doesn't mind. Doesn't in any way check that I am using the UserID/e-mail that they issued me. I imagine, that the larger Verizon company is simply going to expand on this policy that certain parts of the customer base have already been dealing with for quite some time.
And you can relay through their server from any IP address, whether it is theirs or not, as long as you put [somestring]@gte.net or [somestring]@verizon.net in the From field of the e-mail message. At least, it was true a few months ago. I haven't had the opportunity to check recently.
If they are sincere in their efforts to stop SPAM relaying through their servers, then they should implement SMTP AUTH or implement POP before SMTP or something like that. This method they are choosing is incredibly annoying and not very effective.
They are not currently blocking Port 25 on the DSL service (knocking on wood), but my DSL was down for a few days a week or so ago, and they gave me temporary dial-up access, and Port 25 was blocked on that. So those customers are really screwed if they are hosting a website somewhere else. They can't send e-mail through Verizon's SMTP server with the correct From: address, and they can't access the server that their WebHost is providing for them.
cobar,
Yes, please do send me the URL. I would like to check it out, as a possibility in the future.
Is that $5/month for the fixed IP address? That's the best mark-up I've seen anywhere, of the ones I've looked at in the Los Angeles area. Can I run my own (small) mail server? What's NAT? What is the recommended way, per your company, to hook up a home network via your DSL service?
Yeah, I have SoCal Verizon DSL. The service seems OK from my vantage point, but I see lots of people in the local Verizon newsgroups complaining about it all the time. Particularly, they complaint about the SMTP and POP mail service. Everyone thinks that the NNTP newsfeed is mediocre at best. The FTP for the websites seems to go down a lot. The only service I use from Verizon, besides the connection, is the NNTP. All other services, I get from my web host, or run off my own machine at home.
Anyhow, the thought of going with a local ISP has crossed my mind, because I might need a fixed IP address at some point, and the cost of getting THAT from Verizon is prohibitive (especially compared to the $39/month we're paying right now).
Can a small ISP provide reliable, dependable SMTP/POP/NNTP and website/FTP/TELNET ? If the service is quality, then I would consider going with them. It's just that I've been with two other small ISPs prior to getting Verizon DSL, and frankly, the service wasn't any better.
I've spoken with my kids, of course, about NOT giving out phone numbers, addresses, etc... I only let them use the web browser when I'm in the room with them. But one really can't stand over teenagers and preteens every minute they are online. It's not enjoyable for either party, and you have to be able to teach your kids proper behavior and let them practice a bit on their own at some point before they turn 18.
But, I like seeing that someone is looking out for the kids. It is far more serious for a pre-teen to have someone get their real name, address, and so on, than it is for an adult. We try to train our children how to be safe and smart, but they aren't adults yet. And they aren't saavy.
Then again, how does one inform parents and get their permission? It's true, some kids could just sign up for some free e-mail throw-away account, enter it as their parents address, and then respond to the emails sent there, as though they were the parent. When my children have gone to online sites, such as Disney, or Mamamedia (?), I have cringed when they asked for my email address. I didn't want to give out my email and be getting spam. If the kids want to give out their email, and deal with spam, fine. But I don't want it in my mailbox!
In a perfect world, I'd like to see online companies held to such a restriction, that they can't collect or sell personal data on children. (Heck, I'd like to see that enforced for ALL Internet users, regardless of age, but for children especially.) But this isn't a perfect world. I don't see any easy solution.
Parent vigilance is the only way to deal with this at this point.
I agree, I'd like to see this, too. Boy, that would be great if the companies I do business with were not allowed to pass on my address, phone number, etc... Well, it was nice dreaming, wasn't it?