Componenti aggiuntivi
Benvenuto in SeaMonkey Add-ons.
Aggiungi nuove funzionalità e stili per rendere SeaMonkey veramente tuo.
ChiudiRich Wales
Informazioni utente
| Nome | Rich Wales |
|---|---|
| Utente da | Marzo 5, 2007 |
| Numero di componenti aggiuntivi sviluppati | 0 componenti aggiuntivi |
| Media delle valutazioni sui componenti aggiuntivi di questo sviluppatore. | Nessun voto |
Le mie recensioni
Signature Switch
Assegnate 3 su 5 stelle
I've been using this add-on for several years and have found it indispensable for handling different signatures for different situations.
I have one major complaint, however -- the add-on insists on including the so-called "Usenet signature separator" (a line containing two hyphens and a space) at the top of any signature.
Apparently the author of the add-on was under the (mis)impression that this separator line was mandated by Internet e-mail standards. In fact, it is not -- it is a convention expected only in the obsolescent Usenet newsgroup system, and it has never been mandated for e-mail. However, I was unable to convince the author to consider removing the separator line or even making it optional.
Note, BTW, that a configuration flag (mail.identity.default.suppress_signature_separator) was added to Thunderbird some time ago to omit the separator line before the initial signature included in a brand-new message. However, the Signature Switch add-on doesn't pay attention to this configuration flag -- perhaps, as I said above, because the author may still be convinced (mistakenly) that the separator line is a mandatory Internet e-mail standard which he must follow regardless of how many people want to ignore it. Whatever . . . .
From a technical point of view, it might be more complicated for the add-on to remove or replace a signature block if it isn't demarcated by the Usenet-standard separator line. On the other hand, it might be acceptable to assume that the last empty line in the e-mail body marked the start of the signature block.
Many people have complained that Signature Switch doesn't support embedding the signature before quoted text from a previous message. Accurately identifying an embedded signature block (in order to remove or replace it) could certainly be tricky, but I assume it could somehow be done. An embedded signature block absolutely must not include the Usenet separator line, since e-mail programs which support the separator line would misinterpret the bottom-quoted text after the embedded signature block as being part of the signature.
P.S.: As a kind of workaround, I discovered that if I include my own Usenet signature separator line in my signature file, Signature Switch will see it and will avoid adding its own separator. In the HTML versions of my various signatures, I specify a white colour for my own separator line -- so one of my signature files looks like this (remember the Signature Switch convention of combining both plain-text and HTML signatures into a single file, separated by a line containing only a single equals sign):
Rich
=
<span style="color:#FFFFFF">-- </span>
<span style="color:#800000"><b>Rich</b></span>
When I use the above signature, even though my separator line is enclosed in HTML markup, Signature Switch still notices it and doesn't add a separator of its own. This workaround doesn't help if I am composing plain text e-mail, and the add-on still puts the signature at the bottom of the message even if I'm writing my reply text above quoted material, but at least the separator line is invisible in HTML, so it's not quite so unsightly.
MailHops
Assegnate 3 su 5 stelle
The change you just made (on your server, I assume) seems to have addressed my concern about the wrong location being reported -- at least in part. I'm still seeing problems with some e-mail; I sent another screen shot to your Facebook account.
Questa recensione riguarda una versione precedente (0.5) del componente aggiuntivo. Questo utente ha inserito una recensione precedente su questo componente aggiuntivo.MailHops
Assegnate 3 su 5 stelle
I'm coming to MailHops after having used the Country Lookup add-on for a long time. Country Lookup doesn't work in current versions of TB, and the author has apparently abandoned work on it.
I am seeing a couple of problems with MailHops. First, many locations are being reported with a city name plus a seemingly arbitrary number (instead of a country name). In my opinion, the country name should always be shown, even if it's the USA or Canada.
Second, the displayed location appears to be based on the FIRST (physically first, chronologically last) "Received:" line. If this add-on is to be of any use showing the origin of a message, it needs to display the location corresponding to the LAST (chronologically first) "Received:" line.
Country Lookup
Assegnate 1 su 5 stelle
This used to be one of my favourite add-ons. Unfortunately, it hasn't worked at all since at least TB5, and the author appears to have abandoned it -- my recent pleas to him to fix the problem have gone unanswered.
I've delayed upgrading from TB 3.1.16, holding out the faint hope that Country Lookup would get fixed, but it's obvious to me now that this simply isn't going to happen. And I have no experience at all writing TB add-ons myself, nor do I have the time right now to climb a steep learning curve in order to try to fix the problem myself, and it doesn't appear that anyone else out there has the required expertise, time, or interest either.
The "MailHops" add-on (suggested by someone else as a possible replacement) has issues of its own, but at least there seems to be some hope of getting those problems addressed -- unlike Country Lookup, which sadly appears to be gone for good.
Country Lookup
Assegnate 1 su 5 stelle
I love this add-on, but it stopped working around Thunderbird version 5. I've refused so far to update TB 3 on my home machine because I'm unwilling to give up this add-on.
I've looked at the code for Country Lookup version 2.0, but I have no experience with Mozilla add-on development and really don't know where to start. The last I heard from the developer, he was very busy with school and simply didn't have any time to track down the problem that breaks this add-on in the current Thunderbird. Any suggestions on where to find someone else who might be willing to look at the code for this add-on?
Enigmail
Assegnate 5 su 5 stelle
I *love* Enigmail and can't imagine living without it. I'm worried, though, because I haven't seen any indication that there's going to be a version of Enigmail for the up-and-coming version 3 of Thunderbird. I tried checking the author's support forum on mozdev.org, but it doesn't look like anyone has said anything there (about anything) in several months. Does anyone know?
Questa recensione riguarda una versione precedente (0.95.7) del componente aggiuntivo.Per creare una tua raccolta devi avere un account per Mozilla Add-ons.
