Re: [cobalt-users] Qube2 Mailing Lists

[Malcolm McLeary <mim@xxxxxxxxxx>]

Jeff,

Thanks for taking the time to reply.

>> How do I get Mailing Lists on a Qube 2 to distribute messages in a timely
>> manner instead of once an hour?
> 
> They should distribute immediately.  If you could give me a little
> more information on how you are setup ( all internal recipients?
> some external recipients?  Dialup or permanent Internet connection?)
> I can see if I can get to the root of the problem.

The "list" is actually a group (of 30 people) so all the mailboxes are
local, although some users have redirected their mail as they work on-site
with a client.

The Qube has a permanent dialup connection to the internet.

In my tests I've sent a message to the group from a machine on the LAN and
then monitored my mailbox ... it regularly takes up to an hour for the
message to appear even though the Qube2 is running with a light load.

>> The Gateway Micro Server distributes immediately so it can't be a big
>> change.
> 
> Same setup as the Qube2 is on the Gateway MS.

It may well be, but in my tests the Gateway Micro Server distributes
immediately, the Qube2 waits ...

Some test messages from last week ...

    Sent:   Thursday, 2 March 2000 2:31 PM
    Rec:    Thursday, 2 March 2000 3:00 PM

    Sent:   Thursday, 2 March 2000 4:07 PM
    Rec:    Thursday, 2 March 2000 4:54 PM

    Sent:   Thursday, 2 March 2000 4:51 PM
    Rec:    Thursday, 2 March 2000 5:32 PM

    Sent:   Friday, 3 March 2000  9:57 AM
    Rec:    Friday, 3 March 2000 10:45 AM

I have just realised that my trials were not based on the same
configuration.  On the Qube2 the group contains 30 users ... on the Micro
Server (as I was just having a look at it) the group consisted on 1 user.

Retesting the Qube2 with a group containing only 1 user distributes the
message immediately ...

Should the number of group members have such a dramatic effect?

Don't you just hate it when a problem is not reproducable ... I ran another
test with the problem group and it is now working as "expected".

    Sent:   Thursday, 9 March 2000 11:03 AM
    Rec:    Thursday, 9 March 2000 11:04 AM

>> Also, how can the "reply-to" header be removed or changed so that replies go
>> to the originator, not the list?
> 
> Each list keeps it configuration under /usr/local/majordomo/lists/.  So
> if you look in /usr/local/majordomo/lists/<listname>.config and look for
> the reply_to variable (around line 282) you can set this to '$SENDER'
> and that will modify the list to change the reply-to header to the
> name of the sender.

Sounds great!  

Does anything need to be stopped and started before the change takes effect?

I guess its a big ask, but what would need to be changed so that all new
groups (lists) behave with "reply-to" = sender?

Cheers,  Malcolm

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

                     TDA Systems Engineering Pty Ltd
                             ACN 079 090 850
                           Canberra, Australia
                        http://www.tdasys.com.au/

Malcolm McLeary                                  Phone: +61 2 6251-5270
Information Technology Manager                   Fax:   +61 2 6251-5205
FileMaker Solutions Alliance Member              Mobile:   0412 636 086

     This message was sent using Outlook Express 5.0 for Macintosh.