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!

[quote user="NessDan"]My previous ISP did not block port 25 nor did it require you to send mail through their SMTP. My current ISP (Comcast) does not block port 25, but I'm on a Policy Blacklist according to spamhaus.org. Many major email sites like Live mail and Gmail don't accept my mail, while websites like mailcatch.com receive it just fine. I've found out that I can use MercuryC to relay mail via Gmail's SMTP and change around a few settings so that I can get my mail to send to major providers without issue so that's the good news.[/quote]

The spamhaus policy blacklist (PBL) contains IP addresses that normally don't send mail directly.  You can apply to be removed, but your current setup using Gmail to relay mail will be much more robust.

[quote]One other HUGE problem I was having until now was that whenever I sent mail from an outside source (Live, Gmail, Texting w/ phone) to my mail server, I'd look at the SMTP end-to-end log and see that the message was successfully delivered, but I didn't see anything in my inbox. This got me very frustrated seeing that no one really posts on a forum to say that their SMTP client is successfully receiving messages :P. I found out that I had to go to Mercury's Core Module > Local domains > and add my domain name (nessdan.net) to the list. This worked wonderfully! I still really wanna know why that actually made a difference...[/quote]

The local domains list tells Mercury which domains it should try to deliver locally.  Everything else it will queue for onward sending.

[quote]My final error is this: when I try sending mail from my mail server to *10DigitPhoneNumber*@txt.att.net , I get an error:

T 20101105 225232 4cd4cfc0 Begin processing job MO000004 from root@nessdan.net
W 20101105 225233 4cd4cfc0 Error connecting to primary server '209.183.32.63'.
E 20101105 225233 4cd4cfc0 Processing of job MO000004 incomplete or failed.
T 20101105 225233 4cd4cfc0 Job MO000004 processing complete.

Inside of Mercury, it says that there was a connection error during a handshake. Then the rest of the lines are txt.att.net being resolved to the IP, then trying to connect to the IP, then a Connection error. When I try sending mail to the same address using Live mail, it works fine. Any ideas on what's going on here?[/quote]

This is MercuryE again and it won't work for the reasons you have already discovered.  Go back to MercuryC :)

Glad you are making progress with your setup, but it can be slow progress using trial and error!

> Can you please explain why exactly the VERP option would help us to not get blacklisted? Also would changing the "Basic minimum period
> between queue job retries" setting help in this regard as well? Is there any best practices or even laws that I should look into that
> would help before sending out this large email blast?

The VERP sends a separate message to each user so that the receiving host does not have to process a single message for multiple users.  This makes the sending process much less spammy.   That said, if the content looks like spam, and the users complains to their providers then you'll get blacklisted no matter what the sending process.  This is especially true if you do not have a subscription process where the receiver actively requests you to send them a message.

Thank you for the advice Thomas.

I made this switch a few months ago.  It was straightforward except that, as Thomas says, you do need to get your ISP to set up a ptr record (also called a reverse dns record) for your fixed ip address before many recipients will accept you.  Do that before you make the switch.

You could use an SMTP transaction filter to reject mail with invalid addresses.

This would not let the mail continue on it's way, but the sender would get an immediate failure, and may become more interested in sanitising their own address list :)

> Our company currently has a dedicated mail host in house that emails out directly to the clouds.  We do not relay to another mail host or
> anything.  We want to implement a feature where we can email clients who have missed their last month's payment when we print their
> current statement.  As such, I'm wondering - how many emails per day can be sent this way before being blacklisted by Spamhaus and the
> like?  Many of them say they don't blacklist based on volume, but by practice, but I'm unsure of other sites.  At a previous job, our
> admin said that AOL would blacklist us for sending out something like 500 1 recipient emails per day, or any number with more than 75
> recipients.  We may have gone through AOL for our mail hosting, however.

BTW, you can register you server with AOL and they'll not block but send you a message showing where an AOL user complained about your mail.  I registered my server with AOL and they do run a pretty professional operation.  The postmaster really does answer the mail at AOL, that's more that I can same for most ISPs.

>
> We typically have around 400 clients who miss a payment each month (usually not the SAME 400, of course).  However, this can jump up
> and down a couple hundred, and many will probably opt out.  How likely does this seem to get us blacklisted?

Probably never if each person was getting a separate, tailored e-mail message.  The number of messages sent generally has nothing to do with getting blacklisted by Spamhaus and others.  Most of the blacklists look at the content and not the process.  

