Email Client Not Working In Tiger

[barracuda156]

I’ll keep this in mind. Cheers.

Could you please try building from https://github.com/barracuda156/macports-ports/commit/0a51b5c4b7ce0e0418455421b57b94abb7450b32

Or otherwise manually add these lines: https://github.com/OpenSMTPD/OpenSMTPD/pull/1247/files

UPD. It will be actually helpful to know if that works.

 

[B S Magnet]

Could you please try building from https://github.com/barracuda156/macports-ports/commit/0a51b5c4b7ce0e0418455421b57b94abb7450b32

Or otherwise manually add these lines: https://github.com/OpenSMTPD/OpenSMTPD/pull/1247/files

UPD. It will be actually helpful to know if that works.

Thank you.

It built successfully on the G3:

 

[barracuda156]

Thank you.

It built successfully on the G3:

View attachment 2356250

Does it actually work btw?

 

[TheShortTimer]

Does it actually work btw?

I'd also like to know too!

 

[B S Magnet]

Does it actually work btw?

I can verify the port load opensmtpd command completed successfully.

At the moment, that G3 is not set up to receive or send email, whether by a pine-like client or horde, or a GUI client like GyazMail, so beyond verifying it compiled/installed and loaded as a daemon with launchd, I haven’t test-driven its functionality as a server.

 

[VirtuallyInsane]

Hi, I've been busy.

It's been a while since I replied to the thread:

Thank you for your efforts.

To the issue:
1. What you see is not an error, it is expected behavior. You just need to do what the message advises: sudo port deactivate libunwind-headers. Then proceed with whatever.
2. Building gcc7 takes a lot of time on G4. Be ready. It is useful to do regardless of a specific port, however. Pretty much anything modern requires C/C++11-capable compilers, so it makes sense to have such installed.
3. It will take a while to get to the point of building nmail itself. I hope we get a fix for it in a few days, there is a minor issue to be addressed with it.

Yes, how is nmail now? Has the issue been fixed?

I am thinking of compiling it on my dual booted Powerbook 17" that runs Tiger and Leopard. Something happened to the 15" running Tiger (the OG of the thread)'s harddrive but I am planning to fix it up again soon.

Would you be able to share any of the relevant building tools (i.e., python, etc.) and the versions to which you have them set?

