how-to block ads
|
|
Uniqs:
19526 |
Share Topic
 |
 |
|
|
|
 bathswifeOriginal Member
join:2000-09-06
Birmingham, AL | reply to NormanS
Re: BellSouth E-mail server Blacklisted? said by NormanS:said by jazzman916:Blacklisting is a common (although largely ineffective) way of reducing spam. I will tell you that statement is wrong; it is very effective at stopping spam from the listed hosts. Nobody would use them, otherwise. I've been turning in spammers for about 4 years now through Spamcop. What I have discovered is that there is absolutely no slow down in the number of spams I receive every day. In fact, I received hundreds per day now. So in the larger scheme of things, I agree with jazzman, blacklisting is ineffective for reducing spam. The spammers know what they're doing, they just find an alternate route. To say that 'nobody would use them otherwise' is sort of like saying nobody would smoke cigarettes if they knew that cigarettes would kill them. Even though I still turn spammers into spamcop now and then when I get a particularly repulsive lot of 'enlarge your penis' and 'impress your girl with huge XXX shots' etc., I've pretty much given up and just use the delete button. What I really wish is that I could send emails back to the spammers explaining that women ARE NOT impressed with ...oh never mind. You know what I mean, what I really want is revenge. Blacklisting ends up causing ME problems....my innocent and legitimate emails get bounced back because some joker used my current dynamic IP address to send spam at some point in the past.
--
jbooksNOSPAM@bellsouth.netremove the "nospam" from the email to email me.mhttp://www.johnsonsusedbooks.com | |
bathswifeOriginal Member
join:2000-09-06
Birmingham, AL | reply to graysonf
said by graysonf:205.152.59.67 is/was not your public IP address. It belongs to one of bellsouth's outgoing mail servers: Name: imf19aec.mail.bellsouth.net Address: 205.152.59.67 Your public IP address that was in effect when you sent the mail appears to be: Name: adsl-63-194-66.bhm.bellsouth.net Address: 208.63.194.66 This address was not the one used for the basis of the rejection, 205.152.59.67 was. Okay, I'm trying to understand this. Where did you get the "adsl-63-194-66"? And how exactly do you find out what your current IP address is? When I looked at my "public IP" address here on the DSLReports site, it showed the 205.152.59.67 as being my IP. Sorry to be so slow on this but I want to make sure I do the right thing when I switch back to static IP. Thanks for using small words and speaking slowly 
--
jbooksNOSPAM@bellsouth.netremove the "nospam" from the email to email me.mhttp://www.johnsonsusedbooks.com | | |
|
bathswifeOriginal Member
join:2000-09-06
Birmingham, AL | reply to NormanS
said by NormanS:Are you running your own mail server? From home? On your residential account? I am not familiar with the Bellsouth AUP/TOS, but, personally, I have no problem if you are doing that. No, I'm not running on my own mail server. I wouldn't have a clue about how to do that sort of thing. I think the problem I'm having explaining my situation is that I have never learned how to properly read a complete email header. I started learning it way back when I signed up for spamcop but got lazy, ahem, busy and didn't do it. Now I think my problem is that I am reading the headers wrong and so giving information wrong.
My goal here is to understand what is happening so I can fix it. I'm thinking that if I switch back to a static IP I will be able to send emails to everyone like I always had been able to before but I'm beginning to think that it might not make any difference which is very depressing.
--
jbooksNOSPAM@bellsouth.netremove the "nospam" from the email to email me.mhttp://www.johnsonsusedbooks.com | |
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:4 Reviews:
 ·SONIC.NET
