Hello All!

I'm having a problem with Crashmail not processing outbound file attaches correctly. Here's a one-line snippet from my BinkD logfile:

=== 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?

Regards,
Martin

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hi! Martin,

On 15 Oct 20 12:50, you wrote to All:

I'm having a problem with Crashmail not processing outbound file
attaches correctly. Here's a one-line snippet from my BinkD logfile:

Ideas anyone?

Use a binkD /crash/ 'filebox', even temporarily. Refer to the file in your mail as "forwarded separately".

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

Cheers,
Paul.

... Will this never-ending series of PLEASURABLE EVENTS never cease?
--- GoldED+/LNX 1.1.5-b20130515
* Origin: Quinn's Rock - Live from Paul's Xubuntu desktop! (3:640/1384)

Hello Paul!

*** Thursday 15.10.20 at 23:04, Paul Quinn wrote to Martin Foster:

I'm having a problem with Crashmail not processing outbound file
attaches correctly. Here's a one-line snippet from my BinkD logfile:

Ideas anyone?

Use a binkD /crash/ 'filebox', even temporarily. Refer to the file in your mail as "forwarded separately".

Thanks, I'll have a look at that but in the meantime, I'm using a "quick
'n dirty" workaround by manually deleting the 'rogue' stuff from in front
of the path to the filename in the .clo file.

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

Perhaps it's time to move on to something else such as hpt or FMail ?

Regards,
Martin

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

Hi! Martin,

On 17 Oct 2020, Martin Foster said the following...

Thanks, I'll have a look at that but in the meantime, I'm using a "quick 'n dirty" workaround by manually deleting the 'rogue' stuff from in
front of the path to the filename in the .clo file.

It is a shame. I later, again, went through the dox and some captures but couldn't spot why CM did what it did to you.

Perhaps it's time to move on to something else such as hpt or FMail ?

I feel for you. CM was my all-time favourite following 20-odd years with FastEcho. In my case I found with the version 0.71 distribution Linux executables, and my own local compiled versions, that there is an inherent hiccup in the inter-zonal operation of CM. Like FastEcho, CM has a native 'zonegate' mode that cannot be turned off.

I recommend FMail, in a Windows environment. On my main node I'm doing FMail in Linux. (It's a pain for the present as it requires a Windows
configurator program.) It is a good old-style tosser, which shows its age in some aspects. E.g. be prepard for a Hudson base requirement.

Good luck.

Cheers,
Paul.

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/32)
* Origin: Paul's Pile of Polygonal Pebbles (3:640/1138)

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)

Hello Oli!

*** Sunday 18.10.20 at 09:39, Martin Foster wrote to Oli:

=== 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 :)

Tests done but the problem remains :(

I notice that the source is included in the distribution archive,
perhaps some kind friendly programmer could have a look at it :))

Regards,
Martin

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

Martin wrote (2020-10-18):

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 :)

0.71 is from 2004.

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?

https://github.com/ftnapps/crashmail

But I'm not aware of any recent binary for Windows and don't know if the recent version in github still compiles on Windows. I also don't know how much has changed between 0.71 and 1.7. For Windows I think FMail might be the better supported option.

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

Hello Paul!

*** Thursday October 15 2020 23:04, you wrote to me:

[snip]

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.

Regards,
Martin

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello Oli!

*** Sunday October 18 2020 13:10, you wrote to me:

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 :)

0.71 is from 2004.

Yes it is but after upgrading to 0.71, it's fixed another issue I was having where Crashmail would lock up after exporting mail.

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?

https://github.com/ftnapps/crashmail

Ah yes, I'd forgotten about that, thanks for reminding me.

But I'm not aware of any recent binary for Windows and don't know if
the recent version in github still compiles on Windows.

The last time I tried to compile a Windows version, it wouldn't compile. See my ticket #10 dated 07.10.2018. Also see my ticket #9 dated 11.03.2018. Neither of them have had a response, so it looks to me as though the project is a bit of a "dead duck" :(

Regards,
Martin

--- GoldED+/W32-MSVC 1.1.5-b20180707
* 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)

Hello All!

Thursday October 15 2020 12:50, I wrote to you:

I'm having a problem with Crashmail not processing outbound file
attaches correctly. Here's a one-line snippet from my BinkD logfile:

=== 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?

Regards,
Martin

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Update .....

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.

Just thought I'd better mention it :)

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

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)