Home | Forums | Submit   Haiku Generator | Quotable JLG | The Icon Tarot 

Interview: Kenny Carruthers

Filed under the:  department.
Posted by:Ryan on Tuesday, 05 Dec, 2000 @ 2:32 AM

Recently BeGroovy reporters Scar and Technix did what can only be described as “bombarding” Kenny Carruthers with questions. After the resulting rubble was sorted through, we ended up with a rather large 6 page interview on everything from Postmaster 2.0, to Be Inc, to BeIA, to his stint at Apple. Party on.

Due to the conversational nature of the interview, colors have been employed to help you keep people seperate. Technix is identified in red, Scar in blue, myself in green and our guest of honor, Kenny Carruthers, is all the indented text. If you have any further questions, please ask them in the comments section. Hopefully Kenny will monitor and answer them. If not, we will see if we cant get them answered for you at a later date.

NOTE: This is currently listed under the Forum News category cause we dont have an interview category and this icon looks cool. when we develop a new icon and category for this article, we will move it and remove this note.

Technix : I want to thank you, Kenny, on behalf of the BeOS community at large and
regular users of BeGroovy, for taking the time out of your busy schedule
and answering some of our readers’ many questions.

Scar : Kenny, first off may I say that Postmaster 1.1.1 is an exceptional
product. I use it on a daily basis at home and enjoy using it immensely.

Thanks for the kind words. It’s great to hear that people
are using and enjoying Postmaster, developers like that
type of feedback… ;)

Scar : How is the development of Postmaster 2.0 progressing and how would you
compare it to Postmaster 1.1.1?

The development of Postmaster 2.0 is coming along slowly. With the current
work being done on BeIA and the previous problems with Apple, I simply
have not been able been able to work on 2.0 as much as I would have liked.
However, I’m hoping that that’s going to change in the coming weeks. Postmaster
1.0 was written predominantly while I was in college, and I had a lot more
spare time back then, then I currently do know.

Technix : How soon is 2.0 expected to be out, with your busy schedule and
commitments to Be Inc.?

It’s very difficult for me to even speculate when 2.0 might be coming out.
Several months ago, I had hoped that it would have been out sometime around November,
which would have represented Postmaster’s one year anniversary, but I unfortunately
will not be achieving that goal. For those that have followed my postings on the
Postmaster web site, you know that there was a period of time back in the spring and summer
when I was working for Apple and could not work on Postmaster. Since my return to Be this past August,
I’m now at least able to continue to work on Postmaster.
However, (and it might not look like it from the outside world), we
are extremely busy here working on BeIA. Over the past month or so I simply have
not been able to allocate any of my time to Postmaster. As a result 2.0 is definitely
“behind schedule”, if there ever was one. I’m hoping that I’ll be able to work on
Postmaster again starting around mid-December. I’d definitely like to spend some
time over the Christmas holidays working on it. As a result, I’d say that in
computer industry jargon Postmaster 2.0 is slated for late Q1 2001.

Scar : From what we’ve read, Postmaster two is a major step forward from
Postmaster 1, is it a total rewrite? or have you been able to re-use a lot
of the Postmaster 1 code?

The best analogy is that of comparing it to renovating a house. I basically
gutted the entire place, left the roof and walls, and I’m redoing everything
else. Many of the rooms will look the same when they’re done, but they’ll be
made from much better materials. If anyone out there has done any home
renovation, then you know that it always takes a lot longer than you anticipated.

Technix : What new features will there be in 2.0?

Well, the biggest feature that keeps getting mentioned is IMAP. That will probably be the one
that get’s most peoples attention. However, 2.0 represents almost a complete rewrite so just about
everything should be either faster, more efficient or more stable then in 1.0. With the release of
OpenTracker, I’m spending some time incorporating some ideas from the Tracker into Postmaster, which
should dramatically speed things up (like loading a mailbox in the list view). I’m also planning on
completely redesigning all the settings panels, because frankly the tabbed interface is showing it’s
flaws. (i.e.: I can’t make it as “live” as I would like it to be.) Everyone’s favorite window, the status
window, should also get a new life in 2.0. I haven’t completely decided how it’s going to be implemented,
but I’m leaning towards the Outlook model of only showing it when the user requests it. I’ve finished
the re-write on the POP and SMTP network code and I can say that performance for sending and receiving
large messages has increased significantly. (I’ve done some overnight stress testing with 750 megabyte
e-mails and the new code is able to handle it just fine whereas the 1.0 code would simply crash.) So I’d
say that as a whole it will be much better, with two or three significant new features.

