Groups | Search | Server Info | Login | Register

Groups > alt.comp.software.seamonkey > #8556

Re: IMAP mail problem

Show all headers | View raw

Dirk Fieldhouse wrote, on 30 Apr 2026 10:36:

> On 30/04/2026 07:49, alexyu wrote:
> 
>> Starting from the end, my IMAP is FastMail (FM); Gmail is just a POP
>> account, so I can keep an eye on the Google account I need to use
>> Android easily.
> 
> This interesting post at the Fastmail site says that the IMAP folders
> you see depend on the choice of IMAP port:
> <https://www.fastmail.com/blog/whats-in-a-name-mailbox-names-via-imap/>

Thanks a lot for the link! Most of it is quite abstruse to me, but it 
seems to suggest that folder namespaces and case-sensitivity MAY be a 
factor, here.

I tried changing the port from 993 to 992, and it definitely involved 
SOMETHING at the FM end, since apparently all the folders (and their 
names) remained the same, but there was a noticeable lag on accessing 
them, and the sort-by-date order changed from the one I had chose to the 
other.  The shenanigans with 'trash folder name' between the Server 
Settings and 'about:config' kept up, with no discernible order: I tried 
several combinations about changing one and/or the other, closing and 
reopening SM, and looking at the result -- which, always, was that 
messages in the FM Inbox in SM, when moved to a Local Folder, were NOT 
also copied to FM Trash, and messages in the FM Inbox in SM, when 
deleted there, WERE moved to FM Trash, same as before.

However, things took a sinister turn in one 'iteration', when I was 
using 992 and not 993: I started to write this response and, when SM 
tried to save my progress automatically (as it's set up to do), it said 
it couldn't, because the "Drafts" folder (which, in my case, should be 
-- and has been -- the FM one) "could not be found", so the Drafts draft 
could not be saved!!  I immediately checked everything, changed port to 
993, reopened SM, and am now back to the 'normal' process, where the 
draft is frequently saved (invaluable, for me!).

After I adequately recovered from the fright, it just reinforced my 
stated intent:

> I still suspect something is 'damaged' in the profile, but don't have
> the knowledge or disposition to try and track it down, and also don't
> want to try anything which would involve migrating all my decades-old
> emails (from Netscape, Moz Suite and SM), and risk creating even
> worse problems.
> 
> "If it ain't broke don't fix it", and in this case it seems to be
> damaged, but not broken, so...

As I hope I commented, large-scale changes to my home system (a 
multi-boot with Windows XP, 7-32, 7-64 and 10, with a SM 2.49.5 profile 
shared between ALL of them) during the previous months did entail some 
problems and crashes, from all of which I apparently recovered, and some 
experiments did involve trying to make changes to the FM folder 
structure, so I think it's very likely that SOMETHING in SM did get 
'damaged', probably in subtle ways which only manifest in some behaviors 
(like this one).

I think I can live with this small problem indefinitely (unless it leads 
to something worse in the future), and "cut my losses", not trying to 
troubleshoot this further.  In that change process, I had a somewhat 
similar experience, when I tried to install Win7-64 'over' Win7-32: I 
ended up deleting that and installing Win7-64 from scratch, and 
migrating what I needed/could from the 32-bit version.

I did consider installing SM 2.53 alongside 2.49 with its own profile, 
likewise ThunderBird (TB), but the potential blunders and slip-ups 
seemed significant and not unlikely, so decided to keep 2.49 only; it's 
also the last one which accepts most of the extensions I use and love, 
and is compatible with FireFox (FF) "56" (ESU, actually) which is 
sometimes useful for sites which don't work well or at all with SM 2.49, 
and currently, in most day-to-day use, MS Edge 104 (the last one for 
Win7) fills the bill.

So, I guess I'll just accept this situation as a small glitch, and keep 
on truckin'...

Thanks a lot for your knowledge and attention, it did help me a lot: At 
least, I have some idea of what's involved, which for me is important.



> Also, maybe try setting up your account from scratch following the
> Thunderbird (pre-115) instructions on the site.
> 
> /df
> 


-- 
Best,

s) alexyu

Back to alt.comp.software.seamonkey | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

IMAP mail problem Alexander Yudenitsch <alexyu@postpro.net> - 2026-04-28 19:14 -0300
  Re: IMAP mail problem "Adam H. Kerman" <ahk@chinet.com> - 2026-04-28 22:45 +0000
    Re: IMAP mail problem alexyu <alexyu@postpro.net> - 2026-04-28 22:11 -0300
      Re: IMAP mail problem Dirk Fieldhouse <surname@gmx.net.plusremovethisandtherest.invalid> - 2026-04-29 19:28 +0100
        Re: IMAP mail problem alexyu <alexyu@postpro.net> - 2026-04-29 22:51 -0300
          Re: IMAP mail problem alexyu <alexyu@postpro.net> - 2026-04-29 23:58 -0300
            Re: IMAP mail problem Dirk Fieldhouse <surname@gmx.net.plusremovethisandtherest.invalid> - 2026-04-30 06:18 +0100
              Re: IMAP mail problem alexyu <alexyu@postpro.net> - 2026-04-30 03:49 -0300
                Re: IMAP mail problem Dirk Fieldhouse <surname@gmx.net.plusremovethisandtherest.invalid> - 2026-04-30 14:36 +0100
                Re: IMAP mail problem alexyu <alexyu@postpro.net> - 2026-04-30 12:19 -0300
              Re: IMAP mail problem "Adam H. Kerman" <ahk@chinet.com> - 2026-04-30 10:08 +0000

csiph-web