> Sorry for taking a long time to respond.
>
>
> I think I understand now, but here is the file you requested Thomas.
> I'll wait till you have a chance to look at it before changing
> anything. Let me know what you think and what changes need to be
> made to the postmaster account.

Here's some comments about your Mercury.ini file.  I've removed the parts that I did not want to comment on.



[General]
myname:          bucataruserver    # Canonical name for this server
timezone:        +0000    # Time Zone to add to date fields
file_api:        1    # Use the file api instead of queues
mailqueue:       C:\MERCURY\QUEUE    # Where mail should be put for delivery
smtpqueue:       C:\MERCURY\QUEUE    # Where the SMTP client should look for mail
newmail_path:    C:\MERCURY\MAIL\~N    # Where to find the users' WinPMail mailboxes.

The entry under myname: is the name of the server.  This means the maiser and postmaster user the postmaster@bucataruserver and maiser@bucataruserver email addresses.

[Protocols]
C:\MERCURY\mercurys.dll
C:\MERCURY\mercuryc.dll
C:\MERCURY\mercuryp.dll
C:\MERCURY\mercuryd.dll
C:\MERCURY\mercuryi.dll

Looks like you are receiving you mail via MercuryD.



postmaster:    bucataru    # NetWare UIC of postmaster

This is the local username of the postmaster.  This user MUST exist in Configuration | Manage local users.


[MercuryC]
Host : shawmail.cg.shawcable.net
Failfile : C:\MERCURY\Mercury\FAILURE.MER
Poll : 30
Scratch : C:\MERCURY\scratch
ReturnLines : 15
Timeout : 30
ESMTP : 1
SMTP_Username: bucataru
SMTP_Password: **********
POP3_Auth : 0
Logfile : C:\MERCURY\Logs\MercuryC\~y-~m-~d.log
Log_Verbose : 0
Session_logging : C:\MERCURY\Sessions\MercuryC
Session_logmode : 0

Sending via shaw mail server.


[MercuryS]
Debug : 1
Logfile : C:\MERCURY\Logs\MercuryS\~y-~m-~d.log
Timeout : 30
Relay : 0
Strict_Relay : 0

You should turn off relaying even if you are only sending locally.

Allow_Illegals : 0
SMTP_Authentication : 0
Session_logging : C:\MERCURY\Sessions\MercuryS
Session_logmode : 0
Compliance_Settings : 0
Maximum_Failed_Rcpts : 4
Max_Relay_Attempts : 4
SSL_Mode : 0
ST_Blacklisting : 288
No_VRFY : 0
SMTP_ConnFlags : 0

[Domains]
shaw: shaw
shaw: shaw.ca

Really bad.  The domain shaw.ca is considered local and you'll never be able to send to anyone at that domain.  The at least should be changed to

[Domains]
shaw: shaw
shaw: local.shaw.ca

and alias all of the accounts you are receiving with the address user@shaw.net to user@local.shaw.net  Personally if you do not have a domain I would use the same domains here as you did for the myname: entry.  You must alias any address you receive though.

Might also want to go to and get one of the free domains and use that for the system.


>
> As for what I'm trying to acheive Dilbert's, I want mercury to
> download my e-mails, store them, and deliver them to my client
> computers, which has already been achieved. Later on I might add
> webmail, but for now I'm good to go. You have to understand that I
> don't even know what real data there is to offer. I'm am so new at
> this that I can barely navigate the menus. It's a miracle I got this
> far and largely due to the great support here at the pmail
> community.
>
>
> Thank you to everybody who took the time to answer my questions. You
> have all been of real help, even though some of you may have guessed
> :)
>
>

Thomas R. Stephenson!

You are THE MAN! I am up and running now! I knew I was making some noob mistake.

I was inspired to post here by this thread, http://community.pmail.com/forums/thread/7695.aspx, that I found by a google search when I first starting working on this problem. And it was you that had helped that thread's parent.

Thank you so much for your help!

Thanks Rolf... everything is up and running :)

[quote user="Peter Strömblad"]

In order for MercuryB to work you need the file mercuryb.htm in the root folder of your installation. WIthout it the first page doesn't show, and comes up blank.

If the does show a blank page, your missing the directory MLSS directly under the root path, or you're missing the files therein. To mend your system, you can unzip the m32-462.exe file and extract the MLSS directory, and all should be fine.

[/quote]

Yes, only a blank page appears.

