Community Discussions and Support
Pegasus on linux server

Hello, Thomas,

 As I walked the dog in the rain the missing piece of the jigsaw puzzle popped (excuse the pun) into place. I _knew_ that you were writing on it and rushed home but you beat me to it.

 Not having Pegasus here on this old m/c I may be wrong in the name, but when you set up Pegasus clients to connecting to the server I think using pconfig (?) you can set the path & extension to match the new mail file location (I need to screw the server back together before I can say what that is) which by default is .CNM but can be set otherwise. So no need to change the new mail extension to suit, Pegasus allows you to set up server access to suit

I wasn't planning on having a GUI server, the Ubuntu standard server version is command line only. Still, I will make a plan to try at least Pegasus under Wine. Expect me back on that, but not for a while until other things have been cleared.

Thanks so much Thomas.

Anne

 

<p>Hello, Thomas,</p><p> As I walked the dog in the rain the missing piece of the jigsaw puzzle popped (excuse the pun) into place. I _knew_ that you were writing on it and rushed home but you beat me to it.</p><p> Not having Pegasus here on this old m/c I may be wrong in the name, but when you set up Pegasus clients to connecting to the server I think using pconfig (?) you can set the path & extension to match the new mail file location (I need to screw the server back together before I can say what that is) which by default is .CNM but can be set otherwise. So no need to change the new mail extension to suit, Pegasus allows you to set up server access to suit </p><p>I wasn't planning on having a GUI server, the Ubuntu standard server version is command line only. Still, I will make a plan to try at least Pegasus under Wine. Expect me back on that, but not for a while until other things have been cleared.</p><p>Thanks so much Thomas. </p><p>Anne  </p>

Hi,

 I am converting our main server to a linux one. I was

wondering

if there is any way of retaining the normal existing pegasus directory

structure, and if so how do you get the new mail into it in a Pegasus

readable way.

 I now have over 2000 folders for the main user alone and I

would like to retain the existing emails and directory structure.


Without elaborating and confusing the issue as is my normal way, that

is it. Since I can't be the

only one to  be on this path, what is the recommended overall approach to handle this issue?


Thanks

Anne

<p>Hi, </p> <p> I am converting our main server to a linux one. I was wondering if there is any way of retaining the normal existing pegasus directory structure, and if so how do you get the new mail into it in a Pegasus readable way. </p> <p> I now have over 2000 folders for the main user alone and I would like to retain the existing emails and directory structure. Without elaborating and confusing the issue as is my normal way, that is it. Since I can't be the only one to  be on this path, what is the recommended overall approach to handle this issue? Thanks</p> Anne

 I am converting our main server to a linux one. I was

wondering

if there is any way of retaining the normal existing pegasus directory

structure, and if so how do you get the new mail into it in a Pegasus

readable way.

You have to make the Linux drive available as a drive for the PC but Mercury/32 runs quite well with Wine of the Linux host.  The only problems I find are:

1.  When running as non-root the low ports are not available.  That means you must do something to route port 25 to a port like 8025 on the Linux system.

2.  The STARTTLS and SLL does not work.

That said I've been connecting to a Linux host via IMAP4 on port 8143 for a few years now with little or no problems.  Mercury/32 is running on a Ubuntu workstation with Wine.  If also go PMail running on the Linux host but I'm not connecting to the Linux host from a Windows system to run the program.  FWIW, I know little or nothing about the internals of Linux or Ubuntu so anyone with real experience with Linux should be able to do a lot better than I.  ;-)

 

 

 

<blockquote> I am converting our main server to a linux one. I was wondering if there is any way of retaining the normal existing pegasus directory structure, and if so how do you get the new mail into it in a Pegasus readable way.</blockquote><p>You have to make the Linux drive available as a drive for the PC but Mercury/32 runs quite well with Wine of the Linux host.  The only problems I find are:</p><p>1.  When running as non-root the low ports are not available.  That means you must do something to route port 25 to a port like 8025 on the Linux system.</p><p>2.  The STARTTLS and SLL does not work.</p><p>That said I've been connecting to a Linux host via IMAP4 on port 8143 for a few years now with little or no problems.  Mercury/32 is running on a Ubuntu workstation with Wine.  If also go PMail running on the Linux host but I'm not connecting to the Linux host from a Windows system to run the program.  FWIW, I know little or nothing about the internals of Linux or Ubuntu so anyone with real experience with Linux should be able to do a lot better than I.  ;-) </p><p> </p><p> </p><p>  </p>

Hello, Thomas,

 Thank you for your reply. I must say that sounds an original solution but not one that I can follow at the moment.

What

I really need is a native linux popper that will dump new mail into the

pegasus folder with a .CNM extension. Then Pegasus can access that

folder via a Samba share on the server and conduct business as usual.

My concern is to not have to do something special at this stage with

the existing Pegasus directory structure.



I don't see that defining the extension of a new mail file is a

configurable option with any linux utility that I have looked at up to

the present. I assume, perhaps naively, that a file downloaded by the

pop3 protocol is the same whether Mercury or mpop does it, and that the

saved new email file is unchanged in structure whether it has a .CNM

extension or something else. Why the pop3 delivery has to be restricted

to mbox or maildir format I haven't worked out yet, Maildir is one file

per email anyway.

I am missing some vital component in my

understanding of the issue. There surely should be a simple way to

retain full Pegaus operability with the files in the typical

/pmail/mail/user structure on a linux server, and that includes getting

