List Readers, I could use some help. I have a CSS table - with an external style sheet - that won't center for me. I have tried all the tricks that I know but just can't seem to find the one thing that I have wrong. I have tried centering it on the page and on the style sheet too, but can't seem to get the right combination. It looks centered on my computer, but we have two more in the house and it isn't centered on them. I tired looking at it with IE, Firefox and Safari, all have the same look - a table on the left. It is here at this link - at all of these pages A - F. http://www.rootsweb.ancestry.com/~mobarry/photos/index.htm Help appreciated. Donna Cooper

Will - > My messages to this list are not being blocked. > My messages to gen-medieval@rootsweb.com are. You have, basically, a list problem. You could take it up with the list admin. Alternatively, there is a helpdesk at RootsWeb for problems. On this list you are only contacting fellow RootsWeb users. Go to http://rootsweb.custhelp.com , and the "Ask a Question" tab, and take it from there. It may be the technical folk behind the scenes can look into this more for you. Wendy

One of two ways...click on the HELP tab on any RootsWeb page and follow the instructions or send an email to: HelpDesk-post@rootsweb.com . However, I will tell you that the email approach may also result in a SORBS bounce if the email goes through a blacklisted server. Joan In a message dated 8/27/2010 3:26:09 P.M. Eastern Daylight Time, WJhonson@aol.com writes: You said to post to the rootsweb help desk. How.

On Fri, Aug 27, 2010 at 3:25 PM, <WJhonson@aol.com> wrote: > You said to post to the rootsweb help desk. > > How. > Go to www.rootsweb.com Click Help. Post your question / problem.

You said to post to the rootsweb help desk. How.

In a message dated 8/27/2010 12:08:40 PM Pacific Daylight Time, WJhonson@aol.com writes: > rootsweb-help@rootsweb.com

For the record, I just had a list message blocked by SORBS and resent it immediately and it went through. The copy that bounced went through the mail server with the IP address of: 64.12.78.142 and the one that worked was sent through: 64.12.78.137. I got lucky the second time around. The one that got blocked: ----- The following addresses had permanent fatal errors ----- <senior-newbie@rootsweb.com> (reason: 550 5.7.1 <senior-newbie@rootsweb.com>... Rejected: 64.12.78.142 listed at dnsbl.sorbs.net) The one that went through about one minute later: Received: from imo-ma02.mx.aol.com (imo-ma02.mx.aol.com [64.12.78.137]) Joan

It isn't an idea--it's how it works. SORBS gets us all from time to time and we just have to keep resending until the email goes through. It's hit or miss. I do have one suggestion: why not contact the RootsWeb HelpDesk and explain that you feel they should not be using SORBS because it is blocking much or your legit list mail? Personally I wish they wouldn't use it either, but I do realize the extent of the spam problem and the impact on the RootsWeb servers. Joan In a message dated 8/27/2010 1:08:48 P.M. Eastern Daylight Time, WJhonson@aol.com writes: JYoung6180@aol.com writes: > AOL sends out the > mail choosing the servers randomly -- so eventually if you keep > resending, the > message will go through a server that isn't blocked and get through. I just sent the same message 12 times, and 12 times it bounced. Any other ideas

At 01:08 PM 8/27/2010, WJhonson@aol.com wrote: >I just sent the same message 12 times, and 12 times it bounced. >Any other ideas > I checked the headers for the messages you have sent to Rootsweb-Help. Here is the list of the time stamps and the IP addresses which are obviously NOT blacklisted: 11:21 EDT [64.12.207.164] 11:35 EDT [205.188.105.143] 12:03 EDT [64.12.207.164] note this one is the same as the 11:21 message. 12:17 EDT [205.188.105.146] 12:47 EDT [205.188.91.96] 13:08 EDT [205.188.91.97] 13:19 EDT [64.12.206.40] If the bounces you are receiving include the full headers of the bounced message, check them for the line that says Received: from imr-ma02.mx.aol.com (imr-ma02.mx.aol.com [xxx.xxx.xxx.xxx]) by mail.rootsweb.com The xxx address will be different from any of those listed above and is the one being blocked. As Joan said, it is the luck of the draw which server AOL chooses to send your mail. As Judy said, it like a football receiver stepping out of bounds. He can't carry the ball to the end zone for the touchdown. You must run the play again until you reach a server that is able to complete the play and deliver the mail. Pat Asher