Nutcase : What new features are in the new mail daemon of postmaster? You
have mentioned The hide-able status window, and multiple accounts. Are
there other aspects? How closely will it function to the e-mail daemon
included with BeOS? Will it have a deskbar replicant? Will it operate
independent of PostMasters GUI?

I’m still undecided as to whether or not the new Postmaster mail
daemon will be part of Postmaster or instead run as a standalone daemon (or both).
There are pro’s and con’s to each. I’m currently testing it with a simple wrapper daemon so
I know that it can properly function in as a daemon, but I’m not so sure
I like to idea of having it completely separate from Postmaster. More
than likely, it will be part of Postmaster like in 1.0, that’s the direction
I’m leaning. There aren’t really any new features in it, more like it just
works properly now. In particular it’s much faster and sending and receiving
mail, properly handles messages that are left on the server (i.e.: no more
duplicate messages), should better respond to being “Stopped”, should not be
nearly as intrusive or annoying….etc… It’s possible there will be a deskbar
replicant for Postmaster, but I haven’t really looked into that yet.
That was a pretty popular feature request from 1.0 and even something that
I’d like so it’s pretty high on my feature list. Quite simply, the new mail
daemon is just better in all respects. The code was completely re-
written, is now much cleaner and hopefully much more stable. Which is pretty much
the theme for 2.0 as a whole.

Technix : Will support for Exchange Servers ever be in a release of PostMaster?

I highly doubt it. I’ve never looked into this so I don’t even know what
is required to support them. In any event, I’m focusing my energy on making improvements
to the POP and SMTP code while adding support for IMAP.

Technix : Will there be HTML support in 2.0?

There certainly will not be support for HTML based messages in 2.0. Supporting HTML
based messages is a pretty big undertaking and essentially requires that you either write your own
HTML rendering engine, or use someone else’s. Anyone who has attempted to write their own rendering
engine understands how large and complicated such a task is. For me, it’s way beyond the scope of
Postmaster. I’m certainly looking into ways that I can better handle HTML mail though. I’m thinking
that I might do some rudimentary parsing to at least eliminate the tags and to try and present the
message in a readable fashion, but if the message contains tables, then this solution would fall short.
Using Netpositive is a possibility, but it has the problems of being a completely different application
that doesn’t really understand how to handle mail. There’s no good solution for handling HTML based
messages under BeOS and I know that Postmaster 2.0 won’t be able to address this shortcoming, sorry.

Technix : A favorite feature that many are requesting is ‘Autosave’. What mechanisms
have you put into place to deal with file corruption, security, and email archiving that
will make it more robust to deal with these issues?

Implementing something like ‘autosave’ is a feature that I’m most definitely
considering. However, before I can do that, I need to significantly improve the code
that handles encoding and decoding of messages. In particular, Postmaster needs to
be able to properly decode an already encoded message, edit it, then re-assemble
it for delivery, this is currently not possible. Whether ‘autosave’ will be apart
of 2.0 or not I don’t know at this time. As for the other three issues, file
corruption, security and archiving, I’m not really addressing any of those issues
with Postmaster. Email archiving can already be done by simply using the included
ZipOMatic Tracker add-on, so I don’t really see a reason why Postmaster should have
it’s own archiving functionality. Security should be done at the system level, not
at the application level. I really don’t think it makes sense for an application
to implement security if the OS itself has no enforcement of permissions. (Though, I
suppose an application could provide per file encryption, but that’s definitely
beyond the scope of Postmaster.)

Technix : Will there be any sort of plug-in architecture that will allow third party add-ons,
such as spell checker, md5, language translation?

I doubt it. I’ve long wanted to implement a full plug-in architecture for third
parties but I’ve just had to draw the line for features in 2.0 and this is something that
got cut.

Nutcase : Would this preclude the possibility of PGP support in postmaster
then? It would be nice to have a transparent way of using it on the
user end.

Well, PGP can be supported without direct support for third-party
add-ons in Postmaster. I can always “special-case” it and support it natively
within Postmaster. (Not sure on the licenses though…) I’ve had several
people express interest in seeing PGP support in Postmaster and while I’d like
to add it, I don’t see it happening for 2.0.

Technix : Will there be a new ‘look & feel’ to the program?

