The perfect forum for general discussions or technical questions about Mercury Mail Server.
What do you mean with "Mailing List Template"?
Do you want a skript (i.e. PHP/Perl) for your webserver for subscribing/unsubscribing to/from lists?
Or do you want a configuration template/example for Mailinglists?
bye Olaf
I disabled the Windows indexing in M32 folder, subfolders and files; no more crashes. Thanks again.
Filippo
Thank you so much.
> 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.
cheers Olaf
Hi Olaf,
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.
Greetings
Joerg
nevermind I got it working :)
thanks for your help I appreciate it
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.
It seems to me that NTWrapper is no longer available.
The developer-site is down, and I was not able to find this software.
For those who have the same problem, and for some reason can 't buy a licence, here is another solution that works with Windows 7 64 Bit.
Had the same problem with Pegasus and Thunderbird both configured that MercuryI only supports trays (not like directories on filessytsem capable holding directories and files: folders holding mails and subfolders). Created them with Pegasus and all seemed good. closed Pegasus and opened Thunderbird. All seemed good too. Next day opened Pegasus @work and all trays have been at root.
OK ... tried deleting the trays - which resulted in .
Created a hierarchie of trays and folders some days later and it seems to be stable. May be your moving of trays resulted in same stability (didn't try that, so don't know if it had worked in my case)?!
May be it is an initial problem on new IMAP-Mailboxes or first time creating a tray with subtrays? Just my suggestions ...
bye Olaf
Dear David,
[quote user="David Harris"]Looking at the code, there is definitely message-id generation going on in Pegasus Mail,[/quote]
That's correct (but not the point in discussion about Mercury/32 and creating MIDs) ...
[quote]although for some reason it's controlled by the setting of an internal system flag, and I can't see clearly what the default value of that flag would be. There also doesn't seem to be anywhere in the UI to change it, although it *appears* that it should always be turned on by default.[/quote]
... if you want Pegasus to create a MID. For some reasons we don't Pegasus want to do it (see other posting in same thread).
The default value of "general system flags" is 0. Via UI you may only change it to 1 by activating session logging. I suppose default is 0, because otherwise SYSLOG.PM will increase endless.
[quote]Suggest to him (not as a solution, just as a curiosity) that he look in his PMAIL.INI file and find the entry called "General system flags": it can have the values 0, 1, 2, or 3. If it's 3, tell him to set it to 1. If it's 2, tell him to set it to 0. This will tell the program to generate message IDs. On my system, it has the value "1", which turns on system message logging. If it was a value other than 1 or 0, could you let me know?[/quote]
I know all about that flag and it was 2 - as wanted!!! But that's not the point in that thread and I think, there is no need for you to change anything on that in the code of Pegasus. Works fine and as designed! The changes should be done in Mercury/32 for the case, that no MID is in a mail from a local user to a local user.
[quote]Should definitely be working, though.[/quote]
It does ... as designed by you. [:D]
@Thomas
[quote user="Thomas R. Stephenson"]I've set the flags to 1 and it's creating a message-id for mail to local users when mail is sent via MercuryS using the built-in mailer. Here's the raw view as received.[/quote]
I know ... but we don't want Pegasus to create a MID and some mailclients (even on smartphones) used here don't do it too. Mercury/NLM, which I used until some weeks ago, did create MIDs for the problematic case (local to local), but Mercury/32 doesn't do that any more. That's my point and I hope David is willing to change that for next version of Mercury (obviously 4.74).
Cheers
Olaf
Hallo Thomas
[quote user="Thomas R. Stephenson"]Mercury maiser creates a new message, it does not just bounce a message. It removes all addresses in the message body to ensure that the list mail only goes to the list members. The To: field is being corrected to the actual setting of the list. These addresses are made comments in the the message. This is all by design.[/quote]
Hmm ... reads like having a designdiscussion. I'm on many mailinglists and some of them administered by me (i.e. the german Mailinglist for Pegasus mail), most of them on majordomo and mailman ... and even had that lists on Mercury/NLM before. None of them behaves like that ... it is very (!!!) unusual.
I've built some mailutilities with perl, PHP (long before they had modules or libraries for that). I used it with Mercury/NLM simply placing ready to send mails as files in the queuedirectory. All you need to do is to add a envelope with mailadresses for sender and recepient(s). In case of maiser you may wish to add headers like sender, errors-to, reply-to, may be some list-headers, change return-path and add some received-lines. Thats all. The other headers don't need to be touched.The recepients are in envelope - nowwhere else, that's all you need to enshure only listmenbers get the mail. So - why does mercury touch and manipulate the other headers? There is no reason at all!
[quote]If you really need to maintain the addresses in the original body of the message then use a real Mercury account and a FORWARD file in that account to bounce the mail.[/quote]
For shure I'm not the only maintainer who needs this information and most times he may not have access to my Mercury/32. And I don't want to have thousands of mails forwarded to have probably that one I have to maintain. It's not my private playground at home - it's the mailserver of a faculty. I was willing to buy a big license of Mercury/32 ... but the more bugs or unusual behavior I find while testing the more I get in doubt.
Sorry, but there is a simple rule in mailhandling: never touch headers that you don't realy need to touch!
bye Olaf
Thanks for the help with login details. I forgot!
I am sure You have right about the bracket and that sort of things, But I can tell You, that without having changing anything, I can now send email to what ever address I will.
I dont understand what have happend, but now everything is working. also from magento!?
OK.
Time to move...
Thanks.
Hi Fulwoodblade,
We experienced problems with Mercury after reduction of the mail retrieving frequency of Mercury X. Mercury is running on a Win Server 2003 R2 (32 bit) with 4 GB RAM. When setting the frequence to "0" (means permanently retrieving) Mercury crashes from time to time (at least once per week) allthough the windows process was still running. Also with deactivated Mercury X, where the Mercury C and D modules use their own timer, Mercury crashes from time to time. It seems Mercury becomes instable when the poll frequence is set lower than the TCP timeout.
Now I have reactivated Mercury X and have set the retrieving intervall to 1 minute with a 30 second TCP timeout. Now it works stable again.
Brgds
Joerg
Edit: Now, appr. half a hour later our Mercury crashed again. There must be another event which causes to the Mercury crash. Please refer to my connected post:
http://community.pmail.com/forums/thread/31830.aspx
You're right. MSE don't really notify you if the website your visiting is infected or not. And that we still need another software for that. I hope there's a free software for that since I'm on a tight budget as of now. =)
While using POP3 (I asume you do) choose your POP3 definition.
On GENERAL you will see a button with "Delete messages from server if sucessfully received" (or something like that - translated from german). Deselect that button.
bye Olaf
If your problem is, that you will read the emails without Pegasus Mail on your system, than you can link .CNR and .CNB to any software, that is able to read EML-Files.
For reasons of security we did not link new mail files (.CNM). It is however just as possible.
We use this feature to search by help of Windows explorer in Pegasus Mail systemwide folders and noticeboards.
For Outlook Express or Windows Mail clients it is necesseary to add some registry keys in the classes root. It is tested with Windows 2000 up to Windows 7 x64 (W7 must patched to Vista WinMail).
I put the scripts there
Torsten