On Fri, Aug 27, 2010 at 12:47 PM, <WJhonson@aol.com> wrote: > Wrong Joan. > The mail is being blocked at the receiving point, not at the sending point. > The headers explain clearly that it's Rootsweb who is blocking the mail. > > > ==== Hi Will, Let me try to explain. I tend to use analogies, so I hope you don't mind. Let me use Football (the sport) as a way to simplify the explanation. Sending a mail is kinda like a football team. You are like a quarterback--- you throw out a football (E-mail) in any direction (to any List or person), AOL, Yahoo, GoogleMail or any other ISP are like receivers; you intend as the quarterback to get your football (E-mail) from you to any ISP you use as an E-mail sender. But around the team's receiver (here AOL) are other players...the servers that each ISP uses. Any particular team member in a football game can get blocked, knocked down, commit some error (I forget what they are called in football). But, team members might also function well in a game. An Umpire (SORBS) are hired to watch the ball (E-mail) and prevent or punish errors (team players who do wrong things). A receiver can be puniished if they make a mistake, but most often it is just one or two team players (the servers in AOL) who are punished. The UMP (SORBS) sometimes reacts by sidelining (penaliizing) the team player (server -- who plays around a receiver, the ISP). Sidelining of course would only happen if the offense (abuse of e-mail) was a big offense (s*p*a*m*). And just liike in sports, some penalities carry a monetary fine (in this case, the ISP who offends must pay a fee to correct the bad behavior and promise not to do it again). Although in a Football game, everyone knows the types of penalities, length of penalties, etc., in the world of E-mail only the Umpire (SORBS) and the receiver (the ISP) know the length of the punishment, when it will end, etc. BUT, in terms of the other players (other servers), they can still "play". So if one team player (server) has been sidelined (blacklisted), the quarterback (you) may still be lucky enough to get the ball (your E-mail) to another team player (another server) who is not sidelined (blacklisted) and the team player who catches your ball (E-mail) may run it all the way down-field (through all the hand-offs that occur in sending an E-mail) to the end-zone (to the goal: your E-mail had arrived to its destination). So, when Pat or Joan says to try again, they mean you may get lucky to hit another team player (server) and get your e-mail through that try. You as the quarterback doesn't pay the financial penalty for a receiver's mistakes. However, you may be inconvenienced and may lose that game (getting that E-mail through). Hope I didn't slaughter the analogy very much. Judy

Fines paid to SORBS go to the Joey McNicol Legal Defense Fund, the *sole* approved "charity" on their site. That case has been *over* for EIGHT years. Eight. Not one, not a month... eight years. And rootsweb supports this extortion and fraud. Very nice.

In a message dated 8/27/2010 9:59:47 AM Pacific Daylight Time, JYoung6180@aol.com writes: > AOL sends out the > mail choosing the servers randomly -- so eventually if you keep > resending, the > message will go through a server that isn't blocked and get through. I just sent the same message 12 times, and 12 times it bounced. Any other ideas

Yes--that is precisely what I wrote. The AOL server is on the SORBS blacklist so when the email hits RootsWeb it bounces it back because RootsWeb uses SORBS as a filtering tool. It all depends on WHICH AOL mail server the mail is sent from--that doesn't mean AOL is doing the blocking--they are NOT--they are the ones BEING blocked erroneously by SORBS. AOL sends out the mail choosing the servers randomly -- so eventually if you keep resending, the message will go through a server that isn't blocked and get through. Joan In a message dated 8/27/2010 12:48:08 P.M. Eastern Daylight Time, WJhonson@aol.com writes: Wrong Joan. The mail is being blocked at the receiving point, not at the sending point. The headers explain clearly that it's Rootsweb who is blocking the mail.

Wrong Joan. The mail is being blocked at the receiving point, not at the sending point. The headers explain clearly that it's Rootsweb who is blocking the mail.