The look and feel will remain the same. I’m making refinements here and there, but
2.0 should at least feel like 1.0 when you’re using it.

Technix : The preferences area (version 1.1.1) appears a little funky, to say the least. How
much design work will you be putting into the new preferences area?

It is my intention that the Preference/Settings area will be completely redesigned
for 2.0. In particular the panels will probably be pulled out of the tabbed interface and
put in individual windows. They will also be much more live and many of the panels will be
more user friendly.

Technix : Have you discussed design and user interface issues with other developers? Would
you be interested in any consortium that oversaw the key issues in dealing with the interface
programs have to use?

I’ve most definitely discussed Postmaster’s interface with users, designers and
other engineers. For the most part, people are very positive about it, but there are some
issues that need to be addressed. I’m aware of those and working to fix them for 2.0. I’ve
gotten lot’s of feedback since 1.0 went out and I’m trying my best to incorporate the ideas
and suggestions that people brought forward. I’ve got a pretty good idea for how things
will look under 2.0 (in particular the design of the new Settings panels). The main window
probably won’t change much at all, nor will the reading and composing windows. Where
needed, I’ll make room for new features but as stated above, I suspect the general look and
feel of the application to remain the same. I’m not sure I totally understand the second
part of the question. Creating a good interface is not hard, it’s just very time consuming.
The most difficult issue related to this under BeOS is the lack of a professional GUI builder
for rapid application development. (I’m aware that there are several of these apps in
development and I’m looking forward to seeing them progress.) I don’t really like the idea
of a consortium dealing with the issues. Ideally, I’d like to see the operating system
manufacturer set clear guidelines as to how applications just look and behave.

Technix : What difficulties have you overcome in working on a robust mail client?
Specifically, were there any late-night, head-scratching issues that drove you crazy? ;)

There’s no single feature that has really had me stumped in terms of how to
implement it, but there are some features that are considerably more involved to implement
efficiently then others. In particular, the loading of messages into the list view.
This operation will always be slow under BeOS because each mail message is stored as
a single file. I’m really not a big fan of cache files because of the inherent overhead
that they introduce. (In particular, keeping a cache in sync with the filesystem when you
allow the user to move their mail around using an application other then the mail client
is very difficult and involves extensive use of node monitoring.) My goal is to have
Postmaster populate it’s list view as fast as Tracker can populate its. I’ll probably
never get quite as fast, but 2.0 will represent a significant improvement over 1.0. The
other main issue that’s caused several problems is the fact that I wanted Postmaster to
be completely “live”. That is, you can have Postmaster open, move mail around with the
Tracker and have Postmaster keep in sync. The obvious solution that everyone says is
“Hey, use node monitors”. Well, it’s not always as simple as that. Yes, node monitoring
is the underlying technology that’s being used, but it’s a bit more complicated then that.
You can see some of the current shortcomings in 1.0 if you use virtual folders or the mail
daemon. In either case, there are many times when Postmaster will fail to properly update
it’s list view. Thankfully, almost all of these issues will be addressed in 2.0, in no small
part to the release of OpenTracker.

Technix : How have you managed to deal with the caching issues of handling potentially
thousands of emails that a person may have in their inbox?

Well, I’m not a big fan of using cache files to solve this particular problem.
The whole point of BeOS is that it’s “live” and “real time”. I can move files around
at will, rename them, open and close applications that depend on these files and
everything should just keep working. Using cache files makes this very difficult
(though not impossible) to implement correctly. There are just to many problems
with synchronization issues that cache files create. I’m holding out on not using
cache files for Postmaster and instead trying to make optimizations so that I can
load the list view as fast as the Tracker does. Having each message represented
as a single file under BeOS has its pros and cons and you unfortunately cannot have
the speed of say an ‘mbox’ style system with the power of attribute searching. I’m
trying to keep Postmaster as BeOS like as possible and my experience indicates that
the number of users that have over 5,000 thousands emails in their inbox represent
the minority and not the majority. I’m always trying to improve loading speed, but
I really think there is a lot of room for improvement in Postmaster before I can say
that I’ve reached the maximum speed and have to look for other alternatives.

Technix : A number of users have brought forward several well-known ‘bugs’, such as the BeOS
timezone bug (emails come in funky, sometimes unsorted.), and the linefeed bug (many linefeeds
added to replies and forwarded email). How are you handling the feedback from the user community?

