thank you very much for all the help & guidance.

regards,

bun

Hello Peter

you can use the MercuryH PH-Server-Module . With this module you can "share" a normal Pegasus-Mail-Adressbook for Users which has a PH-client.

Info from the Mercury-Help-File:

>MercuryH PH Directory Server
>
>MercuryH is a directory services module - it accepts requests for addressbook lookups from other systems and returns lists of possible matches. The protocol used by MercuryH is called the PH >protocol, also sometimes known as the QI/CSO protocol: it is widely-used on the Internet by mail clients such as Pegasus Mail and Qualcomm's Eudora. At the time this help file was written, an >Internet standard was in the late stages of being formalised for the PH protocol - MercuryH implements that standard.
>
>In order to fulfil queries, MercuryH uses a Pegasus Mail addressbook file, mapping the fields in the addressbook file onto the standard fields defined by the PH protocol. Any Pegasus Mail >addressbook can be used by MercuryH, and you can use the import/export tools provided with Pegasus Mail to create and maintain addressbooks for MercuryH.
>

Hope this helps

Hans 

[quote user="mikerocosm"]

Long time user, first time poster . . .

I've just converted my home Mercury server (gathers several POP3 accounts for myself and my wife, distributes them back to us through Pegasus) to deliver mail using IMAP instead of POP3. I've got it all working just fine, locally and from various remote installations, but IMAP clients will not connect to the Mercury server as long as the Pegasus client is running on the server machine (which is also my trusty does-everything home computer). Simplest solution is to just close Pegasus on the server after I've run my traps each morning, I suppose, but I never had to do that when using POP3, and Lord knows, I don't want to have to change my behavior now.

So, is there a way to configure Pegasus locally on the Mercury server so that it doesn't interfere with IMAP access from remote Pegasus clients?

Nope, the lock file is in place to ensure that a user and Mercury/32 are not both accessing the same folders at the same time.  That would be a sure way to lose data and maybe the entire folder.  This is not a problem with POP3 since it is only downloading the mail as separate files from the new mail directory.  Even when these files are downloaded and deleted via POP3 the only thing you have to do in WinPMail to clear it up is to close and reopen the new mail folder.

Inquiring minds want to know . . .

Best regards,

Mike

Open relays are quickly discovered and misused, so it's important to get the relaying settings right in Mercury. Once that is done you have done what you can, tracking down spammers and making them rethink their lives is not a realistic undertaking.

