Hallo David,
On Thu, 17 Oct 2002 01:26:02 +0200GMT (17-10-02, 1:25 +0200GMT, where
I live), you wrote:
DC> Here's the situation: I have a group of 4 people (a small company) who
DC> share a common address with the same username. I can't create aliases
DC> on the server, and the solution of forwarding all the mails from the
DC> main account to their personal ones isn't a possibility. TB! is
DC> configured to leave the messages on the server for 2 weeks so they all
DC> get the same e-mails, regardless of what each person does in its own
DC> inbox.
A few questions.
Is everyone of them using TB? And if so, do all copies of TB show the
same behaviour? In the latter case you could try to ask the ISP about
changes in the server.
Does TB every time download all messages, or did it only once and
afterwards only when you killed the dupes. That might point to a
change on the server side.
A solution for the current situation would be to let the four of them
download their mail with the last of them to delete it immediately on
the server. Unless their flow is real high, this action shouldn't
cause more than one or two messages not to be distributed to the four
of them (but only to the last).
Since you've been working this way for months, the idea behind it is
sound. However with a real high flow the storage on the server or the
buffer that TB uses might overrun and cause something like this.
Possible solutions:
1) Kill messages after a week
2) If your four are on a LAN and use TB, you could configure one copy
of TB as server to collect and send the mail. Look at the TB help
file for: "The Bat! Networking Course" to get more info on this
subject. Now TB can delete mail on the server.
3) Install a real server on your LAN, this enables everyone to mail
among themselves and with my server (I'm using Mailtraq) it's easy
to distribute the mail to all four of them. Or if you'd like to
spread the workload, to send every message only to one of them.
And I expect the same functionality in other servers like Mercury
or MDaemon.
In my message I presumed four copies of TB, I'm not sure whether
that's correct, but you didn't give lots of info. ;-)
To do more possible error hunting:
1) Four copies of the same version of TB?
2) Do all copies experience the same problem?
3) Do other mua's have the same problem?
4) How often did the problem occur (without killing dupes, that only
repeats the whole problem): once, once a month, once a half year,
once per 65536 messages.
5) Was their a setup/version change before TB started to behave
erroneously? (This includes other software, OS, hardware, ISP,
internet connection)
6) Did something else change with the computers or the people that use
them? (One of them taking the kids to office could prove
disastrous. <g>)
--
Groetjes, Roelof
________________________________________________
Current version is 1.61 | "Using TBUDL" information:
http://www.silverstones.com/thebat/TBUDLInfo.html
