/
YAM_english.guide
11642 lines (8294 loc) · 373 KB
/
YAM_english.guide
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
@DATABASE YAM.guide
@$VER: YAM.guide 2.7 (24.12.2011)
/***************************************************************************
YAM - Yet Another Mailer
Copyright (C) 1995-2000 by Marcel Beck <mbeck\@yam.ch>
Copyright (C) 2000-2017 YAM Open Source Team
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
YAM Official Support Site : http://yam.ch/
$Id$
***************************************************************************/
/*
** TO DO...
**
** - Explain the NListtree tricks for the folder list
** - Explain how to get the most of Message preselection
** - Explain how to use "Avoid duplicates" properly
** - More detailed info about which MUI settings affect what part of YAM
** (especially fonts)
** - Quick mention of PrintMethod in the FAQ (assuming it doesn't make it
** into 2.4), maybe rename the "Tips & Tricks" node as such
** - Postscript / PDF editions of this manual
** - ...
**
*/
@INDEX "Index"
@NODE "Main" "YAM - English documentation"
@{b}=============================================
Y A M (Yet Another Mailer) VERSION 2.7
=============================================@{ub}
© 1995-2000 by Marcel Beck
© 2000-2011 by YAM Open Source Team
@{" Legal stuff " link "COPY"} - Legal information
@{" Getting started " link "BEGI"} - Requirements, installation
@{" What is e-mail? " link "MAIL"} - Introduction to electronic mail
@{" Configuration " link "CO_W"} - Configuring YAM to suit your own needs
@{" Windows " link "WI_W"} - The main windows used by YAM
@{" Reference " link "RF_W"} - File formats, ARexx commands, etc.
@{" Tips & tricks " link "TIPS"} - Some useful hints
@{" Known problems " link "PROB"} - Things that you should be aware of
@{" Support " link "INFO"} - Some useful contact links
@{" The future " link "PLAN"} - Planned improvements
@{" Credits " link "CRED"} - Those who supported the development of YAM
@endnode
@node "COPY" "Legal stuff"
@next "BEGI"
@prev "Main"
@toc "Main"
Legal stuff
***********
YAM - Yet Another Mailer
Copyright (C) 1995-2000 Marcel Beck
Copyright (C) 2000-2017 YAM Open Source Team
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or (at
your option) any later version.
This program is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
USA
@endnode
@node "BEGI" "Getting started"
@next "MAIL"
@prev "COPY"
@toc "Main"
Getting started
***************
@{" Introduction " link "INTR"} - About YAM
@{" Requirements " link "REQS"} - System requirements and software needed
@{" Installation " link "INST"} - Installing YAM on a hard disk
@{" Quickstart " link "TUTO"} - Getting YAM started in 5 minutes
@endnode
@node "INTR" "Introduction"
@next "REQS"
@prev "COPY"
@toc "BEGI"
Introduction
============
YAM (Yet Another Mailer) lets you send and receive @{" electronic mail " link "MAIL"}
over the Internet and maintain archives of messages in your computer.
The idea for YAM came to me in 1995, when I first tried using E-mail.
The programmes available then were either powerful but complicated to
configure, or else used a graphical interface but with few functions.
The goal, therefore, was to program a cross between AdMail and AirMail,
with a few ideas from Pegasus Mail.
The unexpectedly enthusiastic response to Version 1.2 led to a steady
development of YAM culminating in Version 2.2, which is much more than
just an upgrade for the popular Version 1.3.5.
As of YAM 2.3, YAM is maintained by the YAM Open Source Team.
Marcel Beck
November 2000
Features of YAM
===============
* Straightforward @{" installation " link "INST"} and @{" configuration " link "TUTO"}, taking only a
few minutes.
* Easy operation using buttons, menus, keyboard and @{" drag&drop " link "DRAG"}.
* Context-sensitive online help system, using help bubbles and AmigaGuide®.
* Provision for up to 16 different @{" users " link "US_W"}, who can each have their
own folders and define their own preferences.
* Any number of @{" user-defined folders " link "FO_W"}, which can be compressed and/or
have passwords set, and be arranged in groups.
* Hierarchical @{" address book " link "AB_W"} with groups and distribution lists as
well as comprehensive descriptions for each entry.
* Embedded read pane in main window, allows for easier reading of your mail.
* Freely customisable interface, thanks to @{" MUI " link "MUI"}.
* Themes, allows easy switching between different icon themes.
* Built-in @{" POP3 " link "PROT"} client, which can check up to 16 different POP3
accounts in one connection and also allows prior selection of the
messages to be downloaded.
* Messages can be written or answered offline and then sent to the
mail server using the built-in @{" SMTP " link "PROT"} client.
* Powerful @{" text editor " link "EDIT"} for writing E-mails providing several type
styles, @{" glossary " link "DI_W"} and spellchecking.
* Comprehensive @{" search capabilities " link "FI_W"}, for example a full text search
through all articles using a single query.
* Automatic sorting of the post with a theoretically unlimited
amount of @{" filters " link "CO03"}.
Archiving or diversion of specified articles, automatic replies or
the deletion of advertising are just a few of the possible
applications of the filters.
* Support for @{" PGP " link "PGP"} encryption and signing of messages as well as
read and receive authentication.
* Built-in support for UUencode and @{" MIME " link "MIME"} for sending and receiving
binary data and automatic recognition of over 20 datatypes.
* Event-sensitive starting of @{" macros " link "CO13"} and comprehensive @{" ARexx " link "REXX"}
support.
* TLSv1/SSLv3 secure connections (POP3/SMTP) via AmiSSL.library.
* Spam filter ported from Thunderbird.
* Localized to many languages.
@endnode
@node "REQS" "Requirements"
@next "INST"
@prev "INTR"
@toc "BEGI"
Requirements
============
Hardware
--------
* Amiga computer
* at least 2 MB RAM
* 68020 CPU or higher
Software
--------
* AmigaOS 3.0 (Kickstart V39) or higher
* @{" MUI " link "MUI"} 3.8 or higher
* 3rd party MUI custom classes:
- BetterString 11.21+
http://sf.net/projects/bstring-mcc/files/latest/download
- NList 0.111+
http://sf.net/projects/nlist-classes/files/latest/download
- TextEditor 15.37+
http://sf.net/projects/texteditor-mcc/files/latest/download
- TheBar 26.8+
http://sf.net/projects/thebar-mcc/files/latest/download
* Codesets Library 6.13+
* AmiTCP compatible TCP/IP stack (AmiTCP, Miami[DX], TermiteTCP, RoadShow)
* optional: XPK for compression of articles
* optional: PGP 2.6 or 5.0 for encryption and signing messages
* optional: AmiSSL v3 for TLSv1/SSLv3 security layers over SMTP/POP
* optional: Archiver for attachment compression, e.g. LhA
* optional: Program for spell-checking, e.g. AlphaSpell
* optional: @{" AutoDST " link "TIP5"} handling tool, e.g. SetDST, FACTS, SummerTimeGuard
@endnode
@node "INST" "Installation"
@next "TUTO"
@prev "COPY"
@toc "BEGI"
Installation
============
YAM 2.7 is distributed in six LhA archives:
@{b}YAM27-AmigaOS4.lha@{ub}
YAM for AmigaOS 4
@{b}YAM27-AmigaOS3.lha@{ub}
YAM for AmigaOS 3
@{b}YAM27-MorphOS.lha@{ub}
YAM for MorphOS
@{b}YAM27-AROS-i386.lha@{ub}
YAM for AROS-i386
@{b}YAM27-AROS-ppc.lha@{ub}
YAM for AROS-ppc
@{b}YAM27-AROS-x86_64.lha@{ub}
YAM for AROS-x86_64
Installation by using the installer
-----------------------------------
Open the 'Install' folder, double-click the 'Install-YAM' icon and
follow the instructions given by the installer. If you have already
installed an older version of YAM, please restart your Amiga after the
installation of YAM 2.7.
Manual installation
-------------------
If you don't have the Amiga Installer or for some reason you are
unable or unwilling to use it, proceed as follows:
- Copy the whole "YAM 2.7" directory path to your destination directory.
- Copy all MUI libraries (mcc/mcp) from the directory @{b}Install/MUI@{ub} to
@{b}MUI:libs/MUI@{ub}.
- Copy all Libraries located in the @{b}Install/Libs@{ub} directory to
@{b}LIBS:@{ub}
- Delete the "Install" directory within the "YAM 2.7" path as you don't
need it anymore.
- Reboot your Amiga and start YAM from the new path by doubleclicking its
icon.
@endnode
@node "TUTO" "Quickstart"
@next "INTR"
@prev "INST"
@toc "BEGI"
Quickstart
==========
This chapter is meant to be a step-by-step guide to the way YAM
works. It is assumed that you already have YAM installed on your
system and that you're using Miami as your TCP/IP software.
If you have used YAM before, you probably can skip this chapter.
1. Get the following information from your Internet provider:
- your e-mail address
- the Internet address of the mail server (so called POP- or
SMTP server)
- your password, required to log in on the mail server
As an example here's the setup for a fictitious user named 'John
Doe' living in Britain. His e-mail address is 'jdoe\@example.com'
and the address of his mail server is 'mail.example.com'. His
password is 'nguz56'.
2. Start YAM by double-clicking its icon. After the copyright window
has closed, the main window should open with two listings (folder
list & message list) and a row of buttons.
3. The program must be configured before you can do anything else.
Choose 'Configuration' from the 'Settings' menu or simply click
the button with the question mark to open the configuration
window. The sheet which then appears is called 'First Steps',
and this is where you must enter the information needed for data
transfer. Following our example this is:
Real Name: John Doe
Email address: jdoe\@example.com
POP3 server: mail.example.com
Password: nguz56
Time zone: GMT
For security reasons the password textfield only shows stars, one
for each character you type. If daylight saving time applies to
you at the time of installation, switch on the adjustment for it
(right beneath the time zone).
4. YAM allows you to define a text passage which will be appended to
all of your e-mail as a complimentary closing phrase. To define it
you have to click on 'Write' in the list on the left hand side of
the configuration window. On the page appearing now select the
text field 'Welcome phrase', delete the original text by hitting
RAmiga-X and insert something such as:
Kind regards,\\n Joe
The control string \\n forces a new line after the word
'regards'.
5. Save the settings now by clicking on [Save]. YAM now has sufficient
data to allow you to write your first message.
6. After saving the settings you're back in the main window. Click
the button 'Write' (sixth button from the left) or choose 'New'
from the 'Message' menu. The editor window will open. Insert
the e-mail address of the recipient into the 'To' textfield (e.g.
'jdoe\@example.com'). Normally of course you would put someone
else's address, but right now you want to test the system, so put
your own address instead. Insert two or three words to indicate
the subject into the 'Subject' text field ('test' will do nicely
for this one!). Now click in the large blank area and type the
actual message.
If you were using YAM in a normal way, and wished to send copies
(including hidden copies) to anyone, this could be done by clicking
on 'Options', thus activating the third of the three sheets
(Message, Attachments, Options) in the Write window.
7. Assuming you are not currently online (Miami is not running),
click on [Send later]. This sends the message to the 'Outgoing'
folder as opposed to transmitting the message right away [Send
now].
8. Now start Miami and connect to the Internet. Open the 'Outgoing'
folder by clicking on 'Outgoing' in the folder list contained in
the main window. Send the message by clicking the 'Send' button
(fifth button from the right hand side). The transfer status
window will appear and report progress as YAM logs in on the
mail server and sends the message.
9. As you've probably noticed the mail has vanished from the
'Outgoing' folder. Don't panic! It has been moved to the 'Sent'
folder. The letter symbol in the list has a little stamp on it
now, which means that the message has been sent successfully.
10. When you double-click the message, the read window will open.
You should be able to recognize the text written by you. The lines
in the upper part of the message have been inserted by YAM and
contain data needed for mail transfer (the so-called "headers").
11. Since you've written the mail to yourself you should start looking
for new mail now. Click the read window to the background or close
it, then click on the 'Get' button (sixth button from the right
hand side).
12. The transfer status window you saw before opens again and you can
watch how YAM downloads your mail from the mail server. Provided
that everything runs as it should, a requester will open up with
the message that you have received new mail. You can read the
mail in the 'Incoming' folder.
If you've made it this far without major problems, you now know the
essential functions of YAM. For further explanations and more detailed
information on single topics, please read the following chapters.
@endnode
@node "MAIL" "Basics - what is e-mail?"
@next "CO_W"
@prev "BEGI"
@toc "Main"
Basics - what is e-mail?
************************
E-mail was the first service to be implemented on the Internet and
is still the most popular method of communication over the Internet.
A substantial proportion of the people on the Internet use only this
service. It is predicted that in the next few years e-mail will replace
the traditional forms of communication like letters and fax for many
purposes. At the present time one can in a matter of minutes reach
several million people world-wide by e-mail. Users of other networks,
such as Compuserve and T-Online, are connected to the Internet through
"gateways".
Related topics:
@{" Make up of a message header " link "HEAD"}
@{" Mail protocols (POP3 and SMTP) " link "PROT"}
@{" What is MIME? " link "MIME"}
@{" Encrypting with PGP " link "PGP"}
@{" Golden rules (Netiquette) " link "NETI"}
@endnode
@node "HEAD" "Basics - make up of a message header"
@next "PROT"
@prev "NETI"
@toc "MAIL"
Basics - make up of a message header
====================================
Every e-mail starts with a header which is separated from the
actual message body by a blank line. YAM constructs this header
automatically following the settings specified in the configuration.
The header of an e-mail is divided into fields which each start on
a new line and have the general form 'Field: contents'. Fields which
are too long to fit in a single line can be split to run over several
lines. The majority of the header lines can be omitted but are added to
provide the recipient's mail program with additional information about
the message or to give data needed to check for errors caused by
transmission problems. A few of the important fields are explained by
means of the following example.
Return-Path: <just\@zfn.uni-bremen.de>
This field is added by the recipient's mail server and contains
the e-mail address of the sender to allow the recipient's computer to
send a reply by e-mail.
Received: from ina.zfn.uni-bremen.de by atlantica.access.ch
(8.8.5/INA-1.05pri) id XAA29100;
Tue, 23 Dec 1997 23:40:45 +0100 (MET)
Received: from moritz37.zfn.uni-bremen.de by
ina.zfn.uni-bremen.de (AIX 3.2/UCB 5.64/ZFNserver) id AA26355;
Tue, 23 Dec 1997 23:40:13 +0100
Each computer which sends the message on the next stage of its
journey, and also the recipient's own system, adds on a "Received:"
field to the header to say when the message arrived and where it
came from. This allows one to reconstruct transmission problems
which may have affected the message along its route.
From: Christian Just <just\@example.net>
E-mail address and real name of the sender.
Reply-To: just\@example.org
The address to which any reply to this message should be sent.
This is used if the message is despatched from a computer which the
sender cannot use to read mail, for whatever reason. Then he can use
this field to say where a reply should be sent. In the absence of a
@{b}Reply-To:@{ub} field, replies go to the address given in the @{b}From:@{ub} field.
To: "Marcel Beck (Yet another Mailer-author)" <mbeck\@example.com>
The address of the recipient; additional names can be given,
separated by commas. This field may contain simply the address
in the form name\@domain or else it may be prefaced by an additional
comment, such as the recipient's name -- in this case, the address
must be enclosed in pointed brackets.
Date: Tue, 23 Dec 1997 23:28:30 +0200
Date and time of despatch of the message. The figure after the time
represents the timezone, expressed as the difference from Greenwich Mean
Time. Here the first two digits show the hours, and the next two the
minutes.
Message-ID: <YAM7296.1549.122414920\@zfn.uni-bremen.de>
An unique identifier, created automatically on despatch. Using
this it is possible unequivocally to cancel any particular message.
In-Reply-To: <YAM7296.263.121102896\@mail.access.ch>
A precise reference to the message being replied, such as its
Message-ID
X-Mailer: YAM 2.0beta4 - Amiga Mailer by Marcel Beck - http://yam.ch
Name and Version of the sender's mail program.
Subject: Re: YAM2beta5
This field should state concisely the topic of the message. Giving
a clear and informative Subject is a mark of good style (@{" Netiquette " link "NETI"}).
Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=iso-8859-1
These fields indicate that the message is set out in MIME format.
In this example, it contains plain text in the ISO-Latin-1 character
set and characters which cannot be represented using 7 bits are encoded
as @{" Quoted-printable " link "MIME"}.
@endnode
@node "PROT" "Basics - mail protocols"
@next "MIME"
@prev "HEAD"
@toc "MAIL"
Basics - mail protocols
=======================
YAM uses the Simple Mail Transfer Protocol (SMTP) in order to send
your mail to the SMTP server, which also uses SMTP to transmit your
mail across the whole world. Incoming mail arrives at your Post Office
Protocol (POP) server, where it waits until YAM downloads it to your
computer, using the POP3 (POP version 3) protocols. The messages which
YAM sends and receives conform to the conventions set out in RFC 822
and RFC 1521 (MIME).
Outgoing mail
-------------
If you want to send an e-mail message to anyone, YAM transfers the
message by SMTP to your local SMTP server. This computer forwards the
message to the recipient's computer, generally also by SMTP.
Why does YAM not deal directly with the recipient's server?
Firstly, it would take quite a long time for your Amiga to get a
connection to one particular computer and then transmit the message.
Secondly, many computers are hard to find; it is much better to let the
mail server look for the address, instead of burdening your Amiga.
Thirdly, quite frequently the recipient's server will not be available
at the time you want to send the mail. The SMTP server solves these
problems, holding back the message until the other computer is ready to
receive it.
Incoming mail
-------------
If someone sends you email, the other computer transfers it using
the SMTP protocol as far as your POP server. This stores the message
in a sort of mailbox, where it remains until YAM collects it. When you
look for new mail, YAM downloads the message to your Amiga using POP3.
Why doesn't YAM use SMTP for incoming mail? SMTP works best if
both computers are ready to receive messages. Unless you run YAM and
your Amiga 24 hours a day and seven days a week, SMTP would not be
particularly suitable for you.
@endnode
@node "MIME" "Basics - what is MIME?"
@next "PGP"
@prev "PROT"
@toc "MAIL"
Basics - what is MIME?
======================
MIME stands for @{i}Multipurpose Internet Mail Extensions@{ui}. MIME serves
two main purposes: it allows one mail application to tell another what
sort of data is contained in a message, and it also provides
standardised rules by which mail applications can encode data, so that
it can be sent through the Internet mail system.
MIME Encoding
-------------
The Internet uses the SMTP protocol to move mail around. SMTP is
limited to the US-ASCII character set. This is a problem for people
who speak languages other than American English and so need accented
characters or non-American letters, or for people who want to use
special symbols like the bullet. Even more difficult is the
transmission of binary files, as it is often the case with attachments.
MIME provides a way around this restriction by offering two
encodings: @{b}quoted-printable@{ub} and @{b}base64@{ub}.
These encodings use US-ASCII character codes to represent any sort
of data you like, including special characters or even non-text data.
Quoted-printable is used for data that is mostly text, but has special
characters for very long lines.
Quoted-printable looks just like regular text, except when a
special character is used -- the special character is replaced with
a "@{b}=@{ub}" (dash) and two more characters that represent the (hexadecimal)
character code of the special character. Thus, a bullet in
quoted-printable looks like @{b}=95DA@{ub}.
No line in quoted-printable is allowed to be more than 76 characters
long. If your mail has some line longer than 76 characters, the
quoted-printable encoding will break your line in two, and put a "@{b}=@{ub}"
at the end of the first line, to notify the mail reader at the other
end that the two lines are really supposed to be one.
@{b} Base64@{ub} encoding is another way to protect binary data from the
SMTP mail system. However, Base64 makes no attempt to be readable,
and is more appropriate for non-text data. It is equivalent to the
older UUencode, but more reliable in use.
Content type
------------
The other important function of MIME is to allow mail programs to
exchange information about what kind of data is in a message (or part
of a message). The primary mechanism used for this is the @{b}Content-Type:@{ub}
header. The main content types are:
text readable text
image pictures and graphics
audio sound
video animations
message messages or parts of messages
multipart several different kinds of data in a single message
The subtype gives additional information about the type of data:
text/plain plain text
text/html text in HTML format
image/gif image in GIF format
etc.
By looking at the @{b}Content-Type:@{ub} header, a mail program can select
the most suitable utility to display an attached file.
@endnode
@node "PGP" "Basics - encrypting with PGP"
@next "NETI"
@prev "MIME"
@toc "MAIL"
Basics - encrypting with PGP
============================
In order to ensure that the e-mail cannot be read by anyone other
than the recipient, it is necessary to encrypt the transmission. Is
this important? Sometimes very much so! It is not possible to say in
advance what route electronic mail will take through the Net and along
the way it is possible for someone to read your mail unauthorised,
admittedly with more trouble than one would normally bother to take.
In particular, encrypting e-mail is a wise precaution if you want to
send passwords, credit card numbers or some such over the Net. Such
encrypted data is then often transmitted more safely than if sent by
normal letter post. A simple, effective and widely used tool for this
sort of encryption is @{b}PGP@{ub}, short for @{b}Pretty Good Privacy@{ub}.
PGP was developed by Phil Zimmermann and employs the @{i}public key @{ui}
method. Using this PGP program, one can be sure that the message is
the one actually written by the sender, and that only the intended
recipient can read it. The so called @{i}public keys @{ui}offer the highest
possible level of security.
There are two kinds of key:
- One is a private key, used on your computer and never revealed
elsewhere.
- The other sort is the public key. You can make as many copies of
this as you like, and send the copies to other users so that they
can send you encrypted mail.
You need both types of key, public and private, because they are
inherently connected together. You can distribute your public key as
often as needed, but it will only work when matched up with its exact
counterpart. Hence, both public and private keys are involved in
locking and (generally) unlocking information.
PGP keys are used in two distinct ways:
1. Another person can encrypt information using your public key and
send the encrypted file to you, to decipher with your private key.
2. You can encrypt information with your private key and send it
safely over the Net. Anyone in possession of your public key
can read your communication. The recipient can be sure that
the communication is genuinely from you (your digital signature
proves its authenticity) and that it has not been altered.
PGP is obtainable as freeware and the International PGP homepage
is easy to find on the Internet at http://www.pgpi.org/
Related topics:
@{" Installing PGP 2.6.x " link "PGP0"}
@{" Installing PGP 5.0i " link "PGP1"}
@endnode
@node "PGP0" "Installing PGP 2.6.x"
@next "PGP1"
@prev "PGP1"
@toc "PGP"
Installing PGP 2.6.x
--------------------
1. To begin with, download PGP2 from a reliable source. For instance,
you can use the International PGP homepage visiting
http://www.pgpi.org/cgi/download.cgi?filename=PGPAmiga-2.6.3is.lha
and then selecting the site which is closest to you.
2. Install PGP in e.g. "Work:PGP/" and create your key pair entering
"pgp -kg" in a shell window. The PGP2 directory has the following
structure:
PGP2 (dir)
bin (dir)
pgp
config.txt
language.idx
language.txt
pubring.pgp
randseed.bin
secring.pgp
3. Add an assign to your s:User-startup file to assign PGP: to the
PGP2 directory, then set the environment variable "PGPPath" to
PGP:bin in a permanent way. For instance,
1.> SetENV PGPPath SAVE Work:PGP/bin
4. In Configuration/Security, set the "PGP's directory" option
to the directory where the PGP executable may be found, e.g.
"Work:PGP/bin/".
5. If you want to be able to edit or read outgoing messages that have
been encrypted already, switch the "Encrypt to self" option on.
6. In "PGP:bin/config.txt" the following changes should be made:
@REMARK *** NOTE FOR TRANSLATORS ***
@REMARK Please specify the correct "Language = XX" parameter for
@REMARK your language, if it is officially supported by PGP
Language = en
EncryptToSelf = off
PubRing = "PGP:bin/pubring.pgp"
SecRing = "PGP:bin/secring.pgp"
RandSeed = "PGP:bin/randseed.bin"
@endnode
@node "PGP1" "Installing PGP 5.0i"
@next "PGP0"
@prev "PGP0"
@toc "PGP"
Installing PGP 5.0i
-------------------
1. To begin with, download PGP5 from a reliable source. A good
starting point is
http://www.amigau.com/amigarealm/pgp5/pgp6.html
2. Install PGP in e.g. "Work:PGP/" and create your key pair entering
"pgpk -g" in a shell window. The PGP5 directory has the following
structure:
PGP5 (dir)
bin (dir)
pgpe
pgpk
pgps
pgpv
keys50 (dir)
pubring.pkr
randseed.bin
secring.skr
language50.txt
pgp.cfg
randseed.bin
(yes, there are two copies of randseed.bin!)
3. Add an assign to your s:User-startup file to assign PGP: to the
PGP5 directory, then set the environment variable "PGPPath" to
PGP:bin in a permanent way. For instance,
1.> SetENV PGPPath SAVE Work:PGP/bin
4. In Configuration/Security, set the "PGP's directory" option
to the directory where the PGP executable may be found, e.g.
"Work:PGP/bin/".
5. If you want to be able to edit or read outgoing messages that have
been encrypted already, switch the "Encrypt to self" option on.
6. In "PGP:keys50/pgp.cfg" the following changes should be made:
@REMARK *** NOTE FOR TRANSLATORS ***
@REMARK Please specify the correct "Language = XX" parameter for
@REMARK your language, if it is officially supported by PGP
Language = en
EncryptToSelf = off
PubRing = "PGP:keys50/pubring.pkr"
SecRing = "PGP:keys50/secring.skr"
RandSeed = "PGP:keys50/randseed.bin"
7. Check the validity of the keys in your public keyring with "pgpk -e",
then validate them with "pgpk -s <UserID>". Bear in mind you can't
send encrypted mail to anyone whose key hasn't been trusted.
IMPORTANT! BUG in PGP5
......................
If a message is encrypted for more than one recipient (including you),
PGP doesn't set an error code as long as there is a valid key for at
least one of the recipients.
For example, you try to encrypt a message for John and yourself;
there's no valid key for John, but there's one for you and PGP doesn't
tell YAM that encryption wasn't successful. The resulting message can
be read by you, but not by John!
@endnode
@node "NETI" "Basics - e-mail netiquette"
@next "HEAD"
@prev "PGP"
@toc "MAIL"
Basics - e-mail netiquette
==========================
- Keep your messages short and to the point.
- Give the message a concise and meaningful @{b}Subject:@{ub} header, so that
it can easily be found again.
- Put a signature at the end of the message. This should contain
your name and e-mail address and should not be longer than five
lines. Signatures often also give the postal address, telephone
number, website and instructions about sending PGP messages.
- Only write in block capitals if you want to give particular
emphasis to a point. *Stars* are also used for emphasis (YAM
interprets this by using bold type). Remember, block capitals
are generally taken as equivalent to SHOUTING.
- Set up YAM to use a line length of less than 80 characters and
don't use any control characters.
- Don't use non-ASCII characters unless you are sure that the
recipient's software interprets them correctly.
- It is regarded as extremely impolite to forward a private message
to a mailing list without the permission of the original sender.
- Abbreviations and @{i}TLAs@{ui} (Three Letter Acronyms) can be useful
provided that they don't make the message unintelligible.
The following are often used:
IMHO (in my humble opinion)
BTW (by the way)
FYI (for your information)
AFAIK (as far as I know)
ASAP (as soon as possible)
CU (see you)
- Use the ;-) smiley (winky?) to denote a touch of irony which could
otherwise easily be misinterpreted.
- Be tolerant of people's failings, e.g. in spelling, grammar, expression
or familiarity with e-mail.
- If you join a mailing list, read the messages for a while to get a
feel of the general style, what questions are asked and what is
not suitable.
- Study the @{i}FAQs@{ui} (lists of Frequently Asked Questions). It is
annoying for the members of a group if the same questions are
being asked repeatedly.
- If someone posts a message which is "off-topic", (i.e. it does not
belong in the mailing list), reply privately and NOT in the list.
- If you quote another message, then cut all the bits which are not
relevant to your answer. No-one wants to read the same message
three or four times, especially when all that is added is "Yes, me
too".
- Resist the temptation to flame in the mailing list. ("Flame" =
write abusively, generally when provoked by idiocy.) Remember that
the list is public and meant for constructive discussion. Do as
you would be done by!
- If you are replying to a message coming from a mailing list, think
carefully whether to send it direct to the sender or to the list,
and check that the @{b}To:@{ub} address is correct. It can be very
irritating when a letter addressed to a particular person appears
on the list, unintentionally.
- When replying to a message coming from a mailing list, it is usually
a good idea to mention the person who wrote that message as part of
your welcome phrase, to avoid confusion.
@endnode
@node "CO_W" "Configuration"
@next "WI_W"
@prev "MAIL"
@toc "Main"
Configuration
*************
YAM has a huge number of options, which can be set up in the