Thomas,

Wonderful - it works - thank you very much.
 

There is no spec for the hierarch.pm, it's not required since yuor not supposed to be working with it.  ;-)

[quote user="jbrowne"]

thanks Thomas.

appreciate your quick response.

does this mean that even a Pegasus xtension could not do it?

[/quote]

I would suspect that the only way an extension could do this is to create a tool to add the attachments and I'm not all sure that would be possible.  Most of the file operations are done with windows calls but the actual attachment is not added until you hit the send button.  You could create a User Defined Gateway to do this sort of process and then build you own program to text the total size of the PMX file that was created.  Really all you could do there though is to delete the PMX file and popup some sort of warning.  Way, way more trouble than it's worth.

On a right click, I see the same menu as Thomas.

I would install the Pegasus Mail program files onto the C: drive of the terminal server and then simply copy the PMAIL.CFG file from a user's PC to the terminal server.  They should all be the same, namely pointing to U:\PMAIL\MAIL. Since U: is a mapped drive that is different for each user (e.g. ), it will work perfectly fine as a single-user standalone environment to Pegasus Mail.  No other mailboxes will be viewable to the user in Pegasus Mail.  In setting it up like this, you should confirm that the new mail directory path and home mailbox path are listed in PMAIL.CFG as: U:\PMAIL\MAIL

If needed, you can use the PCONFIG.EXE utility that ships with the PMAIL/DOS product to change the paths as required.  Make sure there is not a "~8" or "~n" at the end of the paths.

[quote user="GSIB"]Thanks.  I am using Netware.   I add users with the PMail Config (P:\Pmail\nconfig.exe).   I have checked user settings, but see no way to change the name.
[/quote]

I do not do NDS.  I use bindery and so I use syscon.exe to change the username.  I just hit F3 when viewing the username to change it.  I suspect that there is something similar in NDS.  

I cannot even fully decode what you have provided using a Bas64 decoder.

thanks,

you are right, I found my first e-mail still sitting in the "queued-mail" - list, which can be reached under file/review queued mail ....

I don't have any folder for outgoing mail - should there be any?

finally: problem solved

Hi Paul,

 The problem I have is this is for a university project and so I really need to be looking to do it as a Daemon that I've written myself in order to gain academic credit.

 Since Thomas' last post regarding the QDF and QCF files I performed the following experiment:

 1.) I took my .dll and .ini file out and sent a message. I performed as it should and was successfully received by the local user and could be viewed in Pegasus. The content of the QCF files was:

 ST: R 000000000000 00 000001 000000 000000
FR:
DF: MG000002.QDF
FL: 0         
OS: 080423161112
BA: ali
ES: R 080423161112
RI: 000.000.000.000 000.000.000.000 000.000.000.000 000.000.000.000
DI: --------.---
EA:

2.) After this I added my .dll and .ini file back in and restarted Mercury. I sent the same message but it was not successfully delievered to the local user. The content of the QDF file was identical (except for time stamps obviously) but the QCF file was different to the run previous:

ST: R 000000000000 05 000001 000000 000000
FR:
DF: MG000001.QDF
FL: 0         
OS: 080423160045
BA: ali
ES: R 080423160045
RI: 000.000.000.000 000.000.000.000 000.000.000.000 000.000.000.000
DI: --------.---
EA:

Do any differences in the QCF files indicate why there would be an error in delivering to local users?

BIG HUGS FOR YOU!  Funny how if you never use something you forget that it is even there.  Thanks. I suppose I should go back and "fix" the pconfig file ...

 Um ....not getting it to work ... does Pegasus Mail need to be on the root of the removable drive?  Here is the current location of mine:

F:\_stored\PMail\Programs\winpm-32.exe

 Tried it both leaving the config file ..\mail\~8 and editing back to the original c:\pmail\mail\~8

I'll look to see if I need to use some other command line options as well.
 

 The identities were there when I shut down one night, the next morning they had evaporated.

The pmail.ini file was lost and WinPMail built a new one.

I had an old .ini saved, but this did not resurrect the situation, I

note that the first section was as if this was a standalone

