LinkBack URL
About LinkBacksSounds like all you need to do is disable Pegasus' local mail delivery
option. Can you configure the Pegasus mail clients to all use the SMTP
delivery option in preference to the LAN mailer? Tools/Internet
Options/Sending(SMTP) tab
This is a discussion on can Mercury be made to always forward. - Pegasus ; Hi, We have a legacy pmail/mercury system running on our netware server Template which is connected to the outside world like so :- Internet-----Protein (linux mail gateway)-----template (mercury). MX for bio.warwick.ac.uk legacy mailserver. We have the primary MX for our ...
can Mercury be made to always forward. Hi,
We have a legacy pmail/mercury system running on our netware server Template
which is connected to the outside world like so :-
Internet-----Protein (linux mail gateway)-----template (mercury).
MX for bio.warwick.ac.uk legacy mailserver.
We have the primary MX for our domain pointing to protein, so that we can do
mail aliasing on this (most of our users have moved on to the campus
groupwise mailserver), which forwards incoming mail addressed to the old
user mailboxes, any incoming mail addressed to @bio that isn't forwarded by
protein (to groupwise), is passed on to template. This works well as users
still on pegasus get their mail, and users who have moved to groupwise also
get theirs.
However, if a user still on pegasus mails a user that has moved to
groupwise, using their pegasus username, then the mail goes to the pegasus
inbox and that user never sees it. Is there a way to disable this so that
the local mail by default is passed on to protein, and can be forwarded from
there to the correct address.
Is this possible ?
Thanks.
Phill.
Re: can Mercury be made to always forward. Sounds like all you need to do is disable Pegasus' local mail delivery
option. Can you configure the Pegasus mail clients to all use the SMTP
delivery option in preference to the LAN mailer? Tools/Internet
Options/Sending(SMTP) tab
Re: can Mercury be made to always forward. On Wed, 5 May 2004 14:22:59 +0000 (UTC), in <comp.mail.pegasus-mail.misc>,
"Phill Harvey-Smith" <phill@dna.warwick.ac.uk> wrote:
>
> Hi,
>
> We have a legacy pmail/mercury system running on our netware server
> Template which is connected to the outside world like so :-
>
[snip]
>
> However, if a user still on pegasus mails a user that has moved to
> groupwise, using their pegasus username, then the mail goes to the pegasus
> inbox and that user never sees it. Is there a way to disable this so that
> the local mail by default is passed on to protein, and can be forwarded
> from there to the correct address.
>
[snip]
I'm not sure I followed all the machinations; but have you considered putting
a .FORWARD file in each remaining user's mail directory on the Merc box?
--
Jay T. Blocksom
--------------------------------
Appropriate Technology, Inc.
usenet01[at]appropriate-tech.net
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-- Benjamin Franklin, Historical Review of Pennsylvania, 1759.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Unsolicited advertising sent to this E-Mail address is expressly prohibited
under USC Title 47, Section 227. Violators are subject to charge of up to
$1,500 per incident or treble actual costs, whichever is greater.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -