Martin wrote (2020-10-15):

=== Cut ===
? 15 Oct 11:30:34 [10132] start_file_transfer: c:\users\martin\mypoint\packets\c:/users/martin/desktop/t_editor.zip: Invalid argument === Cut ===

Looks to me as though Crashmail has added the path to its "packets" directory in front of the path to the file attachment but I can't figure out why it's done that. Ideas anyone?

Which version of Crashmail are you using?

The first part is a path with backslashes, the second part with forward slashes. Maybe CMcannot handle both styles?

I never tested file attachments with CM, but for mails it works fine on Linux (Crashmail II 1.7)

---
* Origin: (2:280/464.47)

Hello Oli!

*** Saturday 17.10.20 at 18:06, Oli wrote to Martin Foster:

=== Cut ===
? 15 Oct 11:30:34 [10132] start_file_transfer:
c:\users\martin\mypoint\packets\c:/users/martin/desktop/t_editor.zip:
Invalid argument === Cut ===

Looks to me as though Crashmail has added the path to its "packets"
directory in front of the path to the file attachment but I can't figure
out why it's done that. Ideas anyone?

Which version of Crashmail are you using?

I'm using v0.7(Win32) but hang on a minute, I could have sworn that I
was using v0.71. I've just upgraded to v0.71 and I'll do some tests,
stay tooooned :)

The first part is a path with backslashes, the second part with forward slashes. Maybe CMcannot handle both styles?

Yes, I noticed the back/forward slashes myself, which I thought was a
bit odd.

I never tested file attachments with CM, but for mails it works fine on Linux (Crashmail II 1.7)

^^^
Where did you get that version from?

Regards,
Martin

--- OpenXP 5.0.47
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hi! Martin,

On 20 Oct 20 09:03, you wrote to me:

CM was originally an Amiga tool. I don't think there was much
'refinement' to ensure smooth operation(s) in other OSes.

After doing a bit of poking around, I've discovered that every text
file which CM creates/updates has Unix line endings, apart from the
*.jdt files in my JAM messagebase, which have Mac line endings. I
don't see a single text file anywhere which CM has created/updated
which has DOS line endings. So yes, I tend to agree with your
thoughts.

Version 0.71/Linux: Readme.txt... Introduction, line two (excluding underline), word six.

Cheers,
Paul.

... Broken pencils are pointless.
--- GoldED+/LNX 1.1.5-b20130515
* Origin: Quinn's Rock - Live from Paul's Xubuntu desktop! (3:640/1384)

Martin wrote (2021-08-05):

Since posting the above message, I've done a complete changeover to Linux and outbound file attaches work perfectly in the Linux version(0.71) of Crashmail. So, this is obviously a problem specific to the Windows version.

Why do you use an old version on Linux?

---
* Origin: . (2:280/464.47)

the Linux version(0.71) of Crashmail.

Why do you use an old version on Linux?

Ahem... That's the Crashmail version. Or did you see something else in his posting?


..

--- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
* Origin: news://eljaco.se (2:203/2)

Björn wrote (2021-08-06):

the Linux version(0.71) of Crashmail.

Why do you use an old version on Linux?

Ahem... That's the Crashmail version. Or did you see something else
in his posting?

Crashmail 1.7 compiles fine on Linux. Why use an older version?

https://github.com/ftnapps/crashmail

---
* Origin: . (2:280/464.47)

Hello Oli!

*** Thursday August 05 2021 10:59, you wrote to me:

Martin wrote (2021-08-05):

Since posting the above message, I've done a complete changeover
to Linux and outbound file attaches work perfectly in the Linux
version(0.71) of Crashmail. So, this is obviously a problem
specific to the Windows version.

Why do you use an old version on Linux?

Because 0.71 was the last release which included pre-compiled Linux binaries and I'm unable to build my own, not even 0.71!!

Here's what happens when I try to build 0.71 .....

=== Cut ===
[martin@sgc src]$
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile.linux:82: ../bin/crashmail] Error 1
make[1]: Leaving directory '/home/martin/Projects/crashmail/crashmail-0.71/src' make: *** [Makefile:16: linux] Error 2
[martin@sgc src]$
=== Cut ===

I get similar errors when trying to build *any* version and I don't have the necessary knowledge to fix the issues :-((

Regards,
Martin

--- GoldED+/LNX 1.1.5-b20180707
* Origin: Bitz-Box - Bradford - UK (2:250/1.333)

Hi! Martin,

On 06 Aug 2021, Martin Foster said the following...

Why do you use an old version on Linux?

Because 0.71 was the last release which included pre-compiled Linux binaries and I'm unable to build my own, not even 0.71!!

I have made edits and built my own binaries on an old Linux (an
old Puppy Linux [2.6.something] with dev apps installed). Hunt
around.

If you don't turn anything up, I'm happy to do a build or three for you.
Send netmail.

Cheers,
Paul.

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/32)
* Origin: Quinn's Rock - stuck in a Linux VM, again! (3:640/1384)

Martin wrote (2021-08-06):

Since posting the above message, I've done a complete changeover
to Linux and outbound file attaches work perfectly in the Linux
version(0.71) of Crashmail. So, this is obviously a problem
specific to the Windows version.

Why do you use an old version on Linux?

Because 0.71 was the last release which included pre-compiled Linux binaries and I'm unable to build my own, not even 0.71!!

Okay. For some reason I didn't expect that an old static binary still works on a recent Linux install. I just assumed you build Crashmail from sources. I never used any Crashmail II version before 1.7, so I was curious why people stick to the old version.

CM 1.7 seems to compile with Zig too (ziglang.org). Maybe that makes it possible to easily cross-compile for different platforms.

---
* Origin: . (2:280/464.47)