I’m always open to feedback from the community and I think I’ve been pretty good at
keeping up dialogue with the users. (Though I admit that the past few months have been a little
rough, sorry). When users report bugs, I take those reports very seriously. Many times I’m
aware of the bug and just need to get around to fixing it. If it’s a new bug then I’ll
probably investigate it right away to at least understand what the problem is. The hardest
ones to deal with are bugs that people report but that I’m not seeing at all
and have had very few other reports to compare with. I keep notes of all the bugs that users
file and if I don’t understand the problem, I’ll just mark it as “undefined” and hope that
I come across the problem later on and can fix it.

Technix : Is there beta testing for 2.0, and can anyone join the list?

There is no private beta testing for 2.0, nor was there for any previous
release of Postmaster. When something becomes available that is worth testing, I’ll
post it on the Postmaster web site for all too download. There’s no list to join
or anything like that.

Technix : Would it be alright if we diverted our usual Q&A pattern, and discuss how your life
has changed so dramatically when you made the shift to Be. Inc?

Well, to be honest, I don’t really think my life has changed that much. Apart from
the geographical change moving from eastern Canada to California, I still pretty much do
the same things in life. If I’m not working then I’m either out mountain biking or
skiing/snowboarding, which was pretty much the case in college. For anyone who works in
the high-tech field, then you know that it’s not your normal 9-5 job. I’ve been totally
able to adopt my own timetable and schedule so my daily routine is relatively unchanged
compared to before I joined Be. Obviously there’s a certain transition that one makes
when they leave college and enter the “real world”, but it was a much smaller transition
then I had though it would be, no doubt because the work environment is very similar
to a college lifestyle. About the only thing that I can chalk up as being “dramatic”
is the cost of living in the Bay Area, but that’s the same for everyone out here so
you can’t really complain about it since I can easily go live somewhere else if I
wanted to.

Technix : It must have been very hard, going from university to Be’s corporate environment,
and working as part of a larger framework. How do you feel, now that you’re part of their company?

Like I said above, going from university to Be was a rather easy transition. I’d
hardly call Be a “corporate environment”, at least not among the engineers and in the
traditional definition of corporate. The people at Be welcomed me with open arms when I joined
them last September and again welcomed me back in July. There’s an awesome group of people
here and it’s really a privilege to get to work with some amazing engineers. It
constantly impresses me how much such a small and focused team is able to accomplish.

Scar : Recently a lot of BeOS developers have either left BeOS or have begun
developing cross-platform. Has this lack of confidence in the future of
BeOS influenced your own development decisions? If so, how? of not, why not?

Well there’s no doubt that with Be’s recent focus shift
towards the internet appliance market, there is much less
emphasis placed on BeOS for the desktop. As a third-party
developer I can certainly share in the pains of other
developers that have been frustrated with the recent
shift away from the desktop. While I don’t like to admit
it, there’s no doubt that I have lost some of my initial
enthusiasm for working on Postmaster over the past
several months. Mostly I just haven’t had as much time
to work on Postmaster as I used to, but I can say that it
is sometimes hard to get motivated to spend hours and hours
writing an application for a platform that has an uncertain
future. Nonetheless, it’s the incredible feedback that I get
from the BeOS community that keeps bringing me back to work
on Postmaster 2.0 and hopefully get it out the door.

Scar : The response from the BeOS community upon hearing news of your
departure for Apple some time ago was immense. Did it take you by
surprise? What were your thoughts/reactions to those events?

