I could really use the LDAP Synonyms listed under Configuration -> Network Support.

I don't use Pegasus Mail as my primary mail client but would greatly benefit from using LDAP lookups for valid email addresses. My Mercury/32 server is set up as an in and outbound relay for various servers and systems and is not my message store.

Is there any way to configure Mercury/32 to perform those LDAP lookups?

Happy Holidays to all

Thank you for the fast and precise reply.

grebbi

>>  So, if I needed to change the location of the Pegasus Mail submission queue could I simply enter the new path to the mail

>> submission (queue) directory (in UNC format) then hit "update configuration" instead of configuring it via PCONFIG?

> Yes, if you did not use identities or did not care that the From: address would always be the same for a user.  I make a number of changes to my UDG so I never use the functions in Mercury to > > modify the UDG.

At the moment I don't have an entry in the Configuration|Pegasus Mail field for the path to the Pegasus Mail executables so the path showing in the outgoing queue field is incorrect.  It is a shame that there isn't a way to enter the path to the executables and have the field for the outgoing queue be updated automatically from PMGATE.SYS.  I certainly don't want to risk updating the configuration just to get these fields to reflect valid paths but it sure mislead me for a few moments when they didn't.  A suggestion to David to fix this perhaps?

> BTW Brian, notice how much easier it is to follow a thread in the PMail mailing lists.  ;-)  I really hate this stupid editor!

AGREED!!!!  The only reason I post here is for maybe some additional perspective from the folks who are active here but aren't active on the list.  It sure is tedious communicating here though.  Of course, communicating with a handheld wireless device is tedious to me.  Is my age showing? <G>

There is no exception list in MercuryS blacklist handling. If you want to be able to take additional aspects into consideration you should change the blacklist definition to tag the message (add a header) instead of rejecting it, and then select the appropriate action using global filtering rules or a daemon.

/Rolf

The mail folder format should be the same, and the program should report it's result regardless of if it's success or failure. If you run the program without any parameters you should get a help text looking like this:

Pegasus Mail/Mercury mailbox maintenance commandline utility

Copyright (c) 1990-2010, David Harris, all rights reserved.

Commandline usage -

   MBXMAINT <command_filename> | <option [option...]>

      -QU[IET]

      -CH[ECK] <folder_pmm_path_with_optional_wildcards>

      -CO[MPRESS] <folder_pmm_path_with_optional_wildcards>

      -MO[VE] <source_path> <dest_path>

      -RE[PAIR] <folder_pmm_path> 

  If the file path is right it could perhaps be that the file system returns an error because the limited space won't allow it to unpack the files. Try it with a very small folder to start with.

/Rolf 

FYI to all...

Ellie has this fixed.

As Thomas says you can't access the envelope recipient in filtering rules, only original message headers (TO, CC). You could use MercuryS transaction level filtering to stop all messages to that mailbox, though, or you could delete the mailbox and set the server not to accept messages to invalid local addresses if that is an option in your case.

For fine grain alternatives it will have to be a daemon, though. There was a request recently for a daemon to stop local users from sending messages to external addresses that are known to not exist any more, and that could presumably be modified to cover other special circumstances as well.

/Rolf 

> The purpose of the PTR record is for reverse dns right?

Correct

> is there a way to enable short names

They work for me when sending via the Mercury queue with Pegasus mail.  The address is expanded though when passing through Mercury.

> thanks for the info, the url doesnt seem to work

I don't know, I'll check this out.

Mercury starts with the system. Loader.exe is in All Programs\Startup and maintenance is scheduled for 2am each day. Mercury is always run under the domain administrator login. The domain (and local) administrator accounts have full control over mercury\*.* and pmail\*.*. User mailboxes are nested under pmail\

It has worked fine for several years - this happened once before. It is a testament to the resiliency of Pegasus Mail and Mercury how easy it is to recover from these situations.

A MX lookup for your domain gives this result:

- Name=imagineandthink.zapto.org
    Type=MX, Class=1, TTL=60 (1 Minute), RDLENGTH=4
    Preference=10, Mail Exchange=imagineandthink.zapto.org
Additional Records Section:
- Name=imagineandthink.zapto.org
    Type=A, Class=1, TTL=60 (1 Minute), RDLENGTH=4
    IP Address=121.215.144.174

However, I'm not able to connect to 121.215.144.174 (no ping response, no reply on port 25, no reply on port 110). In other words, the MX record is formally correct, but there is no server to be found at that IP address.

So: Make sure the MX IP is right, make sure the required ports aren't blocked by a firewall, make sure SMTP and POP3 ports are forwarded to the local server IP from your Internet router/modem. Furthermore, to connect locally to the server on port 110 use the LAN IP address, not the public IP.

This is the networking part. Besides that there might be things to check in Mercury configuration, but we can come back to that when the network issues are resolved.

Needless to say it's much easier to set things up with a fixed IP if that option is available.

/Rolf 

How do I  configure pop server passwords in a non netware mode mercury configuration

You enter them manually in Configuration | Manage local users by editing the user and entering a password.  This password ends up in a file called passwf.pm in the new mail directory of the user.  Here's a sample.  The <password> is replaced by the desired password.

[quote user="Thomas R. Stephenson"] The problem is caused by the receiving system not properly handling the packet too large error message so that the sending system does not know that it must reduce the packet size.  On the Mercury system you can turn off the  MTU discovery which always uses the same packet size.  BTW, when you test the MTU size it's best to test against the server with the problem.[/quote]