·Pacific Bell - SBC
| said by bathswife:No, I'm not running on my own mail server. I wouldn't have a clue about how to do that sort of thing... My goal here is to understand what is happening so I can fix it. I'm thinking that if I switch back to a static IP I will be able to send emails to everyone like I always had been able to before but I'm beginning to think that it might not make any difference which is very depressing. No. For your case there will be no difference between the static and the dynamic IP address. Which isn't to say that you shouldn't try to get it back; assuming that you were paying for a static IP package, you should not have been switched to a dynamic IP account.
However, if you are not running a server from your computer, your email is going out through somebody else's SMTP server; in your case, a Bellsouth SMTP server. Your problem with rejected email is separate from, and unrelated to your problem with your lost static IP address. No mail server should reject email from an ISP SMTP server on the basis of the submission IP address; else nobody would be able to send email. My submission IP address is blocked six ways from Sunday just because it is a dynamic IP address.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum | |
bathswifeOriginal Member
join:2000-09-06
Birmingham, AL | said by NormanS:However, if you are not running a server from your computer, your email is going out through somebody else's SMTP server; in your case, a Bellsouth SMTP server. Your problem with rejected email is separate from, and unrelated to your problem with your lost static IP address. No mail server should reject email from an ISP SMTP server on the basis of the submission IP address; else nobody would be able to send email. My submission IP address is blocked six ways from Sunday just because it is a dynamic IP address.
So each time I power off my router and then power it back on I'm sent through a different bellsouth mail server? Argh. How can I change which bellsouth smtp server my mail is sent through? I would like to avoid this problem. --
jbooksNOSPAM@bellsouth.netremove the "nospam" from the email to email me.mhttp://www.johnsonsusedbooks.com | |
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:4 Reviews:
·SONIC.NET
·Pacific Bell - SBC
1 edit | 
SMTP relay diagam. |
said by bathswife:So each time I power off my router and then power it back on I'm sent through a different bellsouth mail server? Argh. How can I change which bellsouth smtp server my mail is sent through? I would like to avoid this problem. No. You set your mail client to use mail.bellsouth.net. The IP address for this server is fixed in DNS. It exists independent of your IP address which you draw from the DHCP address pool. Furthermore, this message submission server need not have the same IP address as the Bellsouth output SMTP server.
There is no way for you to control which Bellsouth output SMTP server sends your email on to the Internet. That is determined entirely by some kind of network traffic management magic. Things work something like this:
You computer gets an IP address from the Bellsouth DHCP pool. When you send email with MS Outlook Express, your computer connects to the BS SMTP server on that server's IP address. In the simplest configuration, that server then does a DNS lookup on the recipient domain to find that domain's MX server; after which, it connects to that MX server. That BS output-to-recipient-MX connection is fixed at one of two IP addresses, as explained earlier. Your computer IP address is well out of this loop by the time that the message is being relayed on to the destination. This relay is between either of two Bellsouth SMTP relay clients, " imf21aec.mail.bellsouth.net [205.152.59.69]", or "imf24aec.mail.bellsouth.net [205.152.59.72]". You have zero control over which of those two servers handles your email.
The diagram I have included shows a schematic of the arrangement. The point at which your email is being rejected is the looping line between the Bellsouth SMTP relay clients and the SBC (prodigy.net) MX server. As you can see, your computer's IP address is not even known to the SBC MX server. At the time an MX server rejects an email, the only foreign IP address that the MX server sees is the connecting SMTP relay client's IP address (oversimplified; some MX servers can examine the message through DATA for content filtering).
Oh, I just picked on the SBC MX server to illustrate the nature of the problem. You should substitute the actual MX server for the domain rejecting your messages.
Addenda:
Bellsouth may have more than the two SMTP relay clients shown in my diagram; some may be blocked, others not. Whether you draw a new IP address may, or may not affect which Bellsouth SMTP servers in their farm will handle your email. Whether your email goes through, or is rejected, is dependent upon which SMTP relay client is handing of the message to the destination MX server.
said by bathswife:Okay, I'm trying to understand this. Where did you get the "adsl-63-194-66"? And how exactly do you find out what your current IP address is? A couple of places to find your IP address:
»www.whatismyip.com/
»myip.dslextreme.com/
BTW, that second one shows why I am sometimes confused in this forum; DSL Extreme is not only the name of a level of Bellsouth DSL service, it is also the name of a CLEC DSL service provider who could have serviced my premises if I hadn't started up on Pacbell DSL (now SBC AT&T) service.
More interesting information can be found here (by filling in the blanks):
»www.dnsstuff.com/
Your IP address should be visible near the upper right corner on the DNSStuff page.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum | |
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:4 Reviews:
·SONIC.NET
·Pacific Bell - SBC
1 edit | reply to bathswife
said by bathswife:I've been turning in spammers for about 4 years now through Spamcop. What I have discovered is that there is absolutely no slow down in the number of spams I receive every day. In fact, I received hundreds per day now. So in the larger scheme of things, I agree with jazzman, blacklisting is ineffective for reducing spam. The spammers know what they're doing, they just find an alternate route. To say that 'nobody would use them otherwise' is sort of like saying nobody would smoke cigarettes if they knew that cigarettes would kill them. Very bad analogy; that "smoking" example. You are turning in spammers through SpamCop; I do that also.
From my standpoint, running an MX server, DNSBLs work very well. I have received, maybe, twenty spam email messages, tops, to my domain this year. Not for a lack of the spammers trying; my MTA logs show a few hundred attempts (or more) over that past year. Here is a sample from the last twenty-four hours (or so):
T 20051222 120439 43a97e40 Connection from 68.117.186.201
T 20051222 120440 43a97e40 HELO 68-117-186-201.dhcp.mtgm.al.charter.com
T 20051222 120444 43a97e40 MAIL FROM: <iyiab@doramail.comE>
E 20051222 120444 43a97e40 Host 68.117.186.201 blocked by Spamhaus - message rejected.
T 20051222 120445 43a97e40 QUIT
T 20051222 120445 43a97e40 Connection closed with 68.117.186.201, 6 sec. elapsed.
T 20051222 132528 43a97e43 Connection from 200.104.78.84
T 20051222 132530 43a97e43 HELO pc-84-78-104-200.cm.vtr.net
T 20051222 132531 43a97e43 MAIL FROM: <owbcbprzvhcafo@freemail.lt>
E 20051222 132531 43a97e43 Host 200.104.78.84 blocked by Spamhaus - message rejected.
T 20051222 132532 43a97e43 QUIT
T 20051222 132532 43a97e43 Connection closed with 200.104.78.84, 4 sec. elapsed.
T 20051222 134327 43a97e44 Connection from 200.207.43.217
T 20051222 134328 43a97e44 ehlo friend
T 20051222 134328 43a97e44 MAIL FROM:<gilbert@englishforum.biz>
E 20051222 134328 43a97e44 Host 200.207.43.217 blocked by Spamhaus - message rejected.
T 20051222 134329 43a97e44 Connection closed with 200.207.43.217, 2 sec. elapsed.
T 20051222 161143 43a97e48 Connection from 68.57.161.152
T 20051222 161144 43a97e48 HELO pcp09063693pcs.centrl01.va.comcast.net
T 20051222 161144 43a97e48 MAIL FROM: <qupcwlwbu@erg.it>
E 20051222 161146 43a97e48 Host 68.57.161.152 blocked by Spamhaus - message rejected.
T 20051222 161146 43a97e48 QUIT
T 20051222 161146 43a97e48 Connection closed with 68.57.161.152, 3 sec. elapsed.
T 20051222 165912 43a97e4b Connection from 200.67.219.248
T 20051222 165912 43a97e4b HELO localhost
E 20051222 165912 43a97e4b 554 Invalid host name - message rejected; see: HTTP://antispam.aosake.net.
T 20051222 165913 43a97e4b Connection closed with 200.67.219.248, 1 sec. elapsed.
E 20051222 165913 0 Connection from 200.67.219.248 refused because of short-term restriction.
E 20051222 165913 0 Connection from 200.67.219.248 refused because of short-term restriction.
T 20051222 172333 43a97e4d Connection from 70.37.42.211
T 20051222 172333 43a97e4d HELO temecula-cuda1-70-37-42-211.ontrca.adelphia.net
T 20051222 172333 43a97e4d MAIL FROM: <ruane@alcoa.com>
E 20051222 172333 43a97e4d Host 70.37.42.211 blocked by Spamhaus - message rejected.
T 20051222 172333 43a97e4d QUIT
T 20051222 172333 43a97e4d Connection closed with 70.37.42.211, 0 sec. elapsed.
T 20051222 191255 43a97e51 Connection from 69.60.133.212
T 20051222 191255 43a97e51 EHLO socialclass.org
T 20051222 191255 43a97e51 MAIL FROM:<ew-update@paypal.com>
E 20051222 191256 43a97e51 Host 69.60.133.212 blocked by SpamCop (Tag only) - message tagged.
T 20051222 191256 43a97e51 RCPT To:<nanae@aosake.net>
E 20051222 191256 43a97e51 554 Recipient address rejected: User not allowed in recipient maps table (in reply to RCPT TO command)
T 20051222 191256 43a97e51 Connection closed with 69.60.133.212, 1 sec. elapsed.
T 20051222 194017 43a97e53 Connection from 68.68.91.132
T 20051222 194018 43a97e53 helo localhost
E 20051222 194018 43a97e53 554 Invalid host name - message rejected; see: HTTP://antispam.aosake.net.
T 20051222 194018 43a97e53 Connection closed with 68.68.91.132, 1 sec. elapsed.
T 20051222 211638 43a97e57 Connection from 68.164.107.254
T 20051222 211639 43a97e57 HELO h-68-164-107-254.sfldmidn.covad.net
T 20051222 211639 43a97e57 MAIL FROM: <%nameheixmkiqn.%nameneca@msa.hinet.net >
E 20051222 211639 43a97e57 Killfile: Mail from '<%nameheixmkiqn.%nameneca@msa.' rejected, talking to 68.164.107.254
T 20051222 211640 43a97e57 QUIT
T 20051222 211640 43a97e57 Connection closed with 68.164.107.254, 2 sec. elapsed.
T 20051222 215513 43a97e59 Connection from 24.49.219.125
T 20051222 215513 43a97e59 HELO ny-lancastercadent4g1-3d-b-125.buf.adelphia.net
T 20051222 215513 43a97e59 MAIL FROM: <stephen@firstadvantage.com>
E 20051222 215513 43a97e59 Host 24.49.219.125 blocked by Spamhaus - message rejected.
T 20051222 215514 43a97e59 QUIT
T 20051222 215514 43a97e59 Connection closed with 24.49.219.125, 1 sec. elapsed.
T 20051222 221510 43a97e5a Connection from 82.193.148.36
T 20051222 221510 43a97e5a HELO localhost
E 20051222 221510 43a97e5a 554 Invalid host name - message rejected; see: HTTP://antispam.aosake.net.
T 20051222 221511 43a97e5a Connection closed with 82.193.148.36, 1 sec. elapsed.
E 20051222 221511 0 Connection from 82.193.148.36 refused because of short-term restriction.
E 20051222 221512 0 Connection from 82.193.148.36 refused because of short-term restriction.
T 20051222 232802 43a97e5d Connection from 202.83.52.86
T 20051222 232802 43a97e5d ehlo friend
T 20051222 232803 43a97e5d MAIL FROM:<simon@funeasy.biz>
E 20051222 232807 43a97e5d Host 202.83.52.86 blocked by SpamCop (Tag only) - message tagged.
T 20051222 232807 43a97e5d RCPT TO:<salty.dog@aosake.net>
E 20051222 232807 43a97e5d 554 Recipient address rejected: User not allowed in recipient maps table (in reply to RCPT TO command)
T 20051222 232807 43a97e5d Connection closed with 202.83.52.86, 5 sec. elapsed.
T 20051222 234017 43a97e5e Connection from 200.199.240.11
T 20051222 234018 43a97e5e HELO 71.131.252.146
E 20051222 234018 43a97e5e 554 Misconfigured host - message rejected; see: HTTP://antispam.aosake.net.
T 20051222 234027 43a97e5e Connection closed with 200.199.240.11, 10 sec. elapsed.
T 20051222 234432 43a97e5f Connection from 24.85.151.208
T 20051222 234432 43a97e5f HELO localhost
E 20051222 234432 43a97e5f 554 Invalid host name - message rejected; see: HTTP://antispam.aosake.net.
T 20051222 234432 43a97e5f Connection closed with 24.85.151.208, 0 sec. elapsed.
E 20051222 234432 0 Connection from 24.85.151.208 refused because of short-term restriction.
E 20051222 234432 0 Connection from 24.85.151.208 refused because of short-term restriction.
T 20051222 234447 43a97e60 Connection from 203.139.25.14
T 20051222 234447 43a97e60 Connection closed with 203.139.25.14, 0 sec. elapsed.
T 20051222 234542 43a97e61 Connection from 80.143.67.251
T 20051222 234542 43a97e61 helo localhost
E 20051222 234542 43a97e61 554 Invalid host name - message rejected; see: HTTP://antispam.aosake.net.
T 20051222 234542 43a97e61 Connection closed with 80.143.67.251, 0 sec. elapsed.
T 20051222 234742 43a97e62 Connection from 211.253.176.115
T 20051222 234745 43a97e62 HELO 71.131.252.146
E 20051222 234745 43a97e62 554 Misconfigured host - message rejected; see: HTTP://antispam.aosake.net.
T 20051222 234745 43a97e62 Connection closed with 211.253.176.115, 3 sec. elapsed.
T 20051222 234752 43a97e63 Connection from 202.112.115.35
T 20051222 234752 43a97e63 Connection closed with 202.112.115.35, 0 sec. elapsed.
T 20051223 004929 43ab43bb Connection from 211.162.200.140
T 20051223 004933 43ab43bb HELO 71.131.252.146
E 20051223 004933 43ab43bb 554 Misconfigured host - message rejected; see: HTTP://antispam.aosake.net.
T 20051223 004934 43ab43bb Connection closed with 211.162.200.140, 5 sec. elapsed.
T 20051223 005015 43ab43bc Connection from 170.215.43.234
T 20051223 005102 43ab43bc Connection closed with 170.215.43.234, 47 sec. elapsed.
T 20051223 005133 43ab43bd Connection from 220.232.98.234
T 20051223 005134 43ab43bd HELO 71.131.252.146
E 20051223 005134 43ab43bd 554 Misconfigured host - message rejected; see: HTTP://antispam.aosake.net.
T 20051223 005135 43ab43bd Connection closed with 220.232.98.234, 2 sec. elapsed.
T 20051223 013337 43ab43c1 Connection from 70.68.252.252
T 20051223 013337 43ab43c1 helo localhost
E 20051223 013337 43ab43c1 554 Invalid host name - message rejected; see: HTTP://antispam.aosake.net.
T 20051223 013337 43ab43c1 Connection closed with 70.68.252.252, 0 sec. elapsed.
T 20051223 014258 43ab43c3 Connection from 83.55.78.122
T 20051223 014300 43ab43c3 HELO 122.Red-83-55-78.dynamicIP.rima-tde.net
T 20051223 014303 43ab43c3 MAIL FROM: <nradford@itftaekwondo.com>
E 20051223 014303 43ab43c3 Host 83.55.78.122 blocked by Spamhaus - message rejected.
T 20051223 014310 43ab43c3 QUIT
T 20051223 014310 43ab43c3 Connection closed with 83.55.78.122, 12 sec. elapsed.
T 20051223 014347 43ab43c4 Connection from 219.21.152.5
T 20051223 014408 43ab43c4 Connection closed with 219.21.152.5, 21 sec. elapsed.
T 20051223 014409 43ab43c5 Connection from 204.50.71.156
T 20051223 014410 43ab43c5 HELP
T 20051223 014410 43ab43c5 Connection closed with 204.50.71.156, 1 sec. elapsed.
T 20051223 031959 43ab43ca Connection from 24.158.94.77
T 20051223 032007 43ab43ca HELO 24-158-94-077.dhcp.chtn.wv.charter.com
T 20051223 032008 43ab43ca MAIL FROM: <bqbxjufc@fds.com>
E 20051223 032008 43ab43ca Host 24.158.94.77 blocked by Spamhaus - message rejected.
T 20051223 032040 43ab43ca QUIT
T 20051223 032040 43ab43ca Connection closed with 24.158.94.77, 41 sec. elapsed.
T 20051223 034312 43ab43cc Connection from 82.50.56.50
T 20051223 034313 43ab43cc HELO host50-56.pool8250.interbusiness.it
T 20051223 034314 43ab43cc MAIL FROM: <hlgfbqqar@centrapoint.com>
E 20051223 034314 43ab43cc Host 82.50.56.50 blocked by Spamhaus - message rejected.
T 20051223 034317 43ab43cc QUIT
T 20051223 034317 43ab43cc Connection closed with 82.50.56.50, 5 sec. elapsed.
T 20051223 105836 43abd46e Connection from 211.73.164.25
T 20051223 105836 43abd46e helo localhost
E 20051223 105836 43abd46e 554 Invalid host name - message rejected; see: HTTP://antispam.aosake.net.
T 20051223 105836 43abd46e Connection closed with 211.73.164.25, 0 sec. elapsed.
T 20051223 114136 43abd479 Connection from 62.143.13.167
T 20051223 114136 43abd479 HELO ip167.13.1411N-CUD12K-02.ish.de
T 20051223 114136 43abd479 MAIL FROM: <nadon@imrgold.com>
E 20051223 114137 43abd479 Host 62.143.13.167 blocked by NJABL - message rejected.
T 20051223 114138 43abd479 QUIT
T 20051223 114138 43abd479 Connection closed with 62.143.13.167, 2 sec. elapsed.
T 20051223 121036 43abd47b Connection from 82.154.158.147
T 20051223 121037 43abd47b HELO bl5-158-147.dsl.telepac.pt
T 20051223 121038 43abd47b MAIL FROM: <pbwqvzdxlsy@msn.com>
E 20051223 121040 43abd47b Host 82.154.158.147 blocked by NJABL - message rejected.
T 20051223 121041 43abd47b QUIT
T 20051223 121041 43abd47b Connection closed with 82.154.158.147, 5 sec. elapsed.
T 20051223 131707 43abd47d Connection from 71.252.159.223
T 20051223 131707 43abd47d helo localhost
E 20051223 131707 43abd47d 554 Invalid host name - message rejected; see: HTTP://antispam.aosake.net.
T 20051223 131707 43abd47d Connection closed with 71.252.159.223, 0 sec. elapsed.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum | |
 graysonfPremium,MVM
