On Saturday 30 April 2016 13:10:56 Gene Heskett wrote: > On Saturday 30 April 2016 02:39:38 Lisi Reisz wrote: > > On Saturday 30 April 2016 00:53:47 Gene Heskett wrote: > > > With > > > gmail, the only practical way to do that is to subscribe using two > > > different names, and always send to only one, but you will then get > > > the list echo back on the 2nd account. Its a PITA with gmail, but > > > its the only way I know of to get around their duplicate deletion. > > > > Nonsense. That is a most impractical way of dealing with it. I deal > > with it by sending via my ISP's smtp server. > > I do too. But the list echo never comes back TO THAT ADDRESS@SERVER. So > you must maintain the sub to the other address or on a 2nd server. Most > just turn off delivery back to the server they post thru. Mailfilters > duplicate nuking doesn't prevent the duplicates in the two server or 2 > addresses situation, each with the same message coming back in, which > may, or more likely is not the case during that invocation. I've has as > much as a 16 hour difference in incoming duplicates doing that. The > best solution was to stop using gmail. And its like an Excedrin > headache in that you've just removed the need for the headache powders. > > So I miss it like I'd miss a broken leg, or a poke in the eye with a > sharp stick. :) > > > No hassle and works > > fine. Others may have other simple ways of dealing with it. > > For you maybe, but gmail has always been a broken solution in search of a > problem to me. So it was just a shrug when they started denying my > fetchmail access to port 995 a year ago. Problem solved by 6 # > characters in the .fetchmailrc file.
Your life always seems so unnecessarily complicated, Gene. :-/ Why HAVE two addresses???? Lisi
