Re: SMTP problem...new builds

Thanks!
I don't believe that's it. Two reasons:
-it typically works for the first outgoing email then starts having 
problems;
-and, though it may not be quite relevant to your thought, Mulberry on my 
laptop, going through the same router to my ISP, works without a hitch.
Do let me know if these arguments are not persuasive.


--On Thursday, March 05, 2015 12:33 PM -0700 Devin Reade <[email protected]> 
wrote:

> I've seen SMTP send queue problems under Linux RHEL as well.  Typically
> if the server isn't available, it won't retry, at least until I send
> another message.
>
> For windows, you might want to ensure that your local firewall is not
> blocking *outbound* SMTP connections.  I've seen that hit various users.
> It could also explain the difference between the two working machines
> and one non-working machine.
>
>
> --On Thursday, March 05, 2015 11:00:40 AM -0800 Brian Reid
> <[email protected]> wrote:
>
>> I use Mac and Unix.
>> I'm trying to transition to Thunderbird while Mulberry still works. I
>> don't want to wake up one morning to discover that I can't read my email
>> without learning a new client.
>>
>> There are still a number of things that Mulberry can do that Thunderbird
>> cannot, so I keep Mulberry active.  But the end is near.
>
> If anyone is contemplating retiring Mulberry, you may want to continue
> to at least keep subscribed to this list to keep an ear out for things.
> It's not as if it's a high-traffic list.
>
> I'm in the *very* early stages of trying to do a Qt-based
> Mulberry-influenced
> variant.  My focus is on Linux, OpenBSD, and portability.  In other words,
> I intend for it to work under Mac/Windows as well, although I don't tend
> to deal on those platforms.
>
> Before you get your hopes up, this is in the realm of "the cobbler's
> children have no shoes".  That is, I develop software for a living
> but this is an unpaid project.  No, that is not a solicitation, but
> it means that development time takes a back seat to family and $work.
> And both of those take up most hours in my day.
>
> No timelines, even wild-ass guesses, are available at the moment,
> so please don't ask.  I can't even promise that it will ever be
> anything but vapourware.
>
> My motivation is driven by the concerns already mentioned by
> others, but also the fact that RHEL as stopped supporting 32-bit
> installs. Which means that for me, the end-of-live of RHEL6 is
> end-of-life for a 32-bit Mulberry (at least on one of my major
> platforms).
>
> Devin
>
>