Yeah, I was kinda surprised. Interestingly I didn’t get any
email from anyone complaining that I was leaving Be for Apple.
It wasn’t until I posted the news concerning Apple’s position
with respect to Postmaster that I started to got a ton of
feedback. What people need to understand, is that Apple’s
position wasn’t as crazy as some people might think. “Working
on a competing product for a competing platform” can certainly
be a conflict of interest and I respect Apple’s stance on that.
(I don’t think Be would be too interested if one of its engineers
was writing Internet Explorer plugins.) What did catch me by
surprise is that I thought that this issue between Apple and I
was understood and that they were fully aware of my intention
to keep working on it while at Apple. Had I have known ahead
of time that this would have come up, then I most certainly
would not have accepted the job. In any event, it didn’t work out
and I’m glad that Be was still willing to let me return (thanks

Scar : At Apple you were involved with the development of MAC OS Finder for
MAC OS X. What is your opinion of MAC OS X compared to BeOS both from a user
and developer perspective?

Well, from a users point of view MacOS X is a much more complete
operating system. Trying to say that OS X or BeOS is better then
the other is fruitless. They both have their pro’s and con’s. There’s
alot to love in the simplicity, cleanliness and ease of use of the BeOS.
Unfortunately there’s still a lot missing before I could completely
use it as my *only* desktop operating system. (I use it as my primary
OS these days, but I do have a Windows box nearby for those times
that BeOS just can’t do what I need…) I think traditional MacOS users
are going to need some time to adjust to OS X but in the end they’ll
probably find a lot of what they’ve been wanting for the past few years.
I’m interested in seeing OS X once many of the mainstay applications
are carbonized. Running OS X with all your apps being launched in the
Classic environment isn’t a fair test. I think the unfortunate reality
is that with more support for applications and a better internet experience,
most users will end up being more productive in OS X then under BeOS,
regardless of which one is “better”.

From a developers point of view, I can say that I prefer BeOS but I’m
somewhat bias here because I have more experience with the BeOS API’s
then with the equivalent MacOS ones. Working on the Finder involved
living in a C++ world that pretty much just called a bunch of C
API’s. (Yes, PowerPlant is used, but PowerPlant is still a C++ interface
to a C API.) Living in a more or less all C++ world under BeOS just seemed
a lot more natural and cleaner to me. (Experienced Finder engineers might
say the exact opposite.) There were some frustrating things that OS X was
trying to implement that the BeOS already had. One example was node
monitoring. The BeOS has the beautifully elegant way of monitoring
changes to a file. You simply ask the system to “watch” it for you and
every time the file gets renamed, moved or deleted, your application
gets notified, I love it. OS X doesn’t have this. I know the Finder
team would *love* to have node monitoring. Things like this make it
frustrating to see so many engineers working on solving problems, or
working around problems, that the BeOS already addressed.

Scar : How were you received back at Be Inc after your short time with Apple?

As far as I can tell (maybe I’m wrong… ;) I got a very warm welcome
when I returned. I mean, I didn’t think it was that strange that the
engineers tied me up, shaved my head, then spray painted it half red
and half blue. Apparently they do this to everyone that leaves and
then returns, right guys?

Technix : What do you do at Be Inc. these days that occupies your time?

Officially I’m an “Applications Engineer”, which means that I spend most of my time
working on application-level software for BeIA. Right now, BeIA supports web browsing, I’m working
on adding, surprise, mail functionality.

Scar : BeIA received quite alot of attention at COMDEX. How are spirits at Be
Inc post expo?

I’d say spirits are pretty high around here, so long as we don’t all start
reading the BeNews message forum… ;) You have to appreciate that there
is a lot more to BeIA then might be visible from the outside world. In
the “good old days”, Be would talk openly about future version of the BeOS,
about what was coming and roughly when it might arrive. Things are different
in the BeIA world. We simply cannot be as open as we were in the past. Maybe
we don’t want to expose features or functionality of BeIA that competitors
might be able to take advantage of. Sometimes we might be working with a
potential OEM that simply isn’t ready to announce a product yet. When BeIA is
demoed at places like COMDEX, users can get a peak at what we’ve been working
on here for the past several months, but it doesn’t tell the entire story. The
Internet Appliance market space has the potential to be huge and incredibly
diverse. “Surfing the web and checking e-mail” represents just one set of
functionality that these types of devices might have in the future. Something
like the Aurora box represents a completely different appliance. Unfortunately
these first generation devices don’t exactly demo in the way that
BeOS and 3D Mix might have in the past so I’m not surprised that some people
come away disappointed after a visit to the Be booth. People need to understand
that BeIA is not BeOS and that the two products are targeted at completely
different markets. Once people start to see and understand what BeIA is
and the potential that it has, then they’ll probably get as excited about
it, and Be’s future, as the engineers here at Be do. We all love the BeOS,
but our focus and energy is behind BeIA, and I think I can speak for everyone
here when I say that our spirits are very high and that we’re extremely
excited with respect to BeIA and the partners that have announced support
for it.

Scar : Some stirrers out there have mentioned that the apparent silence from
the Postmaster camp signals a lack of confidence on your part in the future of
BeOS, and that for a Be employee to be acting that way is sign of things
to come. Any chance you can allay peoples fears there?

