[ngw] multiple identical postings to shared folders
Mathias.Faust at gruner.ch
Thu Nov 13 13:14:39 UTC 2014
Hi Georg, Ken and all others,
We (also an engineering company) face similar problems. We share project folders from a resource and everyone "dumps" their project related mails to these shared folders (sometimes even unread if they are in CC).
We once played around with gwava retain and saw that it archives only one mail of several identical mails are there. After some digging we saw that actually the message ID of a mail remains the same for all TO/CC (not sure about BCC) recipients.
Maybe the tool of ken could be extended to compare the message ID and delete all duplicates... Or we could try to convince Novell to provide such an option...
> On 12.11.2014, at 16:04, Georg Fritsch FCP <gf at fcp.at> wrote:
> Hi Ken,
> We face exactly the same situation. Project based engineering firm - you know how this works... :-)
> Well, we habe written our own little tool for this task. With the SOAP api it is possible to do this (and much more) directly on the server.
> Our tool collects metadata from all mails in a folder/folderstructure/user/po and allows queries on this data.
> * Compile a list of all mails in a folder of similar size and/or date and the same subject
> * Optionally archive them in a seperate IMAP-Server (could also be a different GW po)
> * Delete all but one
> Currently this is not fully automated und as many internal tools not really documented.
> Error handling could be improved as well. ;-)
> If your (or others on the list) are interested, i might manage to make this freely available for the commandline orientated and fearless admin.
>>>> "Ken Etter" <kle at msktd.com> schrieb am 12.11.2014 um 14:39 in Nachricht
> <54631CC802000013000FCD35 at mail.msktd.com>:
>> Ok, bad choice of words. :-) I just meant I should be able to remove
>>>>> "Elbert LaGrew" <Elbert.LaGrew at katun.com> 11/12/2014 8:31 AM >>>
>> "GroupWise should be intelligent enough to handle that"
>> Seriously? GroupWise is doing exactly as it is supposed to be doing. Asking
>> that it be more intelligent than the people using it is, IMHO asking a lot.
>> That said...I agree there should be a way of removing duplicates...but
>> asking it to possess "intelligence" is going a bit far. :-)
>>>>> On 11/12/2014 at 7:08 AM, in message
>> <5463156002000013000FCD30 at mail.msktd.com>, "Ken Etter" <kle at msktd.com> wrote:
>> Every email that needs to go into the shared folder isn't guaranteed to go
>> to the owner of the folder. We are an Architectural/Engineering firm and are
>> project based. We create a shared folder for each project. Everyone
>> assigned to the project gets access to the folder. Sometimes emails are sent
>> to the whole team and sometimes they are sent to specific members of the
>> team. So everyone needs add access. I just want to ease the congestion when
>> an email goes to more than one member of the team and all those members add
>> the email to the folder. GroupWise should be intelligent enough to handle
>>>>> "Joe Acquisto-j4" <joea at j4computers.com> 11/12/2014 5:59 AM >>>
>> Why do all of them need "add" rights? Seem limiting that to the "owner" is
>> the simplest solution.
>>>>> On 11/11/2014 at 4:28 PM, "Ken Etter" <kle at msktd.com> wrote:
>>> But they weren't different. I send an email to 4 people. All 4 people read
>>> the email and then file it in a shared folder that is owned by one of them
>>> and shared with the other three. Now there are 4 copies of the same email
>>> that shared folder.
>> ngw mailing list
>> ngw at ngwlist.com
Diese E-Mail enthaelt u.U. vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte den Absender und vernichten Sie diese E-Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail sind untersagt.
Diese E-Mail wurde durch unseren MAILsweeper geprueft. Weder die Gruner Gruppe noch der Sender koennen zur Verantwortung gezogen werden fuer defekte Daten infolge von Viren oder Uebermittlungsfehlern.
More information about the ngw