The new mailbox (the default mailbox = "my mailbox") was recreated on my laptop (same Pegasus v).
I transfer once more by copying the data to my laptop.
The new mailbox shows up but empty on Laptop's Pegasus. Only the default "new mail folder" appears. So the other data that do not appear are present in the new mailbox when I check the new mailbox's content through Explorer.
I found out what the problem was. I had set the preferences to compact folders after deleting 24000 bytes. When I increased this to 2400000 bytes, the behaviour stopped and emails clear again in a flash when I delete them from my inbox.
The 160's are simply html blanks defined in the Windows 1252 character set. The character set is selected in the Pegasus Mail menu Tools/General Settings/Advanced. There is a drop down list that selects the character set you want. If you select Rich Text when composing or replyng to Html messages, this value is important, as it tells the recipient how to display text characters. You also need to look in menu Tools/Options/Messages & Replies to make sure that Rich Text is checked, And also Tools/options/sending mail the Generate multipart should be checked.
The "Change user" function is heavily deprecated now, and will vanish from the next version onwards: the mechanics of maintaining this function are just too hard with the burgeoning features in the program. I'm fairly sure that this function is either directly or indirectly responsible for some of the more difficult to track problems in the program, especially problems with HIERARCH.PM and folder index damage.
Instead, use the -MS commandline switch to start multiple Pegasus Mail sessions for each user you have. This is much the better way of doing things.
Pegasus stores new messages as *.cnm files in the mailbox directory. Other folders (i.e. copies of sent messages) are stored in compound files + indexes.
Therefore, if you would write a filter rule that moves all new mail where subject <> "specificsubject" to a 'to be read' folder, your separate program could check for new *.cnm files that are at least 1 minute old (give the rule some time to do its work). Another option is to write a rule that appends the message to a specific file somewhere on your system. Which is best depends on how flexible your 'separate program is'.
Writing filter rules is very straightforward with Pegasus - give it a try.
I've been using, and promoting Pegasus since 1995 (using Windows - currently XP Professional SP2).
Each time an update has been made available I've updated. Problem is, although the version is listed as being what I have, the layout doesn't change and some of the features aren't available (I know this to be a fact because I've seen the layout and features available on new installations by other people). It appears as if the original installation is still controlling what I can do and not do with Pegasus.
I doubt this since I've been upgrading since running PMail for MSDOS and WinPMail v0.9 over the same setup and always have all of the features of the new system. If the Help | About Pegasus Mail shows the current setup then you'll just have to make the changes as required in Tools | Options to bring them out.
I have decided to uninstall Pegasus and re-install the latest version HOWEVER, I'm concerned that by doing so I'll loose all my address books, my folders, my signature files, etc., and etc. so I'm very hesitant to do so. Could somebody help me through this process so I don't loose what I need??
The way to do a reinstall without losing any data at all in to delete the PMail.ini, State.pmj and hierarch.pm and then re-install the program over the current version.
Having the same problem after any distribution list - mine is only 8 recipients. A new message, not to a distribution list but to 4 people, refuses to be sent. The error I get (with last digits of IP addresses and parts of e-mail addresses censored):
[*] Connection established to 195.241.79.132 >> 0055 220 ESMTP smtp-out3.tiscali.nl. NO UBE/UCE tolerated. << 0024 EHLO [192.168.123.152] >> 0067 250-smtp-out3.tiscali.nl Hello [192.168.ip.ip] [82.171.ip.ip] >> 0019 250-SIZE 57671680 >> 0016 250-PIPELINING >> 0010 250 HELP << 0054 MAIL FROM:<me@tiscali> SIZE=10751 >> 0008 250 OK << 0035 RCPT TO:<someone@hotmail.com> >> 0014 250 Accepted << 0031 RCPT TO:<someoneelse@gmail.com> >> 0014 250 Accepted << 0030 RCPT TO:<fook@gmail.com> >> 0014 250 Accepted << 0031 RCPT TO:<bar@hotmail.com> >> 0014 250 Accepted << 0006 DATA >> 0056 354 Enter message, ending with "." on a line by itself >> 0032 550 Administrative prohibition
This is saying that your server has setup some restrictions on sending. ( it might be it does not accept a message with more than x number of RCPT TO: addresses) and the only way to solve this is to either get them to relax the restriction or use a different SMTP host (like GMail) that does not restrict the access. I would recommend you talk to your ISP and ask them the same question.
[quote user="David Harris"]I've just tried this here and everything looks OK - I see normal CR/LF line endings on the message once I have copied it from inbox to local new mail. Can you give me anything more to work with? I'm happy to fix this if we can track down where it's happening.
Cheers!
-- David --
[/quote]
Attached is a ZIP file with the following files with an example:
YFST76U4.CNM - CNM file as it is on the server
7X9M3YU0.CNM - CNM file as retrieved via IMAP to the local workstation. Note the the extra <CR> on every line
TCP000D.MI, TCP000E.MI - IMAP logs on the server
TCP0001.WPM, TCP0002.WPM - the Pegasus logs (-Z 32)
The logs have been edited to x-out the login and password, but are otherwise intact.
One strange thing: I had originally tried to create this example with a much smaller message (CNM file about 1.4 K), and the headers did not get the extra <CR> although the body did get modified.
When I repeated the test with larger message (attached CNM files, about 4K) both the headers and body got modified.
If there's any more information you need, let me know.
I double checked the ip's and names didn't find any typos.
I agree with your theory that the delivery is failing because the mx resolved to the inaccessible outside address and that the system should not get to the point of trying to deliver out since the is configured as a local address.
It is equally strange that a test email - sent from the server 'send message' menu to postmaster does get delivered local to the admin user. it seems like it is only the notification/failure notices that have the bad behavior.
(Thanks again for your help on this problem).
[/quote]
Is mail mail.momjunction.com entered into Configuration | Mercury core "Internet name for this system"?
As I understand it, v1.4 is the first release to look at the identity name, and not require an identity's e-mail address. Everyone at my location is set to use the Default identity only and I have lots of things disabled (using the disable extension) or removed from the PMAIL run directory.
I am not sure if there is some setting or way to "trick" the v1.4 into applying the info to all outbound messages but you can try asking Gerard Thomas (he responds rather quickly to e-mail but hasn't been overly helpful when I've asked how to use his extension in a non-standard way). You might try a DOS-type wildcard or Pegasus-aware variable / substitution. The following are from the UDG.TXT file and may only work at runtime (not when an identity is changed) but they might be of some use:
Command substitution --------------------
Most of the entries in this screen which accept strings allow you to use special command substitution characters in the strings: these are like "escape sequences" which will cause PMail to perform some substitution at run-time. Command substitutions always begin with a tilde (~) character, and are always two characters long. The following command substitutions are recognised:
This sequence... Is replaced with this value
~c The full path to the file containing the message ~t The address to which to send this message (note: this is not necessarily the To: field) ~s The message's subject field ~f The full form of the message's "from" field ~n The sender's user name in its simplest form ~b The sender's bindery id, as a long hex integer ~8 The first 8 chars in the sender's username ~y The time and date in RFC-822 format ~d A random integer, expressed as 4 hex digits ~q Y if this message is a BCC, N otherwise ~%name% The value of the environment variable %name%. ~p The user's personal name preference ~x The name.ext ONLY of the container file (no path) ~a The directory from which PMail was run (or base directory) ~h The current user's home mailbox location ~w The current user's new mail location ~~ A single tilde character
[:$] Slightly embarrassed. The folder hierarchy structure that had gone .... that was because my husband's Pmail was open at the same time, and I didn't realise it and thought it was my own.
I did not restore anything, as it seemed it was only some of the options that had changed. At least I hope so. All seems to be well now that I set them back as they were.
?? If that fixed the problem, then you should really consider ringing your ISP and getting them to make their server generate more accurate and useful error messages. The error message that it was returning gives no useful indication to the user that authentication might be an issue.