Well, during my time at Apple I wasn’t working on Postmaster so there really
wasn’t much to report back then. When I returned to Be at the end of July,
I arrived right in the think of BeIA development. Quite simply, I have not
been able to allocate time to work on Postmaster in the past few months. I
really wish that there was more to report on Postmaster’s progress but
there simply isn’t. If there were more hours in the day, then there
would probably be more Postmaster updates. Please don’t try and make any
correlation between the number of Postmaster updates and my confidence in
the future of the BeOS.

People need to realize that BeOS no longer represents the primary product
for Be Inc, nor does it represent the immediate future for Be Inc. As has
been stated many times, the bulk of the engineering effort here at Be is
going towards making BeIA a success. Nonetheles there are some great
things going up for BeOS, namely an improved network stack called BONE
and improved OpenGL support, so I think users still have a lot to
look forward to. After that, we’ll have to wait and see. If you read
the BeIA literature, then you can see that the BeOS plays a very important
role in the success of BeIA, namely that it represents the development
platform for BeIA. While the BeOS might not become the great desktop
based “Media OS”, it will still live on. And as far as I’m concerned, so
long as there are people using BeOS, then there will be people that
want to send and receive e-mail (maybe even from an IMAP server…).

Technix : Thank you so much for your time, Kenny. This has been a great help to the user community. We’re looking
forward to your progress, when it’s available!

Your welcome, and thanks to everyone in the Be community who has supported Postmaster, it’s very much appreciated.

Scar : Thanks very much for your time, Kenny. I look forward to using
Postmaster 2.0 in the near future.

You’re welcome and thanks for the support.

So now head into the comments and let us know what you think! :)

