Legend:

For further readings on the pros and cons and how a mail should be properly quoted please have a look at http://learn.to/quote. Keep especially an eye on the 'Quotationsmarks' section that pretty much sums the issue up.

217

217

218

=== When replying to a mail, a wrong To: address is put in the write window, why? ===

219

Well, there seems to be a common misunderstanding of the folder based "mailing list" feature in YAM. Normally YAM allows to configure a folder as a so-called "mailing list folder" where you can set a "To: pattern" and "To: address", so that certain mail actions like reply, forward or new mail react differently when the configured pattern matches the To: address of a mail. For example, if you are suscbribed to the YAM user mailing list your ought to have a seperate folder for the posts arriving from the YAM mailing list and eventually your folder configuration will have a configuration similar to:

220

221

{{{

222

'To' pattern: #?yam@freelists.org#?

223

'To' address: yam@freelists.org

224

}}}

225

226

So in case you are pressing reply to a mail where the To: matches the configured pattern, the preconfigured "To: address" of the folder will be inserted instead.

227

228

However, it seems that some people mix up the "To: pattern" and set it to "#?" or their own mail address only. This is clearly not what this 'To' pattern is all about and definitly ends up in not being able to correctly reply to a mail - especially when you are in the Incoming folder.

229

230

So, please go through all your folder configurations (doubleclicking on each folder) and check that you have the "To: pattern" correctly set or the mailing list feature disabled for the folder. Best practice would be, if you want the mailing list feature enabled, to use the "Auto" button in the folder configuration window. This will automatically try to find out the correct pattern and mail address in case you already have some mails in the folder.

231

232

In addition, please also keep in mind that when replying to a mail that is stored in the incoming folder, YAM will check all mailing list configurations of all folders. That means, if you press "reply" on a mail in the incoming folder, YAM will walk through all your folders and if a "To: pattern" matches the mail, the write window will get the specified "To: address" instead of the mail's original sender address. So here the incoming folder is somewhat special and therefore it is absolutely necessary to have all 'To' patterns of all folders setup correctly.

233

234

=== What's the purpose of the 'Bounce' option in YAM and can I use it to e.g. bounce SPAM mail back? ===

235

Since early versions (2.3), YAM has a 'bounce' (remail) option which allows to send a mail to an alternative recipient as it would have been sent to that recipient originally. This functionality is also often called a 'remail' operation. What YAM does is, to take the mail as you have received it and directly remail it to an alternative recipient. The new recipient will receive that mail with more or less not noticing that it was send to an another person previously.

236

237

In fact, 'more or less' in this term means, that YAM will add some special header entries (e.g. 'Resent-From:' header) to signal that the mail in question was not really comming from the original author directly, but 'resent' instead. This is to conform to RFCs and to give the new recipient at least a minor hint that the mail in question may have been altered on the way.

238

239

So if you once received a mail on accident which normally should have gone to someone else you can use the bounce functionality to do that. Another use case could be to forward the mail as is to another account of your own.

240

241

However, this functionality is not meant to be used to bounce the mail back to the original author. This includes that e.g. if you received a SPAM message you want to bounce it back to the original author (the spammer) to give him the impression that something went wrong and that the user didn't exist. That's not only producing unnecessary email traffic but also isn't the scope of the bounce functionality in YAM. In addition, since 95% of the junk mail have bogus sender addresses this would result in error messages or that you have sent SPAM yourself to someone innocent. Spammers themself don't care about whether the mail makes it or not (hence the bogus address). All they are after is the small percent that fall for whatever they are spamming for. If the address is simply bad then it is going to bounce back or more commonly it is someone else's address that is going to get bombarded with bounced messages.

Yes it is. You just have to create a new list with a suitable name in YAM's address book and add all the desired recipients. Then add this list as a regular recipient when writing a mail.

222

248

223

224

249

=== When writing an email I get an error message like "+++ Host environment not found"? ===

250

If you are about to write an email in the internal texteditor of YAM and you automatically get an error message similar to this one:

251

252

{{{

253

+++ Error 13 in line 1: Host environment not found

254

}}}

255

256

This points out that the internal TextEditor.mcc tries to perform spell checking via its internal functionality. So this is no error message from YAM, but an error message comming from TextEditor.mcc. To get rid of the warning, please go to the MUI preferences (SYS:MUI/MUI) and make sure you disable the spell checking of TextEditor.mcc within its MUI preferences there. Afterwards the above error message should vanish.

257

258

But if you prefer to get the spell checking running, please consult additional documentation about the AlphaSpell support of TextEditor.mcc and how to properly set it up.

259

260

=== Why isn't YAM able to mark whole sentences as bold/italic/underline and just highlights single words? Wasn't that possible already? ===

261

Since YAM 2.5 the text highlighting functionality in YAM was changed according to more or less established standard when writing/displaying email on different email programs.

262

263

Previously, the internal TextEditor allowed to mark whole sentences as bold/underline/italic/colored whereas this operation ended up in showing those sentences in the corresponding style. When having sent the mail it would then end up as e.g. the following example in the final email message:

264

265

{{{

266

*This sentence in bold*

267

}}}

268

269

However, this scheme was completly incompatible to the given established standards in the email client community. Mailers such as Thunderbird never displayed those sentences in the correct style. In addition, it wasn't quite intuitive to notice the bold state when reading through such emails in the first place especially if they are wrapped to the next line.

270

271

Therefore, the highlighting practices were changed in YAM 2.5 so that each single word in a sentence will now be selected and set to the corresponding style separatly. So now the above sentence will end up looking like the following in YAM 2.5:

272

273

{{{

274

*This* *sentence* *in* *bold*

275

}}}

276

277

Even if that seems to be very ugly on a first thought, it is the only logical approach to the problem of having such mail interchangeable between different mailers. In addition, in most cases only single words need to get or should be highlighted in an email so that you will hardly set a whole sentence in bold/underline or such.