installation running with own pop/smtp whereas I have a mercury server

installation. My thought is that if I do a correct reinstall, then I

can cut and paste the relevant identity sections out of the old into

the new.

Actually all you really have to do is edit  the file to have it point to the correct home and new mail directory to get this to work.

Move all of the *.CNM files out of the new mail directory and try again.  It should now open normally.  You can then put the messages back one at a time until you find the problem message.  

It's probaby going to be a really large message.  If you are using content control then I'd recommend that you set a limit on the message size so you are not scanning these large files with encoded attachments.

1.    Use  Tools | Spam and content controls | Content control...

2.    Select and edit the control definition

3.    Select the "Message tests" tab.

4.    Enter 8000 in "Check at most this many bytes in each message"

Could you forward one of those voicemail messages to me at support@tstephenson.com for analysis?  I would like a copy of the cnm file from the new mail directory zipped if possible.

Thanks, Thomas!!  I fiddled around with it and found I needed to right-click the inbox, then click "Folder Options" to get to the header and body cache CLEAR buttons.  When I did this, I went back out and clicked the messages and VOILA! I could see the from and to addresses in the message, and I can see the contents of the file attachments.

Man, my IT guy about had a cow when I said it was fixed (but then I let him see your E-mail).[:D]

Thanks many times over!! 

Thanks Erik,

I have just come back from a 3 day holiday to find 143 spam messages and 4 real messages.  Still, it only took about 60 seconds to:

1.         Mark all delete (highlight first and last message while holding down Shift)
2.         Scan manually and individually overmark the real messages as download and delete
3          Make it so.

Thanks to the spammers complete lack of imagination, the spam is easy to spot, with a bit of practice, and if you start out with the default instruction of delete, then over-right as required, it is very quick - and I think I'm better at it than any form of computer filter I've tried for the simple reason that there are never any false positives.

What I reallly need is something that deletes them on the server as soon as they are received, so that after a three week holiday I do not find 1000 emails to sift, nor that something important has been lost because there was no room left in the inbox.  My ISP is supposed to have one, but does it work - nah !

But for the moment, after experimenting with filters at all levels, I'm sticking to my DIY filter.

That said, your suggestions may be useful to those who do like to use the filters - I'm opting out of the discussion from now on.

Regards,

Philip Jones

check yout quede mail. You may have a bad file there.

Really strange indications.  First thing I would do in use File | Review queued mail and verify that that large message is not still in the queue.

Problem solved, thank you for your help.

It was indeed a question of user rights in "Outgoing mail path" - security setting were allright but those sharing permission were read only -argh!

Thank you for pointing me into right direction - I was somewhat confused about where Pegasus was writing the 101-files, of some mysterious reason I was looking for them under pmail-path not mercury.

New server is up and running.

---

What is the meaning of that last setting "Force all mail through?" ? Where else could the mail possibly go than through Mercury?

[quote user="Paolo_DF"]

Hi all.

I started using Mercury in a new way (to me, at least).

This is what I did:

1. retrieve messages with Mercury from email account 1@...

2. use popfile daemon in order to classify messages

3. deliver to local user 1

4. apply filter in order to forward only non-spam messages to email address 2@...

This way, I use my old email address 1@... because everyone knows it, but receive all my mail on email address 2@... because it is a fresh address.

Now, of course, there is this local user 1 mailbox that *never* get any access, so it starts filling up.

And here is the question: how may I delete messages in local mailbox 1 since I never access it and only use it as a buffer?

Thank you all for your reply. 

[/quote]

If you are never going to look at these then why not simply use a Mercury/32 filter to delete all of the messages marked  spam by POPfileD before they are delivered to the user.  This may require yuo to leave the local user blank in the MercuryD setup and alias this mail to user@local.domain so that core have a chance to filter them.

 Personally though, I use the MOVE action to move all of these messages

to a spam user account so I can check for false positives.
 

Right now that is the only possible way to do this in Pegasus Mail.  You can enter a fixed Bcc: address however these will not be a copy self type message so you will not be able to send use the right click "Resend this message"