評分: 5 / 5 顆星

I used it successful for years, but now there is some bug.

After updating TB to 60.8.0 it stopped working.
Completely removing it, restarting TB and reinstalling it and restarting TB helped.

此使用者對此附加元件 曾發表過 1 筆評論

評分: 5 / 5 顆星

Thank you for a GREAT Mail Merge add-on. I've used two other approaches in yours is far easier. Worked perfectly the first time.

評分: 5 / 5 顆星

Way better than Microsoft mail merge and mailings. Works like a charm. Great job!

評分: 5 / 5 顆星

Really great tool for sending conference correspondence.

此意見為舊版本 (5.6.0) 的附加元件。 

評分: 5 / 5 顆星

A great way to send emails to your mail list. Each address gets an individual email with only their address in the TO field. You can also insert variables (any field in your address book) like first name into the emails.

此意見為舊版本 (5.6.0) 的附加元件。 

評分: 5 / 5 顆星

Excellent. Easy to use and very flexible. There are many ways to supply the source data for merge. eg address book, CSV file, spreadsheet, etc. Merge fields can be used in headers and message body. Works well.

此意見為舊版本 (5.5.0) 的附加元件。 

評分: 5 / 5 顆星

Great application

此意見為舊版本 (5.4.0) 的附加元件。 

評分: 5 / 5 顆星

This is SO much better than the Microsoft mail merge. Great job on this extension! Very easy to use, and flexible enough that it can do almost anything I can think of.

此意見為舊版本 (5.2.0) 的附加元件。 

評分: 5 / 5 顆星

Perfect

此意見為舊版本 (5.2.0) 的附加元件。 

評分: 3 / 5 顆星

The new Version stops when one Mailadress causes an error - please fix!

此意見為舊版本 (5.1.0) 的附加元件。 

評分: 5 / 5 顆星

I just wanted to add my 'five stars worth'. Works like a charm without using .csv! Credit to Alexander Bergmann.

All the reviews here seem to be about overcoming difficulties encountered with .csv but I thought I would try the 'easy' way and it works fine if you just need to personalise by using first name or other fields that are available in TB address books - and, of course, protect the privacy of your recipients.

I expected to have to create a template for re-use in future mailings to my group but no - you can create a list in the TB address book and then send the mail to the list name. How cool is that?!

Of course, I want even more so who can tell me how easy it is to create custom fields in the TB address book?

此意見為舊版本 (4.12.0) 的附加元件。 

評分: 5 / 5 顆星

Excellent!

此意見為舊版本 (4.12.0) 的附加元件。 

評分: 5 / 5 顆星

I've been using Mail Merge for quite a few years. It took some learning at the beginning, but I use it effortlessly and well now. My experience is all with CSV file as source, and "send now" without any other options, and the program works flawlessly. Love it. Couldn't live without it. Alex, why don't you have a "donate" button? Unless you're filthy rich, I'd like to improve your life a little as thanks for improving and simplifying mine!

此意見為舊版本 (4.12.0) 的附加元件。  此使用者對此附加元件 曾發表過 1 筆評論

評分: 5 / 5 顆星

Great add-on, and thanks for showing me what I did wrong.

