upgrading the webmail interfaces ?

[rlance]

Lately I've been missing sqwebmail, it gives a 404 Not Found error from the URL:
http://email.websaddress.net/cgi-bin/sqwebmail/login/postmaster%40target.tld/6C503FD390D333D3EFBA750BEEA01092/1171233251?folder=INBOX&form=refreshfr
despite that
toaster.conf:web_sqwebmail                   = 1
toaster.conf:web_sqwebmail_host              = 0       # 0 or a valid full qualified host name
toaster.conf:web_sqwebmail_url               = /cgi-bin/sqwebmail
toaster.conf:web_sqwebmail_require_ssl       = 1

My attention was refocused on this problem today because I also lost squirrelmail temporarily after this week's php upgrade, until i remembered to copy /usr/local/bin/php-cgi to /usr/local/www/cgi-bin.

Why isn't sqwebmail staying in https (my whole toaster only runs in https) and where does the mapping from /cgi-bin/sqwebmail to /usr/local/share/sqwebmail occur?

[matt]

sqwebmail handles the serving of stuff from /usr/local/share/sqwebmail internally, so the only thing you need in your web server config for sqwebmail is the correct URL to /cgi-bin/sqwebmail.  Toaster_setup.pl does this correctly, but portupgrade often puts the sqwebmail bin in /cgin-bin/sqwebmail/sqwebmail. The fix is easy:

   cd /usr/local/www/cgi-bin
   mv sqwebmail foo
   mv foo/sqwebmail .
   rm -r foo

And sqwebmail should work perfectly. All the sqwebmail images files should already be in your htdoc root/sqwebmail.

[rlance]

I must have permitted sqwebmail and qmailadmin from the portupgrade -ai.

Both were fixed by portmaster -e of each, removing sqwebmail from cgi-bin and data and doing the trusty old toaster_setup.pl -s al

Thanks, Matt!

[jerm]

sqwebmail handles the serving of stuff from /usr/local/share/sqwebmail internally, so the only thing you need in your web server config for sqwebmail is the correct URL to /cgi-bin/sqwebmail.  Toaster_setup.pl does this correctly, but portupgrade often puts the sqwebmail bin in /cgin-bin/sqwebmail/sqwebmail. The fix is easy:

   cd /usr/local/www/cgi-bin
   mv sqwebmail foo
   mv foo/sqwebmail .
   rm -r foo

And sqwebmail should work perfectly. All the sqwebmail images files should already be in your htdoc root/sqwebmail.

would there be any downside to changing the reference in toaster.conf to /cgi-bin/sqwebmail/sqwebmail, thereby avoiding the need to fix during future upgrades?

[matt]

None I can think of, unless you have virtual hosts that depend on that not changing. I try to keep the URLs and stuff the same, regardless of what happens with the ports. Things in the ports tree change often so I try to mask that as much as possible.

Another solution is to update /usr/local/etc/pkgtools.conf and make tell portupgrade and pkg* friends not to stuff it into a directory.