I know this is very vague (I apologize) but I used everything that was included in the package and I built it with the latest versions of each tool (I'm still a Macports beginner), but it seems like barracuda has solved your problem.

I do also have the latest version of Python installed (3.11, I think. It's for PPCMC). I wonder if that has an impact on the packages being installed at all? Or the processor speed/type? (PowerPC 7446, 7400 etc).

 

[barracuda156]

Yes, how is nmail now? Has the issue been fixed?

Yes, everything builds and should work.

 

[barracuda156]

Has anyone tried this one?

Sylpheed - 軽快で使いやすいオープンソースのメールソフト

Sylpheed - Sylpheed はシンプル、軽量かつ高機能で使いやすい、無料のメールソフトです。Sylpheed は Windows から Linux まで様々なプラットフォームに対応しています。

sylpheed.sraoss.jp

Install sylpheed on macOS with MacPorts

ports.macports.org

 

[VirtuallyInsane]

View attachment 2364363

Has anyone tried this one?

Tried it once, and it failed:

Then, I installed the suggestions:

Then I went back to try and install it, and it didn't work again:

I also tried nmail again and it didn't work.

It seems like the "m4" port is the recurring issue in both builds failing. Do you have any ideas on how to solve this/any altnernative links/builds for it?

This is running on 10.5.8 on a 1.33 GHz Powerbook G4 17" with 2GB of RAM, but I looked at the "confirmed plaforms" page and it seems to have been running on older OS X versions:

But the page was last updated in November 2004. Is m4 out of date, or something? I'm just wondering because it seems like it hasn't been worked on in a long time. Thanks.

 

[barracuda156]

Tried it once, and it failed:

View attachment 2364897

Then, I installed the suggestions:

View attachment 2364899

View attachment 2364900

View attachment 2364901

Then I went back to try and install it, and it didn't work again:

View attachment 2364902

I also tried nmail again and it didn't work.

View attachment 2364903

It seems like the "m4" port is the recurring issue in both builds failing. Do you have any ideas on how to solve this/any altnernative links/builds for it?

This is running on 10.5.8 on a 1.33 GHz Powerbook G4 17" with 2GB of RAM, but I looked at the "confirmed plaforms" page and it seems to have been running on older OS X versions:

View attachment 2364904

But the page was last updated in November 2004. Is m4 out of date, or something? I'm just wondering because it seems like it hasn't been worked on in a long time. Thanks.

Could you please try the following: https://trac.macports.org/ticket/62994#comment:96

P. S. We are aware of the issue, just no one submits the patch…

 

[barracuda156]

Another e-mail client with GUI (I have just updated it, wait a bit for the new version to land via rsync – should be 3.20.0):

claws-mail | MacPorts

ports.macports.org

Claws Mail - The user-friendly, lightweight, and fast e-mail client

Builds fine on PowerPC

 

[krrsh]

Has anyone tried this one?

Excuse me.
Sylpheed builds, runs and crashes after launch with "extension randr missing on display" message in terminal. It shows 'create mailbox' dialog at this moment.
But there is a trick. Ports has xorg. After running it and placing in dock "applications" submenu appers. Sylpheed can be run from there.
I've noticed "rebuild folder tree" is necessary for imap, otherwise it doesn't get mail.
Ports xorg is 1.20.10. Sorbet xorg = 1.4.2-apple33.
Sylpheed builds from author's source via autogen.sh (libtoolize->glibtoolize), behaviour the same.

About claws-mail. Poppler doesn't want to be build.
:debug:configure configure phase started at Wed Oct 30 12:29:52 EET 2024
:notice:configure ---> Configuring poppler
:error:configure Failed to configure poppler: Invalid value for configure.compiler:
:debug:configure Error code: NONE
:debug:configure Backtrace: Invalid value for configure.compiler:
:debug:configure while executing
:debug:configure "[ditem_key $ditem prerun] $targetname"

Thank you.

 

[barracuda156]

Excuse me.
Sylpheed builds, runs and crashes after launch with "extension randr missing on display" message in terminal. It shows 'create mailbox' dialog at this moment.
But there is a trick. Ports has xorg. After running it and placing in dock "applications" submenu appers. Sylpheed can be run from there.
I've noticed "rebuild folder tree" is necessary for imap, otherwise it doesn't get mail.
Ports xorg is 1.20.10. Sorbet xorg = 1.4.2-apple33.
Sylpheed builds from author's source via autogen.sh (libtoolize->glibtoolize), behaviour the same.

About claws-mail. Poppler doesn't want to be build.
:debug:configure configure phase started at Wed Oct 30 12:29:52 EET 2024
:notice:configure ---> Configuring poppler
:error:configure Failed to configure poppler: Invalid value for configure.compiler:
:debug:configure Error code: NONE
:debug:configure Backtrace: Invalid value for configure.compiler:
:debug:configure while executing
:debug:configure "[ditem_key $ditem prerun] $targetname"

Thank you.

poppler needs C++20 now, which means you need gcc14 (or some modern gcc). Possible solutions:

1. Follow the procedure I described to switch to using gcc14. Needs some manual work, but nothing complex.
2. Downgrade poppler to the last pre-C++20 version which can be built with gcc7 (see commit history for it in MacPorts). Keep that version in a local overlay repo.
3. Complain on Trac that poppler is broken on < 10.6 (it is a credible complaint, whoever upgraded it did not think much about consequences). In fact, there is my ticket there and with upstream. Consider writing there to express an interest in having it fixed.
4. Switch to using 10.6 ppc, forget about pains with compilers. (Needs a bit of one-time set-up, mostly streamlined.)