If you are working in a Novell environment and the pmxf.ini file hasn't been automatically created, try creating it manually (see Thomas' post of 2008-06-17 for details).

/Rolf

Hello,

we use Pegasus 4.41 in NDS-Modus (Novell 6.5) with Mercury/32 4.01b. This konfiguration run well.

The mails automaticly delivered locally, so that the user not retrieve the mails.

The problem:

We want also read our mails at home.  So we configured a mail forwarding to an external e-mail adress.

 * localy > Fanker@domain

* EXTERNAL > Fanker@mail.domain.de

*external domain > Domain.de

But now,  we get the forwarding mails  three times

1. The mail will send to Fanker@mail.domain.de and forwarding to Fanker@domain.de

2. The mail will delivered to Fanker@domain

3. The mail of Fanker@domain.de will picked and served  

that it's, why we get the mail three times :-)

What can we do?

Fanker

Not sure what you are doing.  Are you using file based forwarding that you setup in Configuration | Manage local users?  If you are I am confused as to why you get multiple forwards.  How are yuo actually receiving your mail?  MercuryD?  MercuryS? I think it woulf help if you provided real information.

The function 'Manage local users' is not active.
Because Pegasus/Mercury is running in a NDS-Modus under Novell 6.5.(I suspect)

The following Mercury-modules are in use:

[Protocols]
# MERCURYS.DLL
MERCURYP.DLL
# MERCURYE.DLL
MERCURYC.DLL
MERCURYD.DLL
# MERCURYH.DLL
# MERCURYF.DLL
# MERCURYW.DLL
# MERCURYX.DLL
# MERCURYI.DLL
# MERCURYB.DLL

We actually receiving our mails with MercuryD.

I would try to explain my problem:
My local E-Mail Adress is Fanker.dohler and my external E-Mail Adress is Fred.Anker@dohle.de

If I get an e-mail from colleagues (in our LAN)  these mail will directly go in my User PMAIL-directory.(I suspect)  
If I get an e-mail from external - the mail is first sending to our provider 1und1.de into our e-mail account.
Mercury gets the mail there and send/copy the mail in the user PMAIL-directory. We dont delete the mail in our external
account, so we can read our mails at home too. But only the external mail.

Because the function - Manage local users - is deactivated, we use the function of Pmail forwarding
to an external mail-adress. But we can't use the mail-adress fred.Anker@dohle.de because mercury 'knows'
that the user fred.Anker @dohle a local user is.

[Domains]
/[root]: guelden.de
/[root]: transg.de
/[root]: dohle.de


so I thought me, create a new mail-account like fred.anker@mail.dohle.de only as forwarding adress
to fred.anker@dohle.de.

If the colleagues send a mail to the new adress, i can read the mail at home: but this will require advance that
the user only send 'internal' mails to the new account. However, many are forgetful and so some mails I can
read at home and others not.

So i create a filtering rule like > if the header = Fanker.dohle Then forwarding to Fred.Anker@mail.dohle.de

now,  we get the forwarding mails  three times

How can I get this kind of forwarding realize with only one local mail?

is this/my approach wrong?

Thanks 

Fanker 

The function 'Manage local users' is not active.

But the file based forwarding is still available  by putting a FORWARD file inn the home mail directory of the user. But this only affects mail delivered via Mercury/32. 

You be able to do both local and internet forwarding via the extended features though since it allows forwarding of both local and internet mail. This is from the readme.nds I got for older versions but these same functions should be available in v6.5

9: Extended Features

Pegasus Mail has a number of specialised features that are not normally
enabled for every user. In NetWare 3.x mode, these features were stored
in the NetWare Bindery, where they were readable by all users. Under
NetWare 4.1, the only equivalent way of doing this involves modifying the
base NDS schema to add a new object type: unfortunately, at the time of
writing, modifying the base schema has far-reaching consequences (most
specifically that it is impossible to merge two NDS trees where either
has a modified schema) and hence we have had to rule out this approach.

Instead, WinPMail and Mercury look for a file called PMXF.INI in each
user's new mail directory. This file must be world-readable to be
effective. PMUSER and MAKEMBOX will automatically create a zero-length
version of this file when creating a new mail directory for a user, and
will grant [RF] rights to all users, as well as making an explicit grant
of [RF] to the user himself; this latter grant prevents the user from
modifying the file, thus keeping compatibility with Pegasus Mail under
NetWare 3.x (where by default users are not permitted to modify their
extended feature sets).