There is a risk your IP address has been blacklisted if you have been relaying a lot of junk, so you may want to check that (for instance here: http://www.mxtoolbox.com/blacklists.aspx)

Haven't been using SSL with Outlook so I can't help there. Maybe someone else knows?

/Rolf 

Hi Thomas

Got some files back but not all? many are ones I deleted some time back.  Pegasus is now working, I must move on, so much time
wasted.

Many thanks for your help and patience.

Happy Christmas to you and yours Thomas

[quote user="boc1580"]

I am able to subscribe and manage email lists through the email without problems.  I am also able to subscribe to mailing lists via the web interface and receive a confirmation.  However, when I try to unsubscribe the confirmation request message does not get sent.  Looking at the Core module logs and the error email generated to the postmaster, it appears the message has no from email address.  I looked into the template files and it appears the templates are only the message body.  Any idea where I can locate the setting to correct this error?

 This mail comes from postmaster and uses the domain that shows in Configuration | Mercury core "Internet name for this system". 

 Here's the raw view of the message I receive when I unsubscribe.

Received: from spooler by tstephenson.com (Mercury/32 v4.62); 18 Dec 2008 09:44:16 -0800
X-Envelope-To: test@tstephenson.com
From: postmaster@tstephenson.com
To: test@tstephenson.com
Subject: Unsubscription information
Date: Thu, 18 Dec 2008 09:44:13 -0800
MIME-Version: 1.0
Content-type: Text/plain; charset=US-ASCII
X-Text-Classification: good
X-POPFile-Link: http://192.168.1.2:8080/jump_to_message?view=24534
X-Recipient: test@tstephenson.com
X-PMFLAGS: 34078848 0 1 YIIVWBBL.CNM                       

Farewell from the testlist@tstephenson.com (Test Digest List) mailing list.

Your subscription to this list has been closed down, either in response
to an explicit request from your e-mail address, or to a command from the
list's moderator.

If you wish to re-subscribe to this list in future, please send a mail
message to maiser@tstephenson.com, containing the following two lines:

   SUBSCRIBE TestList test
   EXIT

Best regards,
The List Management.
 

Thank you,

Chris Anderson

[quote user="Konrad Hammerer"]

Yes, I tried it and it seems to work but I do not know if there is something I cannot see right now and this might cause me trouble later on. But I hope STUNNEL and Mercury now how to deal with this scenario!

No different that using a NAT router, all the connections come from the same IP address from the router to the server but if you look the original IP address is preserved.

Best,

Konrad

This problem *is* repeatable - I'm unable to move any folder at any time.

I'm using Mercury/32 v4.62 on XP.

One thing you might try.  Install Pegasus Mail on the Mercury/32 system and point the mailboxes at the Mercury/32 mailbox structure.  You can then work directly with the mail folders.  If nothing else this should make it easier to re-build the folder structure.

> This is pretty wierd. If I telnet from my office which is on the same
> lan as the server, I can telnet the mail server without any problem.
> Its only when I get home that I cant telnet to the smtp port 25. Will
> have to put the router off and connect the isp line directly to the
> server and see if that makes any difference. Once my mailserver ip and
> my external IP are the same, it should give me an idea if the isp is
> blocking the port. Although, they swear they arent blocking the
> ports..only blocking telnet to the ip. Sounds fishy to me..

Always difficult to get the fact's out of the phone support people.  However in this case they may be correct.

>
>  Do I need to make a mx record for smtp.bharatfloorings.com as well?

Nope, it's the MX host and it should have the IP address of the router.

>
>  Here is the mercury ini file..once again, I am very grateful for your help.
>

I'm removing some lines that are not pertinent.

>
> [General]
> myname:          bharatfloorings.com    # Canonical name for this server
> timezone:        +0000    # Time Zone to add to date fields
> file_api:        1    # Use the file api instead of queues
> mailqueue:       C:\MERCURY\QUEUE    # Where mail should be put for delivery
> smtpqueue:       C:\MERCURY\QUEUE    # Where the SMTP client should look for mail
> newmail_path:    C:\MERCURY\MAIL\~N    # Where to find the users' WinPMail mailboxes.

Ok, pretty normal.

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

You are running Mercury core, MercuryS (port 25 inbound), MercuryP (port 110) and MercuryC (port 25 outbound but this can change)


>
>
> [MercuryC]
> Host : smtp.bharatfloorings.com

This should be the host name of the ISPs SMTP host.  MercuryC will connect to the external SMTP host to send the mail.


> Failfile : C:\MERCURY\Mercury\FAILURE.MER
> HELO : bharatfloorings.com
> Poll : 30
> Scratch : C:\MERCURY\scratch
> ReturnLines : 15
> Timeout : 30
> ESMTP : 1
> POP3_Auth : 0
> Logfile : C:\MERCURY\Logs\MercuryC\~y-~m-~d.log
> Log_Verbose : 0
> Session_logging : C:\MERCURY\Sessions\MercuryC
> Session_logmode : 0
>
> [MercuryE]

Not used.

>
> [MercuryD]

Not used

>
> [MercuryS]

looks normal

> Debug : 1
> Logfile : C:\MERCURY\Logs\MercuryS\~y-~m-~d.log
> Timeout : 30
> Relay : 0
> Strict_Relay : 1
> Allow_Illegals : 0
> SMTP_Authentication : 0

Might need to turn on authentication for sending from outside the system.

> Session_logging : C:\MERCURY\Sessions\MercuryS
> Session_logmode : 0
> Compliance_Settings : 0
> Maximum_Failed_Rcpts : 4
> Max_Relay_Attempts : 4
> SSL_Mode : 0
> ST_Blacklisting : 288
> No_VRFY : 0
> SMTP_ConnFlags : 0
>
> [MercuryP]

Pretty normal.

> logfile : C:\MERCURY\Logs\MercuryP\~y-~m-~d.log   # Traffic logging file
> Session_logging : C:\MERCURY\Sessions\MercuryP\   # Directory for session log files
> Session_logmode : 0
> Scratch : C:\MERCURY\Scratch\MercuryP
> Timeout : 60
> UIDL_nul_list : 1
> New_UIDs : 1
> No_NUL_passwords : 1
>
> [MercuryX]

Not used

> # [Groups]
> # testgroup            :     TESTGRP
>
> [Domains]
; server : domain
> bharatfloorings: bharatfloorings
> bharatfloorings: bharatfloorings.com
> bharatfloorings: (202.177.251.251)

Wrong brackets, should be [202.177.251.251]

> Delta: bharatfloorings.com

Remove this one, you can only have one server.

>
> [Maiser]
> Maiser:          Maiser   # 'Username' of mail server account
> Helpfile:        C:\MERCURY\Mercury\MAISER.HLP   # Help sent on failed maiser requests
> Lookupfile:      C:\MERCURY\Mercury\MAISER.LKP   # Format file for the 'lookup' command
> Send_dir:        C:\MERCURY\Mercury\SENDABLE   # Directory for the 'send' command
> Logfile:         C:\MERCURY\Logs\Maiser\~y-~m-~d.LOG   # Mail server log file
> Notify:          C:\MERCURY\Mercury\TMP   # Dir. for pending 'notify' commands
> NoList:          N   # If 'Y', disable the 'list' command
> Local_only:      Y   # If 'Y', local 'notify' commands only
>

Found a workable solution!

Ended up using the daemon MercuryForward by Petr Jaklin - has been running like a champ for three different domains.  

[quote user="Bidul63"]

Hello,

I have a Mercury Transport System (V 1.48) for Novell NetWare.

Is it possible to modify the SMTP port to 26 (default value is 25) ? How I can do this, what are the modification to do in Mercury.ini ?

Not possible, the port 25 is fixed in the program.  You can change the port on Mercury/32 though and you can use Mercury/32 as a front-end to Mercury.

 Thank for your answer.

 Bidul63.

Thank you ver much!

Konrad

Hi,

The message come from outside network.

I have now tick 3 checkboxes :

* Do not permit SMTP relaying of nonlocal email

* Use Strict Relaying instructions (see help)

* Authenticated SMTP connections may relay mail

 Hope this will work.

Thanks for the advise.

If you telnet to MercuryI you'll find what commands are supported. Have to check - sounds very interesting.

Is there some firewall running on the server that might block SMTP, POP3 or IMAP connections? Try using Telnet to connect to port 25 and 110 to see what happens.

/Rolf 

It worked.

I created a htl-maiser Pegasus Mail account on both servers, edited the mercury.ini file on the HTL server so that it contained:

[Maiser]

Maiser:          HTL-Maiser   # 'Username' of mail server account

Helpfile:        C:\MERCURY\Mercury\MAISER.HLP   # Help sent on failed maiser requests

Lookupfile:      C:\MERCURY\Mercury\MAISER.LKP   # Format file for the 'lookup' command

Send_dir:        C:\MERCURY\Mercury\SENDABLE   # Directory for the 'send' command

Logfile:         C:\MERCURY\Logs\Maiser\~y-~m-~d.LOG   # Mail server log file

Notify:          C:\MERCURY\Mercury\TMP   # Dir. for pending 'notify' commands

NoList:          N   # If 'Y', disable the 'list' command

Local_only:      Y   # If 'Y', local 'notify' commands only

and replaced every instance of 'maiser' with 'htl-maiser' in the *.mer files in the root of the Mercury installation folder.

All mail for these lists is now accepted by the APS server. The HTL server polls the pop3 box and collects the mail for htl-maiser, and all introductory emails sent to subscribers after they ahve successfully joined a list contain the correct htl-maiser@heritagelincs.org address.

Hoorah!

They are just text files, open a couple with notepad (or better) and have a look.

If MercS is listening on your internet interface it could well be spam.

[quote user="Joerg"][quote user="Thomas R. Stephenson"]

Again not sure what this means.  If this is the MAIL FROM: address of the sending server can't you just change this to match a valid email address on your system? 

[/quote]

Here my summary again.

The managing card of the server is a DELL DRAC5 card. This card creates its own e-mail sender address ( DRAC5@[192.168.21.244] )when sending notification e-mails. This sender address is not adjustable. I'm only able to set an address of a recipient, a message text and a SMTP server IP address.

Now I have adjusted Mercury S to receive those "non-local" e-mails from the server. Mercury S hands over them to the Mercury Relay Client which tries to dispatch them to the ISP SMTP server. But this will be rejected  by the ISP because of non-registered domain ([192.168.21.244]). That's clear.

 Is it rejecting the From: address or the MAIL FROM: address?    

Now I'm searching for an opportunity to change the "non-local" address of the DRAC5 card to a already registered address (at the ISP) when processing in Mercury. May be I could solve it in the same way like the "translation" of e-mail addresses for our users. For example: My nmae is Joerg Mueller, my Pegasus login name is "jm". This normally causes to a sender address like jm@domain.com. But our registered ISP addresses read j.mueller@domain.com. Now I have created a synonym.mer file where all local user addresses will be translated to the official ISP addresses. This works properly.

Personally I change the MERCURY UDG via pconfig.exe from

 *Reply address format :  "~p" <~L~L~8@host.domain>

to

*Reply address format :  "~p" <~r>

and the users "Reply To:" address is used in place of the ~r.  This allows the users to have multiple identities with different From: addresses.

May be I could solve my DRAC5 problem in a similar manner?

Not really since this is a forward and it's going to be using the original From: address in the forwarding.   If you are not allowed to  change the it then you might have to send to a local address and then pull via IMAP4/POP3 from the outside world.  You might also talk to your ISP and explain the problem to them and ask them how to handle this.

One more thing.  Do you have a fixed IP address?  Does the ISP block port 25?  If the answers are Yes and NO then try using MercuryE and bypass the ISPs rules. 

regards

Joerg

Thanks.

The guy who was doing the web page tried it out last friday - I gave him the full MLSS address with the custom port number and it worked a treat.

Excellent, I was able to find and correct the function in phpbb, thanks for the help.