That said if you are trying to send the same message to 400 RCPT TO addresses and it looked at all spammy then you're getting on at least someone's blacklist.  ;-(

Hi, I've set up the mailbe webmail pro correctly, but, a question came to my mind, I intend to use only webmail pro to some users outside my organization, but how can I convert the pegasus files to Afterlogic webmail?? I know that I can copy the arquives, but the entries at the database I have to create also, don't I?

Can somebody help me?

Thanks [:)]

No problem.  All installed now and good to go.  Love your software.  Thanks for the help.

Thomas it works perfectly !!!  Also other options are very interesting.

I have no words to say thank you ... Mercury/32 reserves allways a lot of nice surprises ... [:D]

Alex Bromo

> Could I have a second Mercury install, that POPs a domain mailbox from my original Mercury?
>
>  And then have this second Mercury forward with mercuryE to the server I'm trying to reach internally?

Sure but you might be able to do the same thing with WSMTPEx without the second instance.


The program WSMTPEx.exe (SMTPEX.NLM for Netware)  and this a separate program that takes mail for a email account and forwards it to any port and any hostname/IP address.  I use this with my domains to forward the mail to a Linux system (must use high ports as non-root) and to a second instance of Mercury/32 running on my system (can't share port 25)  Here's a sample of the ini file I use for forwarding all mail to Mercury/32 running on Ubuntu and Wine.   

 #  You can rename this tool, but name of following section must remain [WSMTPEx]
[WSMTPEx]
Version=0.10
#  TCP port, on which SMTP server listens
Port=8025
#  Number of seconds to delay between searches for emails
LoopDelay=30
#  Folder, under which is most of user's mailboxes
UserFolder=
Domains=1
# Users mail address domain part
Domain1=linux-tstephenson.com
LogName=c:\Mercury\WSMTPEx.log
SMTPServer=192.168.1.4
MailBoxes=1
Badmails=c:\pmail\mail\BadMail

[linux-tstephenson.com]
# When user name start with "DM:", WSMTPEx will try to find SMTP envelope address in mail file
Mb1addr=dm:ubunto
Mb1dir=c:\pmail\mail\ubunto


This takes all the mail in the domain account "UBUNTO"  and sends it to port 8025 on
192.168.1.4 to be received by MercuryS.  The directory BADMAIL I have specified
must exist.  You can run multiple instances of this tool and and it can be run as a
service.  If run as a service and running multiple instances the name of the program
should be changed.  I use WSE-UBUNTO to rename the program and ini file for this
one.  

Many thanks to Petr Jaklin for the development of these tools.  You can get these
tools at the community download areas or directly from Petr Jaklin's site
http://www.3net.cz/software/softe.htm  

> Am I the only one apparently having this problem?

Since I get Hotmail all the time to my domains I do not see a problem here.  I also quickly went through the MercuryS logs and did not see any rejections of Hotmail connections.  FWIW, they all used the proper <> around the RCPT TO address. FWIW, if MercuryS was rejecting for the lack of the <> around the address then you should see it in the logs.  If you do not see any rejections then the MS comment is spurious.

Also, I went through two months of mail in the MercuryS log looking for hotmail.com and found that most of the connections using this host name did not have an IP address associated with MS (Hotmail, MSN)  at all and were blacklisted IP addresses.

> 1 - Why is the 'Internet name for this system' not automatically also used as a local domain? wouldn't that make sense?

Not in a lot of cases.  The system name may be what you want to maiser and postmaster domain to be but it may not be a domain that has any local user other that the postmaster account.  If this is used as the connecting host name there can be real problems if this is not in the domains list.  There is nothing added to the domains be default since it's expected that the system admin only list the domains where there is a set of local users or aliases.

> 2 - other mailboxes got corrupted, blank messages appeared. Deleting those resulted in more errors regarding files that could not be
> deleted from some queue.

Not sure what you mean here.


> 3 - if observation 1 has a valid reason, I think Mercury should still not crash

If it trying to deliver a message to a local user with the domain matching the name of the system and not listed in the domains list then this would be a major configuration error.  When you start getting bounces of huge messages then it's quite possible that the OS could be running out of handles trying to handle the configuration error.

OK. Database restored from backup. Vacuum and reindex commands completed successfully. GW is working now.

 [:)]

Thank you for your help.

Jyrki

Hi,

thank you very much Mr. Stephenson!
Works great now.

Regards