[Coco] Bounce

[Gene Heskett]

On Saturday 03 May 2014 23:13:06 Steve Ostrom did opine:

> I just got an e-mail from the list that I was temporarily de-listed due
> to list messages that were directed to me and were being bounced.  I
> replied back to that e-mail, and have been hopefully re-listed again. 
> I remember something like this happening many years ago, but I don't
> remember the cause.  I have been getting at least 20 or so messages
> from the list everyday for years until I got that message today.  Then
> no list messages followed that "bounce" message.
> 
> Did this message make it through?

Got it just fine Steve.

> Any ideas as to what might have just
> happened that had not been a problem for many years?  It's difficult to
> fix something without knowing the cause.  I have been using Windows
> Live Mail (Windows 7) for years now without issue.  I think that MS
> just did a patch for IE, but I can't imagine that that could have
> caused this problem.  Ideas or solutions?
> 
> Thanks!
> 
> Coco-Steve

Web based email seems to be undergoing some sort of an asthmatic choking 
fit in their attempts to control spam, which is easily 98% of the mainline 
traffic now.

I don't use it except an occasional login to do some house cleaning, 
perhaps annually or less.

I "pop3" all my mail, so the whole corpus of my email that gets past my 
spam filters actually exists on this machine, goes back about 13 years now, 
and occupies a ball park figure of 20 gigabytes.  With commodity drives at 
1 terrabyte, thats N.B.D.

I use mailfilter ahead of fetchmail, mailfilter can kill bad UCE right on 
the server, so it never even downloads.  Then fetchmail pulls the rest and 
hands it off to procmail which is in charge of having clamav and 
spamassassin look it over, and what passes that gauntlet gets stuffed into 
/var/spool/mail.  If it doesn't pass, it gets sent to /dev/null.  All 
scripted, no action on my part.

I have a bash script running as a daemon that sends inotifywait to watch 
that directory, and when a mailfile is closed, it then sends a message over 
dbus to kmail, instructing kmail to go get that mail and sort it into the 
proper mailbox in kmail.

Somewhat complex, but its been working flawlessly here for several years.

The net result is that to read the next unread mail, I tap the numpads plus 
key.  If that email is something I can comment on, I click on the correct 
format of a reply, mailing list, personal, everybody, whatever, type my 
answer as I am doing right now, and when done I click send.  Hit the + key 
again to repeat that loop.

None of this firing up a browser and logging into your email account and 
trying to see the message under all those popups that pay for this often 
broken webmail service.

Whats not to like about that, truly the minimum amount of work for me.  
Repetitive stuff, like checking the server for new mail every 3 minutes, is 
best left to the computer, as it can and does do it 24/7 while I'm catching 
40 winks.

If you are running linux, I can help you set it up. No windoze allowed on 
the property here.

Cheers, Gene
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS