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?
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.
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.
Perhaps it's time to move on to something else such as hpt or FMail ?
=== 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?
=== 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)^^^
=== 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 :)
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 :)
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?
CM was originally an Amiga tool. I don't think there was much 'refinement' to ensure smooth operation(s) in other OSes.
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.
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.
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)
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.
the Linux version(0.71) of Crashmail.
Why do you use an old version on Linux?
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?
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?
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!!
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!!
Sysop: | Rempala |
---|---|
Location: | Richlands, NC |
Users: | 106 |
Nodes: | 10 (0 / 10) |
Uptime: | 13:18:52 |
Calls: | 199 |
Files: | 6 |
Messages: | 110,829 |