join:1999-07-16
Fort Lauderdale, FL | reply to bathswife
You pasted the header from the rejected mail. In that header was the Received: header inserted by the bellsouth mail server that handled your message. That Received header contained your IP address, 208.63.194.66. A reverse lookup of that IP yields adsl-63-194-66.bhm.bellsouth.net.
One very simple way to determine your current IP address is to surf to this link:
»checkip.dyndns.org/
I don't see how it's possible you had an IP address that belongs to a bellsouth.net mail server. | |
 GizguyPremium
join:2003-01-23
Alpharetta, GA | reply to graysonf
Isn't this fun..... two hours after I sent my 12:25pm email a reject message was received - once again reporting the Bellsouth outgoing email with ip address of 205.152.59.69 as the cause of the rejection. Perhaps it takes some time for '»www.us.sorbs.net ' to update the removal of this IP address from '»www.mxtoolbox.com ' , or maybe sorbs.net is rejecting the mail for another reason. In all fairness, it may just be a problem between BellSouth and the receiving email system since all of my other POP mail is not rejecting.
Again as I posted earlier, when I send an POP email to this one recipient from the same PC, with same DSL IP address, but I send it using a non-BellSouth email ID through Google's GMAIL smtp server (outgoing port of 465) the message is not rejected. Similarly if I send the mail using the smtp server of the web hosting company I use (not using port 25) it gets through fine.
So it appears to be a problem within the BellSouth Email system - which many on this forum have reported as being very weak. It even failed when I sent the message using BellSouth's Webmail.
Please note, that regardless of what email address I use (BellSouth, or my personal domain address), the mail rejects for this one recipient only when I use the BellSouth.Net (port 25) mail server. I'm not going to lose any sleep over this as I am now sending all of my POP email via Google's SMTP server and/or my web hosting server. However, if BellSouth ever prevents me from using these alternatives, then I guess I'll switch to an alternative broadband provider. | |
bathswifeOriginal Member
join:2000-09-06
Birmingham, AL | reply to NormanS
Okay, great diagram and information. At least there is a glimmer of hope that I might understand all of this because I have a place to start.
I can see I am going to have to start reading a bunch of technical stuff to try to understand and you all have been very helpful. I appreciate that.
Yes, it was a bad analogy and really all I was pointing out is that I get more spam now than I ever did before and that turning spammers in hasn't decreased the number of spams I receive every day.
Now that I realize that my ip address doesn't make any difference I am wondering why change it to a static ip address at all.
I have a lot to think about and really, thanks to everybody who has tried to explain all this to me. I'm not a stupid person but understanding this sort of thing is sort of like looking at a map and having a feel for directions and that is a talent I am unfortunately without.
--
jbooksNOSPAM@bellsouth.netremove the "nospam" from the email to email me.mhttp://www.johnsonsusedbooks.com | |
bathswifeOriginal Member
join:2000-09-06
Birmingham, AL | reply to graysonf
said by graysonf:(snip) I don't see how it's possible you had an IP address that belongs to a bellsouth.net mail server. I don't either after reading all the information you guys have posted. The only thing I can think is that I must have had a dyslexic moment when looking at my ip last night. Thanks again for being so patient.
I'm still not totally convinced that powering off my router and getting a new ip address doesn't help take care of the problem of bounced emails but I'm not completely married to that idea and realize it could be coincidence.
--
jbooksNOSPAM@bellsouth.netremove the "nospam" from the email to email me.mhttp://www.johnsonsusedbooks.com | |
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:4 Reviews:
·SONIC.NET
·Pacific Bell - SBC
| reply to bathswife
said by bathswife:Yes, it was a bad analogy and really all I was pointing out is that I get more spam now than I ever did before and that turning spammers in hasn't decreased the number of spams I receive every day. Now that I realize that my ip address doesn't make any difference I am wondering why change it to a static ip address at all. I have a lot to think about and really, thanks to everybody who has tried to explain all this to me. I'm not a stupid person but understanding this sort of thing is sort of like looking at a map and having a feel for directions and that is a talent I am unfortunately without. Spam reaching your Inbox is a measure of the degree of filtering your email provider is using. Unfortunately, an ISP with the customer base of Bellsouth can't afford to be as aggressive at blocking as much smaller ISP. Corporate email services can also be more aggressive. I use a DNSBL which targets Brazil, China, and Korea, but my ISP, SBC, couldn't afford to use that DNSBL because they have a larger customer base of people with relations in Brazil, China, or Korea.
I decided to buy a domain, and run my own MTA when I realized that SBC did not explicitly prohibit that for DSL lines, and that I could employ more aggressive blocking techniques than SBC was able to use. Unfortunately, without a static IP address and a ptr record reflecting my MX configuration, there are recipient domains, such as those run by AOL (@aol.com, @aim.com, @compuserve.com, @netscape.net, and some others), which refuse to accept connections from SMTP relay clients hosted on dynamic IP addresses. So I use one of the SBC SMTP servers as a "smarthost", an SMTP relay for my domain. This leaves me at the mercy of the same kind of problem you are having; and AOL, in particular, has been known to block the SBC relay clients from time to time.
A static IP address has its uses. If I could justify the price, I'd pay for a static IP package from SBC, or DSL Extreme. I could get either to set up a ptr record reflecting my domain name, and then run a proper SMTP end-to-end relay client. Then I wold not have to worry about AOL, and others, doing to the SBC SMTP relay clients the same as you are seeing with the Bellsouth SMTP relay clients. However, with the exception of running some kind of server, there is no real advantage to a static IP address.
Map reading I am good at. Schematics reading is something else, entirely. I could look at a schematic of a circuit all day, and have a hard time picturing how the circuit in the schematic would translate into readings on a DVM display, or 'scope CRT. For somebody who just wants to use the Internet, knowing the details of how the Internet works is kind of like trying to learn how the internal combustion engine works when all you need is to drive the car from home to work, and back.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum | |
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:4 Reviews:
·SONIC.NET
·Pacific Bell - SBC
| reply to Gizguy
said by Gizguy:Again as I posted earlier, when I send an POP email to this one recipient from the same PC, with same DSL IP address, but I send it using a non-BellSouth email ID through Google's GMAIL smtp server (outgoing port of 465) the message is not rejected. Similarly if I send the mail using the smtp server of the web hosting company I use (not using port 25) it gets through fine. So it appears to be a problem within the BellSouth Email system - which many on this forum have reported as being very weak. It even failed when I sent the message using BellSouth's Webmail. Technically, you don't send POP email. POP, or "Post Office Protocol" describes the method of accessing email from a mailbox. But you send email either through a client which uses the "Simple Mail Transfer Protocol" (SMTP), or a web form. Either way, once the email submission is complete, the process is SMTP all the way to the Mail Delivery Agent (MDA), which is the SMTP server which puts the email into the mailbox. After that, you access your email either by using a POP3 client to download the message, or using an IMAP client, or web browser, to access the message store on-line.
When you use a web form for email submission, there is an interaction between the HTTP client, which submits your email, and an SMTP submission server, which accepts the message for transfer. After that, your email may take the same path to the edge of the ISP network. So it is likely that Bellsouth email is handled by the same output servers, whether the submission was handled by an SMTP client, such as MS Outlook Express, or a web browser, such as MS Internet Explorer.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum | |
tberg
join:2001-08-23
Greenville, SC | reply to NormanS
I get very little spam. I have my own domain, host the mail "out on the internet" and forward it all to my Bellsouth accounts. I do my own spam filtering at my host and Bellsouth also does spam filtering themselves. I get double spam-filtering. The spam that does get through is almost always to my bellsouth address, not my own domain name.
Also, my family and I are very careful how we use our domain and its e-mail. We don't download "free" screensavers, etc. If an e-mail address is required, we use a Juno or Hotmail account. We don't give our "real" address to anyone we don't know. That more than anything else helps the spam. | |
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:4 Reviews:
·SONIC.NET
·Pacific Bell - SBC
| That is one advantage of having your own domain, and hosting it yourself. You can control the level of filtering to suit your ideals. I run my own MTA on my SBC line because there is no explicit prohibition in the SBC TOS (the prohibitions are against dial-up users running servers, and against running open relay mail servers).
I can create my own aliases, and kill them, if needed. Also, Yahoo!, SBC's partner in the ISP business, now has AddressGuard, a system for creating disposable email addresses; up to 500 of them.
I see hardly any spam to my domain email accounts, and I have basically overfiltered my older accounts which were heavily spammed. Nobody I correspond with uses them, so they are blocked to the max. The ditzy spammers can spam them to their heart's content; I don't see any of it.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum | |
DirtyMic
join:2003-11-19
Pompano Beach, FL | This is from Bellsouth's postmaster site:
Block Issues
If you are not a BellSouth subscriber and you believe that BellSouth Internet Services is blocking your e-mail, please contact postmaster @ bellsouth.net (remove the spaces) with the subject line “Block”.
"If you are a BellSouth customer and your IP address has been listed on an e-mail block list, please send an e-mail with the following information to AUPGeneral @ bellsouth.net (without the spaces): your IP address, name, and e-mail address, who is blocking you, the exact bounce error message (if any), and your contact information. Please put the following in the subject line "Block Request Removal Assistance", and we will make every effort to assist you with this matter.
If you are a Bellsouth customer and you feel we are blocking e-mail that you wish to receive, please contact BellSouth Technical Support at 888-321-2375."
The URL:
http://postmaster.bellsouth.net/ | |
 drhea
join:2000-02-12
Pompano Beach, FL
1 edit | reply to Gizguy
How about this... assuming you are running a Westell modem like most of us... try »192.168.1.254 (that's the default IP address for the Westell Modem/Router).
Click home and you should see all of your connection info. The one labeled "IP Address" is you current IP address.
I'm not sure it this works for USB connections, but if the modem is using ethernet, you should see your modem respond to you. One other caviat, if you have the Westell as a bridge and something else as your router... your router should have your IP address.
--
Dan Rhea - Windows programmer | |
|