The reason SOME emails get blocked and others do not is because AOL uses many mail servers and it all depends (like the roll of dice) which mail server a particular email you sent went out through. If it happened to go out through one that SORBS has a temporary block on -- then you get the bounce from RootsWeb. If it goes out through a mail server that is NOT blocked, it goes through. It doesn't matter what list you are sending the email TO but rather it is determined by which mail server your message happens to go out through. Joan In a message dated 8/27/2010 12:17:25 P.M. Eastern Daylight Time, WJhonson@aol.com writes: My messages to this list are not being blocked. My messages to gen-medieval@rootsweb.com are. Explain that. Pat answers aren't very helpful. Sorbs is a horrible horrible awful worthless spam filter. All you have to do is google for it, and read the thousands of messages about how bad they are. My messages have been being blocked for several days now. Not just one message. I just today figured out why. And the answer makes me spitting mad. Absolutely furious.

In a message dated 8/27/2010 9:07:51 AM Pacific Daylight Time, JYoung6180@aol.com writes: > WHO is going to have to pay a fine? > > AOL mail servers and those of some other ISPs occasionally get blacklisted > > by SORBS temporarily. RootsWeb uses SORBS as one of its spam filtering > tools. When your emails intended for a list get bounced back for this > reason > just resend them until they go through--often the very next time you try > to > send them, they go through successfully. > > Joan My messages to this list are not being blocked. My messages to gen-medieval@rootsweb.com are. Explain that. Pat answers aren't very helpful. Sorbs is a horrible horrible awful worthless spam filter. All you have to do is google for it, and read the thousands of messages about how bad they are. My messages have been being blocked for several days now. Not just one message. I just today figured out why. And the answer makes me spitting mad. Absolutely furious.

Will- WHO is going to have to pay a fine? AOL mail servers and those of some other ISPs occasionally get blacklisted by SORBS temporarily. RootsWeb uses SORBS as one of its spam filtering tools. When your emails intended for a list get bounced back for this reason just resend them until they go through--often the very next time you try to send them, they go through successfully. Joan In a message dated 8/27/2010 11:21:48 A.M. Eastern Daylight Time, WJhonson@aol.com writes: My email messages to a rootsweb mailing list are bouncing because of a sorbs blacklist. Their site states that I'm going to have to pay a FINE to get this cleared up. What's up with that? Will Johnson

In a message dated 8/27/2010 8:59:49 AM Pacific Daylight Time, pjroots@att.net writes: > Will, > > The "fine" is not paid to RootsWeb, and it is not YOU who would pay > it. The ISP who is allowing sp*m to be sent through their servers is > the one who would pay SORBS to remove the blacklisting and promise to > close any open relays <g> > > In the case of AOL, one of their mail servers may have been > blacklisted accidentally because someone reported as sp*m mail that > was sent through that server. AOL will clear it up with SORBS. It > usually happens fairly quickly. > > > Pat Asher I don't think you are understanding that my emails are going through just fine. It's ROOTSWEB that is blocking them. Not AOL. I'm using Aol right now aren't I? And you're reading my mail aren't you? So explain that. No one else, and I send at *least* fifty emails every day, is bouncing. Just Rootsweb. And evidently just gen-medieval, not even all of Rootsweb. If AOL were blocking them, then you wouldn't see this. Will Johnson

At 11:35 AM 8/27/2010, WJhonson@aol.com wrote: >Like I said, their site states that I'm going to have to pay a fine. >I already said that. The point is, why is rootsweb doing this, not why is >Sorbs doing this. >They are doing it to make money off suckers. Why is rootsweb doing it. Will, The "fine" is not paid to RootsWeb, and it is not YOU who would pay it. The ISP who is allowing sp*m to be sent through their servers is the one who would pay SORBS to remove the blacklisting and promise to close any open relays <g> In the case of AOL, one of their mail servers may have been blacklisted accidentally because someone reported as sp*m mail that was sent through that server. AOL will clear it up with SORBS. It usually happens fairly quickly. Pat Asher

In a message dated 8/27/2010 8:29:16 AM Pacific Daylight Time, nrcnsdar@gmail.com writes: > This might answer your questions - http://www.au.sorbs.net/ > > > > On Fri, Aug 27, 2010 at 10:21 AM, <WJhonson@aol.com> wrote: > > My email messages to a rootsweb mailing list are bouncing because of a > > sorbs blacklist. Their site states that I'm going to have to pay a FINE > to > > get > > this cleared up. What's up with that? > > > > Will Johnson > > > > Like I said, their site states that I'm going to have to pay a fine. I already said that. The point is, why is rootsweb doing this, not why is Sorbs doing this. They are doing it to make money off suckers. Why is rootsweb doing it.