To allow a user to modify his/her extended features, grant all rights
to PMXF.INI. Note that if you manually edit a PMXF.INI file, you will
probably alter the rights grants to the file. Make sure you grant [RF]
to [Root] (all logged-in users) each time you modify the file manually. 

PMXF.INI is a simple text file that contains statements, one per line.
The following statements are recognized:

   "Local autoforward = <address>"
      - Sets a forwarding address for mail delivered by Pegasus Mail
        itself. "<address>" can be any valid address to which you could
        normally send mail using Pegasus Mail.

   "Internet autoforward = <internet_address>"
      - Sets a forwarding address for mail delivered by Mercury. The
        address can only be a local NDS address or an Internet address.

   "Deliver even when forwarding = <Y or N>"
      - Determines whether or not a copy of mail that is automatically
        forwarded by Mercury or Pegasus Mail should be left in the
        recipient's new mailfolder as well.

   "Allow confirmation of reading = <Y or N>"
      - If 'N', then Pegasus Mail will not honour requests for confirm-
        ation that a message has been read.

   "Disable mail delivery = <Y or N>"
      - If 'Y', then no mail can be delivered to this account.

   "Send delivery broadcasts = <Y or N>"
      - If 'Y', then NetWare broadcast messages will be sent to the
        recipient when new mail arrives.

Lines beginning with '#', ';' or '*' in PMXF.INI are regarded as comments
and are ignored.
 

I do create the following ini-File:

PMXF.INI
Local autoforward =
Internet autoforward = Fred.Anker@dohle.de
Deliver even when forwarding = N

A colleague (of our LAN) send a test-mail to my local adress Fanker.Doehle.

>> and then Mercury/32 do this:

E 20080618 1038 [Unknown] Fanker.dohle                  Message loop detected - message discarded.
I 20080618 1038 MG00006D th.brin@dohle.de             Fanker.dohle                  7411

This mail is not in my mailbox.

an other test:

PMXF.INI

Local autoforward =

Internet autoforward = Fred.Anker@mail.dohle.de  (a forwarding account)

Deliver even when forwarding = N

I 20080618 1152 MG0000A3 J.Korner@dohle.de        fanker.dohle                  4528
O 20080618 1152 MG0000A5 J.Korner@dohle.de      Fred.Anker@mail.dohle.de 4752
I 20080618 1153 MG0000A9 J.Korner@dohle.de        fanker.dohle                  5617
O 20080618 1153 MG0000AB J.Korner@dohle.de      Fred.Anker@mail.dohle.de 5841

This mail is not in my mailbox too.

I don't understand this loop's   :-(

Thanks
Fanker

This looks like you are trying to forward off server using one of the local domains.  Try forwarding to a totally different account like a GMail or Yahoo account and see what happens. 

It also appears that you are not using a header in the message with the RCPT TO: address to deliver the mail in MercuryD.  If you do not have this capability and this is a domain account yuo are going to have real problems with messages containing multiple addresses.

If I forwarding to a total different account I get the mail correctly.

And the mail to the 'external' account Fred.Anker@mail.dohle.de is ' going in correctly ' and forwarding correctly to F.Anker@dohle.de:

O 20080618 1152 MG0000A5 J.Korner@dohle.de      Fred.Anker@mail.dohle.de 4752

In the next step Mercury/32 see a mail in the Fred.Anker@dohle.de account and pop this mail to the local adress Fanker.dohle. And there is, in turn, an forwarding-rule to Fred.Anker@mail.dohle.de and this mail will forwarding to the internet-adress and so on ....

I 20080618 1153 MG0000A9 J.Korner@dohle.de        fanker.dohle                  5617
O 20080618 1153 MG0000AB J.Korner@dohle.de      Fred.Anker@mail.dohle.de 5841

Mercury does not seem to know that the mails has already been served.

- and this/that is the problem we have :-)

 We want our local mails automatically in our Domain-account can read.

>> It also appears that you are not using a header in the message with the RCPT TO: address to deliver the mail in MercuryD

How can I check this?

Thank you very much

Fanker

Mercury does not seem to know that the mails has already been served.

MercuryD downloads all mail in the account all the time.  If the server says it's available it will be downloaded.

>> It also appears that you are not using a header in the

message with the RCPT TO: address to deliver the mail in MercuryD

How can I check this?

In the MercuryD setup.  You can set a header to be used assuming that your ISP adds one.

We ar not using a special header in the message. There are no entries in MercuryD.

What exactly must I set in the MercuryD to solve my problem?