But there ist that MLSS directory (whith all the files in it)  and the mercuryB.htm in the root directory.

Thank you for the help!

fokus

Appreciate the assists - Thank you!

 Please mark me as "Resolved" :)

-Larry

I suppose that I should have thought about this but, when I replaced all relative (to MERCURY) pathnames with full pathnames, everything worked fine.

I don't seem to need to use the Policy approach, but I will try this just to gain some familiarity.

Thank you to those assisting in getting me there.

GordonM

session log on MercuryE will show why aol.com drops the connection. My guess is that the maildrop is full.

I would setup a FORWARD file in one of the mailboxes forwarding to the other email addresses.  You have to make sure you have turned on the file based forwarding in Configuration | Mercury Core | Advanced.

It would be interesting to hear if someone is running GrayWall 1.1.0 on Win98SE without having these problems. There are some differences in the Windows API between the Win95 and WinNT generation that can cause unexpected errors.

/Rolf 

[*-)]  This was to easy to for me to find it out by myself... Thank you, it´s working and now I have a "C" in my log [:)]

Where is fine tool-, program can be also used to recover information from Microsoft Exchange ost files and/or convert them into Microsoft Outlook pst files,will be recovered and saved together with messages and objects from the corrupted *.pst file,program recover Outlook files and data from corrupted pst files of all Microsoft Outlook mail clients, from Microsoft Outlook 97 to Microsoft Outlook 2003. To save the recovered information as files with the *.pst extension, you should have the Microsoft Outlook 98 mail client or higher installed on your computer.

So, you're running MercuryD and MercuryE. Try to intercept the message via a global policy or filter rule, so you save a copy of each message before they get processed. Then you can later toss them into the queue (hold MercuryE first !!!!) to see if it's the list engine that causes this. I doubt that though. I'd much sooner suspect that something is causing packet/socket problems in your setup, and somehow MercuryE or MercuryD, or the loopback logic is messing things up.

If all else fails, I'd move Mercury to another machine, and use MercuryD and MercuryC, using hMailServer as the "smart host".

Nevertheless I'll see if I can't speed up my web-admin development a bit. Much of the foundation is already in place but I'm noway near a release.

Thanks for your reply FJR.

Using Outlook (2013) with multiple e-mail accounts only one account I can manage to have hierarchical folders. The other accounts, even creating a new account I cannot manage to create hierarchical folders.

How can I fix this?

 Mat 

One work around for this, if your ISP permits it, is to forward, at the ISP server, every arriving message to a second account while leaving the original message in place.  Not all ISPs offer this facility, but I seem to recall that GMail does.  You could then extract the mail through the Mercury POP process from one ISP account, while leaving the other one untouched.  I would have to check further about this but, in the GMail case, it might be better to use IMAP for your incoming connection.  I can't remember what all of the GMail options are.

If your ISP doesn't provide this type of forwarding facility, it may be possible to forward all messages from Mercury to a second account at your ISP.

 GordonM

Hi Peter,

[quote user="Peter Strömblad"]Hmm, never heard of their platform. Couldn't see If 9.2 is their latest build (the reference only to 2008 on their homepage). If 9.2 is their latest build I'd file a support case with them.[/quote]

 yes, its the latest client-version. I contacted them aready. They will give me some information next week.

Greetings

Asgard

ehh what? M/32 doesn't allow local usernames like user@domain.com

Sure is does in aliasing. Core then will deliver the mail using this full email address.  

If you use a local username like USER in an alias the X-Envelope-To: address will contain the local username USER.  If this account is auto forwarded then the local username USER shows up as the MAIL FROM: address and since it's not a full SMTP email address it is bounced.  I've asked David to change this to add the mail server domain if none exists but so far nothing has changed.

Thank you very much, I´m such a blind i****

I´ve searched Allow the use of "+" forms in addresses to carry user-specified data  for two days and couldn´t find it[*-)]

Again Thank you !!!

Ok,

 thanks to everyone who helped me.

i think i got the point.

Mark

Thanks so much Rolf. The fanout distribution is working fine.  I'll keep the VERP option in the back of my mind to try some other time.  For now, though everything is clicking away like it is supposed to!  Thanks again.

That looks like the MercuryE (end-to-end SMTP) console output, though. Your Internet provider is most likely blocking outgoing traffic on port 25. So unless you can convince them that you should be allowed to use port 25 you will need to switch to MercuryC and relay the mail through your Internet provider's mail server.

/Rolf