Hello Dorothy Johnston,
your mailbox is blocking my mails permanently.
"A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
dhjohnston7@comcast.net"
If you are interested in exchanging data or in receiving corrections to your
data, keep your box opened.
Otherwise I will cease my cooperation.
It is disgusting in getting mails back.
Klaus
I don't understand what I did wrong. I'm very sorry I caused you trouble. I do not need to learn any more about Feldhusen.....I joined this list primarily to give details about what happened to them after they left Germany. Just take me off the list and I will move on to other work. Thank you.
Dorothy
Hi Dorothy,
I don't think you need to leave the list. I don't think everybody had
trouble with your posting. Perhaps, if you sent a message to Klaus's own
mailbox, there was a problem. You've been sending them to the list and I
don't see there is anything wrong there.
Computers can do weird things at times. I had received a hilarious joke
the other day and I tried over and over to forward it to other people and it
just sat in my outbox forever.
Barbara
Hi Dorothy:
I concur with Barbara. There are two primary reasons mail is returned. One is that the address is nonexistant and the second is that it was incorrectly written. For an instance if you add an " to the end of an e-mail address, it will not go through.
I have had no problem with your e-mails.
There have been a lot of spammers using return mail routes to get their junk to you. Why am I going on like this???--If anyone has a serious problem with this list he/she should contact the administrator and leave the list to genealogy.
Gale
Dear Dorothy & Klaus,
Perhaps your mail filter is set to exclusive and this is why mail is being rejected? Perhaps add Klaus to your address book would work.
Or..
If the " was mistakenly carried over into the email addy.. I think this would prevent delivery.
Barbie-Lew
I have had no problem with your e-mails.
There have been a lot of spammers using return mail routes
to get their junk to you. Why am I going on like
this???--If anyone has a serious problem with this list
he/she should contact the administrator and leave the list
to genealogy.
Gale
There are two others you are overlooking beyond the two "biggies" already mentioned. One is that the recipient's inbox is full, and since it has exceeded its volume allowance, it rejects anything more in the way of incoming mail heading its way. This can be corrected by simply making adequate space available. The other is due to overly aggressive/restrictive SPAM filters or rules in place, generally at the e-mail client end but occasionally connected to the firewall. These can either be via broad restrictions (rules in place, to include the rejection of attachments) or targeted to specific e mail or URL addresses (often times set accidentally).
You'd be wise to check all for all of these possibilities if this continues.
Jb
HI JB:
Your thoughts are valid, but in this case we are
communicating with Barbara - No full mailbox. (the response for a full mailbox is normally "undeliverable due to full mailbox"), however, there are a lot of programs out there. Also others on the same list are not being screened.
Gale
Well perhaps I'm missing something among the messages that were sent, and I admit I dropped that additional advice without really looking at all the messages (since those are what tend to be causes so many of these kinds of errors), but going back a bit now, is it not the same issue where Klaus cannot get his e mail over to Dorothy? I can't see where Barbara - and the list for that matter - figures prominently in this. Unless I'm missing something obvious, or something has transpired offline I'm out of the loop on (?).
If the issue is indeed the recent e-mail failure between Klaus and Dorothy, one of their ISP's mail servers is most likely having a problem "handshaking" with the other side. One may be flagging the other as either being a source of spam, or a channel through which it is delivered. Some e mail server administrators choose to run open relays or proxies; others will refuse anything coming from open ones since spammers often send their junk through these kinds of channels. This is because open relays act as amplifiers and anonymizers for spammed messages [an open relay is simply a mail server that will accept and deliver mail from point A to point B without question].
Many ISPs have begun implementing stricter filter systems on their servers over the last few years, with far greater restrictions in place than in earlier times. This is an ongoing practice, so things can change at any time with them (they all act independently and strictly with their own security interests in mind). So it often comes down to how any given ISP sets up their security settings and filtering baselines, and that is subject to change at any time.
I'd suggest both parties contact their respective ISPs and point them to the rejected e mails so that those folks can examine the header information. This should determine where and what the hang-up is between the two servers. Legitimate mail getting erroneously blocked is nothing new, especially with all the junk mail floating about nowadays. No ISP firm (or server) is obliged to accept mail from anywhere, but if they do reject it, they should at least give sensible and valid reasons. An American based ISP might choose to block perfectly legitimate e mails sent from say a British or German ISP, or it might be just the opposite! Sometimes automated systems create blacklists that are at the root of this trouble. Other times the problem comes from incorrectly issued - and thus unrecognized - dynamic (residential) IP address ranges which will be rejected out of hand by many servers, since those kinds are not allowed direct access. An ISP might also choose to block specific domains. For any of these reasons, you have to ask the ISP to do something about it, as in unblock the block!
Keep in mind, bounced e mails can also come from certain viruses or worms infecting one's system locally, transmission timeouts or DNS caching issues, a malfunctioning or misconfigured (or simply cheap and unreliable) mail server at the host site, or the use of antiquated (non-updated) spammer blacklists. Any of these can cause permanent SMPT error messages, aka "Fatal Errors" (temporary ones are where the server indicates it will retry a number of times to push through a hung message, with no intervention on your part required). However as soon as you see "Permanent Error" in the rejection return, there's little point in attempting to resend the mail, as it is unlikely to change.
Beyond that, all Internet Providers have ISP-specific space and usage limits. Also the sending mail server may require you to authenticate (confirm your identity) to it. Sometimes you need to check with your e mail provider to see that you are properly set up via your e-mail client. One of the ISPs in question may also simply have misconfigured one of their SMTP->SMS gateways, or intentionally locked them down because of excessive SPAM or DDOS attacks. On and on it goes.
As for the clarity of SMPT return error messages, trust me they are not always as precise or clear as you might think (no more than Windows generates clear error codes at all times). The error message one reads on one end may not be spelled out the same on the other. This is generally determined by how a server is set up to begin with. Only the header information on the rejected messages and tracer pings will render a clearer picture. And that is an ISP support dept's responsibility.
Both parties should contact their Internet Service Provider before assuming the fault lies on the opposite side. Whoever has the actual rejected messages (with the requisite header info), start there.
Hope this helps gang. File for future reference!
Jb
PS. Gale shake me good if I'm overlooking something obvious (wouldn't be the first time I needed it).
es ist sp�t!
SMPT => SMTP [Simple Mail Transfer Protocol]
Hi JB:
I am opting out of this thread. I have already contributed too much to a subject outside of genealogy. For that, I APOLOGIZE to the members of the list. Because I was not alert, I simply lost sight of when to stop, or maybe just not to start.
Gale
Beg to differ Gale. I classify these things as educational, as sooner or later just about everyone experiences such problems. I've yet to be on a list or forum or BBS exchange, going back to the early days of the Net on Gopher and UseNet, where these types of issues did not come up with some degree of regularity. Why you feel this is not genlist related is beyond me, when this forum itself is e-mail based. If anyone read the ensuing messages, they should now know such things can be cause by a wide variety of things (like almost everything else computer related), but at the same time it does not need to remain a mystery or voodoo magic. If they make the requisite checks on their system (as were posted), and then touch bases with their ISP beyond that, they should be able to rectify these kinds of issues, and they're only the wiser for it now. It's the same way I learned such things ages ago --- someone pointed them out!
Since these messages have all been posted under the 'FELDHUSEN in Meyenburg' thread, presumably Klaus and Dorothy are reading them since they initiated it, and will soon be exchanging their familial notes as a consequence of what was suggested (assuming they act on it). So why the need to apologize to the list for trying to lend a hand here? A lot of other folks may have learned something to boot. If anyone is miffed by such offerings, they should simply ignore the thread, or learn to use that button called DELETE.
Jb