You can't tell with this message if the ISP is adding a header or not, this one was delivered locally.  You need to send this message from outside, say from a GMail account, and then check the headers.  You are looking for something like X-Originally-To:, X-Delivered-To: or X-RCPT-To:, a header added to the message by the ISP when it was delivered to the POP3 mailbox that contains the original RCPT TO: address.

I don't understand or it dosn't work:

If I send a mail from Hotmail.com to my adress F.Anker@dohle.de the mail is correctly in my mailbox and a header looks like this:

Received: from spooler by dohle.de (Mercury/32 v4.01b); 23 Jun 2008 08:47:49 +0200
X-Envelope-To: fanker.dohle
Return-Path: <phil@hotmail.de>
   phil@hotmail.de

If I send a mail to the Forwarding-account F.Anker@dohle.de the ISP will adding the header X-Envelope to: to the message too:

Received: from spooler by dohle.de (Mercury/32 v4.01b); 23 Jun 2008 12:51:13 +0200
X-Envelope-To: fanker.dohle
Return-Path: <a.walter@dohle.de>

If I send a mail to fanker.dohle with Forwarding rule to f.anker@mail.dohle.de:

Received: from spooler by dohle.de (Mercury/32 v4.01b); 23 Jun 2008 13:02:01 +0200
X-Envelope-To: fanker.dohle
Return-Path: <a.walter@dohle.de>
Received: from pop.puretec.de ([212.337.15.165])
   by KEN (4.00.93-v070725) with POP3
   ; Mon, 23 Jun 2008 13:05:43 +0200
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.337.126.186])
   by mx.kundenserver.de (node=mxeu9) with ESMTP (Nemesis)
   id 0MKt64-1KAjib3pII-0000qg for f.anker@mail.dohle.de; Mon, 23 Jun 2008 12:56:17 +0200
Received: from isdn (p5B1059EA.dip.t-dialin.net [91.16.89.234])
   by mrelayeu.kundenserver.de (node=mrelayeu3) with ESMTP (Nemesis)
   id 0MKxQS-1KAjia356x-0000x2; Mon, 23 Jun 2008 12:56:17 +0200
Received: from [184.134.100.101]
   by KEN (4.00.93-v070725) with SMTP
   ; Mon, 23 Jun 2008 13:03:10 +0200
Received: from Spooler by  (Mercury/32 v4.01b) ID MO00010C;
   23 Jun 2008 12:59:11 +0200
Received: from spooler by dohle.de (Mercury/32 v4.01b); 23 Jun 2008 12:58:20 +0200
Date: Mon, 23 Jun 2008 09:56:24 +0200
From: "A Walter" <a.walter@dohle.de>
Subject: Test

there're a lot adding to the header :-)

In the MercuryD POP3-Client I enter X-Envelope to in the checking header.

But now I have a loop (again).

I think i don't understand how mercury works.

I try to send local mails automaticly both to external mail-accounts and to the local adress.    

Thank you for your patience

Fanker 

Mercury adds an 'X-Envelope-To:' header (if unfiltered), but late in the delivery process, so it can't be used by MercuryD or in normal filters.

It seems your ISP isn't adding a delivery header.

Ok,  I probably understand this now.

I looked in my mails the entry X-RCPT or X-Deliver. Ther are no entries.

But can i use the entry ' Received: from [184.134.100.101] '  for my problem ?  because this entry (IP-Adress of the Mercury Server) is  only in  the 

header  when  the mail is send by a local user.

Thanks 

Fanker 

But can i use the entry ' Received: from [184.134.100.101] '  for my problem ?

No you cannot use this header since it does not identify the sender.  You might be able to use filters with this header at the client level though I do not see how this could be done all that easily. 

Sorry for delays in answering, I'm on vacation and do not have all that many internet connections.  Banff as bit more civilized. ;-)

I ask our ISP and they do not want (can not) to add anything in the Mail-Headers.

Ok, if I generate a filtering-rule like this:

If expression headers matches "X-Delivered-to: Dohle.lokal" Call "MovMail"
If header "T" contains "Fanker.Dohle" AddHeader "X-Delivered-to: Dohle.lokal"
If header "T" contains "Fanker.dohle" Forward "Fred.Anker@mail.dohle.de"

Label "MovMail"
If expression headers matches "X-Delivered-to: Dohle.lokal" Delete ""

So there's a clear entry. Is it possible to do this or missing something here ? 

Many thanks for your spending time and

have a good time on your vacation 

Fanker 

If I cannot find the file pmxf.ini on the netware mail directory is there any other way to set up local and internet forwarding?