Thanks for the explanation. I'm presently learning the intracies of TCP/IP and so far have discovered that there are a lot of controls in place to try to prevent this from happening. Although I still have a lot more to learn, I guess that there exists the odd system along the route that is ancient or does not comply with the RFC's.

[quote user="Thomas R. Stephenson"] Typical problem where the receiving system is not properly handling the MTU Discovery operation.  When using MTU Discovery, the sending system keeps increasing the packet size until the receiving  system sends back the packet too large message.[/quote]

Again, from I have read, TCP on the receiving system should close the receive window so that the sending system stops sending data until it receives a notification that it can resume. However, I'm still working my way through this so this statement may be rather naive...

[quote user="Thomas R. Stephenson"] If the anti-virus software is setting between Mercury and the receiving host monitoring the TCP/IP transfer then this can also cause the same sort of problem.  Most anti-virus operating as a proxy is probably causing more problems than it solves.[/quote]

Thanks for all the help. I guess that all I can do is contact the receipient and say that this behaviour is beyond our control.

Cheers!

1. Make a backup of that mailbox.

2. Delete the file named newmail.cac

3. Verify that the file in question indeed has the correct filename extension (which presumably is .PMM). If not rename it. Try opening the folder again.

4. If it still doesn't work, get the mbxmaint utility from your Pegasus installation, or download it from here:

5. Run a check on the folder. If mbxmaint reports a problem, run a repair. If possible, close Mercury and Pegasus while doing this.

/Rolf 

> Hi, I'm new in Mercury mail, even I'm trying it before to get the software.
>
>  My problem is: I need to keep the e-mails of all my users into the  server, because when I have a problems with the computer, and is
>  necessary to restore the software, I can restore the e-mails from the  server, is this possible with mercury? and how can I do?

If all of the users use IMAP4 then you will have all of the mail on the server.  That said, IMAP4 is a much more busy protocol that POP3 and if you have a lot of users then you need a honkin' big server (multiple processors, gigs of RAM) to handle the process.

If all of your users were using Pegasus Mail and are all on the same LAN then they could be using Pegasus Mail in the direct mode and forget about using any sort of POP3/IMAP4/SMTP at all.

1.  Install WinPmail in the multiuser mode on the "server".  Use c:\pmail  for the program; c:\pmail\mail for the mail directories.

2.  Run PCONFIG.exe from the WinPMail program directory and change the HOME and NEW mail directory specification to the \\server\vol\pmail\mail\~8
    format.

3.  Go to the remote workstations and install a shortcut to the common program.

Ok, now you have the basic mail system setup.  You can send mail to each other using Pegasus Mail.  

4.  Install Mercury/32 on this same server pointing to the Pegasus Mail directory structure.  Use MercuryD, MercuryS, MercuryC at least. Use
    \\server\vol\mercury\queue for the mail spool directory.

5.  Point MercuryD at all of your POP3 mailboxes to download the mail to your Pegasus Mail user directories.

You now can send and receive Internet mail via Pegasus Mail.  The mail is delivered to the Pegasus Mail directories automatically.  You send mail simply but putting the output files into the Mercury/32 mail spool directory.  This is accomplished automatically with a Pegasus Mail User Defined Gateway.  

6.  If you want to maintain other POP3/IMAP4 clients, point the client at the at your Mercury/32 host as a POP3 and SMTP host using the Pegasus
    Mail username and password to pickup the mail.

You can do a complete inbound and outbound mail archive with this setup using a simple Mercury/32 "Always" filter that put a copy in a users mail directory.

[quote user="davron"]When I used option one I utilized MercuryE and it worked nicely. The Name servers input was left empty. 

When I wanted to work inside my network, in MercuryE there was an error which said (in general): can not resolve the "domain" (), so I cuntinued with your recommendation and I transfered to MercuryC.[/quote]

For sending and delivering mail entirely within your network, neither MercuryE nor MercuryC should normally come into use - Mercury should recognise that it is a local delivery because the domain name is in the list of 'Local domains', and deliver directly to the mailbox.

[quote]In the definition for the Smart host name i entered the mail server IP, and I had to enter my user name and password for authontication. Now MercuryC worked as well.

When I operated MercuryC and left Smart host name empty the program crashed. The site does not permit me to upload the printscreen of the crush, and I did not find any dump file to upload.[/quote]

MercuryC must have a hostname or (IP address) or else it can't operate.

Evening all.

I'm playing with global rulesatm, specifically printing. I found from back in 2008 which talks about printing attachments, but I'm more concerned with non-plain-text emails.Is there any way for mercury to nicely print HTML emails? If not i've planned a script to run instead which will go something like this:

• called by "run" filter for specific email address
• check script isn't already running (if so end)
• for each .cnm in local-users-direcotry
• open file as a text stream
• insert <html> & <pre> tags around header
• deal with message body as best we can
• create file array
• push each attachment through a binary stream and save them
• add each filename to the file array (including that of the original with .html extension)
• print each file in array using its default app (if possible)
• delete each file in array and delete the original email

It feels like overkill to have to go that far but i can see a better way to do it using the rules.

Any thoughts?

(p.s. i'm running v4.72)

You are right, it is not Mercury.

See here...

http://support.microsoft.com/kb/312362

I fully understand now, thank you for the response!