afaik, mailing list signatures only work with plain text messages and not multipart boundary ones.

Further to Peter's reply, here is what the Mercury help file says about list title and the From: field:

List title  Every list must have a title -- a descriptive name that Mercury will use to form the "from" field of messages sent to the list. Try to keep the title short and descriptive and avoid international or accented characters. On rare occasions, you may wish to include address details as part of the title (Mercury usually adds the proper address to the list title automatically): in this case, you should ensure that the address you enter conforms to RFC822 addressing rules and includes a fully-qualified domain address appropriate for the list, then check the control labelled Is a full address next to the list title. NOTE: This feature is extremely specialised and is not normally required; because it can cause problems with mail delivery, we recommend that you only use it if you are very sure of what you are doing.

/Rolf 

I'm glad you have this sorted.

Sending separate attachments dates back to earlier standards, and the default for new installs changed some time ago to embedded attachments.

Nope, no limit on the user count.

Restart, and if it doesn't help, send me your ini file privately and I'll have a look.

[quote user="Francisco6x"]

But, how to configure Mercury to receive localhost email from Thunderbird?

Thank You, Francisco 

[/quote]

 

If you are running the MercuryS SMTP server then you tell Thunderbird it as the server.

 

UID calculation in MercuryP and MercuryI have been overhauled in the upcoming release.

> Thanks for the help, your instructions were clear and worked for me.
> Now I am trying to determine a way to mass populate some of my
> larger mail lists, hopefully I will find it soon. The config file
> itself doesn't look formatted in a way this would be easy with an
> editor. If you know of a way to mass populate a mail list, I'm all
> ears.

Here's a utility from James Haley that makes this pretty easy.  I can't pass you a URL for his site since the one I have does not work.  I can provide a copy of the ZIP file though. It should be attached, if it is not contact me directly.

BuildMLF is a freeware utility program for use with Mercury Mail.

BuildMLF builds MLF files from text files.  In Mercury Mail, MLF files hold information about people subscribed to mailing lists.  

If you have previously used LIS2MLF for converting text files to MLF files, this does the same thing but adds some additional functions.  

This program is free, on the condition that you help support Mercury or Pegasus Mail. If you find this program useful, you use Mercury extensively and have a interest in seeing its success continue.  Here are several ways you could support Mercury and Pegasus Mail:  

* Buying a Pegasus Mail or Mercury Manual
* Not using Pegasus Mail or Mercury for uses against the Terms and Conditions, such as sending unsolicited bulk e-mail.
* Helping other Pegasus Mail or Mercury users.
* Writing and making available your own Pegasus utilities.

>
> Thanks again,
>
> Travis Wineinger  

OMG how simple it can be! I've noticed that i can also remove the filtering in global filtering rules.

 

It works like a charm! We are most happy now!

 

 

Thanks for that, Pingu. the page is now bookmarked :)

Connection history of POP3 Server reports the following info:

"... 

User admin, (2) 0 messages, 0 bytes

..." 

What means the number "2" in the brackets?
 Anybody an idea? Thanks.

Hartmut

Hi!

Is mercury able to accept ssl imap and smtp connections directly without having a tool like stunnel in between? Of course, stunnel is an option but using this kind of tools, mercury must be configured to accept plain text connections as well and I do not want this option to be active! Most of my users use TLS but some of them want to use Outlook and Outlook does not support TLS. Therefore I need SSL as secure connection. Now, using stunnel, I must enable the plaintext logins and so the users can connect via Port 143 in plain text because this port must be open in my firewall for the TLS connections...
 

Thanks,

Konrad 

Yes we use a CA antivirus product and I find we actually have to turn the real time off completely because even with the drive the email is on exempted from real time checking it still seems to Detect viruses in files on those drives, mainly when our archive Pegasus account which runs on the same server is filtering emails.   I have just changed the settings so that it never starts that way I should not have to remember to turn it off.

 I tried to get ClamAV working a week or so back I really ought to get back onto that.   I noted a thread where someone else was having similar problems the other day so I'd better read it!
 

Hello Thomas,

 

Many thanks for your help.

 

ineuw 

Oooops - in my excitement after noticing this new feature I missed the html file....

 Thanks, Gordon

Cheers Thomas. [:)]

Hi, yep thats it, sorry typo from my end.  So not needed on Windows then.

You have not turned off relaying since the first two items are not checked.  I would recommend checking the first three items to turn off relaying and allowing authorized users to relay. You can then set the two internal IP addresses  in the allow section to be allowed to bypass the relaying.

 

It can be an advantage to have a 'Swiss Army Knife' rather than a drawer full of knives & forks [:D]

try 'telnet localhost 25' [:)]

 

Hello all

This was also reported tonight on SANS's weekly Consensus Security Vulnerability Alert (Vol. 6 No. 39) and rated Moderate:

(7) MODERATE: Pegasus Mercury/32 IMAP Server SEARCH Command Buffer
Overflow
Affected;
Pegasus Mercury/32 version 4.52 and prior

Description: Pegasus Mercury/32 IMAP is a popular IMAP server for
Microsoft Windows. The server fails to properly handle overlong IMAP
SEARCH commands. A specially crafted IMAP SEARCH command could trigger
a buffer overflow and allow an authenticated user to execute arbitrary
code with the privileges of the vulnerable process (often SYSTEM). A
proof-of-concept for this vulnerability is publicly available. Note that
an attacker would need valid login credentials to exploit this
vulnerability.

Status: Vendor has not confirmed, no updates available.

References:
Proof-of-Concept
http://downloads.securityfocus.com/vulnerabilities/exploits/25733.pl
Wikipedia Article on IMAP
http://en.wikipedia.org/wiki/IMAP
Vendor Home Page
http://www.pmail.com/
SecurityFocus BID
http://www.securityfocus.com/bid/25733

Note that it is listed upfront in the newsletter as MErcury is considered a widely deployed software (a bit of vanity doesn't hurt [;)] ) As you can see, there seem to be a proff of concept out there. I cannot verify myself as I currently have no working installation of Mercury.

The SANS institue can be contacted from their website at www.sans.org.

Cheers!