(I have updated my review in light of Alexander's clarification of an issue I had with conditional statements, and to help others avoid the mistake I made.)

In case anyone else has an issue with conditional statements not working as intended, you may have a syntax issue. Taking one of the If/Then/Else constructs as an example, say '{{var|$|if|then|else}}', let me explain;

Af first glance, you may think, as I did, that in order to make that statement work, you would simply substitute the parameters with your variables. Thus, you might write something like the following:

{{{{JobTitle}}|$|{{TestField}}|{{ThenField}}|{{ElseField}}}}

However, this is incorrect!! The right way to implement this would be to use (notice the lack of curly brackets around JobTitle):

{{JobTitle|$|{{TestField}}|{{ThenField}}|{{ElseField}}}}

The conditional syntax is actually an extension of how variables are represented, rather than a separate construct. So, to use the job title field in your email without conditions you would refer to it simply as {{JobTitle}}.

Note that you can use string literals, variables, or combinations of these, as the 'if', 'then', and 'else' parameters. It may also be possible to perform indirection on 'var' if you construct 'var' from variables and text, but I haven't tried this.

此意見為舊版本 (4.12.0) 的附加元件。 

評分: 5 / 5 顆星

I needed to send a simple e-mail to 50+ members to confirm their contact info. (Nothing fancy, no logic conditionals) The MailMerge extension worked perfectly once I conformed my source .csv file to the exact variable names supported by Thunderbird (no spaces, capitalization the same) , and the sequence it expects (i.e. followed the developer's instructions).

此意見為舊版本 (4.12.0) 的附加元件。 

評分: 5 / 5 顆星

Please, add to the description. When using on Windows with .CSV, then, after saving the .CSV, it's better to reopen it in a text editor and save it in UTF-8, and after that choose UTF-8 in the add-on's dialog window. Otherwise there may be some charset problems or even errors in sending emails.

此意見為舊版本 (4.12.0) 的附加元件。 

評分: 4 / 5 顆星

Excellent add-on for sending customized emails to many people at once. However it would be great if it would allow nested variables. For example,

Pluralizing numbers:
{{NumProducts|==|1|1 product|{{NumProducts}} products}}, which would use the text "1 product" if "NumProducts" is 1, or else it would display "{{NumProducts}} products" if it is not 1.

Either one variable or another variable:
{{Name||{{Company}}|{{Name}}}} which would use the text of "Company" if "Name" is empty, or else use the text of "Name"

URL containing string:
{{PromoCode|||Click on http://www.example.com/promo/{{PromoCode}} for a {{PromoDiscount}}% discount off your next purchase}} which would add this text if the "PromoCode" is not empty.

此意見為舊版本 (4.11.0) 的附加元件。 

評分: 5 / 5 顆星

This is really good - and could be even better:

(Alexander, you seem to be German, so I'll be lazy):

Scheinbar hat Thunderbird die eigenen Maßnahmen zur Überprüfung der EMails auf Gültigkeit verbessert. Zumindest bekomme ich heutzutage reichlich Fehlermeldungen noch bevor die Email rausgegangen ist.

Mail Merge wird durch diese Meldung im Sendeprozess unterbrochen, wenn man es nicht gleich merkt wird mitunter auch der ganze Sendeprozess abgebrochen. Das ist sehr lästig. Die Lösung wäre ein Überspringen und Ausgabe eines Sende/Fehlerprotokolles. Vorschlag: Ausgabe als CSV-Datei, die dann direkt überarbeitet werden kann (Tippfehler korrigieren, zum nochmal probieren, oder einfach aufheben als Dokumentation).

PS.: Die Bewertung "Excellent mais" hat das Gleiche zum THema.

此意見為舊版本 (4.11.0) 的附加元件。 

評分: 4 / 5 顆星

Je suis novice et j'ai expédié un message à partir d'une liste de +- 20 noms en utilisant .csv.
Mais si une adresse est erronée (courriel) alors tout le processus semble stoppé. Je n'ai pas encore trouvé le moyen de ne pas recommencé tout le processus autrement qu'en refaisant une nouvelle liste (.csv)

此意見為舊版本 (4.11.0) 的附加元件。 

評分: 5 / 5 顆星

I've used this program for years. It's quite feature-filled and useful.

I use this sparingly, not every day. So sometimes I forget which settings work and which do not. This has led to two high-stress problems for me recently.

First, I always forget how to get attachments to work, and I struggle to format the .csv file correctly. The best luck I've had is to make sure that a double-quote is around every text field in the csv file. But I've had trouble getting even this to work before.

The second problem sent me in a panic earlier today. To my memory, I thought that the default send setting on mail merge was to save everything as a draft that I can review before sending. I realize there's an option to select this, but I thought it was the default, and I ended up sending a bunch of letters I didn't review. This turned out to have fairly bad consequences in this case, actually, and in any event was an unpleasant surprise.

These are really my problems, and shouldn't reflect poorly on the program. But it could be improved by making it more idiot proof: making "save as draft" the default setting and having a simpler way to associate file paths with other data for attachments.

此意見為舊版本 (4.11.0) 的附加元件。