Article View: misc.consumers
Article #9069Re: How Does This Happen?
From: max
Date: Fri, 08 Aug 2008 00:50
Date: Fri, 08 Aug 2008 00:50
54 lines
3734 bytes
3734 bytes
In article <B%Lmk.150383$102.120236@bgtnsc05-news.ops.worldnet.att.net>, "SpammersDie" <xx@xx.xx> wrote: > <spamtrap1888@gmail.com> wrote in message > news:dc64fddb-49b4-4796-914a-045b75378e1a@z6g2000pre.googlegroups.com... > > On Aug 7, 12:43 pm, "SpammersDie" <x...@xx.xx> wrote: > >> <spamtrap1...@gmail.com> wrote in message > >> > >> news:c1f774e3-94de-4c23-9924-32b208533d23@j1g2000prb.googlegroups.com... > >> > >> > On Aug 5, 8:00 am, Scott in SoCal <scottenazt...@yahoo.com> wrote: > >> > >> >> I find that hard to believe the way you keep playing the victim card > >> >> on behalf of these incompetent money managers. > >> > >> > There is a fine banking tradition of refusing to honor withdrawals > >> > after a sufficient lapse of time -- "stale-dated" checks. All my > >> > dividend checks have a date on them beyond which they will no longer > >> > be honored. After that, the payee must go groveling back to the maker > >> > to get a replacement check. If a giant corporation is not required to > >> > keep sufficient funds in its checking account for eternity, neither > >> > should Joe Consumer be. > >> > >> > Banks should have treated these withdrawals as if they were stale- > >> > dated checks. > >> > >> Where did it say in the article that the banks honored aged EFTs? > >> > >> It sounds more like the vendor spit out the merchandise and waited months > >> to > >> initiate the EFT. > > > > The vendor does not initiate the EFT, the customer does when he sticks > > his debit card in the vendor's machine. > > [Sigh.] > > The vendor is the one that contacts the bank. Until the vendor does that, > the banks have no way of knowing a transaction has occurred. > > So why are you claiming it's the banks' job to reject the EFT when there's > no evidence in the article that the banks could have known the ETF was for a > transaction that occurred month's earlier, good point. It is computationally infeasable to embed a BEGIN timestamp in the transaction headers. This is largely due to the quantum uncertainty of time arising from relativistic effects at different latitudes. We certainly know that PIN-enabled transaction points don't provide this information in the user reciept. -- This signature can be appended to your outgoing mesages. Many people include in their signatures contact information, and perhaps a joke or quotation.
Technical Details
Message-ID:
<betatron-CCF456.19502607082008@news.ftupet.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news2.google.com!news.glorb.com!gail.ripco.com!not-for-mailReferences:
<ko35949b1nba66qgk3hjg024brcr26vdgu@4ax.com> <g74vjr$3hl$2@jik3.kamens.brookline.ma.us> <gcqc94lo4l0n39p5alvlukv3rem2cbs223@4ax.com> <g77c1l$qll$1@jik3.kamens.brookline.ma.us> <3kpg94tbalh9lmoe6avfa1i9jcc0mau8j4@4ax.com> <c1f774e3-94de-4c23-9924-32b208533d23@j1g2000prb.googlegroups.com> <tfImk.150188$102.3147@bgtnsc05-news.ops.worldnet.att.net> <dc64fddb-49b4-4796-914a-045b75378e1a@z6g2000pre.googlegroups.com> <B%Lmk.150383$102.120236@bgtnsc05-news.ops.worldnet.att.net>Show Full Headers
Complete Article Headers
X-Google-Thread: 107518,d777ae74711f9ca1 X-Google-Thread: 10e835,d777ae74711f9ca1 X-Google-Attributes: gid107518,gid10e835,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news2.google.com!news.glorb.com!gail.ripco.com!not-for-mail From: max <betatron@earthlink.net> Newsgroups: misc.consumers,chi.general Subject: Re: How Does This Happen? Date: Thu, 07 Aug 2008 19:50:26 -0500 Organization: lord of the rings Lines: 54 Message-ID: <betatron-CCF456.19502607082008@news.ftupet.com> References: <ko35949b1nba66qgk3hjg024brcr26vdgu@4ax.com> <g74vjr$3hl$2@jik3.kamens.brookline.ma.us> <gcqc94lo4l0n39p5alvlukv3rem2cbs223@4ax.com> <g77c1l$qll$1@jik3.kamens.brookline.ma.us> <3kpg94tbalh9lmoe6avfa1i9jcc0mau8j4@4ax.com> <c1f774e3-94de-4c23-9924-32b208533d23@j1g2000prb.googlegroups.com> <tfImk.150188$102.3147@bgtnsc05-news.ops.worldnet.att.net> <dc64fddb-49b4-4796-914a-045b75378e1a@z6g2000pre.googlegroups.com> <B%Lmk.150383$102.120236@bgtnsc05-news.ops.worldnet.att.net> NNTP-Posting-Host: ftupet.com X-Trace: e250.ripco.com 1218157202 21375 209.100.225.158 (8 Aug 2008 01:00:02 GMT) X-Complaints-To: usenet@ripco.com NNTP-Posting-Date: Fri, 8 Aug 2008 01:00:02 +0000 (UTC) User-Agent: MT-NewsWatcher/3.5.3b2 (Intel Mac OS X)