> i've got an old backup text export of my mails, i'd like to re import in any common format (like mbox). > (haven't been using pegasus for years, since i got rid of windows.) > Could someone help me to identify the format, and suggest how to parse it, or convert it?
Not sure what you are saying. How did you backup the messages? Send this all to the a single text file? Extract the messages to single message files?
Pegasus Mail messages are just RFC 2822 messages and the file extension can be changed to match the extension required for most any new mail of a mail client.
FWIW what operating system are you using? Pegasus Mail (and Mercury) can be run on Mac/Linux using Wine.
Mercury supports any charset in messages, but not in IMAP SEARCH queries. In this case the query is for all messages (in the given range 1 - 64) that do not have the /deleted flag set. As there is no text part to match here I'm not sure why a CHARSET was specified at all. CHARSET is not a required part of a query according to RFC 3501, but the server is required to return a NO response if queried with a non-supported charset. It's then up to the client to adapt to that, but in this case the client simply repeats the exact same query one more time (hoping that the server is going to change its mind?).
I would suggest that you try POP3 instead of IMAP to access the mailbox, or see if there is an email client update or some alternative email client available.
If after making sure that the settings for Local domains and host name in Mercury core and MercuryE configuration are OK (have a look in Mercury help!) sending still fails the most common reason is that your Internet provider blocks port 25. Many Internet providers do this to stop spam bots, unless it's a business connection that is expected to host servers. If so you could try asking them to open port 25 for you, or you could switch to using the MercuryC module and relay mail through your Internet provider's SMTP server.
Hmm ... you had Mercury/NLM on a Novell Netware server - right?
Now the servers os was replaced with Novell OES.... so there still is a NDS/eDirectory.
Have a look at the logs. Is MercuryS receiving mails? Or are they not delivered to users homediretories?
Anyway ... the WinXP has another IP-address than the Netware server before. Did you change the involved DNS-entries so that external SMTP-Servers know about where to deliver?
Thank you for the prompt reply. As it turns out, the root of the problem was my own lack of faith. Both systems are configured identically and both Mercury installations are identical. And when I went into the system tools to investigate my problem, lo and behold there was Mercury running as a system service exactly as it should. Apparently, all I needed to do was to reboot after copying Mecury over to the new server and that was the only thing I had forgotten to do.
Sorry for the false alarm; I feel like such a Noob! (And I've been around long enough that I should have known better!)
[quote user="FJR"]Donwloaded CalmAV from http://www.clamav.net/lang/en/about/win32 which gets ClamAVWindowsSetup.exe and got no warning from my Sophos!!![/quote]
That is the cloud version is no good for integrating with Mercury.
[quote]So I think it is not OK!!![/quote]
Maybe he has a corrupted version but I've never had anything bad from tBB at hideout.ath.cx, so it could be a false positive from Sophos.
[quote]In most cases you should download from original source![/quote]
In this case in would be but that lacks some optimisation and a built-in service installer. tBB's version (above) hasn't been updated recently, so I would try the version at http://oss.netfarm.it/clamav/ which is up-to-date.
> I'm at a loss. I'm not sure why I can send it to the postmaster, but > none of the other accounts.
Not sure what to tell you here's a couple of things to try.
1. Try using CTRL+Configuration+Manage local users and edit one of the users.
2. Send a message to postmaster using the Reload users.
* The mail server now has its own password file, created and managed on the "Mail server" configuration page. This is not covered in the help yet, but you can create any number of mail server passwords that can be used in a "PASSWORD" command to handle the new operations described below. If you have no password file, then no password will ever succeed and the new operations will fail automatically - hence the operation is secure by default. Mail server passwords are simply one-per-line (like everywhere else) and cannot contain the character ';' (semi-colon).
* A new mail server command, "KILLFILE" has been added. This command allows you to manipulate the MercuryS killfile by mail. At present, the only implemented command is "KILLFILE ADD", which adds the parameter you supply to the MercuryS killfile. An example is at the end of this message.
* A new mail server command, "RELOAD" has been added. This command allows you to force Mercury to re-read certain configuration files by mail. At present, the only implemented command is "RELOAD USERS", which takes no parameters, and tells Mercury to reload the user database, PMAIL.USR.
Both of these commands need to be preceded by a PASSWORD command specifying a valid password from the password file created in the mail server configuration dialog.
Examples (these examples assume that the password 'foo4u' is specified in the Mail Server password file):
* To add *@163.com to the MercuryS killfile, issue these commands:
PASSWORD foo4u KILLFILE ADD *@163.com
* To force Mercury to reload its user database, issue these commands:
PASSWORD foo4u RELOAD USERS
The commands are not case sensitive - I've shown them in uppercase only to emphasize them.
I plan to add more commands of this kind - administrative in nature - and will be adding a level of discrimination to the password file to allow passwords to work only for certain types of operation (hence the reason why ';' cannot be used in a password).
> I tried to run pconfig.exe and got the message "The version of this > file is not compatible with the version of Windows you're running. > Check your computer's system information to see whether you need an > x86 (32-bit) or x64 (64-bit) version of the program, and then contact > the software publisher." I'm running Windows 7, Pegasus Mail 4.52 and > Mercury 4.73.
You are obviously using Windows 64bit and it does not support 16 bit programs. pconfig.exe is 16-bit.
To run 16-bit MSDOS programs on your 64-bit Windows systems (and Linux) get a copy of DOSBox. This is quite handy to have around when you have old MSDOS utilities to run.
http://www.dosbox.com/
> I looked for an alternative version of pconfig in the downloads, but > couldn't find one. Can I edit pmgate.sys directly, or do I need > pconfig?
You cannot edit the pmgate.sys directly, it's binary.
Don't know if they are described in detail somewhere, but have a look at these logfiles. Regular means, that every logentry in one logfile has the same entry in simple text. I.e. the coremodule has the columns "status (Input, Output. Error), date, time, job ID, from, to, msg size" per line.
I have red the user manual again and found some requirements for the "To:" field within the settings of distribution lists. It should looks like a real e-mail address. I will test it again.
On Wednesday, November 30, 2011 at 16:45, Pegasus Mail & Mercury - Automated Email wrote:
> This is another question about something we need to do for our new > owners. They have a company signature that they like to have used on > all email which includes pictures and hyperlinks to various pages on > their company web page, youtube facebook etc. It is easy enough to > paste the signature in to the Pegasus signature after the personal > bits and I can do it that way for all users or they could be asked to > do it themselves.
This is what I recommend since this means only the mail that they generate using a specific ID will have the signature created. The users must be setup to send all "Rich text" messages to get the graphic signature.
For each of your nine signature sets, you can create both formatted and unformatted versions of your signatures: the unformatted version will be attached to plain text messages, while the formatted version will be attached to any message that contains formatting - pictures, tables, bold and so on. The formatted variants of your signatures can themselves contain tables and pictures if you wish.
> > I do not think the add a text fragment filtering rule or the Mail > disclaimer add on for Mercury will handle this kind of data though. > Is there a way to add a signature block of this type to the end of > all emails automatically on the server? I am quite happy not to do > it on internal mail or on Forwards of course.
You could probably do this using an outbound filter where the domain of the From: address matches the desired domain. The problem here is that you will have to be sending all HTML messages to get the graphics and/or you will need to have both a plain text and HTML version of the outbound message. In addition, this will always create the signature even if the message already contains the signature.
Inserting text into a message
One of the more powerful actions a rule can take is to insert text into a mail message. This can be used to add corporate disclaimers to outgoing messages, to indicate that particular messages have been processed by the mail system or just about any other purpose. The process of inserting text into a message is actually very complicated, but Mercury is quite smart about it and can handle all the most common cases. When you create a rule with an action that inserts a text fragment, you provide the rule with the name of a text file containing the text it should add. If you wish, you can create a second file in the same location and with the same name, but with the extension .HTM, containing simple HTML text that Mercury should insert into HTML documents. Mercury will insert the text version of the file into plain text message parts, and the HTML version into HTML parts (it is inserted immediately before the </HTML> tag at the end of the message). If you do not provide an HTML version of the text, Mercury will insert the text version in a <BLOCKQUOTE> section of the message, which is probably adequate for most situations. Note that if you provide an HTML part, it can include most HTML formatting except for graphics.
Ah well our new owners use hosted mail and access via POP3 from the clients. They had wanted us to do the same and to point our old MX records at gridmail. This seems a bit cumbersome and would have meant us having no central store of our email which could be backed up, and no archive account to cover us for legal liability under local data protection legislation. I was looking at ways to keep our system while allowing GridMail to forward our legacy stuff and wondered if I could set GridMail to forward directly to our IP address.
However there are other reasons for not doing this to do with the fact that we use our server in our internal workflow so it is better to keep our old URL as our local domain. That means we can use it to do the forwards from GridMail which is what I have set up. If however our new users insist on grabbing our old URL we could ask for a sub domain of their Domain as a compromise which although it is obvious was not an idea that had occurred to me.
At the moment I am hoping they will go for us setting all users to have their from and reply to addresses at the new domain which I can do by making Pegasus send via SMTP to ourinternal server our our local network instead of using the built in link and by setting all the GridMail accounts for our new owners domain name to forward using SMTP to our old URL a set which is pretty much invisible to users. I have this working for my own email already so its a case of job done if the new owners are happy.
Thanks again Thomas. I will have a go when I get home and can log in to work again. I found PMGATE.sys in my PMAIL program files dir I assume thatis the one to change. The do not put the Pegasus program in "Program Files" is suddenly making loads more sense!
I have found it all now I am logged in at home. Thanks again.