20 Responses to “Interview: Kenny Carruthers”

  1. Epiphyte Says:

    Word Services API?

    In terms of adding things like spell checkers and the like, which Kenny states would be desirable but beyond the scope of Postmaster at this time, why not just support the Word Services API? It already exists, the SDK is readily available, and third parties can write text-processing plugins for it. It’s already supported by a number of other applications out there.

  2. wondering Says:

    In Response To Maxx @ 12/05/2000 10:15:20 AM

    Re: HTML support, BeMail question

    and your source for this info? link, please. “adding IMAP support” is very different from “cleaning up”

  3. Technix : Chris Simmons Says:

    In Response To IAmWhoIHam @ 12/05/2000 10:12:26 AM

    Re: Great interview!

    Thank you very much.

    A positive attitude goes a long way. Keep the faith!

  4. Scar Says:

    In Response To IAmWhoIHam @ 12/05/2000 10:12:26 AM

    Re: Great interview!

    Cheers. Its much appreciated.

    Keep on truckin’ folks.

  5. NorseLord Says:

    HTML support, BeMail question

    I’m not a big fan of marked-up e-mail, but when I do get messages marked up with HTML I would love to be able to view them quickly in a browser. How about having a “View in Browser” button in Postmaster which would perhaps save the current message content as a temporary .html file and then open that .html file in NetPositive for viewing? It’s not an elegant solution, but useful enough.

    Also, Kenny, do you know the status of open source BeMail? Several weeks ago one of the Be developers mentioned on bedevtalk that it was “in his inbox” to clean up the BeMail code and release it open source. Do you know anything about this?

    Thanks, guys, for a nice interview. I think it’s great how we keep our nose to the grindstone and keep moving ahead.

  6. David Bruce Says:

    file attachments

    I’ve used the demo version of Postmaster for the last few weeks, and like it a lot. One problem I’ve noticed is that when I get messages with file attachments from Windows users, it doesn’t seem to handle them properly. For example, Excel spreadsheets wind up as gibberish tacked on to the end of the body of the message. OTOH, if I copy an Excel file to my hard drive and click on it, it appropriately launches Gobe Productive. Will PostMaster 2.0 do better in this respect?

  7. IAmWhoIHam Says:

    Great interview!

    Lots of good information, good questions, good answers, and best of all — each question didn’t have a negative slant to them as some other Be news sites have done in the past. ::ahem::

  8. Maxx Says:

    In Response To NorseLord @ 12/05/2000 08:57:12 AM

    Re: HTML support, BeMail question

    Be is re-writting the Mail Kit to include IMAP by default and also some other goodies. This is the reason why the BeMail hasn’t been open sourced yet.

  9. rgering Says:

    It’s nice to here…

    that people who work at Be think that BeOS apps are still worth working on. I take this a s a good sign. Thanks for this interview.
    Remember to read “The ‘Any’ Key”

  10. gsc Says:

    Very positive

    EXCELLENT Interview !!

    It goes a long way to explain whats happening
    behind the scenes, without giving away secrets.
    I liked how he explained that PR has to be different
    with BeIA, and that there is a reason for Be Inc.
    being fairly quiet, yet that does not mean things
    are going bad.
    Nice to hear that within Be, spirits are good.
    I though his comment about the benews attacks were

  11. Seker Says:

    In Response To Epiphyte @ 12/05/2000 12:23:27 AM

    Re: Word Services API?

    Good idea…
    I would kill to get a spell checker for Postmaster.

  12. Anonymous Says:

    In Response To NorseLord @ 12/05/2000 08:57:12 AM

    Why no PGP support?

    BeOS is the only OS without GUI frontend for PGP or mail client that supports it:-<<<<<!!!!!

  13. bequick Says:

    In Response To David Bruce @ 12/05/2000 09:10:16 AM

    Re: file attachments

    i dont know about postmaster 1.1, but please include a “save all” attachment option…. thanks

  14. LeftTurn Says:

    Good job guys!

    Excellent interview that brought out some much needed info. One could almost say perfect timing.
    Life is still good at Be, and Be is still doing stuff for BeOS. What more can we ask?
    As for BeIA, it sounds like Be is in a good position with it and may do very well.
    Guess I need to check out the Postmaster app to see what it’s about. I know Personal Assistant works fine with it at the moment, but will Kenny’s proposed changes for ver 2.0 mess that up?

    Anyway, keep up the good work BeGroovy team. It’s stories like this that keep you as my “Home” page :) .

  15. Nimdok Says:

    In Response To gsc @ 12/05/2000 11:37:31 AM

    Re: Very positive

    Yes, don’t let the BeNews posts get you down Kenny. We all mean well :)

  16. C.Degea Says:


    Excellent! We need more interviews like this;
    thanks to the begroovy crew and kudos to Kenny
    for keeping on working on PM in his spare time
    even though Be is in crunch time until december!

    Looking forward to Postmaster2 (and to
    reading/posting here instead of more uh..
    crowdy news site forums ;)

  17. Anonymous Says:

    In Response To Anonymous @ 12/05/2000 6:18:23 PM

    Re: Why no PGP support?

    Back in the R3 days there was a guy who wrote a fully featured US version of PGP w/a GUI. I’m not sure what ever happened to it though.

  18. flabrod Says:

    In Response To C.Degea @ 12/06/2000 03:54:06 AM

    Re: Excellent

    Couldn’t have said it better myself. Cudos to all involved in the interview.

  19. Kenny Says:

    In Response To Maxx @ 12/05/2000 10:15:20 AM

    Re: HTML support, BeMail question

    Be is re-writting the Mail Kit to include IMAP by default and also some other goodies. This is the reason why the BeMail hasn’t been open sourced yet.

    I have no idea where you got this information, but it is unfortunately incorrect. Any changes being made to the Mail Kit are completely independant of when the BeMail source might be released. My bet is that Todd, the engineer who was going to clean-up the source, is just so busy these days that he hasn’t been able to work on it. I can promise you that it has absolutely nothing to do with any work on the Mail Kit.


  20. Kenny Says:

    In Response To David Bruce @ 12/05/2000 09:10:16 AM

    Re: file attachments

    One problem I’ve noticed is that when I get messages with file attachments from Windows users, it doesn’t seem to handle them properly.

    Postmaster should be able to handle these attachments just fine so long as they were encoded in base64 (commonly called MIME). Some mail clients use uuencode for attachments, which unfortunately Postmaster does not support. (That case, Postmaster would not even recognize that the message had attachments and simply show you a bunch of garbage characters in the text view).

    Second, be sure that you have an appropriate application on your computer that can handle the type of attachment you receive. For example, if a Windows user sends you a Word 2001 format file, then you probably won’t be able to view this. (Can Gobe 2.0 open these?) Many times Postmaster will correctly extract the attachment to disk, but you might not have a viewer for them.

    Of course, there’s always the posssibility that Postmaster is choking on the message (bugs do exist..;). If that’s the case, then I’d be very interested in seeing the format of that message.


[powered by WordPress.]

Random Haiku:

Buy some freaking stock
All you stupid investors
Make lots of money

Since 1998 - Until the Last User Leaves...
BeGroovy, established 1998

search BeGroovy:

BeGroovy Archives:

October 2018
« Sep    


22 queries. 0.062 seconds

[powered by WordPress.]