the new mails in a format that Pegaus can read. Sure, IMAP would be

fine, but what about years of email all stacked up that I need to

access. I don't want to archive them or go to some special machine so

that I can access info a dozen times a day.

 

I don't see that I can be the first person in this bind. If i find a solution I'll follow up on this thread.

 best regards

Anne



 

<p>Hello, Thomas,</p><p> Thank you for your reply. I must say that sounds an original solution but not one that I can follow at the moment.</p><p>What I really need is a native linux popper that will dump new mail into the pegasus folder with a .CNM extension. Then Pegasus can access that folder via a Samba share on the server and conduct business as usual. My concern is to not have to do something special at this stage with the existing Pegasus directory structure.</p><p> I don't see that defining the extension of a new mail file is a configurable option with any linux utility that I have looked at up to the present. I assume, perhaps naively, that a file downloaded by the pop3 protocol is the same whether Mercury or mpop does it, and that the saved new email file is unchanged in structure whether it has a .CNM extension or something else. Why the pop3 delivery has to be restricted to mbox or maildir format I haven't worked out yet, Maildir is one file per email anyway.</p><p>I am missing some vital component in my understanding of the issue. There surely should be a simple way to retain full Pegaus operability with the files in the typical /pmail/mail/user structure on a linux server, and that includes getting the new mails in a format that Pegaus can read. Sure, IMAP would be fine, but what about years of email all stacked up that I need to access. I don't want to archive them or go to some special machine so that I can access info a dozen times a day.  </p><p>I don't see that I can be the first person in this bind. If i find a solution I'll follow up on this thread.</p><p> best regards</p><p>Anne</p><p>  </p>

[quote user="Anne Wainwright"]Hello, Thomas,

 Thank you for your reply. I must say that sounds an original solution but not one that I can follow at the moment.

What

I really need is a native linux popper that will dump new mail into the Pegasus Mail folder with a .CNM extension. Then Pegasus can access that

folder via a Samba share on the server and conduct business as usual.

My concern is to not have to do something special at this stage with

the existing Pegasus directory structure.

Actually Mercvury/32 and Wine would make that a piece of cake.

I don't see that defining the extension of a new mail file is a

configurable option with any linux utility that I have looked at up to

the present. I assume, perhaps naively, that a file downloaded by the

pop3 protocol is the same whether Mercury or mpop does it, and that the

saved new email file is unchanged in structure whether it has a .CNM

extension or something else. Why the pop3 delivery has to be restricted

to mbox or maildir format I haven't worked out yet, Maildir is one file

per email anyway.

A CNM file is simply an RFC 2822 message body.  If you use an 8.3 file name with the CNM file extension it becomes a PMail new mail message.

I am missing some vital component in my

understanding of the issue. There surely should be a simple way to

retain full Pegaus operability with the files in the typical

/pmail/mail/user structure on a linux server, and that includes getting

the new mails in a format that Pegaus can read. Sure, IMAP would be

fine, but what about years of email all stacked up that I need to

access. I don't want to archive them or go to some special machine so

that I can access info a dozen times a day.

 

You can simply copy the existing to the Samba share to get PMail running.  You can also have Mercury/32 pointing at the same mail directory structure from either the Linux server or a Win32 system to get the mail into the PMail mailboxes. 

I don't see that I can be the first person in this bind. If i find a solution I'll follow up on this thread.

There are a number of people running Mercury/32 on a Linux host and PMail on a Samba share.

 best regards

Anne[/quote]

<blockquote>[quote user="Anne Wainwright"]Hello, Thomas,<p> Thank you for your reply. I must say that sounds an original solution but not one that I can follow at the moment.</p><p>What I really need is a native linux popper that will dump new mail into the Pegasus Mail folder with a .CNM extension. Then Pegasus can access that folder via a Samba share on the server and conduct business as usual. My concern is to not have to do something special at this stage with the existing Pegasus directory structure.</p></blockquote><p>Actually Mercvury/32 and Wine would make that a piece of cake. </p><blockquote> I don't see that defining the extension of a new mail file is a configurable option with any linux utility that I have looked at up to the present. I assume, perhaps naively, that a file downloaded by the pop3 protocol is the same whether Mercury or mpop does it, and that the saved new email file is unchanged in structure whether it has a .CNM extension or something else. Why the pop3 delivery has to be restricted to mbox or maildir format I haven't worked out yet, Maildir is one file per email anyway.</blockquote>A CNM file is simply an RFC 2822 message body.  If you use an 8.3 file name with the CNM file extension it becomes a PMail new mail message. <blockquote><p>I am missing some vital component in my understanding of the issue. There surely should be a simple way to retain full Pegaus operability with the files in the typical /pmail/mail/user structure on a linux server, and that includes getting the new mails in a format that Pegaus can read. Sure, IMAP would be fine, but what about years of email all stacked up that I need to access. I don't want to archive them or go to some special machine so that I can access info a dozen times a day. </p></blockquote><p>  You can simply copy the existing to the Samba share to get PMail running.  You can also have Mercury/32 pointing at the same mail directory structure from either the Linux server or a Win32 system to get the mail into the PMail mailboxes.  </p><blockquote><p>I don't see that I can be the first person in this bind. If i find a solution I'll follow up on this thread.</p></blockquote><p>There are a number of people running Mercury/32 on a Linux host and PMail on a Samba share. </p><blockquote><p> best regards</p><p>Anne[/quote]</p></blockquote>
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft