Re: [cobalt-users] Qube2 problems

["Jona Tallieu (T & T n.v.)" <Junk@xxxxxx>]

At 21:21 +1100 on 29-01-2001, Malcolm McLeary wrote:


>> Problem 1:
>> The Qube has about 40 email accounts configured for
>> 1 domain. We want that mail which does not have
>> a final destination, is not bounced, but is send to
>> the general emailbox "info@xxxxxxxxxx". So incoming
>> email which is normally bounced with "user unknown"
>> is accepted and redirected to the info-mailbox.
>> How can this be done on the Qube2??
>
> You need to edit /etc/aliases to add a "catch all" at the end.  Make sure
> you run newaliases after you edit this file.
>
> The downside is that the Cobalt GUI scripts will add new entries to the end
> of /etc/aliases so you will have to move the "catch all" whenever the GUI
> updates the list.

So every time I add or delete or adjust a mailbox using the webinterface,
I have to do this?

>> Problem 2:
>> The general mail address info@xxxxxxxxxx has
>> to be forwarded to 4 offices. So all mail
>> for info@xxxxxxxxxx must be redirected to user1, user2, user3
>> and user4. The only solution I found for this was
>> creating a mailinglist.
>> But this has as result that user1, user2, user3 and user4
>> get a mail from "owner-info@xxxxxxxxxxxxxxx" instead
>> of the original sender. I found a solution for this
>> on the FAQ, I let a Linux-expert apply the fix, and it
>> worked for a couple of days, but then the wrong-reply adress
>> bug came back.
>
> The problem is that you probably edited the config file for mailing list.
> The config file is created by a script ... if the script is reactivated by
> the GUI (e.g. change list members) you will lose your manual changes.
>
> To change the list preference for all future mailing lists, change the
> following'
>
> /usr/local/majordomo/config_parse.pl
>
> From:
>         'reply_to',             '#! local($TEMP) = $list;
>                                     if ( $list =~ /-digest$/) {
>                                        $TEMP =~ s/-digest$//;
>                                        $TEMP;
>                                     } else {
>                                        "";
>                                        }',
>
> To:
>         'reply_to',             '$SENDER',
> #       'reply_to',             '#! local($TEMP) = $list;
> #                                   if ( $list =~ /-digest$/) {
> #                                      $TEMP =~ s/-digest$//;
> #                                      $TEMP;
> #                                   } else {
> #                                      "";
> #                                      }',
>
>> Another problem is that large messages (over 40000 characters)
>> get bounced uwhen using the mailinglist!!!
>
> In /usr/local/majordomo/config_parse.pl you will also find a section which
> talks about message size being 40000 characters ... increase it.
>
>> I just really do not like that you can not just put more
>> than 1 emailaddresses in the "forward to" box in the admin!!!
>
> Yeh, that is a bit of a pain, but you can always manually edit /etc/aliases.

But this means that I still will be uinsg the listserver to do this.
The listserver adds lots of headers that confuse a lot of my newbie
users. I would like to accomplish this without the use of majordomo...
Oliver suggested the following:
------------>
>Try to edit /etc/virtusertable or /etc/mail/virtusertable (don't know
>exactly where the file is at your drive) look for the line
>info@xxxxxxxxxxxxxx      user1
>change it to
>info@xxxxxxxxxxxxxx      user1,user2,user3,user4
>
>After you've applied this you had to make an "makemap
>hash /etc/virtusertable.db < /etc/virtusertable" or "makemap
>hash /etc/mail/virtusertable.db < /etc/mail/virtusertable". This is dependent
>on the path to you virtusertable file.
<------------

Any comments on that solution? I will have to let a Linux
expert do this, because this goes well beyond my knowledge
of Linux...

Thanks for your reply!


J.