1# $Id: pine.hlp 1266 2009-07-14 18:39:12Z hubert@u.washington.edu $ 2# 3# T H E A L P I N E M E S S A G E S Y S T E M 4# 5#/* ======================================================================== 6# * Copyright 2013-2021 Eduardo Chappa 7# * Copyright 2006-2008 University of Washington 8# * 9# * Licensed under the Apache License, Version 2.0 (the "License"); 10# * you may not use this file except in compliance with the License. 11# * You may obtain a copy of the License at 12# * 13# * http://www.apache.org/licenses/LICENSE-2.0 14# * 15# * ======================================================================== 16# */ 17# 18 Help text for the Alpine mailer 19 20This file is in a format created to be turned into text strings in a C 21program. 22 23There are two shell scripts that run on this. Cmplhelp.sh is the 24first and turns this into a C file (helptext.c) of text strings that 25are compiled and linked. The other program, cmplhlp2.sh, turns this 26into a .h file (helptext.h) with extern string definitions of the 27strings in the .c file. The code that actually processes these files 28while alpine is running is in help.c 29 30The lines with "===== xxxx ====" divide the different help screens. The 31xxx is the name of the variable that strings will be put in, which are 32also declared in helptext.h. 33 34# is a comment 35 36Help text screen text can be either plain text OR HTML. The latter is 37denoted by the first line starting with "<HTML>". The former is simply 38displayed as it's formatted here. 39 40HTML is limited to simple formatting ala HTML 2.0. No forms, or tables. 41In addition a small set of tools are are available to customize the HTML 42screen's text: 43 441a) Default and function key bindings are separated like this: 45 46<!--chtml if pinemode="function_key"--> 47 Function key bindings here 48<!--chtml else--> 49 Default key bindings here 50<!--chtml endif--> 51 52 531b) A way to distinguish HTML text that is to be displayed when 54 pine is running vs. when the text is served up outside Alpine 55 (someday) can be done via: 56 57<!--chtml if pinemode="running"--> 58 Text displayed when viewed within a running pine session 59<!--chtml else--> 60 Text displayed when HTML viewed outside pine (using chtml aware server) 61<!--chtml endif--> 62 631c) A way to distinguish HTML text that is to be displayed under 64 PC-Alpine vs. not is available via: 65 66<!--chtml if pinemode="os_windows"--> 67 Text displayed under PC-Alpine 68<!--chtml else--> 69 Text displayed otherwise 70<!--chtml endif--> 71 72WARNING ABOUT CHTML "if-else-endif" CLAUSES: They don't nest. 73 742a) Several "server side include" commented elements are supported: 75 76<!--#include file="textfile"--> 77 78The file "textfile" will be inserted into the HTML text directly. 79Alpine does no formatting of the text. At some point we might want to 80look at the first line for <HTML> but not today. 81 822b) Various bits of Alpine's running state can be inserted into the 83HTML text as well using the special comment: 84 85<!--#echo var="variable"--> 86 87Where "variable" is one of either: 88 89 ALPINE_VERSION 90 ALPINE_REVISION 91 ALPINE_COMPILE_DATE 92 ALPINE_TODAYS_DATE 93 C_CLIENT_VERSION 94 _LOCAL_FULLNAME_ 95 _LOCAL_ADDRESS_ 96 _BUGS_FULLNAME_ 97 _BUGS_ADDRESS_ 98 CURRENT_DIR 99 HOME_DIR 100 PINE_CONF_PATH 101 PINE_CONF_FIXED_PATH 102 PINE_INFO_PATH 103 MAIL_SPOOL_PATH 104 MAIL_SPOOL_LOCK_PATH 105 VAR_<VARNAME> - where <VARNAME> is config variable name 106 FEAT_<FEATURENAME> - where <FEATURENAME> is config feature name 107 1083) The URL scheme "X-Alpine-Gripe:" is available to insert links to 109 pine's composer such that various debugging data can be attached to the 110 message. Aside from normal email addresses, this can be set to 111 either "_LOCAL_ADDRESS_" for the configured local help address, or 112 "_BUGS_ADDRESS_" for the configured local bug reporting address. 113 Aside from the special tokens above, the default behavior only differs 114 from "mailto:" by the insertion of a special Subject: prefix that 115 consists of a randomly-generated token for tracking purposes. 116 Several optional parameters can be included to control what is 117 attached or offered for attachment to the message: 118 119 ?config -- Automatically attaches the user's configuration 120 information to the trouble report 121 ?keys -- Automatically attaches the user's most recent 122 keystrokes 123 ?curmsg -- Causes the user to get an offer to attach the 124 current message to the trouble report 125 ?local -- Automatically attaches the result of the script 126 defined by VAR_BUGS_EXTRAS 127 128For HTML-format sections, the help screen dividers "===== xxxx ====" must 129contain one and only one space after the first and before the second set of 130equal signs. 131 132Note to authors of this file: to mark sections that need further revision, 133please use the text string on the following line consistently so that it is 134easy to find those places again in this file: 135*revision needed* 136 137NOTE: Several sections of help text which weren't being used were removed 138at RCS version number 4.122. In particular, there were some placeholders 139with help text for the config screen and the composer that didn't have any 140reasonable place to be called from. 141Dummy change to get revision in pine.hlp 142============= h_revision ================= 143Alpine Commit 592 2021-09-18 09:01:17 144============= h_news ================= 145<HTML> 146<HEAD> 147<TITLE>RELEASE NOTES for Alpine</TITLE> 148</HEAD> 149<BODY> 150<H1>Alpine Release Notes</H1> 151<DIV ALIGN=CENTER> 152Version <!--#echo var="ALPINE_VERSION"--> (<!--#echo var="ALPINE_REVISION"-->) 153<BR> 154<!--chtml if pinemode="running"--> 155(built <!--#echo var=ALPINE_COMPILE_DATE-->) 156<!--chtml endif--> 157 158<BR> 159<BR>Copyright 2013-2021 Eduardo Chappa 160<BR>Copyright 2006-2008 University of Washington 161</DIV> 162 163<P> 164Alpine is an "Alternatively Licensed Program for Internet 165News and Email" produced until 2009 by the University of Washington. 166It is intended to be an easy-to-use program for 167sending, receiving, and filing Internet electronic mail messages and 168bulletin board (Netnews) messages. Alpine is designed to run on a wide 169variety of Unix® operating systems. A version for Microsoft Windows® 170is available as is a world wide web based version designed to run under the 171Apache web server. 172 173<P> 174Alpine is a free email program. Your use of Alpine is subject to the terms of the <A 175href="h_apache_license">Apache License 2.0</A>. 176 177<P> 178Alpine's privacy policy is a living, online only, document, which can be found at 179<A href="h_privacy_policy">http://alpine.x10host.com/privacy.html</A>. 180By following the previous link, Alpine 181will connect to an external server, and will download it and display 182it for you. Please take some time to read it and understand it. 183Since the Privacy Policy could be amended to take into consideration 184new additions to Alpine, please check it periodically. 185 186 <P> The changes in version <!--#echo var="ALPINE_VERSION"--> are as 187follows: 188 189<P> 190New features include: 191<UL> 192<LI> Unix Alpine: New configuration variable <a href="h_config_ssl_ciphers"><!--#echo var="VAR_ssl-ciphers"--></a> that allows 193 users to list the ciphers to use when connecting to a SSL server. 194 Based on a collaboration with Professor Martin Trusler. 195 196<LI> New hidden feature <a href="h_config_delete_before_writing"><!--#echo var="FEAT_enable-delete-before-writing"--></a> 197 to add support for terminals that need lines to be deleted 198 before being written. Based on a collaboration with Professor 199 Martin Trusler. 200 201<LI> Experimental: The instruction to remove the double quotes from the processing of 202 customized headers existed in pine, but it was removed in alpine. Restoring 203 old Alpine behavior. See 204 <A href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981781">this</A> 205 report for more background information. 206 207<LI> Add the capability to record http debug. This is necessary to debug XOAUTH2 208 authentication, and records sensitive login information. Do not share your 209 debug file if you use this form of debug. 210 211<LI> Remove the ability to choose between the device and authorize methods 212 to login to outlook, since the original client-id can only be used 213 for the device method. One needs a special client-id and client-secret 214 to use the authorize method in Outlook. 215 216<LI> PC-Alpine only: Some service providers produce access tokens that are 217 too long to save in the Windows Credentials, so the access tokens will 218 be split and saved as several pieces. This means that old versions of 219 Alpine will NOT be able to use saved passwords once this new version of 220 Alpine is used. 221 222<LI> PC-Alpine: Debug files used to be created with extension .txt1, .txt2, etc. 223 Rename those files so that they have extension .txt. 224 225<LI> Always follow ‘suppress-asterisks-in-password-prompt’ setting in the 226 various password prompts. Submitted by Étienne Deparis. 227 228<LI> Use 'alpine -F' instead of 'pine -F' as the browser default pager. 229 Submitted by Étienne Deparis. 230 231<LI> Introduction of OTHER CMDS menu for the browser/pilot to let 232 people discover the two new commands: "1" is a toggle that 233 switches between 1 column and multicolumn mode. The "." command 234 toggles between hiding or showing hidden files, and the "G" 235 command to travel between directories. Contributed by Étienne 236 Deparis. 237 238<LI> Add option -xoauth2-flow to the command line, so that users can specify the 239 parameters to set up an xoauth2 connection through the command line. 240 241<LI> Alpine deletes, from its internal memory and external cache, passwords 242 that do not work, even if they were saved by the user. 243 244<LI> New format for saving passwords in the windows credential manager 245 for PC-Alpine. Upon starting this new version of Alpine the passwords 246 saved in the credential manager are converted to the new format and 247 they will not be recognized by old versions of Alpine, but only by 248 this and newer versions of Alpine. 249 250<LI> Enabled encryption protocols in PC-Alpine are based on those enabled 251 in the system, unless one is specified directly. 252</UL> 253 254<P> 255Bugs addressed include: 256 257<UL> 258<LI> The c-client library parses information from an IMAP server during 259 non-authenticated state which could lead to denial of service. 260 Reported by Damian Poddebniak from Münster University of Applied 261 Sciences. 262 263<LI> Memory corruption when alpine searches for a string that is 264 an incomplete utf8 string in a local folder. This could happen by 265 chopping a string to make it fit a buffer without regard to its content. 266 We fix the string so that chopping it does not damage it. Reported 267 by Andrew. 268 269<LI> Crash in the ntlm authenticator when the user name does not include 270 a domain. Reported and fixed by Anders Skargren. 271 272<LI> When forwarding a message, replacing an attachment might make Alpine 273 re-attach the original attachment. Reported by Michael Traxler. 274 275<LI> When an attachment is deleted, the saved message with the deleted 276 attachment contains extra null characters after the end of the 277 attachment boundary. 278 279<LI> Tcp and http debug information is not printed unless the default 280 debug level is set to 1. Print this if requested, regardless of what 281 the default debug level is. 282 283<LI> When trying to select a folder for saving a message, one can only enter 284 a subfolder by pressing the ">" command, rather than the normal 285 navigation by pressing "Return". Reported by Ulf-Dietrich Braunmann. 286 287<LI> Crash when attempting to remove a configuration for a XOAUTH2 server 288 that has no usernames configured. 289 290<LI> Crash caused by saving (and resaving) XOAUTH2 refresh and access tokens 291 in PC-Alpine. Reported by Karl Lindauer. 292</UL> 293 294<P> Version 2.24 adds new features and addresses bugs found in previous 295releases. 296 297<P> 298New features include: 299 300<UL> 301<LI> Experimental: The instruction to remove the double quotes from the processing of 302 customized headers existed in pine, but it was removed in alpine. Restoring 303 old Alpine behavior. See 304 <A href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981781">this</A> 305 report for more background information. 306<LI> Add the capability to record http debug. This is necessary to debug XOAUTH2 307 authentication, and records sensitive login information. Do not share your 308 debug file if you use this form of debug. 309<LI> Remove the ability to choose between the device and authorize methods 310 to login to outlook, since the original client-id can only be used 311 for the device method. One needs a special client-id and client-secret 312 to use the authorize method in Outlook. 313<LI> PC-Alpine only: Some service providers produce access tokens that are 314 too long to save in the Windows Credentials, so the access tokens will 315 be split and saved as several pieces. This means that old versions of 316 Alpine will NOT be able to use saved passwords once this new version of 317 Alpine is used. 318<LI> PC-Alpine: Debug files used to be created with extension .txt1, .txt2, etc. 319 Rename those files so that they have extension .txt. 320<LI> Always follow ‘suppress-asterisks-in-password-prompt’ setting in the 321 various password prompts. Submitted by Étienne Deparis. 322<LI> Use 'alpine -F' instead of 'pine -F' as the browser default pager. 323 Submitted by Étienne Deparis. 324<LI> Introduction of OTHER CMDS menu for the browser/pilot to let 325 people discover the two new commands: "1" is a toggle that 326 switches between 1 column and multicolumn mode. The "." command 327 toggles between hiding or showing hidden files, and the "G" 328 command to travel between directories. Contributed by Étienne 329 Deparis. 330</UL> 331 332<P> 333Bugs addressed: 334 335<UL> 336<LI> When forwarding a message, replacing an attachment might make Alpine 337 re-attach the original attachment. Reported by Michael Traxler. 338 339<LI> When an attachment is deleted, the saved message with the deleted 340attachment contains extra null characters after the end of the 341attachment boundary. 342</UL> 343 344<P> Version 2.24 adds new features and addresses bugs found in previous 345releases. 346 347<P> New features include: 348 349<UL> 350<LI> Implementation of XOAUTH2 for Yahoo! Mail. <A href="h_yahoo_configuration">Learn More</A> 351 352<LI> Expansion of the configuration screen for XOAUTH2 to include 353 username, authorization flow, and tenant. 354 355<LI> XOAUTH2: automatic renew of access token and connection to a server 356 within 60 seconds of expiration of the access token. 357 358<LI> If a user has more than one client-id for a service, Alpine 359 asks the user which client-id to use and associates that client-id to 360 the credentials in the XOAUTH2 configuration screen. 361 <A HREF="h_xoauth2_config_screen">Learn more</A>. 362 363<LI> Addition of Yandex.com to the list of services that Alpine can use XOAUTH2 to 364 authenticate for reading and sending email. <A href="h_yandex_configuration">Learn More</A> 365 366<LI> Addition of a link to the Apache License 2.0 (see above). This is 367 available from the Release Notes as well as the welcome screen. 368 369<LI> Modifications to protect the privacy of users: 370<UL> 371<LI> Alpine does not generate Sender or X-X-Sender by default 372 by enabling <a href="h_config_disable_sender"><!--#echo var="FEAT_disable-sender"--></a> 373 as the default. 374<LI> Alpine does not disclose User Agent by default by enabling 375 <A HREF="h_config_suppress_user_agent"><!--#echo var="FEAT_suppress-user-agent-when-sending"--></A> 376 by default. 377<LI> Alpine uses the domain in the From: header of a message 378 to generate a message-id and suppresses all information 379 about Alpine, version, revision, and time of generation 380 of the message-id from this header. This information is 381 replaced by a random string. 382</UL> 383 384<LI> Unix Alpine displays configure options and flags when 385 invoked as "alpine -v". Suggested by Matt Ackeret. 386 387<LI> Alpine will ding the terminal bell when asking about quitting 388 when new mail arrives. This is consistent with Alpine dinging the 389 bell when new mail arrives. The bell will not ding if it is disabled 390 for status messages. Suggested by Chime Hart. 391 392<LI> When messages are selected, pressing the ";" command to broaden or narrow 393 a search, now offers the possibility to completely replace the search, and 394 is almost equivalent to being a shortcut to "unselect all messages, and select 395 again". The difference is that cancelling this command will not unselect 396 all currently selected messages. Suggested by Holger Trapp. 397 398<LI> Alpine will not write debug files unless started with the option -d, 399 so for example "alpine -d 2" will generate a debug file at level 2, 400 but just issuing the alpine command will not write any debug to a file. 401 402<LI> Experimental: Attempt to implement the Encryption Range in Windows. It works 403 in Windows 10, and it should work in Windows 8.1. It needs testing in 404 Windows 7 and Windows Vista. 405 406<LI> Addition of variables <A HREF="h_config_user_certs_path"><!--#echo var="VAR_user-certs-path"--></A> 407 and <A HREF="h_config_user_certs_file"><!--#echo var="VAR_user-certs-file"--></A> 408 which allow a user to specify locations for certificates that the user 409 trusts. 410 411<LI> Ignore non-empty initial challenge in the GSSAPI authenticator. Based 412 on a patch written by Jarek Polok, but submitted by Ignacio Reguero. 413 414<LI> When a server expires a refresh token, Alpine needs to cancel it 415 internally. Alpine will attempt to get a new one when it reopens the 416 folder after it cancels it. 417 418<LI> Set up the IMAP ID at the moment of logging in to the server, rather than 419 as a one time option, in case we need to use a special IMAP ID. 420</UL> 421 422<P> 423Bugs addressed: 424 425<UL> 426<LI> When Alpine starts a PREAUTH connection, it might still ask the user 427 to login. Reported by Frank Tobin. 428 429<LI> Crash while resizing the screen when viewing a calendar event. 430 431<LI> When Alpine opens a folder in a server whose address is given numerically 432 it might crash due to an incorrect freeing of memory. Reported by Wang Kang. 433 434<LI> Crash when Alpine frees memory on a system where LC_CTYPE is not 435 configured, and the user calls the file browser to attach files to 436 a message. Reported by Luis Gerardo Tejero. 437 438<LI> Invalid signatures created by Alpine, when built with recent 439 releases of the Openssl-1.1.1 series (but not in the Openssl-1.0.1 series). 440 Fix contributed by Bernd Edlinger. 441 442<LI> After returning from the directory side of a dual-folder, sometimes 443 Alpine would return to the first folder in the parent directory or to 444 the dual-folder. The fix is to return to the original dual-folder as 445 intended. Reported by Holger Trapp. 446 447<LI> When an attachment is deleted and the original message is saved, Alpine 448 might write only a part of the name of the file deleted. Reported by Holger 449 Trapp. 450 451<LI> URLs that are surrounded by white space are not cleaned by Alpine before 452 passing them to the browser, resulting in no display of the URL when Alpine 453 tries to open it. Reported by Gregory Heytings. 454 455<LI> When Alpine is built without smime, password file functionality might 456 fail. Reported by Andres Fehr. 457 458<LI> Crash in PC-Alpine when using the eXternal command. 459 460<LI> Fix in Macs that made Alpine abort a ssh connection to an imap server. 461 Reported and assisted by Wang Kang. 462</UL> 463 464<P> 465Version 2.23 has new additions and addresses bugs found in previous releases. 466 467<P> 468Additions include: 469 470<UL> 471<LI> Implementation of XOAUTH2 authentication support for Outlook. 472 Based on documentation suggested by Andrew C Aitchison. <A href="h_outlook_configuration">Learn More</A> 473 474<LI> Add support for the OAUTHBEARER authentication method in Gmail. Thanks to 475 Alexander Perlis for suggesting it and explaining how the method works. <A href="h_gmail_configuration">Learn More</A> 476 477<LI> Creation of Alpine's Privacy Policy. This is presented as a link to 478 an online document from the Release Notes (Link at the top of this 479 document.) Upon user request, Alpine downloads and displays this 480 document. Links to the privacy policy are also displayed when a user 481 starts Alpine for the first time, or when a user starts a new version 482 of Alpine. There is no default exit greeting command for these 483 screens, and to exit the user must press "E", instead of the old 484 default, which was the RETURN command. The RETURN command will open 485 the handle on which the cursor is on, which by default is the Privacy 486 Policy. 487 488<LI> Support for the SASL-IR IMAP extension that avoids a round trip during 489 authentication. Similar support added for the SMTP, NNTP and POP3 490 protocols. Thanks to Geoffrey Bodwin for a report that lead to this 491 implementation. 492 493<LI> Alpine can pass an HTML message to an external web browser, by using the 494 "External" command in the <a href="h_attachment_screen">ATTACHMENT INDEX</a> 495 screen. <A href="h_command_external_browser">Learn more</A>. 496 497<LI> New configuration variable 498 <a href="h_external_loads_inline_images_only"><!--#echo var="FEAT_external-command-loads-inline-images-only"--></a> 499 that controls if Alpine will keep the source link to all the images in the 500 HTML message, or will only pass a link to inline images included in the message. For your 501 privacy and security this feature is enabled by default. 502 503<LI> When reading an email and a user selects an email address to which to compose 504 a message from the message, the user will be able to select a role to compose 505 that message. 506 507<LI> New variable system-certs-path that allows users to indicate the 508 location of the directory where certificates are located. In PC-Alpine 509 this must be C:\\libressl\\ssl\\certs. The C: drive can be replaced 510 by the name of the drive where the binary and DLL files are located. 511 512<LI> New variable system-certs-file that allows users to configure the 513 location of a container of certificate authority (CA) certificates 514 to be used to validate certificates of remote servers. 515 516<LI> Remove sleep of 5 seconds for mailcap programs that use the terminal 517 to display content. Suggested by Carl Edquist. In addition, remove the 518 configurable process table command and its corresponding sleep time. 519</UL> 520 521<P> 522Bugs addressed: 523 524<UL> 525 <LI> Security Bug: Alpine can be configured to start a secure connection using /tls 526 on an insecure connection. However, if the connection is PREAUTH, Alpine 527 will not upgrade the connection to a secure connection, because a client 528 must not issue a STARTTLS to a server that supports it in authenticated 529 state. This makes Alpine continue to use an insecure connection with the 530 server, exposing user data. Reported by Damian Poddebniak and Fabian 531 Ising from Münster University of Applied Sciences. 532 533 <LI> Selecting by subject might not copy the subject of the current message 534 to the selection text correctly. Reported by Iosif Fettich. 535 536 <LI> Alpine does not set the return path correctly when using a role while bouncing 537 a message. Reported by Dr. C. Griewatsch. 538 539<LI>Bug in PC-Alpine that made Alpine go into an infinite loop and 540 consume CPU when it was iconized. Reported by Holger Schieferdecker in 541 comp.mail.pine. 542 543<LI>Crash in Alpine when attempting to reply to a multipart/alternative 544 message that is malformed, and the option to include attachments in 545 reply is enabled. Reported and patched by Peter Tirsek. 546 547<LI>Bug that makes Alpine split encoded words in the subject of a message 548 in the middle of a utf-8 character into two encoded words, breaking the 549 encoding. Reported by Jean Chevalier. 550 551<LI> Alpine would not redraw the screen when a check for new mail in an 552 incoming folder failed due to a failure while validating the server 553 certificate, and the user did not allow the connection to proceed. 554 555<LI> Crash in Alpine while resizing the screen when using any of the tokens 556 SUBJKEYTEXT, SUBJECTTEXT, or SUBJKEYINITTEXT in the index format, and 557 the screen was resized. Reported by Iggy Mogo. 558 559<LI> When Alpine is trying to authenticate to Gmail, using the XOAUTH2 method, 560 it does not display the url the user needs to open, in order to authorize 561 Alpine to access Gmail using XOAUTH2 when Alpine still has not created 562 a screen. Reported by Baron Fujimoto. 563 564<LI> When an html anchor does not quote the link in the href parameter, 565 alpine does not link to it. 566 567<LI> Attempt to fix a bug that breaks scrolling of a message in Alpine when 568 the screen is resized. Reported in the Debian bug system at 569 <A HREF="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956361">https://bugs.debian.org/cgi-bin/bugreport.cgie?bug=956361</A>. 570</UL> 571 572<P> 573Version 2.22 addresses bugs found in previous releases and has several 574additions as well. 575 576<P> 577Additions include: 578 579<UL> 580<LI> Support for <A HREF="h_xoauth2">XOAUTH2</A> authentication method in Gmail. 581 <A href="h_gmail_configuration">Learn More</A> 582 583<LI> PC-Alpine builds with LibreSSL and supports S/MIME. 584 585<LI> NTLM authentication support with the ntlm library, in Unix systems. 586Based on code provided by Maciej W. Rozycki. 587 588<LI> Add /tls1_3 flag for servers that support it. Read more information 589in the secure protocols <A HREF="h_network_encryption_security">help</A>. 590 591<LI> To increase user's privacy, remove phone-home code that would prompt 592users to send an email message upon starting Alpine for the first time for 593purposes of counting. Your use of Alpine does not disclose information about 594you or your use of Alpine to the developers of Alpine. 595 596<LI> New variable 597<A HREF="h_config_encryption_range"><!--#echo var="VAR_encryption-protocol-range"--></A> 598that allows users to configure versions of the SSL/TLS protocol that Alpine is 599restricted to try when establishing a secure connection SSL/TLS to a remote 600server. The default can be set at compilation time. 601 602<LI> Add -dict option to PC-Pico, which allows users to choose a dictionary 603when spelling. Sample usage: -dict "en_US, de_DE, fr_FR". 604 605<LI> Improvements to the configure stage of compilation. Some of 606these contributed by Helmut Grohne. See 607<A href="https://bugs.debian.org/876164">Bug 876164</A> in Debian. 608 609<LI> Add "remove password" command to the management screen for the 610password file encryption key. This allows users to use their password file 611without entering a master password. 612 613<LI> Add the "g" option to the select command that works in IMAP 614servers that implement the X-GM-EXT-1 capability (such as the one offered 615by Gmail.) This allows users to do selection in Alpine as if they were 616doing a search in the web interface for Gmail. 617 618<LI> New variable close-connection-timeout, which tells Alpine to close 619a connection that is having problems being kept alive after the number 620of seconds configured in this variable, if the connection has not 621recovered. The default is 0, which means to keep the connection alive 622and wait for the connection to recover. 623 624<LI> When a message is of type multipart/mixed, and its first part is 625multipart/signed, Alpine will include the text of the original message 626in a reply message, instead of including a multipart attachment. 627Suggested by Barry Landy. 628 629<LI> S/MIME: Some clients do not transform messages to canonical form when 630signing first and encrypting second, which makes Alpine fail to parse the 631signed data after encryption. Reported by Holger Trapp. 632 633<LI> Add /auth=XYZ to the way to define a server. This allows users to 634select the method to authenticate to an IMAP, SMTP or POP3 server. 635Examples are /auth=plain, or /auth=gssapi, etc. 636 637<LI> Add backward search in the index screen. Based on patch by Astyanax Foo, 638submitted in 2009, but resubmitted by Erich Eckner on 2019. 639 640<LI> SMIME: When Alpine is set to validate a message using the user's store, and 641 user agrees to save a certificate of another user, use the saved 642 certificate immediately to verify the smime message. Reported by 643 Stefan Mueller. 644 645<LI> Do not use a delay when printing messages to screen when the initial 646 keystroke sequence of commands is active. Based on a report from Holger 647 Trapp. 648 649<LI> In PC-Alpine, when the decoded name of an attachment does not agree 650 with its encoded name, Alpine will offer to save the file using the 651 UTF8 encoded name. 652</UL> 653 654<P> 655Bugs that have been addressed include: 656<UL> 657 <LI> Width of characters is not always determined correctly when wcwidth 658 is used. Revert to using code for the Windows operating system. 659 Reported by Andrew Ho. 660 661 <LI> The call realpath(..., NULL) gives an error in Solaris, which means that 662 we need to allocate memory for storing the resolved path. Reported by 663 Fabian Schmidt. 664 665 <LI> Crash when attempting to bounce a message due to lack of space in 666 allocated space for key menu array. Reported by David Sewell. 667 668 <LI> Crash when a CA certificate failed to load, and user attempted to 669 view certificate information of other certificate authorities. 670 671 <LI> Crash in the S/MIME configuration screen when a user turned off S/MIME, and 672 then re-enabled it. Also crash when attempting to enter the S/MIME 673 configuration screen if S/MIME was turned off. 674 675 <LI> Deactivate some color code from Pico (as standalone editor in the 676 windows version) until I find a way to activate it again. This is 677 not critical and it is not something that PC-Pico must have (some 678 of it already exists in other ways, like color support, what does 679 not exist is the more complex code that Unix-Pico has with color 680 codes for specific colors.) 681 682 <LI> When a message is multipart, and the first part is flowed text, 683 then forwarding the message will set the first part to be flowed, 684 and sent that way even when the option Do Not Send Flowed Text is 685 enabled. Reported by Holger Trapp. 686 687 <LI> When a message/rfc822 part of a message is encoded with 688 Content-Transfer-Encoding: QUOTED-PRINTABLE, Alpine will stop 689 processing that message. Later this causes Alpine to crash because 690 when it displays messages, it assumes that both header and body 691 parts are processed. Reported by Mark Crispin in 2010, in the 692 Alpine-info list (message with subject "crash bug in 693 alpine/mailpart.c:format_msg_att()") with no example, and reported 694 now by Holger Trapp, with an example. 695 696 <LI> In addition to the previous report, Alpine encodes message/rfc822 697 messages as QUOTED-PRINTABLE, in contradiction with RFC 2045, 698 when it receives a report that its encoding is 8bit. We preserve 699 the encoding reported by the IMAP server, and do not encode in 700 QUOTED-PRINTABLE. 701 702 <LI> Update build.bat file to add /DWINVER=0x0501 so that Alpine can 703 build when using Visual Studio 2017. Fix contributed by 704 Ulf-Dietrich Braunmann. 705 706 <LI> When the locale is not set up to UTF-8, alpine might determine the 707 width of a character incorrectly. Reported by Alexandre Fedotov. 708 709 <LI> In some rare cases, when attachments are deleted before saving 710 emails, the filenames will be displayed in RFC1522 representation, 711 instead of in decoded form. Reported and patched by Wang Kang. 712 713 <LI> When colors are edited from the main setup configuration screen, some 714 color settings are not updated until Alpine is restarted. Reported by 715 Andrew Hill. 716 717 <LI> If the first part of a message is multipart/alternative, and the 718 first part of this is also a multipart type, then Alpine might 719 fail to select the first text part when replying to a message. 720 Reported by Lucio Chiappetti. 721 722 <LI> TLS 1.2 works does not work if Alpine is compiled with openssl >= 1.1.0. 723 Reported and patched by Kyle George. 724 725 <LI> If the directory where Alpine saves the certificates is empty, 726 alpine would not create a self-signed certificate to encrypt the 727 password file. 728 729 <LI> S/MIME: The list of public certificates is freed before it is 730 reused when a signature fails to verify. This causes Alpine to 731 crash. Patch submitted by Linus Torvalds. 732 733 <LI> S/MIME: A message could fail to verify its signature even if the 734 certificate was saved when the message was open. Based on a report 735 by David Woodhouse to the RedHat bugzilla system. 736 737 <LI> When there are time changes in the clock, Alpine might go to sleep 738 for big amounts of time while displaying messages in the screen. 739 Reset sleep time to 5 seconds in case it finds it needs to sleep 740 more than 5 seconds or a negative amount of time. 741 742 <LI> Restore recognition of empty directories. It was deleted by mistake 743 when added support for internationalization in folders. Based on a 744 report by Michael Rutter. 745 746 <LI> Alpine stops parsing the mailcap file when it finds an invalid entry. 747 Reported by Matt Roberds to the Debian bug system at 748 <A HREF="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886370">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886370</A>. 749 750 <LI> Crash with error "Lock when already locked" when an attempt to check 751 for new mail on a locked stream that is being used for a save 752 operation. Reported by Carlos E.R. 753 754 <LI> Alpine removes trailing spaces from passwords, making a longin attempt 755 fail. Reported by R. Lyons. 756 757 <LI> Alpine crashes when opening a remote imap folder and computing scores. 758 Reported by Paul DeStefano. 759 760 <LI> When more than one server was given in the server-name configuration 761 option of rldap servers, none of them worked. Reported by Robert Wolf. 762</UL> 763 764<P> 765Version 2.21 addresses bugs found in previous releases and has several 766additions as well. 767 768<P> 769Additions include: 770<UL> 771 <LI> PC-Alpine: New configuration option "Aspell Dictionaries" allows a 772 user to choose the dictionary used to spell check, in case the user 773 communicates in more than one language. Examples of values for the 774 variable are "en_US" or "de_DE", etc. Only the first 10 775 dictionaries are offered. 776 777 <LI> Unix-Alpine: Connect securely to a LDAP server on a secure port. 778 Based on a contribution by Wang Kang. 779 780 <LI> Colors configured in Alpine are inherited in the composer. 781 782 <LI> When Alpine is compiled with password file and SMIME support 783 the password file is encrypted using a private key/public 784 certificate pair. If one such pair cannot be found, one will be 785 created. <A HREF="h_password_file_support">Learn more</A>. 786 787 <LI> Alpine builds with any version of OpenSSL greater than or equal 788 to 1.0.0c. This includes version 1.1.0. Alpine also builds with 789 LibreSSL. 790 791 <LI> New SHORTSUBJECT, SHORTSUBJKEY and SHORTSUBJKEYINIT token for index 792 format, which removes text in the SUBJECT between "[" and 793 "]". 794 795 <LI> New SMARTTIME24 token for index screen. It is close to SMARTDATETIME 796 but it differns in that it gives the time in which the message was 797 sent for messages that are less than a week old. it uses a 24 hour 798 format. 799 800 <LI> Alpine will include attachments when forwarding some 801 multipart/alternative messages for which it did not use to include 802 attachments. 803 804 <LI> New configuration option 805 <a href="h_config_alt_reply_menu"><!--#echo var="FEAT_alternate-reply-menu"--></a> 806 which adds more ways to control features and variables when you 807 start to reply to a message. 808 809 <LI> Added support for RFC 2971 - IMAP ID extension. 810 811 <LI> Add configuration <A href="h_config_ignore_size"><!--#echo var="FEAT_ignore-size-changes"--></A> 812 that allows users to ignore errors in the computation of the size 813 of a message from defective servers. 814 815 <LI> SMIME: Upgrade the default signature digest from sha1 to sha-256, since 816 clients such as Thunderbird do not validate signatures that use sha1 digest. 817 818 <LI> Add the configuration variable "default-directories", which is called 819 <A href="h_config_history"><!--#echo var="VAR_default-directories"--></A> 820 variable saves a list of directories that are readily accessible 821 for save or export of attachments. This makes it easier to save 822 attachments in directories that are hard to navigate to, or that 823 are accessed frequently. 824 825 <LI> When a filename is attached and its name is encoded, the save 826 attachment command will offer to save the file in the encoded form. 827 This might work for some users, but the save command will have a 828 subcommand ^N to decode the file name and save the file with the 829 decoded name. 830 831 <LI> The TAB key allows autocomplete in the Fcc field in the composer headers, 832 as well as autocompletes automatically when only one possibility exists 833 for the ^J attach command. 834 835 <LI> Add support for the "TYPE" and "VALUE" attributes of 836 the html OL tag. 837 838 <LI> Ignore message from smtp server after a successful authentication 839 challenge. 840 841 <LI> When a message is saved in the Form Letter folder, add the ability 842 to save the role being used to compose such message so that settings 843 such as the SMTP server set in the role can be used when sending 844 such form message. Suggested and patched by Frank Doepper. 845 846 <LI> If SSLDIR is defined somehow, do not disable S/MIME if the 847 SSLCERTSDIR is not found. 848 849 <LI> When Alpine sends an attachment, it will set the boundary attribute 850 in lower case, as some SMTP servers, such as those of libero.it 851 reject messages if the boundary attribute is in uppercase. 852 853 <LI> Add the ability to change the private key and certificates used 854 to encrypt a password file in the SMIME setup configuration screen. 855 <A HREF="h_config_smime_password_file_certificates">Learn more</A> 856 857 <LI> SMIME: The ctrl-E command that gives information on the certificate 858 is only available for messages that have a signed or encrypted 859 part. 860 861 <LI> SMIME: If a message contains a RFC822 attachment that is 862 signed/decrypted add the ability to view its SMIME information. 863 864 <LI> SMIME: Certificate information in the S/MIME screen is available 865 for certificates stored in a container. 866 867 <LI> SMIME: Offer the common name of the person, instead of the name of 868 file containing the certificate, as the name to be displayed in the 869 certificate management screen for certificate authorities. 870 Suggested by Matthias Rieber. 871 872 <LI> SMIME: Management of several alternate name (SAN) certificates is 873 improved. When importing a SAN certificate, also import a certificate 874 for the filename, besides for the e-mail addresses in the 875 certificate. Suggested by Matthias Rieber. 876 877 <LI> SMIME: add full year when displaying information about a certificate 878 in the certificate management screen. Suggested by Matthias Rieber. 879 880 <LI> SMIME: sort certificates by some type of alphabetical order in the 881 displayed name. 882 883 <LI> SMIME: Alpine will ask users if they wish to save S/MIME 884 certificates included in signatures, when the option "Validate 885 Using Certificate Store Only" is enabled. If the user does not wish 886 to save it, validation will fail. 887 888 <LI> HTML: Add support for decoding entities in hexadecimal notation. 889 Suggested by Tulipánt Gergely. 890 891 <LI> The "#" command, when used as part of an aggregate 892 operation will allow users to select the role used in either 893 replying, forwarding or replying to the group of selected messages, 894 Suggested by Hisashi T Fujinaka. 895 896 <LI> If the charset of a message can not be determined, use the value set 897 in the <A HREF="h_config_unk_char_set"><!--#echo var="VAR_unknown-character-set"--></A> for its value. 898 899 <LI> Resizing setup screen will redraw screen. 900 901 <LI> Unix Alpine only. Experimental: If Alpine/Pico finds a UCS4 code 902 in the width ambiguous zone, it will use other means to determine 903 the width, such as call wcwidth. 904 905 <LI> Pico: Code reorganization in the search command to make it easier to 906 add subcommands of the search command. 907 908 <LI> Pico: Search command can do a case sensitive match. Use the Ctrl-^ 909 subcommand of the search command to bring this choice into view. 910 911 <LI> Pico: Add the ability to search for strings in the beginning or end 912 of a line. Use the Ctrl-^ subcommand of the search command to bring 913 this choice into view. 914 915 <LI> For a multipart/alternative message, the Take Address command will 916 work on the part that is being read. 917 918 <LI> When sending a message, allow for 512 characters of consecutive 919 non-white space before folding the subject line. 920 921 <LI> Make sure titlebar (the line at the top of the screen) always 922 contains the name of the folder/newsgroup that is open, if this 923 fits in the title. 924 925 <LI> The feature <a href="h_config_scramble_message_id">FEATURE: <!--#echo var="FEAT_scramble-message-id"--></a> 926 will also scramble the name, version and operating system in the 927 message-id header. Based on a contribution by Dennis Davis, which 928 is itself based on a contribution by Mark Hills. 929 930 <LI> Change in logic in imap_set_password function to make Alpine ask if 931 a user wants to save a password before reading the password file. 932 933 <LI> When exporting all parts of a message, if two attachments have the same 934 name, do not overwrite a file more than once, but instead add a counter 935 number to the filename to make a new file that does not exist in the file 936 system. 937 938 <LI> Add the Control-R subcommand to the save command for attachments. 939 This subcommand toggles if the saving will be done in binary mode 940 for text attachments. When a user saves an attachment using binary 941 mode it will be saved as it was sent, otherwise the attachment will 942 be transformed to UTF-8 for further transformation through internal 943 and user defined filters for saving. 944 945 <LI> Add command line argument -smimedir, which allows users to specify 946 the default path for a directory that contains the public, private, 947 and ca directories. This is useful in case a user has a backup of 948 old certificates that cannot be installed in the ~/.alpine-smime 949 dir. 950 951 <LI> Reimplementation of the code that allows the .pinerc file to be a 952 symbolic link by Kyle George from tcpsoft.com to use realpath. 953 954 <LI> When saving an attachment, the "^T" command leads to a screen where the 955 "A" command can be used to add a file. A directory can be added by 956 pressing "^X" after the "A" command. Added after a suggestion by 957 Stefan Goessling. 958 959 <LI> When saving an attachment, the ^Y and ^V commands allow a user to 960 scroll through the history of directories used to save attachments, 961 while preserving the given name of the file. Suggested by Peter 962 Koellner. 963 964 <LI> SMIME: Turn off automatic signing and encrypting of a message when 965 bouncing. Suggested after a discussion with Matthias Rieber. 966 967 <LI> When messages are selected, warn the user if a message that is not 968 selected will be bounced, or if not all selected messages will be 969 bounced. Suggested by Ulf-Dietrich Braumann. 970 971 <LI> The bounce command adds a subcommand to choose a role. 972 973 <LI> When selecting messages by number, the "." character can 974 be used to specify the message on which the cursor is on. 975 976 <LI> When Alpine opens an attachment, it sometimes changes the extension 977 of the file that is being opened and replaces it by another for the 978 same mime type. If Alpine finds that the extension of the file 979 corresponds with the mime type, according to the mime-types file, 980 then it will keep it, and no substitution will be made. 981 982 <LI> Set no restrictions on the length of encoded subjects, but encode 983 words in length of no more than 75 characters. 984</UL> 985 986 987<P> 988Bugs that have been addressed include: 989<UL> 990 <LI> SMIME: Crash when a certificate has an invalid date of validity. Also 991 Alpine will use the function ASN1_TIME_print to determine the date 992 of validity. Reported by Ben Stienstra. 993 994 <LI> SMIME: Crash when attempting to unlock the password file and an 995 incorrect password is entered. 996 997 <LI> SMIME: Crash when checking the signature of a message that contains 998 a RFC822 attached message. Reported by Holger Trapp and Björn 999 Krellner. 1000 1001 <LI> SMIME: Cancelling entering password to unlock key will not reprompt. 1002 1003 <LI> SMIME: fix a bug that did not allow users to transfer certificates to 1004 remote containers. Reported by Matthias Rieber. 1005 1006 <LI> SMIME: certificates included in messages were not being transferred 1007 to a remote container. 1008 1009 <LI> SMIME: Crash if public certificates are located in an inaccessible 1010 remote server and the private key is not available. 1011 1012 <LI> SMIME: Alpine does not remove temporary files created when adding a 1013 CA certificate to a container. Reported by Holger Trapp. 1014 1015 <LI> SMIME: When reading a local certificate, Alpine converts the name 1016 of the certificate to lowercase, which may make Alpine not be able 1017 to read such certificate. Reported by Dennis Davis. 1018 1019 <LI> SMIME: If the option "Remember S/MIME Passphrase" is disabled, then 1020 entering a password to read an encrypted message will make Alpine 1021 forget the key and not ask the password to unlock it again in case 1022 it is necessary to unlock it again. Reported by Ulf-Dietrich 1023 Braumann. 1024 1025 <LI> Alpine would use freed memory while trying to compute the color 1026 of the titlebar. This happened when trying to continue a postponed 1027 message. 1028 1029 <LI> Alpine failed to read an encrypted password file if too many 1030 passwords were saved in the password file. 1031 1032 <LI> When selecting messages while in Threaded Index Screen, some 1033 messages other than top of threads could appear in the index, making 1034 Alpine display messages "out of the screen." 1035 1036 <LI> The index format would be chopped at the position of an unrecognized 1037 token, instead of skipping the token as intended. 1038 1039 <LI> Work in progress: Avoid calling non-safe functions when Alpine 1040 receives a signal. See bug report 1041 <A HREF="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825772">here.</A> 1042 1043 <LI> Crash when attempting to read a message after a bounce command. 1044 In order to produce a crash one needed to use the ^T subcommand and 1045 do a search in a LDAP directory. The crash is produced by changes 1046 to the text in the title bar. Reported by Heinrich Mislik in the 1047 Alpine-info list. 1048 1049 <LI> HTML messages that contain UTF-8 may wrap at the wrong position, 1050 making Alpine not display the correct character at the position 1051 that wrapping is done. Reported by Wang Kang. 1052 1053 <LI> Pico: Searching for a string that is too long causes Pico to crash 1054 in the next search. 1055 1056 <LI> Fix vulnerability in regex library. This only affects those who use 1057 this library, such as the windows version of Alpine. See 1058 <A HREF="http://www.kb.cert.org/vuls/id/695940">http://www.kb.cert.org/vuls/id/695940</A> 1059 for more details. 1060 1061 <LI> Alpine would not set include and lib paths for OpenSSL if this was 1062 installed in /usr/local/ssl. 1063 1064 <LI> If the .pinerc file is a symbolic link, Alpine might not write its 1065 contents when saving its configuration. 1066 1067 <LI> The _INIT_ token does not skip over non-alphanumeric characters in 1068 the name. Reported by Andreas Fehr. 1069 1070 <LI> When opening an INBOX folder in a context different from the 1071 incoming folders collection, from the command line, Alpine would 1072 open the INBOX folder from the incoming folders collection. 1073 1074 <LI> Mismatch in size of UCS and CELL caused a corruption in the 1075 content of a pointer, which made the speller in PC-Alpine get the 1076 content of a word incorrectly. 1077 1078 <LI> Skip testing openssl compatibility version when cross-compilation 1079 is detected. Fix contributed by Antti Seppälä 1080 1081 <LI> Alpine fails to remove temporary files used during a display or sending 1082 filter. Fix contributed by Phil Brooke. 1083 1084 <LI> When the index is in zoomed state, adding new messages to the 1085 selection would not show those messages if those messages are on 1086 top of the current message in the top of the screen. Reported by 1087 Ulf-Dietrich Braumann. In addition, when the user scrolls through 1088 the index, this scroll smoothly, without jumping pages. Reported 1089 by Holger Trapp. 1090 1091 <LI> Crash when reviewing history of saving attachments. 1092 1093 <LI> Crash when canceling a goto command on a local collection that has 1094 not been expanded and attempting to expand such collection. 1095 1096 <LI> Crash in Pico when forwarding messages that contain a direction mark 1097 at the end of a line. Reported by James Mingo. 1098 1099 <LI> Solve compilation errors when Alpine is built with Visual Studio 2015. 1100</UL> 1101 1102 1103<P> 1104Version 2.20 addresses bugs found in previous releases and has several 1105additions as well. 1106 1107<P> 1108Additions include: 1109<P> 1110 1111<UL> 1112 <LI> Upgrade UW-IMAP to Panda IMAP from 1113 <A HREF="https://github.com/jonabbey/panda-imap">https://github.com/jonabbey/panda-imap</A>. 1114 <LI> S/MIME: Add screen to manage certificates. 1115 <LI> S/MIME: Signatures are validated using the user's certificates instead 1116 of the ones included in the message. Behavior can be disabled by 1117 disabling the option <A href="h_config_smime_use_cert_store"> 1118 <!--#echo var="FEAT_smime-use-storey-only"--></A>, which is enabled 1119 by default. 1120 <LI> S/MIME: sign messages using intermediate certificates when needed 1121 and possible. 1122 <LI> S/MIME: validation of certificates for servers that modify signed 1123 content. 1124 <LI> S/MIME: signed and encrypted messages will be signed first and 1125 encrypted second, so that they can be decoded by other clients. 1126 <LI> S/MIME: add the sender certificate to the list of certificates in 1127 encrypted messages to make it possible for the sender to decrypt 1128 the message they sent. 1129 <LI> S/MIME: When transferring certificates to a local container, create 1130 container with default names PublicContainer, PrivateContainer and 1131 CAContainer, as appropriate for these files, unless the user has 1132 provided some other names. 1133 <LI> S/MIME: Forwarding a message will include the signed part as part 1134 of the text and not as a multipart message, just as the reply 1135 command does. 1136 <LI> HTML: Style tag in body of html message causes Alpine to not write 1137 its content until a new </style> 1138 <LI> HTML: <BR>, <BR />, and <BR/> are considered 1139 the same inline tag; the same is valid for the <HR> tag. 1140 <LI> Add support to selective expunge through a subcommand of the 1141 select-apply commands. Read more in the <A 1142 HREF="h_index_cmd_expunge">help</A> for the expunge command. 1143 <LI> Pico: New subcommand of the search command, allows to reverse the 1144 direction of search. 1145 <LI> Unix Alpine: If a password file is defined, and S/MIME is enabled, 1146 the key and certificate used to encrypt the password file are saved 1147 in the ~/.alpine-smime/.pwd directory, or in the directory specified 1148 by the -pwdcertdir command line option. 1149 <A HREF="h_password_file_support">Learn more</A>. 1150 <LI> Add /tls1, /tls1_1, /tls1_2 and /dtls1 to the definition of a 1151 server to use different ways to connect using ssl, for 1152 example {server.com/tls1} will attempt to connect to 1153 server.com at the ssl imap port (port 993) and establish a 1154 connection using TLSv1. These flags can be used in 1155 conjunction with the /ssl flag, the ssl flag is redundant. 1156 Conversely, however, the /ssl flag does not imply any of 1157 these flags; the /ssl flag means SSLv3 or, if not available, 1158 SSLv2 in the SSL port. 1159 <LI> Alpine does not attempt to automatically reopen a collection 1160 that was not opened due to cancellation by the user. 1161 Instead, the user must try to open it explicitly. 1162 <LI> Alpine searches for a certificate that matches an email address in 1163 all addresses in a certificate (instead of just the first 1164 one) but when it tries to unlock the certificate, it asks 1165 for the password for the first email address in that 1166 certificate. 1167 <LI> Style tag in body of html message causes Alpine to not write its content 1168 until a new </style> 1169 <LI> Experimental: Write the content-type of a message in 1170 lowercase, as some non-compliant servers do not understand 1171 uppercase content-type, such as those of GMX.de. 1172 <LI> Experimental: Do not send the RSET command before attempting 1173 to send a message, as this causes a delay in some evily managed 1174 servers. 1175 <LI> Opening a folder updates recent count in maildrops (this 1176 already works for other types of folders) 1177 <LI> Automatically redraw screen after opening an attachment 1178 instead of simply clearing it. 1179 <LI> Pico: Justification works without need of a predefined quote 1180 string. This allows justification of blocks of text that are 1181 indented with spaces. 1182 <LI> Decode the name of attachment names, so they can be written as part 1183 of the description of the part. 1184 <LI> Check bounds and tie strings off to improve security. Contributed 1185 by James Jerkins. 1186 <LI> Replace tabs by spaces in From and Subject fields to control for 1187 size in screen of these fields. Change only in index screen display. 1188 <LI> Aggregate operations allows bouncing a list of messages using a role. 1189 Suggested by Ulf-Dietrich Braumann. 1190 <LI> Disable saving new passwords to the password file. Implemented 1191 by Louis Raphael from dpslabs.com. <A HREF="h_config_disable_password_file_saving">Learn more.</A> 1192 <LI> Makefile: Add $(LIBINTL) to the flags to link rpdump, rpload, 1193 alpined and alpineldap because MAC OSX 10.8 x86_64 needs it. Reported by 1194 Charles M. Register. 1195</UL> 1196 1197 1198<P> 1199Bugs that have been addressed include: 1200<UL> 1201 <LI> Fix _INIT_ token for reply quote string to include support for 8-bit 1202 in personal names. Reported by Lev Gorenstein. 1203 <LI> When writing the .pinerc file, lines were truncated if they were longer 1204 than 10,000 characters. This could cause data corruption, so now lines 1205 are allowed to be of any length. 1206 <LI> S/MIME: signed messages that contained an attachment would not validate. 1207 <LI> S/MIME: signed and encrypted messages from Thunderbird would not 1208 validate. Thanks to Andreas Schamanek for testing, debugging and 1209 advising during the process of fixing this problem. 1210 <LI> S/MIME: Forwarding messages with multipart content-type failed to be signed 1211 with "Error writing pipe" message. Reported by Andreas Schamanek 1212 and Stefan Mueller. 1213 <LI> S/MIME: Certificates are lost when using a pinerc file outside of the 1214 home directory. 1215 <LI> S/MIME: Accessing the S/MIME configuration screen would deinitialize 1216 SMIME making it not possible to sign or encrypt messages. 1217 <LI> S/MIME: Forwarding a signed message might make the body contain mime 1218 information that is not part of the body, and hence making the body 1219 of the message seem wrong. 1220 <LI> S/MIME Alpine would compute incorrectly the signature of a message 1221 that contains 8bit if the option "Enable 8bit ESMTP Negotiation" is 1222 enabled, the message contains 8bit characters and the smtp server 1223 supports 8bit sending. 1224 <LI> When replying to several messages, subject will be decoded first, 1225 and then stripped from re/fwd before they are compared to determine 1226 the subject of the replied message. 1227 <LI> Crash when tcp connection to NNTP server was lost after connection 1228 had been established, but lost immediately afterwards. 1229 <LI> Crash with message "lock when already locked", when painting 1230 an index was based on scores that needed information from a remote 1231 addressbook in the same server as the folder opened. Reported by 1232 Peter Koellner. 1233 <LI> Crash in message/rfc822 attachments encoded in base64. 1234 <LI> Postponed messages whose content-type is text/html, text/enriched and 1235 text/richtext are sent with that content-type, even though, after 1236 resuming composition, Alpine had changed its type to text/plain. 1237 <LI> Alpine cannot handle correctly some characters in the Windows-1256 1238 character set, which might lead to a crash or a corruption in the 1239 screen. Work was done to contain the bug. A more complete fix will 1240 be done in a future release. Reported by Professor Robert Funnell. 1241 <LI> WebAlpine: add _GNU_SOURCE to make pubcookie build. 1242 <LI> WebAlpine: fail to build with debug disabled. Fix from Sam Hathaway. 1243 <LI> Save command did not warn of existence of a message with a deleted 1244 attachment in an aggregate save, unless cursor was positioned on a message 1245 with a deleted attachment. Reported by Florian Herzig. 1246 <LI> Transformation of UTF-8 to MUTF7 was not being done when creating a folder 1247 in an IMAP server. 1248 <LI> DATE tokens were not internally transformed to UTF-8, which made their 1249 values not appear complete in the screen. Reported by Werner Scheinast. 1250 <LI> Fixes to configure script so that it will not require PAM for every system. 1251 <LI> Fix to configure script so that it will use CPPFLAGS instead of 1252 CPPCFLAGS, and so the --with-ssl-include-dir option take effect 1253 during the build. Fix by Ulf-Dietrich Braumann. 1254 <LI> Fix in WebAlpine: do not use deprecated dereference in pointer, 1255 needs to use tcl_getstringresult() instead. Reported by 1256 Ulf-Dietrich Braumann. 1257 <LI> Quoted string in URL Viewers configuration variable were not 1258 unquoted before passing to viewer. 1259 <LI> Fix in configure script to detect location of tcl library; add 1260 /usr/local in FreeBSD and fix a bug in configure script that used 1261 $alpine_TCLINC instead of $alpine_TCLINC/tcl.h. Reported and fixed 1262 by Werner Scheinast. 1263 <LI> Move SSL configurations from UW-IMAP to configure script, and 1264 update OpenSSL configuration for Mac OS X. 1265 <LI> Remove -lregex from linker flags when building --with-supplied-regex. 1266 <LI> When the download of an attachment is interrumpted, Alpine stills 1267 caches what was downloaded, making the download incomplete for 1268 subsequent calls of Alpine attempting to open the attachment. In the 1269 future, Alpine will not cache any downloaded part of the attachment 1270 when it is interrupted. 1271</UL> 1272<P> 1273 1274 1275<P> 1276Version 2.11 addresses bugs found in previous releases and has a few 1277additions as well. 1278 1279<P> 1280Additions include: 1281<P> 1282 1283<UL> 1284 <LI> Alpine requires version 1.0.0c of Openssl to build. 1285 <LI> Increase encryption of S/MIME encrypted messages. 1286 <LI> Pico: Improvements in justification of paragraphs: lines that begin 1287with a quote string, followed by a space were considered individual paragraphs, 1288now they are considered part of a paragraph. Based on earlier joint work 1289with Jeff Franklin. 1290 <LI> Unix Alpine: Allow local .pinerc file to be a symbolic link. 1291 <LI> Experimental extended support of recognition of UTF-8 in urls based on 1292information from <A HREF="http://url.spec.whatwg.org">http://url.spec.whatwg.org</A>. 1293 <LI> Added recognition of ws and wss URIs. 1294 <LI> Add ability to <A HREF="h_config_folder_color">color folder names</A>, 1295 <A HREF="h_config_directory_color">directory names</A>, 1296 and <A HREF="h_config_folder_list_color">text</A> in the FOLDER SCREEN. 1297 <LI> Add the ability to <A HREF="h_config_indextoken_color">color any token</A> 1298used in the display of the INDEX SCREEN. 1299 <LI> New option <A HREF="h_config_preserve_field"><!--#echo var="FEAT_preserve-original-fields"--></A> 1300that adds the ability to preserve To: and Cc: fields when replying to a 1301message, as specified by original sender. 1302 <LI> Add a _SILENT_ token to the <A HREF="h_config_display_filters">list of tokens</A> 1303 for a display filter, so that Alpine will not redraw the screen when it is unnecessary. 1304 <LI> Quota command includes subcommands for printing, forwarding, etc. 1305</UL> 1306 1307<P> 1308Bugs that have been addressed include: 1309<P> 1310<UL> 1311 <LI> Crash when a non-compliant SMTP server closes a connection without a QUIT command. 1312 <LI> Crash when resizing the screen in a configuration screen. 1313 <LI> Do not bail out during a tcp timeout, instead close connection and avoid crash. 1314 <LI> Do not use a shell to open a browser. 1315 <LI> Configure script did not test for crypto or pam libraries. 1316 <LI> Configure script attempted to build web component, even if header file tcl.h was not present. 1317 <LI> Change Cygwin directory separator to "/". 1318 <LI> Alpine could set List- headers, contrary to RFC 2369. 1319</UL> 1320 1321<P> 1322Version 2.10 addresses bugs found in previous releases and has a few 1323additions as well. 1324 1325<P> 1326Additions include: 1327<P> 1328 1329<UL> 1330 <LI> Quota report for IMAP folders that support it (press the "@" command in the index screen of such folder). 1331 <LI> Search a folder for the content of any header with the ";" command. 1332 <LI> Foreign characters are decoded correctly in IMAP folder names. 1333 <LI> Question about breaking connection to slow servers includes their name. 1334 <LI> Internal x-alpine-help: resource locator for sending links to internal help. 1335 <LI> OpenSuse: Alpine find location of OpenSSL certificates. 1336 <LI> Cygwin: Alpine builds without need of patch. 1337 <LI> Recognition of proper mime type for docx, xlsx, and pptx files. 1338 <LI> When composing a message, Alpine will create a new thread when the subject is erased. 1339 <LI> Add support for strong encryption of password file when S/MIME is built in. 1340</UL> 1341 1342<P> 1343Bugs that have been addressed include: 1344<P> 1345 1346<UL> 1347 <LI> Alpine will close a folder after confirming with user their intention and not reopen it. 1348 <LI> Double allocation of memory in Pico. 1349 <LI> Alpine does not give warning of message sent and posted upon receipt by email of message posted in newsgroup. 1350 <LI> Handling of STYLE html parameter may make Alpine not display the content of a message. 1351 <LI> Not recognition of environment variables in some options. 1352 <LI> Not display of login prompt during initial keystrokes. 1353 <LI> justification of long urls breaks them. 1354 <LI> Incorrect New Mail message when envelope is not available. 1355 <LI> Incorrect display of PREFDATE, PREFDATETIME and PREFTIME tokens. 1356 <LI> Crash when resizing the screen after display of LDAP search. 1357 <LI> Crash when redrawing screen while opening a remote folder collection. 1358 <LI> Infinite loop in scrolltool function during notification of new mail. 1359 <LI> No repaint of the screen after midnight was done when the SMARTDATE token is used in the index screen. 1360 <LI> No display of signed and encrypted S/MIME messages. 1361 <LI> Alpine will not build with OpenSSL. 1362 <LI> Crash for double locking in calls to c-client. 1363 <LI> Bad recognition of mime-encoded text may make Alpine not print the subject of a message. 1364 <LI> Ignore the references header when threading messages 1365 <LI> No update of colors in index screen after update to addressbook. 1366</UL> 1367 1368<P> 1369Version 2.01 addresses bugs found in previous releases and has a few 1370additions as well. 1371 1372<P> 1373Additions include: 1374<P> 1375 1376<UL> 1377 <LI> Fixed non-ASCII web alpine handling 1378 <LI> Added web alpine help. 1379 <LI> Allow web alpine inbox on second IMAP server. 1380 <LI> Allow web alpine config reset after bad inbox-path gets set. 1381 <LI> Added web alpine ability to create group contact from contact list members. 1382 <LI> Backed out web alpine coercing of default sort-key of arrival to date/reverse. 1383 <LI> Tidied up web alpine script layout. 1384 <LI> Fixed web alpine status message ordering 1385 <LI> Added web alpine Fcc setting via Contacts in Compose 1386 <LI> Fixed web alpine autodraft attachment issues 1387 <LI> Fixed web alpine problems with recent count maintenance 1388 <LI> Fixed web alpine newmail arrival display in message list 1389 <LI> Added web alpine confirmation to folder create for Move/Copy 1390 <LI> Added web alpine user-domain support 1391 <LI> Fixed web alpine to support INBOX-within-a-collection deletion 1392</UL> 1393 1394<P> 1395Bugs that have been addressed include: 1396<P> 1397 1398<UL> 1399 <LI> In web alpine fixed delete all selected within a search result to reorient 1400 correctly to whole-mailbox message list. 1401 <LI> Fixed web alpine delete in view page to be sensitive to sort 1402 <LI> Fixed web alpine open of folder within directory from folder manager page. 1403 <LI> Fixed web alpine open of folder within directory from left column's recent cache. 1404 <LI> Fixed web alpine problems with spaces in special folder names like Drafts 1405 <LI> Fixed web alpine adding contacts from message list and view 1406 <LI> Fixed web alpine create of non-existent fcc 1407 <LI> Remove mistakenly left debugger statement in web alpine javascript. 1408 <LI> Some UNIX alpine build problems fixed 1409 <LI> Crash in pico and pilot when nl_langinfo returned something unrecognizable 1410 or NULL. Add recognition of "646" to nl_langinfo wrapper. This is returned 1411 by locale charmap call on some Solaris 8 systems. 1412 <LI> MacOS Keychain logins were not working correctly with generic host names, like 1413 imap.gmail.com, as opposed to specific instances like rx-in-209.google.com, causing 1414 new password requests when not needed 1415 <LI> Possible crash in WhereIs command while in FOLDER LIST when cursor is located on the 1416 last folder in the list 1417 <LI> Change to S/MIME get_x509_subject_email so that X509v3 alternative names are 1418 looked for along with the email address 1419 <LI> Changes to configure to get spellcheck options with work with arguments. 1420 <LI> Add change from Mark Crispin of panda.com to at least minimally handle non-ascii hostname 1421 returned by gethostname (iPhone can do this) 1422 <LI> Fixed a bug that prevents a filter that moves a message into a local folder 1423 from also setting the DELETE flag in that moved message. Fix from Eduardo Chappa. 1424 <LI> Changed size of shellpath in open_system_pipe from 32 to MAXPATH. Fix from 1425 Jake Scott of marganstanley.com. 1426 <LI> Buffer overflow bug in c-client's tmail/dmail, fix from Mark Crispin. This 1427 is not used in alpine. 1428 <LI> Imapd server crash from unguarded fs_give in IDLE code, fix from Crispin. 1429 Apparently this causes RIM Blackberry BIS service problems. This is not 1430 used in alpine. 1431 <LI> Tmail uninitialized pointer fix from Neil Hoggarth. Not used in alpine. 1432 <LI> Buffer overflow possibility in RFC822BUFFER routines in c-client library. 1433 Fix from Ludwig Nussel of SUSE and from Crispin. 1434 <LI> Include whole filename in export filename history 1435 <LI> Fix display bug in pico when Replace command is canceled. Fix from Eduardo Chappa. 1436</UL> 1437 1438<P> 1439Version 2.00 1440addressed bugs found in previous releases and had a few additions as well. 1441<P> 1442Additions included: 1443<P> 1444 1445<UL> 1446 <LI> Redesigned Web Alpine interface 1447 <LI> Experimental <A HREF="h_mainhelp_smime">S/MIME support</A> added 1448 in UNIX versions of Alpine 1449 <LI> Attempt to include the attachment filename as part of the name of the 1450 temporary file used when viewing an attachment with an external program. 1451 Add some randomness to that filename to make it hard to predict the filename. 1452 Add a filename extension, usually derived from the type/subtype, to the 1453 temporary filename. This was previously done only on Windows and MacOS X. 1454 <LI> Enhance address completion in the composer (TAB command) so that it looks 1455 through nicknames, fullnames, and addresses from the address book; addresses 1456 from the message being viewed, if any; and the results from 1457 <A HREF="h_direct_config">LDAP Directory Server</A> 1458 lookups for all of the defined directory servers that have the 1459 <A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A> 1460 feature set. 1461 <LI> Make the default character set setting more liberal in what it will accept 1462 from the UNIX nl_langinfo call and the various values of LANG seen in the wild 1463 <LI> Remove the Alpine revision number from the titlebar in released versions 1464 while leaving it there in snapshot versions 1465 <LI> Add a <A HREF="h_config_quell_asterisks">feature</A> to suppress the 1466 display of asterisks when you type a password for Alpine 1467 <LI> Add line wrapping when displaying <EM>PRE</EM> formatted sections of HTML 1468 <LI> When the 1469 <A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A> 1470 feature is turned on convert not only the dates in the index screen but also 1471 the dates in the MESSAGE VIEW 1472</UL> 1473 1474<P> 1475Bugs addressed in the 2.00 release included: 1476<P> 1477 1478<UL> 1479 <LI> Crash when using tab-completion for selecting a Save filename 1480 <LI> Make Web Alpine help text images relative for more portability 1481 <LI> Fixed attach save of html parts in Web Alpine 1482 <LI> Viewing, printing, exporting, replying, and bouncing of message 1483 digests was broken. Replying and bouncing should not have been 1484 allowed at all for digests. It would be nice to have a more standard 1485 index-like view of a message digest but that has not been addressed 1486 with this minor bug fix. 1487 <LI> Adjust wrapping of HTML messages so that the margins specified by 1488 <A HREF="h_config_viewer_margin_left"><!--#echo var="VAR_viewer-margin-left"--></A> and 1489 <A HREF="h_config_viewer_margin_right"><!--#echo var="VAR_viewer-margin-right"--></A> 1490 are observed correctly 1491 <LI> Interrupt of WhereIs command in index was broken 1492 <LI> The <A HREF="h_config_unk_char_set"><!--#echo var="VAR_unknown-character-set"--></A> 1493 option did not work correctly interpreting unknown characters in message headers 1494 <LI> Long address lines could cause blank continuation lines 1495 <LI> Save to a local default INBOX failed if the primary collection was also local, 1496 which it is by default. The save went to ~/mail/inbox instead. 1497 <LI> Make a default save folder of "inbox" always mean the real 1498 inbox, not the inbox in the primary collection 1499 <LI> Address book entries with lots of addresses would be truncated when 1500 entered in the composer with a screen size wider than 270 or so characters 1501 <LI> Some fields in the index screen were truncated when the screen width was 1502 wider than 256 characters 1503 <LI> Crash when TABing to next folder, the next folder with new mail is a POP 1504 folder, and there is a more than 10 minute pause between typing the TAB 1505 and typing the Yes 1506</UL> 1507 1508<P> 1509Version 1.10(962) 1510addressed bugs found in previous releases and had a few additions as well. 1511<P> 1512Additions included: 1513<P> 1514 1515<UL> 1516 <LI> Add the possibility of setting a default role 1517 (see <A HREF="h_role_select">Roles Screen</A>) 1518 which may be convenient if your work flow involves acting in one 1519 role for a while then switching to another role and staying in the 1520 new role for another period of time 1521 <LI> When Saving and the IMAP server problem "Message to save shrank!" 1522 is encountered, ask the user if he or she wants to continue with the 1523 risky Save anyway instead of aborting. This may be helpful if your 1524 IMAP server is broken in this way but be aware that it is possible there 1525 was a real error instead of just a broken server implementation. 1526 <LI> Some configure adjustments for Kerberos detection and 1527 for SCO OpenServer 5 support 1528 <LI> Hide INBOX in a collection if it also appears as an 1529 <A HREF="h_config_enable_incoming">Incoming Folder</A> 1530 <LI> Show asterisks for feedback when the user is typing a password 1531 <LI> Performance improvement for threading of large folders 1532 <LI> Previously, the search used to find 1533 Pattern matches containing To patterns searched for both To 1534 and Resent-To headers. The relatively complicated search this 1535 produces causes problems when using some deficient IMAP servers. 1536 Now the default is to look only for To headers and ignore the 1537 presence of Resent-To. The previous behavior may be restored 1538 with the <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> feature. 1539 <LI> Add an 1540 <A HREF="h_config_unk_char_set"><!--#echo var="VAR_unknown-character-set"--></A> 1541 to help with reading malformed unlabeled messages 1542 <LI><A HREF="h_config_suppress_user_agent"><!--#echo var="FEAT_suppress-user-agent-when-sending"--></A> option added 1543 <LI> Map some Shift-LeftArrow escape sequences to LeftArrow 1544 <LI> Add feature <A HREF="h_config_warn_if_fcc_blank"><!--#echo var="FEAT_warn-if-blank-fcc"--></A> 1545</UL> 1546 1547<P> 1548Bugs addressed in the 1.10(962) release included: 1549<P> 1550 1551<UL> 1552 <LI> Crash when encountering certain errors from an SMTP server 1553 <LI> Crash in composer caused by overflow in replace_pat() 1554 <LI> Hang when authenticating to an SMTP server that fails with a 1555 "connection disconnected" error 1556 <LI> Bug in handling of trailing tab character in flowed text 1557 <LI> Security enhancement for mailcap parameter substitution 1558 <LI> <A HREF="h_config_strip_sigdashes"><!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></A> 1559 did not work if the message being replied to was not flowed text 1560 and <A HREF="h_config_quell_flowed_text"><!--#echo var="FEAT_quell-flowed-text"--></A> 1561 was not turned on 1562 <LI> Don't allow printer to be changed through hidden config screen 1563 if system administrator didn't want it to be allowed 1564 <LI> Attempts are sometimes made to set the Forwarded flag when alpine 1565 should know that it won't work, causing error messages to appear 1566 <LI> A <A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A> 1567 of double-quote double-quote didn't work right 1568 <LI> Quoting wasn't being done to protect special characters from the 1569 MacOS X shell when 1570 <A HREF="h_config_browser"><!--#echo var="VAR_url-viewers"--></A> 1571 was not defined 1572 <LI> On MacOS X message attachments should be shown internally instead of 1573 being shown using the Mail application 1574 <LI> When replying to a message with a charset of X-UNKNOWN Alpine would 1575 sometimes set the outgoing charset to X-UNKNOWN, making the result 1576 unreadable 1577 <LI> When the sending of a message failed lines with leading spaces had one 1578 additional space inserted in each of those lines when the user 1579 was returned to the composer 1580 <LI> The <A HREF="h_index_cmd_whereis">WhereIs</A> command missed some index lines 1581 that contained non-ascii characters because it was truncating the 1582 line being searched so that it was shorter than what was visible on 1583 the screen 1584 <LI> When composing, an attachment with a long name that causes wrapping in 1585 just the wrong place would generate an error and cause the send 1586 of the attachment to fail 1587 <LI> After calling the file browser to attach a file in the composer, a resize 1588 of the window when back in the composer would redraw the last screen that 1589 had been shown in the browser instead of the current composer screen 1590 <LI> Possible crash in index screen when encountering unparsable addresses 1591 or when using one of the PRIORITY tokens or the HEADER token in the 1592 <a href="h_config_index_format"><!--#echo var="VAR_index-format"--></a> 1593 <LI> Problems with Header Color editing if the configuration option 1594 <a href="h_config_customhdr_color"><!--#echo var="VAR_viewer-hdr-colors"--></a> 1595 was inadvertently changed to the Empty Value in the hidden config screen 1596 <LI> When resuming the final postponed message from an Exchange server the user 1597 could get a certificate validation failure because alpine was trying 1598 to validate the canonical name of the folder instead of the name the 1599 user used 1600 <LI> Windows line endings in a mimetypes file on a Unix system cause a 1601 failure to find a match 1602 <LI> Make matching of extension names case independent in mimetypes files 1603 <LI> Windows dialog boxes for entering text were not working correctly 1604 <LI> Replying to or Forwarding multipart/alternative messages which had a 1605 single text/html part did not work well 1606 <LI> Printing the print confirmation page caused a crash 1607 <LI> A To line with a long, quoted personal name could display incorrectly 1608 if it was close to the same width as the screen 1609 <LI> When <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A> 1610 and <A HREF="h_config_incoming_checking_total"><!--#echo var="FEAT_incoming-checking-includes-total"--></A> 1611 are turned on hide (0/0) when the folder is empty 1612 <LI> Folder completion while Saving didn't work if the collection being 1613 saved to was the local home directory 1614</UL> 1615 1616<P> 1617Version 1.00 1618was an evolutionary release based on Pine, which was also 1619developed at the University of Washington. 1620It is upwards-compatible for existing Pine users. 1621 1622<P> 1623Changes included: 1624<P> 1625<UL> 1626 <LI> Ground-up reorganization of source code around addition 1627 of "pith/" core routine library. 1628 <LI> Fundamental improvement in Alpine's internal text handling, which 1629 is now based exclusively on Unicode. This allows displaying incoming 1630 messages and producing outgoing messages in many different languages. 1631 <LI> Ground-up reorganization of build and install procedures 1632 based on GNU Build System's autotools. NOTE, the included IMAP library 1633 build is not based on autotools, so some features will not work. However, 1634 it should get built automatically during the Alpine build process. 1635 <LI> Web-based version included built on TCL designed to run under 1636 a suitable CGI-supporting web server such as Apache. 1637</UL> 1638 1639<P> 1640 1641Details on changes in previous (prerelease) versions of Alpine 1642may be found at the following URL: 1643<P> 1644<CENTER><SAMP><A HREF="http://repo.or.cz/alpine.git">http://repo.or.cz/alpine.git</A></SAMP></CENTER> 1645<P> 1646 1647<HR WIDTH="75%"><P> 1648 1649<H2>Getting Help</H2> 1650<DL> 1651<DT>Online Help</DT> 1652<DD> 1653Every Alpine screen and command has associated help text 1654accessible via the "?" key (or Ctrl-G in text-input contexts). 1655</DD> 1656 1657<DT>Web Help</DT> 1658<DD> 1659The most current source of information about Alpine, 1660including new version availability, is the web page at 1661<P> 1662<CENTER><SAMP><A HREF="http://repo.or.cz/alpine.git">http://repo.or.cz/alpine.git</A></SAMP></CENTER> 1663</DD> 1664</DL> 1665 1666<HR WIDTH="75%"><P> 1667 1668<H2>Additional Information</H2> 1669 1670General Alpine configuration information can be found 1671<A HREF="h_news_config">here</A>. 1672<P> 1673This is revision (<!--#echo var="ALPINE_REVISION"-->) of the Alpine software. 1674Alpine mailbox and <A HREF="https://github.com/jonabbey/panda-imap/">IMAP</A> server 1675access is provided by the IMAP Toolkit Environment (c-client library) 1676version <!--#echo var="C_CLIENT_VERSION"-->. 1677<P> 1678Alpine was developed until 2009 by the Office of Computing 1679& Communications at the University of Washington in Seattle. 1680Since then, the effort of developing Alpine has been continued by 1681a community of volunteers who make good software even better! 1682 1683<P> 1684Alpine Copyright 2013-2021 Eduardo Chappa, 1685<BR> Copyright 2006-2008 University of Washington. 1686 1687<P> 1688Additional legal notices can be found <A HREF="h_news_legal">here</A>, 1689or instead you can find the Apache License, version 2.0 at the web URL: 1690 1691<P> 1692<CENTER><A HREF="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</A></CENTER> 1693 1694<P> 1695<End of Release Notes> 1696</BODY> 1697</HTML> 1698====== h_password_file_support ====== 1699<HTML> 1700<HEAD> 1701<TITLE>Encryption for Password File Support Explained</TITLE> 1702</HEAD> 1703<BODY> 1704<H1>Encryption for Password File Support Explained</H1> 1705 1706Index<BR> 1707<OL> 1708<LI><A HREF="#content">Explanation</A> 1709<LI><A HREF="#example_existing_key">Example of Use of Existing Key and Certificate</A> 1710<LI><A HREF="#example_self_signed">Example of Creating Master Password</A> 1711</OL> 1712 1713<P><A NAME="content">Unix Alpine Only.</A> 1714 1715<P> If your version of Alpine has been built with password file support 1716then you can use a special file to save your passwords, and avoid typing 1717them every time you open a connection to a remote server. 1718 1719<P> If, in addition, your version of Alpine was built with SMIME support, then your 1720password file will be encrypted with a strong key. There are two ways in 1721which this can happen: Alpine will either use a matching private key and 1722public certificate pair that you already own, or it will create one for 1723you, just for purposes of encrypting this file. We describe both processes 1724below. 1725 1726<P> Initially, Alpine will scan your public and private directories for a 1727certificate/private key pair that works. Alpine will pick the first pair 1728that it finds that matches. 1729 1730<P> Once a pair has been chosen, it will be copied to the directory 1731~/.alpine-smime/.pwd, and from then on, Alpine will use the pair found in 1732that directory. The first time this process is done, this directory will 1733be created, a key/certificate pair will be copied to it, from then on 1734this pair will be used to encrypt and decrypt your password file. 1735 1736<P> If you want to use a specific key and certificate pair to encrypt 1737your password file, you can create the directory ~/.alpine-smime/.pwd 1738manually, and then create your preferred key/certificate pair there. 1739Alpine will use this key regardless of if it has expired, or if it is 1740self-signed. These issues do not affect the encryption or decryption 1741of the password file. 1742 1743<P> If you prefer not to use the directory ~/.alpine-smime/.pwd to save 1744your key/certificate pair, you can specify a different one with the 1745-pwdcertdir command line option in Alpine. If the directory specified by 1746this option is not found Alpine will fail to encrypt and decrypt your 1747password file. However if it exists, Alpine will search for a 1748key/certificate pair in that 1749directory, and if it does not find one, it will create one and save it 1750in that directory. 1751 1752<P> Alpine does not care about the names of the key and certificates in 1753this directory, but the private key must have ".key" extension 1754and your public certificate must have the ".crt" extension. The 1755name of the private key will be used in the prompt when you are asked 1756to unlock your key to decrypt your password. 1757 1758<P> If Alpine cannot find a suitable private key and public certificate 1759pair to encrypt your password, it will create one. You will be asked to 1760create a "Master Password" to protect such key. At this moment 1761there are no restrictions on passwords, other than they have to be at 1762least 8 characters long, but future versions of Alpine will include 1763functionality to restrict master passwords, as set up by the administrator 1764of the system in the alpine.conf.fixed file. 1765 1766<P><A NAME="example_existing_key"><B>Example of Use of Existing Key and Certificate</B></A> 1767 1768<P>Assume you have a private key called peter@address.com.key in your, 1769~/.alpine-smime/private directory, and a public certificate called 1770peter@address.com.crt in your ~/.alpine-smime/public directory, and these 1771are your only key/certificate pair. 1772 1773<P> When Alpine starts for the first time, without command line options, 1774it will check if the directory ~/.alpine-smime/.pwd exists, and if not, 1775it will create it. Then it will go through your keys and certificates and 1776find a pair that it can use, and copy the files peter@address.com.key, 1777and peter@address.com.crt to the ~/.alpine-smime/.pwd directory. Alternatively 1778you can do the same by copying these files by yourself. This can be done 1779with the sequence of commands 1780 1781<PRE> 1782mkdir ~/.alpine-smime/.pwd 1783cp ~/.alpine-smime/private/peter@address.com.key ~/.alpine-smime/.pwd 1784cp ~/.alpine-smime/public/peter@address.com.crt ~/.alpine-smime/.pwd 1785</PRE> 1786 1787<P> When Alpine starts, you will be asked the password to unlock your 1788private key with the prompt. 1789 1790<PRE> 1791Enter password of key <peter@address.com> to unlock password file: 1792</PRE> 1793 1794<P> If you prefer to use different names for your private and public keys 1795in the ~/.alpine-smime/.pwd directory, you can do so, but you must 1796preserve the extension of the files. For example, you can use the names 1797private_key.key and public_cert.crt instead. In this case, the prompt you 1798will see when you are asked to unlock your private key will read 1799 1800<PRE> 1801Enter password of key <private_key> to unlock password file: 1802</PRE> 1803 1804<P>Observe that you do not need to use an existing key/certificate pair, 1805and that you can create a new private key/public certificate pair to 1806encrypt and decrypt your password file. Alpine provides a mechanism to 1807change the encryption key for this file in the S/MIME configuration 1808screen. 1809 1810<P><A NAME="example_self_signed"><B>Example of Creating Master Password</B></A> 1811 1812<P> If Alpine cannot find a suitable private key and public certificate pair 1813to encrypt your password file, it will create one. When doing so, it will 1814start the process with the following warning: 1815 1816<PRE> 1817Creating a Master Password for your Password file. 1818</PRE> 1819 1820<P> Then Alpine will ask you to enter your Master Password: 1821 1822<PRE> 1823Create master password (attempt 1 of 3): 1824</PRE> 1825 1826<P> Once you enter this password, and it validates according to system policy, 1827you will be asked to confirm this password. 1828 1829<PRE> 1830Confirm master password (attempt 1 of 3): 1831</PRE> 1832 1833<P> If you input the same password, then Alpine will set that as your 1834Master Password, and you will use this password to unlock your key in the 1835future. 1836 1837<P> If you would like to switch your Master Password in the future, you can 1838do so by creating a new public key and public certificate pair. You can do 1839so in the S/MIME configuration screen, in the "Manage Key and 1840Certificate for Password File" section, simply enter your current 1841password to unlock your current key and then press "C" to create 1842a new key. 1843 1844<P> 1845<End of help> 1846</BODY> 1847</HTML> 1848====== h_network_encryption_security ====== 1849<HTML> 1850<HEAD> 1851<TITLE>Network Encryption Security Explained</TITLE> 1852</HEAD> 1853<BODY> 1854<H1>Network Encryption Security Explained</H1> 1855 1856You can specify which encryption protocol you would like to try when 1857creating a secure connection to a server. Alpine will attempt to use 1858that encryption protocol, but in practice the protocol being used will 1859default to the most secure protocol that both Alpine and the server 1860support. 1861 1862<P> If you use the latest version of OpenSSL, the /ssl modifier to the 1863server definition will use the most secure version of the TLS encryption 1864protocol. The same will be true if you try /tls1_1 or /tls1_2, but in an 1865old version of OpenSSL (pre 1.1.0 series) /tls1_1 might mean to use 1866version 1.1 of the TLS protocol. 1867 1868<P> You will never go wrong by using the /ssl modifier. At the time of 1869this writing OpenSSL had released version 1.1.1, with support for 1870TLS version 1.3. If your version of OpenSSL does not support this version 1871of the TLS protocol, then the /tls1_3 modifier will only mean to use 1872the most secure version of the TLS protocol that OpenSSL and the 1873server can negotiate. In future versions of OpenSSL, /tls1_3 might mean 1874to try to negotiate a higher version of the TLS protocol. 1875 1876<P> In order to avoid confusion, the /ssl flag is the best way to guarantee 1877the highest encryption protocol available, and it is the recommended 1878modifier to the server definition to create a secure encrypted connection. 1879 1880<P> 1881<End of help> 1882</BODY> 1883</HTML> 1884====== h_gmail_configuration ====== 1885<HTML> 1886<HEAD> 1887<TITLE>Configuring Access to Gmail Using XOAUTH2</TITLE> 1888</HEAD> 1889<BODY> 1890<H1>Configuring Access to Gmail Using XOAUTH2</H1> 1891 1892Gmail allows you to access their IMAP and SMTP server using either the XOAUTH2 1893or OAUTHBEARER authentication method. You can choose any of them. A sample configuration for reading 1894incoming mail is 1895 1896<P> 1897inbox-path = {imap.gmail.com/ssl/user=YourId@gmail.com/auth=xoauth2}INBOX<BR> 1898smtp-server = smtp.gmail.com/ssl/user=YourId@gmail.com/auth=xoauth2 1899 1900<P> 1901Note that you can substitute /auth=xoauth2 by /auth=oauthbearer. 1902 1903<P> 1904Gmail implements the authorize method. This means that in order to use xoauth2, you must 1905open a URL, login to your Gmail account, and authorize Alpine to access your email. As a 1906result of this process, you will get a <B>code</B>, which you must input back into Alpine. 1907Once you have done that, Alpine will be able to get a refresh and access token, which 1908Alpine will use later to read and send email. 1909 1910<P> 1911<End of help> 1912</BODY> 1913</HTML> 1914====== h_outlook_configuration ====== 1915<HTML> 1916<HEAD> 1917<TITLE>Configuring Access to Outlook Using XOAUTH2</TITLE> 1918</HEAD> 1919<BODY> 1920<H1>Configuring Access to Outlook Using XOAUTH2</H1> 1921 1922Outlook allows you to access their IMAP and SMTP server using the XOAUTH2 1923authentication method. A sample configuration for reading incoming mail is 1924 1925<P> 1926inbox-path = {outlook.office365.com/ssl/user=YourId@outlook.com/auth=xoauth2}INBOX<BR> 1927smtp-server = smtp.office365.com/submit/user=YourId@outlook.com/auth=xoauth2 1928 1929<P> 1930Outlook implements the authorize and device methods to get your authorization to access 1931your account. Alpine uses by default the device method, so try that one first. 1932 1933<P> 1934<End of help> 1935</BODY> 1936</HTML> 1937====== h_yahoo_configuration ====== 1938<HTML> 1939<HEAD> 1940<TITLE>Configuring Access to Yahoo! Using XOAUTH2</TITLE> 1941</HEAD> 1942<BODY> 1943<H1>Configuring Access to Yahoo! Using XOAUTH2</H1> 1944 1945Yahoo! allows you to access their IMAP and SMTP server using either the XOAUTH2 or 1946OAUTHBEARER authentication method. You can choose any of them. A sample configuration for 1947reading incoming mail is 1948 1949<P> 1950inbox-path = {imap.mail.yahoo.com/ssl/user=YourId@yahoo.com/auth=xoauth2}INBOX<BR> 1951smtp-server = smtp.mail.yahoo.com/ssl/user=YourId@yahoo.com/auth=xoauth2 1952 1953<P> 1954Note that you can substitute /auth=xoauth2 by /auth=oauthbearer. 1955 1956<P> 1957Yahoo! implements the authorize method. This means that in order to use xoauth2, you must 1958open a URL, login to your Yahoo! account, and authorize Alpine to access your email. As a 1959result of this process, you will get a <B>code</B>, which you must input back into Alpine. 1960Once you have done that, Alpine will be able to get a refresh and access token, which 1961Alpine will use later to read and send email. 1962 1963<P> 1964<End of help> 1965</BODY> 1966</HTML> 1967====== h_yandex_configuration ====== 1968<HTML> 1969<HEAD> 1970<TITLE>Configuring Access to Yandex Using XOAUTH2</TITLE> 1971</HEAD> 1972<BODY> 1973<H1>Configuring Access to Yandex Using XOAUTH2</H1> 1974 1975Yandex allows you to access their IMAP and SMTP server using the XOAUTH2 1976authentication method. A sample configuration for reading incoming mail is 1977 1978<P> 1979inbox-path = {imap.yandex.com/ssl/user=YourId@yandex.com/auth=xoauth2}INBOX<BR> 1980smtp-server = smtp.yandex.com/ssl/user=YourId@yandex.com/auth=xoauth2 1981 1982<P> 1983Yandex implements the authorize method. This means that in order to use xoauth2, you must 1984open a URL, login to your Yandex account, and authorize Alpine to access your email. As a 1985result of this process, you will get a <B>code</B>, which you must input back into Alpine. 1986Once you have done that, Alpine will be able to get a refresh and access token, which 1987Alpine will use later to read and send email. 1988 1989<P> 1990<End of help> 1991</BODY> 1992</HTML> 1993====== h_xoauth2 ====== 1994<HTML> 1995<HEAD> 1996<TITLE>XOAUTH2 Authenticator Explained</TITLE> 1997</HEAD> 1998<BODY> 1999<H1>XOAUTH2 Authenticator Explained</H1> 2000 2001The XOAUTH2 authenticator method is a way in which you can sign in to your 2002account to read and send email. This method is different from the traditional 2003username/password that users are accustomed to, and it needs to be set up 2004by the user. This text will help you understand this authentication method. 2005 2006<P> A quick list of services supported by Alpine are (follow each link for 2007specific configuration instructions) 2008 2009<UL> 2010<LI> <A href="h_gmail_configuration">Gmail</A> 2011<LI> <A href="h_outlook_configuration">Outlook</A> 2012<LI> <A href="h_yahoo_configuration">Yahoo!</A> 2013<LI> <A href="h_yandex_configuration">Yandex</A> 2014</UL> 2015 2016<P> 2017The most important difference between this method and other authentication 2018methods is what happens if someone steals your credentials. This method is 2019attached to three components: Your username, your password and your email 2020program. 2021 2022<P> 2023At the beginning of this process, the developer of the email program 2024registers the email program with the email service provider (Gmail, 2025Outlook, etc.) In return, the email service provider creates a client-id. 2026In addition, some services provide a client-secret. 2027Since Alpine is an open source program, these values are part 2028of the source code, and are known to everyone, and cannot be obfuscated. 2029 2030<P> 2031After a program has been registered with an email service provider, the 2032user must authorize the email program access to their email account in 2033that service. Alpine helps you do that, but it cannot do all the process 2034for you, and you will need to use an external web browser to authorize 2035Alpine to read and send email. 2036 2037<P> 2038This part of the process is simple. Alpine creates a URL based on the id 2039and secret created by the email service, which the user opens. Once the 2040URL has been opened, the user signs in to the server, and once signed into 2041the account, the user is asked to authorize Alpine access to the email 2042account. If the user agrees, an "<I>Access Code</I>" will be 2043generated. 2044 2045<P> 2046An Access Code is a very long string, and so the recommendation is to copy 2047and paste this code back into Alpine, at the time Alpine is helping you 2048set up this authenticator. This part of the process is done only once per 2049email program (If you run Alpine in several computers, you would do this 2050once per computer. Each computer gets its own Access Code.) 2051 2052<P> 2053Once Alpine has an Access Code, it goes back internally to the email 2054service and asks it to generate two strings, called the "<I>Refresh 2055Token</I>" and the "<I>Access Token</I>". This part is 2056invisible to the user, and they will never see it, but in order for you to 2057understand what to do in case you lose them, you need to understand their 2058use. 2059 2060<P> 2061The <I>Access Token</I> is the equivalent of a temporary password. It 2062allows the user to access (and reaccess as many times as they would like) 2063their email account for a limited amount of time, typically 1 hour after 2064it was issued. After that time expires, users need a new Access Token. 2065 2066<P> 2067The <I>Refresh Token</I> is the equivalent of a password generator. With 2068this token, Alpine can go to the email service provider and request a new 2069Access Token. This part of the process does not need user intervention, 2070anyone can do this, as long as they have the Refresh Token, program id and 2071program secret, so it is important that users keep their Refresh Token as 2072secure as they can. 2073 2074<P> 2075Given that the Refresh Token and the Access Token are long strings, users 2076are not supposed to be able to memorize them and recall them later. Alpine 2077will store them in the password file, should a user have one. Otherwise, 2078the user will have to create one each time they run Alpine, starting by 2079creating the Access Code all over each time they try to sign in to their 2080email account. When Alpine is compiled with SSL and password file support, 2081it will default to saving this information using encryption and under a 2082master password, so unless they have made changes to this process, their 2083Refresh and Access Tokens are saved securely and persist from one session 2084to the next. 2085 2086<P> 2087Should any person steal your Refresh Token, you must login to your account 2088with your username and password and revoke Alpine authorization to your 2089account. This is enough to stop the person who stole your Refresh Token 2090from accessing your email service. In the case of Gmail, changing your 2091password will invalidate your Refresh Token, and this will be enough to 2092prevent others from using a stolen Refresh Token. Consult with your email 2093service provider to learn what you can do if someone steals your Refresh 2094Token. 2095 2096<P> 2097If, for any reason, Alpine cannot sign in to your email service for two 2098consecutive times with Access Codes generated by your Refresh Token, it 2099will remove the Refresh Token from your password file, forcing you to get 2100a new one, by getting an Access Code first, and granting authorization to 2101Alpine to access your email once again. 2102 2103<P> 2104This implementation of XOAUTH2 knows the list of servers that it can 2105access using the same credentials, so Alpine will be able to read and send 2106emails using the same Access Token. You will not have to create 2107Access and Refresh Tokens for the IMAP and SMTP servers separately. 2108 2109<P> 2110<End of help> 2111</BODY> 2112</HTML> 2113====== h_xoauth2_config_screen ====== 2114<HTML> 2115<HEAD> 2116<TITLE>XOAUTH2 Configuration Screen</TITLE> 2117</HEAD> 2118<BODY> 2119<H1>XOAUTH2 Configuration Screen</H1> 2120 2121The XOAUTH2 configuration screen helps you connect your client-id and 2122other configuration information about the service you want to use with 2123Alpine. 2124 2125<P> Alpine provides a default configuration for you. For some providers 2126this configuration does not work, and requires you to get your own 2127Client-ID for Alpine. Depending on the service, you might need extra information, 2128such as a Client-Secret or a Tenant. 2129 2130<P> If the default configuration of Alpine does not work for you, you can simply 2131replace the default configuration of Alpine by your new configuration. If for 2132any reason you need to have a second client-id, you can use the ^A command to 2133add a new configuration for one of the supported services by Alpine. 2134 2135<P> If you wish to delete a configuration for a service, place the cursor 2136on the configuration you want to delete and press ^D. 2137 2138<P> When you have more than one client-id for the same service, is is convenient 2139to fill up the username field. This will tell Alpine that that specific configuration 2140is to be used with the username(s) specified in that variable. If Alpine cannot 2141determine which configuration to use, it will ask you to select the correct 2142Client-ID for your connection. This could happen when you are trying to login to 2143your account. The client-id you select will be used by Alpine for that and future 2144connections to that server. 2145 2146 2147<P> 2148<End of help> 2149</BODY> 2150</HTML> 2151====== h_tls_failure_details ====== 2152<HTML> 2153<HEAD> 2154<TITLE>Certificate Validation Details</TITLE> 2155</HEAD> 2156<BODY> 2157<H1>Certificate Validation Details</H1> 2158 2159This screen gives details as to why the certificate validation failed: the 2160name of the desired server system; the reason for failure; and the name on 2161the certificate. This is primarily of interest to experts. 2162 2163<P> 2164<End of help> 2165</BODY> 2166</HTML> 2167====== h_tls_failure ====== 2168<HTML> 2169<HEAD> 2170<TITLE>TLS or SSL Failure</TITLE> 2171</HEAD> 2172<BODY> 2173<H1>TLS or SSL Failure</H1> 2174 2175An attempt was made to establish a secure, encrypted connection to the 2176server system using either Transport Layer Security (TLS) or the older 2177Secure Sockets Layer (SSL). This attempt failed. 2178 2179<P> 2180You should contact your server system management for more assistance. 2181The problem is probably at the server system and not in Alpine or your local 2182system. The text in this screen may be helpful for the server system 2183management in debugging the problem, 2184 2185<P> 2186<End of help> 2187</BODY> 2188</HTML> 2189====== h_tls_validation_failure ====== 2190<HTML> 2191<HEAD> 2192<TITLE>TLS and SSL Certificate Validation Failures</TITLE> 2193</HEAD> 2194<BODY> 2195<H1>TLS and SSL Certificate Validation Failures</H1> 2196 2197An attempt was made to establish a secure, encrypted connection to the 2198server system using either Transport Layer Security (TLS) or the older 2199Secure Sockets Layer (SSL). 2200 2201<P> 2202An important part of this procedure is server certificate validation. A 2203server certificate is an "electronic identification card" for the server 2204system that is signed by a well-known certificate authority (CA). Alpine 2205compares the server system identity in the server certificate with the 2206name of the server system to which it is trying to connect. Alpine also 2207verifies that the CA signature is authentic. 2208 2209<P> 2210Some common failure conditions are: 2211<P> 2212 2213<UL> 2214 <LI> [UNIX Alpine] Self signed certificate. This means that the server system 2215signed its own certificate. This does not necessarily indicate anything 2216bad; the server operators may simply have elected to not purchase a 2217signed certificate from a certificate authority. 2218 2219 <LI> [UNIX Alpine] Unable to get local issuer certificate. This means that 2220the signature on the server system is from an unknown certificate authority. 2221It can also mean that no certificate authority certificates have been 2222installed on the local UNIX system. 2223 2224 <LI> [PC Alpine] Self-signed certificate or untrusted authority. This is 2225the same as either of the above two conditions in UNIX Alpine. Note that 2226Windows systems typically have a full set of certificate authority 2227certificates installed, so it is more likely to be a self-signed 2228certificate than an unknown certificate authority. 2229 2230 <LI> Server name does not match certificate. This means that the server 2231presented a proper signed certificate for a name other than the desired 2232name. 2233</UL> 2234 2235<P> 2236Any of these conditions can indicate that you are being attacked and have 2237been directed to an imposter server that will record your password and 2238your private mail messages. It can also mean something innocuous. 2239 2240<P> 2241If you are certain that the problem is innocuous, you can append the 2242option 2243 2244<P> 2245<CENTER><SAMP>/novalidate-cert</SAMP></CENTER> 2246<P> 2247 2248to the server system name where it appears in your configuration (e.g. the 2249<A HREF="h_config_inbox_path"><!--#echo var="VAR_inbox-path"--></A>, 2250a folder-collection, or a news or SMTP server). This will 2251disable certificate validation. On the other hand, if you are attacked, 2252you will get no warning if you do this. 2253 2254<P> When you get an error indicating a self-signed certificate from the 2255remote server, you can download and install the certificate for that 2256server. Avoid using the /NoValidate-Cert modifier. Alpine cannot help you 2257with this process because certificates are part of the system and are not 2258under the control of the user. Find directions on how to download and 2259install certificates for your system using your favorite search engine. 2260 2261<P> 2262<End of Cert Validation Failures help> 2263</BODY> 2264</HTML> 2265====== h_oauth2_start ====== 2266<HTML> 2267<HEAD> 2268<TITLE>Setting up XOAUTH2 Authentication</TITLE> 2269</HEAD> 2270<BODY> 2271<H1>Setting up XOAUTH2 Authentication</H1> 2272 2273You are trying to connect to a server that uses the XOAUTH2 method of 2274authentication. 2275 2276<P> 2277In order to set this up, you need to authenticate in the target server 2278and authorize Alpine to access your email account. 2279 2280<P> 2281After you have authorized Alpine, the server will generate an 2282"access code." In order to use this code, press 'C' 2283and copy and paste this code back into Alpine. 2284 2285<P> 2286After you have input the code, Alpine will conclude logging you into your 2287account. 2288 2289<P> 2290<End of setting up XOAUTH2 Authentication help> 2291</BODY> 2292</HTML> 2293====== h_release_tlscerts ====== 2294<HTML> 2295<HEAD> 2296<TITLE>TLS and SSL usage note</TITLE> 2297</HEAD> 2298<BODY> 2299<H1>TLS and SSL usage note</H1> 2300 2301<P> 2302When using Alpine from Unix or Windows 2000, 2303server certificates must be signed by a trusted certificate authority. 2304You may relax this requirement (at the cost of some security) by using 2305the 2306<A HREF="h_folder_server_syntax">NoValidate-Cert</A> 2307modifier in the mailbox name. 2308 2309<P> 2310<CENTER><SAMP>{foo.example.com/novalidate-cert}INBOX</SAMP></CENTER> 2311<P> 2312 2313The fully-qualified host name of the server should be used 2314so that it matches the host name in the server certificate. 2315<P> 2316Here is an example of a host specification that directs Alpine to use 2317the SSL port (993) and an encrypted data stream. 2318<P> 2319<CENTER><SAMP>{foo.example.com/ssl}INBOX</SAMP></CENTER> 2320<P> 2321<End of TLS usage help> 2322</BODY> 2323</HTML> 2324====== h_news_config ====== 2325<HTML> 2326<HEAD> 2327<TITLE>Alpine Configuration</TITLE> 2328</HEAD> 2329<BODY> 2330<H1>Alpine Configuration</H1> 2331 2332<H2>Using Environment Variables</H2> 2333 2334The values of Alpine configuration options may include environment variables 2335that are replaced by the value of the variable at the time Alpine is run 2336(and also at the time the config option is changed). 2337The syntax to use environment variables is a subset of the common Unix 2338shell dollar-syntax. 2339For example, if 2340 2341<P><CENTER><SAMP>$VAR</SAMP></CENTER><P> 2342 2343appears in the value of an Alpine configuration option it is looked up in the 2344envirom ent (using getenv("VAR")) and its 2345looked-up value replaces the <SAMP>$VAR</SAMP> part of the option value. 2346To include a literal dollar sign you may precede the dollar sign with another 2347dollar sign. 2348In other words, if the text 2349 2350<P><CENTER><SAMP>$$text</SAMP></CENTER><P> 2351 2352is the value of a configuration option, it will be expanded to 2353 2354<P><CENTER><SAMP>$text</SAMP></CENTER><P> 2355 2356and no environment lookup will be done. 2357For Unix Alpine it will also work to use a backslash character to 2358escape the special meaning of the dollar sign, but $$ is preferable since 2359it works for both PC-Alpine and Unix Alpine, allowing the configuration option 2360to be in a shared configuration file. 2361<P> 2362 2363This all sounds more complicated than it actually is. 2364An example may make it clearer. 2365Unfortunately, the way in which environment variables are set is OS-dependent 2366and command shell-dependent. 2367In some Unix command shells you may use 2368 2369<P><CENTER><SAMP>PERSNAME="Fred Flintstone"</SAMP></CENTER><P> 2370 <CENTER><SAMP>export PERSNAME</SAMP></CENTER><P> 2371 2372Now, if you use Alpine's Setup/Config screen to set 2373 2374<P><CENTER><SAMP><!--#echo var="VAR_personal-name"-->=$PERSNAME</SAMP></CENTER><P> 2375 2376the <SAMP>$PERSNAME</SAMP> would be replaced by <SAMP>Fred Flintstone</SAMP> 2377so that this would be equivalent to 2378 2379<P><CENTER><SAMP><!--#echo var="VAR_personal-name"-->=Fred Flintstone</SAMP></CENTER><P> 2380 2381Note, environment variable substitution happens after configuration 2382options that are lists are split into the separate elements of the list, 2383so a single environment variable can't contain a list of values. 2384 2385<P> 2386The environment variable doesn't have to be the only thing 2387after the equal sign. 2388However, if the name of the variable is not at the end of the line or 2389followed by a space (so that you can tell where the variable name ends), 2390it must be enclosed in curly braces like 2391 2392<P><CENTER><SAMP>${VAR}</SAMP></CENTER><P> 2393 2394It is always ok to use the braces even if you don't need to. 2395<P> 2396It is also possible to set a default value for an environment variable. 2397This default value will be used if the environment variable is not 2398set (that is, if getenv("VAR") returns NULL). 2399The syntax used to set a default value is 2400 2401<P><CENTER><SAMP>${VAR:-default value}</SAMP></CENTER><P> 2402 2403If the config file contains 2404 2405<P><CENTER><SAMP>personal-name=${VAR:-Fred Flintstone}</SAMP></CENTER><P> 2406 2407then when Alpine is run <SAMP>VAR</SAMP> will be looked up in the environment. 2408If <SAMP>VAR</SAMP> is found then <SAMP>personal-name</SAMP> will have 2409the value that <SAMP>VAR</SAMP> was set to, otherwise, 2410<SAMP>personal-name</SAMP> will be set to <SAMP>Fred Flintstone</SAMP>, 2411the default value. 2412(Note that the variable is called "personal-name" in the config 2413file but is displayed in the config screen as 2414"<!--#echo var="VAR_personal-name"-->". 2415In general, the value that goes into a config file is never exactly the 2416same as the value you see on the screen.) 2417 2418<P> 2419An example where an environment variable might be useful is the 2420variable <SAMP>Inbox-Path</SAMP> in the global configuration file. 2421Suppose most users used the server 2422 2423<P><CENTER><SAMP>imapserver.example.com</SAMP></CENTER><P> 2424 2425but that there were some exceptions who used 2426 2427<P><CENTER><SAMP>altimapserver.example.com</SAMP></CENTER><P> 2428 2429In this case, the system manager might include the following line in 2430the systemwide default Alpine configuration file 2431 2432<P><CENTER><SAMP>Inbox-Path=${IMAPSERVER:-imapserver.example.com}</SAMP></CENTER><P> 2433 2434For the exceptional users adding 2435 2436<P><CENTER><SAMP>IMAPSERVER=altimapserver.example.com</SAMP></CENTER><P> 2437 2438to their environment should work. 2439<P> 2440Another example might be the case where a user has to use a different 2441SMTP server from work and from home. 2442The setup might be something as simple as 2443 2444<P><CENTER><SAMP>smtp-server=$SMTP</SAMP></CENTER><P> 2445 2446or perhaps a default value could be given. 2447Note that, as mentioned above, the variable <SAMP>SMTP</SAMP> cannot contain 2448a list of SMTP servers. 2449<P> 2450 2451<H2>Configuration precedence</H2> 2452 2453There are several levels of Alpine configuration. Configuration values at 2454a given level override corresponding values at lower levels. In order of 2455increasing precedence: 2456<P> 2457<UL> 2458 <LI> built-in defaults 2459 <LI> system-wide 2460<!--chtml if pinemode="os_windows"--> 2461 config file from command line or provided 2462 by "PINECONF" environment variable 2463<!--chtml else--> 2464 alpine.conf file 2465<!--chtml endif--> 2466 <LI> personal configuration file 2467 <LI> personal exceptions configuration file 2468 <LI> command-line options 2469 <!--chtml if pinemode="os_windows"--><!--chtml else--> 2470 <LI> system-wide alpine.conf.fixed file<!--chtml endif--> 2471</UL> 2472<P> 2473The values in both the personal configuration file and the 2474<A HREF="h_config_exceptions">exceptions</A> 2475configuration file may be set using the Setup command. 2476Setup/Config is the command to change most of the personal configuration 2477options. 2478The other Setup subcommands are also used to change the configuration, 2479for example, Setup/AddressBook, Setup/Rules, and so on. 2480Changing the personal exceptions configuration is very similar. 2481To change a value in the Config screen you would use the command 2482Setup/eXceptions/Config. 2483Likewise for the other Setup subcommands (Setup/eXceptions/Rules and so on). 2484<P> 2485There are a couple exceptions to the rule that configuration values are replaced 2486by the value of the same option in a higher-precedence file. 2487The Feature-List variable has values that are additive, but can be 2488negated by prepending "no-" in front of an individual feature name. 2489So for features, each individual feature's value is replaced by the value 2490of the same feature in a higher-precedence file. 2491Note that this is done automatically for you when you change these values via 2492the Setup/Config command. 2493The other exception to the <EM>replace</EM> semantics happens when you 2494use <A HREF="h_config_inheritance">configuration inheritance</A> 2495for option lists. 2496<P> 2497 2498<H2>File name defaults</H2> 2499 2500Notes:<P> 2501 2502<BR> <exe dir> = directory where pine.exe found. 2503<BR> <pinerc dir> = directory where pinerc found. 2504<BR> # = default file name is overridable in pinerc. 2505<BR> $HOME, if not explicitly set, defaults to root of the current drive. 2506<BR> $MAILCAPS, if set, is used in lieu of the default mailcap search paths. 2507<BR> + between the mailcap paths implies that the two files are combined. 2508<BR> ; between other default paths implies that the first one found is used. 2509</P> 2510Alpine looks for most support files in the same directory it finds its 2511personal configuration file (pinerc). The -p command-line flag may be 2512used to specify a particular path name for the pinerc file. If a 2513pinerc file does not exist, it will be created (if directory permissions 2514allow). In PC-Alpine, if -p or $PINERC are not defined, Alpine will look 2515in $HOME\PINE and the directory containing the PINE.EXE. If a PINERC 2516file does not exist in either one, it will create one in the first of those 2517two directories that is writable. In detail: 2518<PRE> 2519 2520PC-Alpine: 2521 2522 executable <DOS search path>\pine.exe 2523 help index <exe dir>\pine.ndx 2524 help text <exe dir>\pine.hlp 2525 2526 pers config $PINERC ; $HOME\pine\PINERC ; <exe dir>\PINERC 2527 except config $PINERCEX ; $HOME\pine\PINERCEX ; <exe dir>\PINERCEX 2528 global cfg $PINECONF 2529 2530 debug <pinerc dir>\pinedebg.txtN 2531 crash <pinerc dir>\pinecrsh.txt 2532 signature# <pinerc dir>\pine.sig 2533 addressbook# <pinerc dir>\addrbook 2534 mailcap# <pinerc dir>\mailcap + <exe dir>\mailcap 2535 mimetypes# <pinerc dir>\mimetype + <exe dir>\mimetype 2536 newsrc# $HOME\newsrc (if exists, else) <pinerc dir>\newsrc 2537 sentmail# $HOME\mail\sentmail.mtx 2538 postponed# $HOME\mail\postpond.mtx 2539 interrupted $HOME\mail\intruptd 2540 2541Unix Alpine: 2542 2543 executable <Unix search path>/pine 2544 persnl cfg ~/.pinerc 2545 except cfg ~/.pinercex 2546 global cfg <!--#echo var="PINE_CONF_PATH"--> 2547 fixed cfg <!--#echo var="PINE_CONF_FIXED_PATH"--> 2548 local help <!--#echo var="PINE_INFO_PATH"--> 2549 2550 interrupted ~/.pine-interrupted-mail 2551 debug ~/.pine-debugN 2552 crash ~/.pine-crash 2553 newsrc# ~/.newsrc 2554 signature# <pinerc dir>/.signature 2555 addressbook# <pinerc dir>/.addressbook 2556 postponed# ~/mail/postponed-msgs 2557 sentmail# ~/mail/sent-mail 2558 mailcap# ~/.mailcap + /etc/mailcap 2559 + /usr/etc/mailcap + /usr/local/etc/mailcap 2560 mimetypes# ~/.mime.types + /etc/mime.types + /usr/local/etc/mime.types 2561 2562 news-spool varies across Unix flavors, e.g. /var/spool/news or /usr/spool/news 2563 active-news varies across Unix flavors, e.g. /usr/lib/news/active 2564 lock files /tmp/.<!--#echo var="MAIL_SPOOL_LOCK_PATH"--> 2565 inbox <!--#echo var="MAIL_SPOOL_PATH"--> 2566 password /etc/passwd 2567 2568Unix Alpine and PC-Alpine: 2569 2570 .ab* remote addressbook support files 2571 a[1-9]* temporary (while Alpine is running) addressbook files 2572 2573</PRE> 2574<P> 2575 2576<H2>Mailcap files</H2> 2577 2578Alpine honors the mailcap configuration system for specifying external 2579programs for handling attachments. The mailcap file maps MIME attachment 2580types to the external programs loaded on your system that can display 2581and/or print the file. A sample mailcap file comes bundled with the Alpine 2582distribution. It includes comments that explain the syntax you need to 2583use for mailcap. With the mailcap file, any program (mail readers, 2584newsreaders, WWW clients) can use the same configuration for handling 2585MIME-encoded data. 2586<P> 2587 2588<H2>MIME-Types files</H2> 2589 2590Alpine uses mime-types files (.mime.types or MIMETYPE) to determine 2591what Content-Type to use for labeling an attached file, based on 2592the file extension. That is, this file provides a mapping between 2593filename extensions and MIME content-types. 2594<P> 2595 2596<H2>Environment variables</H2> 2597 2598PC-Alpine uses the following environment variables: 2599<DL> 2600<DT>PINERC</DT> 2601<DD>Optional path to pinerc file.</DD> 2602<DT>PINERCEX</DT> 2603<DD>Optional path to personal exceptions configuration file.</DD> 2604<DT>PINECONF</DT> 2605<DD>Optional path to global pine config file.</DD> 2606<DT>HOME</DT> 2607<DT>TMPDIR, TMP, or TEMP</DT> 2608<DT>COMSPEC</DT> 2609<DT>MAILCAPS</DT> 2610<DD>A <B>semicolon</B> delimited list of path names to mailcap files.</DD> 2611<DT>USER_DICTIONARY</DT> 2612<DD>Used to specify the file to contain the user's spell check 2613dictionary. The default is <SAMP>DICT.U</SAMP> in the same 2614directory as the <SAMP>SPELL32.DLL</SAMP></DD> 2615</DL> 2616 2617Unix Alpine uses the following environment variables: 2618<DL> 2619<DT>TERM</DT> 2620<DD>Tells Alpine what kind of terminal is being used.</DD> 2621<DT>DISPLAY</DT> 2622<DD>Determines if Alpine will try to display IMAGE attachments.</DD> 2623<DT>SHELL</DT> 2624<DD>If not set, default is "/bin/sh".</DD> 2625<DT>TMPDIR, TMP, or TEMP</DT> 2626<DT>MAILCAPS</DT> 2627<DD>A <B>colon</B> delimited list of path names to mailcap files.</DD> 2628</DL> 2629<!--chtml if pinemode="os_windows"--> 2630<P> 2631<H2>Common PC-Alpine Configuration Problems</H2> 2632 2633<H3>Configuration settings aren't being saved</H3> 2634 2635<P>This problem can happen if you run pine from one directory and 2636then decide to move your pine directory to another location. PC-Alpine 2637stores certain variables, including the configuration location, in the 2638Windows Registry (which you shouldn't ever need to manually edit). There 2639are a couple of ways to go about removing or resetting the values in the 2640registry. 2641 2642<P> 26431) Run PC-Alpine's registry value deletion command. This can be done by 2644running: "<your pine directory>\pine.exe -registry clear" from the DOS 2645prompt. You could create a shortcut to pine.exe and change the "Target" 2646value to the above command. 2647 2648<P> 26492) Tell PC-Alpine where to look for the configuration file. Configuration 2650information is stored in a file called the PINERC. With the "-p PINERC" 2651option, you can tell PC-Alpine the location of your pinerc. An example of 2652this would be to run: "<your pine directory>\pine.exe -p C:\pine\mypinerc". 2653Again, you can use the DOS prompt or the shortcut method explained in (1). 2654 2655<P> 2656Additionally, there is the "-registry set" option, which will actively 2657set registry values to the current setting, and is therefore useful with 2658the "-p PINERC" option. 2659 2660<!--chtml endif--> 2661<P> 2662<End of Configuration Notes> 2663</BODY> 2664</HTML> 2665====== h_news_legal ====== 2666<html> 2667<head> 2668<TITLE>Alpine Legal Notices</TITLE> 2669</head> 2670<body> 2671 2672<H1>Alpine Legal Notices</H1> 2673 2674Alpine and its constituent programs are covered by the Apache License Version 2.0. 2675 2676 2677<P> 2678<End of Alpine Legal Notices> 2679</BODY> 2680</HTML> 2681===== h_info_on_mbox ===== 2682<HTML> 2683<HEAD> 2684<TITLE>Information on mbox driver</TITLE> 2685</HEAD> 2686<BODY> 2687<H1>Information on "Missing Mail" and the "mbox" driver</H1> 2688 2689Beginning with Pine 4.00 (Pine came before Alpine) 2690a new INBOX access method is 2691available as part of the standard configuration. It is called the 2692"mbox" driver and it works like this:<P> 2693 2694<P> 2695<BLOCKQUOTE> 2696If the file "mbox" exists in the user's home directory, and 2697is in Unix mailbox format, then when INBOX is opened this file will be 2698selected as INBOX instead of the mail spool file. Messages will be 2699automatically transferred from the mail spool file into the mbox 2700file. 2701</BLOCKQUOTE> 2702 2703<P> 2704The advantage of this method is that, after new mail has been copied 2705from the system mail spool, all subsequent access is confined to the 2706user's home directory, which is desirable on some systems. However, a 2707possible disadvantage is that mail tools other than those from the 2708University of Washington will not know to look for mail in the user's 2709mbox file. For example, POP or IMAP servers other than those from the 2710University of Washington, and many "new mail notification" 2711programs may not work as expected with this driver enabled.<P> 2712 2713To disable this behavior, either remove/rename the "mbox" 2714file or find the <A HREF="h_config_disable_drivers"><!--#echo var="VAR_disable-these-drivers"--></A> 2715option in Setup/Config 2716and add "mbox" to it: 2717<P> 2718<CENTER><SAMP><!--#echo var="VAR_disable-these-drivers"-->=mbox</SAMP></CENTER> 2719<P> 2720<End of help on this topic> 2721</BODY> 2722</HTML> 2723===== h_info_on_locking ===== 2724<HTML> 2725<HEAD> 2726<TITLE>FAQs on Alpine Locking</TITLE> 2727</HEAD> 2728<BODY> 2729<H1>What Systems Managers Need to Know about Alpine File Locking</H1> 2730 2731There is an extensive section on locking in the Alpine technical notes; 2732this information is intended to provide answers to some common questions:<P> 2733<OL> 2734<LI> Why did locking change in Pine 4.00?<BR> 2735The actual locking mechanisms did not change in 4.00. 2736What changed is that when one particular locking mechanism used by Alpine 2737fails, Alpine now issues a warning message. Prior to Pine 4.00, the locking 2738failure would occur, but no warning was issued.<P> 2739 2740<LI> Is this what the "Mailbox vulnerable" message is about?<BR> 2741Yes. It means that Alpine was unable to create a lockfile in the 2742spool directory, generally because of overly restrictive protections on the 2743spool directory. The correct permissions on the spool directory for 2744running Alpine are 1777, i.e. read-write-execute permission for everyone, 2745with the sticky-bit set, so only owners of a file can delete them.<P> 2746 2747<LI> Why does Alpine require that the mail spool directory have 1777 2748 protections?<BR> 2749Alpine was designed to run without special privileges. This means that in 2750order to create a lockfile in the spool directory, it is necessary to have 2751the spool directory permissions be world-writable.<P> 2752 2753<LI> Can't you create the lockfile somewhere else?<BR> 2754No. The lockfile in question must be in the mail spool directory, because 2755that's where the mail delivery program expects to find it, and the purpose 2756of the file is to coordinate access between the mail client (Alpine) and the 2757mail delivery program.<P> 2758 2759<LI> Isn't having the spool directory world-writable a big security risk?<BR> 2760No. Remember that the individual mail files in the spool directory are 2761NOT world-writable, only the containing directory. Setting the "sticky 2762bit" -- indicated by the "1" before the "777" mode 2763-- means that only the owner of the file (or root) can delete files in the 2764directory. So the only bad behavior that is invited by the 1777 mode is that 2765anyone could 2766create a random file in the spool directory. If the spool directory is 2767under quota control along with home directories, there is little incentive 2768for anyone to do this, and even without quotas a periodic scan for 2769non-mail files usually takes care of the problem. <P> 2770 2771<LI> Why not run Alpine as setgid mail?<BR> 2772Alpine was never designed to run with privileges, and to do so introduces a 2773significant security vulnerability. For example, if a user suspends Alpine, 2774the resulting shell will have group privileges. This is one example of 2775why we strongly recommend against running Alpine as a privileged program. 2776In addition, a "privileged mailer " paradigm would mean that normal 2777users 2778could not test Alpine versions or other mailers that had not been installed 2779by the system administrators.<P> 2780 2781 2782<LI> Are there any alternatives to creating .lock files in the spool dir?<BR> 2783There are, but they all have different sets of tradeoffs, and not all will 2784work on all systems. Some examples:<UL> 2785 <LI> Use lock system calls. Works fine on a few systems, provided mail 2786 spool is local. Doesn't work reliably if NFS is used. 2787 Doesn't work unless <B>all</B> the mail programs accessing the spool dir 2788 use the same calls. 2789 <LI> Deliver mail to user's home directory. An excellent solution, highly 2790 recommended -- but one which is incompatible with some "legacy" 2791mail tools that always look in the spool directory for the mail. 2792</UL><P> 2793 2794<LI> Are these spool directory lock files the only kinds of locks used by 2795 Alpine?<BR> 2796No. Alpine also creates lockfiles in the /tmp directory. For normal Unix 2797mailbox format folders, these are used to coordinate access between 2798multiple Alpine sessions. <P> 2799 2800<LI> What about the 2801<A HREF="h_config_quell_lock_failure_warnings">"<!--#echo var="FEAT_quell-lock-failure-warnings"-->"</A> feature added in Pine 4.01?<BR> 2802This is for people who are content to live dangerously, or who have 2803specific knowledge that the spool directory lockfiles are superfluous on 2804their system (because both Alpine and the mail delivery program are using 2805system call file locking in a context that works reliably, e.g. not NFS.)<P> 2806 2807<LI> Where can I find more details on how Alpine locking works?<BR> 2808See the Alpine Technical Notes.<P> 2809 2810</OL> 2811<P> 2812<End of help on this topic> 2813</BODY> 2814</HTML> 2815===== h_finding_help ==== 2816<HTML> 2817<HEAD> 2818<TITLE>Finding more information and requesting help</TITLE> 2819</HEAD> 2820<BODY> 2821<H1>Places to Look for More Answers</H1> 2822If you have questions about or problems with Alpine that you cannot resolve 2823after consulting the program's internal, context-sensitive help screens, here 2824are additional information resources that you may find helpful: 2825<P> 2826<UL> 2827 <LI> Alpine's top-level <A HREF="main_menu_tx">MAIN MENU HELP</A>.<P> 2828 2829 <LI> Alpine's <A HREF="h_help_index">Help Index</A>.<P> 2830 2831 <LI> Alpine's internal <A HREF="h_news">Release Notes</A>. They contain a 2832listing of changes in Alpine <!--#echo var="ALPINE_VERSION"--> 2833 since the last version, which may be useful for you to be aware of, 2834<B>especially</B> if a "problem" you are encountering is actually 2835a change in the way an aspect of Alpine works. There, you will also find notes 2836on Alpine configuration.<P> 2837 <LI> The main site for Alpine contains information on configuring and solving problems 2838 with Alpine, it can be found at 2839 2840<CENTER><A HREF="http://alpine.x10host.com/alpine/">http://alpine.x10host.com/alpine/</A></CENTER> 2841 2842 <LI> Archives of the Alpine-info mailing list, at <A 2843href="http://mailman13.u.washington.edu/pipermail/alpine-info/">http://mailman13.u.washington.edu/pipermail/alpine-info/</A> 2844 2845 <LI>The newsgroup comp.mail.pine. 2846 2847</UL> 2848<P><HR WIDTH="75%"> 2849<H1>Requesting help</H1> 2850If the internal help, the Release Notes, and your 2851local online and print resources do not help you resolve a problem, please 2852start by contacting your local computer support staff and asking for help. 2853<p> 2854This is especially true if: 2855<ul> 2856 <li>You suddenly have trouble sending or receiving mail. 2857 <li>You receive a "disk quota exceeded" message. 2858 <li>You have forgotten your password. 2859 <li>You think your account may have been compromised. 2860 <li>You need help viewing an attachment. 2861 <li>You need to know how to configure your: 2862 <A HREF="h_config_nntp_server">NNTP (news) server</A>, 2863 <A HREF="h_config_smtp_server">SMTP (sending mail) server</A>, 2864 <A HREF="h_config_ldap_server">LDAP (directory lookup) server</A>, or 2865 <A HREF="h_config_inbox_path">INBOX (incoming mail) path</A>. 2866 <li>You want to know what alternative editors or spellcheckers you may be able to use. 2867 <li>You want to block email from a particular person. 2868 <li>You're going on vacation and need to autorespond to incoming mail. 2869 <li>You want to automatically file or filter incoming messages. 2870</ul> 2871 2872In all of these cases, 2873you should contact <B>your</B> support staff, because <B>only they</B> 2874will be able to assist you effectively. Your support staff may be, depending on who 2875provides you with the email account you use Alpine with, for example:<UL> 2876<LI> the computing help desk of (a department of) your university, school, 2877employer, ... ; or 2878<LI> the customer service center of your Internet Service Provider; or 2879<LI> the friendly volunteer helpers of your Freenet; or 2880<LI> the person who setup your computer and internet connection. 2881</UL> 2882 2883<P> 2884If you have no local computing support to turn to, the worldwide <b>comp.mail.pine</b> 2885newsgroup can be a valuable source of information and assistance for Alpine 2886user issues. 2887<P> 2888For systems/email administrators, developers, trainers, user support 2889personnel, and others involved with Alpine messaging on a "technical" 2890level, the mailing list alpine-info is available; for information on 2891subscribing and posting to it, see 2892<P> 2893<CENTER><A HREF="https://mailman13.u.washington.edu/mailman/listinfo/alpine-info">https://mailman13.u.washington.edu/mailman/listinfo/alpine-info</A></CENTER> 2894<P> 2895 2896Regardless of whom you are asking for help with Alpine, remember 2897to provide as much detail as you can about the 2898nature of any problem you are encountering, such as 2899<UL> 2900<LI>when it first occurred; 2901<LI>what, if anything, happened that might have brought it about; 2902<LI>whether it still persists; 2903<LI>whether it is reproducible, and if so, how; 2904<LI>what, if anything, you already tried to solve it. 2905</UL> 2906It may also be helpful if you specify what version of Alpine you are using 2907<!--chtml if pinemode="running"--> 2908-- this is <!--#echo var="ALPINE_VERSION"--> -- 2909<!--chtml endif--> 2910and on what system, and when the copy of Alpine you are using was created 2911<!--chtml if pinemode="running"--> 2912-- for this copy: <!--#echo var=ALPINE_COMPILE_DATE--> 2913<!--chtml endif--> 2914 2915<!--chtml if pinemode="running"--> 2916<P> 2917When the Alpine program you are currently using was installed, a support 2918contact email address may have been set up; in that case, you can simply select 2919this link now to send a message to it:<BR> 2920<A HREF="X-Alpine-Gripe:_LOCAL_ADDRESS_?local"><!--#echo var="_LOCAL_FULLNAME_"--></A><P> 2921<!--chtml endif--> 2922<!--chtml if [ -r PINE_INFO_PATH ]--> 2923<HR WIDTH="75%">Local Support Contacts:<P> 2924<!--#include file="PINE_INFO_PATH"--> 2925<HR WIDTH="75%"> 2926<!--chtml endif--> 2927<P> 2928<End of help on this topic> 2929</BODY> 2930</HTML> 2931===== new_user_greeting ====== 2932<HTML> 2933<HEAD> 2934<TITLE>NEW USER GREETING</TITLE> 2935</HEAD> 2936<BODY> 2937<CENTER><<<This message will appear only once>>></CENTER> 2938<BR> 2939<H1>Welcome to Alpine ... a Program for Internet News and Email</H1> 2940We hope you will explore Alpine's many capabilities. From the MAIN MENU, 2941select Setup/Config to see many of the options available to you. Also note 2942that all screens have context-sensitive help text available. 2943 2944<P> 2945Alpine is a free email program. Your use of Alpine is subject to the terms of the <A 2946href="h_apache_license">Apache License 2.0</A>. 2947 2948<P> 2949Alpine's privacy policy is a living, online only, document, which can be found at 2950<A href="h_privacy_policy">http://alpine.x10host.com/privacy.html</A>. 2951By following the previous link, Alpine 2952will connect to an external server, and will download it and display 2953it for you. Please take some time to read it and understand it. 2954Since the Privacy Policy could be amended to take into consideration 2955new additions to Alpine, please check it periodically. You can always 2956find a link to the Privacy Policy in the <A href="h_news">Release Notes</A>. 2957 2958<P> 2959To Exit this screen and continue your Alpine session press "E". 2960</BODY> 2961</HTML> 2962===== new_alpine_user_greeting ====== 2963<HTML> 2964<HEAD> 2965<TITLE>NEW ALPINE USER GREETING</TITLE> 2966</HEAD> 2967<BODY> 2968<CENTER><<<This message will appear only once>>></CENTER> 2969<BR> 2970<H1>Welcome to Alpine ... a Program for Internet News and Email</H1> 2971Your Alpine configuration file indicates that you may have used Pine before 2972but not Alpine. 2973If you are familiar with the way Pine works, you should be comfortable 2974using Alpine. 2975Your Pine configuration file is automatically used for Alpine. 2976The Release Notes may be viewed by pressing 2977"R" now or while in the MAIN MENU. 2978 2979<P> 2980Alpine is a free email program. Your use of Alpine is subject to the terms of the <A 2981href="h_apache_license">Apache License 2.0</A>. 2982 2983<P> 2984Alpine's privacy policy is a living, online only, document, which can be found at 2985<A href="h_privacy_policy">http://alpine.x10host.com/privacy.html</A>. 2986By following the previous link, Alpine 2987will connect to an external server, and will download it and display 2988it for you. Please take some time to read it and understand it. 2989Since the Privacy Policy could be amended to take into consideration 2990new additions to Alpine, please check it periodically. You can always 2991find a link to the Privacy Policy in the <A href="h_news">Release Notes</A>. 2992 2993<P> 2994To Exit this screen and continue your Alpine session press "E". 2995</BODY> 2996</HTML> 2997===== new_version_greeting ====== 2998<HTML> 2999<HEAD> 3000<TITLE>NEW VERSION GREETING</TITLE> 3001</HEAD> 3002<BODY> 3003<CENTER><<<This message will appear only once>>></CENTER> 3004<BR> 3005<H1>Welcome to Alpine version <!--#echo var="ALPINE_VERSION"-->!</H1> 3006Your Alpine configuration file indicates that you may not have used 3007this version of Alpine before. This version's significant changes are 3008documented in the Release Notes, which may be viewed by pressing 3009"R" now or while in the MAIN MENU. 3010<P> 3011 3012<P> 3013Alpine is a free email program. Your use of Alpine is subject to the terms of the <A 3014href="h_apache_license">Apache License 2.0</A>. 3015 3016<P> 3017Alpine's privacy policy is a living, online only, document, which can be found at 3018<A href="h_privacy_policy">http://alpine.x10host.com/privacy.html</A>. 3019By following the previous link, Alpine 3020will connect to an external server, and will download it and display 3021it for you. Please take some time to read it and understand it. 3022Since the Privacy Policy could be amended to take into consideration 3023new additions to Alpine, please check it periodically. You can always 3024find a link to the Privacy Policy in the <A href="h_news">Release Notes</A>. 3025 3026<P> 3027To Exit this screen and continue your Alpine session press "E". 3028</BODY> 3029</HTML> 3030 3031===== main_menu_tx ====== 3032<HTML> 3033<HEAD> 3034<TITLE>GENERAL INFORMATION ON THE ALPINE MESSAGE SYSTEM</TITLE> 3035</HEAD> 3036<BODY> 3037<H1>GENERAL INFORMATION ON THE ALPINE MESSAGE SYSTEM</H1> 3038<DIV ALIGN=CENTER> 3039Version <!--#echo var="ALPINE_VERSION"--> 3040<!--chtml if pinemode="running"--> 3041<BR>(built <!--#echo var=ALPINE_COMPILE_DATE-->) 3042<!--chtml endif--> 3043</DIV> 3044<CENTER>Copyright 2013-2021 Eduardo Chappa, 3045<BR>Copyright 2006-2008 University of Washington. 3046</CENTER> 3047 3048<P> 3049When you are viewing a help screen, there may be links to 3050other topics highlighted (in Reverse video) in the text. 3051Here is an example. 3052The word "Introduction" in the TABLE OF CONTENTS below should be 3053highlighted. 3054If you type carriage return (or V for View Link, see the commands at the 3055bottom of the screen) you will be taken to a new help screen to view the 3056Introduction. 3057The commands at the bottom of the screen should then include 3058"P Prev Help". 3059If you type "P" you will end up back here. 3060If you type "E" for Exit, you will be back out of help and returned 3061to the place you were in Alpine when you entered Help. 3062In this case, you would go back to the MAIN MENU. 3063There are also other links that are highlighted in bold (or the color used 3064by your terminal to display bold). 3065The items after the Introduction in the TABLE OF CONTENTS are all examples 3066of such links. 3067In order to view those links, you first have to make the link you want 3068to view the current link. 3069The "NextLink" and "PrevLink" commands 3070(see bottom of screen) can do that for you. 3071<P> 3072 3073<H2>TABLE OF CONTENTS</H2> 3074<OL> 3075 <LI> <A HREF="h_mainhelp_intro">Introduction</A> 3076 <LI> <A HREF="h_mainhelp_pinehelp">Alpine Help</A> 3077<!--chtml if [ -r PINE_INFO_PATH ]--> 3078 <LI> <A HREF="h_mainhelp_localsupport">Local Support Contacts</A> 3079<!--chtml endif--> 3080 <LI> <A HREF="h_mainhelp_cmds">Giving Commands in Alpine</A> 3081 <LI> <A HREF="h_mainhelp_config">Alpine Configuration</A> 3082 <LI> <A HREF="h_mainhelp_status">Titlebar Line</A> 3083 <LI> <A HREF="h_mainhelp_mainmenu">Main Menu</A> 3084 <LI> <A HREF="h_mainhelp_index">Index of Messages</A> 3085 <LI> <A HREF="h_mainhelp_reading">Reading Messages</A> 3086 <LI> <A HREF="h_mainhelp_composing">Composing Messages</A> 3087 <LI> <A HREF="h_mainhelp_readingnews">Reading News</A> 3088 <LI> <A HREF="h_mainhelp_abooks">Address Books</A> 3089 <LI> <A HREF="h_mainhelp_ldap">LDAP Directories</A> 3090 <LI> <A HREF="h_mainhelp_folders">Folders</A> 3091 <LI> <A HREF="h_mainhelp_collections">Collection Lists</A> 3092 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A> 3093 <LI> <A HREF="h_mainhelp_color">Color Setup</A> 3094 <LI> <A HREF="h_mainhelp_filtering">Filtering</A> 3095 <LI> <A HREF="h_mainhelp_roles">Roles</A> 3096 <LI> <A HREF="h_mainhelp_patterns">Patterns</A> 3097 <LI> <A HREF="h_mainhelp_keywords">Keywords (or Flags, or Labels)</A> 3098 <LI> <A HREF="h_mainhelp_mouse">Using a Mouse</A> 3099 <LI> <A HREF="h_mainhelp_cmdlineopts">Command Line Options</A> 3100 <LI> <A HREF="h_mainhelp_securing">Securing Your Alpine Session</A> 3101 <LI> <A HREF="h_mainhelp_smime">S/MIME</A> 3102 <LI> <A HREF="h_mainhelp_problems">Reporting Problems</A> 3103 <LI> <A HREF="X-Alpine-Config:">Show Supported Options in this Alpine</A> 3104 <LI> <A HREF="h_help_index">Index to Alpine's Online Help</A> 3105</OL> 3106 3107<P> 3108<End of help on this topic> 3109</BODY> 3110</HTML> 3111===== h_mainhelp_intro ====== 3112<HTML> 3113<HEAD> 3114<TITLE>Introduction</TITLE> 3115</HEAD> 3116<BODY> 3117<H1>Introduction</H1> 3118 3119Alpine is an "Alternatively Licensed Program for Internet 3120News and Email" produced until 2009 by the University of Washington. 3121It is intended to be an easy-to-use program for 3122sending, receiving, and filing Internet electronic mail messages and 3123bulletin board (Netnews/Usenet) messages. Alpine supports the following 3124Internet protocols and specifications: SMTP (Simple Mail Transport Protocol), 3125NNTP (Network News Transport Protocol), MIME (Multipurpose Internet Mail 3126Extensions), IMAP (Internet Message Access Protocol), and LDAP (Lightweight 3127Directory Access Protocol).<p> 3128 3129Although originally designed for inexperienced email users, Alpine has 3130evolved to support many advanced features. There are an ever-growing 3131number of configuration and personal-preference options, though which of 3132them are available to you is determined by your local system managers. 3133 3134<H2>WHAT ALPINE DOES...</H2> 3135 3136Alpine is a "mail user agent" (MUA), which is a program that 3137allows you to 3138compose and read messages using Internet mail standards. (Whether you 3139can correspond with others on the Internet depends on whether or not your 3140computer is connected to the Internet.) Alpine also allows reading and 3141posting messages on the Internet "net news" system, provided 3142that your site operates a suitable news server. 3143 3144<H2>WHAT ALPINE DOES NOT DO...</H2> 3145 3146A "mail user agent" such as Alpine is just one part of a 3147messaging system. Here are some things that are <B>not</B> done by Alpine, 3148but require other programs:<P> 3149<UL> 3150 <LI> Actual relaying of email... which is done by "message transfer 3151agents". 3152 <LI> Vacation messages... automatically responding to incoming messages 3153 <LI> Anything to do with "talk"... which has nothing to do with 3154email. 3155 <LI> Anything to do with "irc"... which has nothing to do with email. 3156 <LI> List processing... resending one message to a list of recipients. 3157</UL> 3158 3159<P> 3160<End of help on this topic> 3161</BODY> 3162</HTML> 3163 3164===== h_mainhelp_pinehelp ====== 3165<HTML> 3166<HEAD> 3167<TITLE>Alpine Help</TITLE> 3168</HEAD> 3169<BODY> 3170<H1>Alpine Help</H1> 3171 3172Alpine help is generally context-sensitive. In other words, each Alpine screen you 3173use will have its own help text, explaining the choices available for that 3174screen. This general help section, on the other hand, attempts to give an 3175overall picture of what Alpine is capable of doing, as well as pointers to 3176additional help sections about specific topics.<p> 3177 3178Much of the help text contains links to further help topics, similar to 3179how the World Wide Web works. 3180You may choose a link to view using the "NextLink" and 3181"PrevLink" commands to change the link that is highlighted. 3182The "View Link" command will then show you the highlighted link. 3183Similar to the Back button in a web browser, the "Prev Help" command 3184will return you to where you were before viewing the link, and "Exit Help" 3185will return you to the location in Alpine before you asked for help. 3186For example, if you are reading this text in Alpine you may return to the 3187help table of contents with the "Prev Help" command or you may view the 3188Release notes link in the next paragraph and then return here with 3189"Prev Help". 3190<P> 3191 3192In addition to this general help on Alpine, <A HREF="h_news">Release Notes</A> 3193on the current Alpine version are also available from the MAIN MENU: Press 3194<!--chtml if pinemode="function_key"--> 3195"F9" 3196<!--chtml else--> 3197"R" 3198<!--chtml endif--> 3199to browse the release notes. These include changes since the last release, 3200configuration information, the history of the Alpine 3201project, credits, and legal notices. 3202 3203Alpine releases are available via the world wide web at 3204<P> 3205<CENTER><SAMP><A 3206HREF="http://repo.or.cz/alpine.git">http://repo.or.cz/alpine.git</A></SAMP 3207></CENTER> 3208<P> 3209 3210If you would like to print <EM>all</EM> of Alpine's internal help text 3211(not recommended) for a little light bedtime reading, then press 3212<!--chtml if pinemode="function_key"--> 3213"F12" 3214<!--chtml else--> 3215"Z" 3216<!--chtml endif--> 3217now. (This assumes that the 3218copy of Alpine you are using has been properly configured for printing 3219at your site.) 3220<P> 3221<End of help on this topic> 3222</BODY> 3223</HTML> 3224===== h_mainhelp_localsupport ====== 3225<HTML> 3226<HEAD> 3227<TITLE>Local Support Contacts</TITLE> 3228</HEAD> 3229<BODY> 3230<H1>Local Support Contacts</H1> 3231 3232<!--chtml if [ -r PINE_INFO_PATH ]--> 3233<!--#include file="PINE_INFO_PATH"--> 3234<!--chtml else--> 3235No Local Support Contacts configured. 3236<!--chtml endif--> 3237 3238<P> 3239<End of help on this topic> 3240</BODY> 3241</HTML> 3242 3243===== h_mainhelp_cmds ====== 3244<HTML> 3245<HEAD> 3246<TITLE>Giving Commands in Alpine</TITLE> 3247</HEAD> 3248<BODY> 3249<H1>Giving Commands in Alpine</H1> 3250 3251Unless configured otherwise 3252(<A HREF="h_config_blank_keymenu"><!--#echo var="FEAT_disable-keymenu"--></A>) 3253the bottom two lines of the screen are always used to list the 3254commands you can give. You press the keys that are highlighted to give 3255the command. The commands for getting help and going back to the main 3256menu are always present (except when viewing help as you are now). 3257<!--chtml if pinemode="function_key"--> 3258<!--chtml else--> 3259<p> 3260Pressing O (meaning "Other Commands") changes the keys 3261you see at the bottom of any screen. In some cases there are 3 or 3262even 4 different 3263sets of keys that can be seen by using the O key. <EM>All commands are 3264active</EM>, even if they are not currently showing at the bottom of your 3265screen. In other words, you <EM>never</EM> need to press the O key, except to 3266remind yourself of the proper key to press to perform an operation. 3267 3268<H2>Control Key Commands</H2> 3269When composing mail, and in a few other places, in Alpine you 3270have to use Control keys. This means pressing the Control key (usually labeled 3271"Ctrl") and the 3272letter indicated at the same time. Usually, this is shown with a 3273"^" in front of the letter. On some systems, certain control 3274characters are intercepted before they get to Alpine. As a work-around, 3275you can press the ESCAPE key twice followed by the desired key. For 3276example, if Ctrl-O (^O) does not work on your system, try typing 3277"ESC ESC O". 3278<!--chtml endif--> 3279<H2>Paging Up and Down</H2> 3280The "+" and "-" keys are used for 3281moving to the next or previous page. The space bar is a synonym for 3282"+". You may also use Ctrl-V to page down and Ctrl-Y to page 3283up as you do in the message composer. On screens with a WhereIs (search) 3284command, W or Ctrl-W followed by Ctrl-V will move to the bottom of the 3285message or list, and W or Ctrl-W followed by Ctrl-Y will move to the top 3286of the message or list. 3287 3288<H2>Return Key</H2> 3289The return key is usually a synonym for a frequently used 3290command. When viewing a message, there is currently not a default 3291command, so RETURN does nothing; when in the index, it is synonymous with 3292"view msg". In the key menu at the bottom of the screen, whatever is 3293enclosed in square brackets [] is the same as the return key. 3294 3295<H2>Control Keys Not Used By Alpine</H2> 3296Most commands in Alpine are single letters, with -- we hope -- some mnemonic 3297value, but in places where Alpine is expecting text input, e.g. in the composer or 3298at prompts for file/folder names, control keys must be used for editing and 3299navigation functions. 3300<P> 3301 3302Alpine has used nearly all the control keys available. There are, however, 3303certain control keys that are reserved by other programs or for technical 3304reasons. Alpine does not use any of these keys: 3305<DL> 3306 <DT>Ctrl-S</DT> <DD>Used by Unix as "stop output"</DD> 3307 <DT>Ctrl-Q</DT> <DD>Used by Unix as "resume output"</DD> 3308 <DT>Ctrl-]</DT> <DD>Often used by Telnet as escape key</DD> 3309</DL> 3310<P> 3311Note: Ctrl-S and Ctrl-Q can be subject to 3312<A HREF="h_special_xon_xoff">special handling</A>. 3313<P> 3314In addition, while the ESC key alone is not used for command input, 3315Alpine will recognize two consecutive ESC key presses followed by a letter 3316key as a substitute for control key input. For example, the control key 3317<SAMP>Ctrl-X</SAMP> can alternatively be entered using the 3318three keystrokes: <SAMP>ESC ESC x</SAMP>. 3319This is useful if the communication program you are using 3320(e.g. Telnet) has its own, conflicting, idea of what certain control 3321characters mean. 3322 3323 3324<H2>Repainting the Screen</H2> 3325Sometimes what is displayed on the screen will be 3326incorrect due to noise on the phone line or other causes and you will want 3327to repaint the whole screen to make it correct. You can use the Ctrl-L 3328command to do this. It never hurts to do it when in doubt. 3329 3330<P> 3331<End of help on this topic> 3332</BODY> 3333</HTML> 3334===== h_mainhelp_status ====== 3335<HTML> 3336<HEAD> 3337<TITLE>Titlebar Line</TITLE> 3338</HEAD> 3339<BODY> 3340<H1>Titlebar Line</H1> 3341 3342The top line of the screen is Alpine's titlebar line. It will always display 3343the current version of Alpine and will also convey information about the 3344status of the program. This is where you look to find out what 3345collection, folder and message number is active and where you are in Alpine. 3346<P> 3347 3348If the titlebar line says "READONLY" it means that the open folder 3349(typically your INBOX) is "locked" by another mail session -- 3350most likely a more recent session of Alpine has taken the INBOX lock. 3351<P> 3352 3353If the titlebar line says "CLOSED" it means that you are trying to 3354access a 3355folder on a remote mail server, and for some reason, communication with 3356the mail server has either been lost, or never successfully established. 3357This can be a result of trying to open a non-existent folder, or one 3358stored on an invalid or non-operational server, or it can mean that Alpine 3359has been suspended for more that 30 minutes while accessing a remote mail 3360server. 3361 3362<P> 3363<End of help on this topic> 3364</BODY> 3365</HTML> 3366===== h_mainhelp_mainmenu ====== 3367<HTML> 3368<HEAD> 3369<TITLE>Main Menu</TITLE> 3370</HEAD> 3371<BODY> 3372<H1>Main Menu</H1> 3373 3374The Main Menu lists Alpine's main options. 3375The key or keys you must type to enter your 3376choice are to the left of each option or command name. 3377You can type either uppercase or lowercase letters, 3378and you should not press <Return> after typing the 3379letter (unless you are specifically asking for the default, 3380highlighted command). 3381<P> 3382 3383From the Main Menu you can choose to read online help, write (compose) and 3384send a message, look at an index of your mail messages, open or maintain 3385your mail folders, update your address book, configure Alpine, and quit Alpine. 3386There are additional options listed at 3387the bottom of the screen as well. 3388 3389<P> 3390The Help command usually returns context-sensitive help information. 3391However, in the Main Menu you get the most general help, which includes 3392a Table of Contents. 3393The last entry in the Table of Contents is an Index of help topics, 3394so this is a good place to go if you are having trouble finding how 3395to do something. 3396 3397<H2>Main Menu Commands</H2> 3398The Alpine main menu lists the most common Alpine functions. A <a 3399href="h_main_menu_commands">full list of these 3400commands</a> and what they do is available. 3401<P> 3402<End of help on this topic> 3403</BODY> 3404</HTML> 3405===== h_mainhelp_abooks ====== 3406<HTML> 3407<HEAD> 3408<TITLE>Address Books</TITLE> 3409</HEAD> 3410<BODY> 3411<H1>Address Books</H1> 3412 3413 3414As you use email, you can build a list of your regular email correspondents 3415in your Alpine 3416Address Book. At the Alpine MAIN MENU, press A to see the Address Book List 3417screen. Your 3418personal address book will be highlighted. Press <Return> to view it. 3419You can use the address book to store email addresses for individuals or 3420groups, to create easily 3421remembered "nicknames" for these addresses, and to quickly retrieve an email 3422address when you are composing a message. 3423<P> 3424There are two ways to add addresses to your address book: you can add them 3425manually or take them from messages (by pressing T to access the Take command). 3426With either method, you specify nicknames for your correspondents. A single 3427address book entry (or nickname) can point to just one email address, or, it can 3428point to more than one. When it points to more than one, it is called a 3429distribution list. Each distribution list has a nickname, a full name, and a 3430list of addresses. These 3431addresses may be actual addresses, other nicknames in your address book, or 3432other 3433distribution lists. 3434 3435<P> 3436Additional information is available in Alpine's online help: 3437<ul> 3438 <li><a href="h_abook_opened">The Alpine Address Book</a></li> 3439</ul> 3440<P> 3441<End of help on this topic> 3442</BODY> 3443</HTML> 3444===== h_mainhelp_ldap ====== 3445<HTML> 3446<HEAD> 3447<TITLE>LDAP</TITLE> 3448</HEAD> 3449<BODY> 3450<H1>LDAP</H1> 3451 3452LDAP (Lightweight Directory Access Protocol) is a standard means of accessing 3453an organization's shared 3454directories. Essentially, using LDAP, Alpine is able to find email addresses in 3455large address 3456books, rather like the White Pages provided by the phone company. As an Alpine 3457user, it is not 3458necessary to know much about how this works, only how to use it and how to 3459configure 3460it. 3461<P> 3462More information on configuring LDAP is available in Alpine's online help: 3463<ul> 3464 <li><a href="h_direct_config">Setup LDAP Directory Servers</a></li> 3465</ul> 3466<P> 3467Additional help on using LDAP in Alpine is also available: 3468<ul> 3469 <li><a href="h_ldap_view">LDAP Response View Explained</a></li> 3470</ul> 3471<P> 3472<End of help on this topic> 3473</BODY> 3474</HTML> 3475===== h_mainhelp_index ====== 3476<HTML> 3477<HEAD> 3478<TITLE>Index of Messages</TITLE> 3479</HEAD> 3480<BODY> 3481<H1>Index of Messages</H1> 3482 3483In Alpine's message index, the selected message is highlighted. The first 3484column on the left is blank, shows a "+" if the message was 3485sent directly to you (i.e., it is not a 3486copy or from a list), or a "-" if you were explicitly Cc'd. 3487<P> 3488The second column may be blank, or it may contain: 3489<ul> 3490 <li>"N" if the message is new (unread), </li> 3491 <li>"A" if you have answered the message (using the Reply command), </li> 3492 <li>"D" if you have marked the message for deletion.</li> 3493</ul> 3494 3495<P> 3496Note: If you answer a message as well as mark it deleted (in either order), 3497you will only see the "D". 3498 3499<P> 3500The rest of the columns in the message line show you the message 3501number, date sent, sender, size, and subject. For details, press ? (Help). 3502The behavior and appearance of the Index screen is highly configurable. 3503In the Setup/Config screen search (with the WhereIs command) for options 3504that contain the words "index" or "thread" to see 3505many of the configuration possibilities. 3506In particular, the 3507"<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" 3508option may be used to configure the look of the standard MESSAGE INDEX lines 3509in many different ways. 3510Find <!--#echo var="VAR_index-format"--> in the Setup/Config screen and 3511read the help text there for more information. 3512<P> 3513Most of the commands you need to handle your messages are visible at the 3514bottom of the screen, and you can press O (OTHER CMDS) to see additional 3515commands that are available. 3516You do not need to see these "other commands" 3517on the screen to use them. That is, you never need to press O as a prefix 3518for any other command. 3519 3520<P> 3521Additional information is available in Alpine's online help: 3522<ul> 3523 <li><a href="h_mail_index">Message Index Commands</a></li> 3524</ul> 3525<P> 3526<End of help on this topic> 3527</BODY> 3528</HTML> 3529===== h_mainhelp_reading ====== 3530<HTML> 3531<HEAD> 3532<TITLE>Reading Messages</TITLE> 3533</HEAD> 3534<BODY> 3535<H1>Reading Messages</H1> 3536 3537The message text screen shows you the text of the message along with 3538its header. If a message has attachments, those will be listed (but not 3539displayed) also. The titlebar line displays information about the currently 3540open message, folder and collection. You see the name of the collection 3541(if there is one) in angle brackets, then the name of the folder, then the 3542message number and finally the position within the current message (in 3543percent). If the message is marked for deletion 3544"DEL" will appear in the 3545upper right as well. 3546 3547<P> 3548As with every Alpine screen, the bottom two lines show you the commands 3549available. 3550 3551<P>Additional information is available in Alpine's online help: 3552<ul> 3553 <li><a href="h_mail_view">Message Text Screen</a></li> 3554 <li><a href="h_attachment_screen">Attachment Index Screen Explained</a></li> 3555 <li><a href="h_mail_text_att_view">Attachment View Screen Explained</a></li> 3556</ul> 3557<P> 3558<End of help on this topic> 3559</BODY> 3560</HTML> 3561===== h_mainhelp_composing ====== 3562<HTML> 3563<HEAD> 3564<TITLE>Composing Messages</TITLE> 3565</HEAD> 3566<BODY> 3567<H1>Composing Messages</H1> 3568 3569To write a message, press C (Compose). You see the Compose Message 3570screen, which is divided into two parts: the header area and the message 3571text area. The header area is where information on the recipient (the To: 3572field) and the subject line go, while the message text area contains the 3573actual text of the email message. Different commands are available to you 3574when your cursor is in different areas on this screen. To see additional 3575help on commands in either the message text or header area, type 3576<Control>G (Get help). 3577 3578<P> 3579To move around, use the arrow keys or Ctrl-N (Next line) and Ctrl-P 3580(Previous line); to correct typing errors, use <Backspace> or <Delete>. 3581 3582<P>The following information from Alpine's online help may prove useful: 3583<ul> 3584 <li><a href="h_composer_to">Message Header Commands</a></li> 3585 <li><a href="h_compose_richhdr">Rich Header Command</a></li> 3586 <li><a href="h_composer">Composer Commands</a></li> 3587 <li><a href="h_edit_nav_cmds">Composer Editing Commands</a></li> 3588 <li><a href="h_config_change_your_from">Changing your From Address</a></li> 3589 <li><a href="h_compose_send">Send Command</a></li> 3590 <li><a href="h_compose_spell">Spell Check Command</a></li> 3591</ul> 3592<P> 3593<End of help on this topic> 3594</BODY> 3595</HTML> 3596===== h_mainhelp_collections ====== 3597<HTML> 3598<HEAD> 3599<TITLE>Collection Lists</TITLE> 3600</HEAD> 3601<BODY> 3602<H1>Collection Lists</H1> 3603 3604Collection lists are Alpine's way of organizing groups of folders. Each 3605"collection" can reside on a different server, for example, and contain a 3606different group of mail folders. 3607 3608<P> 3609For more information on this, see: 3610<ul> 3611 <li><a href="h_what_are_collections">Folder Collections Explained</a></li> 3612</ul> 3613<P> 3614Additional information relating to collection lists is also available in 3615Alpine's online 3616help: 3617<ul> 3618 <li><a href="h_collection_maint">Setup Collection List Screen</a></li> 3619 <li><a href="h_collection_screen">Collection List Screen</a></li> 3620</ul> 3621<P> 3622<End of help on this topic> 3623</BODY> 3624</HTML> 3625===== h_mainhelp_folders ====== 3626<HTML> 3627<HEAD> 3628<TITLE>Folders</TITLE> 3629</HEAD> 3630<BODY> 3631<H1>Folders</H1> 3632 3633Messages can quickly accumulate in your INBOX folder. If you use email 3634often, you soon could have hundreds. You need to delete messages you do 3635not want, and you can use folders to organize messages you wish to save. A 3636folder is a collection of one or more messages that are stored (just like 3637the messages in your INBOX) so you can access and manage them. 3638 3639<P> 3640You can organize your email messages into different folders by topic, 3641correspondent, date, or any other category that is meaningful to you. You 3642can create your own folders, and Alpine automatically provides three: 3643<ul> 3644 <li>The INBOX folder: messages sent to you are listed in this folder. 3645 When you first start Alpine and go to the Message Index screen, you are 3646looking at the list of messages in your INBOX folder. Every incoming 3647message remains in your INBOX until you delete it or save it in another 3648folder. </li> 3649 <li>The sent-mail folder: copies of messages you send are stored in this 3650folder. This is 3651convenient if you cannot remember whether you actually sent a message and want 3652to check, or 3653if you want to send a message again.</li> 3654 <li>The saved-messages folder: copies of messages you save are stored in this 3655folder 3656unless you choose to save them to other folders you create yourself.</li> 3657</ul> 3658 3659<P> 3660More information about folders is available in Alpine's online help: 3661<ul> 3662 <li><a href="h_folder_open">Explanation of Folder Selection</a></li> 3663 <li><a href="h_folder_maint">Help for Folder List</a></li> 3664 <li><a href="h_valid_folder_names">Explanation of Valid Folder Names</a></li> 3665 <li><a href="h_folder_fcc">Folder Select for Fcc ("sent-mail") 3666Explained</a></li> 3667 <li><a href="h_folder_save">Folder Select for Save Explained</a></li> 3668</ul> 3669<P> 3670<End of help on this topic> 3671</BODY> 3672</HTML> 3673===== h_mainhelp_color ====== 3674<HTML> 3675<HEAD> 3676<TITLE>Color</TITLE> 3677</HEAD> 3678<BODY> 3679<H1>Color</H1> 3680 3681If the terminal emulator you are using is capable of displaying color or if 3682you are using PC-Alpine, then it is possible to set up Alpine so that various 3683parts of the display will be shown in colors you configure. This is done 3684using the Setup Color screen, available from the MAIN MENU by selecting 3685the Setup command followed by "K" for Kolor (because "C" 3686stands for Config in this context). 3687 3688<P> 3689For example, you may color things like the titlebar, the current item, 3690the keymenu, and the status messages. 3691You may also color lines in the index, and headers and quoted text in the 3692MESSAGE TEXT screen. 3693You use the Color Setup screen for configuring most of this, but you must 3694use the IndexColor setup for coloring whole index lines. 3695These are available from the MAIN MENU under Setup/Kolor and Setup/Rules/IndexColor. 3696 3697<P> 3698The following entries in Alpine's online help provide additional information 3699about how to use color: 3700<UL> 3701 <LI> <A HREF="h_color_setup">Color Setup screen</A> 3702 <LI> <A HREF="h_rules_incols">Index Line Color</A> 3703 <LI> <A HREF="h_config_quote_color">quoted text</A> in message view 3704 <LI> <A HREF="h_config_customhdr_pattern">text associated with user-defined headers</A> in message view 3705</UL> 3706<P> 3707<End of help on this topic> 3708</BODY> 3709</HTML> 3710===== h_mainhelp_mouse ====== 3711<HTML> 3712<HEAD> 3713<TITLE>Using a Mouse</TITLE> 3714</HEAD> 3715<BODY> 3716<H1>Using a Mouse</H1> 3717 3718If you are using PC-Alpine mouse support is turned on automatically. 3719If you are using UNIX Alpine within an X terminal window or within 3720a terminal emulator that supports an xterm-style mouse, then you may 3721turn on support for the mouse with the feature 3722<A HREF="h_config_enable_mouse"><!--#echo var="FEAT_enable-mouse-in-xterm"--></A>. 3723For UNIX Alpine you will also need to set the $DISPLAY environment variable. 3724<P> 3725PC-Alpine offers considerable mouse support. You can view what is 3726"clickable" by dragging your mouse over any screen; when the 3727arrow cursor changes into a hand, you found something. Mouse-click 3728possibilities include navigating between screens and folders and 3729double-clicking on hyperlinks to open your Web browser. 3730Context-sensitive pop-up menus appear with a right-click on your PC-Alpine 3731screen. Examples of right-click options include "copy" after 3732selecting text to copy and "View in New Window" when you click 3733on a particular message in the Message Index. The menu choices available 3734to you will vary based upon what screen is open, where on the screen your 3735cursor is located, and even what action you have already taken. 3736Within a folder, you may set the "Important" flag on any 3737message. 3738<P> 3739X terminal mouse support is more limited but still quite powerful. 3740As with PC-Alpine, clicking on any of the commands in the keymenu at 3741the bottom of the screen will execute that command as if you typed it. 3742Double-clicking on a link, for example the link to the 3743<!--#echo var="FEAT_enable-mouse-in-xterm"--> feature in the paragraph above, 3744will take you to that link. 3745Double-clicking on an index line will view the message, and so on. 3746<P> 3747<End of help on this topic> 3748</BODY> 3749</HTML> 3750===== h_mainhelp_keywords ====== 3751<HTML> 3752<HEAD> 3753<TITLE>Keywords</TITLE> 3754</HEAD> 3755<BODY> 3756<H1>Keywords</H1> 3757 3758Within a folder, you may set the "Important" flag on any 3759message. 3760This doesn't have any system-defined meaning and is only called 3761the Important flag because many users use it to signify that a message 3762is important to them in some way. 3763<P> 3764You may also define your own set of keywords. 3765You might know these as user defined flags or as labels. 3766These are similar to the Important flag but you choose the names for yourself. 3767<P> 3768Alpine will only display keywords that 3769have been added by you in the Flag Details screen or 3770that have been configured by you using the Setup/Config option 3771<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>. 3772Keywords set by other means (for example, by another email client) will not 3773show up in Alpine unless you configure Alpine to know about them. 3774They will show up in the Flag Details screen, but will not show up, for example, 3775in the index line. 3776 3777<P> 3778The following entries in Alpine's online help provide additional information 3779about how to use keywords: 3780<ul> 3781 <li><A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--> config option</A></li> 3782 <li><A HREF="h_common_flag">Flag command to set keywords</A></li> 3783</ul> 3784<P> 3785<End of help on this topic> 3786</BODY> 3787</HTML> 3788===== h_mainhelp_roles ====== 3789<HTML> 3790<HEAD> 3791<TITLE>Roles</TITLE> 3792</HEAD> 3793<BODY> 3794<H1>Roles</H1> 3795 3796You may play different roles depending on who you are replying to. For 3797example, if you are replying to a message addressed to help-desk you may 3798be acting as a Help Desk Worker. That role may require that you use a 3799different return address and/or a different signature. 3800 3801<P> 3802To configure roles, go to the MAIN MENU and use the Setup command 3803followed by "Rules" and then "Roles". 3804The following entries in Alpine's online help provide additional information 3805about how to 3806use roles: 3807<ul> 3808 <li><a href="h_rules_roles">Setup Roles Screen</a></li> 3809 <li><a href="h_role_select">Roles Screen</a></li> 3810</ul> 3811<P> 3812<End of help on this topic> 3813</BODY> 3814</HTML> 3815===== h_mainhelp_filtering ====== 3816<HTML> 3817<HEAD> 3818<TITLE>Filtering</TITLE> 3819</HEAD> 3820<BODY> 3821<H1>Filtering</H1> 3822 3823The software that actually delivers mail (the stuff that happens 3824before Alpine is involved) for you is in a better position to do mail filtering 3825than Alpine itself. 3826If possible, you may want to look into using that sort of mail filtering to 3827deliver mail to different folders, delete it, or forward it. 3828However, if you'd like Alpine to help with this, Alpine's filtering is for you. 3829 3830<P> 3831Filtering is a way to automatically move certain messages from one folder 3832to another or to automatically delete messages. 3833You may also automatically set the state (Important, New, Deleted, Answered) of messages 3834and set <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> for messages. 3835Alpine doesn't have the ability to forward mail to another address or 3836to deliver vacation messages. 3837 3838<P> 3839To configure filtering, go to the MAIN MENU and use the Setup command 3840followed by "Rules" and then "Filters". 3841The following entries in Alpine's online help provide additional information 3842about how to use filtering: 3843<UL> 3844 <LI> <A HREF="h_rules_filter">Filtering Setup screen</A> 3845</UL> 3846<P> 3847<End of help on this topic> 3848</BODY> 3849</HTML> 3850===== h_mainhelp_patterns ====== 3851<HTML> 3852<HEAD> 3853<TITLE>Patterns</TITLE> 3854</HEAD> 3855<BODY> 3856<H1>Patterns</H1> 3857 3858Patterns are used with Roles, Filtering, Index Coloring, 3859Scoring, Other Rules, and Search Rules, so it may help you to understand exactly how Patterns work. 3860The following entries in Alpine's online help provide information 3861about using Patterns: 3862<UL> 3863 <LI> <A HREF="h_rule_patterns">Patterns</A> 3864</UL> 3865<P> 3866<End of help on this topic> 3867</BODY> 3868</HTML> 3869===== h_mainhelp_cmdlineopts ====== 3870<HTML> 3871<HEAD> 3872<TITLE>Command Line Options</TITLE> 3873</HEAD> 3874<BODY> 3875<H1>Command Line Options</H1> 3876 3877Alpine accepts a number of command line arguments, allowing you, for 3878example, to start Alpine and immediately access a particular folder. 3879Many of these arguments overlap with options in the Alpine configuration file. 3880If there is a difference, then an option set on the command line takes 3881precedence. 3882Alpine expects command line arguments (other than addresses) to be 3883preceded by a "-" (dash) as normally used by UNIX programs. 3884A <a href="h_command_line_options">full list</a> of command line 3885possibilities is available. 3886<P> 3887<End of help on this topic> 3888</BODY> 3889</HTML> 3890===== h_mainhelp_config ====== 3891<HTML> 3892<HEAD> 3893<TITLE>Alpine Configuration</TITLE> 3894</HEAD> 3895<BODY> 3896<H1>Alpine Configuration</H1> 3897 3898Unless it has been administratively disabled, the Setup command on the 3899MAIN MENU has several subcommands that allow you to modify Alpine's behavior. 3900The possible subcommands are for general Configuration settings, 3901Printer settings, Changing your Password, Signature setup, 3902AddressBook setup, Collection Lists setup, Rules (including Roles, Filters, 3903Scores, Search, Indexcolor, and Other rules), LDAP Directory setup, 3904and Color configuration. 3905In particular, the "Config" subcommand has many features you may 3906set or unset and many other configuration variables that may be set to change 3907the way Alpine works. 3908Every one of the hundreds of options available in that configuration settings 3909screen has help text associated with it. 3910You may read that text by moving the cursor to highlight the option and then 3911typing the Help command. 3912<P> 3913These settings are stored in your personal 3914"pinerc" configuration file (or, optionally, they may be stored 3915<A HREF="h_config_remote_config">remotely</A>), 3916but on shared systems these settings 3917may be over-ridden by a system-wide control file (due to local site 3918security or support policies). A global pine configuration file can also 3919be used to set default values for all Alpine users on a particular system. 3920Power users may be interested in splitting their personal configuration 3921data into two pieces, a generic piece and 3922<A HREF="h_config_exceptions">exceptions</A> which apply to 3923a particular platform. 3924They may also be interested in <A HREF="h_config_inheritance">configuration inheritance</A>. 3925General Alpine configuration information can be found 3926<A HREF="h_news_config">here</A>. 3927<P> 3928<End of help on this topic> 3929</BODY> 3930</HTML> 3931===== h_mainhelp_aggops ====== 3932<HTML> 3933<HEAD> 3934<TITLE>Aggregate Operations</TITLE> 3935</HEAD> 3936<BODY> 3937<H1>Aggregate Operations</H1> 3938 3939When you are in the MESSAGE INDEX, the available commands 3940(for example, Delete, Undelete, Save, Reply, and so on) 3941normally act on a single message. 3942So, for example, if you press the Delete command, the currently highlighted 3943message is marked Deleted. 3944These commands that normally act on a single message may be applied to 3945several messages at once instead. 3946<P> 3947By default this feature is turned on, but it could be administratively turned 3948off to reduce complexity. 3949The feature 3950<A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A> 3951in the Setup/Config screen is used to turn it off or on. 3952When this feature is turned on, the four commands "Select", 3953"SelectCur", "ZoomMode", and "Apply" 3954are available. 3955The two selection commands allow you to mark a set of 3956messages as being "selected". 3957The "ZoomMode" command will toggle between 3958displaying only the selected messages and displaying all the messages. 3959The "Apply" command allows you to 3960apply one of the regular MESSAGE INDEX commands to all of the selected 3961messages instead of to only the highlighted message. 3962<P> 3963An example aggregate operation would be to catch up when reading 3964a news group. 3965That is, get rid of all the messages in the news group so that you can 3966start fresh. 3967The easiest way to do this in Alpine is to use aggregate operations. 3968You want to Delete all of the messages in the group. 3969You could start at the top and type "D" once for every message. 3970A much faster method is to first Select all of the messages in the group, 3971and then Delete all of them. 3972This would take four keystrokes: 3973<P> 3974<CENTER><SAMP>; a (to select all messages)</SAMP></CENTER> 3975<BR> 3976<CENTER><SAMP>a d (to delete all selected messages)</SAMP></CENTER> 3977<P> 3978Another use of Select is to use it for searching for a particular message 3979or set of messages in a large folder. 3980You may know that the message was From a certain user. 3981You could select all messages from that user to start, and use Zoom to 3982look at only those messages. 3983If there were still too many messages to look at you could Narrow the 3984set of messages further by selecting from all of those messages only 3985the ones that were after a certain date, or contained a particular phrase 3986in the Subject, or were too a particular address, and so on. 3987That may be the end of what you are doing, or you may want to use Apply to 3988Save or Forward or Print all of the selected messages. 3989<P> 3990Some related help topics are 3991<UL> 3992<LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>, 3993<LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>, 3994<LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>. 3995<LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>, 3996<LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and 3997<LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>. 3998</UL> 3999<P> 4000<End of help on this topic> 4001</BODY> 4002</HTML> 4003===== h_mainhelp_readingnews ====== 4004<HTML> 4005<HEAD> 4006<TITLE>Reading News</TITLE> 4007</HEAD> 4008<BODY> 4009<H1>Reading News</H1> 4010 4011<H2>Background</H2> 4012Alpine can read and post to Internet (or USENET) newsgroups, using the same 4013commands as for mail. Similar to mailing lists but existing on a larger scale, 4014Usenet newsgroups allow groups of people with common interests to discuss 4015particular topics. You might find newsgroups related to your career, or you 4016might wish to check out the online discussion among the fans of your favorite 4017television show. 4018 4019<H2>Configuring Alpine for Reading News</H2> 4020Alpine often arrives 4021pre-configured by your system administrator to automatically access the 4022newsgroups offered by your organization, Internet Service Provider, or 4023school. PC-Alpine users, and those attempting to customize Unix Alpine, will 4024need additional details on <a href="h_configuring_news">how to 4025configure Alpine to read news</a>. 4026 4027<H2>Accessing Newsgroups</H2> 4028The first step in reading news is to access the newsgroups collections 4029screen from Alpine. If everything is configured properly, you should be able 4030to do this by first typing L (folder List), then selecting the folder 4031collection listed as "News." The actual name of this collection may differ 4032from system to system. 4033 4034<H2>Subscribing to Newsgroups</H2> 4035 4036Once you have accessed the news collection, you need to subscribe to a 4037newsgroup that interests you. Subscribing to a newsgroup means that Alpine 4038will keep a record of the newsgroups in which you are interested and which 4039articles in those newsgroups have been read. 4040 4041<H2>Using Newsgroups</H2> 4042Alpine uses the similar commands to read news as to read mail. For example, 4043the D command marks messages as Deleted (or "Dismissed," if you prefer), 4044and the R command Replies to a news posting. Basically, Alpine allows you to 4045read news as if it were mail, so you don't need to change the way you 4046interact with Alpine. 4047<P> 4048There is also additional Alpine help available on 4049<A HREF="h_reading_news">how to use Alpine to read news</A>. 4050<P> 4051<End of help on this topic> 4052</BODY> 4053</HTML> 4054===== h_mainhelp_securing ====== 4055<HTML> 4056<HEAD> 4057<TITLE>Securing your Alpine Session</TITLE> 4058</HEAD> 4059<BODY> 4060<H1>Securing your Alpine Session</H1> 4061 4062By default, Alpine will attempt to connect to an IMAP server on the normal 4063IMAP service port (143). 4064If the Alpine you are using has been built to 4065support "Transport Layer Security" (TLS) 4066and "Secure Sockets Layer" (SSL) 4067(check by clicking <A HREF="X-Alpine-Config:">here</A>), 4068and the server offers the STARTTLS capability, then a secure (encrypted) 4069session will be established. 4070<P> 4071When you are connected to a remote folder the titlebar will contain a plus sign 4072in the far right column if the connection is encrypted using TLS or SSL. 4073Similarly, when you are being prompted for a password a plus sign will appear in the prompt 4074if the connection is encrypted. 4075 4076<H2>More Information on Alpine with SSL and TLS</H2> 4077<UL> 4078<LI> <A HREF="h_release_tlscerts">TLS and SSL Usage Note</A> </LI> 4079<LI> <A HREF="h_folder_server_syntax">/SSL</A> option for older servers which support port 993 SSL but not TLS </LI> 4080<LI> <A HREF="h_config_alt_auth"><!--#echo var="FEAT_try-alternative-authentication-driver-first"--></A> feature </LI> 4081<LI> <A HREF="h_config_quell_ssl_largeblocks"><!--#echo var="FEAT_quell-ssl-largeblocks"--></A> PC-Alpine feature for working around OS SSL-problems</A> </LI> 4082</UL> 4083<H2>Here are some other security-related features and options</H2> 4084<P> 4085<UL> 4086<LI> <A HREF="h_config_disable_password_caching"><!--#echo var="FEAT_disable-password-caching"--></A> feature to disable password caching </LI> 4087<LI> <A HREF="h_config_disable_password_file_saving"><!--#echo var="FEAT_disable-password-file-saving"--></A> Disable password file saving</LI> 4088<LI> <A HREF="h_config_mailcap_params"><!--#echo var="FEAT_enable-mailcap-param-substitution"--></A> feature </LI> 4089<LI> <A HREF="h_config_disable_auths"><!--#echo var="VAR_disable-these-authenticators"--></A> option </LI> 4090<LI> <A HREF="h_config_encryption_range"><!--#echo var="VAR_encryption-protocol-range"--></A> option </LI> 4091</UL> 4092<P> 4093<End of help on this topic> 4094</BODY> 4095</HTML> 4096===== h_mainhelp_problems ====== 4097<HTML> 4098<HEAD> 4099<TITLE>Reporting Problems</TITLE> 4100</HEAD> 4101<BODY> 4102<H1>Reporting Problems</H1> 4103 4104We ask that you first read the relevant help screens and then seek 4105assistance from your own local support staff. Once you are sure that your 4106difficulty is not a local configuration problem, you might look at the 4107help section explaining where to look for 4108<A HREF="h_finding_help">more information</A> and where to 4109get assistance. 4110<P> 4111 4112<ADDRESS> 4113 Eduardo Chappa <chappa@gmx.com> 4114</ADDRESS> 4115 4116<P> 4117<End of help on this topic> 4118</BODY> 4119</HTML> 4120===== h_main_menu_commands ====== 4121<HTML> 4122<HEAD> 4123<TITLE>MAIN MENU COMMANDS</TITLE> 4124</HEAD> 4125<BODY> 4126<H1>MAIN MENU COMMANDS</H1> 4127 4128<!--chtml if pinemode="function_key"--> 4129 Available Commands -- 4130 Group 1 Available Commands -- Group 2<BR> 4131 ------------------------------ 4132 -------------------- 4133----------<BR> 4134 F1 Show this help text F1 Show this help text<BR> 4135 F2 Show all other available commands F2 Show other commands<BR> 4136 F3 Quit Alpine<BR> 4137 F4 Execute current MAIN MENU command F4 <A 4138HREF="h_common_compose">Compose</A> a message<BR> 4139 F5 Select previous command up on menu F5 <A 4140HREF="h_common_folders">FOLDER LIST</A> screen<BR> 4141 F6 Select next command down on menu F6 <A 4142HREF="h_common_goto">Goto</A> a specified folder<BR> 4143 4144 F7 <A 4145HREF="h_common_index">MESSAGE INDEX</A> screen<BR> 4146 4147 F8 <A 4148HREF="h_main_journal">Journal</A> of status messages<BR> 4149 F9 Display <A 4150HREF="h_main_release_notes">Release Notes</A> notes F9 <A 4151HREF="h_main_setup">SETUP</A> menus<BR> 4152 F10 <A 4153HREF="h_main_kblock">Lock Keyboard</A> F10 <A 4154HREF="h_main_addrbook">ADDRESS BOOK</A> screen<BR> 4155 4156 F11 <A 4157HREF="h_common_role">Compose message using a role</a><BR> 4158<!--chtml else--> 4159 General Alpine Commands Main Menu Screen Commands<BR> 4160 --------------------- --------------------------<BR> 4161 ? Show Help Text O Show all Other available commands<BR> 4162 C <A 4163HREF="h_common_compose">Compose</A> a message P Select Previous command up on menu<BR> 4164 I <A 4165HREF="h_common_index">MESSAGE INDEX</A> screen N Select Next command down on menu<BR> 4166 L <A 4167HREF="h_common_folders">FOLDER LIST</A> screen R Display Alpine <A HREF="h_main_release_notes">Release Notes</A><BR> 4168 A <A 4169HREF="h_main_addrbook">ADDRESS BOOK</A> screen K <A 4170HREF="h_main_kblock">Lock Keyboard</A><BR> 4171 S <A 4172HREF="h_main_setup">SETUP</A> functions G <A 4173HREF="h_common_goto">Goto</A> a specified folder<BR> 4174 Q Quit Alpine J <A HREF="h_main_journal">Journal</A> of status messages<BR> 4175 # <A 4176HREF="h_common_role">Compose message using a role</a><BR> 4177<!--chtml endif--> 4178 4179<P> 4180NOTE: 4181<OL> 4182 <LI>For help on a particular command, highlight the bold text associated 4183with it above and hit Return. 4184 <LI> The availability of certain commands (e.g. some of the options under 4185SETUP) is determined by Alpine configuration files and system capabilities. 4186At some sites, certain commands may not be available due to security or 4187support concerns. 4188</OL> 4189<P> 4190<End of help on this topic> 4191</BODY> 4192</HTML> 4193 4194===== h_command_line_options ====== 4195<HTML> 4196<HEAD> 4197<TITLE>COMMAND LINE OPTIONS</TITLE> 4198</HEAD> 4199<BODY> 4200<H1>COMMAND LINE OPTIONS</H1> 4201Possible starting arguments for Alpine: 4202 4203<DL COMPACT> 4204 4205<DT> <EM>[addresses]</EM> 4206 4207<DD> Send-to: If you give <EM>Alpine</EM> an argument or arguments which 4208do not begin with a dash, <EM>Alpine</EM> treats them as email addresses. 4209<EM>Alpine</EM> will startup in 4210the composer with a message started to the addresses specified. 4211Once the message is sent, the <EM>Alpine</EM> session closes. 4212Standard input redirection is allowed. 4213Separate multiple addresses with a space between them. 4214Addresses are placed in the "To" field only. 4215<P> 4216 4217<DT> < <EM>file</EM> 4218 4219<DD> <EM>Alpine</EM> will startup in the composer with <EM>file</EM> read 4220into the body of the message. 4221Once the message is sent, the <EM>Alpine</EM> session closes. 4222<P> 4223 4224<DT> -attach <EM>file</EM> 4225 4226<DD> Go directly into composer with given file attached. 4227<P> 4228 4229<DT> -attachlist <EM>file-list</EM> 4230 4231<DD> Go directly into composer with given files attached. 4232This must be the last option on the command line. 4233<P> 4234 4235<DT> -attach_and_delete <EM>file</EM> 4236 4237<DD> Go directly into composer with given file attached, delete when finished. 4238<P> 4239 4240<DT> -aux <EM>local_directory</EM> 4241 4242<DD> <EM>PC-Alpine</EM> only. 4243This tells <EM>PC-Alpine</EM> the local directory to use for storing auxiliary 4244files, like debug files, address books, and signature files. The pinerc may 4245be local or remote. 4246<P> 4247 4248<DT> -bail 4249 4250<DD> If the personal configuration file doesn't already exist, exit. 4251This might be useful if the configuration file is accessed using some 4252remote filesystem protocol. If the remote mount is missing this will cause 4253<EM>Alpine</EM> to quit instead of creating a new pinerc. 4254<P> 4255 4256<DT> -c <EM>n</EM> 4257 4258<DD> When used with the <CODE>-f</CODE> option, apply the <EM>n</EM>th context. 4259This is used when there are multiple folder collections (contexts) and you 4260want to open a folder not in the primary collection. 4261<P> 4262 4263<DT> -conf 4264 4265<DD> Configuration: Prints a sample system configuration file to the 4266screen or standard output. To generate an initial system configuration 4267file, execute 4268 4269<PRE><CODE> 4270 pine -conf > <!--#echo var="PINE_CONF_PATH"--> 4271</CODE></PRE> 4272<P> 4273 4274To generate a system configuration file using settings from an old 4275system configuration file, execute 4276 4277<PRE><CODE> 4278 pine -P old-alpine.conf -conf > <!--#echo var="PINE_CONF_PATH"--> 4279</CODE></PRE> 4280<P> 4281A system configuration file is not required. 4282<P> 4283 4284<DT> -copy_abook <<EM>local_abook_file</EM>> <<EM>remote_abook_folder</EM>> 4285 4286<DD> Copy an address book file to a remote address book folder. 4287If the remote folder doesn't exist, it will be created. 4288If it exists but the first message in the folder isn't a remote address 4289book header message, the copy will be aborted. 4290This flag will not usually be used by a user. 4291Instead, the user will create a remote address book from within <EM>Alpine</EM> 4292and copy entries from the local address book by using aggregate Save in 4293the address book screen. 4294<P> 4295 4296<DT> -copy_pinerc <<EM>local_pinerc_file</EM>> <<EM>remote_pinerc_folder</EM>> 4297 4298<DD> Copy a pinerc configuration file to a remote pinerc folder. 4299If the remote folder doesn't exist, it will be created. 4300If it exists but the first message in the folder isn't a remote pinerc 4301header message, the copy will be aborted. 4302This flag may be useful to users who already have a local pinerc file and 4303would like to convert it to a remote pinerc folder and use that instead. 4304This gives a way to bootstrap that conversion without having to manually 4305reset all of the variables in the remote pinerc folder. 4306<P> 4307 4308<DT> -d <EM>debug-level</EM> 4309 4310<DD> Debug Level: Sets the level of debugging information written by 4311<EM>Alpine</EM>. 4312<EM>debug-level</EM> can be set to any integer 0-9. 4313A debug level of 0 turns off debugging for the session. 4314(Actually there are some levels higher than 9, but you probably don't 4315want to see them.) 4316<P> 4317 4318<DT> -d <EM>keywords</EM> 4319 4320<DD> You may use a more detailed version of the debugging flag to set 4321the debug level in separate parts of <EM>Alpine</EM>. 4322The possibilities are flush, timestamp, imap=0..4, tcp, numfiles=0..31, and 4323verbose=0..9. 4324<EM>Flush</EM> causes debugging information to be flushed immediately to 4325the debug file as it is written. 4326<EM>Verbose</EM> is the general debugging verbosity level. 4327<EM>Timestamp</EM> causes timestamps to be added to the debug file, which 4328is useful when you are trying to figure out what is responsible for delays. 4329<EM>Numfiles</EM> sets the number of debug files saved. 4330<EM>Imap</EM> sets the debug level for the debugging statements related 4331to the conversation with the IMAP server, and more generally, for the 4332debugging related to <EM>Alpine</EM>'s interaction with the C-Client library. 4333<EM>Tcp</EM> turns on some TCP/IP debugging. 4334<P> 4335 4336<DT> -f <EM>folder</EM> 4337 4338<DD> Startup folder: <EM>Alpine</EM> will open this folder in place 4339of the standard INBOX. 4340<P> 4341 4342<DT> -F <EM>file</EM> 4343 4344<DD> Open named text file for viewing and forwarding. 4345<P> 4346 4347<DT> -h 4348 4349<DD> Help: Prints the list of available command-line arguments to the 4350screen. 4351<P> 4352 4353<DT> -i 4354 4355<DD> <EM>Alpine</EM> will start up in the FOLDER INDEX 4356screen instead of the MAIN MENU. 4357<P> 4358 4359Configuration equivalent: <EM><!--#echo var="VAR_initial-keystroke-list"-->=i</EM>. 4360<P> 4361 4362<DT> -I <EM>a,b,c,...</EM> 4363 4364<DD> Initial Keystrokes: <EM>Alpine</EM> will execute this comma-separated 4365sequence of commands upon startup. 4366This allows users to get <EM>Alpine</EM> to start in any 4367of its menus/screens. 4368You cannot include any input to the composer in the initial keystrokes. 4369The key <Return> is represented by a ``CR'' in 4370the keystroke list; the spacebar is designated by the letters ``SPACE''. 4371Control keys are two character sequences beginning with ``^'', such as 4372``^I''. 4373A tab character is ``TAB''. 4374Function keys are ``F1'' - ``F12'' and the arrow keys are ``UP'', 4375``DOWN'', ``LEFT'', and ``RIGHT''. 4376A restriction is that you can't mix function keys and character keys in this 4377list even though you can, in some cases, mix them when running <EM>Alpine</EM>. 4378A user can always use only <EM>character</EM> keys in the startup list even 4379if he or she is using <EM>function</EM> keys normally, or vice versa. 4380If an element in this list is a string of characters surrounded by double 4381quotes (") then it will be expanded into the individual characters in 4382the string, excluding the double quotes. 4383<P> 4384 4385Configuration equivalent: <EM><!--#echo var="VAR_initial-keystroke-list"--></EM> 4386<P> 4387 4388<DT> -install 4389 4390<DD> For <EM>PC-Alpine</EM> only, this option prompts the user for 4391some basic information to help with getting properly set up. 4392<P> 4393 4394<DT> -k 4395 4396<DD> Function-Key Mode: When invoked in this way, <EM>Alpine</EM> expects 4397the input of commands to be function-keys. 4398Otherwise, commands are linked to the regular character keys. 4399<P> 4400 4401Configuration equivalent: <EM><!--#echo var="FEAT_use-function-keys"--></EM> included in 4402<EM>Feature-List</EM>. 4403<P> 4404 4405<DT> -n <EM>n</EM> 4406 4407<DD> Message-Number: When specified, <EM>Alpine</EM> starts up in the 4408FOLDER INDEX screen with the current message being the specified 4409message number. 4410<P> 4411 4412<DT> -nosplash 4413 4414<DD> <EM>PC-Alpine</EM> only. 4415This tells <EM>PC-Alpine</EM> not to display the splash screen upon startup. 4416This may be helpful for certain troubleshooting or terminal server scenarios. 4417<P> 4418 4419<DT> -o <EM>folder</EM> 4420 4421<DD> Opens the INBOX (or a folder specified via the -f argument) ReadOnly. 4422<P> 4423 4424<DT> -p <EM>pinerc</EM> 4425 4426<DD> Uses the named file as the personal configuration file instead of 4427<EM>~/.pinerc</EM> or the default PINERC search sequence <EM>PC-Alpine</EM> uses. 4428Alpinerc may be either a local file or a remote configuration folder. 4429<P> 4430 4431<DT> -P <EM>pinerc</EM> 4432 4433<DD> Uses the named file as the system wide configuration file instead of 4434<EM><!--#echo var="PINE_CONF_PATH"--></EM> on UNIX, or nothing on <EM>PC-Alpine</EM>. 4435Alpinerc may be either a local file or a remote configuration folder. 4436<P> 4437 4438<DT> -passfile <EM>passfile</EM> 4439 4440<DD> This tells <EM>Alpine</EM> what file should be used as the password file. 4441This should be a fully-qualified filename. 4442<P> 4443 4444<DT> -pinerc <EM>file</EM> 4445 4446<DD> Output fresh pinerc configuration to <EM>file</EM>, preserving the 4447settings of variables that the user has made. 4448Use <EM>file</EM> set to ``-'' to make output go to standard out. 4449<P> 4450 4451<DT> -r 4452 4453<DD> Restricted Mode: For UNIX <EM>Alpine</EM> only. 4454<EM>Alpine</EM> in restricted mode can only send email to itself. 4455Save and export are limited. 4456<P> 4457 4458<DT> -registry <EM>cmd</EM> 4459 4460<DD> For <EM>PC-Alpine</EM> only, this option affects the values of 4461<EM>Alpine</EM>'s registry entries. 4462Possible values for <EM>cmd</EM> are set, clear, and dump. 4463<EM>Set</EM> will always reset <EM>Alpine</EM>'s registry 4464entries according to its current settings. 4465<EM>Clear</EM> will clear the registry values. 4466<EM>Clearsilent</EM> will clear the registry values without any dialogs. 4467<EM>Dump</EM> will display the values of current registry settings. 4468Note that the dump command is currently disabled. 4469Without the -registry option, <EM>PC-Alpine</EM> will write values into 4470the registry only if there currently aren't any values set. 4471<P> 4472 4473<DT> -sort <EM>key</EM> 4474 4475<DD> Sort-Key: Specifies the order messages will be displayed in for the 4476FOLDER INDEX screen. 4477<EM>Key</EM> can have the following values: 4478arrival, date, subject, orderedsubj, thread, from, size, score, to, cc, 4479arrival/reverse, date/reverse, subject/reverse, orderedsubj/reverse, thread/reverse, 4480from/reverse, size/reverse, score/reverse, to/reverse, and cc/reverse. 4481The default value is "arrival". 4482The <EM>key</EM> value reverse is equivalent to arrival/reverse. 4483<P> 4484 4485Configuration equivalent: <EM><!--#echo var="VAR_sort-key"--></EM>. 4486<P> 4487 4488<DT> -uninstall 4489 4490<DD> For <EM>PC-Alpine</EM> only, this option removes references to Alpine 4491in Windows settings. The registry settings are removed and 4492the password cache is cleared. 4493<P> 4494 4495<DT> -url <EM>url</EM> 4496 4497<DD> Open the given URL. 4498<P> 4499 4500<DT> -v 4501 4502<DD> Version: Print version information to the screen. 4503<P> 4504 4505<DT> -x <EM>exceptions_config</EM> 4506 4507<DD> Configuration settings in the exceptions configuration override your normal 4508default settings. 4509<EM>Exceptions_config</EM> may be either a local file or a remote Alpine configuration folder. 4510<P> 4511 4512<DT> -z 4513 4514<DD> Enable Suspend: When run with this flag, the key sequence ctrl-z 4515will suspend the <EM>Alpine</EM> session. 4516<P> 4517 4518Configuration equivalent: <EM><!--#echo var="FEAT_enable-suspend"--></EM> included in 4519<EM>Feature-List</EM>. 4520<P> 4521 4522<DT> -<EM>option</EM>=<EM>value</EM> 4523 4524<DD> Assign <EM>value</EM> to the config option <EM>option</EM>. 4525For example, <EM>-signature-file=sig1</EM> or 4526<EM>-Feature-List=signature-at-bottom</EM>. 4527Note: Feature-List values are 4528additive and features may be preceded with no- to turn them off. 4529Also, as a special case, the "Feature-List=" part of that may be 4530omitted. For example, <EM>-signature-at-bottom</EM> is equivalent to 4531<EM>-Feature-List=signature-at-bottom</EM>. 4532<P> 4533 4534</DL> 4535<P> 4536<End of help on this topic> 4537</BODY> 4538</HTML> 4539===== h_configuring_news ====== 4540<HTML> 4541<HEAD> 4542<TITLE>CONFIGURING NEWS</TITLE> 4543</HEAD> 4544<BODY> 4545<H1>CONFIGURING NEWS</H1> 4546Alpine can access news folders in any one of three different ways: 4547<DL> 4548<DT>REMOTE NNTP</DT> 4549<DD>Using the Network News Transport Protocol (NNTP) to 4550access news on a remote news server. In this case the newsrc file is 4551stored on the machine where Alpine is running. 4552 4553<P> 4554To specify a remote news-collection accessed via NNTP use the 4555SETUP/collectionList screen's "Add" command. Set the 4556Server: value to the NNTP server's hostname appended with the 4557communication method "/service=NNTP", and set the Path: 4558value to the "#news." namespace (without the quotes). See 4559the "<A HREF="h_composer_cntxt_server">Server:</A>" field's 4560help text for a more complete explanation of access method, and the 4561"<A HREF="h_composer_cntxt_path">Path:</A>" field's help 4562text for a more complete explanation of "namespace". 4563<P> 4564Instead of specifying a news-collection, you may simply set the 4565<A HREF="h_config_nntp_server">NNTP Server</A> 4566option, which will cause Alpine to create a default news-collection for you. 4567Another NNTP option that may be of interest is 4568<A HREF="h_config_nntprange"><!--#echo var="VAR_nntp-range"--></A>. 4569 4570<DT>REMOTE IMAP</DT> 4571<DD>Using the Internet Message Access Protocol (IMAP) to 4572access news on a remote news server. In this case, your newsrc file is 4573stored on the news server, in your home directory, so you must have an 4574account on the news server, but you would be running Alpine on a different 4575machine. The news server must be running an IMAPd server process. 4576 4577<P> 4578To specify a remote news-collection accessed via IMAP use the 4579SETUP/collectionList screen's "Add" command. Set the 4580Server: value to the IMAP server's hostname, and set the Path: value 4581to the "#news." namespace (without the quotes). See the 4582"<A HREF="h_composer_cntxt_path">Path:</A>" field's help 4583text for a more complete explanation of "namespace". 4584 4585</DD> 4586 4587<DT>LOCAL</DT> 4588<DD>Using local file access to the news database. In this 4589case, your newsrc file is stored on the news server, in your home 4590directory, so you must have an account on the news server, and you would 4591be running Alpine on the same machine. 4592 4593<P> 4594To specify a local news-collection use the SETUP/collectionList 4595screen's "Add" command. Leave the Server: value blank, and 4596set the Path: value to the "#news." namespace (without the 4597quotes). See the "<A HREF="h_composer_cntxt_path">Path:</A>" 4598field's help text for a more complete explanation of "namespace". 4599 4600</DD> 4601</DL> 4602 4603<P> 4604 4605NOTE: Should no news-collection be defined as above, Alpine will 4606automatically create one using the Setup/Config screen's 4607"<!--#echo var="VAR_nntp-server"-->" variable's value if defined. The collection 4608will be created as a "Remote NNTP" as described above. 4609 4610<P> 4611 4612If you are a PC-Alpine user, either option 1 (NNTP) or option 2 (IMAP) is 4613possible. If you don't have an account on the news server, or if the news 4614server is not running an IMAP daemon, then you must use NNTP. (If you are not 4615sure, ask your service provider, university, or company for help.) In 4616this case, your Unix .newsrc file can be transferred to your PC. A good 4617place to put it would be in the same directory as your PINERC file, under 4618the name NEWSRC, but you can 4619<A HREF="h_config_newsrc_path">specify a different location</A> 4620via Alpine's Setup/Config screen. 4621 4622<P> 4623Other configuration features related to news are 4624<A HREF="h_config_8bit_nntp"><!--#echo var="FEAT_enable-8bit-nntp-posting"--></A>. 4625<A HREF="h_config_compose_news_wo_conf"><!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></A>, 4626<A HREF="h_config_news_uses_recent"><!--#echo var="FEAT_news-approximates-new-status"--></A>, 4627<A HREF="h_config_news_cross_deletes"><!--#echo var="FEAT_news-deletes-across-groups"--></A>, 4628<A HREF="h_config_news_catchup"><!--#echo var="FEAT_news-offers-catchup-on-close"--></A>, 4629<A HREF="h_config_post_wo_validation"><!--#echo var="FEAT_news-post-without-validation"--></A>, 4630<A HREF="h_config_read_in_newsrc_order"><!--#echo var="FEAT_news-read-in-newsrc-order"--></A>, and 4631<A HREF="h_config_quell_post_prompt"><!--#echo var="FEAT_quell-extra-post-prompt"--></A>. 4632 4633<P> 4634<End of help on this topic> 4635</BODY> 4636</HTML> 4637===== h_reading_news ====== 4638<HTML> 4639<HEAD> 4640<TITLE>READING NEWS</TITLE> 4641</HEAD> 4642<BODY> 4643<H1>READING NEWS</H1> 4644 4645Alpine uses almost the same commands for manipulating news folders as for 4646mail folders. This means, for example, that when you are done with a 4647message, you would use "D" to mark it as Deleted (or Dismissed, 4648if you prefer.) This "mail-like" behavior differs from that of 4649most newsreaders, wherein a message is implicitly dismissed after you have 4650looked at it once. We strongly believe that Alpine should offer as much 4651consistency as possible between mail and news, so the mail paradigm -- 4652wherein a message does not magically disappear without explicit action by 4653the user -- is used for news as well. <P> 4654 4655If you answer a message in a news folder, the index view will show the 4656"A" flag as usual; but the industry standard file Alpine uses to 4657keep track of what news as been read has no way of storing this flag, so 4658it will not be preserved across sessions. The Deleted flag is the only 4659one that is preserved when you leave and then return to a newsgroup. As an 4660additional note on replies, when you Reply to a newsgroup message and say 4661you want to reply to all recipients, Alpine will ask if you want to post the 4662message to all the newsgroups listed in the original message. <P> 4663 4664If you would like Alpine to mark more-or-less recent news messages as 4665"New", then set the 4666<A HREF="h_config_news_uses_recent">"<!--#echo var="FEAT_news-approximates-new-status"-->"</A> 4667feature (which is set by default). This will cause messages after the last one you have marked as 4668Deleted to appear with "N" status in the MESSAGE INDEX. The 4669"N" status often makes it easier to distinguish later news 4670articles from those you've previously seen, but not yet disposed of via 4671the "D" key. Note that this is an approximation, not an exact 4672record of which messages you have not seen. 4673<P> 4674 4675A frequent operation in news-reading is "catching up" -- that 4676is, getting rid of all the messages in the newsgroup so that you can 4677"start fresh." The easiest way to do this in Alpine is via the 4678Select command. You would enter the following four keystrokes: 4679<tt>;aad</tt> to select all messaged, and then apply the delete (or 4680dismiss) command to all of them. 4681 4682<P> 4683There are also additional details on 4684<A HREF="h_configuring_news">configuring news</a>. 4685 4686<P> 4687<End of help on this topic> 4688</BODY> 4689</HTML> 4690====== h_help_index ====== 4691<HTML> 4692<HEAD> 4693<TITLE>Help Index</TITLE> 4694</HEAD> 4695<BODY> 4696<H1>Help Index</H1> 4697<ul> 4698<li><a href="h_mainhelp_abooks">Address Books</a></li> 4699<li><a href="h_abook_top">ADDRESS BOOK LIST COMMANDS</a> 4700<li><a href="h_main_addrbook">Address Book Command</a> 4701<li><a href="h_abook_view">Address Book View Explained</a> 4702<li><a href="h_compose_addrcomplete">Address Completion</a> 4703<li><a href="h_abook_select_listmode">Address Listmode Selection from Composer Explained</a> 4704<li><a href="h_abook_select_checks">Address Selection from Composer Explained</a> 4705<li><a href="h_composer_abook_comment">Addressbook Comment Explained</a> 4706<li><a href="h_composer_abook_fcc">Addressbook Fcc Explained</a> 4707<li><a href="h_composer_abook_add_folder">Addressbook Folder Name Field Explained</a> 4708<li><a href="h_composer_abook_full">Addressbook Fullname Explained</a> 4709<li><a href="h_composer_abook_add_nick">Addressbook NickName Field Explained</a> 4710<li><a href="h_composer_abook_nick">Addressbook Nickname Explained</a> 4711<li><a href="h_abook_select_addr">Addressbook Selection Explained</a> 4712<li><a href="h_abook_select_top">Addressbook Selection Navigation Explained</a> 4713<li><a href="h_composer_abook_add_server">Addressbook Server Name Field Explained</a> 4714<li><a href="h_mainhelp_aggops">Aggregate Operations</a> 4715<li><a href="h_mainhelp_config">Alpine Configuration</a> 4716<li><a href="h_mainhelp_pinehelp">Alpine Help</a> 4717<li><a href="h_news_legal">Alpine Legal Notices</a> 4718<li><a href="h_compose_alted">Alt Editor Command</a> 4719<li><a href="h_index_cmd_apply">Apply Command</a> 4720<li><a href="h_attachment_screen">Attachment Index Screen Explained</a> 4721<li><a href="h_mail_text_att_view">Attachment View Screen Explained</a> 4722<li><a href="h_mainhelp_filtering">Blocking Messages</a> 4723<li><a href="h_composer_browse">BROWSER</a> 4724<li><a href="h_common_bounce">Bounce Command</a> 4725<li><a href="h_compose_cancel">Cancel Command</a> 4726<li><a href="h_config_change_your_from">Changing your From Address</a> 4727<li><a href="h_collection_screen">COLLECTION LIST screen</a> 4728<li><a href="h_mainhelp_color">Color</a> 4729<li><a href="h_composer_ctrl_j">COMPOSER ATTACH</a> 4730<li><a href="h_composer">COMPOSER COMMANDS</a> 4731<li><a href="h_mainhelp_composing">Composing Messages</a> 4732<li><a href="h_mainhelp_collections">Collection Lists</a> 4733<li><a href="h_composer_cntxt_nick">Collection Nickname Explained</a> 4734<li><a href="h_composer_cntxt_path">Collection Path: Explained</a> 4735<li><a href="h_composer_cntxt_server">Collection Server: Explained</a> 4736<li><a href="h_composer_cntxt_view">Collection View: Explained</a> 4737<li><a href="h_mainhelp_cmdlineopts">Command Line Options</a> 4738<li><a href="h_common_compose">Compose Command</a> 4739<li><a href="h_edit_nav_cmds">Composer Editing Commands Explained</a> 4740<li><a href="h_common_conditional_cmds">Conditional Commands</a> 4741<li><a href="h_reply_token_conditionals">Conditional Inclusion of Text for <!--#echo var="VAR_reply-leadin"-->, Signatures, and Templates</a> 4742<li><a href="h_mainhelp_config">Configuration</a> 4743<li><a href="h_composer_custom_free">CUSTOMIZED HEADER FIELD</a> 4744<li><a href="h_config_dflt_color">Default Color</a> 4745<li><a href="h_common_delete">Delete and Undelete Commands</a> 4746<li><a href="h_composer_qserv_cn">Directory Query Form Explained</a> 4747<li><a href="h_special_list_commands">Email List Commands Explained</a> 4748<li><a href="h_composer_search">Explanation of Composer Whereis Command </a> 4749<li><a href="h_folder_open">Explanation of Folder Selection</a> 4750<li><a href="h_special_xon_xoff">Explanation of Alpine's XOFF/XON Handling</a> 4751<li><a href="h_valid_folder_names">Explanation of Valid Folder Names</a> 4752<li><a href="h_ge_export">Export File Selection</a> 4753<li><a href="h_ge_allparts">Export Message File Selection</a> 4754<li><a href="h_index_cmd_expunge">Expunge/Exclude Command</a> 4755<li><a href="h_info_on_locking">FAQs on Alpine Locking</a> 4756<li><a href="h_config_allow_chg_from">FEATURE: <!--#echo var="FEAT_allow-changing-from"--></a> 4757<li><a href="h_config_allow_talk">FEATURE: <!--#echo var="FEAT_allow-talk"--></a> 4758<li><a href="h_config_alt_compose_menu">FEATURE: <!--#echo var="FEAT_alternate-compose-menu"--></a> 4759<li><a href="h_config_alt_role_menu">FEATURE: <!--#echo var="FEAT_alternate-role-menu"--></a> 4760<li><a href="h_config_alt_reply_menu">FEATURE: <!--#echo var="FEAT_alternate-reply-menu"--></a> 4761<li><a href="h_config_force_low_speed">FEATURE: <!--#echo var="FEAT_assume-slow-link"--></a> 4762<li><a href="h_config_auto_read_msgs">FEATURE: <!--#echo var="FEAT_auto-move-read-msgs"--></a> 4763<li><a href="h_config_auto_open_unread">FEATURE: <!--#echo var="FEAT_auto-open-next-unread"--></a> 4764<li><a href="h_config_auto_unselect">FEATURE: <!--#echo var="FEAT_auto-unselect-after-apply"--></a> 4765<li><a href="h_config_auto_unzoom">FEATURE: <!--#echo var="FEAT_auto-unzoom-after-apply"--></a> 4766<li><a href="h_config_auto_zoom">FEATURE: <!--#echo var="FEAT_auto-zoom-after-select"--></a> 4767<li><a href="h_config_use_boring_spinner">FEATURE: <!--#echo var="FEAT_busy-cue-spinner-only"--></a> 4768<li><a href="h_config_check_mail_onquit">FEATURE: <!--#echo var="FEAT_check-newmail-when-quitting"--></a> 4769<li><a href="h_config_combined_abook_display">FEATURE: <!--#echo var="FEAT_combined-addrbook-display"--></a> 4770<li><a href="h_config_combined_folder_display">FEATURE: <!--#echo var="FEAT_combined-folder-display"--></a> 4771<li><a href="h_config_combined_subdir_display">FEATURE: <!--#echo var="FEAT_combined-subdirectory-display"--></a> 4772<li><a href="h_config_cancel_confirm">FEATURE: <!--#echo var="FEAT_compose-cancel-confirm-uses-yes"--></a> 4773<li><a href="h_config_lame_list_mode">FEATURE: <!--#echo var="FEAT_enable-lame-list-mode"--></a> 4774<li><a href="h_config_compose_rejects_unqual">FEATURE: <!--#echo var="FEAT_compose-rejects-unqualified-addrs"--></a> 4775<li><a href="h_config_send_filter_dflt">FEATURE: <!--#echo var="FEAT_compose-send-offers-first-filter"--></a> 4776<li><a href="h_config_compose_news_wo_conf">FEATURE: <!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></a> 4777<li><a href="h_config_del_from_dot">FEATURE: <!--#echo var="FEAT_compose-cut-from-cursor"--></a> 4778<li><a href="h_config_compose_maps_del">FEATURE: <!--#echo var="FEAT_compose-maps-delete-key-to-ctrl-d"--></a> 4779<li><a href="h_config_confirm_role">FEATURE: <!--#echo var="FEAT_confirm-role-even-for-default"--></a> 4780<li><a href="h_config_tab_no_prompt">FEATURE: <!--#echo var="FEAT_continue-tab-without-confirm"--></a> 4781<li><a href="h_config_dates_to_local">FEATURE: <!--#echo var="FEAT_convert-dates-to-localtime"--></a> 4782<li><a href="h_config_copy_to_to_from">FEATURE: <!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></a> 4783<li><a href="h_config_del_skips_del">FEATURE: <!--#echo var="FEAT_delete-skips-deleted"--></a> 4784<li><a href="h_config_disable_config_cmd">FEATURE: <!--#echo var="FEAT_disable-config-cmd"--></a> 4785<li><a href="h_config_disable_index_locale_dates">FEATURE: <!--#echo var="FEAT_disable-index-locale-dates"--></a> 4786<li><a href="h_config_disable_kb_lock">FEATURE: <!--#echo var="FEAT_disable-keyboard-lock-cmd"--></a> 4787<li><a href="h_config_blank_keymenu">FEATURE: <!--#echo var="FEAT_disable-keymenu"--></a> 4788<li><a href="h_config_disable_password_caching">FEATURE: <!--#echo var="FEAT_disable-password-caching"--></a> 4789<li><a href="h_config_disable_password_cmd">FEATURE: <!--#echo var="FEAT_disable-password-cmd"--></a> 4790<li><a href="h_config_disable_pipes_in_sigs">FEATURE: <!--#echo var="FEAT_disable-pipes-in-sigs"--></a> 4791<li><a href="h_config_disable_pipes_in_templates">FEATURE: <!--#echo var="FEAT_disable-pipes-in-templates"--></a> 4792<li><a href="h_config_disable_regex">FEATURE: <!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></a> 4793<li><a href="h_config_disable_roles_setup">FEATURE: <!--#echo var="FEAT_disable-roles-setup-cmd"--></a> 4794<li><a href="h_config_disable_roles_sigedit">FEATURE: <!--#echo var="FEAT_disable-roles-sig-edit"--></a> 4795<li><a href="h_config_disable_roles_templateedit">FEATURE: <!--#echo var="FEAT_disable-roles-template-edit"--></a> 4796<li><a href="h_config_input_history">FEATURE: <!--#echo var="FEAT_disable-save-input-history"--></a> 4797<li><a href="h_config_disable_collate">FEATURE: <!--#echo var="FEAT_disable-setlocale-collate"--></a> 4798<li><a href="h_config_disable_shared">FEATURE: <!--#echo var="FEAT_disable-shared-namespaces"--></a> 4799<li><a href="h_config_disable_signature_edit">FEATURE: <!--#echo var="FEAT_disable-signature-edit-cmd"--></a> 4800<li><a href="h_config_delete_before_writing">FEATURE: <!--#echo var="FEAT_enable-delete-before-writing"--></a> 4801<li><a href="h_config_take_fullname">FEATURE: <!--#echo var="FEAT_disable-take-fullname-in-addresses"--></a> 4802<li><a href="h_config_take_lastfirst">FEATURE: <!--#echo var="FEAT_disable-take-last-comma-first"--></a> 4803<li><a href="h_config_disable_reset_disp">FEATURE: <!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></a> 4804<li><a href="h_config_disable_sender">FEATURE: <!--#echo var="FEAT_disable-sender"--></a> 4805<li><a href="h_config_quell_dead_letter">FEATURE: <!--#echo var="FEAT_quell-dead-letter-on-cancel"--></a> 4806<li><a href="h_config_quell_flowed_text">FEATURE: <!--#echo var="FEAT_quell-flowed-text"--></a> 4807<li><a href="h_downgrade_multipart_to_text">FEATURE: <!--#echo var="FEAT_downgrade-multipart-to-text"--></a> 4808<li><a href="h_config_8bit_smtp">FEATURE: <!--#echo var="FEAT_enable-8bit-esmtp-negotiation"--></a> 4809<li><a href="h_config_8bit_nntp">FEATURE: <!--#echo var="FEAT_enable-8bit-nntp-posting"--></a> 4810<li><a href="h_config_enable_agg_ops">FEATURE: <!--#echo var="FEAT_enable-aggregate-command-set"--></a> 4811<li><a href="h_config_enable_alt_ed">FEATURE: <!--#echo var="FEAT_enable-alternate-editor-cmd"--></a> 4812<li><a href="h_config_alt_ed_now">FEATURE: <!--#echo var="FEAT_enable-alternate-editor-implicitly"--></a> 4813<li><a href="h_config_arrow_nav">FEATURE: <!--#echo var="FEAT_enable-arrow-navigation"--></a> 4814<li><a href="h_config_relaxed_arrow_nav">FEATURE: <!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></a> 4815<li><a href="h_config_compose_bg_post">FEATURE: <!--#echo var="FEAT_enable-background-sending"--></a> 4816<li><a href="h_config_enable_bounce">FEATURE: <!--#echo var="FEAT_enable-bounce-cmd"--></a> 4817<li><a href="h_config_cruise_mode">FEATURE: <!--#echo var="FEAT_enable-cruise-mode"--></a> 4818<li><a href="h_config_cruise_mode_delete">FEATURE: <!--#echo var="FEAT_enable-cruise-mode-delete"--></a> 4819<li><a href="h_config_compose_dsn">FEATURE: <!--#echo var="FEAT_enable-delivery-status-notification"--></a> 4820<li><a href="h_config_enable_dot_files">FEATURE: <!--#echo var="FEAT_enable-dot-files"--></a> 4821<li><a href="h_config_enable_lessthan_exit">FEATURE: <!--#echo var="FEAT_enable-exit-via-lessthan-command"--></a> 4822<li><a href="h_config_fast_recent">FEATURE: <!--#echo var="FEAT_enable-fast-recent-test"--></a> 4823<li><a href="h_config_enable_flag">FEATURE: <!--#echo var="FEAT_enable-flag-cmd"--></a> 4824<li><a href="h_config_flag_screen_default">FEATURE: <!--#echo var="FEAT_enable-flag-screen-implicitly"--></a> 4825<li><a href="h_config_flag_screen_kw_shortcut">FEATURE: <!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"--></a> 4826<li><a href="h_config_enable_full_hdr_and_text">FEATURE: <!--#echo var="FEAT_enable-full-header-and-text"--></a> 4827<li><a href="h_config_enable_full_hdr">FEATURE: <!--#echo var="FEAT_enable-full-header-cmd"--></a> 4828<li><a href="h_config_allow_goto">FEATURE: <!--#echo var="FEAT_enable-goto-in-file-browser"--></a> 4829<li><a href="h_config_enable_dot_folders">FEATURE: <!--#echo var="FEAT_enable-dot-folders"--></a> 4830<li><a href="h_config_enable_incoming">FEATURE: <!--#echo var="FEAT_enable-incoming-folders"--></a> 4831<li><a href="h_config_enable_incoming_checking">FEATURE: <!--#echo var="FEAT_enable-incoming-folders-checking"--></a> 4832<li><a href="h_config_enable_jump">FEATURE: <!--#echo var="FEAT_enable-jump-shortcut"--></a> 4833<li><a href="h_config_show_delay_cue">FEATURE: <!--#echo var="FEAT_enable-mail-check-cue"--></a> 4834<li><a href="h_config_mailcap_params">FEATURE: <!--#echo var="FEAT_enable-mailcap-param-substitution"--></a> 4835<li><a href="h_config_enable_mouse">FEATURE: <!--#echo var="FEAT_enable-mouse-in-xterm"--></a> 4836<li><a href="h_config_enable_view_addresses">FEATURE: <!--#echo var="FEAT_enable-msg-view-addresses"--></a> 4837<li><a href="h_config_enable_view_attach">FEATURE: <!--#echo var="FEAT_enable-msg-view-attachments"--></a> 4838<li><a href="h_external_loads_inline_images_only">FEATURE: <!--#echo var="FEAT_external-command-loads-inline-images-only"--></a> 4839<li><a href="h_config_enable_view_arrows">FEATURE: <!--#echo var="FEAT_enable-msg-view-forced-arrows"--></a> 4840<li><a href="h_config_enable_view_url">FEATURE: <!--#echo var="FEAT_enable-msg-view-urls"--></a> 4841<li><a href="h_config_enable_view_web_host">FEATURE: <!--#echo var="FEAT_enable-msg-view-web-hostnames"--></a> 4842<li><a href="h_config_enable_mulnewsrcs">FEATURE: <!--#echo var="FEAT_enable-multiple-newsrcs"--></a> 4843<li><a href="h_config_enable_xterm_newmail">FEATURE: <!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></a> 4844<li><a href="h_config_enable_newmail_short_text">FEATURE: <!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></a> 4845<li><a href="h_config_sub_lists">FEATURE: <!--#echo var="FEAT_enable-partial-match-lists"--></a> 4846<li><a href="h_config_enable_y_print">FEATURE: <!--#echo var="FEAT_enable-print-via-y-command"--></a> 4847<li><a href="h_config_prefix_editing">FEATURE: <!--#echo var="FEAT_enable-reply-indent-string-editing"--></a> 4848<li><a href="h_config_enable_search_and_repl">FEATURE: <!--#echo var="FEAT_enable-search-and-replace"--></a> 4849<li><a href="h_config_sigdashes">FEATURE: <!--#echo var="FEAT_enable-sigdashes"--></a> 4850<li><a href="h_config_new_thread_blank_subject">FEATURE: <!--#echo var="FEAT_new-thread-on-blank-subject"--></a> 4851<li><a href="h_config_can_suspend">FEATURE: <!--#echo var="FEAT_enable-suspend"--></a> 4852<li><a href="h_config_enable_tab_complete">FEATURE: <!--#echo var="FEAT_enable-tab-completion"--></a> 4853<li><a href="h_config_enable_take_export">FEATURE: <!--#echo var="FEAT_enable-take-export"--></a> 4854<li><a href="h_config_enable_role_take">FEATURE: <!--#echo var="FEAT_enable-rules-under-take"--></a> 4855<li><a href="h_config_tray_icon">FEATURE: <!--#echo var="FEAT_enable-tray-icon"--></a> 4856<li><a href="h_config_enable_pipe">FEATURE: <!--#echo var="FEAT_enable-unix-pipe-cmd"--></a> 4857<li><a href="h_config_verbose_post">FEATURE: <!--#echo var="FEAT_enable-verbose-smtp-posting"--></a> 4858<li><a href="h_config_expanded_addrbooks">FEATURE: <!--#echo var="FEAT_expanded-view-of-addressbooks"--></a> 4859<li><a href="h_config_expanded_distlists">FEATURE: <!--#echo var="FEAT_expanded-view-of-distribution-lists"--></a> 4860<li><a href="h_config_expanded_folders">FEATURE: <!--#echo var="FEAT_expanded-view-of-folders"--></a> 4861<li><a href="h_config_expose_hidden_config">FEATURE: <!--#echo var="FEAT_expose-hidden-config"--></a> 4862<li><a href="h_config_expunge_manually">FEATURE: <!--#echo var="FEAT_expunge-only-manually"--></a> 4863<li><a href="h_config_auto_expunge">FEATURE: <!--#echo var="FEAT_expunge-without-confirm"--></a> 4864<li><a href="h_config_full_auto_expunge">FEATURE: <!--#echo var="FEAT_expunge-without-confirm-everywhere"--></a> 4865<li><a href="h_config_no_fcc_attach">FEATURE: <!--#echo var="FEAT_fcc-without-attachments"--></a> 4866<li><a href="h_config_force_arrow">FEATURE: <!--#echo var="FEAT_force-arrow-cursor"--></a> 4867<li><a href="h_config_ignore_size">FEATURE: <!--#echo var="FEAT_ignore-size-changes"--></a> 4868<li><a href="h_config_forward_as_attachment">FEATURE: <!--#echo var="FEAT_forward-as-attachment"--></a> 4869<li><a href="h_config_preserve_field">FEATURE: <!--#echo var="FEAT_preserve-original-fields"--></a> 4870<li><a href="h_config_quell_empty_dirs">FEATURE: <!--#echo var="FEAT_quell-empty-directories"--></a> 4871<li><a href="h_config_hide_nntp_path">FEATURE: <!--#echo var="FEAT_hide-nntp-path"--></a> 4872<li><a href="h_config_attach_in_reply">FEATURE: <!--#echo var="FEAT_include-attachments-in-reply"--></a> 4873<li><a href="h_config_fcc_on_bounce">FEATURE: <!--#echo var="FEAT_fcc-on-bounce"--></a> 4874<li><a href="h_config_include_header">FEATURE: <!--#echo var="FEAT_include-header-in-reply"--></a> 4875<li><a href="h_config_auto_include_reply">FEATURE: <!--#echo var="FEAT_include-text-in-reply"--></a> 4876<li><a href="h_config_incoming_checking_total">FEATURE: <!--#echo var="FEAT_incoming-checking-includes-total"--></a> 4877<li><a href="h_config_incoming_checking_recent">FEATURE: <!--#echo var="FEAT_incoming-checking-uses-recent"--></a> 4878<li><a href="h_config_add_ldap">FEATURE: <!--#echo var="FEAT_ldap-result-to-addrbook-add"--></a> 4879<li><a href="h_config_maildrops_preserve_state">FEATURE: <!--#echo var="FEAT_maildrops-preserve-state"--></a> 4880<li><a href="h_config_mark_fcc_seen">FEATURE: <!--#echo var="FEAT_mark-fcc-seen"--></a> 4881<li><a href="h_config_mark_for_cc">FEATURE: <!--#echo var="FEAT_mark-for-cc"--></a> 4882<li><a href="h_config_mulnews_as_typed">FEATURE: <!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></a> 4883<li><a href="h_config_news_uses_recent">FEATURE: <!--#echo var="FEAT_news-approximates-new-status"--></a> 4884<li><a href="h_config_news_cross_deletes">FEATURE: <!--#echo var="FEAT_news-deletes-across-groups"--></a> 4885<li><a href="h_config_news_catchup">FEATURE: <!--#echo var="FEAT_news-offers-catchup-on-close"--></a> 4886<li><a href="h_config_post_wo_validation">FEATURE: <!--#echo var="FEAT_news-post-without-validation"--></a> 4887<li><a href="h_config_read_in_newsrc_order">FEATURE: <!--#echo var="FEAT_news-read-in-newsrc-order"--></a> 4888<li><a href="h_config_nntp_search_uses_overview">FEATURE: <!--#echo var="FEAT_nntp-search-uses-overview"--></a> 4889<li><a href="h_config_thread_sorts_by_arrival">FEATURE: <!--#echo var="FEAT_thread-sorts-by-arrival"--></a> 4890<li><a href="h_config_expunge_inbox">FEATURE: <!--#echo var="FEAT_offer-expunge-of-inbox"--></a> 4891<li><a href="h_config_expunge_stayopens">FEATURE: <!--#echo var="FEAT_offer-expunge-of-stayopen-folders"--></a> 4892<li><a href="h_config_pass_c1_control">FEATURE: <!--#echo var="FEAT_pass-c1-control-characters-as-is"--></a> 4893<li><a href="h_config_pass_control">FEATURE: <!--#echo var="FEAT_pass-control-characters-as-is"--></a> 4894<li><a href="h_config_predict_nntp_server">FEATURE: <!--#echo var="FEAT_predict-nntp-server"--></a> 4895<li><a href="h_config_prefer_plain_text">FEATURE: <!--#echo var="FEAT_prefer-plain-text"--></a> 4896<li><a href="h_config_preopen_stayopens">FEATURE: <!--#echo var="FEAT_preopen-stayopen-folders"--></a> 4897<li><a href="h_config_preserve_start_stop">FEATURE: <!--#echo var="FEAT_preserve-start-stop-characters"--></a> 4898<li><a href="h_config_quell_folder_internal_msg">FEATURE: <!--#echo var="FEAT_quell-folder-internal-msg"--></a> 4899<li><a href="h_config_quell_checks_comp">FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"--></a> 4900<li><a href="h_config_quell_checks_comp_inbox">FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-inbox"--></a> 4901<li><a href="h_config_quell_partial">FEATURE: <!--#echo var="FEAT_quell-partial-fetching"--></a> 4902<li><a href="h_config_quell_local_lookup">FEATURE: <!--#echo var="FEAT_quell-user-lookup-in-passwd-file"--></a> 4903<li><a href="h_config_ff_between_msgs">FEATURE: <!--#echo var="FEAT_print-formfeed-between-messages"--></a> 4904<li><a href="h_config_print_from">FEATURE: <!--#echo var="FEAT_print-includes-from-line"--></a> 4905<li><a href="h_config_print_index">FEATURE: <!--#echo var="FEAT_print-index-enabled"--></a> 4906<li><a href="h_config_custom_print">FEATURE: <!--#echo var="FEAT_print-offers-custom-cmd-prompt"--></a> 4907<li><a href="h_config_prune_uses_iso">FEATURE: <!--#echo var="FEAT_prune-uses-yyyy-mm"--></a> 4908<li><a href="h_config_quell_personal_name_prompt">FEATURE: <!--#echo var="FEAT_quell-personal-name-prompt"--></a> 4909<li><a href="h_config_quell_ssl_largeblocks">FEATURE: <!--#echo var="FEAT_quell-ssl-largeblocks"--></a> 4910<li><a href="h_config_quell_user_id_prompt">FEATURE: <!--#echo var="FEAT_quell-user-id-prompt"--></a> 4911<li><a href="h_config_quit_wo_confirm">FEATURE: <!--#echo var="FEAT_quit-without-confirm"--></a> 4912<li><a href="h_config_quote_replace_noflow">FEATURE: <!--#echo var="FEAT_quote-replace-nonflowed"--></a> 4913<li><a href="h_config_next_thrd_wo_confirm">FEATURE: <!--#echo var="FEAT_next-thread-without-confirm"--></a> 4914<li><a href="h_config_auto_reply_to">FEATURE: <!--#echo var="FEAT_reply-always-uses-reply-to"--></a> 4915<li><a href="h_config_inbox_no_confirm">FEATURE: <!--#echo var="FEAT_return-to-inbox-without-confirm"--></a> 4916<li><a href="h_config_save_aggregates">FEATURE: <!--#echo var="FEAT_save-aggregates-copy-sequence"--></a> 4917<li><a href="h_config_save_part_wo_confirm">FEATURE: <!--#echo var="FEAT_save-partial-msg-without-confirm"--></a> 4918<li><a href="h_config_save_advances">FEATURE: <!--#echo var="FEAT_save-will-advance"--></a> 4919<li><a href="h_config_save_wont_delete">FEATURE: <!--#echo var="FEAT_save-will-not-delete"--></a> 4920<li><a href="h_config_quote_all_froms">FEATURE: <!--#echo var="FEAT_save-will-quote-leading-froms"--></a> 4921<li><a href="h_config_scramble_message_id">FEATURE: <!--#echo var="FEAT_scramble-message-id"--></a> 4922<li><a href="h_config_select_wo_confirm">FEATURE: <!--#echo var="FEAT_select-without-confirm"--></a> 4923<li><a href="h_config_auto_fcc_only">FEATURE: <!--#echo var="FEAT_fcc-only-without-confirm"--></a> 4924<li><a href="h_config_send_wo_confirm">FEATURE: <!--#echo var="FEAT_send-without-confirm"--></a> 4925<li><a href="h_config_separate_fold_dir_view">FEATURE: <!--#echo var="FEAT_separate-folder-and-directory-entries"--></a> 4926<li><a href="h_config_show_cursor">FEATURE: <!--#echo var="FEAT_show-cursor"--></a> 4927<li><a href="h_config_textplain_int">FEATURE: <!--#echo var="FEAT_show-plain-text-internally"--></a> 4928<li><a href="h_config_select_in_bold">FEATURE: <!--#echo var="FEAT_show-selected-in-boldface"--></a> 4929<li><a href="h_config_show_sort">FEATURE: <!--#echo var="FEAT_show-sort"--></a> 4930<li><a href="h_config_single_list">FEATURE: <!--#echo var="FEAT_single-column-folder-list"--></a> 4931<li><a href="h_config_sig_at_bottom">FEATURE: <!--#echo var="FEAT_signature-at-bottom"--></a> 4932<li><a href="h_config_slash_coll_entire">FEATURE: <!--#echo var="FEAT_slash-collapses-entire-thread"--></a> 4933<li><a href="h_config_sort_fcc_alpha">FEATURE: <!--#echo var="FEAT_sort-default-fcc-alpha"--></a> 4934<li><a href="h_config_sort_save_alpha">FEATURE: <!--#echo var="FEAT_sort-default-save-alpha"--></a> 4935<li><a href="h_config_always_spell_check">FEATURE: <!--#echo var="FEAT_spell-check-before-sending"--></a> 4936<li><a href="h_config_winpos_in_config">FEATURE: <!--#echo var="FEAT_store-window-position-in-config"--></a> 4937<li><a href="h_config_strip_sigdashes">FEATURE: <!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></a> 4938<li><a href="h_config_strip_ws_before_send">FEATURE: <!--#echo var="FEAT_strip-whitespace-before-send"--></a> 4939<li><a href="h_config_quells_asterisks">FEATURE: <!--#echo var="FEAT_suppress-asterisks-in-password-prompt"--></a> 4940<li><a href="h_config_quell_attach_ext_warn">FEATURE: <!--#echo var="FEAT_quell-attachment-extension-warn"--></a> 4941<li><a href="h_config_quell_attach_extra_prompt">FEATURE: <!--#echo var="FEAT_quell-attachment-extra-prompt"--></a> 4942<li><a href="h_config_no_bezerk_zone">FEATURE: <!--#echo var="FEAT_quell-berkeley-format-timezone"--></a> 4943<li><a href="h_config_quell_charset_warning">FEATURE: <!--#echo var="FEAT_quell-charset-warning"--></a> 4944<li><a href="h_config_quell_content_id">FEATURE: <!--#echo var="FEAT_quell-content-id"--></a> 4945<li><a href="h_config_quell_post_prompt">FEATURE: <!--#echo var="FEAT_quell-extra-post-prompt"--></a> 4946<li><a href="h_config_quell_filtering_done_message">FEATURE: <!--#echo var="FEAT_quell-filtering-done-message"--></a> 4947<li><a href="h_config_quell_filtering_messages">FEATURE: <!--#echo var="FEAT_quell-filtering-messages"--></a> 4948<li><a href="h_config_quell_full_hdr_reset">FEATURE: <!--#echo var="FEAT_quell-full-header-auto-reset"--></a> 4949<li><a href="h_config_quell_imap_env">FEATURE: <!--#echo var="FEAT_quell-imap-envelope-update"--></a> 4950<li><a href="h_config_quell_lock_failure_warnings">FEATURE: <!--#echo var="FEAT_quell-lock-failure-warnings"--></a> 4951<li><a href="h_config_quell_domain_warn">FEATURE: <!--#echo var="FEAT_quell-maildomain-warning"--></a> 4952<li><a href="h_config_quell_news_env">FEATURE: <!--#echo var="FEAT_quell-news-envelope-update"--></a> 4953<li><a href="h_config_quell_host_after_url">FEATURE: <!--#echo var="FEAT_quell-server-after-link-in-html"--></a> 4954<li><a href="h_config_quell_beeps">FEATURE: <!--#echo var="FEAT_quell-status-message-beeping"--></a> 4955<li><a href="h_config_quell_tz_comment">FEATURE: <!--#echo var="FEAT_quell-timezone-comment-when-sending"--></a> 4956<li><a href="h_config_suppress_user_agent">FEATURE: <!--#echo var="FEAT_suppress-user-agent-when-sending"--></a> 4957<li><a href="h_config_tab_checks_recent">FEATURE: <!--#echo var="FEAT_tab-checks-recent"--></a> 4958<li><a href="h_config_tab_uses_unseen">FEATURE: <!--#echo var="FEAT_tab-uses-unseen-for-next-folder"--></a> 4959<li><a href="h_config_tab_new_only">FEATURE: <!--#echo var="FEAT_tab-visits-next-new-message-only"--></a> 4960<li><a href="h_config_termcap_wins">FEATURE: <!--#echo var="FEAT_termdef-takes-precedence"--></a> 4961<li><a href="h_config_color_thrd_import">FEATURE: <!--#echo var="FEAT_thread-index-shows-important-color"--></a> 4962<li><a href="h_config_alt_auth">FEATURE: <!--#echo var="FEAT_try-alternative-authentication-driver-first"--></a> 4963<li><a href="h_config_unsel_wont_advance">FEATURE: <!--#echo var="FEAT_unselect-will-not-advance"--></a> 4964<li><a href="h_config_use_current_dir">FEATURE: <!--#echo var="FEAT_use-current-dir"--></a> 4965<li><a href="h_config_use_fk">FEATURE: <!--#echo var="FEAT_use-function-keys"--></a> 4966<li><a href="h_config_use_reg_start_for_stayopen">FEATURE: <!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></a> 4967<li><a href="h_config_use_resentto">FEATURE: <!--#echo var="FEAT_use-resent-to-in-rules"--></a> 4968<li><a href="h_config_use_sender_not_x">FEATURE: <!--#echo var="FEAT_use-sender-not-x-sender"--></a> 4969<li><a href="h_config_suspend_spawns">FEATURE: <!--#echo var="FEAT_use-subshell-for-suspend"--></a> 4970<li><a href="h_config_use_system_translation">FEATURE: Use System Translation</a> 4971<li><a href="h_config_vertical_list">FEATURE: <!--#echo var="FEAT_vertical-folder-list"--></a> 4972<li><a href="h_config_warn_if_fcc_blank">FEATURE: <!--#echo var="FEAT_warn-if-blank-fcc"--></a> 4973<li><a href="h_config_warn_if_subj_blank">FEATURE: <!--#echo var="FEAT_warn-if-blank-subject"--></a> 4974<li><a href="h_config_warn_if_no_to_or_cc">FEATURE: <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></a> 4975<li><a href="h_mainhelp_filtering">Filtering</a> 4976<li><a href="h_finding_help">Finding more information and requesting help</a> 4977<li><a href="h_common_flag">Flag Command</a> 4978<li><a href="h_config_quell_flowed_text">Flowed Text</a> 4979<li><a href="h_mainhelp_folders">Folders</a> 4980<li><a href="h_what_are_collections">Folder Collections Explained</a> 4981<li><a href="h_common_folders">Folder List Command</a> 4982<li><a href="h_folder_fcc">Folder Select for Fcc Explained</a> 4983<li><a href="h_folder_save">Folder Select for Save Explained</a> 4984<li><a href="h_folder_server_syntax">Folder Server Name Syntax</a> 4985<li><a href="h_config_change_your_from">From Address, Changing</a> 4986<li><a href="main_menu_tx">GENERAL INFORMATION ON THE ALPINE MESSAGE SYSTEM</a> 4987<li><a href="h_pine_for_windows">GETTING HELP IN ALPINE</a> 4988<li><a href="h_common_goto">Goto Command</a> 4989<li><a href="h_common_hdrmode">HdrMode Command</a> 4990<li><a href="h_mainhelp_pinehelp">Help</a> 4991<li><a href="h_special_help_nav">Help Text Navigation Explained</a> 4992<li><a href="h_folder_maint">Help for Folder List</a> 4993<li><a href="h_valid_folder_names">IMAP</a> 4994<li><a href="h_ge_import">Import File Selection</a> 4995<li><a href="h_mainhelp_index">Index of Messages</a> 4996<li><a href="h_composer_ins_m">INSERT MESSAGE</a> 4997<li><a href="h_composer_ins">INSERT TEXT FILE</a> 4998<li><a href="h_address_format">INTERNET EMAIL ADDRESS FORMAT</a> 4999<li><a href="h_info_on_mbox">Information on mbox driver</a> 5000<li><a href="h_mainhelp_intro">Introduction</a> 5001<li><a href="h_main_journal">Journal Command</a> 5002<li><a href="h_common_jump">Jump Command</a> 5003<li><a href="h_compose_justify">Justify Command</a> 5004<li><a href="h_main_kblock">Keyboard Lock Command</a> 5005<li><a href="h_mainhelp_keywords">Keywords (or Flags, or Labels)</a> 5006<li><a href="h_mainhelp_ldap">LDAP</a> 5007<li><a href="h_config_ldap_opts_tls">LDAP FEATURE: Attempt-TLS-On-Connection</a> 5008<li><a href="h_config_ldap_opts_nosub">LDAP FEATURE: Disable-Ad-Hoc-Space-Substitution</a> 5009<li><a href="h_config_ldap_opts_rhs">LDAP FEATURE: Lookup-Addrbook-Contents</a> 5010<li><a href="h_config_ldap_opts_tlsmust">LDAP FEATURE: Require-TLS-On-Connection</a> 5011<li><a href="h_config_ldap_opts_ldaps">LDAP FEATURE: Require-LDAPS-On-Connection</a> 5012<li><a href="h_config_ldap_opts_ref">LDAP FEATURE: Save-Search-Criteria-Not-Result</a> 5013<li><a href="h_config_ldap_opts_impl">LDAP FEATURE: Use-Implicitly-From-Composer</a> 5014<li><a href="h_config_ldap_binddn">LDAP OPTION: Bind-DN</a> 5015<li><a href="h_config_ldap_cust">LDAP OPTION: Custom-Search-Filter</a> 5016<li><a href="h_config_ldap_email_attr">LDAP OPTION: EmailAttribute</a> 5017<li><a href="h_config_ldap_gn_attr">LDAP OPTION: GivennameAttribute</a> 5018<li><a href="h_config_ldap_server">LDAP OPTION: <!--#echo var="VAR_ldap-servers"--></a> 5019<li><a href="h_config_ldap_cn_attr">LDAP OPTION: NameAttribute</a> 5020<li><a href="h_config_ldap_nick">LDAP OPTION: Nickname</a> 5021<li><a href="h_config_ldap_port">LDAP OPTION: Port</a> 5022<li><a href="h_config_ldap_base">LDAP OPTION: Search-Base</a> 5023<li><a href="h_config_ldap_searchrules">LDAP OPTION: Search-Rule</a> 5024<li><a href="h_config_ldap_searchtypes">LDAP OPTION: Search-Type</a> 5025<li><a href="h_config_ldap_size">LDAP OPTION: Sizelimit</a> 5026<li><a href="h_config_ldap_sn_attr">LDAP OPTION: SurnameAttribute</a> 5027<li><a href="h_config_ldap_time">LDAP OPTION: Timelimit</a> 5028<li><a href="h_ldap_view">LDAP Response View Explained</a> 5029<li><a href="h_maildrop">Mail Drop: What is it?</a> 5030<li><a href="h_mainhelp_mainmenu">MAIN MENU</a> 5031<li><a href="h_mail_index">MESSAGE INDEX COMMANDS</a> 5032<li><a href="h_mail_view">MESSAGE TEXT SCREEN</a> 5033<li><a href="h_compose_markcutpaste">Mark, Cut and Paste Commands</a> 5034<li><a href="h_common_index">Message Index Command</a> 5035<li><a href="h_mainhelp_mouse">Mouse</a> 5036<li><a href="h_mainhelp_aggops">Multiple Message Operations</a> 5037<li><a href="new_user_greeting">NEW USER GREETING</a> 5038<li><a href="new_version_greeting">NEW VERSION GREETING</a> 5039<li><a href="h_mainhelp_readingnews">News Reading</a> 5040<li><a href="h_folder_subscribe">Newsgroup Subscribe Screen explained</a> 5041<li><a href="h_folder_postnews">Newsgroup selecting for Posting explained</a> 5042<li><a href="h_common_nextnew">NextNew Command</a> 5043<li><a href="h_abook_select_nick">Nickname Selection Explained</a> 5044<li><a href="h_mainhelp_readingnews">NNTP</a> 5045<li><a href="h_config_address_book">OPTION: <!--#echo var="VAR_address-book"--></a> 5046<li><a href="h_config_abook_formats">OPTION: <!--#echo var="VAR_addressbook-formats"--></a> 5047<li><a href="h_config_ab_sort_rule">OPTION: <!--#echo var="VAR_addrbook-sort-rule"--></a></a> 5048<li><a href="h_config_alt_addresses">OPTION: <!--#echo var="VAR_alt-addresses"--></a> 5049<li><a href="h_config_active_msg_interval">OPTION: <!--#echo var="VAR_busy-cue-rate"--></a> 5050<li><a href="h_config_color_style">OPTION: Color Style</a> 5051<li><a href="h_config_wordseps">OPTION: <!--#echo var="VAR_composer-word-separators"--></a> 5052<li><a href="h_config_composer_wrap_column">OPTION: <!--#echo var="VAR_composer-wrap-column"--></a> 5053<li><a href="h_config_index_color_style">OPTION: <!--#echo var="VAR_current-indexline-style"--></a> 5054<li><a href="h_config_cursor_style">OPTION: Cursor Style</a> 5055<li><a href="h_config_custom_hdrs">OPTION: <!--#echo var="VAR_customized-hdrs"--></a> 5056<li><a href="h_config_deadlets">OPTION: <!--#echo var="VAR_dead-letter-files"--></a> 5057<li><a href="h_config_comp_hdrs">OPTION: <!--#echo var="VAR_default-composer-hdrs"--></a> 5058<li><a href="h_config_default_fcc">OPTION: <!--#echo var="VAR_default-fcc"--></a> 5059<li><a href="h_config_def_save_folder">OPTION: <!--#echo var="VAR_default-saved-msg-folder"--></a> 5060<li><a href="h_config_disable_auths">OPTION: <!--#echo var="VAR_disable-these-authenticators"--></a> 5061<li><a href="h_config_encryption_range">OPTION: <!--#echo var="VAR_encryption-protocol-range"--></a> 5062<li><a href="h_config_disable_drivers">OPTION: <!--#echo var="VAR_disable-these-drivers"--></a> 5063<li><a href="h_config_char_set">OPTION: Display Character Set</a> 5064<li><a href="h_config_display_filters">OPTION: <!--#echo var="VAR_display-filters"--></a> 5065<li><a href="h_config_download_cmd">OPTION: <!--#echo var="VAR_download-command"--></a> 5066<li><a href="h_config_download_prefix">OPTION: <!--#echo var="VAR_download-command-prefix"--></a> 5067<li><a href="h_config_editor">OPTION: <!--#echo var="VAR_editor"--></a> 5068<li><a href="h_config_empty_hdr_msg">OPTION: <!--#echo var="VAR_empty-header-message"--></a> 5069<li><a href="h_config_fcc_rule">OPTION: <!--#echo var="VAR_fcc-name-rule"--></a> 5070<li><a href="h_config_file_dir">OPTION: File Directory</a> 5071<li><a href="h_config_folder_spec">OPTION: <!--#echo var="VAR_folder-collections"--></a> 5072<li><a href="h_config_reopen_rule">OPTION: <!--#echo var="VAR_folder-reopen-rule"--></a> 5073<li><a href="h_config_fld_sort_rule">OPTION: <!--#echo var="VAR_folder-sort-rule"--></a> 5074<li><a href="h_config_font_char_set">OPTION: Font Character Set</a> 5075<li><a href="h_config_font_name">OPTION: Font Name</a> 5076<li><a href="h_config_font_size">OPTION: Font Size</a> 5077<li><a href="h_config_font_style">OPTION: Font Style</a> 5078<li><a href="h_config_form_folder">OPTION: <!--#echo var="VAR_form-letter-folder"--></a> 5079<li><a href="h_config_glob_addrbook">OPTION: <!--#echo var="VAR_global-address-book"--></a> 5080<li><a href="h_config_goto_default">OPTION: <!--#echo var="VAR_goto-default-rule"--></a> 5081<li><a href="h_config_header_general_color">OPTION: Header General Color</a> 5082<li><a href="h_config_image_viewer">OPTION: <!--#echo var="VAR_image-viewer"--></a> 5083<li><a href="h_config_inbox_path">OPTION: <!--#echo var="VAR_inbox-path"--></a> 5084<li><a href="h_config_archived_folders">OPTION: <!--#echo var="VAR_incoming-archive-folders"--></a> 5085<li><a href="h_config_incoming_interv">OPTION: <!--#echo var="VAR_incoming-check-interval"--></a> 5086<li><a href="h_config_incoming_second_interv">OPTION: <!--#echo var="VAR_incoming-check-interval-secondary"--></a> 5087<li><a href="h_config_incoming_list">OPTION: <!--#echo var="VAR_incoming-check-list"--></a> 5088<li><a href="h_config_incoming_timeo">OPTION: <!--#echo var="VAR_incoming-check-timeout"--></a> 5089<li><a href="h_config_incoming_folders">OPTION: <!--#echo var="VAR_incoming-folders"--></a> 5090<li><a href="h_config_inc_startup">OPTION: <!--#echo var="VAR_incoming-startup-rule"--></a> 5091<li><a href="h_config_incunseen_color">OPTION: Incoming Unseen Color</a> 5092<li><a href="h_config_index_arrow_color">OPTION: Index Arrow Color</a> 5093<li><a href="h_config_index_color">OPTION: Index Colors</a> 5094<li><a href="h_config_index_format">OPTION: <!--#echo var="VAR_index-format"--></a> 5095<li><a href="h_config_index_from_color">OPTION: Index From Color</a> 5096<li><a href="h_config_index_opening_color">OPTION: Index Opening Color</a> 5097<li><a href="h_config_index_pri_color">OPTION: Index Priority Symbol Colors</a> 5098<li><a href="h_config_index_subject_color">OPTION: Index Subject Color</a> 5099<li><a href="h_config_init_cmd_list">OPTION: <!--#echo var="VAR_initial-keystroke-list"--></a> 5100<li><a href="h_config_key_char_set">OPTION: Keyboard Character Set</a> 5101<li><a href="h_config_keylabel_color">OPTION: KeyLabel Color</a> 5102<li><a href="h_config_keyname_color">OPTION: KeyName Color</a> 5103<li><a href="h_config_keywords">OPTION: <!--#echo var="VAR_keywords"--></a> 5104<li><a href="h_config_kw_color">OPTION: Keyword Colors</a> 5105<li><a href="h_config_kw_braces">OPTION: <!--#echo var="VAR_keyword-surrounding-chars"--></a> 5106<li><a href="h_config_prune_date">OPTION: <!--#echo var="VAR_last-time-prune-questioned"--></a> 5107<li><a href="h_config_last_vers">OPTION: <!--#echo var="VAR_last-version-used"--></a> 5108<li><a href="h_config_literal_sig">OPTION: <!--#echo var="VAR_literal-signature"--></a> 5109<li><a href="h_config_mailcheck">OPTION: <!--#echo var="VAR_mail-check-interval"--></a> 5110<li><a href="h_config_mailchecknoncurr">OPTION: <!--#echo var="VAR_mail-check-interval-noncurrent"--></a> 5111<li><a href="h_config_mailcap_path">OPTION: <!--#echo var="VAR_mailcap-search-path"--></a> 5112<li><a href="h_config_maildropcheck">OPTION: <!--#echo var="VAR_maildrop-check-minimum"--></a> 5113<li><a href="h_config_maxremstream">OPTION: <!--#echo var="VAR_max-remote-connections"--></a> 5114<li><a href="h_config_metamsg_color">OPTION: Meta-Message Color</a> 5115<li><a href="h_config_mimetype_path">OPTION: <!--#echo var="VAR_mimetype-search-path"--></a> 5116<li><a href="h_config_new_ver_quell">OPTION: <!--#echo var="VAR_new-version-threshold"--></a> 5117<li><a href="h_config_fifopath">OPTION: NewMail FIFO Path</a> 5118<li><a href="h_config_newmailwidth">OPTION: <!--#echo var="VAR_newmail-window-width"--></a> 5119<li><a href="h_config_news_active">OPTION: <!--#echo var="VAR_news-active-file-path"--></a> 5120<li><a href="h_config_news_spec">OPTION: <!--#echo var="VAR_news-collections"--></a> 5121<li><a href="h_config_news_spool">OPTION: <!--#echo var="VAR_news-spool-directory"--></a> 5122<li><a href="h_config_newsrc_path">OPTION: <!--#echo var="VAR_newsrc-path"--></a> 5123<li><a href="h_config_nntprange">OPTION: <!--#echo var="VAR_nntp-range"--></a> 5124<li><a href="h_config_nntp_server">OPTION: <!--#echo var="VAR_nntp-server"--></HEAD></a> 5125<li><a href="h_config_normal_color">OPTION: Normal Color</a> 5126<li><a href="h_config_opening_sep">OPTION: <!--#echo var="VAR_opening-text-separator-chars"--></a> 5127<li><a href="h_config_oper_dir">OPTION: <!--#echo var="VAR_operating-dir"--></a> 5128<li><a href="h_config_pat_old">OPTION: Patterns</a> 5129<li><a href="h_config_pat_filts">OPTION: <!--#echo var="VAR_patterns-filters2"--></a> 5130<li><a href="h_config_pat_other">OPTION: <!--#echo var="VAR_patterns-other"--></a> 5131<li><a href="h_config_pat_roles">OPTION: <!--#echo var="VAR_patterns-roles"--></a> 5132<li><a href="h_config_pat_scores">OPTION: <!--#echo var="VAR_patterns-scores2"--></a> 5133<li><a href="h_config_pers_name">OPTION: <!--#echo var="VAR_personal-name"--></a> 5134<li><a href="h_config_print_cat">OPTION: <!--#echo var="VAR_personal-print-category"--></a> 5135<li><a href="h_config_print_command">OPTION: <!--#echo var="VAR_personal-print-command"--></a> 5136<li><a href="h_config_post_char_set">OPTION: <!--#echo var="VAR_posting-character-set"--></a> 5137<li><a href="h_config_postponed_folder">OPTION: <!--#echo var="VAR_postponed-folder"--></a> 5138<li><a href="h_config_print_font_char_set">OPTION: Print-Font-Char-Set</a> 5139<li><a href="h_config_print_font_name">OPTION: Print-Font-Name</a> 5140<li><a href="h_config_print_font_size">OPTION: Print-Font-Size</a> 5141<li><a href="h_config_print_font_style">OPTION: Print-Font-Style</a> 5142<li><a href="h_config_printer">OPTION: Printer</a> 5143<li><a href="h_config_prompt_color">OPTION: Prompt Color</a> 5144<li><a href="h_config_pruned_folders">OPTION: <!--#echo var="VAR_pruned-folders"--></a> 5145<li><a href="h_config_pruning_rule">OPTION: <!--#echo var="VAR_pruning-rule"--></a> 5146<li><a href="h_config_quote_color">OPTION: Quote Colors</a> 5147<li><a href="h_config_quote_replace_string">OPTION: <!--#echo var="VAR_quote-replace-string"--></a> 5148<li><a href="h_config_quote_suppression">OPTION: <!--#echo var="VAR_quote-suppression-threshold"--></a> 5149<li><a href="h_config_read_message_folder">OPTION: <!--#echo var="VAR_read-message-folder"--></a> 5150<li><a href="h_config_remote_abook_history">OPTION: <!--#echo var="VAR_remote-abook-history"--></a> 5151<li><a href="h_config_abook_metafile">OPTION: <!--#echo var="VAR_remote-abook-metafile"--></a> 5152<li><a href="h_config_remote_abook_validity">OPTION: <!--#echo var="VAR_remote-abook-validity"--></a> 5153<li><a href="h_config_reply_indent_string">OPTION: <!--#echo var="VAR_reply-indent-string"--></a> 5154<li><a href="h_config_reply_intro">OPTION: <!--#echo var="VAR_reply-leadin"--></a> 5155<li><a href="h_config_reverse_color">OPTION: Reverse Color</a> 5156<li><a href="h_config_rshcmd">OPTION: <!--#echo var="VAR_rsh-command"--></a> 5157<li><a href="h_config_rsh_open_timeo">OPTION: <!--#echo var="VAR_rsh-open-timeout"--></a> 5158<li><a href="h_config_rshpath">OPTION: <!--#echo var="VAR_rsh-path"--></a> 5159<li><a href="h_config_saved_msg_name_rule">OPTION: <!--#echo var="VAR_saved-msg-name-rule"--></a> 5160<li><a href="h_config_scroll_margin">OPTION: <!--#echo var="VAR_scroll-margin"--></a> 5161<li><a href="h_config_slctbl_color">OPTION: Selectable Item Color</a> 5162<li><a href="h_config_sending_filter">OPTION: <!--#echo var="VAR_sending-filters"--></a> 5163<li><a href="h_config_sendmail_path">OPTION: <!--#echo var="VAR_sendmail-path"--></a> 5164<li><a href="h_config_signature_color">OPTION: Signature Color</a> 5165<li><a href="h_config_signature_file">OPTION: <!--#echo var="VAR_signature-file"--></a> 5166<li><a href="h_config_smtp_server">OPTION: <!--#echo var="VAR_smtp-server"--></a> 5167<li><a href="h_config_sort_key">OPTION: <!--#echo var="VAR_sort-key"--></a> 5168<li><a href="h_config_speller">OPTION: <!--#echo var="VAR_speller"--></a> 5169<li><a href="h_config_aspell_dictionary">OPTION: <!--#echo var="VAR_aspell-dictionary-list"--></a> 5170<li><a href="h_config_sshcmd">OPTION: <!--#echo var="VAR_ssh-command"--></a> 5171<li><a href="h_config_ssh_open_timeo">OPTION: <!--#echo var="VAR_ssh-open-timeout"--></a> 5172<li><a href="h_config_sshpath">OPTION: <!--#echo var="VAR_ssh-path"--></a> 5173<li><a href="h_config_status_color">OPTION: Status Color</a> 5174<li><a href="h_config_status_msg_delay">OPTION: <!--#echo var="VAR_status-message-delay"--></a> 5175<li><a href="h_config_permlocked">OPTION: <!--#echo var="VAR_stay-open-folders"--></a> 5176<li><a href="h_config_tcp_open_timeo">OPTION: <!--#echo var="VAR_tcp-open-timeout"--></a> 5177<li><a href="h_config_tcp_query_timeo">OPTION: <!--#echo var="VAR_tcp-query-timeout"--></a> 5178<li><a href="h_config_quit_query_timeo">OPTION: <!--#echo var="VAR_close-connection-timeout"--></a> 5179<li><a href="h_config_tcp_readwarn_timeo">OPTION: <!--#echo var="VAR_tcp-read-warning-timeout"--></a> 5180<li><a href="h_config_tcp_writewarn_timeo">OPTION: <!--#echo var="VAR_tcp-write-warning-timeout"--></a> 5181<li><a href="h_config_thread_disp_style">OPTION: <!--#echo var="VAR_threading-display-style"--></a> 5182<li><a href="h_config_thread_exp_char">OPTION: <!--#echo var="VAR_threading-expanded-character"--></a> 5183<li><a href="h_config_thread_index_style">OPTION: <!--#echo var="VAR_threading-index-style"--></a> 5184<li><a href="h_config_thread_indicator_char">OPTION: <!--#echo var="VAR_threading-indicator-character"--></a> 5185<li><a href="h_config_thread_lastreply_char">OPTION: <!--#echo var="VAR_threading-lastreply-character"--></a> 5186<li><a href="h_config_title_color">OPTION: Title Color</a> 5187<li><a href="h_config_titleclosed_color">OPTION: Title Closed Color</a> 5188<li><a href="h_config_titlebar_color_style">OPTION: <!--#echo var="VAR_titlebar-color-style"--></a> 5189<li><a href="h_config_unk_char_set">OPTION: <!--#echo var="VAR_unknown-character-set"--></a> 5190<li><a href="h_config_upload_cmd">OPTION: <!--#echo var="VAR_upload-command"--></a> 5191<li><a href="h_config_upload_prefix">OPTION: <!--#echo var="VAR_upload-command-prefix"--></a> 5192<li><a href="h_config_browser">OPTION: <!--#echo var="VAR_url-viewers"--></a> 5193<li><a href="h_config_history">OPTION: <!--#echo var="VAR_default-directories"--></a> 5194<li><a href="h_config_domain_name">OPTION: <!--#echo var="VAR_use-only-domain-name"--></a> 5195<li><a href="h_config_user_dom">OPTION: <!--#echo var="VAR_user-domain"--></a> 5196<li><a href="h_config_user_id">OPTION: <!--#echo var="VAR_user-id"--></a> 5197<li><a href="h_config_user_input_timeo">OPTION: <!--#echo var="VAR_user-input-timeout"--></a> 5198<li><a href="h_config_viewer_headers">OPTION: <!--#echo var="VAR_viewer-hdrs"--></a> 5199<li><a href="h_config_customhdr_pattern">OPTION: Viewer Header Color Pattern</a> 5200<li><a href="h_config_customhdr_color">OPTION: <!--#echo var="VAR_viewer-hdr-colors"--></a> 5201<li><a href="h_config_viewer_margin_left">OPTION: <!--#echo var="VAR_viewer-margin-left"--></a> 5202<li><a href="h_config_viewer_margin_right">OPTION: <!--#echo var="VAR_viewer-margin-right"--></a> 5203<li><a href="h_config_viewer_overlap">OPTION: <!--#echo var="VAR_viewer-overlap"--></a> 5204<li><a href="h_config_window_position">OPTION: Window-Position</a> 5205<li><a href="h_mainhelp_patterns">Patterns</a> 5206<li><a href="h_config_role_abookfrom">PATTERNS: Address in Address Book</a> 5207<li><a href="h_config_role_age">PATTERNS: Age Interval</a> 5208<li><a href="h_config_role_alltextpat">PATTERNS: AllText Pattern</a> 5209<li><a href="h_config_role_bom">PATTERNS: Beginning of Month</a> 5210<li><a href="h_config_role_boy">PATTERNS: Beginning of Year</a> 5211<li><a href="h_config_role_bodytextpat">PATTERNS: BodyText Pattern</a> 5212<li><a href="h_config_role_cat_cmd">PATTERNS: Categorizer Command</a> 5213<li><a href="h_config_role_cat_cmd_example">PATTERNS: Categorizer Command Example</a> 5214<li><a href="h_config_role_ccpat">PATTERNS: Cc Pattern</a> 5215<li><a href="h_config_role_cat_limit">PATTERNS: Character Limit</a> 5216<li><a href="h_config_role_charsetpat">PATTERNS: Character Set Pattern</a> 5217<li><a href="h_config_role_comment">PATTERNS: Comment</a> 5218<li><a href="h_config_role_fldr_type">PATTERNS: Current Folder Type</a> 5219<li><a href="h_config_role_cat_status">PATTERNS: Exit Status Interval</a> 5220<li><a href="h_config_role_arbpat">PATTERNS: Extra Headers Pattern</a> 5221<li><a href="h_config_role_frompat">PATTERNS: From Pattern</a> 5222<li><a href="h_config_role_keywordpat">PATTERNS: Keyword Pattern</a> 5223<li><a href="h_config_role_stat_ans">PATTERNS: Message Answered Status</a> 5224<li><a href="h_config_role_stat_del">PATTERNS: Message Deleted Status</a> 5225<li><a href="h_config_role_stat_imp">PATTERNS: Message Important Status</a> 5226<li><a href="h_config_role_stat_new">PATTERNS: Message New Status</a> 5227<li><a href="h_config_role_stat_recent">PATTERNS: Message Recent Status</a> 5228<li><a href="h_config_role_newspat">PATTERNS: News Pattern</a> 5229<li><a href="h_config_role_nick">PATTERNS: Nickname</a> 5230<li><a href="h_config_role_particpat">PATTERNS: Participant Pattern</a> 5231<li><a href="h_config_role_stat_8bitsubj">PATTERNS: Raw 8-bit in Subject</a> 5232<li><a href="h_config_role_recippat">PATTERNS: Recipient Pattern</a> 5233<li><a href="h_config_role_scorei">PATTERNS: Score Interval</a> 5234<li><a href="h_config_role_senderpat">PATTERNS: Sender Pattern</a> 5235<li><a href="h_config_role_size">PATTERNS: Size Interval</a> 5236<li><a href="h_config_role_subjpat">PATTERNS: Subject Pattern</a> 5237<li><a href="h_config_role_topat">PATTERNS: To Pattern</a> 5238<li><a href="h_config_filt_opts_nonterm">PATTERNS FEATURE: Dont-Stop-Even-if-Rule-Matches</a> 5239<li><a href="h_config_filt_opts_notdel">PATTERNS FEATURE: Move-Only-if-Not-Deleted</a> 5240<li><a href="h_config_filt_opts_sentdate">PATTERNS FEATURE: Use-Date-Header-For-Age</a> 5241<li><a href="h_config_filt_rule_type">PATTERNS FILTER ACTION: Filter Action</a> 5242<li><a href="h_config_filter_kw_clr">PATTERNS FILTER ACTION: Clear These Keywords</a> 5243<li><a href="h_config_filt_stat_ans">PATTERNS FILTER ACTION: Set Answered Status</a> 5244<li><a href="h_config_filt_stat_del">PATTERNS FILTER ACTION: Set Deleted Status</a> 5245<li><a href="h_config_filt_stat_imp">PATTERNS FILTER ACTION: Set Important Status</a> 5246<li><a href="h_config_filt_stat_new">PATTERNS FILTER ACTION: Set New Status</a> 5247<li><a href="h_config_filter_kw_set">PATTERNS FILTER ACTION: Set These Keywords</a> 5248<li><a href="h_config_incol">PATTERNS INDEXCOLOR ACTION: Index Line Color</a> 5249<li><a href="h_config_set_index_format">PATTERNS OTHER ACTION: Set Index Format</a> 5250<li><a href="h_config_perfolder_sort">PATTERNS OTHER ACTION: Set Sort Order</a> 5251<li><a href="h_config_other_startup">PATTERNS OTHER ACTION: Set Startup Rule</a> 5252<li><a href="h_config_role_inick">PATTERNS ROLE ACTION: Initialize Values From Role</a> 5253<li><a href="h_config_role_setfcc">PATTERNS ROLE ACTION: Set Fcc</a> 5254<li><a href="h_config_role_setfrom">PATTERNS ROLE ACTION: Set From</a> 5255<li><a href="h_config_role_setlitsig">PATTERNS ROLE ACTION: Set Literal Signature</a> 5256<li><a href="h_config_role_setotherhdr">PATTERNS ROLE ACTION: Set Other Headers</a> 5257<li><a href="h_config_role_setreplyto">PATTERNS ROLE ACTION: Set Reply-To</a> 5258<li><a href="h_config_role_setsig">PATTERNS ROLE ACTION: Set Signature</a> 5259<li><a href="h_config_role_settempl">PATTERNS ROLE ACTION: Set Template</a> 5260<li><a href="h_config_role_usenntp">PATTERNS ROLE ACTION: Use NNTP Server</a> 5261<li><a href="h_config_role_usesmtp">PATTERNS ROLE ACTION: Use SMTP Server</a> 5262<li><a href="h_config_role_scoreval">PATTERNS SCORE ACTION: Score Value</a> 5263<li><a href="h_config_role_scorehdrtok">PATTERNS SCORE ACTION: Score Value From Header</a> 5264<li><a href="h_config_role_composeuse">PATTERNS USE: Compose Use</a> 5265<li><a href="h_config_role_forwarduse">PATTERNS USE: Forward Use</a> 5266<li><a href="h_config_role_replyuse">PATTERNS USE: Reply Use</a> 5267<li><a href="h_pipe_command">Pipe Command SubOptions</a> 5268<li><a href="h_common_pipe">Pipe Command</a> 5269<li><a href="h_valid_folder_names">POP</a> 5270<li><a href="h_common_postpone">Postpone Command</a> 5271<li><a href="h_common_print">Print Command</a> 5272<li><a href="h_mainhelp_readingnews">Reading News</a> 5273<li><a href="h_news">RELEASE NOTES for Alpine</a> 5274<li><a href="h_mainhelp_roles">Roles</a> 5275<li><a href="h_role_select">ROLES SCREEN</a> 5276<li><a href="h_compose_readfile">Read File Command</a> 5277<li><a href="h_mainhelp_reading">Reading Messages</a> 5278<li><a href="h_main_release_notes">Release Notes Command</a> 5279<li><a href="h_common_reply">Reply and Forward Commands</a> 5280<li><a href="h_compose_richhdr">Rich Header Command</a> 5281<li><a href="h_common_role">Role Command</a> 5282<li><a href="h_mainhelp_smime">S/MIME</a> 5283<li><a href="h_index_cmd_select">Searching for Messages</a> 5284<li><a href="h_address_display">SEARCH RESULTS INDEX</a> 5285<li><a href="h_address_select">SEARCH RESULTS INDEX</a> 5286<li><a href="h_simple_index">SELECT POSTPONED MESSAGE</a> 5287<li><a href="h_abook_config">SETUP ADDRESS BOOKS SCREEN</a> 5288<li><a href="h_collection_maint">SETUP COLLECTION LIST screen</a> 5289<li><a href="h_color_setup">SETUP COLOR COMMANDS</a> 5290<li><a href="h_direct_config">SETUP LDAP DIRECTORY SERVERS SCREEN</a> 5291<li><a href="h_rules_roles">SETUP ROLES SCREEN</a> 5292<li><a href="h_rules_incols">SETUP INDEX COLORS SCREEN</a> 5293<li><a href="h_rules_filter">SETUP FILTERING SCREEN</a> 5294<li><a href="h_rules_score">SETUP SCORING SCREEN</a> 5295<li><a href="h_common_save">Save and Export Commands</a> 5296<li><a href="h_mainhelp_securing">Securing Your Alpine Session</a> 5297<li><a href="h_index_cmd_select">Selecting: Select and WhereIs/Select</a> 5298<li><a href="h_compose_send">Send Command</a> 5299<li><a href="h_folder_server_syntax">Server Name Syntax</a> 5300<li><a href="h_main_setup">Setup Command</a> 5301<li><a href="X-Alpine-Config:">Show Supported Options in this Alpine</a> 5302<li><a href="h_composer_sigedit">Signature Editor Commands Explained</a> 5303<li><a href="h_simple_text_view">Simple Text View Screen Explained</a> 5304<li><a href="h_mainhelp_smime">S/MIME</a> 5305<li><a href="h_config_smime_dont_do_smime">S/MIME FEATURE: <!--#echo var="FEAT_smime-dont-do-smime"--></a> 5306<li><a href="h_config_smime_encrypt_by_default">S/MIME FEATURE: <!--#echo var="FEAT_smime-encrypt-by-default"--></a> 5307<li><a href="h_config_smime_remember_passphrase">S/MIME FEATURE: <!--#echo var="FEAT_smime-remember-passphrase"--></a> 5308<li><a href="h_config_smime_sign_by_default">S/MIME FEATURE: <!--#echo var="FEAT_smime-sign-by-default"--></a> 5309<li><a href="h_config_smime_use_cert_store">S/MIME FEATURE: <!--#echo var="FEAT_smime-use-store-only"--></a> 5310<li><a href="h_config_smime_pubcerts_in_keychain">S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></a> 5311<li><a href="h_config_smime_cacertcon">S/MIME OPTION: <!--#echo var="VAR_smime-cacert-container"--></a> 5312<li><a href="h_config_smime_cacertdir">S/MIME OPTION: <!--#echo var="VAR_smime-cacert-directory"--></a> 5313<li><a href="h_config_smime_privkeycon">S/MIME OPTION: <!--#echo var="VAR_smime-private-key-container"--></a> 5314<li><a href="h_config_smime_privkeydir">S/MIME OPTION: <!--#echo var="VAR_smime-private-key-directory"--></a> 5315<li><a href="h_config_smime_pubcertcon">S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-container"--></a> 5316<li><a href="h_config_smime_pubcertdir">S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-directory"--></a> 5317<li><a href="h_config_smime_transfer_cacert_to_con">S/MIME: Transfer CA Certs to Container</a> 5318<li><a href="h_config_smime_transfer_cacert_to_dir">S/MIME: Transfer CA Certs to Directory</a> 5319<li><a href="h_config_smime_transfer_priv_to_con">S/MIME: Transfer Private Keys to Container</a> 5320<li><a href="h_config_smime_transfer_priv_to_dir">S/MIME: Transfer Private Keys to Directory</a> 5321<li><a href="h_config_smime_transfer_pub_to_con">S/MIME: Transfer Public Certs to Container</a> 5322<li><a href="h_config_smime_transfer_pub_to_dir">S/MIME: Transfer Public Certs to Directory</a> 5323<li><a href="h_config_smime_public_certificates">S/MIME: Manage Public Certificates</a> 5324<li><a href="h_config_smime_private_keys">S/MIME: Manage Private Keys</a> 5325<li><a href="h_config_smime_certificate_authorities">S/MIME: Manage Certificate Authorities</a> 5326<li><a href="h_index_cmd_sort">Sort Command</a> 5327<li><a href="h_compose_spell">Spell Check Command</a> 5328<li><a href="h_common_suspend">Suspend Command</a> 5329<li><a href="h_compose_addrcomplete">THE MESSAGE COMPOSER'S ADDRESS COMPLETION</a> 5330<li><a href="h_composer_attachment">THE MESSAGE COMPOSER'S ATTCHMNT FIELD</a> 5331<li><a href="h_composer_bcc">THE MESSAGE COMPOSER'S BCC FIELD</a> 5332<li><a href="h_composer_cc">THE MESSAGE COMPOSER'S CC FIELD</a> 5333<li><a href="h_composer_from">THE MESSAGE COMPOSER'S FROM FIELD</a> 5334<li><a href="h_composer_lcc">THE MESSAGE COMPOSER'S LCC FIELD</a> 5335<li><a href="h_composer_news">THE MESSAGE COMPOSER'S NEWSGRPS LINE</a> 5336<li><a href="h_composer_reply_to">THE MESSAGE COMPOSER'S REPLY-TO FIELD</a> 5337<li><a href="h_composer_to">THE MESSAGE COMPOSER'S TO FIELD</a> 5338<li><a href="h_abook_opened">THE ALPINE ADDRESS BOOK</a> 5339<li><a href="h_abook_select_nicks_take">Take Address Nickname Selection Explained</a> 5340<li><a href="h_takeaddr_screen">Take Address Screen Explained</a> 5341<li><a href="h_common_take">TakeAddr Command</a> 5342<li><a href="h_mainhelp_status">Titlebar Line</a> 5343<li><a href="h_index_tokens">Tokens for Index and Replying</a> 5344<li><a href="h_config_usenone_color">Use None Color</a> 5345<li><a href="h_config_usenormal_color">Use Normal Color</a> 5346<li><a href="h_config_usetransparent_color">Use Transparent Color</a> 5347<li><a href="h_whatis_vcard">VCARD EXPLAINED</a> 5348<li><a href="h_view_cmd_hilite">View Hilite and Next item/Previous item</a> 5349<li><a href="h_view_cmd_viewattch">ViewAttch Command</a> 5350<li><a href="h_index_cmd_whereis">WhereIs Command</a> 5351<li><a href="h_view_cmd_whereis">WhereIs Command</a> 5352<li><a href="h_index_cmd_zoom">ZoomMode Command</a> 5353<li><a href="h_config_browser_xterm"><!--#echo var="VAR_url-viewers"--> and X windows applications</a> 5354</UL> 5355 5356<P> 5357<End of Help Index> 5358</BODY> 5359</HTML> 5360 5361 5362============== h_config_remote_config ============= 5363<HTML> 5364<HEAD> 5365<TITLE>Remote Configuration</TITLE> 5366</HEAD> 5367<BODY> 5368<H1>Remote Configuration</H1> 5369 5370You may use the command line argument "-p pinerc" to tell 5371Alpine to use a non-default configuration file. 5372There are two types of storage for configuration information. 5373<EM>Local</EM> configuration files are used by default. 5374These are just regular files on the UNIX system or on the PC. 5375The file "<CODE>.pinerc</CODE>" is the default for Unix Alpine and the 5376file "<CODE>PINERC</CODE>" is the default for PC-Alpine. 5377<EM>Remote</EM> configuration folders are stored on an IMAP server. 5378The advantage of using a remote configuration is that the same information 5379may be accessed from multiple platforms. 5380For example, if you use one computer at work and another at home, the same 5381configuration could be used from both places. 5382A configuration change from one place would be seen in both places. 5383To use a remote configuration you simply give a 5384<A HREF="h_valid_folder_names">remote folder name</A> 5385as the argument to the "-p" command line option. 5386The command line might look something like: 5387<P> 5388<CENTER><SAMP>pine -p {my.imap.server}remote_pinerc</SAMP></CENTER> 5389<P> 5390If there are special characters in the command shell you use, you may need to 5391quote the last argument (to protect the curly braces from the shell). 5392The command might look like: 5393<P> 5394<CENTER><SAMP>pine -p "{my.imap.server}remote_pinerc"</SAMP></CENTER> 5395<P> 5396You should choose a folder name for a folder that does not yet exist. 5397It will be created containing an empty configuration. 5398Do not use a folder that you wish to store regular mail messages in. 5399<P> 5400The Setup/RemoteConfigSetup command will help you convert from a local 5401configuration to a remote configuration. 5402It will create a remote configuration for you and copy your current local 5403configuration to it. 5404It will also help you convert local address books into remote address books 5405and local signature files into literal signatures contained in the 5406remote configuration file. 5407<P> 5408If the Setup/RemoteConfigSetup command doesn't do what you want, you 5409may copy a local pinerc file to a remote configuration folder by hand 5410by using the command line option "-copy_pinerc". 5411<P> 5412Another command line option, which is somewhat related to remote 5413configuration, is the option "-x exceptions_config". 5414The configuration settings in the exceptions configuration override 5415your default settings. 5416It may be useful to store the default configuration (the -p argument) remotely 5417and to have the exceptions configuration stored in a local file. 5418You might put generic configuration information in the remote configuration 5419and platform-specific configuration on each platform in the exceptions 5420configuration. 5421The arguments to the "-p" and "-x" options 5422can be either remote folders or local files. 5423<P> 5424There is another command line argument that works only with PC-Alpine and 5425which may prove useful when using a remote configuration. 5426The option "-aux local_directory" allows you to tell PC-Alpine where 5427to store your local auxiliary files. 5428This only has an effect if your configuration file is remote. 5429Some examples of auxiliary files are debug files, address book files, and 5430signature files. 5431<P> 5432<End of help on this topic> 5433</BODY> 5434</HTML> 5435============== h_config_exceptions ============= 5436<HTML> 5437<HEAD> 5438<TITLE>Generic and Exceptional Configuration</TITLE> 5439</HEAD> 5440<BODY> 5441<H1>Generic and Exceptional Configuration</H1> 5442 5443If you use Alpine from more than one platform it may be convenient 5444to split your configuration information into two pieces, a generic piece 5445and exceptions that apply to a particular platform. 5446For example, suppose you use Alpine from home and from work. 5447Most of your configuration settings are probably the 5448same in both locations, so those settings belong in the generic settings 5449configuration. 5450However, you may use a different SMTP server and INBOX 5451from home than you do from work. 5452The 5453<A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A> 5454and 5455<A HREF="h_config_inbox_path">"<!--#echo var="VAR_inbox-path"-->"</A> 5456options could be 5457part of your exceptional configuration so that they could be different in the 5458two places. 5459<P> 5460The command line option "-x exceptions_config" 5461may be used to split your configuration into generic and exceptional pieces. 5462"Exceptions_config" may be either local or remote. 5463The regular Alpine configuration file will contain the generic data, and 5464"exceptions_config" will contain the exceptional data. 5465<P> 5466For Unix Alpine, if you don't have a "-x" command line option, 5467Alpine will look for the file "<CODE>.pinercex</CODE>" 5468in the same local directory that the regular config file is located in (usually 5469the Unix home directory). 5470If the regular config file is remote (because the command line option 5471"-p remote_config" was used) then Unix Alpine looks in the Unix home 5472directory for "<CODE>.pinercex</CODE>". 5473If the file does not already exist then no exceptions will be used. 5474You can force exceptions to be used by using the "-x" option or 5475by creating an empty "<CODE>.pinercex</CODE>" file. 5476<P> 5477For PC-Alpine, if you don't have a "-x" command line option, 5478PC-Alpine will use the value of the 5479environment variable <CODE>$PINERCEX</CODE>. 5480If that is not set, PC-Alpine will look for 5481the local file "<CODE>PINERCEX</CODE>" 5482in the same local directory that the regular config file is located in. 5483If the regular config file is remote (because the command line option 5484"-p remote_config" was used) then PC-Alpine looks in the 5485local directory specified by the "-aux local_directory" command 5486line argument, or the directory <CODE>$HOME\PINE</CODE>, or 5487in the <CODE><PINE.EXE </CODE>directory<CODE>></CODE>. 5488<P> 5489When you have an exception configuration there is a new command 5490in the Alpine Setup screen, Setup/eXceptions. 5491It toggles between exceptions and the regular configuration. 5492This is the usual way to make changes in your exceptional configuration data. 5493For example, you would type "S" for Setup, "X" for 5494eXception, then follow that with one of the Setup commands, like "C" 5495for Config or "K" for Kolor. 5496<P> 5497For most people, splitting the configuration information into two pieces is 5498going to be most useful if the generic information is accessed 5499<A HREF="h_config_remote_config">remotely</A>). 5500That data will be the same no matter where you access it from and if you 5501change it that change will show up everywhere. 5502The exceptional data will most commonly be in a local file, so that the 5503contents may easily be different on each computing platform used. 5504<P> 5505If you already have a local configuration file with settings you like 5506you may find that the command Setup/RemoteConfigSetup is useful 5507in helping you convert to a remote configuration. 5508The command line flag "-copy_pinerc" 5509may also be useful. 5510<P> 5511<End of help on this topic> 5512</BODY> 5513</HTML> 5514============== h_config_inheritance ============= 5515<HTML> 5516<HEAD> 5517<TITLE>Configuration Inheritance</TITLE> 5518</HEAD> 5519<BODY> 5520<H1>Configuration Inheritance</H1> 5521 5522Configuration inheritance is a power user feature. 5523It is confusing and not completely supported by the configuration 5524user interface. 5525We start with an explanation of how configuration works in hopes of making 5526it easier to describe how inheritance works. 5527<P> 5528Alpine uses a hierarchy of configuration values from different locations. 5529There are five ways in which each configuration option (configuration 5530variable) can be set. 5531In increasing order of precedence they are: 5532<P> 5533<OL> 5534<LI> the system-wide configuration file. 5535 5536<LI> the personal configuration file 5537 5538<LI> the personal exceptions file 5539 5540<LI> a command line argument 5541 5542<LI> the system-wide <EM>fixed</EM> configuration file (Unix Alpine only) 5543</OL> 5544<P> 5545The fixed configuration file is normally 5546<CODE><!--#echo var="PINE_CONF_FIXED_PATH"--></CODE>. 5547<P> 5548The system-wide configuration file is normally 5549<CODE><!--#echo var="PINE_CONF_PATH"--></CODE> for Unix Alpine and is normally not 5550set for PC-Alpine. 5551For PC-Alpine, if the environment variable <EM>$PINECONF</EM> is set, that 5552is used for the system-wide configuration. 5553This location can be set or changed on the command line with the -P flag. 5554The system-wide configuration file can be either a local file or a 5555remote configuration folder. 5556<P> 5557For Unix Alpine, the personal configuration file is normally the file 5558<CODE>.pinerc</CODE> in the user's home directory. 5559This can be changed with the -p command line flag. 5560For PC-Alpine, the personal configuration file is in 5561<CODE>$PINERC</CODE> or <CODE><AlpineRC registry value></CODE> or 5562<CODE>$HOME\PINE\PINERC</CODE> or 5563<CODE><PINE.EXE </CODE>dir<CODE>>\PINERC</CODE>. 5564This can be changed with the -p command line flag. 5565If -p is used, the configuration data may be in a local file or a remote config 5566folder. 5567<P> 5568For Unix Alpine, the personal exceptions configuration file is named 5569<CODE>.pinercex</CODE> and is in the same directory as the personal 5570configuration file, if that configuration file is not remote, and is in 5571the home directory if the personal configuration file is remote. 5572If the file exists, then exceptions are turned on. 5573If it doesn't, then you are not using exceptions. 5574Alternatively, you may change the location of the exceptions configuration 5575by using the command line argument "-x <exceptions_config>". 5576Like the personal configuration data, exceptions_config may be 5577either local or remote. 5578<P> 5579For PC-Alpine, the personal exceptions configuration file is named 5580<CODE>PINERCEX</CODE> and is in the same directory as the personal 5581configuration file unless the personal configuration file is remote. 5582In that case, it is in the local directory specified by the 5583"-aux local_directory" command line argument. 5584(In the case that the personal configuration is remote and there is no 5585"-aux" command line argument, Alpine searches for 5586a PINERCEX file in the directory <CODE>$HOME\PINE</CODE> and 5587the directory <CODE><PINE.EXE </CODE>dir<CODE>></CODE>.) 5588If the file exists, then exceptions are turned on. 5589If it doesn't, then you are not using exceptions. 5590You may change the location of the exceptions configuration 5591by using the command line argument "-x <exceptions_config>". 5592or with the 5593environment variable <CODE>$PINERCEX</CODE> (if there is no "-x" 5594option). 5595<P> 5596To reiterate, the value of a configuration option is taken from the 5597last location in the list above in which it is set. 5598Or, thinking about it slightly differently, a default value for an option 5599is established in the system-wide configuration file (or internally by Alpine 5600if there is no value in the system-wide file). 5601That default remains in effect until and unless it is overridden by a value in a 5602location further down the list, in which case a new "default" 5603value is established. 5604As we continue down the list of locations we either retain the 5605value at each step or establish a new value. 5606The value that is still set after going through the whole list of 5607configuration locations is the one that is used. 5608<P> 5609So, for example, if an option is set in the system-wide configuration 5610file and in the personal configuration file, but is not set in the 5611exceptions, on the command line, or in the fixed file; then the value 5612from the personal configuration file is the one that is used. 5613Or, if it is set in the system-wide config, in the personal config, not 5614in the exceptions, but is set on the command line; then the value 5615on the command line is used. 5616<P> 5617Finally we get to inheritance. 5618For configuration options that are lists, like "<!--#echo var="VAR_smtp-server"-->" or 5619"<!--#echo var="VAR_incoming-folders"-->", 5620the inheritance mechanism makes it possible to <EM>combine</EM> 5621the values from different locations instead of <EM>replacing</EM> the value. 5622This is true of all configuration lists other than the "Feature-List", 5623for which you may already set whatever you want at 5624any configuration location (by using the "no-" prefix if 5625necessary). 5626<P> 5627To use inheritance, set the first item in a configuration list to the 5628token "INHERIT", without the quotes. 5629If the first item is "INHERIT", 5630then instead of replacing the default value established so far, the rest of 5631the list is appended to the default value established so far and that is 5632the new value. 5633<P> 5634Here is an example which may make it clearer. Suppose we have: 5635<P> 5636<PRE> 5637 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com 5638 Personal config : smtp-server = INHERIT, mysmtp.home 5639 Exceptions config : smtp-server = <No Value Set> 5640 Command line : smtp-server = <No Value Set> 5641 Fixed config : smtp-server = <No Value Set> 5642</PRE> 5643<P> 5644 5645This would result in an effective smtp-server option of 5646<P> 5647<PRE> 5648 smtp-server = smtp1.corp.com, smtp2.corp.com, mysmtp.home 5649</PRE> 5650<P> 5651The "INHERIT" token can be used in any of the configuration files 5652and the effect cascades. 5653For example, if we change the above example to: 5654<P> 5655<PRE> 5656 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com 5657 Personal config : smtp-server = INHERIT, mysmtp.home 5658 Exceptions config : smtp-server = INHERIT, yoursmtp.org 5659 Command line : smtp-server = <No Value Set> 5660 Fixed config : smtp-server = <No Value Set> 5661</PRE> 5662<P> 5663 5664This would result in: 5665<P> 5666<PRE> 5667 smtp-server = smtp1.corp.com, smtp2.corp.com, mysmtp.home, yoursmtp.org 5668</PRE> 5669<P> 5670Unset variables are skipped over (the default value is carried forward) so 5671that, for example: 5672<P> 5673<PRE> 5674 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com 5675 Personal config : smtp-server = <No Value Set> 5676 Exceptions config : smtp-server = INHERIT, yoursmtp.org 5677 Command line : smtp-server = <No Value Set> 5678 Fixed config : smtp-server = <No Value Set> 5679</PRE> 5680<P> 5681 5682produces: 5683<P> 5684<PRE> 5685 smtp-server = smtp1.corp.com, smtp2.corp.com, yoursmtp.org 5686</PRE> 5687<P> 5688 5689If any later configuration location has a value set (for a particular list 5690option) which does <EM>not</EM> begin with "INHERIT", 5691then that value replaces whatever value has been defined up to that point. 5692In other words, that cancels out any previous inheritance. 5693<P> 5694<PRE> 5695 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com 5696 Personal config : smtp-server = INHERIT, mysmtp.org 5697 Exceptions config : smtp-server = yoursmtp.org 5698 Command line : smtp-server = <No Value Set> 5699 Fixed config : smtp-server = <No Value Set> 5700</PRE> 5701<P> 5702 5703results in: 5704<P> 5705<PRE> 5706 smtp-server = yoursmtp.org 5707</PRE> 5708<P> 5709 5710For some configuration options, like "<!--#echo var="VAR_viewer-hdr-colors"-->" or 5711"<!--#echo var="VAR_patterns-roles"-->", it is 5712difficult to insert the value "INHERIT" into the list of values 5713for the option using the normal Setup tools. 5714In other words, the color setting screen (for example) does not 5715provide a way to input the text "INHERIT" as the first 5716item in the <!--#echo var="VAR_viewer-hdr-colors"--> option. 5717The way to do this is to either edit the pinerc file directly and manually 5718insert it, or turn 5719on the <A HREF="h_config_expose_hidden_config"><!--#echo var="FEAT_expose-hidden-config"--></A> 5720feature and insert it using the Setup/Config screen. 5721<P> 5722<End of help on this topic> 5723</BODY> 5724</HTML> 5725============== h_special_xon_xoff ============= 5726<HTML> 5727<HEAD> 5728<TITLE>Explanation of Alpine's XOFF/XON Handling</TITLE> 5729</HEAD> 5730<BODY> 5731<H1>XOFF/XON Handling within Alpine</H1> 5732 5733By default, Alpine treats Ctrl-S or Ctrl-Q (sometimes known as XOFF 5734and XON) as normal characters, even though Alpine does not use them. 5735However, the printer, modem, or communication software you are using may 5736be configured for "software flow control," which means that 5737XON/XOFF must be treated as special characters by the operating system. 5738If you see messages such as "^S not defined for this screen", 5739then your system is probably using software flow control. In this case 5740you will need to set the 5741<A HREF="h_config_preserve_start_stop">"<!--#echo var="FEAT_preserve-start-stop-characters"-->"</A> 5742feature. 5743<P> 5744If you <EM>do</EM> set this 5745feature, be advised that if you accidentally hit a Ctrl-S, Alpine will 5746mysteriously freeze up with no warning. In this case, try typing a Ctrl-Q 5747and see if that puts things right. Printing via the 5748"attached-to-ansi" or 5749"attached-to-wyse" 5750option will automatically enable software 5751flow-control handling for the duration of the printing. 5752<P> 5753<End of help on this topic> 5754</BODY> 5755</HTML> 5756============= h_special_help_nav ============= 5757<HTML> 5758<HEAD> 5759<TITLE>Help Text Navigation Explained</TITLE> 5760</HEAD> 5761<BODY> 5762<H1>Help Text Navigation Explained</H1> 5763 5764Alpine contains extensive context-sensitive help text. At any point, 5765pressing the "?" key will bring up a page of help text 5766explaining the options available to you. You can leave the help 5767text screen and return to normal Alpine operation by pressing 5768the 5769<!--chtml if pinemode="function_key"--> 5770F3 function 5771<!--chtml else--> 5772"E" 5773<!--chtml endif--> 5774key to Exit Help at any time. 5775 5776<P> 5777Within the help screen you might find a word or phrase displayed in 5778inverse text and others displayed in bold typeface. Such words and 5779phrases are used to tell you Alpine has more information available on 5780the topic they describe. 5781The inverted text is the "selected" topic. 5782Use the arrow keys, Ctrl-F, and Ctrl-B to change which of the phrases 5783displayed in bold type 5784is "selected". 5785Hit the Return key to display the information Alpine has available on that 5786topic. While viewing such additional information, the 5787<!--chtml if pinemode="function_key"--> 5788F3 function 5789<!--chtml else--> 5790"P" 5791<!--chtml endif--> 5792key will return you to the previous help screen, and the 5793<!--chtml if pinemode="function_key"--> 5794F2 function 5795<!--chtml else--> 5796"E" 5797<!--chtml endif--> 5798key will Exit the Help system altogether. 5799 5800<P> 5801The "N" command will tell you the internal name of the help text you are 5802reading each time, so that you can send this name in the text of a message 5803and create a direct link to that internal help using the x-pine-help URL 5804scheme. For example, the direct link to this item is 5805x-pine-help:h_special_help_nav. If you add this text to a message, then 5806a person using Pine to read such message would have a direct link to this 5807help text. 5808 5809<P> 5810When you are finished reading this help text, you can press the 5811<!--chtml if pinemode="function_key"--> 5812F3 function 5813<!--chtml else--> 5814"P" 5815<!--chtml endif--> 5816key to return to the previously displayed help text. 5817 5818<P> 5819<End of help on this topic> 5820</BODY> 5821</HTML> 5822============= h_special_list_commands ============= 5823<HTML> 5824<HEAD> 5825<TITLE>Email List Commands Explained</TITLE> 5826</HEAD> 5827<BODY> 5828<H1>Email List Commands Explained</H1> 5829 5830Electonic mail lists provide a way for like-minded users to join in 5831discussions on topics of interest. The email list itself is 5832represented by a 5833single address that participants send messages to when they have 5834something of interest to share with other members of the list. The 5835receiving computer then, either automatically or after review by the 5836list's owner (or moderator), sends a copy of that message to each 5837member of the list. 5838 5839<P> 5840Usually, subscribing and unsubscribing is done by sending requests in 5841an email message to a special address setup to handle managing list 5842membership. Often this is the name of the list followed by 5843<I>-request</I>. This address is almost <EM>never</EM> the same as 5844the address used to send messages to the list. 5845 5846<P> 5847Unfortunately, email list participation commands are more a matter 5848of convention than standard, and thus may vary from list to list. 5849Increasingly, list management software is adding information to 5850the copy of the postings as they're copied to the list members that 5851explains how to do the various list management functions. 5852 5853<P> 5854Alpine will recognize this information and offer the management commands 5855they represent in a simple display. One or more of the following 5856operations will be made available: 5857 5858<DL> 5859<DT>Help</DT> 5860<DD> 5861A method to get help on subscribing, unsubscribing, 5862an explanation of what the list is about, or special instructions 5863for participation. This may be in the form of a reply in response 5864to an email message, or instructions on how to connect to a Web site. 5865</DD> 5866 5867<DT>Unsubscribe</DT> 5868<DD> 5869A method to get your email addressed removed from the list of 5870recipients of the email list. 5871</DD> 5872 5873<DT>Subscribe</DT> 5874<DD> 5875A method to get your email address added to the list of recipients 5876of the email list. It may be in the form of a message sent to 5877a special address or you may be connected to a web site. 5878<DD> 5879</DD> 5880 5881<DT>Post</DT> 5882<DD> 5883A method used to post to the email list. However, it might also 5884indicate that no posting is allowed directly to the list. 5885</DD> 5886 5887<DT>Owner</DT> 5888<DD> 5889A method to contact the list owner for special questions you might 5890have regarding the list. 5891</DD> 5892 5893<DT>Archive</DT> 5894<DD> 5895A method to view an archive of previous messages posted to the list. 5896This may be in the form of a mail folder on a remote computer, an 5897IMAP mailbox or even a Web site. 5898</DD> 5899</DL> 5900 5901<P> 5902<End of help on this topic> 5903</BODY> 5904</HTML> 5905============= h_quota_command ============= 5906<HTML> 5907<HEAD> 5908<TITLE>Quota Screen Explained</TITLE> 5909</HEAD> 5910<BODY> 5911<H1>Quota Screen Explained</H1> 5912 5913<P> This screen summarizes the quota report for this mailbox in the 5914IMAP server. For each resource that you have a quota, this reports summarizes 5915its use and limit. 5916 5917<P> Your IMAP server administrator may have set a quota based either on 5918the total size of your mailbox (STORAGE), or the number of messages in 5919your mailbox (MESSAGES), or some other criteria. This will be reported 5920to you indicating the type of quota, its total use and its limit. 5921 5922<P> The report for STORAGE is reported in kibibytes (KiB). One kibibyte is 59231024 bytes. Each of the characters that you see in this help text is one 5924byte, and this help text is about 1 kibibyte in size. Small messages sent 5925by Alpine are normally less than 4 kibibytes in size (which includes 5926headers and text). Other email programs may send messages with bigger 5927sizes when they send messages, since they send plain text and an 5928alternative part in HTML. 5929 5930<P> A convenient way to save space for the STORAGE type of quota is by 5931deleting attachments. This is done on each individual message by pressing 5932the "V" command while reading the message text, then moving the cursor 5933to the position of the attachment that is to be deleted, then pressing 5934"D" to delete such attachment, going back to reading the 5935message with the "<" command and pressing "S" to 5936save the message in the same folder you are reading from. The saved 5937message will not have the attachment that was marked deleted. Now you 5938can delete and expunge the message with the unwanted attachment. 5939 5940<P> 5941<End of help on this topic> 5942</BODY> 5943</HTML> 5944============= h_mail_thread_index ============= 5945<HTML> 5946<HEAD> 5947<TITLE>THREAD INDEX COMMANDS</TITLE> 5948</HEAD> 5949<BODY> 5950<H1>THREAD INDEX COMMANDS</H1> 5951<!--chtml if pinemode="function_key"--> 5952Available Commands -- Group 1 Available Commands -- Group 2<BR> 5953------------------------------- -----------------------------<BR> 5954F1 Show Help Text F1 Show Help Text<BR> 5955F2 Toggle to see more commands F2 Toggle to see more commands<BR> 5956F3 <A HREF="h_common_folders">FOLDER LIST</A> Screen F3 MAIN MENU Screen<BR> 5957F4 View current thread F4 Quit Alpine<BR> 5958F5 Move to previous thread F5 <A HREF="h_common_compose">Compose</A> a message<BR> 5959F6 Move to next thread F6 <A HREF="h_common_goto">Goto</A> a specified folder<BR> 5960F7 Show previous screen F7 <A HREF="h_common_nextnew">Next new</A> thread<BR> 5961F8 Show next screen F8 <A HREF="h_index_cmd_whereis">Whereis</A><BR> 5962F9 <A HREF="h_common_delete">Mark thread for deletion</A> F9 <A HREF="h_common_print">Print</A> index<BR> 5963F10 <A HREF="h_common_delete">Undelete</A> (remove delete mark) F10 <A HREF="h_common_take">Take Address</A> into address book<BR> 5964F11 <A HREF="h_common_reply">Reply</A> to thread F11 <A HREF="h_common_save">Save</A> messages into an email folder<BR> 5965F12 <A HREF="h_common_reply">Forward</A> messages F12 <A HREF="h_common_save">Export</A> messages into a plain file<BR> 5966<BR> 5967Available Commands -- Group 3<BR> 5968-----------------------------<BR> 5969F3 <A HREF="h_index_cmd_expunge">Expunge</A> F7 <A HREF="h_index_cmd_sort">Sort</A> F10 <A HREF="h_common_bounce">Bounce</A> (remail) msg<BR> 5970F5 <A HREF="h_index_cmd_select">Select</A> F8 <A HREF="h_common_jump">Jump</A> to thread F11 <A HREF="h_common_flag">Flag</A> messages as important<BR> 5971F6 F9 <A HREF="h_common_hdrmode">Full Header Mode</A> F12 <A HREF="h_common_pipe">Pipe</A> to a Unix command<BR> 5972<BR> 5973Available Commands -- Group 4<BR> 5974-----------------------------<BR> 5975F3 Select Current F4 <A HREF="h_index_cmd_zoom">Zoom</A> F5 COLLECTION LIST Screen 5976F6 <A HREF="h_common_role">Compose using a role</A><BR> 5977<BR> 5978<!--chtml else--> 5979Navigating the List of Threads Operations on the Current Thread<BR> 5980------------------------------- ---------------------------------<BR> 5981 P Move to the previous thread > View Thread % <A HREF="h_common_print">Print</A><BR> 5982 N Move to the next thread R <A HREF="h_common_reply">Reply</A> to thread F <A HREF="h_common_reply">Forward</A><BR> 5983 - Show previous screen D <A HREF="h_common_delete">Mark thread for deletion</A><BR> 5984Spc (space bar) Show next screen U <A HREF="h_common_delete">Undelete</A> (remove deletion mark)<BR> 5985 J <A HREF="h_common_jump">Jump</A> to a specific thread T <A HREF="h_common_take">Take Address</A> into Address Book<BR> 5986 W <A HREF="h_index_cmd_whereis">Whereis</A> -- search for a S <A HREF="h_common_save">Save</A> into an email folder<BR> 5987 specific thread E <A HREF="h_common_save">Export</A> as a plain text file<BR> 5988Tab <A HREF="h_common_nextnew">Next new</A> thread B <A HREF="h_common_bounce">Bounce</A> * <A HREF="h_common_flag">Flag</A><BR> 5989 | <A HREF="h_common_pipe">Pipe</A> to a Unix Command<BR> 5990<BR> 5991Miscellaneous Operations General Alpine Commands<BR> 5992------------------------ ---------------------<BR> 5993 G <A HREF="h_common_goto">Goto</A> a specified folder O Show all other available commands<BR> 5994 $ <A HREF="h_index_cmd_sort">Sort</A> order of index ? Show Helptext Q Quit Alpine<BR> 5995 H <A HREF="h_common_hdrmode">Full header mode</A> M MAIN MENU Screen < <A HREF="h_common_folders">FOLDER LIST</A> Screen<BR> 5996 X <A HREF="h_index_cmd_expunge">Expunge/Exclude</A> C <A HREF="h_common_compose">Compose</A> a new message<BR> 5997 Z <A HREF="h_index_cmd_zoom">Zoom</A> # <A HREF="h_common_role">Compose using a role</A><BR> 5998 ; <A HREF="h_index_cmd_select">Select</A> A <A HREF="h_index_cmd_apply">Apply</A> L COLLECTION LIST Screen<BR> 5999 : Select Messages in Current Thread<BR> 6000<!--chtml endif--> 6001<P> 6002 6003NOTE: 6004<OL> 6005 <LI>For help on a particular command, highlight the bold text associated 6006with it above and hit Return. 6007 <LI>Availability of certain commands depends on <A HREF="h_common_conditional_cmds">feature settings</A>. 6008</OL> 6009 6010<H2>Description of the THREAD INDEX Screen</H2> 6011 6012The THREAD INDEX displays summary information from each 6013thread (conversation) in the current folder. 6014This is useful if you want to quickly 6015scan new threads, or find a particular thread without having to go 6016through the text of each message, or to quickly get rid of junk 6017threads, etc. 6018The current thread is always highlighted. 6019Each line of the THREAD INDEX contains the following columns: <P> 6020<DL> 6021 <DT>STATUS:</DT> 6022 <DD> The markings on the left side of the thread tell you about its 6023status. You may see one or more of the following codes on any given 6024thread: 6025<UL> 6026 <LI> "D" for Deleted. All of the messages in this thread are marked for deletion but not yet eXpunged from the folder. 6027 <LI> "A" for Answered. All of the messages in this thread are marked answered. 6028 <LI> "N" for New. At least one message in the thread is New (you haven't looked at it yet). 6029 <LI> "+" for direct-to-you. The "+" indicates that a message in the thread was sent directly to your account, your copy is not part of a cc: or a mailing list. 6030 <LI> "-" for cc-to-you. The "-" indicates that a 6031 message in the thread was sent to you as a cc:. This symbol will only show up if 6032 the feature 6033 "<A HREF="h_config_mark_for_cc"><!--#echo var="FEAT_mark-for-cc"--></A>" is turned on (which is the default). 6034 <LI> "X" for selected. You have selected at least one message in the thread by using the 6035 "select" command. (Some systems may optionally allow selected 6036 messages to be denoted by the index line being displayed in bold 6037 type instead.) 6038 <LI> "*" for Important. You have previously used the "Flag" command 6039 to mark at least one message in this thread as "important". 6040</UL></DD><P> 6041 6042 <DT>THREAD NUMBER:</DT> 6043 <DD>Threads in a folder are numbered, from one through the number 6044of threads in the folder, to help you know where you are in the folder. 6045</DD><P> 6046 6047 <DT>DATE STARTED:</DT> 6048 <DD>The date the thread was started. This is actually from the Date header 6049of the first message in the thread. It doesn't take different time zones 6050into account.</DD><P> 6051 6052 <DT>WHO STARTED THE THREAD:</DT> 6053 <DD>This is usually the name of the sender of the first message in the thread, taken from 6054the From header of the message. 6055If there is no personal name given in that 6056address, then the email address is used instead. 6057If the message is from you (or from one of your 6058<A HREF="h_config_alt_addresses">alternate addresses</A>), 6059then the recipient's name is shown here instead, with the characters 6060"To: " inserted before the name. 6061(The idea of this is that if you started the thread you would rather see who 6062the mail was sent to instead of that the mail was from you.) 6063In Newsgroups, if you are 6064the sender and there are no email recipients, the newsgroup name will be 6065listed after the "To: ". 6066</DD><P> 6067 6068 <DT>SIZE:</DT> 6069 <DD>The number in parentheses is the number of messages in the thread.</DD><P> 6070 6071 <DT>SUBJECT:</DT> 6072 <DD>As much of the thread's subject line as will fit on the screen. 6073This is the subject of the first message in the thread.</DD> 6074</DL> 6075 6076<P><UL> 6077<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 6078</UL> 6079<P> 6080<End of help on this topic> 6081</BODY> 6082</HTML> 6083============= h_mail_index ============= 6084<HTML> 6085<HEAD> 6086<TITLE>MESSAGE INDEX COMMANDS</TITLE> 6087</HEAD> 6088<BODY> 6089<H1>MESSAGE INDEX COMMANDS</H1> 6090<!--chtml if pinemode="function_key"--> 6091Available Commands -- Group 1 Available Commands -- Group 2<BR> 6092------------------------------- -----------------------------<BR> 6093F1 Show Help Text F1 Show Help Text<BR> 6094F2 Toggle to see more commands F2 Toggle to see more commands<BR> 6095F3 <A HREF="h_common_folders">FOLDER LIST</A> Screen F3 MAIN MENU Screen<BR> 6096F4 View current message F4 Quit Alpine<BR> 6097F5 Move to previous message F5 <A HREF="h_common_compose">Compose</A> a message<BR> 6098F6 Move to next message F6 <A HREF="h_common_goto">Goto</A> a specified folder<BR> 6099F7 Show previous screen of messages F7 <A HREF="h_common_nextnew">Next new</A> message<BR> 6100F8 Show next screen of messages F8 <A HREF="h_index_cmd_whereis">Whereis</A><BR> 6101F9 <A HREF="h_common_delete">Mark message for deletion</A> F9 <A HREF="h_common_print">Print</A> message<BR> 6102F10 <A HREF="h_common_delete">Undelete</A> (remove delete mark) F10 <A HREF="h_common_take">Take Address</A> into address book<BR> 6103F11 <A HREF="h_common_reply">Reply</A> to message F11 <A HREF="h_common_save">Save</A> message into an email folder<BR> 6104F12 <A HREF="h_common_reply">Forward</A> message F12 <A HREF="h_common_save">Export</A> message into a plain file<BR> 6105<BR> 6106Available Commands -- Group 3<BR> 6107-----------------------------<BR> 6108F3 <A HREF="h_index_cmd_expunge">Expunge/Exclude</A> F7 <A HREF="h_index_cmd_sort">Sort</A> order of index F10 <A HREF="h_common_bounce">Bounce</A> (remail) msg<BR> 6109F5 <A HREF="h_index_cmd_select">Select</A> F8 <A HREF="h_common_jump">Jump</A> to message F11 <A HREF="h_common_flag">Flag</A> message as important<BR> 6110F6 <A HREF="h_index_cmd_apply">Apply</A> F9 <A HREF="h_common_hdrmode">Full Header Mode</A> F12 <A HREF="h_common_pipe">Pipe</A> to a Unix command<BR> 6111<BR> 6112Available Commands -- Group 4<BR> 6113-----------------------------<BR> 6114F3 Select Current F4 <A HREF="h_index_cmd_zoom">Zoom</A> F5 COLLECTION LIST Screen 6115F6 <A HREF="h_common_role">Compose using a role</A> F10 <A HREF="h_index_collapse_expand">Collapse/Expand</A> Thread<BR> 6116<BR> 6117<!--chtml else--> 6118Navigating the List of Messages Operations on the Current Message<BR> 6119------------------------------- ---------------------------------<BR> 6120 P Move to the previous message > View % <A HREF="h_common_print">Print</A><BR> 6121 N Move to the next message R <A HREF="h_common_reply">Reply</A> to message F <A HREF="h_common_reply">Forward</A><BR> 6122 - Show previous screen of messages D <A HREF="h_common_delete">Mark for deletion</A><BR> 6123Spc (space bar) Show next screen U <A HREF="h_common_delete">Undelete</A> (remove deletion mark)<BR> 6124 J <A HREF="h_common_jump">Jump</A> to a specific message T <A HREF="h_common_take">Take Address</A> into Address Book<BR> 6125 W <A HREF="h_index_cmd_whereis">Whereis</A> -- search for a S <A HREF="h_common_save">Save</A> into an email folder<BR> 6126 specific message E <A HREF="h_common_save">Export</A> as a plain text file<BR> 6127Tab <A HREF="h_common_nextnew">Next new</A> message B <A HREF="h_common_bounce">Bounce</A> * <A HREF="h_common_flag">Flag</A><BR> 6128 | <A HREF="h_common_pipe">Pipe</A> to a Unix Command<BR> 6129Miscellaneous Operations<BR> 6130------------------------<BR> 6131 G <A HREF="h_common_goto">Goto</A> a specified folder General Alpine Commands<BR> 6132 $ <A HREF="h_index_cmd_sort">Sort</A> order of index ---------------------<BR> 6133 H <A HREF="h_common_hdrmode">Full header mode</A> O Show all other available commands<BR> 6134 X <A HREF="h_index_cmd_expunge">Expunge/Exclude</A> ? Show Help text Q Quit Alpine<BR> 6135 Z <A HREF="h_index_cmd_zoom">Zoom</A> M MAIN MENU Screen < <A HREF="h_common_folders">FOLDER LIST</A> Screen<BR> 6136 ; <A HREF="h_index_cmd_select">Select</A> A <A HREF="h_index_cmd_apply">Apply</A> C <A HREF="h_common_compose">Compose</A> a new message<BR> 6137 : Select Current message # <A HREF="h_common_role">Compose using a role</A><BR> 6138 / <A HREF="h_index_collapse_expand">Collapse/Expand</A> Thread L COLLECTION LIST Screen<BR> 6139<!--chtml endif--> 6140<P> 6141 6142NOTE: 6143<OL> 6144 <LI>For help on a particular command, highlight the bold text associated 6145with it above and hit Return. 6146 <LI>Availability of certain commands depends on <A HREF="h_common_conditional_cmds">feature settings</A>. 6147</OL> 6148 6149<H2>Description of the MESSAGE INDEX Screen</H2> 6150 6151The MESSAGE INDEX displays summary information from each 6152message in the current folder. 6153This is useful if you want to quickly 6154scan new messages, or find a particular message without having to go 6155through the text of each message, or to quickly get rid of junk 6156messages, etc. 6157<P> 6158The current message is always highlighted 6159and many commands operate on the current message. 6160For example, the Delete command will delete the current message. 6161If the folder is sorted by either Threads or OrderedSubject, then, depending 6162on some of your configuration settings, a single line in the index may 6163refer to an entire thread or to a subthread. 6164If that is the case, then the commands that normally operate on the current 6165message will operate on the thread or subthread instead. 6166For example, the Delete command will delete the whole collapsed thread 6167instead of just a single message. 6168<P> 6169Each line of the MESSAGE INDEX contains the following columns (by default -- 6170you can change this with the 6171"<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" option 6172in the SETUP CONFIGURATION screen): <P> 6173<DL> 6174 <DT>STATUS:</DT> 6175 <DD> The markings on the left side of the message tell you about its 6176status. You may see one or more of the following codes on any given 6177message: 6178<UL> 6179 <LI> "D" for Deleted. You have marked this message for deletion but not 6180 yet eXpunged the folder. 6181 <LI> "N" for New. You have not looked at the text of the message yet. 6182 <LI> "A" for Answered. Any time you reply to a message it is considered 6183 to be answered. 6184 <LI> "F" for Forwarded. Similar to Answered, this is set whenever you 6185 forward a message. 6186 <LI> "+" for direct-to-you. The "+" indicates that a message was sent 6187 directly to your account, your copy is not part of a cc: or a 6188 mailing list. 6189 <LI> "-" for cc-to-you. The "-" indicates that a 6190 message was sent to you as a cc:. This symbol will only show up if 6191 the feature 6192 "<A HREF="h_config_mark_for_cc"><!--#echo var="FEAT_mark-for-cc"--></A>" is turned on (which is the default). 6193 <LI> "X" for selected. You have selected the message by using the 6194 "select" command. (Some systems may optionally allow selected 6195 messages to be denoted by the index line being displayed in bold 6196 type.) 6197 <LI> "*" for Important. You have previously used the "Flag" command 6198 to mark this message as "important". 6199</UL></DD><P> 6200 6201 <DT>MESSAGE NUMBER:</DT> 6202 <DD>Messages in a folder are numbered, from one through the number 6203of messages in the folder, to help you know where you are in the folder. 6204These numbers are always in increasing order, even if you sort the folder 6205in a different way.</DD><P> 6206 6207 <DT>DATE SENT:</DT> 6208 <DD>The date the message was sent. By default, messages are 6209ordered by arrival time, not by date sent. Most of the time, arrival time 6210and date sent (effectively departure time) are similar. Sometimes, 6211however, the index will appear to be out of order because a message took a 6212long time in delivery or because the sender is in a different time 6213zone than you are. This date is just the date from the Date header 6214field in the message.</DD><P> 6215 6216 <DT>WHO SENT THE MESSAGE:</DT> 6217 <DD>This is usually the name of the sender of the message, taken from 6218the From header of the message. 6219If there is no personal name given in that 6220address, then the email address is used instead. 6221If the message is from you (or from one of your 6222<A HREF="h_config_alt_addresses">alternate addresses</A>), 6223then the recipient's name is shown here instead, with the characters 6224"To: " inserted before the name. 6225(The idea of this is that if you sent the mail you would rather see who 6226the mail was sent to instead of that the mail was from you. 6227This behavior may be changed by modifying the <!--#echo var="VAR_index-format"--> option mentioned 6228above. 6229In particular, use the FROM token or the FROMORTONOTNEWS token 6230in place of the FROMORTO token.) 6231In Newsgroups, if you are 6232the sender and there are no email recipients, the newsgroup name will be 6233listed after the "To: ". </DD><P> 6234 6235 <DT>SIZE:</DT> 6236 <DD>The number in parentheses is the number of characters in the message. 6237It may have a suffix of K, M, or G which means the number should be 6238multiplied by one thousand, one million, or one billion to get the 6239size of the message.</DD><P> 6240 6241 <DT>SUBJECT:</DT> 6242 <DD>As much of the message's subject line as will fit on the screen.</DD> 6243</DL> 6244 6245<P><UL> 6246<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 6247</UL> 6248<P> 6249<End of help on this topic> 6250</BODY> 6251</HTML> 6252============= h_mail_view ======================== 6253<HTML> 6254<HEAD> 6255<TITLE>MESSAGE TEXT SCREEN</TITLE> 6256</HEAD> 6257<BODY> 6258<H1>MESSAGE TEXT SCREEN</H1> 6259<!--chtml if pinemode="function_key"--> 6260Available Commands -- Group 1 Available Commands -- Group 2<BR> 6261------------------------------- ------------------------------<BR> 6262F1 Show Help Text F1 Show Help Text<BR> 6263F2 Toggle to see more commands F2 Toggle to see more commands<BR> 6264F3 <A HREF="h_common_index">MESSAGE INDEX</A> Screen F3 MAIN MENU Screen<BR> 6265F4 <A HREF="h_view_cmd_viewattch">View attachment</A> F4 Quit Alpine<BR> 6266F5 Display previous message F5 <A HREF="h_common_folders">FOLDER LIST</A> Screen<BR> 6267F6 Display next message F6 <A HREF="h_common_goto">Goto</A> a specified folder<BR> 6268F7 Previous screen of this message F7 <A HREF="h_common_compose">Compose</A> message<BR> 6269F8 Next screen of this message F8 <A HREF="h_view_cmd_whereis">Whereis</A><BR> 6270F9 <A HREF="h_common_delete">Mark message for deletion</A> F9 <A HREF="h_common_print">Print</A> message<BR> 6271F10 <A HREF="h_common_delete">Undelete</A> (remove delete mark) F10 <A HREF="h_common_take">Take Address</A> into address book<BR> 6272F11 <A HREF="h_common_reply">Reply</A> to message F11 <A HREF="h_common_save">Save</A> message into an email folder<BR> 6273F12 <A HREF="h_common_reply">Forward</A> F12 <A HREF="h_common_save">Export</A> message into a plain file<BR> 6274<BR> 6275Available Commands -- Group 3<BR> 6276------------------------------<BR> 6277F1 Show Help Text<BR> 6278F2 Toggle to see more commands<BR> 6279F3 <A HREF="h_view_cmd_hilite">View hilited</A><BR> 6280F4 Select current message<BR> 6281F5 Previous selectable item<BR> 6282F6 Next selectable item<BR> 6283F7 <A HREF="h_common_jump">Jump</A> to message number<BR> 6284F8 <A HREF="h_common_nextnew">Next new</A> message<BR> 6285F9 <A HREF="h_common_hdrmode">Display full headers</A><BR> 6286F10 <A HREF="h_common_bounce">Bounce</A> message<BR> 6287F11 <A HREF="h_common_flag">Flag</A> message<BR> 6288F12 <A HREF="h_common_pipe">Pipe</A> to a Unix command<BR> 6289Available Commands -- Group 4<BR> 6290F5 <A HREF="h_common_role">Compose using a role</A><BR> 6291<!--chtml else--> 6292Operations on the Current Message<BR> 6293---------------------------------<BR> 6294<BR> 6295 - Show previous page of this msg S <A HREF="h_common_save">Save</A> into an email folder<BR> 6296Spc (space bar) Show next page E <A HREF="h_common_save">Export</A> as a plain text file<BR> 6297 > <A HREF="h_view_cmd_viewattch">View attachment</A> B <A HREF="h_common_bounce">Bounce</A><BR> 6298 R <A HREF="h_common_reply">Reply</A> to message F <A HREF="h_common_reply">Forward</A> message<BR> 6299 D <A HREF="h_common_delete">Mark for deletion</A> Ret View <A HREF="h_view_cmd_hilite">hilited</A> item<BR> 6300 U <A HREF="h_common_delete">Undelete</A> (remove deletion mark) ^F Select next <A HREF="h_view_cmd_hilite">hilited</A> item in message<BR> 6301 T <A HREF="h_common_take">Take Address</A> into Address Book ^B Select previous <A HREF="h_view_cmd_hilite">hilited</A> item<BR> 6302 % <A HREF="h_common_print">Print</A> * <A HREF="h_common_flag">Flag</A> message<BR> 6303 W <A HREF="h_view_cmd_whereis">Whereis</A>: search for text in msg | <A HREF="h_common_pipe">Pipe</A> to a Unix command<BR> 6304<BR> 6305Navigating the List of Messages Other Commands<BR> 6306------------------------------- ----------------------------<BR> 6307 P Display previous message G <A HREF="h_common_goto">Goto</A> a specified folder<BR> 6308 N Display next message H <A HREF="h_common_hdrmode">Full header mode</A> on/off<BR> 6309 J <A HREF="h_common_jump">Jump</A> to a specific message : Select Current message<BR> 6310Tab <A HREF="h_common_nextnew">Next new</A> message A <A HREF="h_config_prefer_plain_text">Toggle Prefer Plain Text</A><BR> 6311<BR> 6312General Alpine Commands<BR> 6313---------------------<BR> 6314 O Show all other available commands<BR> 6315 ? Show Help text Q Quit Alpine<BR> 6316 M MAIN MENU Screen L <A HREF="h_common_folders">FOLDER LIST</A> Screen (or COLLECTION LIST Screen)<BR> 6317 < <A HREF="h_common_index">MESSAGE INDEX</A> Screen C <A HREF="h_common_compose">Compose</A> a new message<BR> 6318 # <A HREF="h_common_role">Compose using a role</A><BR> 6319<!--chtml endif--> 6320<P> 6321 6322NOTE: 6323<OL> 6324 <LI>For help on a particular command, highlight the bold text associated 6325with it above and hit Return. 6326 <LI>Availability of certain commands depends on <A HREF="h_common_conditional_cmds">feature settings</A>. 6327</OL> 6328 6329<H2>Description of the MESSAGE TEXT Screen</H2> 6330 6331The top line of the view message screen displays status 6332information about the currently open collection and folder and about the 6333current message. It shows the name of the collection in angle brackets 6334and then the name of the folder. The line also displays the number 6335of messages in the folder, the number of the current message and the 6336percentage of the current message that has been displayed on the screen. 6337If the message is marked for deletion "DEL" will appear in the upper 6338right corner. 6339If the message has been answered (but not deleted) "ANS" will show 6340in the corner. 6341<P> 6342 6343NOTE: to rapidly move to the end of a message, hit the 6344<!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif--> 6345(or Ctrl-W) key followed 6346by Ctrl-V. Similarly, 6347<!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif--> 6348followed by Ctrl-Y will take you to the beginning of 6349a message. 6350 6351<H2>Explanation of Alternate Character Sets</H2> 6352 6353Alpine attempts to stay out of the way so that it won't prevent you from 6354viewing mail in any character set. It will simply send the message to 6355your display device. If the device is capable of displaying the 6356message as it was written it will do so. If not, the display may be 6357partially or totally incorrect. 6358If the message contains characters that are not representable in your 6359<A HREF="h_config_char_set">"Display Character Set"</A> 6360variable in your configuration, then a warning message will be printed 6361to your screen at the beginning of the message display. 6362It is probably best to use UNIX Alpine in a terminal emulator 6363capable of displaying UTF-8 characters. 6364See <A HREF="h_config_char_set">Display Character Set</A> for a little 6365more information about character set settings. 6366 6367<P><UL> 6368<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 6369</UL> 6370<P> 6371<End of help on this topic> 6372</BODY> 6373</HTML> 6374======= h_index_cmd_select ======= 6375<HTML> 6376<HEAD> 6377<TITLE>Selecting: Select and WhereIs/Select</TITLE> 6378</HEAD> 6379<BODY> 6380<H1>Selecting: Select and WhereIs/Select</H1> 6381 6382Aggregate operations give you the ability to process a group of messages 6383at once. Acting on multiple messages requires two steps: (1) selecting a 6384set of messages and then; (2) applying a command to that set. The first 6385part is handled by the select command. Select allows you to 6386select messages based on their status (read, answered, etc.), contents, 6387date, size, or keywords. 6388You may also select based on one of your Rules or based on threads, 6389and there are quick options to select a specific message or range of messages, 6390to select the current message, or to select all messages. 6391<P> 6392 6393We describe the various selection criteria briefly: 6394<P> 6395 6396<DL> 6397<DT>select All</DT> 6398<DD> Marks all the messages in the folder as selected. 6399</DD> 6400 6401<DT>select Cur</DT> 6402<DD> Selects the currently highlighted message or currently highlighted 6403set of messages if in a threaded view. 6404</DD> 6405 6406<DT>select by Number</DT> 6407<DD> Select by message number. This may be a comma-separated list instead or 6408a single entry. 6409Each element in the list may be either a single message number or a range 6410of numbers with a dash between the lowest and highest member of the range. 6411Some examples are 7 to select only message number 7; 2-5 to select messages 64122 through 5; and 2-5,7-9,11 to select messages 2, 3, 4, 5, 7, 8, 9, and 11. 6413The word "end" or the character "$" may be used as a 6414substitute for the highest numbered message in the folder, while the 6415character "." represents the message number holding the position 6416of the cursor in the folder. 6417If in a separate thread index where the numbers refer to threads instead of 6418to messages, then you will be selecting all of the messages in the 6419referenced threads instead of selecting by message number. 6420</DD> 6421 6422<DT>select by Date</DT> 6423<DD> Select by either the date stored in the Date headers of each message, 6424or by the date when the messages arrived. 6425This does not adjust for different time zones, but just checks to see what 6426day the message was sent on. 6427You may type in a date. If you do, the date should be in the form 6428<P><SAMP><CENTER>DD-Mon-YYYY</CENTER></SAMP><P> 6429For example, 6430<P><SAMP><CENTER>24-Nov-2004</CENTER></SAMP><P> 6431or 6432<P><SAMP><CENTER>09-Nov-2004</CENTER></SAMP><P> 6433If the date you want is close to the current date, it is probably 6434easier to use the "^P Prev Day" or "^N Next Day" commands to change the default date that 6435is displayed, instead of typing in the date yourself. 6436Or, the "^X Cur Msg" command may be used to fill in 6437the date of the currently highlighted message. 6438<P> 6439There are six possible settings that are selected using the 6440"^W Toggle When" command. 6441Three of them select messages based on the Date headers. 6442They are "SENT SINCE", "SENT BEFORE", 6443and "SENT ON". 6444SINCE is all messages with the selected date or later. 6445BEFORE is all messages earlier than the selected date (not including the day 6446itself). 6447ON is all messages sent on the selected date. 6448The other three select messages in the same way but they use the arrival 6449times of the messages instead of the Date headers included in the messages. 6450Those three are "ARRIVED SINCE", "ARRIVED BEFORE", 6451and "ARRIVED ON". 6452When you save a message from one folder to another the arrival time is 6453preserved. 6454</DD> 6455 6456<DT>select by Text</DT> 6457<DD> Selects messages based on the message contents. 6458This allows you to select a set of messages based on whether or not the 6459message headers or message body contain specified text. 6460You may look for text in the Subject, the From header, 6461the To header, or the Cc header. 6462You may also choose Recipient, which searches for the text in 6463either the To or the Cc header; 6464or Participant, which means To or Cc or From. 6465Besides those specific header searches, you may also search the entire 6466header and text of the message with "All Text", or just the 6467body of the message. 6468<P> 6469To search for the absence of text, first type the "! Not" command 6470before typing the specific type of text search. 6471For example, you could type "!" followed by "S" to 6472search for all messages that do not contain a particular word in their 6473Subjects. 6474<P> 6475If you choose a Subject search, you may use the subject from the current 6476message by typing the "^X Cur Subject" command. 6477You may then edit it further if you wish. 6478For example, you might select the subject of a reply and edit the 6479"Re: " off of the front of it in order to search for 6480the original message being replied to. 6481All of the other header searches allow you to use addresses from the 6482headers of the current message if you want to. 6483You may use the "^T Cur To", "^R Cur From", or 6484"^W Cur Cc". 6485In each case, if there is more than one address, only the first is offered. 6486</DD> 6487 6488<DT>select by Status</DT> 6489<DD> Selects messages based on their status. 6490You may select all New, Important, Deleted, Answered, Recent, or Unseen 6491messages. 6492Or, if you first type the "! Not" command, you get not New, 6493or not Important, and so on. 6494If you select Deleted messages, you will get all messages with their 6495Deleted flag set. 6496Likewise for Important messages, all messages that you have flagged as 6497being Important with the 6498<A HREF="h_common_flag">Flag</A> command. 6499The "New" and "Answered" choices are a little bit odd 6500because they try to match what you see on the screen by default. 6501"New" is a shorthand for messages that are Unseen, Undeleted, 6502and Unanswered. 6503If you have looked at the message, or deleted it, or answered it; then it 6504is not considered "New ". 6505"! New" is the opposite of "New". 6506<P> 6507"Answered" is another one that is a little different. 6508It means that the message has been Answered <EM>and</EM> is not deleted. 6509And to make it even more confusing, "! Answered" is not 6510the opposite of "Answered"! 6511Instead, "! Answered" stands for messages that are 6512both Unanswered <EM>and</EM> not deleted. 6513<P> 6514The other two types were added later because the special nature of the 6515New flag was not what was wanted by all users. 6516New does match what you see in the index by default, but if you use 6517the IMAPSTATUS or SHORTIMAPSTATUS token in the 6518"<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" it may not 6519be exactly what you want. 6520"Unseen" simply selects all unseen messages, whether or not 6521they are deleted or answered, and 6522"Recent" selects all of the messages that have been added to 6523the folder since you started this Alpine session. 6524(That's not technically quite true. If there are multiple mail clients 6525reading an IMAP mailbox, each message will be marked as Recent in only 6526one of the client's sessions.) 6527</DD> 6528 6529<DT>select by siZe</DT> 6530<DD> Selects messages based on their size being smaller than or larger 6531than the size you specify. 6532The size is the number of bytes. 6533You may use the suffix "K" or "k" to mean 1,000 times 6534the number. 6535For example, 7K is the same as 7000. 6536The suffix "M" or "m" means 1,000,000 times the number, 6537and the suffix "G" or "g" means 1,000,000,000 times. 6538Use the "^W" command to toggle back and forth between Smaller 6539and Larger. 6540</DD> 6541 6542<DT>select by Keyword</DT> 6543<DD> Selects messages that either have or do not have 6544(using the "! Not" command) 6545a particular <A HREF="h_config_keywords">Keyword</A> set. 6546One way to select a keyword is to use the "^T To List" 6547command to select one from your list of keywords. 6548The 6549<A HREF="h_config_flag_screen_kw_shortcut"><!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"--></A> option allows selecting by Keyword initials if set. 6550</DD> 6551 6552<DT>select by Rule</DT> 6553<DD> Selects messages that either match or don't match 6554(using the "! Not" command) 6555one of the Rules you have defined. 6556The most likely method of filling in the Rule is to use the 6557"^T To List" 6558command to select one of your Rules. 6559All of the Rules you have defined will be in the list, including 6560Rules for Searching, Indexcolors, Filtering, Roles, Score setting, and Other. 6561They may not all make sense for this purpose, but they are all there for 6562flexibility. 6563You might find it useful to define some rules solely for the purpose 6564of being used by the Select command. 6565There is a special category for such Rules. They are called Search Rules. 6566<P> 6567Unfortunately, Alpine does not allow all possible Rules to be defined. 6568For example, there is no logical OR operation. 6569OR is accomplished in the Filter Rules or the other types of Rules by 6570simply defining two rules, one that matches the first part of the OR 6571and another that matches the second part. 6572But you can't do that here, since you only have a single Rule to work with. 6573Likewise, the order of Rules is usually important. 6574For example, if the first Filter Rule (or Indexcolor rule or ...) matches 6575a message, then that stops the search for a further match. 6576This means that you may be confused if you try to use Select by Rule to 6577check your Filter rules because the order is important when filtering but 6578is not considered here. 6579</DD> 6580 6581<DT>select by tHread</DT> 6582<DD> Selects all of the messages in the current thread. 6583</DD> 6584</DL> 6585 6586After you have an initial selection, the next and subsequent selection 6587commands modify the selection. 6588The select command changes. It first gives 6589you selection "alteration" options: "unselect All", 6590"unselect Current", 6591"Broaden selection" (implements a logical OR), and 6592"Narrow selection" (implements a logical AND). 6593After you choose either Broaden or Narrow, you then choose one of the 6594selection criteria listed above (by Text or Number or ...). 6595You may use select as many times as you wish to get the selected set right. 6596<P> 6597 6598The WhereIs command has a feature (Ctrl-X) to 6599select all the messages that match the WhereIs search. WhereIs searches 6600through just the text that appears on the MESSAGE INDEX screen. 6601This method is often slower than using the select command itself, unless the 6602line you are looking for is not too far away in the index. 6603<P> 6604 6605The availability of the aggregate operations commands is determined by the 6606<A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A> 6607Feature-List option in your Alpine 6608configuration, which defaults to set. 6609The features 6610<A HREF="h_config_auto_zoom">"<!--#echo var="FEAT_auto-zoom-after-select"-->"</A> 6611and 6612<A HREF="h_config_select_wo_confirm">"<!--#echo var="FEAT_select-without-confirm"-->"</A> 6613affect the behavior of the Select command. 6614 6615<P> 6616<End of help on this topic> 6617</BODY> 6618</HTML> 6619======= h_select_rule ======= 6620<HTML> 6621<HEAD> 6622<TITLE>Select: Rule</TITLE> 6623</HEAD> 6624<BODY> 6625<H1>Select: Rule</H1> 6626 6627You are selecting messages that either match or don't match 6628one of the Rules you have defined. 6629You may either type the nickname of the Rule at the prompt, or use the 6630"^T To List" 6631command to select one of your Rules. 6632All of the Rules you have defined will be in the list, including 6633Rules for Indexcolors, Filtering, Roles, Score setting, and Other. 6634They may not all make sense for this purpose, but they are all there for 6635flexibility. 6636Rules may be added by using the Setup/Rules screen off of the main Alpine 6637menu. 6638<P> 6639Unfortunately, Alpine does not allow all possible Rules to be defined. 6640For example, there is no logical OR operation. 6641OR is accomplished in the Filter Rules or the other types of Rules by 6642simply defining two rules, one that matches the first part of the OR 6643and another that matches the second part. 6644But you can't do that here, since you only have a single Rule to work with. 6645Likewise, the order of Rules is usually important. 6646For example, if the first Filter Rule (or Indexcolor rule or ...) matches 6647a message, then that stops the search for a further match. 6648This means that you may be confused if you try to use Select by Rule to 6649check your Filter rules because the order is important when filtering but 6650is not considered here. 6651 6652<P> 6653<End of help on this topic> 6654</BODY> 6655</HTML> 6656======= h_select_text ======= 6657<HTML> 6658<HEAD> 6659<TITLE>Select: Text</TITLE> 6660</HEAD> 6661<BODY> 6662<H1>Select: Text</H1> 6663 6664You are selecting messages based on the contents of the message. 6665This allows you to select a set of messages based on whether or not the 6666message headers or message body contain specified text. 6667You may look for text in the Subject, the From header, 6668the To header, or the Cc header. 6669You may also choose Recipient, which searches for the text in 6670either the To or the Cc header; 6671or Participant, which means either the To header, or the Cc header, 6672or the From header. 6673Besides those specific header searches, you may also search the entire 6674header and text of the message with "All Text", or just the 6675body of the message with "Body". 6676<P> 6677To search for the absence of text, first type the "! Not" command 6678before typing the specific type of text search. 6679For example, you could type "!" followed by "S" to 6680search for all messages that do not contain a particular word in their 6681Subjects. 6682<P> 6683If you choose a Subject search, you may use the subject from the current 6684message by typing the "^X Cur Subject" command. 6685You may then edit it further if you wish. 6686For example, you might select the subject of a reply and edit the 6687"Re: " off of the front of it in order to search for 6688the original message being replied to. 6689All of the other header searches allow you to use addresses from the 6690headers of the current message if you want to. 6691You may use the "^T Cur To", "^R Cur From", or 6692"^W Cur Cc". 6693In each case, if there is more than one address, only the first is offered. 6694 6695<P> 6696<End of help on this topic> 6697</BODY> 6698</HTML> 6699======= h_select_status ======= 6700<HTML> 6701<HEAD> 6702<TITLE>Select: Status</TITLE> 6703</HEAD> 6704<BODY> 6705<H1>Select: Status</H1> 6706 6707You are selecting messages based on the status of the message. 6708For example, whether or not the message has been marked Deleted or Important, 6709or whether or not it has been Answered or is New. 6710If you first type the "! Not" command, you will get the 6711opposite: not Deleted, not Important, and so on. 6712<P> 6713If you select Deleted messages, you will get all messages with their 6714Deleted flag set. 6715Likewise for Important messages, all messages that you have flagged as 6716being Important with the 6717<A HREF="h_common_flag">Flag</A> command. 6718The "New" and "Answered" choices are a little bit odd 6719because they try to match what you see on the screen by default. 6720"New" is a shorthand for messages that are Unseen, Undeleted, 6721and Unanswered. 6722If you have looked at the message, or deleted it, or answered it; then it 6723is not considered "New ". 6724"! New" is the opposite of "New". 6725<P> 6726"Answered" is another one that is a little different. 6727It means that the message has been Answered <EM>and</EM> is not deleted. 6728And to make it even more confusing, "! Answered" is not 6729the opposite of "Answered"! 6730Instead, "! Answered" stands for messages that are 6731both Unanswered <EM>and</EM> not deleted. 6732<P> 6733(The New and Answered options may seem counter-intuitive. 6734The reason it is done this way is 6735because, by default, a Deleted message will show up with the "D" 6736symbol in the MAIL INDEX screen even if it is New or Answered. 6737The Delete symbol overrides the New and Answered symbols, because you 6738usually don't care about the message anymore once you've deleted it. 6739Similarly, you usually only care about whether a message is Answered or 6740not if it is not Deleted. 6741Once it is Deleted you've put it out of your mind.) 6742<P> 6743The other two options were added later because the special nature of the 6744New flag was not what was wanted by all users. 6745New does match what you see in the index by default, but if you use 6746the IMAPSTATUS or SHORTIMAPSTATUS token in the 6747"<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" it may not 6748be exactly what you expect. 6749"Unseen" simply selects all unseen messages, whether or not 6750they are deleted or answered, and 6751"Recent" selects all of the messages that have been added to 6752the folder since you started this Alpine session. 6753(That's not technically quite true. If there are multiple mail clients 6754reading an IMAP mailbox, each message will be marked as Recent in only 6755one of the client's sessions. 6756That behavior can be convenienent for some purposes, like filtering, but 6757it isn't usually what you expect when selecting.) 6758 6759<P> 6760<End of help on this topic> 6761</BODY> 6762</HTML> 6763======= h_index_cmd_apply ======= 6764<HTML> 6765<HEAD> 6766<TITLE>Apply Command</TITLE> 6767</HEAD> 6768<BODY> 6769<H1>Apply Command</H1> 6770 6771Apply 6772(<!--chtml if pinemode="function_key"-->F6<!--chtml else-->A<!--chtml endif-->) 6773is the second step of most aggregate operations. Apply 6774becomes active any time there is a defined set of selected messages. The 6775following commands can be applied to a selected message set: delete, 6776undelete, reply, forward, 6777<!--chtml if pinemode="os_windows"--> 6778<!--chtml else--> 6779pipe, 6780<!--chtml endif--> 6781print, take address, save, export, bounce, and flag. 6782<P> 6783 6784The behavior of some of these commands in an aggregate sense is not easy to 6785explain. Try them out to see what they do. 6786The feature 6787<A HREF="h_config_auto_unzoom">"<!--#echo var="FEAT_auto-unzoom-after-apply"-->"</A> 6788affects the behavior of the Apply command, as does the feature 6789<A HREF="h_config_auto_unselect">"<!--#echo var="FEAT_auto-unselect-after-apply"-->"</A>. 6790 6791<P> 6792<End of help on this topic> 6793</BODY> 6794</HTML> 6795======= h_index_cmd_zoom ======= 6796<HTML> 6797<HEAD> 6798<TITLE>ZoomMode Command</TITLE> 6799</HEAD> 6800<BODY> 6801<H1>ZoomMode Command</H1> 6802 6803Another action you might want to take on a set of selected messages is to 6804zoom in on them. Like apply, zoom only becomes active when messages have 6805been selected. 6806ZoomMode 6807(<!--chtml if pinemode="function_key"-->F3<!--chtml else-->Z<!--chtml endif-->) 6808is a toggle command that allows you to 6809zoom-in (and only see the selected messages) and zoom-out (to see all 6810messages in the folder). Neither apply nor zoom removes the markings that 6811define the selected set; you need to use a select command in order 6812to do that. 6813 6814<P> 6815<End of help on this topic> 6816</BODY> 6817</HTML> 6818======= h_index_collapse_expand ======= 6819<HTML> 6820<HEAD> 6821<TITLE>Collapse/Expand Command</TITLE> 6822</HEAD> 6823<BODY> 6824<H1>Collapse/Expand Command</H1> 6825 6826The Collapse/Expand command is only available from the MESSAGE INDEX screen when 6827the folder is sorted by either Threads or OrderedSubject, and the 6828<A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A> 6829is set to something other than "none". 6830By default, this command collapses or expands the subthread that starts at 6831the currently highlighted message, if any. 6832If the subthread is already collapsed, then this command expands it. 6833If the subthread is expanded, then this command collapses it. 6834If there are no more messages below the current message in the 6835thread tree (that is, there are no replies to the current message) then 6836this command does nothing. 6837 6838<P> 6839The behavior of this command is affected by the option 6840<A HREF="h_config_slash_coll_entire">"<!--#echo var="FEAT_slash-collapses-entire-thread"-->"</A>. 6841Normally, this command Collapses or Expands the subthread that 6842starts at the currently highlighted message. 6843If the above option is set, then this command Collapses or Expands the 6844entire current thread instead of just the subthread. 6845The current thread is simply the top-level thread that contains the 6846current message. 6847 6848<P> 6849<End of help on this topic> 6850</BODY> 6851</HTML> 6852======= h_index_cmd_sort ======= 6853<HTML> 6854<HEAD> 6855<TITLE>Sort Command</TITLE> 6856</HEAD> 6857<BODY> 6858<H1>Sort Command</H1> 6859 6860In Alpine's generic configuration, messages are presented in the order in 6861which they arrive. This default can be changed in the SETUP CONFIGURATION 6862with the "<A HREF="h_config_sort_key"><!--#echo var="VAR_sort-key"--></A>" option. 6863You can also re-sort the folder on demand with the sort 6864(<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->) 6865command. 6866Your sorting options are: 6867<P> 6868<UL> 6869 <LI> <A HREF="h_index_sort_arrival">A</A>rrival 6870 <LI> <A HREF="h_index_sort_date">D</A>ate 6871 <LI> <A HREF="h_index_sort_subj">S</A>ubject 6872 <LI> <A HREF="h_index_sort_ordsubj">O</A>rderedSubject 6873 <LI> t<A HREF="h_index_sort_thread">H</A>read 6874 <LI> <A HREF="h_index_sort_from">F</A>rom 6875 <LI> si<A HREF="h_index_sort_size">Z</A>e 6876 <LI> scor<A HREF="h_index_sort_score">E</A>, 6877 <LI> <A HREF="h_index_sort_to">T</A>o 6878 <LI> <A HREF="h_index_sort_cc">C</A>c 6879</UL> 6880 6881<P> 6882The Reverse option will toggle the order the index is currently 6883sorted by, but will not change the relative sort order. 6884 6885<P> 6886Sorting a folder does not actually rearrange the way the folder is saved, 6887it just re-arranges how the messages are presented to you. This means 6888that Alpine has to do the work of sorting every time you change sort order. 6889Sometimes, especially with PC-Alpine or with large folders, this could take 6890a while. 6891 6892<P> 6893<End of help on this topic> 6894</BODY> 6895</HTML> 6896======= h_index_sort_default ======= 6897<HTML> 6898<HEAD> 6899<TITLE>SORT OPTION: Default</TITLE> 6900</HEAD> 6901<BODY> 6902<H1>SORT OPTION: Default</H1> 6903 6904The <EM>Default</EM> sort option just means to use the default sort order 6905set in the 6906<li><a href="h_config_sort_key"><!--#echo var="VAR_sort-key"--></a> 6907option in Setup/Config. 6908 6909<P> 6910<End of help on this topic> 6911</BODY> 6912</HTML> 6913======= h_index_sort_arrival ======= 6914<HTML> 6915<HEAD> 6916<TITLE>SORT OPTION: Arrival</TITLE> 6917</HEAD> 6918<BODY> 6919<H1>SORT OPTION: Arrival</H1> 6920 6921The <EM>Arrival</EM> sort option arranges messages in the MESSAGE INDEX 6922in the order that they exist in the folder. This is usually the same as the 6923order in which they arrived. This option is comparable to not sorting 6924the messages at all. 6925 6926<P> 6927<End of help on this topic> 6928</BODY> 6929</HTML> 6930======= h_index_sort_date ======= 6931<HTML> 6932<HEAD> 6933<TITLE>SORT OPTION: Date</TITLE> 6934</HEAD> 6935<BODY> 6936<H1>SORT OPTION: Date</H1> 6937 6938The <EM>Date</EM> sort option arranges messages in the MESSAGE INDEX 6939according to the date and time they were 6940sent. 6941 6942<P> 6943On a folder like INBOX, sorting by "Date" should be almost 6944identical to sorting by "Arrival". 6945 6946<P> 6947<End of help on this topic> 6948</BODY> 6949</HTML> 6950======= h_index_sort_subj ======= 6951<HTML> 6952<HEAD> 6953<TITLE>SORT OPTION: Subject</TITLE> 6954</HEAD> 6955<BODY> 6956<H1>SORT OPTION: Subject</H1> 6957 6958The <EM>Subject</EM> sort option arranges messages in the MESSAGE INDEX 6959by subject. 6960 6961<P> 6962Messages with the same subject are 6963first grouped together, and then the groups of like-subject messages 6964are arranged alphabetically. 6965 6966<P> 6967Alpine ignores leading "Re:" and 6968"re:" and trailing "(fwd)" when determining the 6969likeness and alphabetical order of subject lines. 6970 6971<P> 6972<End of help on this topic> 6973</BODY> 6974</HTML> 6975======= h_index_sort_ordsubj ======= 6976<HTML> 6977<HEAD> 6978<TITLE>SORT OPTION: OrderedSubject</TITLE> 6979</HEAD> 6980<BODY> 6981<H1>SORT OPTION: OrderedSubject</H1> 6982 6983The <EM>OrderedSubject</EM> sort option arranges messages in the 6984MESSAGE INDEX by grouping all messages with the same subject 6985together, similar to sort by <A HREF="h_index_sort_subj">S</A>ubject. 6986 6987<P> 6988However, <EM>OrderedSubj</EM> then arranges the groups of like-subject 6989messages by the date of the oldest message in the group. 6990 6991<P> 6992This sort method provides for pseudo threading of conversations within 6993a folder. 6994You may want to try sorting by Thread instead. 6995 6996<P> 6997<End of help on this topic> 6998</BODY> 6999</HTML> 7000======= h_index_sort_thread ======= 7001<HTML> 7002<HEAD> 7003<TITLE>SORT OPTION: Thread</TITLE> 7004</HEAD> 7005<BODY> 7006<H1>SORT OPTION: Thread</H1> 7007 7008The <EM>Thread</EM> sort option arranges messages in the 7009MESSAGE INDEX by grouping all messages that indicate 7010they are part of a conversation (discussion thread) taking 7011place within a mailbox or newsgroup. This indication is 7012based on information in the message's header -- specifically 7013its <tt>References:</tt>, <tt>Message-ID:</tt>, and <tt>Subject:</tt> fields. 7014 7015<P> 7016<End of help on this topic> 7017</BODY> 7018</HTML> 7019======= h_index_sort_from ======= 7020<HTML> 7021<HEAD> 7022<TITLE>SORT OPTION: From</TITLE> 7023</HEAD> 7024<BODY> 7025<H1>SORT OPTION: From</H1> 7026 7027The <EM>From</EM> sort option arranges messages in the MESSAGE INDEX 7028by the name of the author of the message. 7029 7030<P> 7031Messages with the same author are grouped together. Groups of 7032messages are then put into alphabetical order according to message 7033author. 7034 7035<P> 7036<End of help on this topic> 7037</BODY> 7038</HTML> 7039======= h_index_sort_size ======= 7040<HTML> 7041<HEAD> 7042<TITLE>SORT OPTION: Size</TITLE> 7043</HEAD> 7044<BODY> 7045<H1>SORT OPTION: Size</H1> 7046 7047The <EM>Size</EM> sort option arranges messages in the MESSAGE INDEX 7048by their relative sizes. 7049 7050<P> 7051<End of help on this topic> 7052</BODY> 7053</HTML> 7054======= h_index_sort_score ======= 7055<HTML> 7056<HEAD> 7057<TITLE>SORT OPTION: Score</TITLE> 7058</HEAD> 7059<BODY> 7060<H1>SORT OPTION: Score</H1> 7061 7062The <EM>Score</EM> sort option arranges messages in the MESSAGE INDEX 7063by their scores. 7064 7065<P> 7066Messages with the same score are sorted in arrival order. 7067Scores are something you create using the 7068<A HREF="h_rules_score">"SETUP SCORING"</A> screen. 7069 7070<P> 7071<End of help on this topic> 7072</BODY> 7073</HTML> 7074======= h_index_sort_to ======= 7075<HTML> 7076<HEAD> 7077<TITLE>SORT OPTION: To</TITLE> 7078</HEAD> 7079<BODY> 7080<H1>SORT OPTION: To</H1> 7081 7082The <EM>To</EM> sort option arranges messages in the MESSAGE INDEX 7083by the names of the recipients of the message. 7084 7085<P> 7086Messages with the same recipients are grouped together. Groups of 7087messages are then put into alphabetical order according to message 7088recipients. 7089 7090<P> 7091<End of help on this topic> 7092</BODY> 7093</HTML> 7094======= h_index_sort_cc ======= 7095<HTML> 7096<HEAD> 7097<TITLE>SORT OPTION: Cc</TITLE> 7098</HEAD> 7099<BODY> 7100<H1>SORT OPTION: Cc</H1> 7101 7102The <EM>Cc</EM> sort option arranges messages in the MESSAGE INDEX by 7103the names of the carbon copy addresses of the message. 7104 7105<P> 7106<End of help on this topic> 7107</BODY> 7108</HTML> 7109======= h_index_cmd_whereis ======= 7110<HTML> 7111<HEAD> 7112<TITLE>WhereIs Command</TITLE> 7113</HEAD> 7114<BODY> 7115<H1>WhereIs Command</H1> 7116 7117The WhereIs 7118(<!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->) 7119command lets you search the MESSAGE INDEX for a word. 7120It scans through whatever you see, usually the name of the author 7121and the Subject line. 7122WhereIs has special subcommands to let you find the beginning of the 7123index (Ctrl-Y -- first message) 7124or the end of the index (Ctrl-V -- last message). 7125<P> 7126Note that WhereIs only searches through the visible text on the screen. 7127For example, if only part of the Subject of a message is shown because it 7128is long, then only the visible portion of the Subject is searched. 7129Also note that WhereIs does not "see" the 7130"X" in column one of Index entries for selected messages 7131so it can't be used to search for 7132selected messages (use "Zoom" instead). 7133<P> 7134If the feature 7135<A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A> 7136is turned on, 7137WhereIs can also be used as a quick way to select messages that match the 7138string being searched for. 7139Instead of typing carriage return to search for the next match, type 7140Ctrl-X to select all matches. 7141Once again, this only selects matches that are (or would be if the right 7142index line was on the screen) visible. 7143Truncated From lines or Subjects will cause matches to be missed. 7144Although WhereIs is sometimes convenient for quick matching, the Select 7145command is usually more powerful and usually faster. 7146 7147<P> 7148<End of help on this topic> 7149</BODY> 7150</HTML> 7151======= h_view_cmd_whereis ======= 7152<HTML> 7153<HEAD> 7154<TITLE>WhereIs Command</TITLE> 7155</HEAD> 7156<BODY> 7157<H1>WhereIs Command</H1> 7158 7159The WhereIs 7160(<!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->) 7161command does a "find in current message" operation. You 7162type in text and Alpine will try to find it in the message you are 7163reading. WhereIs also has subcommands to jump to the beginning (Ctrl-Y) 7164or end (Ctrl-V) of the message. 7165That is, to rapidly move to the end of a message, hit the 7166<!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif--> 7167(or Ctrl-W) key followed 7168by Ctrl-V. Similarly, 7169<!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif--> 7170followed by Ctrl-Y will take you to the beginning of a message. 7171 7172<P> 7173<End of help on this topic> 7174</BODY> 7175</HTML> 7176======= h_view_cmd_hilite ======= 7177<HTML> 7178<HEAD> 7179<TITLE>View Hilite and Next item/Previous item</TITLE> 7180</HEAD> 7181<BODY> 7182<H1>View Hilite and Next item/Previous item</H1> 7183 7184Sometimes messages may be in the form of formatted HTML text 7185or they may contain URLs or Web server hostnames. 7186When any of the features 7187<A HREF="h_config_enable_view_url">"<!--#echo var="FEAT_enable-msg-view-urls"-->"</A>, 7188<A HREF="h_config_enable_view_web_host">"<!--#echo var="FEAT_enable-msg-view-web-hostnames"-->"</A>, 7189<A HREF="h_config_enable_view_attach">"<!--#echo var="FEAT_enable-msg-view-attachments"-->"</A>, 7190or 7191<A HREF="h_config_enable_view_addresses">"<!--#echo var="FEAT_enable-msg-view-addresses"-->"</A> 7192are enabled, Alpine will represent such selectable items in the text 7193in bold typeface. One of the selectable items will be displayed in 7194inverse video (highlighted). This is the "currently selected" item. 7195Press the Return key to view the currently selected item. 7196<P> 7197 7198The Up and Down Arrows keys can be used to change the selected item 7199(also see the feature 7200<A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>). 7201If there are no selectable items in the direction of the arrow you 7202pressed, Alpine will scroll the display in that direction until one 7203becomes visible. To "jump" forwards/backwards among selectable 7204items in the message text, use the Previous and Next item commands, 7205<!--chtml if pinemode="function_key"-->F5 and F6 7206<!--chtml else-->^B and ^F<!--chtml endif-->. 7207 7208<P> 7209<End of help on this topic> 7210</BODY> 7211</HTML> 7212======= h_view_cmd_viewattch ======= 7213<HTML> 7214<HEAD> 7215<TITLE>ViewAttch Command</TITLE> 7216</HEAD> 7217<BODY> 7218<H1>ViewAttch Command</H1> 7219 7220 7221The View/Save Attachment 7222(<!--chtml if pinemode="function_key"-->F4<!--chtml else-->V<!--chtml endif-->) 7223command allows you to handle MIME attachments to a message you have 7224received. Alpine shows you a list of the message attachments -- you just 7225choose the attachment you want. You may either view or save the 7226selected attachment. 7227 7228<P> 7229Because many attachments require external programs for display, there 7230is some system configuration that has to happen before you can 7231actually display attachments. Hopefully much of that will have been 7232done already by your system administrator. MIME configuration is 7233handled with the "mailcap" configuration file. (See the section 7234on configuration in the 7235<A HREF="h_news">release notes</A> for more information.) 7236 7237<P> 7238<End of help on this topic> 7239</BODY> 7240</HTML> 7241======= h_index_cmd_expunge ======= 7242<HTML> 7243<HEAD> 7244<TITLE>Expunge/Exclude Command</TITLE> 7245</HEAD> 7246<BODY> 7247<H1>Expunge/Exclude Command</H1> 7248 7249Expunge/Exclude 7250(<!--chtml if pinemode="function_key"-->F3<!--chtml else-->X<!--chtml endif-->) 7251is the command Alpine uses to actually remove all messages 7252marked for deletion. With regular email files, expunge literally deletes 7253the text from the current folder. With newsgroups or shared mailboxes, 7254you don't have permission to actually remove the message, so it is an 7255exclude -- Alpine removes the message from your view of the folder even 7256though it is not technically gone. 7257 7258<P> A selective expunge command is available in IMAP folders that support 7259the UID EXPUNGE extension in <A 7260HREF="http://tools.ietf.org/html/rfc4315">RFC 4315</A> as well as for all 7261other folders (local folders in all formats, POP3 inbox, and newsgroups) 7262as a subcommand of the apply command. If some selected messages are marked 7263deleted, then the apply command will offer the eXpunge command, which when 7264executed will only expunge those messages that are selected and deleted. 7265 7266<P> 7267Observe that the expunge command (when not used from the apply command) 7268will expunge/exclude all deleted messages from the folder, and so all 7269messages marked deleted will be expunged, regardless of if they are 7270selected or not. In other words, there is no protection against 7271potentially expunging more messages than only those that have been 7272selected and deleted. 7273<P> 7274 7275The configuration features 7276<A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A> 7277and 7278<A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A> 7279affect the behavior of the Expunge command. 7280 7281<P> 7282<End of help on this topic> 7283</BODY> 7284</HTML> 7285======= h_common_compose ======= 7286<HTML> 7287<HEAD> 7288<TITLE>Compose Command</TITLE> 7289</HEAD> 7290<BODY> 7291<H1>Compose Command</H1> 7292 7293The Compose command takes you into the Alpine message composer where you 7294can start a new message for sending. This is where you type in the 7295message's text and specify its recipient list (the "To:" 7296address), where copies should be directed (e.g., "Fcc", 7297"Cc:" or "Bcc:"), and which files, if any, should 7298be attached to the message. 7299 7300<P> 7301When you type this command, Alpine will also automatically check for any 7302interrupted (i.e., a message that was being composed when your modem 7303or network connection was broken) or previously postponed messages and 7304offer you a chance to continue working on those. 7305 7306<P> 7307<UL> 7308<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 7309</UL><P> 7310<End of help on this topic> 7311</BODY> 7312</HTML> 7313======= h_common_index ======= 7314<HTML> 7315<HEAD> 7316<TITLE>Message Index Command</TITLE> 7317</HEAD> 7318<BODY> 7319<H1>Message Index Command</H1> 7320 7321The Index command takes you to the MESSAGE INDEX screen that displays a 7322summary caption for each message in the currently-open folder. One 7323message will be highlighted; this is the "Current" message. 7324The message commands available from this screen (e.g. View, Reply, 7325Forward, Delete, Print, Save, etc) apply to the current message. 7326 7327<P> 7328<End of help on this topic> 7329</BODY> 7330</HTML> 7331======= h_common_folders ======= 7332<HTML> 7333<HEAD> 7334<TITLE>Folder List Command</TITLE> 7335</HEAD> 7336<BODY> 7337<H1>Folder List Command</H1> 7338 7339This Folder List command takes you to the FOLDER LIST screen that displays 7340the names of all your message folders and allows you to view, rename, 7341delete, and add folders. You can open (view) a different folder than the 7342one currently open by highlighting the desired one (using the arrow keys 7343or their control-key equivalents) and pressing RETURN. 7344 7345<P> 7346If you have multiple folder collections defined (see the Help text for 7347the FOLDER LIST screen to learn more about Collections), you may need 7348to press Return to expand the collection and display all of the 7349folders in it. 7350 7351<P> 7352<End of help on this topic> 7353</BODY> 7354</HTML> 7355======= h_main_addrbook ======= 7356<HTML> 7357<HEAD> 7358<TITLE>Address Book Command</TITLE> 7359</HEAD> 7360<BODY> 7361<H1>Address Book Command</H1> 7362 7363This command, available only from the MAIN MENU, takes you 7364to the ADDRESS BOOK management screen. From here, your personal address 7365book(s) may be updated. 7366 7367<P> 7368<End of help on this topic> 7369</BODY> 7370</HTML> 7371======= h_main_setup ======= 7372<HTML> 7373<HEAD> 7374<TITLE>Setup Command</TITLE> 7375</HEAD> 7376<BODY> 7377<H1>Setup Command</H1> 7378 7379The Setup command, available only from the MAIN MENU, prompts you for 7380one of several configuration screens, including the SETUP CONFIGURATION 7381screen, by which you may activate optional Alpine features. 7382 7383<P> 7384<End of help on this topic> 7385</BODY> 7386</HTML> 7387======= h_main_release_notes ======= 7388<HTML> 7389<HEAD> 7390<TITLE>Release Notes Command</TITLE> 7391</HEAD> 7392<BODY> 7393<H1>Release Notes Command</H1> 7394 7395This command displays information about Alpine <!--#echo var="ALPINE_VERSION"-->, 7396as well as pointers to further information such as history and legal notes. 7397 7398<P> 7399<End of help on this topic> 7400</BODY> 7401</HTML> 7402======= h_main_kblock ======= 7403<HTML> 7404<HEAD> 7405<TITLE>Keyboard Lock Command</TITLE> 7406</HEAD> 7407<BODY> 7408<H1>Keyboard Lock Command</H1> 7409 7410This command allows your Alpine session to be protected 7411during a temporary absence from your terminal. 7412 7413<P> 7414<End of help on this topic> 7415</BODY> 7416</HTML> 7417======= h_main_journal ======= 7418<HTML> 7419<HEAD> 7420<TITLE>Journal Command</TITLE> 7421</HEAD> 7422<BODY> 7423<H1>Journal Command</H1> 7424 7425This command displays a list of all the status messages Alpine has 7426displayed (on the third line from the bottom of the screen). This may 7427be useful if a message disappeared before you had a chance to read it. 7428 7429<P> 7430<End of help on this topic> 7431</BODY> 7432</HTML> 7433======= h_common_role ======= 7434<HTML> 7435<HEAD> 7436<TITLE>Role Command</TITLE> 7437</HEAD> 7438<BODY> 7439<H1>Role Command</H1> 7440 7441The Role command is similar to the Compose command except that it starts 7442off by letting you select a <A HREF="h_rules_roles">role</A> 7443to be used for the composition. 7444You may set up alternate roles by using Setup/Rules/Roles. 7445 7446<P> 7447<End of help on this topic> 7448</BODY> 7449</HTML> 7450======= h_common_conditional_cmds ======= 7451<HTML> 7452<HEAD> 7453<TITLE>Conditional Commands</TITLE> 7454</HEAD> 7455<BODY> 7456<H1>Conditional Commands</H1> 7457 7458The presence or absence of certain commands, particularly in the 7459MESSAGE INDEX and MESSAGE TEXT screens, is determined by 7460whether or not specific features are set in your Alpine configuration. 7461(You can access the SETUP CONFIGURATION screen, where they are found, from 7462Alpine's MAIN MENU.) To see if a desired command's availability is 7463conditioned on a feature setting, see the command's help text (highlight 7464the phrase associated with the command and hit Return). 7465 7466<P> 7467Also note that some 7468commands may be administratively disabled by your system manager; 7469if they don't work, please check with your local help desk. 7470 7471<P> 7472<UL> 7473<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 7474</UL><P> 7475<End of help on this topic> 7476</BODY> 7477</HTML> 7478======= h_common_pipe ======= 7479<HTML> 7480<HEAD> 7481<TITLE>Pipe Command</TITLE> 7482</HEAD> 7483<BODY> 7484<H1>Pipe Command</H1> 7485 7486Pipe 7487(<!--chtml if pinemode="function_key"-->F12<!--chtml else-->|<!--chtml endif-->) 7488allows you to send a message to a specified Unix command for external 7489processing. 7490This command's availability is controlled by the 7491<A HREF="h_config_enable_pipe">"<!--#echo var="FEAT_enable-unix-pipe-cmd"-->"</A> 7492feature. 7493By default, the processed text of the message is sent to the command 7494you specify and the output is captured by Alpine and shown to you. 7495When you run the pipe command, there are some sub-commands which may be 7496used to alter this behavior. 7497These sub-commands are described <A HREF="h_pipe_command">here</A>. 7498 7499<P> 7500<End of help on this topic> 7501</BODY> 7502</HTML> 7503======= h_common_goto ======= 7504<HTML> 7505<HEAD> 7506<TITLE>Goto Command</TITLE> 7507</HEAD> 7508<BODY> 7509<H1>Goto Command</H1> 7510 7511Goto 7512(<!--chtml if pinemode="function_key"-->F6<!--chtml else-->G<!--chtml endif-->) 7513is the command that lets you bypass Alpine's folder selection screens 7514and jump directly to a new folder. You can select any folder in the 7515world: one in your current collection, one in a different collection or 7516one in a collection you've never even used before. 7517<P> 7518 7519Alpine will help you as much as possible to narrow in on the folder you want. 7520However, if the folder is outside of your defined collections, you are 7521going to have to enter the exact folder location using the correct 7522<A HREF="h_valid_folder_names">syntax</A> 7523for a remote folder and/or fully-qualified path name. 7524 7525<P> 7526<End of help on this topic> 7527</BODY> 7528</HTML> 7529======= h_common_nextnew ======= 7530<HTML> 7531<HEAD> 7532<TITLE>NextNew Command</TITLE> 7533</HEAD> 7534<BODY> 7535<H1>NextNew Command</H1> 7536 7537When you press the TAB key, Alpine advances to the next 7538"interesting" message. 7539This will be the next message you have not seen before, or the next message 7540you have flagged Important, whichever comes first. 7541Unread messages that have been deleted are not considered interesting. 7542(A note about reading news. Alpine expects you to "Delete" news 7543articles after you have read them if you want to remove them from future 7544consideration. See <A HREF="h_mainhelp_readingnews">Reading News</A> for 7545more information.) 7546 7547<P> 7548The NextNew command is affected by the feature 7549<A HREF="h_config_tab_new_only">"<!--#echo var="FEAT_tab-visits-next-new-message-only"-->"</A>, 7550which causes Alpine to only consider Unread messages interesting, not messages 7551flagged Important. 7552 7553<P> 7554This command behaves a little differently when it finds there are no more 7555interesting messages left in the current folder. 7556If the current folder is one of your Incoming Message Folders 7557(<A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>) 7558or it is a newsgroup, then Alpine will try to find the next folder or 7559newsgroup that contains <EM>Recent</EM> messages and will ask you 7560if you want to open that folder. 7561This behavior may be modified by using the 7562<A HREF="h_config_tab_uses_unseen">"<!--#echo var="FEAT_tab-uses-unseen-for-next-folder"-->"</A> 7563feature that causes Alpine to look for Unseen messages instead of Recent 7564messages. 7565The NextNew command's behavior is also affected by the configuration features 7566<A HREF="h_config_auto_open_unread">"<!--#echo var="FEAT_auto-open-next-unread"-->"</A>, 7567and 7568<A HREF="h_config_tab_no_prompt">"<!--#echo var="FEAT_continue-tab-without-confirm"-->"</A>. 7569 7570<P> 7571<End of help on this topic> 7572</BODY> 7573</HTML> 7574======= h_common_jump ======= 7575<HTML> 7576<HEAD> 7577<TITLE>Jump Command</TITLE> 7578</HEAD> 7579<BODY> 7580<H1>Jump Command</H1> 7581 7582This is Alpine's way of allowing you to go straight to a specific message. 7583Just press "J" and then enter the message number. By default, Alpine is also 7584configured such that typing in any number automatically jumps you to that 7585message 7586(<A HREF="h_config_enable_jump">"<!--#echo var="FEAT_enable-jump-shortcut"-->"</A> 7587in the SETUP CONFIGURATION). 7588 7589<P> 7590<End of help on this topic> 7591</BODY> 7592</HTML> 7593======= h_common_flag ======= 7594<HTML> 7595<HEAD> 7596<TITLE>Flag Command</TITLE> 7597</HEAD> 7598<BODY> 7599<H1>Flag Command</H1> 7600 7601Flag 7602(<!--chtml if pinemode="function_key"-->F11<!--chtml else-->*<!--chtml endif-->) 7603is the command that allows users to manipulate the status flags that 7604appear on the left side of the MESSAGE INDEX screen. The most common 7605use of this is to mark a message as important. This is something of a 7606note to yourself to get back to that message. You may also use the 7607flag command to set (or unset) the flags that indicate that a message 7608is new, answered, deleted, or forwarded.<P> 7609 7610Provided the mail server supports it, 7611you may also manipulate user-defined keywords 7612for a message using the flag command. 7613These keywords will be available if you use the Flag Details screen that you 7614can get to after typing the 7615Flag (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->*<!--chtml endif-->) 7616command. 7617They will be listed after the Important, New, Answered, Deleted , and Forwarded flags, 7618which are always present. 7619You may add new keywords by using the Add KW command from the Flag Details screen 7620or by defining them in the <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen. 7621 7622The availability of the flag command is determined by the 7623<A HREF="h_config_enable_flag">"<!--#echo var="FEAT_enable-flag-cmd"-->"</A> 7624feature in your Alpine configuration. Also, it is possible that Flag could be 7625administratively disabled by your system manager; if it doesn't work, 7626please check with your local help desk before reporting a bug. 7627The behavior of the flag command may be modified by the 7628<A HREF="h_config_flag_screen_default">"<!--#echo var="FEAT_enable-flag-screen-implicitly"-->"</A> option or the 7629<A HREF="h_config_flag_screen_kw_shortcut">"<!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"-->"</A> option. 7630 7631<P> 7632<End of help on this topic> 7633</BODY> 7634</HTML> 7635======= h_common_hdrmode ======= 7636<HTML> 7637<HEAD> 7638<TITLE>HdrMode Command</TITLE> 7639</HEAD> 7640<BODY> 7641<H1>HdrMode Command</H1> 7642 7643Every email message comes with some header lines that you normally 7644don't see (and don't want to see). 7645These include anywhere from 3-20 lines (or more) added by the 7646Internet mail transport system to record the route your message took, 7647for diagnostic purposes. 7648These are normally of no import and simply 7649add clutter, so Alpine suppresses them in the MESSAGE TEXT display. 7650This also includes other non-standard headers the message may contain. 7651If you want to see these headers, there is a way to reveal them. 7652<P> 7653 7654The Header Mode 7655(<!--chtml if pinemode="function_key"-->F9<!--chtml else-->H<!--chtml endif-->) 7656command is a toggle that controls Alpine's handling of these header 7657lines. Normally, full headers is "off" and you only see a 7658few lines about who a message is to and who it is from. When you 7659press 7660(<!--chtml if pinemode="function_key"-->F9<!--chtml else-->H<!--chtml endif-->) 7661to turn full headers on, Alpine will show you 7662the normal header lines as well as delivery headers, comment headers, 7663MIME headers, and any other headers present. 7664<P> 7665 7666Several different Alpine commands honor the header mode -- it affects how 7667messages are displayed, how they appear in forward and reply email, how 7668they are printed, how they are saved, and how they are exported. 7669<!--chtml if pinemode="os_windows"--> 7670<!--chtml else--> 7671The pipe command is also affected. 7672<!--chtml endif--> 7673<P> 7674 7675The presence or absence of the Header Mode command is determined by the 7676<A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A> 7677Feature-List option in your Alpine configuration. 7678 7679<P> 7680If you have also turned on the 7681<A HREF="h_config_quote_suppression">"Quote Suppression"</A> 7682option then the HdrMode command actually rotates through three states 7683instead of just two. 7684The first is the normal view with long quotes suppressed. 7685The second is the normal view but with the long quotes included. 7686The last enables the display of all headers in the message. 7687When using Export, Pipe, Print, Forward, or Reply the quotes are 7688never suppressed, so the first two states are identical. 7689 7690<P> 7691The behavior of the Header Mode command may be altered slightly by 7692turning on the 7693<A HREF="h_config_quell_full_hdr_reset">"<!--#echo var="FEAT_quell-full-header-auto-reset"-->"</A> 7694Feature-List option in your Alpine configuration. 7695In particular, it will cause the Header Mode to be persistent when moving 7696from message to message instead of resetting to the default for each message. 7697 7698<P> 7699<UL> 7700<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 7701</UL><P> 7702<End of help on this topic> 7703</BODY> 7704</HTML> 7705======= h_common_print ======= 7706<HTML> 7707<HEAD> 7708<TITLE>Print Command</TITLE> 7709</HEAD> 7710<BODY> 7711<H1>Print Command</H1> 7712 7713The Print 7714(<!--chtml if pinemode="function_key"-->F9<!--chtml else-->%<!--chtml endif-->) 7715command allows you to print a copy of a message. 7716There are many SETUP CONFIGURATION features that affect the 7717Print command, including 7718<A HREF="h_config_enable_y_print">"<!--#echo var="FEAT_enable-print-via-y-command"-->"</A>, 7719<A HREF="h_config_print_index">"<!--#echo var="FEAT_print-index-enabled"-->"</A>, 7720<A HREF="h_config_custom_print">"<!--#echo var="FEAT_print-offers-custom-cmd-prompt"-->"</A>, 7721<A HREF="h_config_print_from">"<!--#echo var="FEAT_print-includes-from-line"-->"</A>, and 7722<A HREF="h_config_ff_between_msgs">"<!--#echo var="FEAT_print-formfeed-between-messages"-->"</A>. 7723You set up for printing by using the Printer option of the Setup command 7724on the MAIN MENU. 7725<P> 7726 7727<P> 7728<End of help on this topic> 7729</BODY> 7730</HTML> 7731======= h_common_take ======= 7732<HTML> 7733<HEAD> 7734<TITLE>TakeAddr Command</TITLE> 7735</HEAD> 7736<BODY> 7737<H1>TakeAddr Command</H1> 7738 7739 7740With the Take Address 7741(<!--chtml if pinemode="function_key"-->F10<!--chtml else-->T<!--chtml endif-->) 7742command, you can extract email addresses from an 7743incoming message and save them in an address book. This is an easy way 7744to add to your address book and avoid having to remember the email 7745addresses of the people who write to you. 7746<P> 7747 7748If the message is just to you individually, then you will only need to 7749provide a nickname. If the message contains more than one email address, 7750then you will see an address 7751selection screen that lets you choose the address you want to save into 7752your address book, or lets you choose several of them add to a 7753personal distribution list. 7754<P> 7755 7756Once you've added an entry to your address book, you can use it from the 7757message composer by typing the nickname of the entry into one of the 7758header fields (for example, into the To: field), or you can use ^T from 7759the header field to select the entry from your address book. 7760<P> 7761 7762If the configuration feature 7763<A HREF="h_config_enable_role_take">"<!--#echo var="FEAT_enable-rules-under-take"-->"</A> 7764is set, the behavior of the Take command is altered slightly. 7765 7766<P> 7767<End of help on this topic> 7768</BODY> 7769</HTML> 7770======= h_ge_import ======= 7771<HTML> 7772<HEAD> 7773<TITLE>Import File Selection</TITLE> 7774</HEAD> 7775<BODY> 7776<H1>Import File Selection</H1> 7777 7778You are importing a file that you previously 7779exported from Alpine. 7780You are now being asked for the name of that file. 7781The easiest way to select a file is probably with the "^T" 7782"To Files" command. 7783Alternatively, you may type in a file name. 7784It may be an absolute pathname. 7785Otherwise, it is a file located in your home directory 7786or current working directory 7787<!--chtml if pinemode="running"--> 7788(which, at least for your current Alpine "session," 7789is "<!--#echo var="CURRENT_DIR"-->") 7790<!--chtml endif-->, depending on the 7791<A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> option. 7792In any case, you finish by typing a carriage return to accept the 7793file name that is displayed. 7794When the feature 7795<A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A> 7796is turned on you may use TAB to complete partially typed in names. 7797<P> 7798You may cancel the import operation by typing "^C" after exiting 7799this help. 7800<P> 7801<End of help on this topic> 7802</BODY> 7803</HTML> 7804======= h_ge_allparts ======= 7805<HTML> 7806<HEAD> 7807<TITLE>Export Message File Selection</TITLE> 7808</HEAD> 7809<BODY> 7810<H1>Export Message File Selection</H1> 7811 7812You are Exporting a message from an Alpine mail folder 7813to a plain text file. 7814You also have the option of exporting all of the attachments associated 7815with the message. 7816You are now being asked for the name of the file to export <EM>to</EM>. 7817The easiest way to select a file is probably with the "^T" 7818"To Files" subcommand. 7819After returning from that subcommand you will still be allowed to 7820edit the name you have selected. 7821Alternatively, you may type in a file name. 7822It may be an absolute pathname. 7823Otherwise, it is a file located in your home directory 7824or current working directory 7825<!--chtml if pinemode="running"--> 7826(which, at least for your current Alpine "session," 7827is "<!--#echo var="CURRENT_DIR"-->") 7828<!--chtml endif-->, depending on the 7829<A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> option. 7830In any case, you finish by typing a carriage return to accept the 7831file name that is displayed. 7832When the feature 7833<A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A> 7834is turned on you may use TAB to complete partially typed in names. 7835<P> 7836The message you are exporting appears to have some attachments. 7837If you wish to save <EM>all</EM> of the attachments at once, 7838type the "^P" "AllParts" command to turn on 7839saving of the attachments. 7840You may turn it back off by typing "^P" again, which will now 7841be labeled "NoAllParts" instead. 7842If you want to save the parts the command displayed should be 7843"NoAllParts"! 7844When you choose to save attachments like this, the attachments will be saved 7845in a newly created directory. 7846That directory will have the same name as the file name you choose here, 7847with the letters ".d" appended. 7848If that directory already exists, then the letters ".d_1" will 7849be tried, then ".d_2" and so on until a name that doesn't exist 7850is found. 7851For example, if you select the file name 7852<P> 7853<CENTER><SAMP>filename</SAMP></CENTER> 7854<P> 7855to export the message to, then the directory used for the attachments will be 7856<P> 7857<CENTER><SAMP>filename.d</SAMP></CENTER> 7858<P> 7859or perhaps 7860<P> 7861<CENTER><SAMP>filename.d_<n></SAMP></CENTER> 7862<P> 7863The attachments will then be put into files inside that directory. 7864The names for the attachment files will be derived from the attachments 7865if possible. 7866This is done in the same way as the default values are derived if you 7867save them one at a time. 7868(The "filename" parameter from the Content-Disposition header 7869is the first choice. If that doesn't exist, the "name" 7870parameter from the Content-Type header is used.) 7871If a name for a particular attachment is not available, then the 7872part number of the attachment is used, with the characters "part_" 7873prepended. 7874An example of that would be 7875<P> 7876<CENTER><SAMP>part_2.1</SAMP></CENTER> 7877<P> 7878If you want to save only some of the attachments or if you want more control 7879over the directory and filename where an attachment is saved you may 7880cancel out of this command and View the attachment list. 7881From there you can save each attachment individually. 7882<P> 7883You may cancel the Export operation by typing "^C" after exiting 7884this help. 7885<P> 7886<End of help on this topic> 7887</BODY> 7888</HTML> 7889======= h_ge_export ======= 7890<HTML> 7891<HEAD> 7892<TITLE>Export File Selection</TITLE> 7893</HEAD> 7894<BODY> 7895<H1>Export File Selection</H1> 7896 7897You are Exporting or Saving something from within the Alpine world 7898(a message, an attachment, etc.) 7899to a plain text file. 7900You are now being asked for the name of the file to export <EM>to</EM>. 7901The easiest way to select a file is probably with the "^T" 7902"To Files" subcommand. 7903After returning from that subcommand you will still be allowed to 7904edit the name you have selected. 7905Alternatively, you may type in a file name. 7906It may be an absolute pathname. 7907Otherwise, it is a file located in your home directory 7908or current working directory 7909<!--chtml if pinemode="running"--> 7910(which, at least for your current Alpine "session," 7911is "<!--#echo var="CURRENT_DIR"-->") 7912<!--chtml endif-->, depending on the 7913<A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> option. 7914In any case, you finish by typing a carriage return to accept the 7915file name that is displayed. 7916When the feature 7917<A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A> 7918is turned on you may use TAB to complete partially typed in names. 7919<P> 7920If the object you are exporting is a message with some attachments, 7921you may wish to save all of the attachments by typing the "^P" 7922"AllParts" command to turn on saving of the attachments. 7923This subcommand will only be visible if the message actually has attachments. 7924You may also View the attachment list and save individual attachments from 7925there. 7926<P> 7927If you are SAVING a text part (text/plain, text/html, etc.) you can use 7928the Control-R subcommand to toggle if saving will be done in binary mode, 7929meaning that the attachment will be decoded, but will not be transformed 7930to UTF-8 for further processing (either in internal filters, or user 7931supplied filters.) This is useful in case you either want to preserve 7932the text as it was encoded originally to you, or the attachment was 7933incorrectly attached (the attachment is not of text type) and you need 7934the original text to process the attachment. 7935<P> 7936You may cancel the Export operation by typing "^C" after exiting 7937this help. 7938<P> 7939<End of help on this topic> 7940</BODY> 7941</HTML> 7942======= h_common_save ======= 7943<HTML> 7944<HEAD> 7945<TITLE>Save and Export Commands</TITLE> 7946</HEAD> 7947<BODY> 7948<H1>Save and Export Commands</H1> 7949 7950Save 7951(<!--chtml if pinemode="function_key"-->F11<!--chtml else-->S<!--chtml endif-->) 7952and Export 7953(<!--chtml if pinemode="function_key"-->F12<!--chtml else-->E<!--chtml endif-->) 7954are the two alternatives Alpine gives you to keep a copy of the message 7955you are reading. If you want to keep the message within Alpine's email 7956world, use "Save"; if you want to use the message in another 7957program, use "Export". 7958<P> 7959 7960When you Save a message, it is put into an existing folder or into a new 7961folder in one of your existing folder collections. The message stays in 7962email format and can be read by Alpine again. Alpine may use a special format 7963for its mail folders -- never edit an Alpine folder by hand or with any 7964program other than Alpine. The exact behavior of the Save command can be 7965configured with the 7966<A HREF="h_config_quote_all_froms">"<!--#echo var="FEAT_save-will-quote-leading-froms"-->"</A>, 7967<A HREF="h_config_save_wont_delete">"<!--#echo var="FEAT_save-will-not-delete"-->"</A>, 7968and 7969<A HREF="h_config_save_advances">"<!--#echo var="FEAT_save-will-advance"-->"</A> 7970feature list settings. 7971The name of the folder offered as a default is controlled by the option 7972<A HREF="h_config_saved_msg_name_rule">"<!--#echo var="VAR_saved-msg-name-rule"-->"</A>. 7973<P> 7974 7975When you use Export, the message is placed in a plain text file in your 7976home directory 7977<!--chtml if pinemode="running"--> 7978(which, in the present configuration of your system, is 7979 "<!--#echo var="HOME_DIR"-->") 7980<!--chtml endif--> 7981or current working directory 7982<!--chtml if pinemode="running"--> 7983(which, at least for your current Alpine "session," 7984is "<!--#echo var="CURRENT_DIR"-->") 7985<!--chtml endif-->, depending on the 7986<A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> 7987configuration setting. In the normal case, only minimal 7988headers are exported with the message; however, if the full header mode 7989(whose availability may be disabled by setting the feature 7990<A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A> 7991in SETUP CONFIGURATION) is 7992toggled on, then complete headers are exported along with the message 7993text. (If you have any <A HREF="h_config_display_filters"><!--#echo var="VAR_display-filters"--></A> 7994defined, they may affect the contents of the exported file.) 7995 7996<P> 7997<End of help on this topic> 7998</BODY> 7999</HTML> 8000======= h_common_bounce ======= 8001<HTML> 8002<HEAD> 8003<TITLE>Bounce Command</TITLE> 8004</HEAD> 8005<BODY> 8006<H1>Bounce Command</H1> 8007 8008The Bounce 8009(<!--chtml if pinemode="function_key"-->F10<!--chtml else-->B<!--chtml endif-->) 8010command allows you to re-send, or "remail", a 8011message, as if you were never in the loop. It is analogous to crossing 8012out your address on a postal letter, writing a different address on the 8013envelope, and putting it into the mailbox. Bounce is used primarily to 8014redirect email that was sent to you in error. 8015Also, some owners of email 8016lists need the bounce command to handle list traffic. 8017Bounce is not anonymous. 8018A ReSent-From header is added to the message so that the recipient may 8019tell that you Bounced it to them. 8020<P> 8021 8022The presence or absence of the Bounce command is determined by the 8023<A HREF="h_config_enable_bounce">"<!--#echo var="FEAT_enable-bounce-cmd"-->"</A> 8024feature in your Alpine configuration. 8025The feature 8026<A HREF="h_config_fcc_on_bounce">"<!--#echo var="FEAT_fcc-on-bounce"-->"</A> 8027affects the behavior of the Bounce command. 8028Also, it is possible that Bounce could be 8029administratively disabled by your system manager; if it doesn't work, 8030please check with your local help desk before reporting a bug. 8031 8032<P> 8033<End of help on this topic> 8034</BODY> 8035</HTML> 8036======= h_common_reply ======= 8037<HTML> 8038<HEAD> 8039<TITLE>Reply and Forward Commands</TITLE> 8040</HEAD> 8041<BODY> 8042 8043<H1>Reply and Forward Commands</H1> 8044 8045Replying 8046(<!--chtml if pinemode="function_key"-->F11<!--chtml else-->R<!--chtml endif-->) 8047and Forwarding 8048(<!--chtml if pinemode="function_key"-->F12<!--chtml else-->F<!--chtml endif-->) 8049are your two alternatives for following up on the 8050message you are reading. You would use reply if you want to get email 8051back to the author of the message and/or the other people who have 8052already seen it. You use forward if you want somebody new to see the 8053message. 8054<P> 8055 8056In the normal case, the only thing that you must supply when forwarding a 8057message is the name/email address of the new recipient. 8058Alpine will include the text of the forwarded message. 8059Alpine will also include any attachments to the message. 8060There is space above the forwarded text for you to include additional comments. 8061<P> 8062 8063When replying, you usually have to answer some questions. 8064If the message is to multiple people and/or specified with a Reply-To: header, 8065then you will have to decide who should get the reply. 8066You also need to decide whether or not to include the previous 8067message in your reply. 8068Some of this is configurable. 8069Specifically, see the 8070<A HREF="h_config_include_header">"<!--#echo var="FEAT_include-header-in-reply"-->"</A>, 8071<A HREF="h_config_auto_include_reply">"<!--#echo var="FEAT_include-text-in-reply"-->"</A>, 8072<A HREF="h_config_attach_in_reply">"<!--#echo var="FEAT_include-attachments-in-reply"-->"</A>, 8073and 8074<A HREF="h_config_auto_reply_to">"<!--#echo var="FEAT_reply-always-uses-reply-to"-->"</A> 8075configuration features. 8076<P> 8077 8078Both the Reply and Forward commands react to the full header mode toggle. 8079If the full header mode is on, then all the header and delivery lines are 8080included with the text of the message in your reply/forward. 8081<P> 8082 8083Other configuration features that affect the Reply command are 8084<A HREF="h_config_sig_at_bottom">"<!--#echo var="FEAT_signature-at-bottom"-->"</A>, 8085<A HREF="h_config_sigdashes">"<!--#echo var="FEAT_enable-sigdashes"-->"</A>, and 8086<A HREF="h_config_strip_sigdashes">"<!--#echo var="FEAT_strip-from-sigdashes-on-reply"-->"</A>. 8087 8088<P> 8089<End of help on this topic> 8090</BODY> 8091</HTML> 8092======= h_common_delete ======= 8093<HTML> 8094<HEAD> 8095<TITLE>Delete and Undelete Commands</TITLE> 8096</HEAD> 8097<BODY> 8098<H1>Delete and Undelete Commands</H1> 8099 8100Delete 8101(<!--chtml if pinemode="function_key"-->F9<!--chtml else-->D<!--chtml endif-->) 8102and Undelete 8103(<!--chtml if pinemode="function_key"-->F10<!--chtml else-->U<!--chtml endif-->) 8104allow you to change the Deleted flag for the current message. 8105Delete marks a message Deleted (turns on the Deleted flag) and Undelete 8106removes the mark. 8107In the MESSAGE INDEX, deleted messages have a "D" in the status field 8108at the left hand edge of the index line. 8109When viewing a deleted message, the letters "DEL" will be present 8110in the upper right hand corner of the screen. 8111Delete simply <EM>marks</EM> a message Deleted, it does not actually 8112get rid of the message. 8113The eXpunge command (available from the MESSAGE INDEX screen) actually 8114removes all of the deleted messages in a folder. 8115Once a message is eXpunged, it can't be retrieved. 8116<P> 8117 8118The Delete command is affected by the setting of the configuration feature 8119<A HREF="h_config_del_skips_del">"<!--#echo var="FEAT_delete-skips-deleted"-->"</A>. 8120 8121<P> 8122<End of help on this topic> 8123</BODY> 8124</HTML> 8125======= h_common_postpone ======= 8126<HTML> 8127<HEAD> 8128<TITLE>Postpone Command</TITLE> 8129</HEAD> 8130<BODY> 8131<H1>Postpone Command</H1> 8132 8133The postpone 8134<!--chtml if pinemode="function_key"-->(F11)<!--chtml else-->(^O)<!--chtml endif--> 8135command allows you to temporarily stop working on the current 8136message so you may read 8137other messages or compose another message. When you want to resume a 8138message later, start to compose and answer "yes" to the 8139"Continue postponed composition?" question. You may 8140postpone as many messages as you like. 8141 8142<P> 8143Note: If a <A HREF="h_config_form_folder"><!--#echo var="VAR_form-letter-folder"--></A> is defined 8144in the Setup/Config screen, then the Postpone command will prompt you for 8145the folder in which to store your outgoing message. 8146 8147<P> 8148<End of help on this topic> 8149</BODY> 8150</HTML> 8151======= h_compose_cancel ======= 8152<HTML> 8153<HEAD> 8154<TITLE>Cancel Command</TITLE> 8155</HEAD> 8156<BODY> 8157<H1>Cancel Command</H1> 8158 8159Cancel 8160<!--chtml if pinemode="function_key"--> 8161(F2) 8162<!--chtml else--> 8163(^C) 8164<!--chtml endif--> 8165 8166The Cancel command returns you to Alpine's normal mail processing and 8167causes the message currently under composition to be thrown out. 8168The message text <EM>will be lost</EM>. 8169 8170<P> 8171Note: Unless the <A HREF="h_config_quell_dead_letter"><!--#echo var="FEAT_quell-dead-letter-on-cancel"--></A> has been set, the text of the most recent composition cancelled 8172will be preserved in the file named 8173<!--chtml if pinemode="os_windows"--> 8174"DEADLETR". 8175<!--chtml else--> 8176"dead.letter" in your home directory. 8177<!--chtml endif--> 8178If you unintentionally cancel a message, look there for its text. 8179 8180<P> 8181<End of help on this topic> 8182</BODY> 8183</HTML> 8184======= h_compose_addrcomplete ======= 8185<HTML> 8186<HEAD> 8187<TITLE>Address Completion</TITLE> 8188</HEAD> 8189<BODY> 8190<H1>Address Completion</H1> 8191 8192When entering addresses in the address fields of the composer (To, Cc, etc.) 8193the TAB key may be used to help complete the address. 8194Type a partial nickname and tap the TAB key to complete the typing. 8195The unambiguous part of the name will be filled in automatically. 8196Typing TAB twice in succession will bring up a selection list of possibilities, 8197making it easy to find and choose the correct address. 8198 8199<P> 8200The matching algorithm is rather ad hoc. 8201The search starts with a search of your address book. 8202It counts as a match if the nickname, address, or fullname field of an 8203entry begins with the text typed in so far. It is also a match if 8204a later word in the fullname (for example, the middle name or last name) 8205begins with the entered text. 8206<P> 8207Next comes an LDAP search. 8208The search will happen for any servers that have the 8209<A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A> 8210feature set. You can set or unset the feature for each server independently 8211in the Setup/Directory screen. 8212<P> 8213Finally, if you are replying to or forwarding a message, that message is 8214searched for likely candidate addresses that match the typed-in text. 8215 8216<P> 8217<End of help on this topic> 8218</BODY> 8219</HTML> 8220======= h_compose_richhdr ======= 8221<HTML> 8222<HEAD> 8223<TITLE>Rich Header Command</TITLE> 8224</HEAD> 8225<BODY> 8226<H1>Rich Header Command</H1> 8227 8228The Rich Header command allows you to toggle between the list of 8229all message headers available for editing and those that are most 8230common. 8231 8232<P> 8233Use this toggle to expose headers that are not normally visible by 8234default. 8235This set usually includes the 8236"Bcc:", 8237"Fcc:", 8238"Lcc:", 8239and "Newsgroups" 8240headers. 8241If you are posting to a newsgroup the set of defaults is a little different. 8242Obviously, in that case, the Newsgroups header is of interest so is not 8243hidden. 8244For news posting the hidden set includes the 8245"To:", 8246"Cc:", 8247"Bcc:", 8248"Fcc:", 8249and "Lcc:" 8250headers. 8251You won't normally want to edit these, which is why they are hidden, 8252but it is sometimes useful to be able to set them manually. 8253 8254<P> 8255The default sets of headers listed above can be altered. 8256Any header that you have added to the 8257<A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A> 8258option, but not to the 8259<A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A> 8260option will appear when you use the Rich Headers command to 8261make the Rich Headers visible. 8262(Headers listed in the <!--#echo var="VAR_default-composer-hdrs"--> list will be visible 8263even without toggling the Rich Headers command.) 8264 8265<P> 8266<End of help on this topic> 8267</BODY> 8268</HTML> 8269======= h_compose_send ======= 8270<HTML> 8271<HEAD> 8272<TITLE>Send Command</TITLE> 8273</HEAD> 8274<BODY> 8275<H1>Send Command</H1> 8276 8277The Send command 8278<!--chtml if pinemode="function_key"--> 8279(F3) 8280<!--chtml else--> 8281(^X) 8282<!--chtml endif--> 8283tells Alpine you are finished composing. 8284Before actually sending it, though, Alpine will ask you to confirm 8285your intention, and, at the same time, redisplayed the message text 8286with the recipients at the top of the screen to give you the opportunity 8287to review and verify that the message is addressed to the people 8288you intended. 8289<P> 8290If the feature 8291<A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set, 8292then this confirmation prompt and any options it allows are skipped. 8293 8294<P> 8295This confirmation prompt may also offer, depending 8296on your particular Setup/Config, options allowing you to set 8297<A HREF="h_config_compose_dsn">delivery status notifications</A>, 8298include attachments in the "Fcc" (if you had previously 8299specified that they <A HREF="h_config_no_fcc_attach">exclude attachments</A>, 8300observe details of the 8301<A HREF="h_config_verbose_post">message submission process</A>, 8302choose the filter through which the 8303<A HREF="h_config_sending_filter">outgoing text should first pass</A>, 8304or turn of flowed text generation. 8305 8306<P> 8307<End of help on this topic> 8308</BODY> 8309</HTML> 8310======= h_compose_markcutpaste ======= 8311<HTML> 8312<HEAD> 8313<TITLE>Mark, Cut and Paste Commands</TITLE> 8314</HEAD> 8315<BODY> 8316<H1>Mark, Cut and Paste Commands</H1> 8317 8318You can define a "block" of text, which can subsequently 8319 be deleted or 8320copied as a unit, by setting a mark at the start of the block (Ctrl-^) and 8321then moving the cursor to the end of the desired text block. You can then 8322"cut" the block out 8323<!--chtml if pinemode="function_key"--> 8324"F9", 8325<!--chtml else--> 8326"Ctrl-K", 8327<!--chtml endif--> 8328move the cursor, and "paste" it 8329<!--chtml if pinemode="function_key"--> 8330"F10", 8331<!--chtml else--> 8332"Ctrl-U", 8333<!--chtml endif--> 8334in the new location. Also, you can paste more than once, allowing you 8335to use this feature to copy a block of text.<P> 8336 8337If you press 8338<!--chtml if pinemode="function_key"--> 8339"F9" 8340<!--chtml else--> 8341"^K" 8342<!--chtml endif--> 8343without having marked anything, Alpine will delete 8344a single line. If you delete a group of lines together, Alpine keeps them 8345in the same buffer, so 8346<!--chtml if pinemode="function_key"--> 8347F10 8348<!--chtml else--> 8349^U 8350<!--chtml endif--> 8351will restore them as a block. About 8352terminology: Mark is shown as "^^". The first "^" means you should 8353hold down the "Control" key on your keyboard. The second "^" means 8354"type the character ^". 8355 8356<P> 8357<End of help on this topic> 8358</BODY> 8359</HTML> 8360======= h_compose_justify ======= 8361<HTML> 8362<HEAD> 8363<TITLE>Justify Command</TITLE> 8364</HEAD> 8365<BODY> 8366<H1>Justify Command</H1> 8367 8368The Justify 8369<!--chtml if pinemode="function_key"--> 8370(F4) 8371<!--chtml else--> 8372(^J) 8373<!--chtml endif--> 8374command reformats the text in the paragraph the cursor is in. 8375Paragraphs are separated by one blank line or a line beginning with a space. 8376This is useful when you have been editing a paragraph and the lines become 8377uneven. The text is left aligned or justified and the right is ragged. If 8378the text is already justified as typed with auto-wrap, no justification will 8379be done. 8380 8381<P> 8382If you have set a <A HREF="h_compose_markcutpaste">mark</A> to select a 8383block of text, the Justify command is modified. 8384Instead of automatically justifying the current paragraph you will be 8385asked if you want to justify the paragraph, justify the selected region, 8386or adjust the quote level of the selected region. 8387Adjusting the quote level only works if you are using standard 8388"> " or ">" quotes, which is the default if you haven't 8389changed "<A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A>". 8390 8391<P> 8392When composing a reply containing included text, the justify command 8393will reformat text to the right of the 8394"<A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A>", 8395adding or removing indented lines as needed. Paragraphs are separated 8396by a blank line, a line containing only the <!--#echo var="VAR_reply-indent-string"-->, or a 8397line containing the indent string and one or more blank spaces. 8398Included text that was previously indented (or "quoted") is 8399not preserved. 8400 8401<P> 8402Because of the introduction of <A HREF="h_config_quell_flowed_text">Flowed Text</A> 8403in 1999 and its wide-spread adoption since then, you will usually be better off if you 8404use the standard 8405"> " or ">" quotes. 8406 8407<P> 8408<End of help on this topic> 8409</BODY> 8410</HTML> 8411======= h_compose_spell ======= 8412<HTML> 8413<HEAD> 8414<TITLE>Spell Check Command</TITLE> 8415</HEAD> 8416<BODY> 8417<H1>Spell Check Command</H1> 8418 8419The "To Spell" 8420<!--chtml if pinemode="function_key"--> 8421(F12) 8422<!--chtml else--> 8423(^T) 8424<!--chtml endif--> 8425command calls an external spell checking program to look over the 8426message you are composing. By default, Alpine uses 8427<P> 8428<CENTER><SAMP>aspell --dont-backup --mode=email check</SAMP></CENTER> 8429<P> 8430if it knows where to find "aspell". 8431If there is no "aspell" command available but the command "ispell" is available 8432then the command used is 8433<P> 8434<CENTER><SAMP>ispell -l</SAMP></CENTER> 8435<P> 8436Otherwise, the ancient "spell" command is used. 8437<P> 8438For PC-Alpine, you must install the aspell library code that you 8439may get from 8440<A HREF="http://aspell.net/win32/">http://aspell.net/win32/</A>. 8441 8442<P> 8443<End of help on this topic> 8444</BODY> 8445</HTML> 8446======= h_compose_alted ======= 8447<HTML> 8448<HEAD> 8449<TITLE>Alt Editor Command</TITLE> 8450</HEAD> 8451<BODY> 8452<H1>Alt Editor Command</H1> 8453 8454The "Alt Editor" command's availability depends on the 8455Setup/Config variable "<A HREF="h_config_editor"><!--#echo var="VAR_editor"--></A>". 8456 8457<P> 8458When the variable specifies a valid editor on your system, this 8459command will launch it with the current text of your message 8460already filled in. 8461 8462<P> 8463<End of help on this topic> 8464</BODY> 8465</HTML> 8466======= h_compose_readfile ======= 8467<HTML> 8468<HEAD> 8469<TITLE>Read File Command</TITLE> 8470</HEAD> 8471<BODY> 8472<H1>Read File Command</H1> 8473 8474The "Read File" 8475<!--chtml if pinemode="function_key"--> 8476(F5) 8477<!--chtml else--> 8478(^R) 8479<!--chtml endif--> 8480command allows you to copy in text from an existing file. You will be 8481prompted for the name of a file to be inserted into the message. The file 8482name is relative to your home directory 8483<!--chtml if pinemode="running"--> 8484(which, in the present configuration of your system, is 8485 "<!--#echo var="HOME_DIR"-->") 8486<!--chtml endif--> 8487or current working directory 8488<!--chtml if pinemode="running"--> 8489(which, at least for your current Alpine "session," 8490is "<!--#echo var="CURRENT_DIR"-->") 8491<!--chtml endif-->, depending on the 8492<A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> 8493configuration setting; or, the file name must be specified as a full path name 8494<!--chtml if pinemode="os_windows"--> 8495-- for example: "A:\PAPER.TXT" 8496<!--chtml else--> 8497-- for example: "/tmp/wisdom-of-the-day" 8498<!--chtml endif--> 8499(without the quotation marks). 8500 8501<P> 8502The file will be inserted where the cursor is located. <B>The 8503file to be read must be on the same system as Alpine.</B> If you use Alpine on a 8504Unix machine but have files on a PC or Mac, the files must be transferred 8505to the system Alpine is running on before they can be read. Please ask your 8506local computer support people about the correct way to transfer a file to 8507your Alpine system. 8508 8509<P> 8510<End of help on this topic> 8511</BODY> 8512</HTML> 8513======= h_config_tray_icon ======= 8514<HTML> 8515<HEAD> 8516<TITLE>FEATURE: <!--#echo var="FEAT_enable-tray-icon"--></TITLE> 8517</HEAD> 8518<BODY> 8519<H1>FEATURE: <!--#echo var="FEAT_enable-tray-icon"--></H1> 8520 8521PC-Alpine only. 8522<P> 8523This option restores a behavior of previous versions of PC-Alpine. 8524These 8525versions, when started, installed a PC-Alpine icon in the notification 8526tray of Window's Taskbar. The primary use of this icon was to indicate 8527new mail arrival by turning red (while the Taskbar icon remained green). 8528Additionally, the icon now changes to yellow to signify that a mail folder 8529has been closed unexpectedly. 8530 8531<P> 8532Rather than add another icon to the Taskbar, this version of PC-Alpine will 8533color its Taskbar entry's icon red (as well as the icon in the Window 8534Title). This feature is only provided for backwards compatibility. 8535 8536<P> 8537<End of help on this topic> 8538</BODY> 8539</HTML> 8540======= h_common_suspend ======= 8541<HTML> 8542<HEAD> 8543<TITLE>Suspend Command</TITLE> 8544</HEAD> 8545<BODY> 8546<H1>Suspend Command</H1> 8547 8548With the <A HREF="h_config_can_suspend"><!--#echo var="FEAT_enable-suspend"--></A> feature 8549enabled, you can, at almost any time, temporarily halt your Alpine session, 8550<!--chtml if pinemode="os_windows"--> 8551minimizing it into an icon. 8552<!--chtml else--> 8553and return to your system prompt. 8554<!--chtml endif--> 8555 8556<P> 8557<End of help on this topic> 8558</BODY> 8559</HTML> 8560======= h_pipe_command ======= 8561<HTML> 8562<HEAD> 8563<TITLE>Pipe Command SubOptions</TITLE> 8564</HEAD> 8565<BODY> 8566<H1>Pipe Command SubOptions</H1> 8567 8568By default, when you use the Pipe command, the processed text of the 8569message is sent to the Unix command 8570you specify and the output is captured by Alpine and shown to you. 8571(This command is available in PC-Alpine, as well, but there aren't many 8572Windows commands that work well with piping.) 8573There are some sub-commands that may be used to alter this behavior. 8574These are toggles that switch the behavior between two possibilities. 8575They can be combined in any way you wish. 8576<P> 8577By default, the prompt at the bottom of the screen looks like 8578<P> 8579<CENTER><SAMP>Pipe message 37 to :</SAMP></CENTER> 8580<P> 8581or 8582<P> 8583<CENTER><SAMP>Pipe messages to :</SAMP></CENTER> 8584<P> 8585if you are piping more than one message. 8586<P> 8587The sub-command options are: 8588<DL> 8589 <DT>Shown Text or Raw Text</DT> 8590 <DD>This option toggles between sending the shown (processed) text 8591of the message to the Unix command, and sending the 8592raw (unprocessed) text of the message to the Unix command. 8593The default is to send the shown text. 8594The raw version of the message will contain all of the headers and any 8595MIME encoding that the message contains. 8596If you've selected the Raw Text then the prompt will have the additional word 8597"RAW" in it, like 8598<P> 8599<CENTER><SAMP>Pipe RAW messages to :</SAMP></CENTER> 8600<P> 8601You can experiment with this option by piping to something simple like the 8602Unix "cat" command. 8603 </DD> 8604 <DT>Captured Output or Free Output</DT> 8605 <DD>This option toggles between having Alpine capture the output of 8606the Unix pipe command for display, and not capturing it. 8607If the command you are piping to is a filter that will produce output 8608you want to view, then you want to capture that output 8609for display (the default). 8610If the Unix command doesn't produce output or handles the display itself, 8611then you want free output. 8612When you've selected the Free Output option the prompt will change to 8613<P> 8614<CENTER><SAMP>Pipe messages to (uncaptured) :</SAMP></CENTER> 8615<P> 8616 </DD> 8617 <DT>No Delimiter or With Delimiter</DT> 8618 <DD>This option controls whether or not a Unix mailbox style delimiter 8619will come before the text of the message. 8620This is the delimiter used in the common Unix mailbox format. 8621It's the single line that begins with the five characters 8622"From" followed by a <SPACE> character. 8623You'll usually only want to include this if the Unix command requires 8624input in the format of a traditional Unix mailbox file. 8625When you've selected the With Delimiter option the prompt will change to 8626<P> 8627<CENTER><SAMP>Pipe messages to (delimited) :</SAMP></CENTER> 8628<P> 8629 </DD> 8630 <DT>To Same Pipe or To Individual Pipes</DT> 8631 <DD>This option only shows up if you are running an aggregate 8632pipe command. 8633That is, the command was Apply Pipe, not just Pipe. 8634You have the option of piping all of the selected messages through a 8635single pipe to a single instance of the Unix command, 8636or piping each individual message through a separate pipe to separate 8637instances of the Unix command. 8638The default is that all of the output will go through a single pipe 8639to a single instance of the command. 8640You can try this option with a command like "less", with Free 8641Output enabled. 8642When you've selected the Individual Pipes option the prompt will change to 8643<P> 8644<CENTER><SAMP>Pipe messages to (new pipe) :</SAMP></CENTER> 8645<P> 8646 </DD> 8647</DL> 8648 8649<P> 8650As mentioned earlier, the options can be combined in any way you wish. 8651You may leave them all off, turn them all on, or turn some of them on 8652and some of them off. 8653If you use the pipe command a second time in the same session the default 8654options will be what you used the last time. 8655 8656<P> 8657<End of help on this topic> 8658</BODY> 8659</HTML> 8660========== h_emptydir_subfolder_name ========= 8661<HTML> 8662<HEAD> 8663<TITLE>ENTER SUBFOLDER NAME</TITLE> 8664</HEAD> 8665<BODY> 8666<H1>Enter Subfolder Name</H1> 8667 8668<P> 8669This is the name of a new subfolder in the directory you are creating. 8670Because empty directories are hidden and therefore not useful, you must also 8671create a subfolder in the directory you are creating in order that the 8672directory remains visible. 8673<P> 8674Alternatively, you may turn off the configuration feature 8675<A HREF="h_config_quell_empty_dirs"><!--#echo var="FEAT_quell-empty-directories"--></A> 8676so that empty directories remain visible. 8677If you do that, you will not be required to create the subfolder when you 8678create a directory. 8679 8680<P> 8681<End of help on this topic> 8682</BODY> 8683</HTML> 8684========== h_incoming_add_folder_name ========= 8685<HTML> 8686<HEAD> 8687<TITLE>ENTER FOLDER NAME</TITLE> 8688</HEAD> 8689<BODY> 8690<H1>Enter Folder Name</H1> 8691 8692<P> 8693This is the name of the folder on the previously specified server. 8694By default the folder name is interpreted as defining a section of your personal 8695folder area. This area and how you specify it are defined by the 8696server, if one is specified. 8697 8698<P> 8699To define a folder outside the default area, prefix 8700the path with the namespace to use when interpreting the 8701given path. If a namespace is specified, the folder name begins with the 8702sharp (#) character followed by the name of the namespace 8703and then the namespace's path-element-delimiter. Aside from the 8704name's format, namespaces can also imply access rights, content 8705policy, audience, location, and, occasionally, access methods. 8706 8707<P> 8708Each server exports its own set (possibly of size one) of 8709namespaces. 8710For a more detailed explanation read about 8711<A HREF="h_folder_name_namespaces">Namespaces</A>. 8712 8713<P> 8714To specify the default for INBOX on the server you can usually just enter 8715"INBOX", and the server will understand the special meaning of 8716that word. 8717 8718<P> 8719<End of help on this topic> 8720</BODY> 8721</HTML> 8722========== h_incoming_add_folder_host ========= 8723<HTML> 8724<HEAD> 8725<TITLE>ENTER INCOMING FOLDER SERVER</TITLE> 8726</HEAD> 8727<BODY> 8728<H1>Enter Incoming Folder Server</H1> 8729 8730You are being asked for the name of the server for use with this incoming 8731folder. 8732If the folder is on the machine where Alpine is running, then just enter 8733RETURN without typing a server name. 8734 8735<P> 8736If the folder is on an IMAP server then type the server's name followed 8737by RETURN. 8738You may use the ^X command if the server is the same as the server that 8739the INBOX is on. 8740 8741<P> 8742You may have to add optional extra information to the server name. 8743For example, if the IMAP server is using a non-standard port number you 8744would specify that by appending a colon (:) followed by the port number 8745to the server name 8746 8747<P> 8748<CENTER><SAMP>foo.example.com:port</SAMP></CENTER> 8749<P> 8750 8751or you may need to specify a different protocol if the server is not an 8752IMAP server. For example: 8753 8754<P> 8755<CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER> 8756<P> 8757 8758for a POP server or 8759 8760<P> 8761<CENTER><SAMP>foo.example.com/nntp</SAMP></CENTER> 8762<P> 8763 8764for an NNTP news server. 8765For an explanation of all of the possibilities, see 8766<A HREF="h_folder_server_syntax">Server Name Syntax</A> 8767for folders. 8768 8769<P> 8770There is a special command (^W) if you want to set up a folder that gets its 8771mail from a 8772<A HREF="h_maildrop">Mail Drop</A>. 8773If you type that command, you will be prompted for the information for 8774both the Mail Drop folder and the destination folder. 8775 8776<P> 8777<End of help on this topic> 8778</BODY> 8779</HTML> 8780========== h_incoming_add_inbox ========= 8781<HTML> 8782<HEAD> 8783<TITLE>ENTER INBOX SERVER</TITLE> 8784</HEAD> 8785<BODY> 8786<H1>Enter INBOX Server</H1> 8787 8788You are being asked for the name of the server for use with 8789the INBOX folder. 8790Type the server's name followed by RETURN. 8791 8792<P> 8793You may have to add optional extra information to the server name. 8794For example, if the server is using a non-standard port number you 8795would specify that by appending a colon (:) followed by the port number 8796to the server name 8797 8798<P> 8799<CENTER><SAMP>foo.example.com:port</SAMP></CENTER> 8800<P> 8801 8802or you may need to specify a different protocol if the server is not an 8803IMAP server. For example: 8804 8805<P> 8806<CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER> 8807<P> 8808 8809for a POP server. 8810<P> 8811 8812For an explanation of all of the possibilities, see 8813<A HREF="h_folder_server_syntax">Server Name Syntax</A> 8814for folders. 8815 8816<P> 8817If the INBOX folder is on the machine where Alpine is running, then just enter 8818RETURN without typing a server name. 8819 8820<P> 8821There is a special command (^W) if you want to set up a folder that gets its 8822mail from a 8823<A HREF="h_maildrop">Mail Drop</A>. 8824If you type that command, you will be prompted for the information for 8825both the Mail Drop folder and the destination folder, which will be used 8826as your INBOX folder. 8827 8828<P> 8829<End of help on this topic> 8830</BODY> 8831</HTML> 8832========== h_incoming_add_maildrop_destn ========= 8833<HTML> 8834<HEAD> 8835<TITLE>ENTER DESTINATION SERVER</TITLE> 8836</HEAD> 8837<BODY> 8838<H1>Enter Destination Server</H1> 8839 8840You are being asked for the name of the server where the destination 8841folder is for use with this Mail Drop incoming folder. 8842That is, you are using a Mail Drop for this incoming folder and 8843you've already entered 8844the server and folder name for the Mail Drop. 8845Now you need to enter the server for the destination folder 8846where the mail should be copied to. 8847Mail will come from the Mail Drop and be copied to the destination folder. 8848 8849<P> 8850Type the server's name followed by RETURN. 8851If the folder is local to this computer, just type RETURN without entering 8852a server name. 8853 8854<P> 8855You may have to add optional extra information to the server name. 8856For example, if the server is using a non-standard port number you 8857would specify that by appending a colon (:) followed by the port number 8858to the server name 8859 8860<P> 8861<CENTER><SAMP>foo.example.com:port</SAMP></CENTER> 8862<P> 8863 8864For an explanation of all of the possibilities, see 8865<A HREF="h_folder_server_syntax">Server Name Syntax</A> 8866for folders. 8867 8868<P> 8869<End of help on this topic> 8870</BODY> 8871</HTML> 8872========== h_inbox_add_maildrop_destn ========= 8873<HTML> 8874<HEAD> 8875<TITLE>ENTER DESTINATION SERVER</TITLE> 8876</HEAD> 8877<BODY> 8878<H1>Enter Destination Server</H1> 8879 8880You are being asked for the name of the server where the destination 8881folder is for use with your Mail Drop INBOX. 8882That is, you are using a Mail Drop for your INBOX and you've already entered 8883the server and folder name for the Mail Drop. 8884Now you need to enter the server for the destination folder 8885where the mail should be copied to. 8886Mail will come from the Mail Drop and be copied to the destination folder. 8887 8888<P> 8889Type the server's name followed by RETURN. 8890If the folder is local to this computer, just type RETURN without entering 8891a server name. 8892 8893<P> 8894You may have to add optional extra information to the server name. 8895For example, if the server is using a non-standard port number you 8896would specify that by appending a colon (:) followed by the port number 8897to the server name 8898 8899<P> 8900<CENTER><SAMP>foo.example.com:port</SAMP></CENTER> 8901<P> 8902 8903For an explanation of all of the possibilities, see 8904<A HREF="h_folder_server_syntax">Server Name Syntax</A> 8905for folders. 8906 8907<P> 8908<End of help on this topic> 8909</BODY> 8910</HTML> 8911========== h_inbox_add_maildrop ========= 8912<HTML> 8913<HEAD> 8914<TITLE>ENTER MAILDROP SERVER</TITLE> 8915</HEAD> 8916<BODY> 8917<H1>Enter Mail Drop Server</H1> 8918 8919You are being asked for the name of the Mail Drop server for use with 8920your INBOX. 8921 8922<P> 8923Type the server's name followed by RETURN. 8924 8925<P> 8926You may have to add optional extra information to the server name. 8927For example, if the server is using a non-standard port number you 8928would specify that by appending a colon (:) followed by the port number 8929to the server name 8930 8931<P> 8932<CENTER><SAMP>foo.example.com:port</SAMP></CENTER> 8933<P> 8934 8935or you may need to specify a different protocol if the server is not an 8936IMAP server. For example: 8937 8938<P> 8939<CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER> 8940<P> 8941 8942for a POP server or 8943 8944<P> 8945<CENTER><SAMP>foo.example.com/nntp</SAMP></CENTER> 8946<P> 8947 8948for an NNTP news server. 8949For an explanation of all of the possibilities, see 8950<A HREF="h_folder_server_syntax">Server Name Syntax</A> 8951for folders. 8952 8953<P> 8954<End of help on this topic> 8955</BODY> 8956</HTML> 8957========== h_incoming_add_maildrop ========= 8958<HTML> 8959<HEAD> 8960<TITLE>ENTER MAILDROP SERVER</TITLE> 8961</HEAD> 8962<BODY> 8963<H1>Enter Mail Drop Server</H1> 8964 8965You are being asked for the name of the Mail Drop server for use with 8966this incoming folder. 8967 8968<P> 8969Type the server's name followed by RETURN. 8970You may use the ^X command if the server is the same as the server that 8971the INBOX is on. 8972 8973<P> 8974You may have to add optional extra information to the server name. 8975For example, if the server is using a non-standard port number you 8976would specify that by appending a colon (:) followed by the port number 8977to the server name 8978 8979<P> 8980<CENTER><SAMP>foo.example.com:port</SAMP></CENTER> 8981<P> 8982 8983or you may need to specify a different protocol if the server is not an 8984IMAP server. For example: 8985 8986<P> 8987<CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER> 8988<P> 8989 8990for a POP server or 8991 8992<P> 8993<CENTER><SAMP>foo.example.com/nntp</SAMP></CENTER> 8994<P> 8995 8996for an NNTP news server. 8997For an explanation of all of the possibilities, see 8998<A HREF="h_folder_server_syntax">Server Name Syntax</A> 8999for folders. 9000 9001<P> 9002If the Mail Drop folder is on the machine where Alpine is running, then just enter 9003RETURN without typing a server name. 9004 9005<P> 9006<End of help on this topic> 9007</BODY> 9008</HTML> 9009========== h_maildrop ========= 9010<HTML> 9011<HEAD> 9012<TITLE>WHAT IS A MAIL DROP?</TITLE> 9013</HEAD> 9014<BODY> 9015<H1>What is a Mail Drop?</H1> 9016 9017In some situaions it may make sense to have your mail delivered to one 9018folder (the Mail Drop) and then when you want to read mail that has been 9019delivered to the Mail Drop folder Alpine will move it to another 9020destination folder. 9021Often the Mail Drop will be a remote folder and messages will be moved from 9022there to a local destination folder. 9023 9024<P> 9025One example where this might make sense is if the Mail Drop folder is accessible 9026only with the POP protocol. 9027You could designate your POP inbox as the Mail Drop folder and have Alpine move 9028mail from there to a local (on the same machine Alpine is running on) 9029destination folder, where you'll read it. 9030 9031<P> 9032A Mail Drop may only be used as your Inbox or as an 9033<A HREF="h_config_enable_incoming">"Incoming folder"</A>. 9034 9035<P> 9036There is no attempt to synchronize the contents of the destination folder 9037with the contents of the Mail Drop folder. 9038All that happens is that all of the messages in the Mail Drop folder are 9039copied to the destination folder and then they are deleted and expunged (if possible) 9040from the Mail Drop folder. 9041The next time a check for new mail is made, any messages in the Mail 9042Drop folder are once again copied to the destination folder and deleted 9043and expunged from the Mail Drop folder. 9044(If the Mail Drop folder is a news group, then the messages can't be 9045expunged from the newsgroup. Instead, only Recent messages are copied from 9046the newsgroup to the destination folder.) 9047 9048<P> 9049Configuration of a Mail Drop is a little different from configuration of 9050a folder that does not use a Mail Drop because you have to specify two 9051folder names instead of one. 9052The two folders may be any types of folders that Alpine can normally use. 9053They don't have to be a remote folder and a local folder, that is 9054simply the most common usage. 9055When you use a Mail Drop folder Alpine will periodically re-open the Mail 9056Drop to check for new mail. 9057The new-mail checks will happen at the frequency set with the 9058<A HREF="h_config_mailcheck"><!--#echo var="VAR_mail-check-interval"--></A> option, 9059but with a minimum time 9060(<A HREF="h_config_maildropcheck"><!--#echo var="VAR_maildrop-check-minimum"--></A>) 9061between checks. 9062Because of this minimum you may notice that new mail does not 9063appear promptly when you expect it. 9064The reason for this is to protect the server from over-zealous opening and 9065closing of the Mail Drop folder. 9066If the user initiates the check by typing ^L (Ctrl-L) or the Next command when at 9067the end of the folder index, then the check will happen, regardless of how 9068long it has been since the previous check. 9069<P> 9070If there is new mail, that mail will be copied to the destination folder 9071and then will be deleted from the Mail Drop. 9072Note that using a Mail Drop with a local destination folder does not make 9073sense if you read mail from more than one machine, because the mail is 9074downloaded to the destination folder (which is accessible from only one 9075machine) and deleted from the Mail Drop. 9076<P> 9077The feature <A HREF="h_config_maildrops_preserve_state"><!--#echo var="FEAT_maildrops-preserve-state"--></A> modifies the operation of Mail Drops. 9078 9079<P> 9080The actual syntax used by Alpine for a folder that uses a Mail Drop is: 9081 9082<P> 9083<CENTER><SAMP>#move<DELIM><MailDropFolder><DELIM><DestinationFolder></SAMP></CENTER> 9084<P> 9085The brackets are not literal. 9086<P> 9087<CENTER><SAMP><DELIM></SAMP></CENTER> 9088<P> 9089is a single character that does not appear in the MailDropFolder name. 9090If the name doesn't contain spaces then it can be a space character. 9091The two folder names are full technical 9092<A HREF="h_valid_folder_names">folder names</A> 9093as used by Alpine. 9094Here are a couple examples to give you an idea what is being talked about: 9095 9096<P> 9097<CENTER><SAMP>#move {popserver.example.com/pop3}inbox localfolder</SAMP></CENTER> 9098<P> 9099<CENTER><SAMP>#move+{nntpserver.example.com/nntp}#news.comp.mail.pine+local folder</SAMP></CENTER> 9100<P> 9101 9102A #move folder may only be used as an 9103<A HREF="h_config_enable_incoming">"Incoming folder"</A> or 9104an Inbox. 9105When you are in the FOLDER LIST of Incoming Message Folders (after turning 9106on the 9107<A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A> 9108option) 9109the Add command has a subcommand "Use Mail Drop" 9110which may be helpful for defining the folder in your Alpine configuration. 9111The same is true when you edit the 9112<A HREF="h_config_inbox_path"><!--#echo var="VAR_inbox-path"--></A> 9113option in Setup/Config. 9114Each of these configuration methods will also create the DestinationFolder 9115if it doesn't already exist. 9116If you are having problems, make sure the DestinationFolder exists. 9117 9118<P> 9119<End of help on this topic> 9120</BODY> 9121</HTML> 9122========== h_save ========= 9123<HTML> 9124<HEAD> 9125<TITLE>CHOOSE A FOLDER TO SAVE INTO</TITLE> 9126</HEAD> 9127<BODY> 9128<H1>Choose a Folder to Save Into</H1> 9129 9130After Exiting from this help text, 9131type the name of the folder you want to save into and press RETURN. 9132<P> 9133Press ^T to get a list of your folders to choose from. 9134Press ^C to cancel the Save. 9135<P> 9136If you have Folder Collections defined you may use 9137Ctrl-P (Previous collection) and Ctrl-N (Next collection) to switch 9138the collection being saved to. 9139<P> 9140If Tab Completion is enabled (it is enabled by default) 9141you may type a Tab character to have Alpine complete the folder name for you. 9142<P> 9143If Partial Match Lists is enabled (it is enabled by default) you may type 9144Ctrl-X to get a list of matches to the prefix you've typed in so far. 9145<P> 9146If the Ctrl-R subcommand is present that means you can decide to Delete or 9147not Delete the message you are saving after you save it. 9148The label on that key gives the action to switch to. 9149If it says Delete and you type Ctrl-R the label displayed will change to 9150No Delete and the source message will be deleted after the save. If it 9151says No Delete and you type Ctrl-R the label displayed will change to 9152Delete and the message will not be deleted. 9153You can control the default for the Delete parameter with the 9154configuration feature <!--#echo var="FEAT_save-will-not-delete"-->. 9155<P> 9156Similarly, if the Ctrl-W subcommand is present that means you can decide 9157to Preserve the order of the messages being saved or not. 9158If it is labeled Preserve Order and you type Ctrl-W, the resulting Saved messages 9159will be in the same order as you see them in the source folder now. 9160The opposite action (which is usually the default) is that you don't care 9161about the order. 9162The Saved messages may or may not be in the same order in the destination folder. 9163There may be a performance penalty for choosing to save the messages in order. 9164You can control the default for the Preserve Order parameter with the 9165configuration feature 9166<!--#echo var="FEAT_save-aggregates-copy-sequence"-->. 9167 9168<P> 9169If you haven't disabled the Save Input History and you've already done a 9170Save earlier in this session then you may use the Up and Down arrows to retrieve 9171a folder name used in a previous Save. 9172 9173<P> 9174<End of help on this topic> 9175</BODY> 9176</HTML> 9177============= h_simple_index ======================== 9178<HTML> 9179<HEAD> 9180<TITLE>SELECT POSTPONED MESSAGE</TITLE> 9181</HEAD> 9182<BODY> 9183<H1>POSTPONED MESSAGE SELECTION COMMANDS</H1> 9184<!--chtml if pinemode="function_key"--> 9185<PRE> 9186Navigating the List of Messages General Alpine Commands 9187------------------------------- ----------------------- 9188 F5 Move to previous message F1 Show this help text 9189 F6 Move to next message 9190 F7 Show previous screen of messages 9191 F8 Show next screen of messages 9192 9193Message Selection Commands 9194-------------------------- 9195 F3 Exit the Message Select menu (canceling Send command) 9196 F4 Select the currently highlighted message 9197 F9 Mark the currently highlighted message as deleted 9198 F10 Undelete (remove deletion mark from) the highlighted message 9199</PRE> 9200<!--chtml else--> 9201<PRE> 9202Navigating the List of Messages General Alpine Commands 9203------------------------------- ----------------------- 9204 P Move to previous message ? Show this help text 9205 N Move to next message 9206 - Show previous screen of messages 9207 Spc (space bar) Show next screen of messages 9208 9209Message Selection Commands 9210-------------------------- 9211 E Exit the Message Select menu (canceling Send command) 9212 S Select the currently highlighted message 9213 D Mark the currently highlighted message as deleted 9214 U Undelete (remove deletion mark from) the highlighted message 9215</PRE> 9216<!--chtml endif--> 9217<P> 9218<H2>Description of the Select Postponed Message Screen</H2> 9219 9220This screen allows you to select one of several previously postponed 9221messages in order to continue composition. Your options are very limited 9222-- the screen is not meant to let you manipulate these messages. However, 9223you may now delete messages from this list. Once you choose a message, 9224Alpine reads it in and puts you into the regular message composer. 9225<P> 9226 9227Messages do not stay in this postponed state automatically. If you select 9228a message and then want to postpone it again, use the normal postpone 9229(Ctrl-O) command in the composer. 9230<P> 9231 9232If you exit this screen without selecting a message, the Compose command 9233that got you here is canceled. Other than messages explicitly marked 9234"Deleted", no messages will be removed. 9235 9236<P> 9237<End of help on this topic> 9238</BODY> 9239</HTML> 9240============= h_collection_screen ======================== 9241<HTML> 9242<HEAD> 9243<TITLE>COLLECTION LIST screen</TITLE> 9244</HEAD> 9245<BODY> 9246<H1>COLLECTION LIST screen</H1> 9247 9248The COLLECTION LIST screen is used to select one of your 9249collection definitions to display the folders they contain. See 9250<A HREF="h_what_are_collections">Folder Collections Explained</A> for 9251detailed explanation of collections.<P> 9252 9253To manage your collection definitions (Add, Change, Delete, etc.), use 9254the <A HREF="h_collection_maint">Setup/collectionList</A> command on Alpine's 9255MAIN MENU. 9256 9257<P> 9258<End of help on this topic> 9259</BODY> 9260</HTML> 9261============= h_collection_maint ======================== 9262<HTML> 9263<HEAD> 9264<TITLE>SETUP COLLECTION LIST screen</TITLE> 9265</HEAD> 9266<BODY> 9267<H1>SETUP COLLECTION LIST screen</H1> 9268 9269The SETUP COLLECTION LIST screen lets you manage your collection 9270definitions. See 9271<A HREF="h_what_are_collections">Folder Collections Explained</A> 9272for detailed explanation of collections.<P> 9273 9274Maintenance commands include: 9275<DL> 9276<DT>Change 9277<!--chtml if pinemode="function_key"--> 9278(F4) 9279<!--chtml else--> 9280(C) 9281<!--chtml endif--> 9282</DT> 9283 9284<DD>Modify attributes of the selected collection definition. 9285 9286<DT>Add Cltn 9287<!--chtml if pinemode="function_key"--> 9288(F9) 9289<!--chtml else--> 9290(A) 9291<!--chtml endif--> 9292</DT> 9293 9294<DD>Create a new collection definition. 9295</DD> 9296 9297<DT>Del Cltn 9298<!--chtml if pinemode="function_key"--> 9299(F10) 9300<!--chtml else--> 9301(D) 9302<!--chtml endif--> 9303</DT> 9304 9305<DD>Delete the selected collection definition.<BR> 9306NOTE: The folders and directories referred to by the 9307collection definition are <EM>NOT</EM> deleted. Folders must 9308be deleted, if that's what you wish to do, from the 9309<A HREF="h_folder_maint">FOLDER LIST screen</A>, which shows the 9310individual folders in a collection. 9311</DD> 9312 9313<DT>Shuffle 9314<!--chtml if pinemode="function_key"--> 9315(F11) 9316<!--chtml else--> 9317($) 9318<!--chtml endif--> 9319</DT> 9320 9321<DD>Change the order of the displayed collections. Alpine will offer 9322to move the currently selected collection one position UP 9323or DOWN. 9324</DD> 9325</DL> 9326 9327<P> 9328<End of help on this topic> 9329</BODY> 9330</HTML> 9331============ h_what_are_collections ========== 9332<HTML> 9333<HEAD> 9334<TITLE>Folder Collections Explained</TITLE> 9335</HEAD> 9336<BODY> 9337<H1>Folder Collections Explained</H1> 9338 9339 9340Those of you with simple mail configurations will just see a list of all the 9341folders you have when choosing FOLDER LIST from Alpine's MAIN MENU. 9342The special folders for INBOX, sent mail and saved messages 9343will appear at the top of the list. All others are in alphabetical order. 9344<P> 9345If you 9346or your system administrator have defined more than one collection or if 9347you have a collection (for newsgroups or email folders) defined on your 9348system, then you will see the COLLECTION LIST screen first when choosing 9349FOLDER LIST from Alpine's MAIN MENU. 9350<P> 9351<H2>Why have multiple folder collections?</H2> 9352<P> 9353For Alpine users who only maintain email folders (and not too many) on one host, 9354a single folder collection is probably sufficient.<P> 9355 9356However, people who have more than one email account - for example, one 9357at their university, and one with their personal Internet Service Provider - 9358will have different sets of folders on different hosts, and they may want to 9359access them all from the same installation of Alpine, rather than use different 9360software and/or log into other hosts to manipulate messages in different 9361accounts. (If in doubt whether one of your email accounts can be accessed 9362with Alpine, contact the technical support people for that account.) Even people 9363who have only one email account on one host, but have dozens or 9364hundreds of email folders, may want to arrange these folders together in a 9365meaningful way.<BR> 9366That is where multiple collections come in. 9367 9368<H2>Types of Collections</H2> 9369<DL> 9370<DT>INCOMING FOLDERS</DT> 9371<DD>"Incoming Message Folders" 9372is a special collection typically used to supplement your single INBOX. 9373All the folders here are meant to be ones that receive incoming messages, 9374which you intend to check more or less frequently. 9375You may have multiple folders like this because you or your systems 9376administrator have set up an external program or you may have set up 9377Alpine to filter incoming 9378messages into different folders, based on certain criteria such as 9379sender, recipient, or subject; or because you have multiple accounts and 9380wish to check their INBOXes easily. This collection is established by 9381setting the 9382<A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A> 9383feature in the SETUP CONFIGURATION screen, which is accessed from the 9384MAIN MENU. 9385</DD> 9386 9387<DT>NEWS</DT> 9388<DD>You can also define a collection specifically for 9389newsgroups. Alpine does this for you implicitly when you 9390<A HREF="h_config_nntp_server">define an NNTP Server</A> 9391in your Alpine configuration. The news collection appears last in the 9392COLLECTION LIST (though you can shuffle it up in the order of presentation), 9393and Alpine knows not to save messages there. 9394</DD> 9395 9396<DT>DEFAULT COLLECTION</DT> 9397<DD>This is the default collection for your saved and sent messages folders. 9398</DD> 9399</DL> 9400 9401<P> 9402 9403<H2>Defining Collections</H2> 9404<P> 9405In the absence of any folder-collection definitions, Alpine will assume a 9406single default folder collection. 9407<!--chtml if pinemode="os_windows"--> 9408<!--chtml else--> 9409If necessary, Alpine will create the directory 9410"mail" in your Unix home directory 9411to hold your folders. 9412<!--chtml endif--> 9413<P> 9414You can use the 9415<A HREF="h_collection_maint">Setup/collectionList screen</A>, called up from 9416the MAIN MENU, to manage your collection list. 9417<P> 9418<End of help on this topic> 9419</BODY> 9420</HTML> 9421===== h_select_address_screen ===== 9422<HTML> 9423<HEAD> 9424<TITLE>SELECT AN ADDRESS SCREEN</TITLE> 9425</HEAD> 9426<BODY> 9427<H1>SELECT AN ADDRESS SCREEN</H1> 9428<H2>COMMANDS</H2> 9429<!--chtml if pinemode="function_key"--> 9430<PRE> 9431Available Commands 9432------------------------------- 9433F1 Show Help Text 9434F3 Exit without selecting anything 9435F4 Select the highlighted address 9436F5 Move highlight to previous address 9437F6 Move highlight to next address 9438F7 Previous page of addresses 9439F8 Next page of addresses 9440F11 Print 9441F12 WhereIs 9442</PRE> 9443<!--chtml else--> 9444<PRE> 9445Navigation General Alpine Commands 9446------------------------- ----------------------- 9447 P Prev Address ? Display this help text 9448 N Next Address E Exit without selecting anything 9449 - Previous page % Print 9450Spc (space bar) Next page 9451 W WhereIs 9452 9453Select Command 9454------------------------------------------------ 9455 S Select the highlighted address 9456</PRE> 9457<!--chtml endif--> 9458 9459<H2>Description of the Select Address Screen</H2> 9460 9461This screen gives you an easy way to select an address from all of 9462the address book entries that match the prefix typed so far. 9463 9464<P><UL> 9465<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 9466</UL> 9467<P> 9468<End of help on this topic> 9469</BODY> 9470</HTML> 9471===== h_select_rule_screen ===== 9472<HTML> 9473<HEAD> 9474<TITLE>SELECT A RULE SCREEN</TITLE> 9475</HEAD> 9476<BODY> 9477<H1>SELECT A RULE SCREEN</H1> 9478<H2>COMMANDS</H2> 9479<!--chtml if pinemode="function_key"--> 9480<PRE> 9481Available Commands 9482------------------------------- 9483F1 Show Help Text 9484F3 Exit without selecting anything 9485F4 Select the highlighted rule 9486F5 Move highlight to previous rule 9487F6 Move highlight to next rule 9488F7 Previous page of rules 9489F8 Next page of rules 9490F11 Print 9491F12 WhereIs 9492</PRE> 9493<!--chtml else--> 9494<PRE> 9495Navigation General Alpine Commands 9496------------------------- ----------------------- 9497 P Prev Rule ? Display this help text 9498 N Next Rule E Exit without selecting anything 9499 - Previous page % Print 9500Spc (space bar) Next page 9501 W WhereIs 9502 9503Select Command 9504------------------------------------------------ 9505 S Select the highlighted rule 9506</PRE> 9507<!--chtml endif--> 9508 9509<H2>Description of the Select Rule Screen</H2> 9510 9511This screen just gives you an easy way to select a rule from all of your 9512defined rules. 9513The list of rules presented is the list of nicknames of all of the rules 9514defined using Setup/Rules. 9515For selecting messages, it is likely that the Indexcolor rules and possibly 9516the Roles rules will be most useful. 9517The others are there also, in case you find a use for them. 9518<P> 9519In order for this to be useful for selecting messages, the nicknames of 9520the rules have to be different. 9521Alpine actually just gets the nickname of the rule that you select and then 9522looks up that rule using the nickname. 9523So if there are duplicate nicknames, the first rule that has that 9524nickname will be used. 9525 9526<P><UL> 9527<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 9528</UL> 9529<P> 9530<End of help on this topic> 9531</BODY> 9532</HTML> 9533===== h_select_priority_screen ===== 9534<HTML> 9535<HEAD> 9536<TITLE>SELECT A PRIORITY SCREEN</TITLE> 9537</HEAD> 9538<BODY> 9539<H1>SELECT A PRIORITY SCREEN</H1> 9540<H2>COMMANDS</H2> 9541<!--chtml if pinemode="function_key"--> 9542<PRE> 9543Available Commands 9544------------------------------- 9545F1 Show Help Text 9546F3 Exit without selecting anything 9547F4 Select the highlighted priority 9548F5 Move highlight to previous priority 9549F6 Move highlight to next priority 9550F7 Previous page of priorities 9551F8 Next page of priorities 9552F11 Print 9553F12 WhereIs 9554</PRE> 9555<!--chtml else--> 9556<PRE> 9557Navigation General Alpine Commands 9558------------------------- ----------------------- 9559 P Prev Priority ? Display this help text 9560 N Next Priority E Exit without selecting anything 9561 - Previous page % Print 9562Spc (space bar) Next page 9563 W WhereIs 9564 9565Select Command 9566------------------------------------------------ 9567 S Select the highlighted priority 9568</PRE> 9569<!--chtml endif--> 9570 9571<H2>Description of the Select Priority Screen</H2> 9572 9573This screen gives you a way to select a priority for the message you are sending. 9574This priority will be placed in the non-standard X-Priority header of your outgoing mail. 9575Some mail programs will display an indication of the priority level to 9576the recipient of the message, some will ignore it. 9577Even in cases where the mail programs of both the sender and the recipient 9578agree on the meaning of this header, keep in mind that it is 9579something that the sender sets so it is only an indication 9580of the priority that the sender attaches to the mail. 9581Alpine can be made to display an indication of this priority in incoming 9582messages by use of one of the tokens 9583(<A HREF="h_index_tokens">Tokens for Index and Replying</A>) 9584PRIORITY, PRIORITYALPHA, or PRIORITY! in the 9585<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option. 9586 9587<P><UL> 9588<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 9589</UL> 9590<P> 9591<End of help on this topic> 9592</BODY> 9593</HTML> 9594===== h_select_keyword_screen ===== 9595<HTML> 9596<HEAD> 9597<TITLE>SELECT A KEYWORD SCREEN</TITLE> 9598</HEAD> 9599<BODY> 9600<H1>SELECT A KEYWORD SCREEN</H1> 9601<H2>COMMANDS</H2> 9602<!--chtml if pinemode="function_key"--> 9603<PRE> 9604Available Commands 9605------------------------------- 9606F1 Show Help Text 9607F3 Exit without selecting anything 9608F4 Select the highlighted keyword 9609F5 Move highlight to previous keyword 9610F6 Move highlight to next keyword 9611F7 Previous page of keywords 9612F8 Next page of keywords 9613F11 Print 9614F12 WhereIs 9615</PRE> 9616<!--chtml else--> 9617<PRE> 9618Navigation General Alpine Commands 9619------------------------- ----------------------- 9620 P Prev Keyword ? Display this help text 9621 N Next Keyword E Exit without selecting anything 9622 - Previous page % Print 9623Spc (space bar) Next page 9624 W WhereIs 9625 9626Select Command 9627------------------------------------------------ 9628 S Select the highlighted keyword 9629</PRE> 9630<!--chtml endif--> 9631 9632<H2>Description of the Select Keyword Screen</H2> 9633 9634This screen just gives you an easy way to select a keyword. 9635The list of keywords presented is the list of all keywords defined in your 9636<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option. 9637If you have given a keyword a nickname, that nickname is displayed 9638instead of the actual keyword. 9639 9640<P><UL> 9641<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 9642</UL> 9643<P> 9644<End of help on this topic> 9645</BODY> 9646</HTML> 9647===== h_select_charset_screen ===== 9648<HTML> 9649<HEAD> 9650<TITLE>SELECT A CHARACTER SET SCREEN</TITLE> 9651</HEAD> 9652<BODY> 9653<H1>SELECT A CHARACTER SET SCREEN</H1> 9654<H2>COMMANDS</H2> 9655<!--chtml if pinemode="function_key"--> 9656<PRE> 9657Available Commands 9658------------------------------- 9659F1 Show Help Text 9660F3 Exit without selecting anything 9661F4 Select the highlighted character set 9662F5 Move highlight to previous character set 9663F6 Move highlight to next character set 9664F7 Previous page of character sets 9665F8 Next page of character sets 9666F11 Print 9667F12 WhereIs 9668</PRE> 9669<!--chtml else--> 9670<PRE> 9671Navigation General Alpine Commands 9672------------------------- ----------------------- 9673 P Prev Character Set ? Display this help text 9674 N Next Character Set E Exit without selecting anything 9675 - Previous page % Print 9676Spc (space bar) Next page 9677 W WhereIs 9678 9679Select Command 9680------------------------------------------------ 9681 S Select the highlighted character set 9682</PRE> 9683<!--chtml endif--> 9684 9685<H2>Description of the Select A Character Set Screen</H2> 9686 9687This screen just gives you an easy way to select a character set from the 9688set of character sets Alpine knows about. 9689The list presented will vary slightly depending on what option you are 9690selecting the character set for. 9691 9692<P><UL> 9693<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 9694</UL> 9695<P> 9696<End of help on this topic> 9697</BODY> 9698</HTML> 9699===== h_select_multcharsets_screen ===== 9700<HTML> 9701<HEAD> 9702<TITLE>SELECT CHARACTER SETS SCREEN</TITLE> 9703</HEAD> 9704<BODY> 9705<H1>SELECT CHARACTER SETS SCREEN</H1> 9706<H2>COMMANDS</H2> 9707<!--chtml if pinemode="function_key"--> 9708<PRE> 9709Available Commands 9710------------------------------- 9711F1 Show Help Text 9712F3 Exit without selecting anything 9713F4 Select the highlighted charset (or chosen charsets in ListMode) 9714F5 Move highlight to previous charset 9715F6 Move highlight to next charset 9716F7 Previous page of charsets 9717F8 Next page of charsets 9718F9 Toggle choices when using ListMode 9719F10 Turn on/off ListMode (makes it easy to choose multiple charsets) 9720F11 Print 9721F12 WhereIs 9722</PRE> 9723<!--chtml else--> 9724<PRE> 9725Navigation General Alpine Commands 9726------------------------- ----------------------- 9727 P Prev Charset ? Display this help text 9728 N Next Charset E Exit without selecting anything 9729 - Previous page % Print 9730Spc (space bar) Next page 9731 W WhereIs 9732 9733Select Command 9734------------------------------------------------ 9735 S Select the highlighted charset (or chosen charsets in ListMode) 9736 L Turn on ListMode (makes it easy to choose multiple charsets) 9737 1 Turn off ListMode 9738 X Toggle choices when using ListMode 9739</PRE> 9740<!--chtml endif--> 9741 9742<H2>Description of the Select Character Set Screen</H2> 9743 9744This screen just gives you an easy way to select a character set or a list of 9745character sets. 9746The list of character sets presented is the list of all character sets known to 9747Alpine. 9748You may select other character sets by typing them in directly. 9749 9750<P><UL> 9751<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 9752</UL> 9753<P> 9754<End of help on this topic> 9755</BODY> 9756</HTML> 9757===== h_select_multkeyword_screen ===== 9758<HTML> 9759<HEAD> 9760<TITLE>SELECT KEYWORDS SCREEN</TITLE> 9761</HEAD> 9762<BODY> 9763<H1>SELECT KEYWORDS SCREEN</H1> 9764<H2>COMMANDS</H2> 9765<!--chtml if pinemode="function_key"--> 9766<PRE> 9767Available Commands 9768------------------------------- 9769F1 Show Help Text 9770F3 Exit without selecting anything 9771F4 Select the highlighted keyword (or chosen keywords in ListMode) 9772F5 Move highlight to previous keyword 9773F6 Move highlight to next keyword 9774F7 Previous page of keywords 9775F8 Next page of keywords 9776F9 Toggle choices when using ListMode 9777F10 Turn on/off ListMode (makes it easy to choose multiple keywords) 9778F11 Print 9779F12 WhereIs 9780</PRE> 9781<!--chtml else--> 9782<PRE> 9783Navigation General Alpine Commands 9784------------------------- ----------------------- 9785 P Prev Keyword ? Display this help text 9786 N Next Keyword E Exit without selecting anything 9787 - Previous page % Print 9788Spc (space bar) Next page 9789 W WhereIs 9790 9791Select Command 9792------------------------------------------------ 9793 S Select the highlighted keyword (or chosen keywords in ListMode) 9794 L Turn on ListMode (makes it easy to choose multiple keywords) 9795 1 Turn off ListMode 9796 X Toggle choices when using ListMode 9797</PRE> 9798<!--chtml endif--> 9799 9800<H2>Description of the Select Keyword Screen</H2> 9801 9802This screen just gives you an easy way to select a keyword or a list of 9803keywords. 9804The list of keywords presented is the list of all keywords defined in your 9805<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option. 9806If you have given a keyword a nickname, that nickname is displayed 9807instead of the actual keyword. 9808 9809<P><UL> 9810<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 9811</UL> 9812<P> 9813<End of help on this topic> 9814</BODY> 9815</HTML> 9816===== h_select_incoming_to_monitor ===== 9817<HTML> 9818<HEAD> 9819<TITLE>SELECT FOLDERS TO CHECK SCREEN</TITLE> 9820</HEAD> 9821<BODY> 9822<H1>SELECT FOLDERS TO CHECK SCREEN</H1> 9823<H2>COMMANDS</H2> 9824<!--chtml if pinemode="function_key"--> 9825<PRE> 9826Available Commands 9827------------------------------- 9828F1 Show Help Text 9829F3 Exit without selecting anything 9830F4 Select the marked folders 9831F5 Move highlight to previous folder 9832F6 Move highlight to next folder 9833F7 Previous page of folders 9834F8 Next page of folders 9835F9 Toggle choices on or off 9836F11 Print 9837F12 WhereIs 9838</PRE> 9839<!--chtml else--> 9840<PRE> 9841Navigation General Alpine Commands 9842------------------------- ----------------------- 9843 P Prev Folder ? Display this help text 9844 N Next Folder ^C exit without changing anything 9845 - Previous page % Print 9846Spc (space bar) Next page 9847 W WhereIs 9848 9849Select Command 9850------------------------------------------------ 9851 S Select the marked folders 9852 X Toggle choices on or off 9853</PRE> 9854<!--chtml endif--> 9855 9856<H2>Description of the Select Folders to Check Screen</H2> 9857 9858This screen is only useful if the feature 9859<A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A> 9860is set. 9861By default, when you set that feature all of your incoming folders 9862will be checked periodically for Unseen messages. 9863By using this screen, you may restrict the set of monitored folders to 9864a subset of all of the incoming folders. 9865<P> 9866Mark the folders you want to monitor for Unseen messages with 9867an "X". 9868When you've finished marking all your selections use the Select 9869command to register your choices. 9870To return to the default of checking all incoming folders 9871delete all folders or unmark all folders. 9872 9873<P><UL> 9874<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 9875</UL> 9876<P> 9877<End of help on this topic> 9878</BODY> 9879</HTML> 9880===== h_role_select ===== 9881<HTML> 9882<HEAD> 9883<TITLE>ROLES SCREEN</TITLE> 9884</HEAD> 9885<BODY> 9886<H1>ROLES SCREEN</H1> 9887<H2>ROLES COMMANDS</H2> 9888<!--chtml if pinemode="function_key"--> 9889<PRE> 9890Available Commands 9891------------------------------- 9892F1 Show Help Text 9893F3 Exit without a selection 9894F4 Select a role to use in composition 9895F5 Move to previous role 9896F6 Move to next role 9897F7 Previous page of roles 9898F8 Next page of roles 9899F11 Change Default Role 9900F12 Whereis (search role nicknames) 9901</PRE> 9902<!--chtml else--> 9903<PRE> 9904Navigation General Alpine Commands 9905------------------------- ----------------------- 9906 P Prev Role ? Display this help text 9907 N Next Role E Exit without a selection 9908 - Previous page 9909Spc (space bar) Next page 9910 W WhereIs (search for word in role nicknames) 9911 9912Select Role Commands 9913------------------------------------------------ 9914 [Return] Select highlighted role 9915 D Change Default Role 9916</PRE> 9917<!--chtml endif--> 9918 9919<H2>Description of the Roles Screen</H2> 9920 9921With this screen you select a role to be used in the composition of a 9922message. 9923Use the Previous and Next commands to highlight the role you wish to 9924use. 9925When you type carriage return you will be placed in the composer using the highlighted role. 9926<P> 9927You don't have any non-default <A HREF="h_rules_roles">roles</A> 9928available unless you set them up. 9929You may do so by using the Setup/Rules command on the MAIN MENU. 9930<P> 9931By using the D command, you may set a default role that will persist until 9932you change it or until you exit Alpine. 9933The D command toggles through three states: set the default role, unset the 9934default role, and leave the default role as it is. 9935<P><UL> 9936<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 9937</UL> 9938<P> 9939<End of help on this topic> 9940</BODY> 9941</HTML> 9942===== h_role_abook_select ===== 9943<HTML> 9944<HEAD> 9945<TITLE>SELECT ADDRESS BOOK SCREEN</TITLE> 9946</HEAD> 9947<BODY> 9948<H1>SELECT ADDRESS BOOK SCREEN</H1> 9949<H2>COMMANDS</H2> 9950<!--chtml if pinemode="function_key"--> 9951<PRE> 9952Available Commands 9953------------------------------- 9954F1 Show Help Text 9955F3 Exit screen without selecting anything 9956F4 Select highlighted address book 9957F5 Move to previous address book 9958F6 Move to next address book 9959F7 Previous page of address books 9960F8 Next page of address books 9961F12 Whereis 9962</PRE> 9963<!--chtml else--> 9964<PRE> 9965Navigation General Alpine Commands 9966------------------------- ----------------------- 9967 P Previous addrbook ? Display this help text 9968 N Next addrbook 9969 - Previous page 9970Spc (space bar) Next page 9971 W WhereIs 9972 9973Select Role Commands 9974------------------------------------------------ 9975 S Select highlighted address book 9976 E Exit screen without selecting anything 9977</PRE> 9978<!--chtml endif--> 9979 9980<H2>Description of the Select Address Book Screen</H2> 9981 9982This screen helps you select one of your address books. 9983Use the Previous and Next commands to highlight the address book you wish to 9984select. 9985<P><UL> 9986<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 9987</UL> 9988<P> 9989<End of help on this topic> 9990</BODY> 9991</HTML> 9992======== h_rule_patterns ============= 9993<HTML> 9994<HEAD> 9995<TITLE>PATTERNS</TITLE> 9996</HEAD> 9997<BODY> 9998<H1>PATTERNS</H1> 9999Patterns are used with Roles, Filtering, Index Coloring, 10000Scoring, Other Rules, and Search Rules. 10001Patterns are compared with a message to see if there is a match. 10002For Filtering, the messages being checked are all the messages in the 10003folder, one at a time. 10004For Index Line Coloring, each message that is visible on the screen is 10005checked for matches with the Index Coloring Patterns. 10006Roles are used with the Reply, Forward, and Compose commands. 10007For Reply, the message used to compare the Pattern with is the message 10008being replied to; 10009for Forward, the message used to compare the Pattern with is the message 10010being forwarded; 10011and for Compose, there is no message, so the parts of the Pattern that depend 10012on a message (everything other than Current Folder Type and the 10013Beginning of Month and Year) 10014are not used. 10015Only the Current Folder Type matters for Compose (plus the Beginning of 10016Month or Year, which you wouldn't usually use for a Role). 10017For Scoring, the message being scored is compared with all of the Score 10018Patterns, and the Score Values from the ones that match are added together to 10019get the message's score. 10020For Other Rules, there is no message. Only the Current Folder Type is checked 10021for Other Rules. 10022<P> 10023Each Pattern has several possible parts, all of which are optional. 10024In order for there to be a match, <EM>ALL</EM> of the 10025<EM>defined</EM> parts of the Pattern must match the message. 10026If a part is not defined it is considered a match, but note that a filtering 10027Pattern must have at least one defined part or it will be ignored. 10028For example, if the To pattern is not defined it will be 10029displayed as 10030<P> 10031<CENTER>To pattern = <No Value Set></CENTER> 10032<P> 10033That is considered a match because it is not defined. 10034This means that the Pattern with nothing defined is a match if the 10035Current Folder Type matches, but there is an exception that was mentioned 10036in the previous paragraph. 10037Because filtering is a potentially destructive action, filtering Patterns 10038with nothing other than Current Folder Type defined are ignored. 10039If you really want a filtering Pattern to match all messages (subject to 10040Current Folder Type) the best way to do it is to define a Score interval 10041that includes all possible scores. 10042This would be the score interval <SAMP>(-INF,INF)</SAMP>. 10043This can be used even if you haven't defined any rules to Set Scores. 10044<P> 10045There are six predefined header patterns called the To, From, Sender, Cc, News, 10046and Subject patterns. 10047Besides those six predefined header patterns, you may add 10048additional header patterns with header fieldnames of your choosing. 10049You add an extra header pattern by placing the cursor on one of the 10050patterns while in the role editor and using the "eXtraHdr" command. 10051The Recip pattern is a header pattern that stands for Recipient (To OR Cc) 10052and the Partic pattern is a header pattern that stands for 10053Participant (From OR To OR Cc). 10054(Defining the Recip pattern does not have the same effect as defining both 10055the To and Cc patterns. Recip is To <EM>OR</EM> Cc, not To <EM>AND</EM> Cc.) 10056Similar to the header patterns are the AllText pattern and the BodyText pattern. 10057Instead of comparing this pattern's text against only the contents of 10058a particular header field, the text for the AllText pattern is compared 10059with text anywhere in the message's header or body, and the text for the 10060BodyText pattern is compared with text anywhere in the message's body. 10061<P> 10062Any of the header patterns, the AllText pattern, or the BodyText pattern may be negated with the 10063"!" "toggle NOT" command. 10064You can tell that <EM>NOT</EM> has been turned on by looking for the character 10065"!" at the beginning of the pattern line. 10066When the "!" is present, it reverses the meaning of the match. 10067That is, if the pattern matches then it is considered to NOT be a match, and 10068if it does not match it is considered to be a match. 10069<P> 10070Don't make the mistake of putting the "!" in the data field for 10071a pattern. 10072For example, if you type the characters "!urgent" into the Subject 10073pattern, the pattern will look like: 10074<P> 10075<PRE> 10076 Subject pattern = !urgent 10077</PRE> 10078<P> 10079This means you want to match the 7 character sequence "!urgent". 10080In order to match messages that do not have "urgent" in 10081their Subject field, first type the characters "urgent" followed 10082by carriage return for the value of the Subject pattern, then negate it 10083by typing the "!" command. 10084It should look like 10085<P> 10086<PRE> 10087 ! Subject pattern = urgent 10088</PRE> 10089<P> 10090The contents of each of these header patterns (or the AllText or BodyText patterns) may 10091be a complete email address, part of an address, or a random set of 10092characters to match against. 10093It may also be a list of such patterns, which means you 10094are looking for a match against the first pattern in the list <EM>OR</EM> 10095the second pattern <EM>OR</EM> the third and so on. 10096For example, a Subject pattern equal to 10097<P> 10098<PRE> 10099 Subject pattern = urgent 10100 emergency 10101 alert 10102</PRE> 10103<P> 10104would match all messages with a subject that contained at least one 10105of those words. 10106It would also match subjects containing the words "alerts" or 10107"Urgently". 10108<P> 10109The same example with "NOT" turned on would be 10110<P> 10111<PRE> 10112 ! Subject pattern = urgent 10113 emergency 10114 alert 10115</PRE> 10116<P> 10117which would match all messages with a subject that did <EM>NOT</EM> contain any of 10118those words. 10119You can use the "Add Value" command to add new words to the list, 10120or you can enter them as a comma-separated list. 10121<P> 10122(It is not possible to specify two patterns that must <EM>BOTH</EM> be 10123present for a match. 10124It is only possible to specify that <EM>EITHER</EM> pattern1 <EM>OR</EM> 10125pattern2 must be present, 10126and that is exactly what using a list does.) 10127<P> 10128The "Current Folder Type" and the "Score Interval" are 10129also part of the Pattern, although the "Score Interval" is not used 10130when checking for matches for Scoring. 10131There are five similar settings that relate to the status of the message. 10132These settings rely on the message being New or not, Deleted or not, 10133Answered or not, Important or not, and Recent or not. 10134There are also some other miscellaneous settings. 10135The first is the Age of the message in days. 10136Another is the Size of the message, in bytes. 10137The third is a setting that detects whether or not the Subject of a 10138message contains raw 8-bit characters (unencoded characters with the most 10139significant bit set). 10140There is a setting that detects whether or not this is the first time 10141Alpine has been run this month (doesn't depend on individual messages), 10142and another that detects whether or not this is the first time Alpine has 10143been run this year. 10144Other parts of the Pattern detect whether or not the From address of a 10145message appears in your address book, whether or not certain keywords 10146are set for a message, and whether or not certain character sets are 10147used in a message. 10148 10149<H2>Parts of a Pattern</H2> 10150 10151<H3>Header patterns</H3> 10152 10153A header pattern is simply text that is searched for in the corresponding 10154header field. 10155For example, if a Pattern has a From header pattern with the value 10156"@company.com", then only messages that have a From header 10157that contains the text "@company.com" will be possible 10158matches. 10159Matches don't have to be exact. 10160For example, if the relevant field of a message contains the text 10161"mailbox@domain" somewhere 10162in it, then header patterns of "box", or "x@d", or 10163"mailbox@domain" are all matches. 10164<P> 10165All parts of the Pattern must match so, for example, 10166if a message matches a defined 10167From pattern, it still must be checked against the other parts of the 10168Pattern that have been defined. 10169The To header pattern is a slightly special case. 10170If the message being checked has a Resent-To header 10171and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on, the addresses 10172there are used in place of the addresses in the To header. 10173This is only true for the To header. 10174Resent-cc and Resent-From headers are never used unless you add them 10175with the eXtraHdrs command. 10176<P> 10177The meaning of a header pattern may be negated with the 10178"!" "toggle NOT" command. 10179You can tell that <EM>NOT</EM> has been turned on by looking for the character 10180"!" at the beginning of the pattern line. 10181It would look something like 10182<P> 10183<PRE> 10184 ! From pattern = susan@example.com 10185</PRE> 10186<P> 10187When the "!" is present, it reverses the meaning of the match. 10188<P> 10189If you want to check for the presence of a header field but don't care 10190about its value, then 10191the empty pattern that you get by entering a pair of 10192double quotes ("") should match any message that 10193has the corresponding header field. 10194 10195<H3><A NAME="pattern_alltext">AllText patterns</A></H3> 10196 10197AllText patterns are just like header patterns except that the text is 10198searched for anywhere in the message's headers or body, not just in the 10199contents of a particular header field. 10200<P> 10201 10202<H3><A NAME="pattern_bodytext">BodyText patterns</A></H3> 10203 10204BodyText patterns are just like header patterns except that the text is 10205searched for anywhere in the message's body, not just in the 10206contents of a particular header field. 10207<P> 10208 10209If there is more than one header pattern or AllText pattern or BodyText pattern 10210for which you want to take the 10211same action there is a shorthand notation that may be used. 10212Any of these patterns may be a list of patterns instead of 10213just a single pattern. 10214If any one of the patterns in the list matches the message 10215then it is considered a match. 10216For example, if "company1" and "company2" both required 10217you to use the same role when replying to messages, you might have 10218a To pattern that looks like 10219<P> 10220<PRE> 10221 To pattern = company1.com 10222 company2.com 10223</PRE> 10224<P> 10225This means that if the mail you are replying to was addressed to 10226either "anything@company1.com" or "anything@company2.com", 10227then this Pattern is a match and the same actions will be taken. 10228<P> 10229The meaning of an AllText or BodyText pattern may be negated with the 10230"!" "toggle NOT" command. 10231You can tell that <EM>NOT</EM> has been turned on by looking for the character 10232"!" at the beginning of the pattern line. 10233When the "!" is present, it reverses the meaning of the match. 10234<P> 10235A technicality: Since comma is the character used to separate multiple values 10236in any of the fields that may have multiple values (such as header patterns, 10237AllText patterns, BodyText patterns, keywords, folder lists, and so on), 10238you must escape comma with a 10239backslash (\) if you want to include a literal comma in one of those fields. 10240In other words, if you type a backslash followed by a comma it will 10241be interpreted as a comma by Alpine, instead of as a separator between 10242pattern values. 10243All other backslashes (those not followed by a comma) are literal 10244backslashes and should not be escaped. 10245It's unlikely you'll ever need to enter a literal comma or backslash in 10246any of the patterns. 10247 10248<H3><A NAME="pattern_current_folder">Current Folder Type</A></H3> 10249 10250The "Current Folder Type" may be set to one of four different 10251values: "Any", "News", "Email", or 10252"Specific". 10253If the value is set to "News", then the 10254Pattern will only match if the currently open folder is a newsgroup. 10255The value "Email" only matches if the current folder is not news and 10256the value "Any" causes any folder to match. 10257If the value of "Current Folder Type" is set to "Specific", 10258then you must fill in a value for "Folder", which is on the line 10259below the "Specific" line. 10260In this case you will only get a match if the currently open folder is 10261the specific folder you list. 10262You may give a list of folders instead of just a single 10263folder name, in which case the Pattern will match if the open folder is 10264any one of the folders in the list. 10265The name of each folder in the list may be either "INBOX", 10266the technical specification 10267of the folder (like what appears in your configuration file) or, if the 10268folder is one of your incoming folders, it may be the nickname you've given 10269the folder. 10270Here are some samples of specific folder names: 10271<P> 10272<CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER> 10273<P> 10274<CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER> 10275<P> 10276<CENTER><SAMP>mail/local-folder</SAMP></CENTER> 10277<P> 10278The easiest way to fill in the "Folder" field is to use 10279the "T" command that is available when the "Folder" line is 10280highlighted, or to use the "Take" command with the configuration 10281feature 10282<A HREF="h_config_enable_role_take">"<!--#echo var="FEAT_enable-rules-under-take"-->"</A> 10283turned on. 10284<P> 10285When reading a newsgroup, there may be a performance penalty 10286incurred when collecting the information necessary to check whether 10287or not a Pattern matches a message. 10288For this reason, the default Current Folder Type is set to "Email". 10289If you have Patterns with a Current Folder Type of either 10290"Any" or "News" and those Patterns are used for 10291Index Line Coloring or Scoring, you may experience 10292slower screen redrawing in the MESSAGE INDEX screen when in a newsgroup. 10293 10294<H3><A NAME="pattern_age_interval">Age Interval</A></H3> 10295 10296The "Age Interval" may be set to an interval of message 10297ages that should be considered a match. 10298Like the other parts of the Pattern, if it is unset it will be ignored. 10299The Age Interval looks like 10300<P> 10301<CENTER><SAMP>(min_age,max_age)</SAMP></CENTER> 10302<P> 10303where "min_age" and "max_age" are integers greater 10304than or equal to zero. 10305The special value "INF" may be used for 10306the max value. It represents infinity. 10307<P> 10308Actually, this option may be defined as a list of intervals instead 10309of just a single interval. 10310The list is separated by commas. 10311It can look like 10312<P> 10313<CENTER><SAMP>(min_age1,max_age1),(min_age2,max_age2),...</SAMP></CENTER> 10314<P> 10315When there is an Age Interval defined, it is a match if the age, in days, of 10316the message is contained in any of the intervals. 10317The intervals include both endpoints. 10318<P> 10319Even though this option is called Age, it isn't actually 10320the <EM>age</EM> of the message. 10321Instead, it is how many days ago the message arrived in one of your folders. 10322If the current time is a little past midnight, then a message that arrived 10323just before midnight arrived yesterday, even though the message is only 10324a few minutes old. 10325By default, the date being used is not the date in the Date 10326header of the message. 10327It is the date that the message arrived in one of your folders. 10328When you Save a message from one folder to another that arrival date 10329is preserved. 10330If you would like to use the date in the Date header that is possible. 10331Turn on the option 10332<A HREF="h_config_filt_opts_sentdate">"Use-Date-Header-For-Age"</A> 10333near the bottom of the rule definition. 10334A value of 0 is today, 1 is yesterday, 2 is the day before yesterday, and so on. 10335 10336<H3><A NAME="pattern_size_interval">Size Interval</A></H3> 10337 10338The "Size Interval" may be set to an interval of message 10339sizes that should be considered a match. 10340Like the other parts of the Pattern, if it is unset it will be ignored. 10341The Size Interval looks like 10342<P> 10343<CENTER><SAMP>(min_size,max_size)</SAMP></CENTER> 10344<P> 10345where "min_size" and "max_size" are integers greater 10346than or equal to zero. 10347The special value "INF" may be used for 10348the max value. It represents infinity. 10349<P> 10350Actually, this option may be defined as a list of intervals instead 10351of just a single interval. 10352The list is separated by commas. 10353It can look like 10354<P> 10355<CENTER><SAMP>(min_size1,max_size1),(min_size2,max_size2),...</SAMP></CENTER> 10356<P> 10357When there is a Size Interval defined, it is a match if the size, in bytes, of 10358the message is contained in any of the intervals. 10359The intervals include both endpoints. 10360 10361<H3><A NAME="pattern_score_interval">Score Interval</A></H3> 10362 10363The "Score Interval" may be set to an interval of message 10364scores that should be considered a match. 10365Like the other parts of the Pattern, if it is unset it will be ignored. 10366The Score Interval looks like 10367<P> 10368<CENTER><SAMP>(min_score,max_score)</SAMP></CENTER> 10369<P> 10370where "min_score" and "max_score" are positive or 10371negative integers, with min_score less than or equal to max_score. 10372The special values "-INF" and "INF" may be used for 10373the min and max values to represent negative and positive infinity. 10374<P> 10375Actually, a list of intervals may be used if you wish. 10376A list would look like 10377<P> 10378<CENTER><SAMP>(min_score1,max_score1),(min_score2,max_score2),...</SAMP></CENTER> 10379<P> 10380When there is a Score Interval defined, it is a match if the score for 10381the message is contained in any of the intervals in the list. 10382The intervals include the endpoints. 10383The score for a message is calculated by looking at every Score rule defined and 10384adding up the Score Values for the ones that match the message. 10385When deciding whether or not a Pattern matches a message for purposes of 10386calculating the score, the Score Interval is ignored. 10387 10388<H3><A NAME="pattern_message_status">Message Status</A></H3> 10389 10390There are five separate message status settings. 10391By default, all five are set to the value "Don't care", which 10392will match any message. 10393The value "Yes" means that the particular status must be true 10394for a match, and the value "No" means that the particular 10395status must not be true for a match. 10396For example, one of the five Message Status settings is whether a message 10397is marked Important or not. 10398A "Yes" means that the message must be Important to be 10399considered a match and "No" means that the message must not be 10400Important to be considered a match. 10401The same is true of the other four message status settings that depend 10402on whether or not the message is New; whether the message has 10403been Answered or not; whether the message has been Deleted or not, and 10404whether the message is Recent or not. 10405<P> 10406The nomenclature for New and Recent is a bit confusing: 10407<P> 10408New means that the message is Unseen. 10409It could have been in your mailbox for a long time but if you haven't looked 10410at it, it is still considered New. 10411That matches the default Alpine index display that shows an N for such a 10412message. 10413<P> 10414Recent means that the message was added to this folder since the last time 10415you opened the folder. 10416Alpine also shows an N by default for these types of messages. 10417If you were to run two copies of Alpine that opened a folder one right after 10418the other, a message would only show up as Recent in (at most) the first 10419Alpine session. 10420 10421<H3><A NAME="pattern_message_keywords">Message Keywords</A></H3> 10422 10423Keywords are similar to Message Status, but they are chosen by the user. 10424Provided the mail server allows for it, you may add a set of possible keywords 10425to a folder and then you may set those keywords or not for each message 10426in the folder (see <A HREF="h_common_flag">Flag Command</A>). 10427The syntax of this part of the Pattern is similar to the header patterns. 10428It is a list of keywords. 10429The Keyword part of the Pattern is a match if the message has any of 10430the keywords in the list set. 10431Like other parts of the Pattern, if this is unset it will be ignored. 10432 10433<H3><A NAME="pattern_message_charsets">Message Character Sets</A></H3> 10434 10435A message may use one or more character sets. 10436This part of the Pattern matches messages that make use of one or more of 10437the character sets specified in the pattern. 10438It will be considered a match if a message uses any of the character 10439sets in the list you give here. 10440 10441<P> 10442Besides actual character set names (for example, ISO-8859-7, KOI8-R, or 10443GB2312) you may also use some shorthand names that Alpine provides. 10444These names are more understandable shorthand names for sets of 10445character set names. 10446Two examples are "Cyrillic" and "Greek". 10447Selecting one of these shorthand names is equivalent to selecting all of 10448the character sets that make up the set. 10449You can see all of these shorthand names and the lists of character sets 10450they stand for by typing the "T" command with the Character 10451Set pattern highlighted. 10452The syntax of this part of the Pattern is similar to the header patterns 10453and the Message Keywords pattern. 10454It is a list of character sets (or shorthand names). 10455The Character Set part of the Pattern is a match if the message uses any 10456of the character sets in the list. 10457Like other parts of the Pattern, if this is unset it will be ignored. 10458 10459<H3><A NAME="pattern_8bit_subject">Raw 8-bit in Subject</A></H3> 10460 10461It seems that lots of unwanted email contains unencoded 8-bit characters 10462in the Subject. 10463Normally, characters with the 8th bit set are not allowed in the Subject 10464header unless they are MIME-encoded. 10465This option gives you a way to match messages that have Subjects that 10466contain unencoded 8-bit characters. 10467By default, the value of this option is "Don't care", which 10468will match any message. 10469The value "Yes" means that there must be raw 8-bit characters in 10470the Subject of the message in order for there to be a match, 10471and the value "No" is the opposite. 10472Setting this option will affect performance in large folders because the 10473subject of each message in the folder has to be checked. 10474 10475<H3><A NAME="pattern_bom">Beginning of Month</A></H3> 10476 10477This option gives you a way to take some action once per month. 10478By default, the value of this option is "Don't care", which 10479will always match. 10480The value "Yes" means that this must be the first time Alpine has 10481been run this month in order to count as a match, 10482and the value "No" is the opposite. 10483 10484<H3><A NAME="pattern_boy">Beginning of Year</A></H3> 10485 10486This option gives you a way to take some action once per year. 10487By default, the value of this option is "Don't care", which 10488will always match. 10489The value "Yes" means that this must be the first time Alpine has 10490been run this year in order to count as a match, 10491and the value "No" is the opposite. 10492 10493<H3><A NAME="pattern_abookfrom">Address in Address Books</A></H3> 10494 10495This option gives you a way to match messages that have an address 10496that is in one of your address books. 10497Only the simple entries in your address books are searched. 10498Address book distribution lists are ignored! 10499By default, the value of this option is "Don't care", which 10500will match any message. 10501The value "Yes, in any address book" means the address 10502from the message must be in at least one of your 10503address books in order to be a match. 10504The value "No, not in any address book" 10505means none of the addresses may 10506be in any of your address books in order to be a match. 10507The values "Yes, in specific address books" and 10508"No, not in any of specific address books" are similar but instead 10509of depending on all address books you are allowed to give a list of address 10510books to look in. 10511The addresses from the message that are checked for are determined by the 10512setting you have for "Types of addresses to check for in address book". 10513If you set this to "From" the From address from the message will 10514be looked up in the address book. 10515If you set it to only "To" then the To addresses will be used. 10516If any of the To addresses are in the address book then it is considered 10517a match for "Yes" or not a match for "No". 10518You could set it to both From and To, in which case all of the From and To 10519addresses are used. 10520The "Reply-To" and "Sender" cases are a little unusual. 10521Due to deficiencies in our tools, Reply-To uses the Reply-To address if it 10522exists or the From address if there is no Reply-To address. 10523Same for the Sender address. 10524Setting this option may affect performance in large folders because the 10525From and Reply-To of each message in the folder have to be checked. 10526 10527<H3><A NAME="pattern_categorizer">Categorizer Command</A></H3> 10528 10529This is a command that is run with its standard input set to the message 10530being checked and its standard output discarded. 10531The full directory path should be specified. 10532The command will be run and then its exit status will be checked against 10533the Exit Status Interval, which defaults to just the value zero. 10534If the exit status of the command falls in the interval, it is considered 10535a match, otherwise it is not a match. 10536<P> 10537 10538This option may actually be a list of commands. 10539The first one that exists and is executable is used. 10540That makes it possible to use the same configuration with Unix Alpine and 10541PC-Alpine. 10542<P> 10543 10544If none of the commands in the list exists and is executable then the rule 10545is <EM>not</EM> a match. 10546If it is possible that the command may not exist, you should be careful 10547to structure your rules so that nothing destructive 10548happens when the command does not exist. 10549For example, you might have a filter that filters away spam when there is 10550a match but does nothing when there is not a match. 10551That would continue to work correctly if the command didn't exist. 10552However, if you have a filter that filters away spam when there is not 10553a match and keeps it when there is a match, that would filter everything 10554if the categorizer command didn't exist. 10555<P> 10556Here is an <A HREF="h_config_role_cat_cmd_example">example</A> 10557setup for the bogofilter filter. 10558 10559<P> 10560<End of help on this topic> 10561</BODY> 10562</HTML> 10563===== h_rules_roles ===== 10564<HTML> 10565<HEAD> 10566<TITLE>SETUP ROLES SCREEN</TITLE> 10567</HEAD> 10568<BODY> 10569<H1>SETUP ROLES SCREEN</H1> 10570<H2>SETUP ROLES COMMANDS</H2> 10571<!--chtml if pinemode="function_key"--> 10572<PRE> 10573Available Commands -- Group 1 Available Commands -- Group 2 10574------------------------------- ------------------------------ 10575F1 Show Help Text F1 Show Help Text 10576F2 See commands in next group F2 See commands in next group 10577F3 Back to MAIN Alpine menu 10578F4 Change configuration for role 10579F5 Move to previous role F5 Include file in role config 10580F6 Move to next role F6 Exclude file from config 10581F7 Previous page of roles 10582F8 Next page of roles 10583F9 Add new role F9 Replicate existing role 10584F10 Delete existing role 10585F11 Shuffle the order of roles 10586F12 Whereis (search role nicknames) 10587</PRE> 10588<!--chtml else--> 10589<PRE> 10590Navigation General Alpine Commands 10591------------------------- ----------------------- 10592 P Prev Role ? Display this help text 10593 N Next Role E Back to MAIN Alpine menu 10594 - Previous page 10595Spc (space bar) Next page 10596 W WhereIs (search for word in role nicknames) 10597 10598Setup Roles Commands 10599------------------------------------------------ 10600 A Add new role $ Shuffle the order of roles 10601 D Delete existing role C Change configuration for highlighted role 10602 R Replicate existing role 10603 I Include file in role config X Exclude file from role config 10604</PRE> 10605<!--chtml endif--> 10606 10607<H2>Description of the Setup Roles Screen</H2> 10608 10609This screen lets you add, delete, modify, or change the order of the rules 10610that determine the role you are playing when composing a message. 10611<P> 10612You may play different roles depending on who you are replying to. 10613For example, if you are replying to a message addressed to help-desk you 10614may be acting as a Help Desk Worker. 10615That role may require that you use a different return address and/or 10616a different signature. 10617<P> 10618Roles are optional. 10619If you set up roles they work like this: Each role has a set of 10620"Uses", which indicate whether or not a role is eligible to be 10621considered for a particular use; a "Pattern", 10622which is used to decide which of the eligible roles is used; and a set 10623of "Actions", which are taken when that role is used. 10624When you reply to a message, the message you are replying to is compared 10625with the Patterns of the roles marked as eligible for use when replying. 10626The comparisons start with the first eligible role and keep going until there 10627is a match. 10628If a match is found, the matching role's Actions are taken. 10629<P> 10630It is also possible to set a default role and to change that role during 10631your Alpine session. 10632When you start Alpine no default role will be set. 10633You may set or change the current default role by using the "D" 10634command in the role selection screen. 10635You'll see that screen while composing a message and being asked to select 10636a role. 10637An easy way to get to that screen is to use the <A HREF="h_common_role">Role Command</A> to 10638compose a message. 10639You may find a default role useful if you normally perform the duties of one 10640of your roles for a while, then you switch to another role and stay in the 10641new role for another period of time. 10642It may be easier than using the Role Command to select the role each time you 10643compose a message. 10644 10645<H2>Role Uses</H2> 10646 10647There are three types of use to be configured; 10648one for Replying, one for Forwarding, and one for Composing. 10649These indicate whether or not you want a role to be considered when you 10650type the Reply, Forward, or Compose commands. 10651(The Role command is an alternate form of the Compose command, and it is 10652not affected by these settings.) 10653Each of these Use types has three possible values. 10654The value "Never" 10655means that the role will never be considered as a candidate for use with 10656the corresponding command. 10657For example, if you set a role's Reply Use to Never, then when you Reply to 10658a message, that role won't even be considered. 10659(That isn't quite true. If the message you are replying to matches some other 10660role that requires confirmation, 10661then there will be a ^T command available which allows you to select a role 10662from all of your roles, not just the reply-eligible roles.) 10663<P> 10664 10665The options "With confirmation" and "Without confirmation" 10666both mean that you do want to consider this role when using the corresponding 10667command. 10668For either of these settings the role's Pattern will 10669be checked to see if it matches the message. 10670For Reply Use, the message used to compare the Pattern with is the message 10671being replied to. 10672For Forward Use, the message used to compare the Pattern with is the message 10673being forwarded. 10674For Compose Use, there is no message, so the parts of the Pattern that depend 10675on a message (everything other than Current Folder Type) are ignored. 10676In all cases, the Current Folder Type is checked if defined. 10677If there is a match then this role will either be used without confirmation 10678or will be the default when confirmation is asked for, depending on 10679which of the two options is selected. 10680If confirmation is requested, you will have a chance to 10681choose No Role instead of the offered role, or to 10682change the role to any one of your other roles (with the ^T command). 10683 10684<H2>Role Patterns</H2> 10685 10686In order to determine whether or not a message matches a role the message is 10687compared with the Role's Pattern. 10688These Patterns are the same for use with Roles, Filtering, Index Coloring, 10689Scoring, Other Rules, and Search Rules, so are described in only one place, 10690"<A HREF="h_rule_patterns">here</A>". 10691<P> 10692Since header patterns, AllText patterns, and BodyText patterns that are unset are ignored, 10693a role that has all header patterns unset, the AllText pattern unset, 10694the BodyText pattern unset, 10695the Score Interval unset, and the Current Folder Type set to 10696"Any" may be used as a default role. 10697It should be put last in the list of roles since the matching 10698starts at the beginning and proceeds until one of the roles is a match. 10699If no roles at all match, then Alpine will 10700use its regular methods of defining the role. 10701If you wanted to, you could define a different "default" role 10702for Replying, Forwarding, and Composing by setting the 10703"Use" fields appropriately. 10704 10705<H2>Role Actions</H2> 10706 10707Once a role match is found, the role's Actions are taken. 10708For each role there are several possible actions that may be defined. 10709They are actions to set the From address, the Reply-To address, 10710the Fcc, the Signature, the Template file, and Other Headers. 10711 10712<H3>Set From</H3> 10713 10714The From address is the address used on the From line of the message 10715you are sending. 10716 10717<H3>Set Reply-To</H3> 10718 10719The Reply-To address is the address used on the Reply-To line of the message 10720you are sending. 10721You don't need a Reply-To address unless it is different from the From address. 10722 10723<H3>Set Other Headers</H3> 10724 10725If you want to set the value of the From or Reply-To headers, use 10726the specific fields "Set From" or "Set Reply-To". 10727If you want to set the values of other headers, use this field. 10728This field is similar to the 10729<A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A> configuration option. 10730Each header you specify here must include the header tag 10731("To:", "Approved:", etc.) 10732and may optionally include a value for that header. 10733It is different from the <!--#echo var="VAR_customized-hdrs"--> in that the value you give 10734for a header here will replace any value that already exists. 10735For example, if you are Replying to a message there will be at least one 10736address in the To header (the address you are Replying to). 10737However, if you Reply using a role that sets the To header, that role's 10738To header value will be used instead. 10739 10740<H3>Set Fcc</H3> 10741 10742The Fcc is used as the Fcc for the message you are sending. 10743 10744<H3>Set Signature or Set LiteralSig</H3> 10745 10746The Signature is the name of a file to be used as the signature file when 10747this role is being used. 10748If the name of the file has a vertical bar following it (|) 10749then it is assumed that the file is a program that should be run to 10750produce the signature. 10751If the LiteralSig is set, then it is used instead of the signature file. 10752LiteralSig is just a different way to store the signature. 10753It is stored in the pine configuration file instead of in a separate 10754signature file. 10755If the <A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A> option is defined 10756either in the role or as the default signature in the Setup/Config screen, 10757then the signature file is ignored. 10758 10759<H3>Set Template</H3> 10760 10761A Template is the name of a file to be included in the message when this 10762role is being used. 10763If the name of the file has a vertical bar following it (|) 10764then it is assumed that the file is a program that should be run to 10765produce the template. 10766 10767<P> 10768Both signature files and template files may be stored remotely on an IMAP 10769server. 10770In order to do that you just give the file a remote name. 10771This works just like the regular 10772<A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A> 10773option that is configured from the Setup/Configuration screen. 10774A remote signature file name might look like: 10775<P> 10776<CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/sig3</SAMP></CENTER> 10777<P> 10778Once you have named the remote signature or template file you create its 10779contents by using the "F" "editFile" command when the 10780cursor is on the "Set Signature" or "Set Template" 10781line of the role editor. 10782 10783<P> 10784Both signature files and template files (or the output of signature programs 10785and template file programs) may contain special tokens 10786that are replaced with contents 10787that depend on the message being replied to or forwarded. 10788See the help for the individual fields inside the role editor for more 10789information on tokens. 10790 10791<H3>Use SMTP Server</H3> 10792 10793If this field has a value, then it will be used as the SMTP server 10794to send mail when this role is being used (unless the SMTP server variable 10795is set in the system-wide fixed configuration file). 10796It has the same semantics as the 10797<A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A> 10798variable in the Setup/Config screen. 10799When you postpone the composition this SMTP server list will be saved 10800with the postponed composition and it cannot be changed later. 10801Because of that, you may want to make this a list of SMTP servers 10802with the preferred server at the front of the list and alternate servers 10803later in the list. 10804 10805<P> 10806If any of the actions are left unset, then the action depends on what 10807is present in the "Initialize settings using role" field. 10808If you've listed the nickname of another one of your roles there, then the 10809corresponding action from that role will be used here. 10810If that action is also blank, or if there is no nickname specified, 10811then Alpine will do whatever it normally does to set these actions. 10812This depends on other configuration options and features you've set. 10813 10814<H2>Command Descriptions</H2> 10815 10816<H3>Add</H3> 10817 10818The Add command is used to add a new role definition to your set of 10819roles. 10820The new role will be added after the highlighted role. 10821 10822<H3>Delete</H3> 10823 10824The Delete command deletes the currently highlighted role. 10825 10826<H3>Change</H3> 10827 10828The Change command lets you edit the nickname, Uses, Pattern, 10829and Actions of the currently highlighted role. 10830 10831<H3>Shuffle</H3> 10832 10833The Shuffle command allows you to change the order of the roles. 10834You may move the currently highlighted role up or down in the list. 10835The order of the roles is important since the roles are tested for a 10836match starting with the first role and continuing until a match is found. 10837You should place the roles with more specific Patterns near the beginning 10838of the list, and those with more general Patterns near the end so that 10839the more specific matches will happen when appropriate. 10840 10841<H3>Replicate</H3> 10842 10843The Replicate command is used to copy an existing role and modify it. 10844The new role will be added after the highlighted role. 10845 10846<H3>IncludeFile</H3> 10847 10848The IncludeFile command allows you to add a roles file to your configuration. 10849Usually, your roles will be contained in your Alpine configuration file. 10850If you wish, some or all of your roles may be stored in a separate file. 10851If a roles file already exists (maybe it was made by somebody else using 10852Alpine), you may insert it before the currently highlighted role. 10853You may also insert an empty file or a file that does not yet exist. 10854Once you have an empty roles file in your configuration, you may use 10855the Shuffle command to move roles into it. 10856In fact, that's the only way to get the initial role into the file. 10857 10858<H3>eXcludeFile</H3> 10859 10860The eXcludeFile command removes a roles file from your roles configuration. 10861A limitation of the program is that in order to exclude a roles file 10862that file must have at least one role 10863in it, otherwise you won't be able to highlight a line in the file. 10864So you may have to add a dummy role to the file in order to exclude the file. 10865<P><UL> 10866<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 10867</UL> 10868<P> 10869<End of help on this topic> 10870</BODY> 10871</HTML> 10872===== h_rules_other ===== 10873<HTML> 10874<HEAD> 10875<TITLE>SETUP OTHER RULES SCREEN</TITLE> 10876</HEAD> 10877<BODY> 10878<H1>SETUP OTHER RULES SCREEN</H1> 10879<H2>SETUP OTHER RULES COMMANDS</H2> 10880<!--chtml if pinemode="function_key"--> 10881<PRE> 10882Available Commands -- Group 1 Available Commands -- Group 2 10883------------------------------- ------------------------------ 10884F1 Show Help Text F1 Show Help Text 10885F2 See commands in next group F2 See commands in next group 10886F3 Back to MAIN Alpine menu 10887F4 Change configuration for rule 10888F5 Move to previous rule F5 Include file in rule config 10889F6 Move to next rule F6 Exclude file from config 10890F7 Previous page of rules 10891F8 Next page of rules 10892F9 Add new rule F9 Replicate existing rule 10893F10 Delete existing rule 10894F11 Shuffle the order of rules 10895F12 Whereis (search rule nicknames) 10896</PRE> 10897<!--chtml else--> 10898<PRE> 10899Navigation General Alpine Commands 10900------------------------- ----------------------- 10901 P Prev rule ? Display this help text 10902 N Next rule E Back to MAIN Alpine menu 10903 - Previous page 10904Spc (space bar) Next page 10905 W WhereIs (search for word in rule nicknames) 10906 10907Setup Other Rules Commands 10908------------------------------------------------ 10909 A Add new rule $ Shuffle the order of rules 10910 D Delete existing rule C Change configuration for highlighted rule 10911 R Replicate existing rule 10912 I Include file in rule config X Exclude file from rule config 10913</PRE> 10914<!--chtml endif--> 10915 10916<H2>Description of the Setup Other Rules Screen</H2> 10917 10918This is where you may set various actions that do not fit well into the 10919other Rules categories. 10920 10921<H2>Patterns</H2> 10922 10923Other Rules are a little different from the rest of the Rules because 10924they depend only on the current folder, and not on a particular message. 10925In order to determine whether or not a rule's actions should be applied 10926the current folder is compared with the rule's Pattern, which consists 10927of only the Current Folder Type. 10928Current Folder Type works the same for Other Rules as it does for Roles, 10929Filtering, Index Coloring, and Scoring. 10930Keep in mind that the only part of the Pattern that applies to Other 10931Rules is the Current Folder Type when looking at the description of 10932Patterns given 10933"<A HREF="h_rule_patterns">here</A>". 10934 10935<H2>The Actions</H2> 10936 10937<H3>Set Sort Order</H3> 10938 10939When you enter a new folder, these rules will be checked to see if you 10940have set a sort order that is different from your default sort order. 10941The default is set in the Setup/Config screen with 10942the "<A HREF="h_config_sort_key"><!--#echo var="VAR_sort-key"--></A>" option. 10943If the Sort Order action is set, then the folder will be displayed sorted in 10944that sort order instead of in the default order. 10945<P> 10946A possible point of confusion arises when you change the configuration 10947of the Sort Order for the currently open folder. 10948The folder will normally be re-sorted when you go back to viewing the 10949index. 10950However, if you have manually sorted the folder with the 10951Sort 10952(<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->) 10953command, then it will not be re-sorted until the next time it is opened. 10954 10955<H3>Set Index Format</H3> 10956 10957When you enter a new folder, these rules will be checked to see if you 10958have set an Index Format that is different from your default Index Format, 10959which is set with the 10960<A HREF="h_config_index_format">"<!--#echo var="VAR_index-format"-->"</A> option. 10961If so, the index will be displayed with this format instead of the default. 10962 10963<H3>Set Startup Rule</H3> 10964 10965When you enter a new folder, these rules will be checked to see if you 10966have set a startup rule that is different from the default startup rule. 10967The default for incoming folders is set in the Setup/Config screen with 10968the "<!--#echo var="VAR_incoming-startup-rule"-->" option. 10969The default for folders other than INBOX that are not part of your 10970incoming collection 10971(see <A HREF="h_config_enable_incoming"><!--#echo var="FEAT_enable-incoming-folders"--></A> feature) 10972is to start with the last message in the folder. 10973If the Startup Rule is set to something other than "default", 10974then the rule will determine which message will be the current message when 10975the folder is first opened. 10976<P> 10977The various startup rule possibilities work the same here as they do in 10978the incoming collection, so check 10979<A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A> 10980for more help. 10981 10982<H2>Command Descriptions</H2> 10983 10984<H3>Add</H3> 10985 10986The Add command is used to add a new rule definition to your set of 10987rules. 10988The new rule will be added after the highlighted rule. 10989 10990<H3>Delete</H3> 10991 10992The Delete command deletes the currently highlighted rule. 10993 10994<H3>Change</H3> 10995 10996The Change command lets you edit the nickname, Pattern, 10997and Action of the currently highlighted rule. 10998 10999<H3>Shuffle</H3> 11000 11001The Shuffle command allows you to change the order of the rules. 11002You may move the currently highlighted rule up or down in the list. 11003The order of the rules is important since the rules are tested for a 11004match starting with the first rule and continuing until a match is found. 11005You should place the rules with more specific Patterns near the beginning 11006of the list, and those with more general Patterns near the end so that 11007the more specific matches will happen when appropriate. 11008 11009<H3>Replicate</H3> 11010 11011The Replicate command is used to copy an existing rule definition and modify it. 11012The new rule will be added after the highlighted rule. 11013 11014<H3>IncludeFile</H3> 11015 11016The IncludeFile command allows you to add a rules file to your configuration. 11017Usually, your rules will be contained in your Alpine configuration file. 11018If you wish, some or all of your rules may be stored in a separate file. 11019If a rules file already exists (maybe it was made by somebody else using 11020Alpine), you may insert it before the currently highlighted rule. 11021You may also insert an empty file or a file that does not yet exist. 11022Once you have an empty rules file in your configuration, you may use 11023the Shuffle command to move rules into it. 11024In fact, that's the only way to get the initial rule into the file. 11025 11026<H3>eXcludeFile</H3> 11027 11028The eXcludeFile command removes a rules file from your rules configuration. 11029A limitation of the program is that in order to exclude a rules file 11030that file must have at least one rule 11031in it, otherwise you won't be able to highlight a line in the file. 11032So you may have to add a dummy rule to the file in order to exclude the file. 11033<P><UL> 11034<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 11035</UL> 11036<P> 11037<End of help on this topic> 11038</BODY> 11039</HTML> 11040===== h_rules_srch ===== 11041<HTML> 11042<HEAD> 11043<TITLE>SETUP SEARCH RULES SCREEN</TITLE> 11044</HEAD> 11045<BODY> 11046<H1>SETUP SEARCH RULES SCREEN</H1> 11047<H2>SETUP SEARCH RULES COMMANDS</H2> 11048<!--chtml if pinemode="function_key"--> 11049<PRE> 11050Available Commands -- Group 1 Available Commands -- Group 2 11051------------------------------- ------------------------------ 11052F1 Show Help Text F1 Show Help Text 11053F2 See commands in next group F2 See commands in next group 11054F3 Back to MAIN Alpine menu 11055F4 Change configuration for rule 11056F5 Move to previous rule F5 Include file in rule config 11057F6 Move to next rule F6 Exclude file from config 11058F7 Previous page of rules 11059F8 Next page of rules 11060F9 Add new rule F9 Replicate existing rule 11061F10 Delete existing rule 11062F11 Shuffle the order of rules 11063F12 Whereis (search rule nicknames) 11064</PRE> 11065<!--chtml else--> 11066<PRE> 11067Navigation General Alpine Commands 11068------------------------- ----------------------- 11069 P Prev rule ? Display this help text 11070 N Next rule E Back to MAIN Alpine menu 11071 - Previous page 11072Spc (space bar) Next page 11073 W WhereIs (search for word in rule nicknames) 11074 11075Setup Search Rules Commands 11076------------------------------------------------ 11077 A Add new rule $ Shuffle the order of rules 11078 D Delete existing rule C Change configuration for highlighted rule 11079 R Replicate existing rule 11080 I Include file in rule config X Exclude file from rule config 11081</PRE> 11082<!--chtml endif--> 11083 11084<H2>Description of the Setup Search Rules Screen</H2> 11085 11086One of the commands that becomes available when that feature is turned on 11087is the "; Select" command, which is used in the MESSAGE INDEX 11088screen to select a set of messages. 11089One way of selecting messages is to use a Rule. 11090All of the messages that match (or don't match if you wish) 11091a Rule's Pattern will be selected. 11092<P> 11093Any of your Rules may be used for this purpose. 11094You might already have Rules set up for filtering, index line color, scores, or roles; 11095and you may use any of those Rules with the Select command. 11096However, you might find it more convenient to set up a separate set of Rules 11097just for this purpose without having to worry about what other effects 11098they may cause. 11099That is the purpose of these Select Rules. 11100 11101<P> 11102Each rule has a "Pattern" 11103that is used to decide which messages are selected when you use it with 11104the Select command. 11105 11106<H2>Patterns</H2> 11107 11108In order to determine whether or not a message should be selected 11109the message is compared with the rule's Pattern. 11110These Patterns are the same for use with Roles, Filtering, Index Coloring, 11111Scoring, Other Rules, and Search Rules, so are described in only one place, 11112"<A HREF="h_rule_patterns">here</A>". 11113 11114<H2>Command Descriptions</H2> 11115 11116<H3>Add</H3> 11117 11118The Add command is used to add a new rule definition to your set of 11119rules. 11120The new rule will be added after the highlighted rule. 11121 11122<H3>Delete</H3> 11123 11124The Delete command deletes the currently highlighted rule. 11125 11126<H3>Change</H3> 11127 11128The Change command lets you edit the nickname and Pattern 11129of the currently highlighted rule. 11130 11131<H3>Shuffle</H3> 11132 11133The Shuffle command allows you to change the order of the rules. 11134This affects only the order they are presented in when you use the 11135^T subcommand of the Select by Rule command. 11136You may move the currently highlighted rule up or down in the list. 11137 11138<H3>Replicate</H3> 11139 11140The Replicate command is used to copy an existing rule definition and modify it. 11141The new rule will be added after the highlighted rule. 11142 11143<H3>IncludeFile</H3> 11144 11145The IncludeFile command allows you to add a rules file to your configuration. 11146Usually, your rules will be contained in your Alpine configuration file. 11147If you wish, some or all of your rules may be stored in a separate file. 11148If a rules file already exists (maybe it was made by somebody else using 11149Alpine), you may insert it before the currently highlighted rule. 11150You may also insert an empty file or a file that does not yet exist. 11151Once you have an empty rules file in your configuration, you may use 11152the Shuffle command to move rules into it. 11153In fact, that's the only way to get the initial rule into the file. 11154 11155<H3>eXcludeFile</H3> 11156 11157The eXcludeFile command removes a rules file from your rules configuration. 11158A limitation of the program is that in order to exclude a rules file 11159that file must have at least one rule 11160in it, otherwise you won't be able to highlight a line in the file. 11161So you may have to add a dummy rule to the file in order to exclude the file. 11162<P><UL> 11163<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 11164</UL> 11165<P> 11166<End of help on this topic> 11167</BODY> 11168</HTML> 11169===== h_rules_incols ===== 11170<HTML> 11171<HEAD> 11172<TITLE>SETUP INDEX LINE COLORS SCREEN</TITLE> 11173</HEAD> 11174<BODY> 11175<H1>SETUP INDEX LINE COLORS SCREEN</H1> 11176<H2>SETUP INDEX LINE COLORS COMMANDS</H2> 11177<!--chtml if pinemode="function_key"--> 11178<PRE> 11179Available Commands -- Group 1 Available Commands -- Group 2 11180------------------------------- ------------------------------ 11181F1 Show Help Text F1 Show Help Text 11182F2 See commands in next group F2 See commands in next group 11183F3 Back to MAIN Alpine menu 11184F4 Change configuration for rule 11185F5 Move to previous rule F5 Include file in rule config 11186F6 Move to next rule F6 Exclude file from config 11187F7 Previous page of rules 11188F8 Next page of rules 11189F9 Add new rule F9 Replicate existing rule 11190F10 Delete existing rule 11191F11 Shuffle the order of rules 11192F12 Whereis (search rule nicknames) 11193</PRE> 11194<!--chtml else--> 11195<PRE> 11196Navigation General Alpine Commands 11197------------------------- ----------------------- 11198 P Prev rule ? Display this help text 11199 N Next rule E Back to MAIN Alpine menu 11200 - Previous page 11201Spc (space bar) Next page 11202 W WhereIs (search for word in rule nicknames) 11203 11204Setup Index Color Commands 11205------------------------------------------------ 11206 A Add new rule $ Shuffle the order of rules 11207 D Delete existing rule C Change configuration for highlighted rule 11208 R Replicate existing rule 11209 I Include file in rule config X Exclude file from rule config 11210</PRE> 11211<!--chtml endif--> 11212 11213<H2>Description of the Setup Index Line Colors Screen</H2> 11214 11215Index Line Color causes lines in the MESSAGE INDEX screen to be colored. 11216This action is only available if your terminal is capable of displaying 11217color and color display has been enabled with the 11218<A HREF="h_config_color_style">Color Style</A> option within the 11219Setup Color screen. 11220(In PC-Alpine, color is always enabled so there is no option to turn on.) 11221This screen lets you add, delete, modify, or change the order of the rules 11222that cause the lines in the MESSAGE INDEX to be displayed in different 11223colors. 11224<P> 11225Each rule has a "Pattern", 11226which is used to decide which of the rules is used; and the color that 11227is used if the Pattern matches a particular message. 11228 11229<H2>Index Color Patterns</H2> 11230 11231In order to determine whether or not a message matches an Index Color Rule 11232the message is compared with the rule's Pattern. 11233These Patterns are the same for use with Roles, Filtering, Index Coloring, 11234Scoring, Other Rules, and Search Rules, so are described in only one place, 11235"<A HREF="h_rule_patterns">here</A>". 11236 11237<P> 11238If none of the Index Color rules is a match for a particular index line, 11239then the color used is set using 11240the <A HREF="h_color_setup">Setup Kolor</A> screen. 11241 11242<H2>Index Line Color</H2> 11243 11244This is the color that index lines are colored when there is a matching 11245Pattern. 11246This colors the whole index line, except possibly the status letters, 11247which may be colored separately using 11248the <A HREF="h_color_setup">Setup Kolor</A> screen. 11249 11250<H2>Command Descriptions</H2> 11251 11252<H3>Add</H3> 11253 11254The Add command is used to add a new rule definition to your set of 11255rules. 11256The new rule will be added after the highlighted rule. 11257 11258<H3>Delete</H3> 11259 11260The Delete command deletes the currently highlighted rule. 11261 11262<H3>Change</H3> 11263 11264The Change command lets you edit the nickname, Pattern, 11265and Index Line Color of the currently highlighted rule. 11266 11267<H3>Shuffle</H3> 11268 11269The Shuffle command allows you to change the order of the rules. 11270You may move the currently highlighted rule up or down in the list. 11271The order of the rules is important since the rules are tested for a 11272match starting with the first rule and continuing until a match is found. 11273You should place the rules with more specific Patterns near the beginning 11274of the list, and those with more general Patterns near the end so that 11275the more specific matches will happen when appropriate. 11276 11277<H3>Replicate</H3> 11278 11279The Replicate command is used to copy an existing rule definition and modify it. 11280The new rule will be added after the highlighted rule. 11281 11282<H3>IncludeFile</H3> 11283 11284The IncludeFile command allows you to add a rules file to your configuration. 11285Usually, your rules will be contained in your Alpine configuration file. 11286If you wish, some or all of your rules may be stored in a separate file. 11287If a rules file already exists (maybe it was made by somebody else using 11288Alpine), you may insert it before the currently highlighted rule. 11289You may also insert an empty file or a file that does not yet exist. 11290Once you have an empty rules file in your configuration, you may use 11291the Shuffle command to move rules into it. 11292In fact, that's the only way to get the initial rule into the file. 11293 11294<H3>eXcludeFile</H3> 11295 11296The eXcludeFile command removes a rules file from your rules configuration. 11297A limitation of the program is that in order to exclude a rules file 11298that file must have at least one rule 11299in it, otherwise you won't be able to highlight a line in the file. 11300So you may have to add a dummy rule to the file in order to exclude the file. 11301<P><UL> 11302<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 11303</UL> 11304<P> 11305<End of help on this topic> 11306</BODY> 11307</HTML> 11308===== h_rules_filter ===== 11309<HTML> 11310<HEAD> 11311<TITLE>SETUP FILTERING SCREEN</TITLE> 11312</HEAD> 11313<BODY> 11314<H1>SETUP FILTERING SCREEN</H1> 11315<H2>SETUP FILTERING COMMANDS</H2> 11316<!--chtml if pinemode="function_key"--> 11317<PRE> 11318Available Commands -- Group 1 Available Commands -- Group 2 11319------------------------------- ------------------------------ 11320F1 Show Help Text F1 Show Help Text 11321F2 See commands in next group F2 See commands in next group 11322F3 Back to MAIN Alpine menu 11323F4 Change configuration for filter 11324F5 Move to previous filter F5 Include file in filter config 11325F6 Move to next filter F6 Exclude file from config 11326F7 Previous page of filters 11327F8 Next page of filters 11328F9 Add new filter F9 Replicate existing filter 11329F10 Delete existing filter 11330F11 Shuffle the order of filters 11331F12 Whereis (search filter nicknames) 11332</PRE> 11333<!--chtml else--> 11334<PRE> 11335Navigation General Alpine Commands 11336------------------------- ----------------------- 11337 P Prev Filter ? Display this help text 11338 N Next Filter E Back to MAIN Alpine menu 11339 - Previous page 11340Spc (space bar) Next page 11341 W WhereIs (search for word in filter nicknames) 11342 11343Setup Filters Commands 11344------------------------------------------------ 11345 A Add new filter $ Shuffle the order of filters 11346 D Delete existing filter C Change configuration for highlighted filter 11347 R Replicate existing filter 11348 I Include file in filter config X Exclude file from filter config 11349</PRE> 11350<!--chtml endif--> 11351 11352<H2>Description of the Setup Filtering Screen</H2> 11353 11354This screen lets you add, delete, modify, or change the order of the rules 11355that determine the filtering Alpine does on folders you view. 11356<P> 11357The software that actually delivers mail (the stuff that happens 11358before Alpine is involved) for you is in a better position to do mail filtering 11359than Alpine itself. 11360If possible, you may want to look into using that sort of mail filtering to 11361deliver mail to different folders, delete it, or forward it. 11362However, if you'd like Alpine to help with this, Alpine's filtering is for you. 11363<P> 11364Filtering is a way to automatically move certain messages from one folder 11365to another or to delete messages. 11366It can also be used to set message status (Important, Deleted, New, 11367Answered) and to set <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> for messages. 11368Alpine doesn't have the ability to forward mail to another address or 11369to deliver vacation messages. 11370<P> 11371Each filtering rule has a "Pattern" and a "Filter Action". 11372When a folder is opened, when new mail arrives in an open folder, or 11373when mail is Expunged from a folder; each 11374message is compared with the Patterns of your filtering rules. 11375The comparisons start with the first rule and keep going until there 11376is a match. 11377If a match is found, the message may be deleted or moved, depending on 11378the setting of the Filter Action. 11379If the message is not deleted, it may have its status altered. 11380 11381<P> 11382<EM>NOTE:</EM> 11383When setting up a Pattern used to delete messages, 11384it is recommended that you test the Pattern first with a "Move" 11385folder specified in 11386case unintended matches occur. Messages that are deleted will be removed 11387from the folder and <EM>unrecoverable</EM> from within Alpine after the 11388next Expunge command or once the folder being filtered has been closed. 11389 11390<H2>Filter Patterns</H2> 11391 11392In order to determine whether or not a message matches a filter the message is 11393compared with the Filter's Pattern. 11394These Patterns are the same for use with Roles, Filtering, Index Coloring, 11395Scoring, Other Rules, and Search Rules, so are described in only one place, 11396"<A HREF="h_rule_patterns">here</A>". 11397<P> 11398Since filtering is a potentially destructive action, if you have a filtering 11399Pattern with nothing other than Current Folder Type set, that filtering 11400rule is ignored. 11401 11402<H2>Filter Actions</H2> 11403 11404Once a filter match is found for a particular message, there are some actions 11405that may be taken. 11406First, the message may have its status changed. 11407This is the same message status that you can manipulate manually using the 11408<a href="h_common_flag">Flag Command</a>. 11409There are always four elements of message status that you can control. 11410You can set or clear the Important status, the New status, the Deleted 11411status, and the Answered status. 11412Of course, if the filter is going to delete the message, 11413then there is no point in setting message status. 11414You may also be able to set user-defined keywords for a message. 11415Read a little about keywords in the help text for the 11416<A HREF="h_common_flag">Flag</A> command. 11417<P> 11418Second, the filter may delete or move the message. 11419Deleting the message marks it Deleted and removes it from view. 11420It is effectively gone forever (though it technically is still there until 11421the next expunge command, which may happen implicitly). 11422Moving the message moves it from the open folder into the folder 11423listed on the "Folder List" line of the filter configuration. 11424If you list more than one folder name (separated by commas) then the message 11425will be copied to each of those folders. 11426In any case, if "Delete" or "Move" is set then the 11427message is removed from the current folder. 11428If you just want to set the messages status without deleting it from 11429the folder, then set the filter action to 11430"Just Set Message Status". 11431<P> 11432(There is no way to do a Copy instead of a Move, due to the difficulties 11433involved in keeping track of whether or not a message has 11434already been copied.) 11435 11436<H2>Command Descriptions</H2> 11437 11438<H3>Add</H3> 11439 11440The Add command is used to add a new filter definition to your set of 11441filters. 11442The new filter will be added after the highlighted filter. 11443 11444<H3>Delete</H3> 11445 11446The Delete command deletes the currently highlighted filter. 11447 11448<H3>Change</H3> 11449 11450The Change command lets you edit the nickname, Pattern, 11451and Folder of the currently highlighted filter. 11452 11453<H3>Shuffle</H3> 11454 11455The Shuffle command allows you to change the order of the filters. 11456You may move the currently highlighted filter up or down in the list. 11457The order of the filters is important since the filters are tested for a 11458match starting with the first filter and continuing until a match is found. 11459You should place the filters with more specific Patterns near the beginning 11460of the list, and those with more general Patterns near the end so that 11461the more specific matches will happen when appropriate. 11462 11463<H3>Replicate</H3> 11464 11465The Replicate command is used to copy an existing filter and modify it. 11466The new filter will be added after the highlighted filter. 11467 11468<H3>IncludeFile</H3> 11469 11470The IncludeFile command allows you to add a filters file to your configuration. 11471Usually, your filters will be contained in your Alpine configuration file. 11472If you wish, some or all of your filters may be stored in a separate file. 11473If a filters file already exists (maybe it was made by somebody else using 11474Alpine), you may insert it before the currently highlighted filter. 11475You may also insert an empty file or a file that does not yet exist. 11476Once you have an empty filters file in your configuration, you may use 11477the Shuffle command to move filters into it. 11478In fact, that's the only way to get the initial filter into the file. 11479 11480<H3>eXcludeFile</H3> 11481 11482The eXcludeFile command removes a filters file from your filters configuration. 11483A limitation of the program is that in order to exclude a filters file 11484that file must have at least one filter 11485in it, otherwise you won't be able to highlight a line in the file. 11486So you may have to add a dummy filter to the file in order to exclude the file. 11487<P><UL> 11488<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 11489</UL> 11490<P> 11491<H3>Performance Considerations</H3> 11492The number and type of patterns being tested can 11493adversely effect performance. Issues to be aware 11494of include: 11495<P> 11496<UL> 11497 <LI> The more filters you have defined the longer it will take to run down 11498the list. Deleting unused filters is a good idea. 11499 <LI> Filtering in newsgroups served by an NNTP server will be slow 11500if your patterns include tests other than "From:" 11501or "Subject:". 11502</UL> 11503<P> 11504<End of help on this topic> 11505</BODY> 11506</HTML> 11507===== h_rules_score ===== 11508<HTML> 11509<HEAD> 11510<TITLE>SETUP SCORING SCREEN</TITLE> 11511</HEAD> 11512<BODY> 11513<H1>SETUP SCORING SCREEN</H1> 11514<H2>SETUP SCORING COMMANDS</H2> 11515<!--chtml if pinemode="function_key"--> 11516<PRE> 11517Available Commands -- Group 1 Available Commands -- Group 2 11518------------------------------- ------------------------------ 11519F1 Show Help Text F1 Show Help Text 11520F2 See commands in next group F2 See commands in next group 11521F3 Back to MAIN Alpine menu 11522F4 Change configuration for rule 11523F5 Move to previous rule F5 Include file in rule config 11524F6 Move to next rule F6 Exclude file from config 11525F7 Previous page of rules 11526F8 Next page of rules 11527F9 Add new rule F9 Replicate existing rule 11528F10 Delete existing rule 11529F11 Shuffle the order of rules 11530F12 Whereis (search rule nicknames) 11531</PRE> 11532<!--chtml else--> 11533<PRE> 11534Navigation General Alpine Commands 11535------------------------- ----------------------- 11536 P Prev rule ? Display this help text 11537 N Next rule E Back to MAIN Alpine menu 11538 - Previous page 11539Spc (space bar) Next page 11540 W WhereIs (search for word in rule nicknames) 11541 11542Setup Scoring Commands 11543------------------------------------------------ 11544 A Add new rule $ Shuffle the order of rules 11545 D Delete existing rule C Change configuration for highlighted rule 11546 R Replicate existing rule 11547 I Include file in rule config X Exclude file from rule config 11548</PRE> 11549<!--chtml endif--> 11550 11551<H2>Description of the Setup Scoring Screen</H2> 11552 11553Most people will not use scores at all, but if you do use them, here's how 11554they work in Alpine. 11555Using this screen, you may define Scoring rules. 11556The score for a message is calculated by looking at every Score rule defined 11557and adding up the Score Values for the ones that match the message. 11558If there are no matches for a message, it has a score of zero. 11559Message scores may be used a couple of ways in Alpine. 11560 11561<H3>Sorting by Score</H3> 11562 11563One of the methods you may use to sort message indexes is to sort by 11564score. 11565The scores of all the messages in a folder will be calculated and then 11566the index will be ordered by placing the messages in order of ascending or 11567descending score. 11568 11569<H3>Scores for use in Patterns</H3> 11570 11571The Patterns used for Roles, Index Line Coloring, and Filtering have a 11572category labeled "Score Interval". 11573When a message is being compared with a Pattern to check for a match, if 11574the Score Interval is set only messages that have a score somewhere in 11575the interval are a match. 11576 11577<H2>Scoring Rule Patterns</H2> 11578 11579In order to determine whether or not a message matches a scoring rule 11580the message is compared with the rule's Pattern. 11581These Patterns are the same for use with Roles, Filtering, Index Coloring, 11582Scoring, Other Rules, and Search Rules, so are described in only one place, 11583"<A HREF="h_rule_patterns">here</A>". 11584 11585<P> 11586Actually, Scoring rule Patterns are slightly different from the other types of 11587Patterns because Scoring rule Patterns don't contain a Score Interval. 11588In other words, when calculating the score for a message, which is done 11589by looking at the Scoring rule Patterns, scores aren't used. 11590 11591<H2>Score Value</H2> 11592 11593This is the value that will be added to the score for a message if the 11594rule's Pattern is a match. 11595Each individual Score Value is an integer between -100 and 100, and the 11596values from matching rules are added together to get a message's score. 11597There is also a way to extract the value from a particular header of each 11598message. See the help text for Score Value for further information. 11599 11600<H2>Command Descriptions</H2> 11601 11602<H3>Add</H3> 11603 11604The Add command is used to add a new scoring rule definition. 11605The new rule will be added after the highlighted rule. 11606 11607<H3>Delete</H3> 11608 11609The Delete command deletes the currently highlighted scoring rule. 11610 11611<H3>Change</H3> 11612 11613The Change command lets you edit the nickname, Pattern, 11614and Score Value of the currently highlighted scoring rule. 11615 11616<H3>Shuffle</H3> 11617 11618The Shuffle command allows you to change the order of the scoring rules. 11619You may move the currently highlighted rule up or down in the list. 11620The order of the rules is important since the rules are tested for a 11621match starting with the first rule and continuing until a match is found. 11622You should place the rules with more specific Patterns near the beginning 11623of the list, and those with more general Patterns near the end so that 11624the more specific matches will happen when appropriate. 11625 11626<H3>Replicate</H3> 11627 11628The Replicate command is used to copy an existing rule and modify it. 11629The new rule will be added after the highlighted rule. 11630 11631<H3>IncludeFile</H3> 11632 11633The IncludeFile command allows you to add a rules file to your configuration. 11634Usually, your rules will be contained in your Alpine configuration file. 11635If you wish, some or all of your rules may be stored in a separate file. 11636If a rules file already exists (maybe it was made by somebody else using 11637Alpine), you may insert it before the currently highlighted rule. 11638You may also insert an empty file or a file that does not yet exist. 11639Once you have an empty rules file in your configuration, you may use 11640the Shuffle command to move rules into it. 11641In fact, that's the only way to get the initial rule into the file. 11642 11643<H3>eXcludeFile</H3> 11644 11645The eXcludeFile command removes a rules file from your rules configuration. 11646A limitation of the program is that in order to exclude a rules file 11647that file must have at least one rule 11648in it, otherwise you won't be able to highlight a line in the file. 11649So you may have to add a dummy rule to the file in order to exclude the file. 11650<P><UL> 11651<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 11652</UL> 11653<P> 11654<End of help on this topic> 11655</BODY> 11656</HTML> 11657===== h_direct_config ===== 11658<HTML> 11659<HEAD> 11660<TITLE>SETUP LDAP DIRECTORY SERVERS SCREEN</TITLE> 11661</HEAD> 11662<BODY> 11663<H1>SETUP LDAP DIRECTORY SERVERS SCREEN</H1> 11664<H2>SETUP LDAP DIRECTORY SERVERS COMMANDS</H2> 11665<!--chtml if pinemode="function_key"--> 11666<PRE> 11667Available Commands 11668------------------------------- 11669F1 Show Help Text 11670F3 Back to MAIN Alpine menu 11671F4 Change configuration for directory server 11672F5 Move to previous directory server 11673F6 Move to next directory server 11674F7 Previous page of directory servers 11675F8 Next page of directory servers 11676F9 Add new directory server 11677F10 Delete existing directory server 11678F11 Shuffle the order of directory servers 11679F12 Whereis (search directory server titles) 11680</PRE> 11681<!--chtml else--> 11682<PRE> 11683Navigation General Alpine Commands 11684------------------------- ----------------------- 11685 P Prev Directory Server ? Display this help text 11686 N Next Directory Server E Back to MAIN Alpine menu 11687 - Previous page 11688Spc (space bar) Next page 11689 W WhereIs (search for word in directory server titles) 11690 11691Setup LDAP Directory Server Commands 11692------------------------------------------------ 11693 A Add new directory server $ Shuffle the order of directory servers 11694 D Delete existing dir server C Change configuration for highlighted server 11695</PRE> 11696<!--chtml endif--> 11697 11698<H2>Description of the Setup LDAP Directory Servers Screen</H2> 11699 11700This screen lets you add, delete, modify, or change the order of your 11701directory servers. You may also set some optional behavior for each server. 11702The "Add Dir" command brings up a blank form to 11703fill in. You will have to supply at least the name of the LDAP server. 11704You will often have to supply a search base to be used with that server, 11705as well. Once the form has been brought up on your screen, there is help 11706available for each of the options you may set. 11707<P> 11708The "Del Dir" command allows you to remove a directory server 11709from your configuration. 11710<P> 11711The "Change" command is similar to the "Add Dir" command. 11712The difference is that instead of bringing up a form for a new server 11713configuration, you are changing the configuration of an existing entry. 11714For example, you might want to correct a typing error, change a 11715nickname, or change one of the options set for that server. 11716<P> 11717The "Shuffle" command is used to change the order of directory 11718servers. 11719<P><UL> 11720<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 11721</UL> 11722<P> 11723<End of help on this topic> 11724</BODY> 11725</HTML> 11726============= h_address_display ======================== 11727<HTML> 11728<HEAD> 11729<TITLE>SEARCH RESULTS INDEX</TITLE> 11730</HEAD> 11731<BODY> 11732<H1>SEARCH RESULTS INDEX</H1> 11733This screen shows the results, if any, of your Directory Server search. 11734Commands (besides those for screen navigation) are: 11735<DL> 11736<DT>View 11737<!--chtml if pinemode="function_key"--> 11738(F4) 11739<!--chtml else--> 11740(V) 11741<!--chtml endif--> 11742</DT> 11743<DD>See the full information for the selected entry. 11744 11745<DT>Compose 11746<!--chtml if pinemode="function_key"--> 11747(F9) 11748<!--chtml else--> 11749(C) 11750<!--chtml endif--></DT> 11751<DD>Compose a message with the selected entry as the recipient. 11752 11753<DT>Role 11754<!--chtml if pinemode="function_key"--> 11755(F2) 11756<!--chtml else--> 11757(#) 11758<!--chtml endif--></DT> 11759<DD>Compose a message with the selected entry as the recipient. This differs 11760from Compose in that you may select a role before beginning your composition. 11761 11762<DT>Forward 11763<!--chtml if pinemode="function_key"--> 11764(F10) 11765<!--chtml else--> 11766(F) 11767<!--chtml endif--></DT> 11768<DD>Send the full information for the selected entry as an 11769email message to someone else. 11770 11771<DT>Save 11772<!--chtml if pinemode="function_key"--> 11773(F11) 11774<!--chtml else--> 11775(S) 11776<!--chtml endif--> 11777</DT> 11778<DD>Save to your address book: 11779<UL> 11780<LI>the result of the search (as just found through your query) for the 11781selected entry; or 11782<LI>the selected entry for repeated Directory Server searching when used 11783in the future. 11784</UL> 11785or<BR> 11786Export to a file (external to Alpine): 11787<UL> 11788<LI>the full information for the selected entry; or 11789<LI>the email address from the selected entry; or 11790<LI>the selected entry in <A HREF="h_whatis_vcard">vCard</A> format. 11791</UL> 11792<DT>WhereIs 11793<!--chtml if pinemode="function_key"--> 11794(F12) 11795<!--chtml else--> 11796(W) 11797<!--chtml endif--> 11798</DT> 11799<DD>Search for text in the SEARCH RESULTS INDEX screen. (Searches only the 11800displayed text, not the full records for each entry.) 11801</DL> 11802<End of help on this topic> 11803</BODY> 11804</HTML> 11805============= h_address_select ======================== 11806<HTML> 11807<HEAD> 11808<TITLE>SEARCH RESULTS INDEX</TITLE> 11809</HEAD> 11810<BODY> 11811<H1>SEARCH RESULTS INDEX</H1> 11812This screen shows the results, if any, of your Directory Server search. 11813Commands (besides those for screen navigation) are: 11814<DL> 11815<DT>Select 11816</DT> 11817<DD>Select this entry for use. 11818 11819<DT>ExitSelect 11820<DD>Exit without selecting any of the entries. 11821 11822<DT>WhereIs 11823</DT> 11824<DD>Search for text in the SEARCH RESULTS INDEX screen. (Searches only the 11825displayed text, not the full records for each entry.) 11826</DL> 11827<End of help on this topic> 11828</BODY> 11829</HTML> 11830===== h_folder_maint ===== 11831<HTML> 11832<HEAD> 11833<TITLE>Help for Folder List</TITLE> 11834</HEAD> 11835<BODY> 11836<H1>FOLDER LIST COMMANDS</H1> 11837<!--chtml if pinemode="function_key"--> 11838<PRE> 11839Available Commands -- Group 1 Available Commands -- Group 2 11840------------------------------- ------------------------------ 11841F1 Show Help Text F1 Show Help Text 11842F2 See commands in next group F2 See commands in next group 11843F3 MAIN MENU Screen F3 Quit Alpine 11844F4 Select folder and view it F4 MAIN MENU Screen 11845F5 Move to previous folder 11846F6 Move to next folder F6 Specify a folder to go to 11847F7 Show previous screen of listing F7 Show MESSAGE INDEX of current folder 11848F8 Show next screen of listing F8 Compose a message 11849F9 Add a new folder F9 Print folder listing 11850F10 Delete selected folder 11851F11 Rename selected folder 11852F12 Whereis (search folder names) 11853 11854Available Commands -- Group 3 11855F1 Show Help Text 11856F2 See commands in next group 11857F5 Go to next new message 11858 (or count recent messages if <A HREF="h_config_tab_checks_recent"><!--#echo var="FEAT_tab-checks-recent"--></A> is set) 11859F8 Compose a message using roles 11860F9 Export folder to a file 11861F10 Import the file back to a folder 11862</PRE> 11863<!--chtml else--> 11864<PRE> 11865Navigating the Folder Screen Operations on the Selected Folder 11866---------------------------- --------------------------------- 11867 P Move to previous folder V View Index of selected folder 11868 N Move to next folder D Delete 11869 - Show previous page of listing R Rename 11870Spc (space bar) Show next page E Export to file 11871 U Import from file to folder 11872 11873FOLDER LIST Screen Commands General Alpine Command 11874--------------------------- ----------------------- 11875 A Add a folder O Show all other available commands 11876 G Specify a folder to go to ? Show Help text 11877 I Show MESSAGE INDEX of current folder M MAIN MENU Screen 11878 W Whereis (search folder names) Q Quit Alpine 11879 % Print folder listing C Compose a message 11880 # Compose a message using roles 11881</PRE> 11882<!--chtml endif--> 11883<P> 11884These commands are only available in the FOLDER LIST screen when the 11885<A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->" 11886feature</A> is set in the SETUP CONFIGURATION screen:<DL> 11887<DT>Select:</DT> 11888<DD>Select folders by certain criteria:<UL> 11889<LI>All: of limited use, since there is no Apply command. 11890<LI>by Property: <UL> 11891 <LI>folder contains messages not yet seen 11892 <LI>folder contains new messages 11893 <LI>folder contains exactly as many, more, or fewer messages 11894than a given number 11895 </UL> 11896<LI>by Text: <UL> 11897 <LI>contained in name of folder (Name Select) 11898 <LI>contained in messages in folder (Content Select) 11899 </UL> 11900</UL></DD> 11901 11902<DT>Select current:</DT> 11903<DD>Select the folder the cursor is on. (Can be used to "manually" 11904add one or more folders to a set created with the Select command described 11905above.)</DD> 11906<DT>Zoom mode:</DT> 11907<DD>Toggles display of only selected folders or all folders on and off.</DD> 11908</DL> 11909<P> 11910If the feature 11911<A HREF="h_config_tab_checks_recent">"<!--#echo var="FEAT_tab-checks-recent"-->"</A> 11912is set then the TAB key will display the number of recent messages and 11913the total number of messages in the highlighted folder. 11914<P> 11915The "Export" command causes the lowest common denominator style 11916mailbox to be written to a file. 11917If the file already exists, you are asked if you want to delete it. 11918If you say No, then the operation is aborted. 11919Export might be a reasonable way to store a backup or an archival copy of 11920a folder. 11921The exported-to file is a local file on the system where you are running Alpine. 11922The "Import" command is the opposite of the Export command. 11923It reads a file created by Export and asks where it should save it in your 11924folders. 11925This could be a new folder or an existing folder. 11926If the folder already exists, the messages from the exported file will be 11927appended to the folder. 11928<P> 11929<CENTER>Description of the FOLDER LIST Screen</CENTER> 11930 11931The purpose of the FOLDER LIST screen is to help you browse and manage 11932the folders and directories (also known as "hierarchy") 11933contained within a collection. 11934 11935<P> 11936Folders and directories are arranged alphabetically across lines of 11937the screen. Directories, if present, are denoted by a special 11938character at the end of the name known as the hierarchy delimiter 11939(typically, "/"). By default, folders and directories are 11940mixed together. The 11941"<A HREF="h_config_fld_sort_rule"><!--#echo var="VAR_folder-sort-rule"--></A>" 11942configuration option can be used to group directories toward the 11943beginning or end of the list. 11944 11945<P> 11946The Next/Prev Page commands help browse the list, the Next/Prev Fldr 11947commands change the "selected" (i.e., highlighted) folder or 11948directory, and the View Fldr/Dir commands will "open" the 11949selected item. Folder and directory management is provided via the 11950Rename, Delete and Add commands. 11951 11952<P><CENTER>About Folders</CENTER> 11953What are Folders?<P> 11954 11955Folders are simply files where messages are kept. Every message has to be 11956in a folder. Most every Alpine user starts out with 3 folders: an INBOX, a 11957folder for sent mail and a folder for saved messages.<P> 11958 11959You may create as many other folders as you wish. They must be given 11960names that can be filenames on the filesystem. 11961<P> 11962 11963You can move messages from one folder to another by opening the original 11964folder and saving messages into the other folder just as you can save 11965message from your INBOX to any other folder.<P> 11966 11967Folders are typically just files in the filesystem. However, the files 11968that are 11969folders have some special formatting in them (so that Alpine knows where one 11970message ends and another begins) and should <EM>not</EM> be edited outside of 11971Alpine. If you want copies of your messages in text files that you can edit 11972or otherwise manipulate, use the Export command to copy them from Alpine into 11973your regular file area. 11974 11975<P> 11976FOR MORE INFORMATION: See the section on 11977<A HREF="h_valid_folder_names">Valid Folder Names</A>. 11978<P> 11979<CENTER>About Directories</CENTER> 11980<P> 11981A directory is simply a container used to group folders within a 11982folder list. You can create as many directories as you like. And 11983directories can even contain directories themselves. 11984 11985<P> 11986SPECIAL NOTES: When accessing folders on an IMAP server, it is important 11987to note that not all IMAP servers support directories. If you find that 11988the Add command fails to offer the "Create Directory" subcommand, 11989then it's likely that directories are not supported by the server serving 11990in that collection. 11991 11992<P> 11993Similarly, servers that do provide for directories may not do so in 11994the same way. On some servers, for example, each folder name you 11995create is at the same time capable of being a directory. When this 11996happens, Alpine will display both the folder name and the name of the 11997directory (with trailing hierarchy delimiter) in the folder list. 11998 11999<P> 12000Another issue with IMAP access, though with a much smaller set of servers, 12001is that not all servers accept the request to list out the available 12002folders and directories in the same way. If you find yourself having 12003trouble viewing folders on your server, you might investigate the 12004"<A HREF="h_config_lame_list_mode"><!--#echo var="FEAT_enable-lame-list-mode"--></A>" 12005feature. 12006<P> 12007<UL> 12008<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 12009</UL> 12010<P> 12011<End of help on this topic> 12012</BODY> 12013</HTML> 12014========= h_valid_folder_names ======== 12015<HTML> 12016<HEAD> 12017<TITLE>Explanation of Valid Folder Names</TITLE> 12018</HEAD> 12019<BODY> 12020<H1>Folder Name Syntax Explained</H1> 12021 12022Once your folder collections are defined, you can usually refer to 12023folders by their simple (unqualified) name, or pick from a FOLDER LIST 12024display. However, understanding the complete syntax for folder names, 12025both local and remote, is handy when using the Goto command and when 12026you are adding new folder collections via the Setups/collectionList screen. 12027<P> 12028An Alpine folder name looks like 12029 12030<P> 12031<CENTER><SAMP>[{<remote-specification>}][#<namespace>]<namespace-specific-part></SAMP></CENTER> 12032<P> 12033 12034The square brackets ([]) mean that the part is optional. 12035 12036<P> 12037If there is no remote-specification, then the folder name is interpreted 12038locally on the computer running Alpine. 12039Local folder names depend on the operating system used by the computer 12040running Alpine, as well as the configuration of that system. For example, 12041"C:\PINE\FOLDERS\OCT-94" might exist on a PC, and 12042"~/mail/september-1994" might be a reasonable folder name on a 12043system running Unix. 12044 12045<P> 12046Alpine users have the option of using folders that are stored on some other 12047computer. Alpine accesses remote folders via IMAP (the Internet Message 12048Access Protocol), or in the case of news, via NNTP (the Network News 12049Transport Protocol). To be able to access remote folders in Alpine, the 12050remote host must be running the appropriate server software (imapd or 12051nntpd) and you must correctly specify the name of the folder to Alpine, 12052including the domain name of the remote machine. For example, 12053<P> 12054<CENTER><SAMP>{monet.art.example.com}INBOX</SAMP></CENTER> 12055<P> 12056could be a remote folder specification, and so could 12057<P> 12058<CENTER><SAMP>{unixhost.art.example.com}~/mail/september-1994</SAMP></CENTER> 12059and 12060<P> 12061<CENTER><SAMP>{winhost.art.example.com}\mymail\SEP-94</SAMP></CENTER> 12062<P> 12063Note that in the case of remote folders, the directory/file path in the specification is 12064determined by the operating system of the remote computer, <B>not</B> by 12065the operating system of the computer on which you are running Alpine. 12066<P> 12067As you can tell, the name of the computer is in {} brackets 12068followed immediately by the name of the folder. (In each of these cases the 12069optional namespace is missing.) If, as in these 12070examples, there is no remote access protocol specified, then IMAP is 12071assumed. Check 12072<A HREF="h_folder_server_syntax">here</A> 12073for a more detailed look at what options can be placed between the brackets. 12074If there are no brackets at all, then the folder name is interpreted locally 12075on the computer on which you are running Alpine. 12076 12077<P> 12078To the right of the brackets when a server name is present, or at the 12079start of the foldername if no server is present, the sharp sign, 12080"#", holds special meaning. It indicates a folder name 12081outside the area reserved for your personal folders. In fact, it's 12082used to indicate both the name of the folder, and a special phrase 12083telling Alpine how to interpret the name that follows. 12084 12085<P> 12086So, for example, Alpine can be used to access a newsgroup that might be 12087available on your computer using: 12088<P> 12089<CENTER><SAMP>#news.comp.mail.pine</SAMP></CENTER> 12090<P> 12091The sharp sign indicates the folder name is outside your personal 12092folder area. The "news." phrase after it tells Alpine to 12093interpret the remainder of the name as a newsgroup. 12094 12095<P> 12096Similarly, to access a newsgroup on your IMAP server, you might 12097use something like: 12098<P> 12099<CENTER><SAMP>{wharhol.art.example.com}#news.comp.mail.misc</SAMP></CENTER> 12100 12101<P> 12102There are a number of such special phrases (or "namespaces") 12103available. For a more detailed explanation read about 12104<A HREF="h_folder_name_namespaces">Namespaces</A>. 12105 12106<P> 12107Note that "INBOX" has special meaning in both local and remote folder 12108names. The name INBOX refers to your "principal incoming 12109message folder" and will be mapped to the actual file name used for your 12110INBOX on any given host. Therefore, a name like 12111"{xxx.art.example.com}INBOX" refers to whatever file is used to 12112store incoming mail for you on that particular host. 12113 12114<P> 12115<End of help on this topic> 12116</BODY> 12117</HTML> 12118======= h_folder_name_namespaces ======= 12119<HTML> 12120<HEAD> 12121<TITLE>FOLDER NAME NAMESPACES EXPLAINED</TITLE> 12122</HEAD> 12123<BODY> 12124<H1>Folder Name Namespaces Explained</H1> 12125 12126An Alpine folder name looks like 12127 12128<P> 12129<CENTER><SAMP>[{<remote-specification>}][#<namespace>][<namespace-specific-part>]</SAMP></CENTER> 12130<P> 12131 12132The local part of a folder name has an optional "Namespace" which 12133tells Alpine how to interpret the rest of the name. 12134 12135<P> 12136By default the folder name is interpreted as defining a section of your personal 12137folder area. This area and how you specify it are defined by the 12138server, if one is specified, or, typically, the home 12139directory, if no server is defined. 12140 12141<P> 12142If a namespace is specified, it begins with the 12143sharp, "#", character followed by the name of the namespace 12144and then the namespace's path-element-delimiter. Aside from the 12145path's format, namespaces can also imply access rights, content 12146policy, audience, location, and, occasionally, access methods. 12147 12148<P> 12149Each server exports its own set (possibly of size one) of 12150namespaces. Hence, it's likely communication with your server's 12151administrator will be required for specific configurations. Some of 12152the more common namespaces, however, include: 12153 12154<DL> 12155<DT>#news.</DT> 12156<DD>This specifies a set of folders in the newsgroup namespace. Newsgroup 12157names are hierarchically defined with each level delimited by a period. 12158<P> 12159<CENTER><SAMP>#news.comp.mail.pine</SAMP></CENTER> 12160<P> 12161</DD> 12162<DT>#public/</DT> 12163<DD>This specifies a folder area that the server may export to the general 12164public. 12165</DD> 12166<DT>#shared/</DT> 12167<DD>This specifies a folder area that the server may export to groups 12168of users. 12169</DD> 12170<DT>#ftp/</DT> 12171<DD>This specifies a folder area that is the same as that it may have 12172exported via the "File Transfer Protocol". 12173</DD> 12174<DT>#mh/</DT> 12175<DD>This specifies the personal folder area associated with folders 12176and directories that were created using the MH message handling system. 12177</DD> 12178<DT>#move/</DT> 12179<DD>This namespace is interpreted locally by Alpine. It has an unusual interpretation and format. 12180<P> 12181<CENTER><SAMP>#move<DELIM><MailDropFolder><DELIM><DestinationFolder></SAMP></CENTER> 12182<P> 12183The #move namespace is followed by two folder names separated by a delimiter 12184character. 12185The delimiter character may be any character that does not appear in 12186the MailDropFolder name. 12187The meaning of #move is that mail will be copied from the MailDropFolder to 12188the DestinationFolder and then deleted (if possible) from the MailDropFolder. 12189Periodic checks at frequency 12190<A HREF="h_config_mailcheck"><!--#echo var="VAR_mail-check-interval"--></A>, but with a minimum 12191time between checks set by 12192<A HREF="h_config_maildropcheck"><!--#echo var="VAR_maildrop-check-minimum"--></A>, 12193are made for new mail arriving in the MailDropFolder. 12194An example that copies mail from a POP inbox to a local folder follows 12195<P> 12196<CENTER><SAMP>#move+{popserver.example.com/pop3/ssl}inbox+local folder</SAMP></CENTER> 12197<P> 12198To you it appears that mail is being delivered to the local folder when it 12199is copied from the MailDropFolder, and you read mail from the local folder. 12200<P> 12201Note that if the DestinationFolder does not exist then the messages are not 12202copied from the MailDropFolder. 12203A #move folder may only be used as an 12204<A HREF="h_config_enable_incoming">"Incoming folder"</A> or 12205an Inbox. 12206When you are in the FOLDER LIST of Incoming Message Folders (after turning 12207on the 12208<A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A> 12209option) 12210the Add command has a subcommand "Use Mail Drop" 12211which may be helpful for defining the folder in your Alpine configuration. 12212The same is true when you edit the 12213<A HREF="h_config_inbox_path"><!--#echo var="VAR_inbox-path"--></A> 12214option in Setup/Config. 12215Each of these configuration methods will also create the DestinationFolder 12216if it doesn't already exist. 12217If you are having problems, make sure the DestinationFolder exists. 12218You may find some more useful information about Mail Drops at 12219<A HREF="h_maildrop">What is a Mail Drop?</A>. 12220</DD> 12221</DL> 12222<P> 12223 12224In addition, the server may support access to other user's folders, 12225provided you have suitable permissions. Common methods use a prefix 12226of either "~<VAR>user</VAR>/", or "/<VAR>user</VAR>/" to 12227indicate the root of the other user's folder area. 12228 12229<P> 12230No, nothing's simple. 12231 12232<P> 12233<End of help on this topic> 12234</BODY> 12235</HTML> 12236============= h_whatis_vcard ======================== 12237<HTML> 12238<HEAD> 12239<TITLE>VCARD EXPLAINED</TITLE> 12240</HEAD> 12241<BODY> 12242<H1>What is the vCard format?</H1> 12243A "vCard" is a sort of electronic business card, for exchanging 12244information about and among people and organizations electronically. 12245More information about vCard can be found (as of May 1998) on the WWW site 12246of the Internet Mail Consortium at the URL: 12247<P> 12248<CENTER><A HREF="http://www.imc.org/pdi/">http://www.imc.org/pdi/</A></CENTER> 12249<P> 12250<End of help on this topic> 12251</BODY> 12252</HTML> 12253===== h_folder_open ===== 12254<HTML> 12255<HEAD> 12256<TITLE>Explanation of Folder Selection</TITLE> 12257</HEAD> 12258<BODY> 12259<BR> 12260<BR> 12261This screen is designed to allow you to quickly and easily survey your 12262folders and select one to open. 12263<!--chtml if pinemode="function_key"--> 12264<PRE> 12265Navigating the List of Folders General Alpine Commands 12266------------------------------ ----------------------- 12267 P Move to previous folder ? Show this help text 12268 N Move to next folder 12269 - Show previous screen of folders 12270Spc (space bar) Show next screen 12271 W WhereIs (search folder names) 12272 12273Folder Selection Commands 12274------------------------- 12275 E Exit the Folder Select menu (without selecting a folder) 12276 S Select the currently highlighted folder 12277</PRE> 12278<!--chtml else--> 12279<PRE> 12280Navigating the List of Folders General Alpine Commands 12281------------------------------ ----------------------- 12282F5 Move to previous folder F1 Show this help text 12283F6 Move to next folder 12284F7 Show previous screen of folders 12285F8 Show next screen of folders 12286F12 WhereIs (search folder names) 12287 12288Folder Selection Commands 12289------------------------- 12290F3 Exit the Folder Select menu (without selecting a folder) 12291F4 Select the currently highlighted folder 12292</PRE> 12293<!--chtml endif--> 12294<P> 12295FOR MORE INFORMATION: See the section on 12296<A HREF="h_valid_folder_names">Valid Folder Names</A>. 12297<P> 12298<End of help on this topic> 12299</BODY> 12300</HTML> 12301===== h_folder_subscribe ===== 12302<HTML> 12303<HEAD> 12304<TITLE>Newsgroup Subscribe Screen explained</TITLE> 12305</HEAD> 12306<BODY> 12307<H1>FOLDER SUBSCRIBE HELP</H1> 12308 12309This screen is designed to help you subscribe to newsgroups you are 12310not currently subscribed to. The screen display is a list of all 12311available newsgroups (or possibly a partial list if you specified a 12312partial name when entering the screen). Groups you have already 12313subscribed to have the letters "SUB" next to them. You may 12314select a single new group to subscribe to by moving the cursor to that 12315group and pressing "S" or carriage return. Alternatively, 12316you may change into ListMode with the "ListMode" command. 12317The display will change slightly so that each group has a checkbox in 12318front of it. Use the cursor and the Set/Unset command to place an 12319"X" in front of each newsgroup you wish to subscribe to. 12320<P> 12321 12322When you are finished marking groups, the "Subscribe" 12323command will subscribe you to those groups you have marked. Note, you 12324may not unsubscribe to groups with this command. Instead of the 12325"A" "Subscribe" command, use the "D" 12326UnSbscrbe command. 12327<P> 12328 12329<!--chtml if pinemode="function_key"--> 12330<PRE> 12331Navigating the List of Newsgroups General Alpine Commands 12332--------------------------------- ----------------------- 12333F5 Move to previous group F1 Show this help text 12334F6 Move to next group 12335F7 Show previous screen of groups 12336F8 Show next screen of groups 12337F12 WhereIs (search group names) 12338F9 Use ListMode 12339 12340Group Selection Commands 12341------------------------- 12342F3 Exit the News Subscribe menu (without selecting any groups) 12343F4 Subscribe to the currently highlighted newsgroup 12344</PRE> 12345<!--chtml else--> 12346<PRE> 12347Navigating the List of Newsgroups General Alpine Commands 12348--------------------------------- ----------------------- 12349 P Move to previous group ? Show this help text 12350 N Move to next group 12351 - Show previous screen of groups 12352Spc (space bar) Show next screen 12353 W WhereIs (search group names) 12354 L Use ListMode 12355 12356Group Selection Commands 12357------------------------- 12358 E Exit the News Subscribe menu (without selecting any groups) 12359 S Subscribe to the currently highlighted newsgroup 12360</PRE> 12361<!--chtml endif--> 12362<P> 12363When in ListMode, there is an additional command for marking groups to 12364subscribe to: 12365<P> 12366<!--chtml if pinemode="function_key"--> 12367<PRE> 12368ListMode Commands 12369------------------------- 12370F9 Set or unset the highlighted group 12371</PRE> 12372<!--chtml else--> 12373<PRE> 12374ListMode Commands 12375------------------------- 12376X Set or unset the highlighted group 12377</PRE> 12378<!--chtml endif--> 12379<P> 12380<End of help on this topic> 12381</BODY> 12382</HTML> 12383===== h_folder_postnews ===== 12384<HTML> 12385<HEAD> 12386<TITLE>Newsgroup selecting for Posting explained</TITLE> 12387</HEAD> 12388<BODY> 12389This screen is designed to allow you to quickly and easily survey 12390the available newsgroups and select one to post news to. 12391<P> 12392<!--chtml if pinemode="function_key"--> 12393<PRE> 12394Navigating the List of Newsgroups General Alpine Commands 12395--------------------------------- ----------------------- 12396F5 Move to previous group F1 Show this help text 12397F6 Move to next group 12398F7 Show previous screen of groups 12399F8 Show next screen of groups 12400F12 WhereIs (search group names) 12401 12402Group Selection Commands 12403------------------------- 12404F3 Exit the Selection menu (without selecting a group) 12405F4 Select the currently highlighted newsgroup 12406</PRE> 12407<!--chtml else--> 12408<PRE> 12409Navigating the List of Newsgroups General Alpine Commands 12410--------------------------------- ----------------------- 12411 P Move to previous group ? Show this help text 12412 N Move to next group 12413 - Show previous screen of groups 12414Spc (space bar) Show next screen of groups 12415 W WhereIs (search group names) 12416 12417Group Selection Commands 12418------------------------- 12419 E Exit the Selection menu (without selecting a group) 12420 S Select the currently highlighted newsgroup 12421</PRE> 12422<!--chtml endif--> 12423<P> 12424<End of help on this topic> 12425</BODY> 12426</HTML> 12427===== h_folder_save ===== 12428<HTML> 12429<HEAD> 12430<TITLE>Folder Select for Save Explained</TITLE> 12431</HEAD> 12432<BODY> 12433This screen is designed to allow you to quickly and easily survey your 12434folders and select one to use for saving the current message. 12435<P> 12436 12437<!--chtml if pinemode="function_key"--> 12438<PRE> 12439Navigating the List of Folders General Alpine Commands 12440------------------------------ ----------------------- 12441F5 Move to previous folder F1 Show this help text 12442F6 Move to next folder 12443F7 Show previous screen of folders 12444F8 Show next screen of folders 12445F12 WhereIs (search folder names) 12446 12447Folder Selection Commands 12448------------------------- 12449F3 Exit the Folder Select menu (without selecting a folder) 12450F4 Select the currently highlighted folder 12451F11 AddNew folder (just like Select, but you type in a new folder name) 12452</PRE> 12453<!--chtml else--> 12454<PRE> 12455Navigating the List of Folders General Alpine Commands 12456------------------------------ ----------------------- 12457 P Move to previous folder ? Show this help text 12458 N Move to next folder 12459 - Show previous screen of folders 12460Spc (space bar) Show next screen of folders 12461 W WhereIs (search folder names) 12462 12463Folder Selection Commands 12464------------------------- 12465 E Exit the Folder Select menu (without selecting a folder) 12466 S Select the currently highlighted folder 12467 A AddNew folder (just like Select, but you type in a new folder name) 12468</PRE> 12469<!--chtml endif--> 12470<P> 12471FOR MORE INFORMATION: See the section on 12472<A HREF="h_valid_folder_names">Valid Folder Names</A>. 12473<P> 12474<End of help on this topic> 12475</BODY> 12476</HTML> 12477===== h_folder_fcc ===== 12478<HTML> 12479<HEAD> 12480<TITLE>Folder Select for Fcc Explained</TITLE> 12481</HEAD> 12482<BODY> 12483This screen is designed to allow you to quickly and easily survey your 12484folders and select one to use as the file carbon copy (fcc) for the 12485current message. 12486<P> 12487 12488<!--chtml if pinemode="function_key"--> 12489<PRE> 12490Navigating the List of Folders General Alpine Commands 12491------------------------------ ----------------------- 12492F5 Move to previous folder F1 Show this help text 12493F6 Move to next folder 12494F7 Show previous screen of folders 12495F8 Show next screen of folders 12496F12 WhereIs (search folder names) 12497 12498Folder Selection Commands 12499------------------------- 12500F3 Exit the Folder Select menu (without selecting a folder) 12501F4 Select the currently highlighted folder 12502F11 AddNew folder (just like Select, but you type in a new folder name) 12503</PRE> 12504<!--chtml else--> 12505<PRE> 12506Navigating the List of Folders General Alpine Commands 12507------------------------------ ----------------------- 12508 P Move to previous folder ? Show this help text 12509 N Move to next folder 12510 - Show previous screen of folders 12511Spc (space bar) Show next screen of folders 12512 W WhereIs (search folder names) 12513 12514Folder Selection Commands 12515------------------------- 12516 E Exit the Folder Select menu (without selecting a folder) 12517 S Select the currently highlighted folder 12518 A AddNew folder (just like Select, but you type in a new folder name) 12519</PRE> 12520<!--chtml endif--> 12521<P> 12522FOR MORE INFORMATION: See the section on 12523<A HREF="h_valid_folder_names">Valid Folder Names</A>. 12524<P> 12525<End of help on this topic> 12526</BODY> 12527</HTML> 12528===== h_folder_pattern_roles ===== 12529<HTML> 12530<HEAD> 12531<TITLE>Folder Select for Current Folder Explained</TITLE> 12532</HEAD> 12533<BODY> 12534This screen is designed to allow you to quickly and easily survey your 12535folders and select one to use as the specific Current Folder 12536in a Pattern. 12537<P> 12538 12539<!--chtml if pinemode="function_key"--> 12540<PRE> 12541Navigating the List of Folders General Alpine Commands 12542------------------------------ ----------------------- 12543F5 Move to previous folder F1 Show this help text 12544F6 Move to next folder 12545F7 Show previous screen of folders 12546F8 Show next screen of folders 12547F12 WhereIs (search folder names) 12548 12549Folder Selection Commands 12550------------------------- 12551F3 Exit the Folder Select menu (without selecting a folder) 12552F4 Select the currently highlighted folder 12553F11 AddNew folder (just like Select, but you type in a new folder name) 12554</PRE> 12555<!--chtml else--> 12556<PRE> 12557Navigating the List of Folders General Alpine Commands 12558------------------------------ ----------------------- 12559 P Move to previous folder ? Show this help text 12560 N Move to next folder 12561 - Show previous screen of folders 12562Spc (space bar) Show next screen of folders 12563 W WhereIs (search folder names) 12564 12565Folder Selection Commands 12566------------------------- 12567 E Exit the Folder Select menu (without selecting a folder) 12568 S Select the currently highlighted folder 12569 A AddNew folder (just like Select, but you type in a new folder name) 12570</PRE> 12571<!--chtml endif--> 12572<P> 12573FOR MORE INFORMATION: See the section on 12574<A HREF="h_valid_folder_names">Valid Folder Names</A>. 12575<P> 12576<End of help on this topic> 12577</BODY> 12578</HTML> 12579===== h_folder_stayopen_folders ===== 12580<HTML> 12581<HEAD> 12582<TITLE>Folder Select Explained</TITLE> 12583</HEAD> 12584<BODY> 12585This screen is designed to allow you to quickly and easily survey your 12586folders and select one to use as a Stay-Open folder. 12587<P> 12588 12589<!--chtml if pinemode="function_key"--> 12590<PRE> 12591Navigating the List of Folders General Alpine Commands 12592------------------------------ ----------------------- 12593F5 Move to previous folder F1 Show this help text 12594F6 Move to next folder 12595F7 Show previous screen of folders 12596F8 Show next screen of folders 12597F12 WhereIs (search folder names) 12598 12599Folder Selection Commands 12600------------------------- 12601F3 Exit the Folder Select menu (without selecting a folder) 12602F4 Select the currently highlighted folder 12603F11 AddNew folder (just like Select, but you type in a new folder name) 12604</PRE> 12605<!--chtml else--> 12606<PRE> 12607Navigating the List of Folders General Alpine Commands 12608------------------------------ ----------------------- 12609 P Move to previous folder ? Show this help text 12610 N Move to next folder 12611 - Show previous screen of folders 12612Spc (space bar) Show next screen of folders 12613 W WhereIs (search folder names) 12614 12615Folder Selection Commands 12616------------------------- 12617 E Exit the Folder Select menu (without selecting a folder) 12618 S Select the currently highlighted folder 12619 A AddNew folder (just like Select, but you type in a new folder name) 12620</PRE> 12621<!--chtml endif--> 12622<P> 12623FOR MORE INFORMATION: See the section on 12624<A HREF="h_valid_folder_names">Valid Folder Names</A>. 12625<P> 12626<End of help on this topic> 12627</BODY> 12628</HTML> 12629===== h_folder_action_roles ===== 12630<HTML> 12631<HEAD> 12632<TITLE>Folder Select Explained</TITLE> 12633</HEAD> 12634<BODY> 12635This screen is designed to allow you to quickly and easily survey your 12636folders and select one to use as the folder into which messages 12637matching this filter will be moved. 12638<P> 12639 12640<!--chtml if pinemode="function_key"--> 12641<PRE> 12642Navigating the List of Folders General Alpine Commands 12643------------------------------ ----------------------- 12644F5 Move to previous folder F1 Show this help text 12645F6 Move to next folder 12646F7 Show previous screen of folders 12647F8 Show next screen of folders 12648F12 WhereIs (search folder names) 12649 12650Folder Selection Commands 12651------------------------- 12652F3 Exit the Folder Select menu (without selecting a folder) 12653F4 Select the currently highlighted folder 12654F11 AddNew folder (just like Select, but you type in a new folder name) 12655</PRE> 12656<!--chtml else--> 12657<PRE> 12658Navigating the List of Folders General Alpine Commands 12659------------------------------ ----------------------- 12660 P Move to previous folder ? Show this help text 12661 N Move to next folder 12662 - Show previous screen of folders 12663Spc (space bar) Show next screen of folders 12664 W WhereIs (search folder names) 12665 12666Folder Selection Commands 12667------------------------- 12668 E Exit the Folder Select menu (without selecting a folder) 12669 S Select the currently highlighted folder 12670 A AddNew folder (just like Select, but you type in a new folder name) 12671</PRE> 12672<!--chtml endif--> 12673<P> 12674FOR MORE INFORMATION: See the section on 12675<A HREF="h_valid_folder_names">Valid Folder Names</A>. 12676<P> 12677<End of help on this topic> 12678</BODY> 12679</HTML> 12680===== h_abook_config ===== 12681<HTML> 12682<HEAD> 12683<TITLE>SETUP ADDRESS BOOKS SCREEN</TITLE> 12684</HEAD> 12685<BODY> 12686<H1>SETUP ADDRESS BOOKS SCREEN</H1> 12687<H2>SETUP ADDRESS BOOKS COMMANDS</H2> 12688<!--chtml if pinemode="function_key"--> 12689<PRE> 12690Available Commands 12691------------------------------- 12692F1 Show Help Text 12693F3 Back to MAIN Alpine menu 12694F4 Change configuration for address book 12695F5 Move to previous address book 12696F6 Move to next address book 12697F7 Previous page of address books 12698F8 Next page of address books 12699F9 Add new address book 12700F10 Delete existing address book 12701F11 Shuffle the order of address books 12702F12 Whereis (search address book titles) 12703</PRE> 12704<!--chtml else--> 12705<PRE> 12706Navigation General Alpine Commands 12707----------------------- ----------------------- 12708 P Prev Address Book ? Display this help text 12709 N Next Address Book E Back to MAIN Alpine menu 12710 - Previous page 12711Spc (space bar) Next page 12712 W WhereIs (search for word in address book titles) 12713 12714Setup Address Books Commands 12715------------------------------------------------ 12716 A Add new address book $ Shuffle the order of address books 12717 D Delete existing address book C Change configuration for address book 12718</PRE> 12719<!--chtml endif--> 12720 12721<H2>Description of the Setup Address Books Screen</H2> 12722 12723This screen lets you add, delete, modify, or change the order of your 12724address books. The "Add Abook" command brings up a blank form to 12725fill in. If you are adding a remote address book on an IMAP server 12726you should fill in the name of the IMAP server. Otherwise, leave 12727that field blank. (Note that remote IMAP address books are an Alpine 12728concept and are unlikely to interoperate with other mail clients.) 12729For a remote address book, fill in the name of the remote folder 12730in the Folder field. This should be a folder that is used only for 12731this one purpose, not a general purpose folder you expect to store 12732messages in. 12733<P>If you are adding a local address book, fill in the 12734Folder Name field with a local file name (e.g., .addressbook). 12735<P> 12736<B>Please note:</B> Remote address books stored on an IMAP server are 12737of an entirely different format (namely, a special-purpose 12738"mail folder") than that of the local addressbook familiar 12739to Alpine users. Therefore, 12740you cannot use "add a remote address book" to make an existing 12741Alpine .addressbook file you may have on a remote IMAP server accessible to 12742Alpine running on a different host. 12743<P> 12744 12745The "Del Abook" command allows you to remove an address book 12746from your configuration. It will also ask you if you wish to remove 12747the data for that address book, which would erase all traces of the 12748address book if you answer Yes. 12749<P> 12750 12751The "Change" command is similar to the "Add Abook" command. 12752The difference is that instead of adding a new address book to your 12753configuration, you are changing the configuration of an existing entry. 12754For example, you might want to correct a typing error or change a 12755nickname. The "Change" command is not a move command. If you 12756change the folder name or server name the data will not be moved for you. 12757<P> 12758 12759The "Shuffle" command is used for two purposes. If you shuffle 12760an address book toward another address book in the same group then 12761the order of those two address books will be swapped. If you shuffle 12762the last Personal address book down towards the Global address book 12763section, it will become a Global address book. If you shuffle 12764the first Global address book up it will become a Personal address 12765book. The main difference between Personal and Global address 12766books is that Global address books are forced read-only. 12767<P><UL> 12768<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 12769</UL> 12770<P> 12771<End of help on this topic> 12772</BODY> 12773</HTML> 12774===== h_abook_top ===== 12775<HTML> 12776<HEAD> 12777<TITLE>ADDRESS BOOK LIST COMMANDS</TITLE> 12778</HEAD> 12779<BODY> 12780<H1>ADDRESS BOOK LIST COMMANDS</H1> 12781<!--chtml if pinemode="function_key"--> 12782<PRE> 12783Available Commands -- Group 1 Available Commands -- Group 2 12784------------------------------- ------------------------------ 12785F1 Show Help Text F1 Show Help Text 12786F2 See commands in next group F2 See commands in next group 12787F3 Exit to MAIN MENU F3 Quit Alpine 12788F4 View/Edit selected address book 12789F5 Move to previous address book F5 FOLDER LIST screen 12790F6 Move to next address book F6 Specify a folder to go to 12791F7 Previous page F7 MESSAGE INDEX screen 12792F8 Next page F9 Print list of address books 12793F12 Whereis (search for word) 12794</PRE> 12795<!--chtml else--> 12796<PRE> 12797Navigation General Alpine Commands 12798----------------------- ----------------------- 12799 P Previous Entry ? Display this help text 12800 N Next Entry O Show all other available commands 12801 - Previous page < Back to MAIN Alpine menu 12802Spc (space bar) Next page Q Quit Alpine 12803 W WhereIs (search for word) L FOLDER LIST screen 12804 G Specify a folder to go to 12805Address Book Commands I MESSAGE INDEX screen 12806------------------------------------------------ 12807 > View/Edit selected address book 12808 or 12809 > Search on selected directory server 12810 12811 % Print list of address books and directory servers 12812</PRE> 12813<!--chtml endif--> 12814 12815<H2>Description of the Address Book List Screen</H2> 12816 12817From this screen you may choose which address book you wish to view 12818or edit. For more information on address books, view one of your 12819address books (with 12820<!--chtml if pinemode="function_key"--> 12821F4 12822<!--chtml else--> 12823">" 12824<!--chtml endif-->) 12825and see the Help Text there.<P> 12826 12827You may also choose a directory server on which to search for entries. 12828You do that by highlighting the directory server line and using 12829<!--chtml if pinemode="function_key"--> 12830F4 12831<!--chtml else--> 12832">" 12833<!--chtml endif-->.<P> 12834 12835If you wish to define new address books or directory servers go to the Main 12836menu and choose Setup. You may then either choose to setup AddressBooks or 12837Directory (among other things). It's possible that the Directory option 12838will not be there if the Alpine you are using does not contain LDAP directory 12839lookup functionality. 12840 12841<P><UL> 12842<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 12843</UL><P> 12844<End of help on this topic> 12845</BODY> 12846</HTML> 12847===== h_abook_opened ===== 12848<HTML> 12849<HEAD> 12850<TITLE>THE ALPINE ADDRESS BOOK</TITLE> 12851</HEAD> 12852<BODY> 12853<H1>THE ALPINE ADDRESS BOOK</H1> 12854<H2>ADDRESS BOOK COMMANDS</H2> 12855<PRE> 12856<!--chtml if pinemode="function_key"--> 12857Available Commands -- Group 1 Available Commands -- Group 2 12858------------------------------- ------------------------------ 12859F1 Show Help Text F1 Show Help Text 12860F2 See commands in next group F2 See commands in next group 12861F3 Exit this screen F3 Quit Alpine 12862F4 View/Edit selected entry F4 Go to MAIN MENU screen 12863F5 Move to previous entry F5 FOLDER LIST screen 12864F6 Move to next entry F6 Specify a folder to go to 12865F7 Previous page of address book F7 MESSAGE INDEX screen 12866F8 Next page of address book F8 Compose to entry using roles 12867F9 Add new entry to address book F9 Print address book 12868F10 Delete selected entry F10 TakeAddr to another addrbook 12869F11 Compose to selected entry F11 Save or Export addrbook selections 12870F12 Whereis (search address book) F12 Forward entry by mail 12871 12872Available Commands -- Group 3 12873------------------------------ 12874F3 Select F6 Zoom (or unZoom) 12875F5 Select Current F7 Apply Command to Selection 12876<!--chtml else--> 12877Address Book Navigation General Alpine Commands 12878----------------------- ----------------------- 12879 P Prev Address ? Display this help text 12880 N Next Address O Show all other available commands 12881 - Previous page of address book M Back to MAIN MENU 12882Spc (space bar) Next page Q Quit Alpine 12883 W WhereIs (search for word C Compose message to selected addr 12884 or name in address book) # Compose to addr using roles 12885 < To List of Address Books if L FOLDER LIST screen 12886 more than one, else to MAIN G Specify a folder to go to 12887 I MESSAGE INDEX screen 12888 12889Address Book Commands 12890---------------------------------------------------- 12891 > View/Update selected entry D Delete selected entries 12892 % Print address book S Save or Export address book selections 12893 F Forward entries by mail @ Add new entry to address book 12894 12895 ; Select command Z Toggle Zoom Mode 12896 : Select highlighted entry A Apply command to selected entries 12897 12898<!--chtml endif--> 12899</PRE> 12900Note: The presence or absence of the final four commands above is 12901controlled by the option 12902<A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A>. 12903<P> 12904 12905<H2>Description of the Address Book Screen</H2> 12906 12907This screen lets you edit and manage entries in your address book. It 12908also acts as a short-cut for composing messages to people in the address 12909book. When, from this screen, you press <!--chtml if pinemode="function_key"-->F11<!--chtml else-->"C"<!--chtml endif--> for ComposeTo, the 12910message starts "pre-addressed" to whatever address book entry is 12911currently selected. If you use the <!--chtml if pinemode="function_key"-->F8<!--chtml else-->"#"<!--chtml endif--> for Role, you may first select a 12912role to use in your composition. 12913<P> 12914Alpine's address book helps you keep a list of addresses you send email to so 12915you do not have to remember addresses that are often complex. Each entry 12916in the address book has five fields, all of them optional. The three 12917elements that are usually visible on the ADDRESS BOOK display, are: <DL> 12918 12919 <P><DT>NICKNAME: <DD>A short easy-to-remember label to identify the entry. 12920 This is what you type in as you are addressing the message in the 12921 composer. If there is a matching entry in your address book(s), 12922 Alpine will extract the corresponding FullName and Address fields to 12923 generate the actual address for your message. 12924 12925 <P><DT>FULLNAME: <DD>A longer field where you can put the full name 12926of the 12927 person or organization. Usually the full names are put in last 12928 name first so they sort nicely in alphabetical order. Whatever 12929 you put as the name here will appear on the message when it is 12930 finally delivered. Examples:<PRE> 12931 Garcia Marquez, Gabriel 12932 Henscheid, Eckhard 12933 Alpine-Info mailing list 12934 Library materials renewal requests 12935 Kim An-guk 12936 "George III, King of Great Britain, 1738-1820" 12937</PRE> 12938(In the second-to-last example, no comma is used in the name so that 12939the family name appears first in the address book and when the entry is 12940used in the composer. 12941In the last example, retaining the commas is intended; 12942double-quotation marks surround the name to 12943prevent the transposition of its parts when the entry is used in 12944the composer.) 12945 12946 <P><DT>ADDRESS: <DD>This is the actual email address itself. This must be 12947 a valid Internet address that conforms to the Internet message 12948 header standard, RFC-822. (See also <A HREF="h_address_format">Explanation of Address formats</A>.)</DL> 12949 12950The two fields that aren't usually visible are:<DL> 12951 12952 <P><DT>FCC: <DD>The name of the folder you would like a copy of any outgoing 12953 message to this address to be saved in. If this field is set, and 12954 this address is the first one in the message's To: header, then 12955 Alpine will use this folder name for the FCC in lieu of the normal 12956 FCC folder name. 12957 12958 <P><DT>COMMENTS: <DD>This field contains arbitrary text for your convenience. 12959 </DL> 12960<P> 12961Due to screen width limitations, these last two fields do not show up in 12962the normal ADDRESS BOOK display. You may select the 12963"View/Update" command to 12964view or modify them. You may use the configuration variable 12965<A HREF="h_config_abook_formats">"<!--#echo var="VAR_addressbook-formats"-->"</A> 12966to add these fields to your ADDRESS BOOK 12967display, or to modify the format of the display. 12968 12969<H2>Sorting the Address book</H2> 12970 12971By default, address book entries are sorted alphabetically on the full 12972name with distribution lists sorted to the end. Sorting can be changed by 12973resetting the address book sort rule in the Alpine SETUP CONFIGURATION screen 12974--assuming you have "write" permission for the address book file. 12975<P> 12976Unlike the sorting of folders (which only changes presentation), sorting an 12977address book actually changes the file as it is kept on the computer. For 12978this reason you won't be able to sort a shared or system-wide address 12979book. 12980 12981<H2>Adding New Entries</H2> 12982 12983The easiest way to add new entries to your address book is to use the 12984"TakeAddr" command when viewing a message. 12985This command allows you to take addresses from the header and body of the 12986message and put them into your address book, without having to type 12987them in. 12988<P> 12989 12990To manually add a new entry from within the address book screen, use the AddNew 12991(<!--chtml if pinemode="function_key"-->F9<!--chtml else-->"@"<!--chtml endif-->) command. 12992Use this command both for adding a simple alias and for adding a 12993distribution list. 12994 12995<H2>Distribution Lists</H2> 12996 12997Address book entries can be simple cases of aliases (a single nickname is linked 12998to a single email address) or distribution lists (a single nickname 12999pointing at more than one email address). Each distribution list has a 13000nickname, a full name and a list of addresses. The addresses may be 13001actual addresses or they may be other nicknames in your address book. 13002They may even refer to other distribution lists. 13003There's really no difference between a simple alias and a distribution list, 13004other than the number of addresses. 13005Therefore, you can turn a simple alias with one address into a distribution 13006list simply by adding more addresses. 13007To add entries to an existing list or alias 13008use the View/Update (<!--chtml if pinemode="function_key"-->F4<!--chtml else-->">"<!--chtml endif-->) command. Delete (<!--chtml if pinemode="function_key"-->F10<!--chtml else-->"D"<!--chtml endif-->) will delete 13009a single address from the list if the cursor is placed on the address; 13010it will delete the entire distribution list if the cursor is on the 13011nickname/fullname line. View/Update may also be used to delete addresses 13012from a list. 13013<P> 13014Address field entries in distribution lists may take any one of three 13015forms: a nickname existing in any of the defined address books, a normal 13016address of the form "jsmith@art.example.com", or a complete 13017fullname/address combination, e.g. "John Smith 13018<jsmith@art.example.com>". 13019<P> 13020Distribution lists in Alpine address books can only be used by the person or 13021people who have access to that address book. They are not usually used to 13022implement discussion groups, but can be used to facilitate small 13023discussion groups if all the participants have access to the same shared 13024address book. 13025 13026<H2>FCC and Comments</H2> 13027 13028As mentioned above, each entry in the address book also has two other optional 13029fields, Fcc and Comments. The command to look at or change either of these 13030is the same View/Update command used for all of the fields (<!--chtml if pinemode="function_key"-->F4<!--chtml else-->">"<!--chtml endif-->). The 13031Comments field is just for your own use. The Fcc field overrides the 13032default Fcc if this address is the first one on the To line. The WhereIs 13033command may be used to search for particular strings in the address book, 13034including fields that are not visible (like Comment and Fcc by default). 13035 13036<H2>Aggregate Operations</H2> 13037 13038If the feature 13039<A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A> 13040is turned on (the default), then the four commands "Select", 13041"Select Current", "Zoom", and "Apply" 13042are available. The two selection commands allow you to mark a set of 13043address book entries as being selected. If you have more than one address 13044book, the selections may be in more than one of those address books. 13045The "Zoom" command will toggle between displaying only the selected 13046entries and all of the entries. The "Apply" command allows you to 13047apply one of the regular address book commands to all of the selected 13048entries. Usually the address book commands apply to only the entry 13049highlighted by the cursor. The "Apply" command works with the 13050commands "ComposeTo", "Delete", "Print", 13051"Save", "Forward", and "Role". 13052 13053<H2>Exporting and Forwarding Address book entries</H2> 13054 13055Under the save option, when you use the Export (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->"X"<!--chtml endif-->) command, the currently highlighted 13056address book entry is placed in a plain text file in your home directory 13057<!--chtml if pinemode="running"--> 13058(which, in the present configuration of your system, is 13059 "<!--#echo var="HOME_DIR"-->") 13060<!--chtml endif--> 13061or current working directory 13062<!--chtml if pinemode="running"--> 13063(which, at least for your current Alpine "session," 13064is "<!--#echo var="CURRENT_DIR"-->") 13065<!--chtml endif-->, depending on the 13066<A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> 13067configuration setting. If you have some entries selected and use the 13068Apply (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->"A"<!--chtml endif-->) Export command, all of the selected addresses will be 13069placed in the text file. 13070<P> 13071When you use the Forward (<!--chtml if pinemode="function_key"-->F12<!--chtml else-->"F"<!--chtml endif-->) command, the currently highlighted 13072address book entry is placed in a special attachment and you are put into 13073the composer. You can fill in some comments in the body of the message, 13074if you'd like, and send it to somebody else who uses Alpine. The recipient 13075may use the TakeAddr command on that message to insert the address book 13076entry you sent in their own address book. If you have some entries 13077selected and use the Apply Forward command all of the selected entries 13078will be forwarded in a single message. You may 13079use Apply (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->"A"<!--chtml endif-->) Forward to forward a copy of an entire address book. 13080The recipient must be using Alpine in order to receive this correctly. 13081One way for the recipient to handle this might be to create an empty 13082address book and then "Take" your forwarded address book entries into 13083that empty address book. 13084 13085<H2>Multiple and/or Site-Wide Address books</H2> 13086 13087You may have more than one personal address book. In addition, there may 13088be one or more global address books. This capability allows you to have 13089multiple personal address books (some of which may be shared) and it also 13090allows system administrators to implement site-wide address books that 13091contain entries for users on multiple machines within the organization. 13092<P><DL> 13093<DT>Searching 13094 <DD> If you enter a nickname when composing a message, your 13095 personal address books will be searched through in order, and then the 13096 global address book(s) searched. If more than one address book has an entry 13097 for the nickname, Alpine uses the first one that it finds, so an entry in 13098 your personal address book would override a global address book entry. If 13099 after searching all the address books there is still no match, (Unix) Alpine 13100 then searches the local host password file on the assumption that you have 13101 entered a local user name rather than an address book nickname. 13102 You may change the search order of your address books with the <!--chtml if pinemode="function_key"-->F3<!--chtml else-->$<!--chtml endif--> Shuffle 13103 command, but global address books are always searched after personal 13104 address books. 13105 13106 <P><DT>Tab completion 13107 <DD> If the 13108 <A HREF="h_config_enable_tab_complete"><!--#echo var="FEAT_enable-tab-completion"--></A> 13109 feature is turned on (the default) then the Tab key may be used 13110 in the composer to complete partially typed nicknames in the To 13111 or Cc lines. You type the first few letters of a nickname and then 13112 press the Tab key. It there is only one nickname that matches it will 13113 be filled in by Alpine. If there is more than one the unambiguous part 13114 of the nicknames will be filled in. For example, if your address book or 13115 books contains only the two entries "barley" and "barbecue" 13116 beginning with the letters "ba", then if you type "ba" 13117 followed by a Tab character Alpine will fill in "bar" and stop. 13118 If you then type a second Tab character you will be presented with a list 13119 of matching nicknames to select from. Alternatively, you could type another 13120 "b" resulting in "barb" and then a Tab would fill 13121 in the entire "barbecue" entry. 13122 13123 <P><DT>Defining 13124 <DD> You define multiple personal address books in the 13125 <A HREF="h_abook_config">SETUP AddressBooks</A> screen, which you may reach 13126 from the MAIN MENU. 13127 You may add as many as you like. Global address books are usually 13128 site-wide address books defined by the System administrator, but 13129 you may define global address books of your own just like you define 13130 personal address books. 13131 13132 <P><DT>Creating and updating 13133 <DD> Personal address books are normally created empty 13134 and populated by explicit additions from within Alpine, e.g. via the 13135 TakeAddr command. Unlike personal address books, global address books may 13136 not be modified/updated from within Alpine; that is, they are Read-Only. 13137 Thus, global address books are created, populated and updated outside of 13138 Alpine. They might be hand-edited, generated by a program from another 13139 database, or by copying an existing address book. They might also be 13140 some other user's personal address book, and so be modified normally by 13141 that user but accessed Read-Only by you. See the Alpine Technical 13142 Notes document (included in the Alpine distribution) for more information on 13143 this. 13144 13145 <P><DT>Accessing 13146 <DD>There are two different types of address books in Alpine. 13147 A local address book is stored in a regular file and the normal file 13148 access permissions apply. A remote address book is stored on an IMAP 13149 server in a special folder that contains only messages pertaining to 13150 that address book. The last message in the remote folder contains a 13151 copy of the address book data, and that data is copied to a local cache 13152 file in your home directory. From there it is accessed just like a local 13153 address book. The name of the cache file is kept track of in a special 13154 file called the 13155 <A HREF="h_config_abook_metafile"><!--#echo var="VAR_remote-abook-metafile"--></A>, 13156 the name of which is stored in 13157 your Alpine configuration file the first time you use a remote address book. 13158 Just as local Alpine address books use a format that only Alpine understands, 13159 remote Alpine address books do the same and other mail reading programs 13160 are unlikely to be able to understand them.<P> 13161 While global address books are explicitly intended to be shared, there is 13162 nothing to prevent you from sharing a personal address book with other 13163 Alpine users. This might be useful in the case of a small workgroup. 13164 However, it is recommended that updates to shared personal address books 13165 be done when other Alpine users are not accessing the address book. Alpine 13166 does not do any file-locking to manage concurrent updates to the 13167 addressbook, but it does check to see if the file has been modified before 13168 making any changes. Consequently, inadvertent concurrent updates will 13169 only cause other Alpine users to have to restart their address book 13170 operation, which will cause Alpine to reopen the updated file. 13171 13172 <P><DT>Converting to Remote 13173 <DD>The easiest way to convert an existing local 13174 address book into a remote address book is to create an empty new remote 13175 personal address book by typing "A" to execute the 13176 "Add Pers Abook" command in the SETUP Addressbook screen. 13177 Make sure you add a <EM>personal</EM> address book, not a <EM>global</EM> 13178 address book. 13179 After you have added the empty 13180 remote address book, go into the screen for the address book you wish 13181 to copy and "Select" "All". 13182 This selects every entry in that 13183 address book. Then type the command "Apply Save". 13184 You will be asked for the address book to save to. You may use ^P and ^N 13185 to get to the new empty address book, then hit RETURN and the addresses 13186 will be copied. 13187 At this point you'll probably want to unselect all the entries in the local 13188 address book before proceeding. You do that with 13189 "Select" "unselect All". 13190 13191</DL> 13192<UL> 13193<LI><A HREF="h_address_format">Explanation of Address formats</A> 13194</UL> 13195<P><UL> 13196<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 13197</UL> 13198<P> 13199<End of help on this topic> 13200</BODY> 13201</HTML> 13202===== h_abook_select_addr ===== 13203<HTML> 13204<HEAD> 13205<TITLE>Addressbook Selection Explained</TITLE> 13206</HEAD> 13207<BODY> 13208<H1>SELECT ADDRESS</H1> 13209<!--chtml if pinemode="function_key"--> 13210<PRE> 13211Navigating the List of Messages General Alpine Commands 13212------------------------------- ----------------------- 13213F5 Move to previous entry F1 Show this help text 13214F6 Move to next entry 13215F7 Show previous screen of address book 13216F8 Show next screen of address book 13217F12 WhereIs (search through address book) 13218 13219Address Selection Commands 13220-------------------------- 13221F3 Exit the Address Select screen (without selecting an address) 13222F4 Select the currently highlighted entry 13223</PRE> 13224<!--chtml else--> 13225<PRE> 13226Navigating the List of Messages General Alpine Commands 13227------------------------------- ----------------------- 13228 P Move to previous entry ? Show this help text 13229 N Move to next entry 13230 - Show previous screen of address book 13231Spc (space bar) Show next screen of address book 13232 W WhereIs (search through address book) 13233 13234Address Selection Commands 13235-------------------------- 13236 E Exit the Address Select screen (without selecting an address) 13237 S Select the currently highlighted entry 13238</PRE> 13239<!--chtml endif--> 13240<P> 13241 13242This screen is designed to let you easily scan your address book(s) in 13243order to select an entry for the message you are composing. You cannot 13244edit your address book in any way at this time, for address book 13245maintenance, select the address book command when not composing a message. 13246<P> 13247 13248If you are composing a message and know the nickname of the person/list you 13249want, you can bypass this screen by simply typing in the nickname on the 13250appropriate header line (To:, Cc:, etc.) Exiting this screen without 13251selecting an entry does not cancel your message. 13252<P> 13253 13254FOR MORE INFORMATION on addressing see 13255<A HREF="h_address_format">Explanation of Address formats</A>, and the 13256<A HREF="h_abook_opened">Address Book Screen's</A> 13257help text. 13258<P> 13259<End of help on this topic> 13260</BODY> 13261</HTML> 13262===== h_abook_select_top ===== 13263<HTML> 13264<HEAD> 13265<TITLE>Addressbook Selection Navigation Explained</TITLE> 13266</HEAD> 13267<BODY> 13268<H1>NAVIGATING WHILE SELECTING ADDRESSES</H1> 13269<!--chtml if pinemode="function_key"--> 13270<PRE> 13271Navigating the List of Address Books General Alpine Commands 13272------------------------------------ ----------------------- 13273F4 View the highlighted address book 13274F5 Move to previous address book F1 Show this help text 13275F6 Move to next address book 13276F7 Show previous screen of address books 13277F8 Show next screen of address books 13278F12 WhereIs (search through address books) 13279 13280Address Selection Commands 13281-------------------------- 13282F3 Exit the Address Select screen (without selecting an address) 13283F4 Select the currently selected entries (if using ListMode) 13284F9 Change to ListMode 13285</PRE> 13286<!--chtml else--> 13287<PRE> 13288Navigating the List of Address Books General Alpine Commands 13289------------------------------------ ----------------------- 13290 > View the highlighted address book 13291 P Move to previous address book ? Show this help text 13292 N Move to next address book 13293 - Show previous screen of address books 13294Spc (space bar) Show next screen of address books 13295 W WhereIs (search through address books) 13296 13297Address Selection Commands 13298-------------------------- 13299 E Exit the Address Select screen (without selecting an address) 13300 S Select the currently selected entries (if using ListMode) 13301 L Change to ListMode 13302</PRE> 13303<!--chtml endif--> 13304<P> 13305 13306This screen is designed to let you easily scan your address book(s) in 13307order to select entries for the message you are composing. You cannot 13308edit your address book in any way at this time. For address book 13309maintenance, select the address book command when not composing a message. 13310<P> 13311 13312If you are composing a message and know the nickname of the person/list you 13313want, you can bypass this screen by simply typing in the nickname on the 13314appropriate header line (To:, Cc:, etc.) Exiting this screen without 13315selecting an entry does not cancel your message. 13316<P> 13317 13318The ListMode command will add a column at the left edge of the screen. 13319You mark the entries that you wish to select with the "X" command. 13320This allows you to choose more than one entry at a time. 13321<P> 13322 13323An alternative method of composing a message to entries in your 13324address book(s) is to first use the "Select" command from 13325the address book maintenance screen and then the "Apply" 13326"ComposeTo" command to start the composer composing to the 13327selected entries. 13328<P> 13329 13330FOR MORE INFORMATION on addressing see 13331<A HREF="h_address_format">Explanation of Address formats</A>, and the 13332<A HREF="h_abook_opened">Address Book Screen's</A> 13333help text. 13334<P> 13335<End of help on this topic> 13336</BODY> 13337</HTML> 13338===== h_abook_select_listmode ===== 13339<HTML> 13340<HEAD> 13341<TITLE>Address Listmode Selection from Composer Explained</TITLE> 13342</HEAD> 13343<BODY> 13344<H1>COMPOSER: SELECT ADDRESSES</H1> 13345<!--chtml if pinemode="function_key"--> 13346<PRE> 13347Navigating the List of Messages General Alpine Commands 13348------------------------------- ----------------------- 13349F5 Move to previous entry F1 Show this help text 13350F6 Move to next entry 13351F7 Show previous screen of address book 13352F8 Show next screen of address book 13353F12 WhereIs (search through address book) 13354 13355Address Selection Commands 13356-------------------------- 13357F3 Exit the Address Select screen (without selecting an address) 13358F4 Select the currently highlighted entry 13359F9 Change to ListMode 13360</PRE> 13361<!--chtml else--> 13362<PRE> 13363Navigating the List of Messages General Alpine Commands 13364------------------------------- ----------------------- 13365 P Move to previous entry ? Show this help text 13366 N Move to next entry 13367 - Show previous screen of address book 13368Spc (space bar) Show next screen of address book 13369 W WhereIs (search through address book) 13370 13371Address Selection Commands 13372-------------------------- 13373 E Exit the Address Select screen (without selecting an address) 13374 S Select the currently highlighted entry 13375 L Change to ListMode 13376</PRE> 13377<!--chtml endif--> 13378<P> 13379 13380This screen is designed to let you easily scan your address book(s) in 13381order to select entries for the message you are composing. You cannot 13382edit your address book in any way at this time, for address book 13383maintenance, select the address book command when not composing a message. 13384<P> 13385 13386If you are composing a message and know the nickname of the person/list you 13387want, you can bypass this screen by simply typing in the nickname on the 13388appropriate header line (To:, Cc:, etc.) Exiting this screen without 13389selecting an entry does not cancel your message. 13390<P> 13391 13392The ListMode command will add a column at the left edge of the screen. 13393You mark the entries that you wish to select with the "X" command. 13394This allows you to choose more than one entry at a time. 13395<P> 13396 13397An alternative method of composing a message to entries in your 13398address book(s) is to first use the "Select" command from 13399the address book maintenance screen and then the "Apply" 13400"ComposeTo" command to start the composer composing to the 13401selected entries. 13402<P> 13403 13404FOR MORE INFORMATION on addressing see 13405<A HREF="h_address_format">Explanation of Address formats</A>, and the 13406<A HREF="h_abook_opened">Address Book Screen's</A> 13407help text. 13408<P> 13409<End of help on this topic> 13410</BODY> 13411</HTML> 13412===== h_abook_select_checks ===== 13413<HTML> 13414<HEAD> 13415<TITLE>Address Selection from Composer Explained</TITLE> 13416</HEAD> 13417<BODY> 13418<H1>COMPOSER: SELECT ADDRESSES</H1> 13419<!--chtml if pinemode="function_key"--> 13420<PRE> 13421Navigating the List of Messages General Alpine Commands 13422------------------------------- ----------------------- 13423F5 Move to previous entry F1 Show this help text 13424F6 Move to next entry 13425F7 Show previous screen of address book 13426F8 Show next screen of address book 13427F12 WhereIs (search through address book) 13428 13429Address Selection Commands 13430-------------------------- 13431F3 Exit the Address Select screen (without selecting an address) 13432F4 Select the currently highlighted entry 13433F8 Either Sets or Unsets all entries in this address book 13434F9 Set or Unset the highlighted entry 13435</PRE> 13436<!--chtml else--> 13437<PRE> 13438Navigating the List of Messages General Alpine Commands 13439------------------------------- ----------------------- 13440 P Move to previous entry ? Show this help text 13441 N Move to next entry 13442 - Show previous screen of address book 13443Spc (space bar) Show next screen of address book 13444 W WhereIs (search through address book) 13445 13446Address Selection Commands 13447-------------------------- 13448 E Exit the Address Select screen (without selecting an address) 13449 S Select the currently highlighted entry 13450 X Set or Unset the highlighted entry 13451 A Either Sets or Unsets all entries in this address book 13452</PRE> 13453<!--chtml endif--> 13454<P> 13455 13456Mark the entries you wish to select with the "X Set/Unset" 13457command. Type "S Select" to select all of the entries you 13458have marked, just as if you had typed them in by hand. 13459<P> 13460 13461An alternative method of composing a message to entries in your 13462address book(s) is to first use the "Select" command from 13463the address book maintenance screen and then the "Apply" 13464"ComposeTo" command to start the composer composing to the 13465selected entries. 13466<P> 13467 13468FOR MORE INFORMATION on addressing see 13469<A HREF="h_address_format">Explanation of Address formats</A>, and the 13470<A HREF="h_abook_opened">Address Book Screen's</A> 13471help text. 13472<P> 13473<End of help on this topic> 13474</BODY> 13475</HTML> 13476===== h_abook_select_nicks_take ===== 13477<HTML> 13478<HEAD> 13479<TITLE>Take Address Nickname Selection Explained</TITLE> 13480</HEAD> 13481<BODY> 13482<H1>TAKEADDR: SELECT NICKNAME</H1> 13483<!--chtml if pinemode="function_key"--> 13484<PRE> 13485Navigating the List of Messages General Alpine Commands 13486------------------------------- ----------------------- 13487F5 Move to previous entry F1 Show this help text 13488F6 Move to next entry 13489F7 Show previous screen of address book 13490F8 Show next screen of address book 13491F12 WhereIs (search through address book) 13492 13493Message Selection Commands 13494-------------------------- 13495F3 Exit the Nickname Select screen (without selecting an address) 13496F4 Select the currently highlighted entry 13497</PRE> 13498<!--chtml else--> 13499<PRE> 13500Navigating the List of Messages General Alpine Commands 13501------------------------------- ----------------------- 13502 P Move to previous entry ? Show this help text 13503 N Move to next entry 13504 - Show previous screen of address book 13505Spc (space bar) Show next screen of address book 13506 W WhereIs (search through address book) 13507 13508Message Selection Commands 13509-------------------------- 13510 E Exit the Nickname Select screen (without selecting an address) 13511 S Select the currently highlighted entry 13512</PRE> 13513<!--chtml endif--> 13514<P> 13515 13516This screen is designed to let you modify or add to an existing 13517address book entry. You have already selected the name(s) and 13518address(es) through "Take Address". This screen simply lets 13519you scan your address books and select the nickname to be 13520changed/augmented. If you want to add a new entry, then you are in 13521the wrong place-- Select "Exit" command. 13522<P> 13523 13524FOR MORE INFORMATION on addressing see 13525<A HREF="h_address_format">Explanation of Address formats</A>, and the 13526<A HREF="h_abook_opened">Address Book Screen's</A> 13527help text. 13528<P> 13529<End of help on this topic> 13530</BODY> 13531</HTML> 13532===== h_abook_select_nick ===== 13533<HTML> 13534<HEAD> 13535<TITLE>Nickname Selection Explained</TITLE> 13536</HEAD> 13537<BODY> 13538<H1>SELECT NICKNAME</H1> 13539<!--chtml if pinemode="function_key"--> 13540<PRE> 13541Navigating the List of Messages General Alpine Commands 13542------------------------------- ----------------------- 13543F5 Move to previous entry F1 Show this help text 13544F6 Move to next entry 13545F7 Show previous screen of address book 13546F8 Show next screen of address book 13547F12 WhereIs (search through address book) 13548 13549Message Selection Commands 13550-------------------------- 13551F3 Exit the Nickname Select screen (without selecting an address) 13552F4 Select the currently highlighted entry 13553</PRE> 13554<!--chtml else--> 13555<PRE> 13556Navigating the List of Messages General Alpine Commands 13557------------------------------- ----------------------- 13558 P Move to previous entry ? Show this help text 13559 N Move to next entry 13560 - Show previous screen of address book 13561Spc (space bar) Show next screen of address book 13562 W WhereIs (search through address book) 13563 13564Message Selection Commands 13565-------------------------- 13566 E Exit the Nickname Select screen (without selecting an address) 13567 S Select the currently highlighted entry 13568</PRE> 13569<!--chtml endif--> 13570<P> 13571 13572This screen is designed to let you look at the nicknames in your address 13573books before choosing a new one. 13574<P> 13575 13576FOR MORE INFORMATION on addressing see 13577<A HREF="h_address_format">Explanation of Address formats</A>, and the 13578<A HREF="h_abook_opened">Address Book Screen's</A> 13579help text. 13580<P> 13581<End of help on this topic> 13582</BODY> 13583</HTML> 13584===== h_takeaddr_screen ===== 13585<HTML> 13586<HEAD> 13587<TITLE>Take Address Screen Explained</TITLE> 13588</HEAD> 13589<BODY> 13590<H1>TAKE ADDRESS COMMANDS</H1> 13591<!--chtml if pinemode="function_key"--> 13592<PRE> 13593Navigating the List of Addresses Address Selection Commands 13594-------------------------------- -------------------------- 13595 F5 Move to previous entry F3 Exit without taking address 13596 F6 Move to next entry F4 Take current address(es) 13597 F7 Show previous page of address list 13598 F8 Show next page of address list 13599 F2 WhereIs (search list) 13600 -------------- 13601Mode Toggle F9 Set/Unset current address 13602----------- F10 Set all 13603 F12 Toggle between List and single mode F11 Unset all 13604</PRE> 13605<!--chtml else--> 13606<PRE> 13607Navigating the List of Addresses Address Selection Commands 13608-------------------------------- -------------------------- 13609 P Move to previous entry < Exit without taking address 13610 N Move to next entry T Take address 13611 - Show previous page of address list 13612Spc (space bar) Show next page of address list 13613 W WhereIs (search list) List Mode 13614 --------- 13615Single Mode X Set/Unset current address 13616----------- A Set all addresses 13617 L Switch to list mode U Unset all addresses 13618 S Switch to single mode 13619</PRE> 13620<!--chtml endif--> 13621 13622<H2>Description of the Take Address Screen</H2> 13623 13624This screen is designed to let you select one or more address/name 13625combinations from the current message and put them into your address book. 13626The cursor is initially placed on the line with the message author. 13627Other lines include the names of people and/or mailing lists who also 13628received the message. Other people "involved" in the 13629message (e.g. the person named as Reply-To:) are also listed here. 13630<P> 13631 13632The simple case is adding a new, single entry into your address book. To 13633do this, simply highlight the correct line and press 13634<!--chtml if pinemode="function_key"--> 13635F4. 13636<!--chtml else--> 13637"T". 13638<!--chtml endif--> 13639To create a new list or add to an existing list, switch the screen display 13640into List Mode by pressing 13641<!--chtml if pinemode="function_key"--> 13642F12. 13643<!--chtml else--> 13644"L". 13645<!--chtml endif--> 13646In List Mode, you select the 13647group of addresses you wish to manipulate by marking them with an 13648"X". 13649The Set/Unset 13650<!--chtml if pinemode="function_key"--> 13651(F9) 13652<!--chtml else--> 13653("X") 13654<!--chtml endif--> 13655command will turn the "X" on for the 13656highlighted address if it was off or turn it off if it was previously on. 13657The SetAll command will select all of the addresses, and the UnSetAll 13658command will turn off all the selections. Once you've gotten the 13659selection the way you want it, you may create a new list by pressing 13660<!--chtml if pinemode="function_key"--> 13661F4. 13662<!--chtml else--> 13663"T". 13664<!--chtml endif--> 13665<P> 13666 13667In both the simple and list cases, after choosing to take the address, 13668you will be asked for the nickname of the entry. Typing in a new name 13669creates the new entry/list. Entering an existing nickname will replace 13670the entry (simple case) or add to the list (list case). Alternatively, 13671you can press Ctrl-T at the nickname prompt and select an existing 13672nickname from your address book. 13673<P> 13674 13675You will normally start in Single Mode, unless you used the Apply command 13676to startup the TakeAddr screen, in which case you will start in List Mode. 13677You may switch between the two modes at any time. If you've already 13678selected several addresses in List Mode, those will be remembered when you 13679switch to Single Mode and then back to List Mode. The set of addresses 13680that are pre-selected when you start in List Mode are the From addresses 13681of all of the messages you are operating on. You may, of course, easily 13682erase those selections with the UnSetAll command. 13683<P> 13684 13685If you have more than one writable address book, you will be prompted for 13686the name of the address book you wish to add the new entry to before 13687anything else. You can use ^N and ^P to choose among the defined address 13688books, or type in the address book name. 13689<P> 13690 13691FOR MORE INFORMATION on addressing see 13692<A HREF="h_address_format">Explanation of Address formats</A>, and the 13693<A HREF="h_abook_opened">Address Book Screen's</A> 13694help text. 13695<P> 13696<End of help on this topic> 13697</BODY> 13698</HTML> 13699===== h_takeexport_screen ===== 13700<HTML> 13701<HEAD> 13702<TITLE>Take Export Screen Explained</TITLE> 13703</HEAD> 13704<BODY> 13705<H1>TAKE EXPORT COMMANDS</H1> 13706<!--chtml if pinemode="function_key"--> 13707<PRE> 13708Navigating the List of Addresses Address Selection Commands 13709-------------------------------- -------------------------- 13710 F5 Move to previous entry F3 Exit without taking address 13711 F6 Move to next entry F4 Take current address(es) 13712 F7 Show previous page of address list 13713 F8 Show next page of address list 13714 F2 WhereIs (search list) 13715 -------------- 13716Mode Toggle F9 Set/Unset current address 13717----------- F10 Set all 13718 F12 Toggle between List and single mode F11 Unset all 13719</PRE> 13720<!--chtml else--> 13721<PRE> 13722Navigating the List of Addresses Address Selection Commands 13723-------------------------------- -------------------------- 13724 P Move to previous entry < Exit without taking address 13725 N Move to next entry T Take address 13726 - Show previous page of address list 13727Spc (space bar) Show next page of address list 13728 W WhereIs (search list) List Mode 13729 --------- 13730Single Mode X Set/Unset current address 13731----------- A Set all addresses 13732 L Switch to list mode U Unset all addresses 13733 S Switch to single mode 13734</PRE> 13735<!--chtml endif--> 13736 13737<H2>Description of the Take Export Screen</H2> 13738 13739This screen is designed to let you select one or more addresses 13740from the current message and put them into a file. 13741Only the user@domain_name part of each address is put into the file. 13742<P> 13743 13744To put a single entry into a file simply highlight the correct line and press 13745<!--chtml if pinemode="function_key"--> 13746F4. 13747<!--chtml else--> 13748"T". 13749<!--chtml endif--> 13750To put more than one entry into a file 13751switch the screen display 13752into List Mode by pressing 13753<!--chtml if pinemode="function_key"--> 13754F12. 13755<!--chtml else--> 13756"L". 13757<!--chtml endif--> 13758In List Mode, you select the 13759group of addresses you wish to manipulate by marking them with an 13760"X". 13761The Set/Unset 13762<!--chtml if pinemode="function_key"--> 13763(F9) 13764<!--chtml else--> 13765("X") 13766<!--chtml endif--> 13767command will turn the "X" on for the 13768highlighted address if it was off or turn it off if it was previously on. 13769The SetAll command will select all of the addresses, and the UnSetAll 13770command will turn off all the selections. Once you've gotten the 13771selection the way you want it, you may put the addresses in a file by typing 13772<!--chtml if pinemode="function_key"--> 13773F4. 13774<!--chtml else--> 13775"T". 13776<!--chtml endif--> 13777<P> 13778 13779You will be asked for the name of a file to put the addresses in. 13780If the file already exists, you will be asked whether you want to Overwrite 13781(replace) the contents of the file or Append to the contents of the file. 13782<P> 13783 13784<End of help on this topic> 13785</BODY> 13786</HTML> 13787============= h_abook_view ======================== 13788<HTML> 13789<HEAD> 13790<TITLE>Address Book View Explained</TITLE> 13791</HEAD> 13792<BODY> 13793This function allows you to view the contents of an address book entry. You 13794can only view one entry at a time. 13795<P> 13796<DL> 13797<DT>Help 13798<!--chtml if pinemode="function_key"--> 13799(F1) 13800<!--chtml else--> 13801(?) 13802<!--chtml endif--> 13803</DT> 13804<DD> 13805Display this help text. 13806 13807<DT>Abook 13808<!--chtml if pinemode="function_key"--> 13809(F3) 13810<!--chtml else--> 13811(<) 13812<!--chtml endif--> 13813</DT> 13814<DD> 13815Go back to index of address book entries. 13816 13817<DT>Update 13818<!--chtml if pinemode="function_key"--> 13819(F4) 13820<!--chtml else--> 13821(U) 13822<!--chtml endif--> 13823</DT> 13824<DD> 13825Update (modify) this entry. 13826 13827<DT>ComposeTo 13828<!--chtml if pinemode="function_key"--> 13829(F5) 13830<!--chtml else--> 13831(C) 13832<!--chtml endif--> 13833</DT> 13834<DD>Compose a message to the address(es) in this entry. 13835 13836<DT>Role 13837<!--chtml if pinemode="function_key"--> 13838(F6) 13839<!--chtml else--> 13840(#) 13841<!--chtml endif--> 13842</DT> 13843<DD>Compose a message to the address(es) in this entry using roles. 13844 13845<DT>Prev Page 13846<!--chtml if pinemode="function_key"--> 13847(F7) 13848<!--chtml else--> 13849(-) 13850<!--chtml endif--> 13851</DT> 13852<DD> 13853Show the previous page of the current entry. 13854 13855<DT>Next Page 13856<!--chtml if pinemode="function_key"--> 13857(F8) 13858<!--chtml else--> 13859(Space) 13860<!--chtml endif--> 13861</DT> 13862<DD> 13863Show the next page of the current entry. 13864 13865<DT>Print 13866<!--chtml if pinemode="function_key"--> 13867(F9) 13868<!--chtml else--> 13869(%) 13870<!--chtml endif--> 13871</DT> 13872<DD>Print the current entry. You can select the 13873printer or the print command via the "Setup" command 13874on the MAIN MENU. 13875 13876<DT>WhereIs 13877<!--chtml if pinemode="function_key"--> 13878(F10) 13879<!--chtml else--> 13880(W) 13881<!--chtml endif--> 13882</DT> 13883<DD>Search the entry for a string of letters. If it is 13884found, move to it. The string can be one word or a phrase. 13885If there are multiple occurrences, the cursor moves to the 13886first occurrence beyond the current cursor position. 13887 13888<DT>Fwd Email 13889<!--chtml if pinemode="function_key"--> 13890(F11) 13891<!--chtml else--> 13892(F) 13893<!--chtml endif--> 13894</DT> 13895<DD>Begin composition of a new mail message with the displayed 13896text already inserted in the message body. 13897 13898</DL> 13899<P> 13900<End of help on this topic> 13901</BODY> 13902</HTML> 13903============= h_ldap_view ======================== 13904<HTML> 13905<HEAD> 13906<TITLE>LDAP Response View Explained</TITLE> 13907</HEAD> 13908<BODY> 13909This function allows you to view the contents of a directory entry. You 13910can only view one entry at a time. 13911<P> 13912<DL> 13913<DT>Help 13914<!--chtml if pinemode="function_key"--> 13915(F1) 13916<!--chtml else--> 13917(?) 13918<!--chtml endif--> 13919</DT> 13920<DD> 13921Display this help text. 13922 13923<DT>Results Index 13924<!--chtml if pinemode="function_key"--> 13925(F3) 13926<!--chtml else--> 13927(<) 13928<!--chtml endif--> 13929</DT> 13930<DD>Go back to index of search results. 13931 13932<DT>ComposeTo 13933<!--chtml if pinemode="function_key"--> 13934(F5) 13935<!--chtml else--> 13936(C) 13937<!--chtml endif--> 13938</DT> 13939<DD>Compose a message to the address(es) in this entry. 13940 13941<DT>Role 13942<!--chtml if pinemode="function_key"--> 13943(F6) 13944<!--chtml else--> 13945(#) 13946<!--chtml endif--> 13947</DT> 13948<DD>Compose a message to the address(es) in this entry using roles. 13949 13950<DT>Prev Page 13951<!--chtml if pinemode="function_key"--> 13952(F7) 13953<!--chtml else--> 13954(-) 13955<!--chtml endif--> 13956</DT> 13957<DD> 13958Show the previous page of the current entry. 13959 13960<DT>Next Page 13961<!--chtml if pinemode="function_key"--> 13962(F8) 13963<!--chtml else--> 13964(Space) 13965<!--chtml endif--> 13966</DT> 13967<DD> 13968Show the next page of the current entry. 13969 13970<DT>Print 13971<!--chtml if pinemode="function_key"--> 13972(F9) 13973<!--chtml else--> 13974(%) 13975<!--chtml endif--> 13976</DT> 13977<DD>Print the current entry on paper. You can select the 13978printer or the print command via the "Setup" command 13979on the MAIN MENU. 13980 13981<DT>WhereIs 13982<!--chtml if pinemode="function_key"--> 13983(F10) 13984<!--chtml else--> 13985(W) 13986<!--chtml endif--> 13987</DT> 13988<DD>Search the entry for a string of letters. If it is 13989found, move to it. The string can be one word or a phrase. 13990If there are multiple occurrences, the cursor moves to the 13991first occurrence beyond the current cursor position. 13992 13993<DT>Fwd Email 13994<!--chtml if pinemode="function_key"--> 13995(F11) 13996<!--chtml else--> 13997(F) 13998<!--chtml endif--> 13999</DT> 14000<DD>Begin composition of a new mail message with the displayed 14001text already inserted in the message body. 14002 14003<DT>Save 14004<!--chtml if pinemode="function_key"--> 14005(F12) 14006<!--chtml else--> 14007(S) 14008<!--chtml endif--> 14009</DT> 14010<DD>Save the displayed entry to one of your address books or export 14011it to a file. 14012</DL> 14013<P> 14014<End of help on this topic> 14015</BODY> 14016</HTML> 14017===== h_attachment_screen ===== 14018<HTML> 14019<HEAD> 14020<TITLE>Attachment Index Screen Explained</TITLE> 14021</HEAD> 14022<BODY> 14023The "ATTACHMENT INDEX" displays a list of the current 14024message's attachments, and allows various operations on them. The 14025first attachment is usually the message text, but does not include the 14026header portion of the message. 14027<P> 14028Available commands include: 14029<P> 14030<DL> 14031 14032<DT>Help</DT> 14033<DD>Show this help text. 14034 14035<DT>Msg #<I>num</I></DT> 14036<DD>Leave this screen without displaying or saving any attachments. 14037 14038<DT>View</DT> 14039<DD>View the currently selected attachment. 14040 14041<DT>External</DT> 14042<DD>Passes a TEXT/HTML message to an external browser for its display. 14043 14044<DT>Prev Attach</DT> 14045<DD>Move to previous attachment. 14046 14047<DT>Next Attach</DT> 14048<DD>Move to next attachment. 14049 14050<DT>Prev Page</DT> 14051<DD>Previous page of the listed attachments. 14052 14053<DT>Next Page</DT> 14054<DD>Next page of the listed attachments. 14055 14056<DT>Delete</DT> 14057<DD>Mark the currently selected attachment for Deletion. 14058This does not modify the current message by deleting the attachment from 14059it, but instead the delete flag <EM>only</EM> has an effect when saving 14060the message to a folder. 14061Attachments marked for deletion are not copied to the destination folder 14062along with the rest of the message when it is saved. 14063It is ok for the destination folder to be the same as the current folder. 14064In addition, the delete mark <EM>only</EM> applies to this Alpine session. 14065 14066<DT>Undelete</DT> 14067<DD>Turn off the Delete flag for the selected attachment. 14068 14069<DT>Save</DT> 14070<DD>Save the selected attachment to a file. If the attachment is of 14071type "RFC822/Message", then the attachment will be saved to 14072the specified mail folder. 14073 14074<DT>Export</DT> 14075<DD>If the attachment is of 14076type "RFC822/Message", then "Export" is used to 14077copy the message to a file in the same way this command works on 14078messages in the MESSAGE INDEX and MESSAGE TEXT screens. 14079 14080<DT>Pipe</DT> 14081<DD>Pipe the attachment contents into a UNIX command (if enabled). 14082A description of the Pipe sub-commands is <A HREF="h_pipe_command">here</A>. 14083 14084<DT>WhereIs</DT> 14085<DD>Find a matching string in the attachment list. 14086 14087<DT>AboutAttch</DT> 14088<DD>Examine various aspects of the selected attachment. 14089 14090<DT>Print</DT> 14091<DD>Print the selected attachment. 14092 14093<DT>Forward</DT> 14094<DD>Forward the selected attachment as an attachment. 14095</DL> 14096 14097<P> 14098 14099All attachments can be saved or piped into a UNIX command, but some may 14100not be readily displayed by either Alpine or an external tool. In such 14101cases, the reason why the message cannot be displayed is displayed on 14102Alpine's message line. 14103<P> 14104<End of help on this topic> 14105</BODY> 14106</HTML> 14107============= h_mail_text_att_view ======================== 14108<HTML> 14109<HEAD> 14110<TITLE>Attachment View Screen Explained</TITLE> 14111</HEAD> 14112<BODY> 14113This function allows you to view the contents of a text attachment. You 14114can only view one attachment at a time. 14115<P> 14116Available commands include: 14117<P> 14118<DL> 14119 14120<DT>Help</DT> 14121<DD>Display this help text 14122 14123<DT>AttchIndex</DT> 14124<DD>Leave viewer and return to the "ATTACHMENT INDEX" screen 14125 14126<DT>Prev Page</DT> 14127<DD>Show the previous page of the current attachment. 14128 14129<DT>Next Page</DT> 14130<DD>Show the next page of the current attachment by pressing the space bar. 14131 14132<DT>Delete</DT> 14133<DD>Mark the viewed attachment for Deletion. The delete 14134flag <EM>only</EM> has affect when saving the message to a folder. 14135Attachments marked for deletion are excluded from the message when 14136it is saved. In addition, the delete mark <EM>only</EM> applies to 14137this Alpine session. 14138 14139<DT>Undelete</DT> 14140<DD>Turn off the Delete flag for the selected attachment. 14141 14142<DT>Save</DT> 14143<DD>Copy the current attachment to a file. If you just enter 14144a filename, the attachment will be saved with that name in 14145your home directory 14146<!--chtml if pinemode="running"--> 14147(which, in the present configuration of your system, is 14148 "<!--#echo var="HOME_DIR"-->") 14149<!--chtml endif--> 14150or current working directory 14151<!--chtml if pinemode="running"--> 14152(which, at least for your current Alpine "session," 14153is "<!--#echo var="CURRENT_DIR"-->") 14154<!--chtml endif-->, depending on the 14155<A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> 14156configuration setting. You may enter the full 14157path and filename to save it in another directory instead. 14158 14159<DT>Export</DT> 14160<DD>If the attachment is of 14161type "RFC822/Message", then "Export" is used to 14162copy the message to a file in the same way this command works on 14163messages in the MESSAGE INDEX and MESSAGE TEXT screens. 14164(If you have any <A HREF="h_config_display_filters"><!--#echo var="VAR_display-filters"--></A> 14165defined, they may affect the contents of the exported file.) 14166 14167<DT>Pipe</DT> 14168<DD>Pipe the attachment contents into a UNIX command (if enabled) 14169 14170<DT>WhereIs</DT> 14171<DD>Search the attachment for a string of letters. If it is 14172found, move to it. The string can be one word or a phrase. 14173If there are multiple occurrences, the cursor moves to the 14174first occurrence beyond the current cursor position. 14175 14176<DT>Print</DT> 14177<DD>Print the current attachment on paper. You can select the 14178printer or the print command via the "Setup" command 14179on the MAIN MENU. 14180 14181<DT>Forward</DT> 14182<DD>Forward the selected attachment as an attachment. 14183</DL> 14184<P> 14185<End of help on this topic> 14186</BODY> 14187</HTML> 14188============= h_journal ============== 14189<HTML> 14190<HEAD> 14191<TITLE>Recent Message Journal Explained</TITLE> 14192</HEAD> 14193<BODY> 14194 14195The following commands are available on this screen: 14196<P> 14197<DL> 14198<DT>Help</DT> 14199<DD>Show this help text 14200 14201<DT>Exit</DT> 14202<DD>Exit Viewer, and go back to mail processing 14203 14204<DT>Prev Page</DT> 14205<DD>Show the previous page text 14206 14207<DT>Next Page</DT> 14208<DD>Show the next page of text by pressing the space bar 14209 14210<DT>Print</DT> 14211<DD>Print the displayed text on paper. You can select the 14212printer or the print command via the "Setup" command 14213on the MAIN MENU. 14214 14215<DT>Fwd Email</DT> 14216<DD>Begin composition of a new mail message with the displayed 14217text already inserted in the message body. 14218 14219<DT>Save</DT> 14220<DD>Copy the displayed text to a file. If you just enter 14221a filename, the text will be saved with that name in 14222your 14223home directory 14224<!--chtml if pinemode="running"--> 14225(which, in the present configuration of your system, is 14226 "<!--#echo var="HOME_DIR"-->") 14227<!--chtml endif--> 14228or current working directory 14229<!--chtml if pinemode="running"--> 14230(which, at least for your current Alpine "session," 14231is "<!--#echo var="CURRENT_DIR"-->") 14232<!--chtml endif-->, depending on the 14233<A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> 14234configuration setting. You may enter the full 14235path and filename to save it in another directory instead. 14236 14237<DT>WhereIs</DT> 14238<DD>Search the text for a string of letters. If it is 14239found, move to it. The string can be one word or a phrase. 14240If there are multiple occurrences, the cursor moves to the 14241first occurrence beyond the current cursor position. 14242</DL> 14243<P> 14244<End of help on this topic> 14245</BODY> 14246</HTML> 14247============= h_debugjournal ============== 14248<HTML> 14249<HEAD> 14250<TITLE>Debug Journal Explained</TITLE> 14251</HEAD> 14252<BODY> 14253 14254The following commands are available on this screen: 14255<P> 14256<DL> 14257<DT>Help</DT> 14258<DD>Show this help text 14259 14260<DT>Exit</DT> 14261<DD>Exit Viewer, and go back to mail processing 14262 14263<DT>Timestamps</DT> 14264<DD>Turn on or off timestamps. 14265 14266<DT>DebugView</DT> 14267<DD>Set the level of debugging you want to see. The level may be any number 14268in the range 0-9. Higher numbers show more debugging detail. Note that the 14269debugging information has already been captured. This setting just causes the 14270debugging information that you see to be filtered. If you set this to 14271the number "5" then you will be shown all of the debugging information 14272at levels 5 and below. 14273It's actually a bit more complicated than that. A fixed amount of memory 14274is used to store the debug information. 14275Since the amount of memory used is limited the debugging information 14276has to be trimmed back when it gets too large. 14277 14278<DT>Prev Page</DT> 14279<DD>Show the previous page text 14280 14281<DT>Next Page</DT> 14282<DD>Show the next page of text by pressing the space bar 14283 14284<DT>Print</DT> 14285<DD>Print the displayed text on paper. You can select the 14286printer or the print command via the "Setup" command 14287on the MAIN MENU. 14288 14289<DT>Fwd Email</DT> 14290<DD>Begin composition of a new mail message with the displayed 14291text already inserted in the message body. 14292 14293<DT>Save</DT> 14294<DD>Copy the displayed text to a file. If you just enter 14295a filename, the text will be saved with that name in 14296your 14297home directory 14298<!--chtml if pinemode="running"--> 14299(which, in the present configuration of your system, is 14300 "<!--#echo var="HOME_DIR"-->") 14301<!--chtml endif--> 14302or current working directory 14303<!--chtml if pinemode="running"--> 14304(which, at least for your current Alpine "session," 14305is "<!--#echo var="CURRENT_DIR"-->") 14306<!--chtml endif-->, depending on the 14307<A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> 14308configuration setting. You may enter the full 14309path and filename to save it in another directory instead. 14310 14311<DT>WhereIs</DT> 14312<DD>Search the text for a string of letters. If it is 14313found, move to it. The string can be one word or a phrase. 14314If there are multiple occurrences, the cursor moves to the 14315first occurrence beyond the current cursor position. 14316</DL> 14317<P> 14318<End of help on this topic> 14319</BODY> 14320</HTML> 14321============= h_simple_text_view ============== 14322<HTML> 14323<HEAD> 14324<TITLE>Simple Text View Screen Explained</TITLE> 14325</HEAD> 14326<BODY> 14327 14328The following commands are available on this screen: 14329<P> 14330<DL> 14331<DT>Help</DT> 14332<DD>Show this help text 14333 14334<DT>Exit</DT> 14335<DD>Exit Viewer, and go back to mail processing 14336 14337<DT>Prev Page</DT> 14338<DD>Show the previous page text 14339 14340<DT>Next Page</DT> 14341<DD>Show the next page of text by pressing the space bar 14342 14343<DT>Print</DT> 14344<DD>Print the displayed text on paper. You can select the 14345printer or the print command via the "Setup" command 14346on the MAIN MENU. 14347 14348<DT>Fwd Email</DT> 14349<DD>Begin composition of a new mail message with the displayed 14350text already inserted in the message body. 14351 14352<DT>Save</DT> 14353<DD>Copy the displayed text to a file. If you just enter 14354a filename, the attachment will be saved with that name in 14355your 14356home directory 14357<!--chtml if pinemode="running"--> 14358(which, in the present configuration of your system, is 14359 "<!--#echo var="HOME_DIR"-->") 14360<!--chtml endif--> 14361or current working directory 14362<!--chtml if pinemode="running"--> 14363(which, at least for your current Alpine "session," 14364is "<!--#echo var="CURRENT_DIR"-->") 14365<!--chtml endif-->, depending on the 14366<A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> 14367configuration setting. You may enter the full 14368path and filename to save it in another directory instead. 14369 14370<DT>WhereIs</DT> 14371<DD>Search the attachment for a string of letters. If it is 14372found, move to it. The string can be one word or a phrase. 14373If there are multiple occurrences, the cursor moves to the 14374first occurrence beyond the current cursor position. 14375</DL> 14376<P> 14377<End of help on this topic> 14378</BODY> 14379</HTML> 14380======= h_pine_for_windows ======== 14381<HTML> 14382<HEAD> 14383<TITLE>GETTING HELP IN PC-ALPINE</TITLE> 14384</HEAD> 14385<BODY> 14386<H1>Getting Help In PC-Alpine</H1> 14387 14388<P> 14389PC-Alpine offers general and specific help text. From the <A 14390HREF="main_menu_tx">MAIN MENU</A>, you will find an overview in the MAIN 14391MENU HELP and the <A HREF="h_news">Release Notes</A>. On all screens, 14392specific help for that screen is available from the toolbar Help menu or 14393with the 14394<!--chtml if pinemode="function_key"--> 14395"F1" key. 14396<!--chtml else--> 14397"?" or "Ctrl-G" keys. "Ctrl-G" is used where 14398typing "?" would be mistaken as entering text. 14399<!--chtml endif--> 14400 14401<P> 14402Although this version of Alpine is for Microsoft Windows, it is not 14403considered a full "Graphical User Interface" application. 14404Yet, many of the controls that Windows users are accustomed to seeing, 14405such as scrollbars and toolbars, are available. 14406 14407<P> 14408PC-Alpine offers considerable mouse support. You can view what is 14409"click-able" by dragging your mouse over any screen; when the 14410arrow cursor changes into a hand, you found something. Mouse-click 14411possibilities include navigating between screens and folders and 14412double-clicking on hyperlinks to open your Web browser. 14413Context-sensitive pop-up menus appear with a right-click on your PC-Alpine 14414screen. Examples of right-click options include "copy" after 14415selecting text to copy and "View in New Window" when you click 14416on a particular message in the Message Index. The menu choices available 14417to you will vary based upon what screen is open, where on the screen your 14418cursor is located, and even what action you have already taken. 14419 14420<P> 14421<End of help on this topic> 14422</BODY> 14423</HTML> 14424===== h_composer ===== 14425<HTML> 14426<HEAD> 14427<TITLE>COMPOSER COMMANDS</TITLE> 14428</HEAD> 14429<BODY> 14430<H1>COMPOSER COMMANDS</H1> 14431 14432CURSOR MOTION KEYS |EDITING KEYS<BR> 14433 ^B (Left Arrow) Back character | ^D Delete current character<BR> 14434 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character<BR> 14435 ^P (Up Arrow) Previous line | ^^ Set a <A HREF="h_compose_markcutpaste">mark</A><BR> 14436 ^N (Down Arrow) Next line | <!--chtml if pinemode="function_key"-->F9<!--chtml else-->^K<!--chtml endif--> <A HREF="h_compose_markcutpaste">Cut</A> marked text or<BR> 14437 ^A Beginning of line | delete current line<BR> 14438 ^E End of line | <!--chtml if pinemode="function_key"-->F10<!--chtml else-->^U<!--chtml endif--> <A HREF="h_compose_markcutpaste">Paste</A> text, undelete lines<BR> 14439 ^Y Previous page | cut with ^K, or unjustify<BR> 14440 ^V Next page |-------------------------------------<BR> 14441 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS<BR> 14442---------------------------------------| <!--chtml if pinemode="function_key"-->F6<!--chtml else-->^W<!--chtml endif--> <A HREF="h_composer_search">Whereis</A> (search for string)<BR> 14443MESSAGE COMMANDS | GENERAL COMMANDS | <!--chtml if pinemode="function_key"-->F12<!--chtml else-->^T <!--chtml endif--> <A HREF="h_compose_spell">Spell checker</A><BR> 14444 <!--chtml if pinemode="function_key"-->F3<!--chtml else-->^C<!--chtml endif--> <A HREF="h_compose_cancel">Cancel</A> | <!--chtml if pinemode="function_key"-->F1<!--chtml else-->^G<!--chtml endif--> Get help | <!--chtml if pinemode="function_key"-->F4<!--chtml else-->^J<!--chtml endif--> <A HREF="h_compose_justify">Justify</A> paragraph<BR> 14445 <!--chtml if pinemode="function_key"-->F11<!--chtml else-->^O <!--chtml endif--> <A HREF="h_common_postpone">Postpone</A> | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen<BR> 14446 <!--chtml if pinemode="function_key"-->F2<!--chtml else-->^X<!--chtml endif--> <A HREF="h_compose_send">Send</A> | <!--chtml if pinemode="function_key"-->F6<!--chtml else-->^_<!--chtml endif--> <A HREF="h_compose_alted">Alt. editor</A> | <!--chtml if pinemode="function_key"-->F5<!--chtml else-->^R<!--chtml endif--> <A HREF="h_compose_readfile">Read in a file</A><BR> 14447 14448<P> 14449NOTE: 14450<OL> 14451 <LI>For help on a particular command, highlight the bold text associated 14452with it above and hit Return. 14453 <LI> The availability of certain commands 14454is determined by Alpine configuration files and system capabilities. 14455At some sites, certain commands may not be available due to security or 14456support concerns. 14457 <LI>Alpine does not use the following keys: Ctrl-S, Ctrl-Q, Ctrl-], 14458Ctrl-\, ESC. 14459 <LI>For special handling of Ctrl-S and Ctrl-Q see special comments regarding 14460<A HREF="h_special_xon_xoff">"XOFF/XON"</A>. 14461</OL> 14462 14463<P> 14464HINT: To move rapidly to the bottom of a message you are composing, 14465enter ^W^V. To go to the top, ^W^Y. These can be used in conjunction 14466with the Mark and Cut commands to eliminate large amounts of unwanted 14467text in a Reply. 14468 14469<H2>Description of Composer</H2> 14470 14471Alpine has a built-in editing program that allows you to compose messages 14472without having to leave Alpine. The editor is designed to be very simple to 14473use so that you can get started writing email right away. 14474 14475<P> 14476Messages are usually just text, about 80 columns wide. Using upper and 14477lower case is encouraged. On some systems the size limit of the message 14478is about 100,000 characters, which is about 2,000 lines. You can include 14479punctuation and special characters found on most keyboards, but you can't 14480include characters with diacritical marks and certain special symbols. 14481 14482<P> 14483Text automatically wraps as you type past the end of a line so you do not 14484have to hit return. Using the 14485"<A HREF="h_compose_justify">Justify</A>" command, 14486you can also reformat text explicitly, perhaps after you have 14487deleted some text. 14488 14489<P> 14490You can include other text files with the 14491"<A HREF="h_compose_readfile">Read File</A>" command, 14492which will prompt you for the name of the file to insert at the 14493current cursor position. 14494 14495<P> 14496<UL> 14497<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 14498</UL> 14499<P> 14500<End of help on this topic> 14501</BODY> 14502</HTML> 14503====== h_composer_browse ===== 14504<HTML> 14505<HEAD> 14506<TITLE>BROWSER</TITLE> 14507</HEAD> 14508<BODY> 14509<H1>BROWSER</H1> 14510This screen lets you browse your files and directories. To go to another 14511directory (identified by "(dir)"), move the cursor to it and 14512choose "Select" (the default choice on the menu); 14513or choose "Goto" and enter the name of the directory. 14514<!--chtml if pinemode="os_windows"--> 14515<!--chtml else--> 14516In Unix Alpine, you may use 14517"~" to refer to your home directory or "~user" to refer 14518to another's home directory. 14519<!--chtml endif--><P> 14520To select a file, move the cursor to it and 14521choose "Select" (the default choice on the menu). 14522<P> 14523<UL> 14524<LI>Note <B>if</B> you are currently using the BROWSER for choosing a file for 14525inclusion in the 14526message body (that is, you chose "Read File" with the cursor under 14527the 14528"----- Message Text -----" line 14529while composing, then "To Files"): Since the file 14530selected will become part of the message text, it must be in a format 14531suitable for that (Alpine does not check!), such as a plain text file. 14532Files of other formats (for example, graphics, databases, software 14533programs) should be 14534<B>attached</B> to the message instead -- 14535by moving the cursor in the COMPOSE MESSAGE screen into the 14536message header area and pressing 14537<!--chtml if pinemode="function_key"--> 14538F6. 14539<!--chtml else--> 14540Ctrl-J. 14541<!--chtml endif--> 14542 14543<P><LI> 14544Note <B>if</B> you are currently using the BROWSER for saving a message 14545attachment, or exporting a message, to a file: You can use the Add command to 14546provide the name for a new file to save/export to, and then select that name 14547to use it for the save/export operation. Back at the prompt 14548"EXPORT: Copy message to file in ..." hit Enter, then choose 14549either Overwrite or Append (it doesn't make a difference, since the file is 14550so far empty). Note: If you cancel the 14551operation at that point, the file created with the Add command will remain 145520 bytes in size. 14553 14554</UL> 14555<P><UL> 14556<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 14557</UL> 14558<P> 14559<End of help on this topic> 14560</BODY> 14561</HTML> 14562====== h_composer_ins ===== 14563<HTML> 14564<HEAD> 14565<TITLE>INSERT TEXT FILE</TITLE> 14566</HEAD> 14567<BODY> 14568<H1>INSERT TEXT FILE</H1> 14569 14570Use this function to insert a text file. The file name 14571given can be an absolute file path name for your system 14572<!--chtml if pinemode="os_windows"--> 14573(for example, "H:\SIGFILES\FULLINFO.TXT"), a file 14574with a relative pathname, or simply a file name without 14575drive or directory specification. 14576<!--chtml else--> 14577(for example, "/tmp/exported.earlier" on Unix hosts), 14578a file in your home directory, or a file path relative to your 14579home directory. In Unix Alpine, you may use "~" to refer to 14580your home directory or "~user" to refer to another 14581account's home directory. 14582<!--chtml endif--> 14583<P> 14584No wild card characters may be used. 14585The file must reside on the system running Alpine. 14586<P> 14587If the 14588<A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> 14589feature is set, names are relative to your current working directory 14590<!--chtml if pinemode="running"--> 14591(which, at least for your current Alpine "session," 14592is "<!--#echo var="CURRENT_DIR"-->") 14593<!--chtml endif--> 14594rather than your home directory 14595<!--chtml if pinemode="running"--> 14596(which, in the present configuration of your system, is 14597 "<!--#echo var="HOME_DIR"-->") 14598<!--chtml endif--> 14599. 14600<P><UL> 14601<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 14602</UL> 14603<P> 14604<End of help on this topic> 14605</BODY> 14606</HTML> 14607====== h_composer_ins_m ===== 14608<HTML> 14609<HEAD> 14610<TITLE>INSERT MESSAGE</TITLE> 14611</HEAD> 14612<BODY> 14613<H1>INSERT MESSAGE</H1> 14614 14615Type in the number of a message in the currently open folder to insert it 14616into your message. 14617<P><UL> 14618<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 14619</UL> 14620<P> 14621<End of help on this topic> 14622</BODY> 14623</HTML> 14624====== h_composer_search ===== 14625<HTML> 14626<HEAD> 14627<TITLE>Explanation of Composer Whereis Command </TITLE> 14628</HEAD> 14629<BODY> 14630<H1>Help For Whereis Command</H1> 14631 14632Whereis is used to search the message for a word or part of a word. 14633When searching in the composer, only the message part of your mail is 14634searched, and the cursor is put on the first occurrence appearing 14635after the location of the cursor. The search will wrap to the 14636beginning of the message when it no longer finds matches in the 14637remainder of the message. 14638 14639To search for the same string a second time, press 14640<!--chtml if pinemode="function_key"--> 14641"F6" 14642<!--chtml else--> 14643"^W" 14644<!--chtml endif--> 14645to begin search and then just press RETURN to accept the previous 14646search string shown in square brackets rather than entering a new 14647search string.<P> 14648 14649The "Search" prompt has several sub-command available: 14650 14651<DL> 14652<DT>Get Help</DT> 14653<DD> Takes you to this help page. 14654 14655<DT>Cancel</DT> 14656<DD> Cancels the prompt. No search takes place. 14657 14658<DT>First Line</DT> 14659<DD> Takes you back to the composer with the cursor on the first character 14660of the first line of text. 14661 14662<DT>Last Line</DT> 14663<DD> Takes you back to the composer with the cursor on the last character 14664of the last line of text. 14665 14666<DT>Replace (Optional)</DT> 14667<DD> This sub-command is enabled by the 14668<A HREF="h_config_enable_search_and_repl">"<!--#echo var="FEAT_enable-search-and-replace"-->"</A> 14669feature (which is on by default); see its help screen for details on how replacing works. 14670 14671</DL> 14672 14673<End of help on this topic> 14674</BODY> 14675</HTML> 14676====== h_sigedit_search ===== 14677<HTML> 14678<HEAD> 14679<TITLE>Explanation of Whereis Command </TITLE> 14680</HEAD> 14681<BODY> 14682<H1>Help For Whereis Command</H1> 14683 14684Whereis is used to search for a word or part of a word. 14685When searching the cursor is put on the first occurrence appearing 14686after the location of the cursor. The search will wrap to the 14687beginning of the signature when it no longer finds matches in the 14688remainder of the signature. 14689 14690To search for the same string a second time, press 14691<!--chtml if pinemode="function_key"--> 14692"F6" 14693<!--chtml else--> 14694"^W" 14695<!--chtml endif--> 14696to begin search and then just press RETURN to accept the previous 14697search string shown in square brackets rather than entering a new 14698search string.<P> 14699 14700The "Search" prompt has several sub-command available: 14701 14702<DL> 14703<DT>Get Help</DT> 14704<DD> Takes you to this help page. 14705 14706<DT>Cancel</DT> 14707<DD> Cancels the prompt. No search takes place. 14708 14709<DT>First Line</DT> 14710<DD> Takes you back to the composer with the cursor on the first character 14711of the first line of text. 14712 14713<DT>Last Line</DT> 14714<DD> Takes you back to the composer with the cursor on the last character 14715of the last line of text. 14716 14717<DT>Replace (Optional)</DT> 14718<DD> This sub-command is enabled by the 14719<A HREF="h_config_enable_search_and_repl">"<!--#echo var="FEAT_enable-search-and-replace"-->"</A> 14720feature (which is on by default); see its help screen for details on how replacing works. 14721 14722</DL> 14723 14724<End of help on this topic> 14725</BODY> 14726</HTML> 14727======= h_composer_to ==== 14728<HTML> 14729<HEAD> 14730<TITLE>THE MESSAGE COMPOSER'S TO FIELD</TITLE> 14731</HEAD> 14732<BODY> 14733<H1>THE MESSAGE COMPOSER'S TO FIELD</H1> 14734 14735<H2>The "To:" field</H2> 14736The address you enter here must be a valid email address that is reachable 14737from your site. 14738 14739<H2>Email Address Format</H2> 14740You may enter a full name and email address, 14741<!--chtml if pinemode="os_windows"--> 14742<!--chtml else--> 14743a local (meaning, on the same 14744host as the one you are running Alpine on) username that Alpine will 14745complete for you, 14746<!--chtml endif--> 14747the nickname of someone in a 14748<A HREF="h_abook_opened">Alpine Address Book</A>, or a local 14749mail alias defined by your system administrator. When you move the cursor 14750out of this field, the nicknames will be expanded to the addresses in your 14751address book, and the local usernames will be expanded to include the 14752persons' actual names. You may enter as many addresses as you wish, but they 14753must be separated by commas. You can move around this and other header fields 14754with the arrow keys and use many of the usual composer editing keys. 14755<P> 14756<UL> 14757<LI><A HREF="h_address_format">Explanation of Address formats</A> 14758</UL> 14759 14760<P> 14761<H2>MESSAGE HEADER COMMANDS</H2> 14762<!--chtml if pinemode="function_key"--> 14763CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------<BR> 14764^B (Left Arrow) Back character | ^D Delete current character<BR> 14765^F (Right Arrow) Forward character | ^H (DEL) Delete previous character<BR> 14766^P (Up Arrow) Previous line |<BR> 14767^N (Down Arrow) Next line | F9 Cut marked text or<BR> 14768^A Beginning of line | delete current line<BR> 14769^E End of line | F10 Undelete line(s)<BR> 14770F7 Previous page | ^W <A HREF="h_composer_search">Whereis</A> (search text)<BR> 14771F8 Next page |-------------------------------------<BR> 14772^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS<BR> 14773----------------------------------------|<BR> 14774MESSAGE COMMANDS | GENERAL COMMANDS | F12 To Addressbook/Browser<BR> 14775F3 <A HREF="h_compose_cancel">Cancel</A> | F1 Get help | F4 Attach File<BR> 14776F11 <A HREF="h_common_postpone">Postpone</A> | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen<BR> 14777F2 <A HREF="h_compose_send">Send</A> | | F5 <A HREF="h_compose_richhdr">Rich Headers</A><BR> 14778<!--chtml else--> 14779CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------<BR> 14780^B (Left Arrow) Back character | ^D Delete current character<BR> 14781^F (Right Arrow) Forward character | ^H (DEL) Delete previous character<BR> 14782^P (Up Arrow) Previous line | <BR> 14783^N (Down Arrow) Next line | ^K Cut marked text or<BR> 14784^A Beginning of line | delete current line<BR> 14785^E End of line | ^U Undelete line(s)<BR> 14786^Y Previous page |<BR> 14787^V Next page |-------------------------------------<BR> 14788^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS<BR> 14789----------------------------------------| ^R <A HREF="h_compose_richhdr">Rich Headers</A><BR> 14790MESSAGE COMMANDS | GENERAL COMMANDS | ^T To Addressbook/Browser<BR> 14791^C <A HREF="h_compose_cancel">Cancel</A> | ^G Get help | ^J Attach File<BR> 14792^O <A HREF="h_common_postpone">Postpone</A> | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen<BR> 14793^X <A HREF="h_compose_send">Send</A> | | TAB <A HREF="h_compose_addrcomplete">Address Completion</A><BR> 14794<!--chtml endif--> 14795 14796<P> 14797NOTE: 14798<OL> 14799 <LI>For help on a particular command, highlight the bold text associated 14800with it above and hit Return. 14801 <LI> The availability of certain commands 14802is determined by Alpine configuration files and system capabilities. 14803At some sites, certain commands may not be available due to security or 14804support concerns. 14805</OL> 14806 14807<P> 14808<UL> 14809<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 14810</UL><P> 14811<End of help on this topic> 14812</BODY> 14813</HTML> 14814======= h_composer_cc ==== 14815<HTML> 14816<HEAD> 14817<TITLE>THE MESSAGE COMPOSER'S CC FIELD</TITLE> 14818</HEAD> 14819<BODY> 14820<H1>THE MESSAGE COMPOSER'S CC FIELD</H1> 14821The Cc: field is just like the To: field, except it is used for addressees 14822that you wish to send a "carbon" copy to. That is, the message is 14823not directly meant directly "for" these recipients, but you wanted 14824them to see the message. The only difference the recipients see is that their 14825name is in the Cc: field, rather than the To: field. 14826<P> 14827For help with Cc: field editing 14828commands, check the <A HREF="h_composer_to">Help for the To:</A> header. 14829<P> 14830<UL> 14831<LI><A HREF="h_address_format">Explanation of Address formats</A> 14832</UL> 14833<P> 14834<UL> 14835<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 14836</UL><P> 14837<End of help on this topic> 14838</BODY> 14839</HTML> 14840======= h_composer_bcc ==== 14841<HTML> 14842<HEAD> 14843<TITLE>THE MESSAGE COMPOSER'S BCC FIELD</TITLE> 14844</HEAD> 14845<BODY> 14846<H1>THE MESSAGE COMPOSER'S BCC FIELD</H1> 14847The "Bcc:" (Blind carbon copy) header is used when you wish to send 14848a copy of the message to one or more people whose addresses you do not 14849wish disclosed, either to reduce clutter or for confidentiality. 14850<P> 14851The format of the Bcc: field is just the same as the To: and Cc: fields in 14852the way the addresses are entered. The recipients listed here will 14853receive a copy of the message, but --assuming your site's mail transport 14854software is properly configured-- their addresses will not show up in the 14855headers of the message, as delivered to all of the recipients. The To: 14856and Cc: recipients will not know a copy was sent to the Bcc: recipients. 14857<P> 14858Note: if there is no To: or Cc: or Lcc: address in the message, Alpine 14859will automatically generate and place in the To: field a pseudo-address of 14860 "undisclosed-recipients: ;" 14861or whatever string has been specified in the 14862<A HREF="h_config_empty_hdr_msg">"<!--#echo var="VAR_empty-header-message"-->"</A> 14863variable. 14864<P> 14865The reason for this is to avoid embarrassment caused by some Internet 14866mail transfer software that interprets a "missing" To: header as 14867an error and replaces it with an Apparently-to: header that may contain 14868the addresses you entered on the Bcc: line. In addition, it may be 14869less disconcerting to Bcc: recipients to see <B>something</B> in the To: field. 14870<P> 14871You can manipulate what text ends up on the (originally) empty To: 14872field. Just remember to put a colon and semicolon at the end of the 14873field, which is a special notation denoting that it is not a real address. 14874<P> 14875For information on message header editing 14876commands, check the <A HREF="h_composer_to">Help for the To:</A> header. 14877<P> 14878<UL> 14879<LI><A HREF="h_address_format">Explanation of Address formats</A> 14880</UL> 14881<P> 14882<UL> 14883<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 14884</UL><P> 14885<End of help on this topic> 14886</BODY> 14887</HTML> 14888======= h_composer_lcc ==== 14889<HTML> 14890<HEAD> 14891<TITLE>THE MESSAGE COMPOSER'S LCC FIELD</TITLE> 14892</HEAD> 14893<BODY> 14894<H1>THE MESSAGE COMPOSER'S LCC FIELD</H1> 14895The "Lcc:" (List carbon copy) header is intended to be used when 14896you wish to send a message to a list of people but avoid having all 14897of their addresses visible, in order to reduce clutter when the 14898message is received. 14899<P> 14900It is similar to the 14901<A HREF="h_composer_bcc">"Bcc" (Blind carbon copy) header</A> 14902in that individual 14903addressees are hidden, but Lcc is designed to work specifically with 14904distribution lists you have created in your 14905<A HREF="h_abook_opened">Alpine Address Book</A>. Placing 14906the nickname of the list on the Lcc line will result in the full name of 14907your Alpine Address Book list being placed on the To: line of the message, 14908using a special notation that distinguishes it from a real address. You 14909must leave the To: line blank for your list name to appear there. 14910<P> 14911For example, if you have this list entered in your Address Book:<PRE> 14912 14913 largo Key Largo List DISTRIBUTION LIST: 14914 bogie@mgm.com 14915 lauren@mgm.com 14916 walter@mgm.com</PRE> 14917 14918 14919and you enter "largo" on the Lcc: line while composing a message, 14920the result is:<PRE> 14921 14922 To : Key Largo List: ; 14923 Cc : 14924 Bcc : 14925 Fcc : sent-mail 14926 Lcc : Key Largo List <bogie@mgm.com>, 14927 lauren@mgm.com, 14928 walter@mgm.com 14929 Subject :</PRE> 14930 14931Each recipient listed on the Lcc: line receives a copy of the message 14932without their address being visible (as though they were listed on the 14933Bcc: line). The colon-semicolon notation used to put the full-name of the 14934list on the To: line is a special address format that doesn't specify any 14935actual addressees, but does give some information to the recipients of the 14936message. 14937<P> 14938Note: if after entering an LCC, you delete the list name that is placed 14939on the To: line, then recipients will see <PRE> 14940 To: undisclosed-recipients: ;</PRE> 14941 14942(or whatever string is defined in the 14943<A HREF="h_config_empty_hdr_msg">"<!--#echo var="VAR_empty-header-message"-->"</A> 14944variable) just as in the BCC case. 14945<P> 14946For help with Lcc: field editing 14947commands, check the <A HREF="h_composer_to">Help for the To:</A> header. 14948<P> 14949<UL> 14950<LI><A HREF="h_address_format">Explanation of Address formats</A> 14951</UL> 14952<P> 14953<UL> 14954<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 14955</UL><P> 14956<End of help on this topic> 14957</BODY> 14958</HTML> 14959======= h_composer_from ======= 14960<HTML> 14961<HEAD> 14962<TITLE>THE MESSAGE COMPOSER'S FROM FIELD</TITLE> 14963</HEAD> 14964<BODY> 14965<H1>THE MESSAGE COMPOSER'S FROM FIELD</H1> 14966 14967This header carries your return address. It is the address toward which 14968replies (and often, future unrelated correspondence) will be directed, 14969unless you have <A HREF="h_config_custom_hdrs">defined an optional 14970"Reply-To:" header</A> in the SETUP CONFIGURATION screen. Make 14971sure this address is correct. 14972<P> 14973For help with message header editing 14974commands, check the <A HREF="h_composer_to">Help for the To:</A> header. 14975<P> 14976<UL> 14977<LI><A HREF="h_address_format">Explanation of Address formats</A> 14978</UL> 14979<P> 14980<UL> 14981<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 14982</UL><P> 14983<End of help on this topic> 14984</BODY> 14985</HTML> 14986======= h_composer_reply_to ======= 14987<HTML> 14988<HEAD> 14989<TITLE>THE MESSAGE COMPOSER'S REPLY-TO FIELD</TITLE> 14990</HEAD> 14991<BODY> 14992<H1>THE MESSAGE COMPOSER'S REPLY-TO FIELD</H1> 14993 14994Most people should not need this header. The Reply-To: header is used in 14995cases where you would like replies to your messages to be directed to an 14996address other than your normal "From:" address. This is atypical, 14997but can happen when you use multiple machines and do not have the same account 14998name on each one, or when you wish to direct certain replies to accounts 14999or folders designated for specific classes of correspondence. 15000<P> 15001For help with message header editing 15002commands, check the <A HREF="h_composer_to">Help for the To:</A> header. 15003<P> 15004<UL> 15005<LI><A HREF="h_address_format">Explanation of Address formats</A> 15006</UL> 15007 15008<P> 15009<UL> 15010<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 15011</UL><P> 15012<End of help on this topic> 15013</BODY> 15014</HTML> 15015======= h_composer_custom_addr ==== 15016<HTML> 15017<HEAD> 15018<TITLE>CUSTOMIZED HEADER FIELD</TITLE> 15019</HEAD> 15020<BODY> 15021<H1>CUSTOMIZED HEADER FIELD</H1> 15022This is a customized header, i.e. not one that is part of Alpine's normal 15023set of Compose headers. 15024<P> 15025For help with message header editing 15026commands, check the <A HREF="h_composer_to">Help for the To:</A> header. 15027<P> 15028<UL> 15029<LI><A HREF="h_address_format">Explanation of Address formats</A> 15030</UL> 15031<P> 15032<UL> 15033<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 15034</UL><P> 15035<End of help on this topic> 15036</BODY> 15037</HTML> 15038======= h_composer_custom_free ==== 15039<HTML> 15040<HEAD> 15041<TITLE>CUSTOMIZED HEADER FIELD</TITLE> 15042</HEAD> 15043<BODY> 15044<H1>CUSTOMIZED HEADER FIELD</H1> 15045This is a customized header, i.e. not one that is part of Alpine's normal 15046set of Compose headers. 15047<P> 15048This field consists of arbitrary text. 15049<P> 15050For help with message header editing 15051commands, check the <A HREF="h_composer_to">Help for the To:</A> header. 15052<P> 15053<UL> 15054<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 15055</UL><P> 15056<End of help on this topic> 15057</BODY> 15058</HTML> 15059====== h_composer_news ===== 15060<HTML> 15061<HEAD> 15062<TITLE>THE MESSAGE COMPOSER'S NEWSGRPS LINE</TITLE> 15063</HEAD> 15064<BODY> 15065<h1>THE MESSAGE COMPOSER'S NEWSGRPS LINE</h1> 15066Use the newsgroups line to specify any and all USENET newsgroups to which 15067your message should be posted. When composing a message from scratch, this 15068line may be hidden. If so, just press the rich headers command 15069(<!--chtml if pinemode="function_key"-->F5<!--chtml else-->^R<!--chtml endif-->) 15070to make it visible. 15071<P> 15072<EM>Be aware</EM> that when you post to a newsgroup thousands of 15073people will be reading your message. Also, you or your system manager 15074must have defined an "<!--#echo var="VAR_nntp-server"-->" in your Alpine configuration 15075in order for you to be able to post. 15076<P> 15077For help with message header editing 15078commands, check the <A HREF="h_composer_to">Help for the To:</A> header. 15079<P><UL> 15080<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 15081</UL> 15082<P> 15083<End of help on this topic> 15084</BODY> 15085</HTML> 15086======= h_composer_fcc ==== 15087<HTML> 15088<HEADER> 15089<TITLE>THE MESSAGE COMPOSER'S FCC FIELD</TITLE> 15090</HEADER> 15091<BODY> 15092<H1>THE MESSAGE COMPOSER'S FCC FIELD</H1> 15093The FCC (File Carbon Copy) specifies the folder used to keep a copy of 15094each outgoing message. The default value can be configured with the 15095"<!--#echo var="VAR_default-fcc"-->" and "<!--#echo var="VAR_fcc-name-rule"-->" options. You can change or remove 15096the file carbon copy on any message you send by editing the FCC header.<p> 15097 15098You may type ^T to get a list of all your folders and select one to use as 15099the FCC for this message.<P> 15100 15101For help with message header editing 15102commands, check the <A HREF="h_composer_to">Help for the To:</A> header. 15103<P> 15104<UL> 15105<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 15106</UL><P> 15107<End of help on this topic> 15108</BODY> 15109</HTML> 15110======= h_composer_subject ==== 15111<HTML> 15112<HEADER> 15113<TITLE>THE MESSAGE COMPOSER'S SUBJECT FIELD</TITLE> 15114</HEADER> 15115<BODY> 15116<H1>THE MESSAGE COMPOSER'S SUBJECT FIELD</H1> 15117 15118The subject header provides a place to enter a few words that summarize 15119the topic of the message you are sending. You may leave this line blank, 15120but it is considered a courtesy to use a meaningful subject.<p> 15121 15122For help with message header editing 15123commands, check the <A HREF="h_composer_to">Help for the To:</A> header. 15124<P> 15125<UL> 15126<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 15127</UL><P> 15128<End of help on this topic> 15129</BODY> 15130</HTML> 15131======= h_composer_attachment ==== 15132<HTML> 15133<HEAD> 15134<TITLE>THE MESSAGE COMPOSER'S ATTCHMNT FIELD</TITLE> 15135</HEAD> 15136<BODY> 15137<H1>THE MESSAGE COMPOSER'S ATTCHMNT FIELD</H1> 15138 15139The "Attchmnt:" field is where you specify what file or 15140files you'd like attached to 15141the message you are composing. Those files must reside on the machine 15142running Alpine. If your file is on a PC or Mac and you run Alpine with an 15143account on a Unix machine, you'll have to transfer it before attaching it. 15144Contact local computer support people for assistance with transferring. 15145 15146<P> 15147The file name 15148given can be an absolute file path name for your system 15149<!--chtml if pinemode="os_windows"--> 15150(for example, "H:\SIGFILES\FULLINFO.TXT"), a file 15151with a relative pathname, or simply a file name without 15152drive or directory specification. 15153<!--chtml else--> 15154(for example, "/tmp/exported.earlier" on Unix hosts), 15155a file in your home directory, or a file path relative to your 15156home directory. In Unix Alpine, you may use "~" to refer to 15157your home directory or "~user" to refer to another 15158account's home directory. 15159<!--chtml endif--><P> 15160No wild card characters may be used. 15161<P>If the 15162<A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> 15163feature is set, names are relative to your current working directory 15164<!--chtml if pinemode="running"--> 15165(which, at least for your current Alpine "session," 15166is "<!--#echo var="CURRENT_DIR"-->") 15167<!--chtml endif--> 15168rather than your home directory 15169<!--chtml if pinemode="running"--> 15170(which, in the present configuration of your system, is 15171 "<!--#echo var="HOME_DIR"-->") 15172<!--chtml endif--> 15173. 15174<P> 15175Alpine uses MIME encoding for attachments, so binaries and files of any 15176length can safely be delivered to any MIME-capable mail reading program. 15177If you send an attachment to someone who does not have a MIME-capable mail 15178reading program yet, then the main message text will be readable, but 15179attachments (even attachments that are just plain text) are not. 15180<P> 15181 15182Typing the filename on the Attchmnt: line achieves the same 15183result as using the 15184<!--chtml if pinemode="function_key"--> 15185F6 15186<!--chtml else--> 15187Ctrl-J 15188<!--chtml endif--> command. 15189<P> 15190 15191If you Forward a message with attachments, you may delete them from your 15192Forwarded message by editing the Attchmnt header line. 15193<P> 15194 15195For help with message header editing 15196commands, check the <A HREF="h_composer_to">Help for the To:</A> header. 15197<P> 15198<UL> 15199<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 15200</UL><P> 15201<End of help on this topic> 15202</BODY> 15203</HTML> 15204======= h_composer_ctrl_j ==== 15205<HTML> 15206<HEAD> 15207<TITLE>COMPOSER ATTACH</TITLE> 15208</HEAD> 15209<BODY> 15210After the 15211<!--chtml if pinemode="function_key"--> 15212F6 15213<!--chtml else--> 15214Ctrl-J 15215<!--chtml endif--> command: 15216At the "File to attach:" prompt, enter the name of the 15217existing file to attach to your message. 15218When the feature 15219<A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A> 15220is set 15221you need only enter the beginning of the filename (enough of it to uniquely 15222identify the file) and press TAB to complete it. 15223 15224Or, press ^T to use the BROWSER screen for 15225selecting the file. <P> 15226For more information on attaching files, see the help screen for the 15227composer's 15228<A HREF="h_composer_attachment">Attchmnt: field</A>, which is normally hidden, 15229but can be revealed using the 15230<!--chtml if pinemode="function_key"--> 15231F5 15232<!--chtml else--> 15233Ctrl-R 15234<!--chtml endif--> 15235command with the cursor positioned above the 15236"----- Message Text -----" line in the COMPOSE MESSAGE screen. 15237<P> 15238<End of help on this topic> 15239</BODY> 15240</HTML> 15241======= h_edit_nav_cmds ========= 15242<HTML> 15243<HEAD> 15244<TITLE>Composer Editing Commands Explained</TITLE> 15245</HEAD> 15246<BODY> 15247<H1>EDITING and NAVIGATION COMMANDS</H1> 15248<!--chtml if pinemode="function_key"--> 15249<PRE> 15250CURSOR MOTION KEYS----------------------|EDITING KEYS------------------------- 15251^B (Left Arrow) Back character | ^D Delete current character 15252^F (Right Arrow) Forward character | ^H (DEL) Delete previous character 15253^P (Up Arrow) Previous line | 15254^N (Down Arrow) Next line | F9 Cut marked text or 15255^A Beginning of line | delete current line 15256^E End of line | F10 Undelete line(s) 15257F7 Previous page | 15258F8 Next page |------------------------------------- 15259^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS 15260----------------------------------------| 15261EXIT COMMANDS | GENERAL COMMANDS | F12 To Addressbook 15262F3 Cancel | F1 Get help | F12 RichView (expand lists) 15263F2 eXit/save | ^Z Suspend | ^L Redraw Screen 15264</PRE> 15265<!--chtml else--> 15266<PRE> 15267CURSOR MOTION KEYS----------------------|EDITING KEYS------------------------- 15268^B (Left Arrow) Back character | ^D Delete current character 15269^F (Right Arrow) Forward character | ^H (DEL) Delete previous character 15270^P (Up Arrow) Previous line | 15271^N (Down Arrow) Next line | ^K Cut marked text or 15272^A Beginning of line | delete current line 15273^E End of line | ^U Undelete line(s) 15274^Y Previous page | 15275^V Next page |------------------------------------- 15276^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS 15277----------------------------------------| 15278EXIT COMMANDS | GENERAL COMMANDS | ^T To Addressbook 15279^C Cancel | ^G Get help | ^R RichView (expand lists) 15280^X eXit/save | ^Z Suspend | ^L Redraw Screen 15281</PRE> 15282<!--chtml endif--> 15283<End of help on this topic> 15284</BODY> 15285</HTML> 15286===== h_composer_sigedit ===== 15287<HTML> 15288<HEAD> 15289<TITLE>Signature Editor Commands Explained</TITLE> 15290</HEAD> 15291<BODY> 15292<H1>SIGNATURE EDITOR COMMANDS</H1> 15293<!--chtml if pinemode="function_key"--> 15294<PRE> 15295CURSOR MOTION KEYS |EDITING KEYS 15296 ^B (Left Arrow) Back character | ^D Delete current character 15297 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character 15298 ^P (Up Arrow) Previous line | ^^ Set a mark 15299 ^N (Down Arrow) Next line | F9 Cut marked text or 15300 ^A Beginning of line | delete current line 15301 ^E End of line | F10 Paste text, undelete lines 15302 F7 Previous page | cut with ^K, or unjustify 15303 F8 Next page |------------------------------------- 15304 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS 15305---------------------------------------| F6 Whereis (search for string) 15306MESSAGE COMMANDS | GENERAL COMMANDS | F12 Spell checker 15307 F3 Cancel | F1 Get help | F4 Justify paragraph 15308 | ^Z Suspend | ^L Redraw Screen 15309 F2 Send | F6 Alt. editor | F5 Read in a file 15310</PRE> 15311<!--chtml else--> 15312<PRE> 15313CURSOR MOTION KEYS |EDITING KEYS 15314 ^B (Left Arrow) Back character | ^D Delete current character 15315 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character 15316 ^P (Up Arrow) Previous line | ^^ Set a mark 15317 ^N (Down Arrow) Next line | ^K Cut marked text or 15318 ^A Beginning of line | delete current line 15319 ^E End of line | ^U Paste text, undelete lines 15320 ^Y Previous page | cut with ^K, or unjustify 15321 ^V Next page |------------------------------------- 15322 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS 15323---------------------------------------| ^W <A HREF="h_composer_search">Whereis</A> (search text) 15324MESSAGE COMMANDS | GENERAL COMMANDS | ^T Spell checker 15325 ^C Cancel | ^G Get help | ^J <A HREF="h_compose_justify">Justify</A> paragraph 15326 | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen 15327 ^X Send | ^_ Alt. editor | ^R Read in a file 15328</PRE> 15329<!--chtml endif--> 15330 15331NOTE: The presence or absence of the following commands is determined 15332by "Feature-List" options in your Alpine configuration. Also, 15333some of these commands may be administratively disabled by your system 15334manager; if they don't work, please check with your local help desk 15335before reporting a bug. 15336<P> 15337<UL> 15338 <LI>Suspend (suspends Alpine and gives a system prompt) 15339 <LI>Alternate editor (allows you to compose with your own editor) 15340</UL> 15341<P> 15342 15343Alpine does not use the following keys: Ctrl-S, Ctrl-Q, Ctrl-], 15344Ctrl-\, ESC 15345<P> 15346 15347NOTE: For special handling of Ctrl-S and Ctrl-Q see special comments regarding 15348<A HREF="h_special_xon_xoff">"XOFF/XON"</A>. 15349<P> 15350<End of help on this topic> 15351</BODY> 15352</HTML> 15353===== h_composer_commentedit ===== 15354<HTML> 15355<HEAD> 15356<TITLE>Comment Editor Commands Explained</TITLE> 15357</HEAD> 15358<BODY> 15359<H1>COMMENT EDITOR COMMANDS</H1> 15360<!--chtml if pinemode="function_key"--> 15361<PRE> 15362CURSOR MOTION KEYS |EDITING KEYS 15363 ^B (Left Arrow) Back character | ^D Delete current character 15364 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character 15365 ^P (Up Arrow) Previous line | ^^ Set a mark 15366 ^N (Down Arrow) Next line | F9 Cut marked text or 15367 ^A Beginning of line | delete current line 15368 ^E End of line | F10 Paste text, undelete lines 15369 F7 Previous page | cut with ^K, or unjustify 15370 F8 Next page |------------------------------------- 15371 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS 15372---------------------------------------| F6 Whereis (search for string) 15373MESSAGE COMMANDS | GENERAL COMMANDS | F12 Spell checker 15374 F3 Cancel | F1 Get help | F4 Justify paragraph 15375 | ^Z Suspend | ^L Redraw Screen 15376 F2 Send | F6 Alt. editor | F5 Read in a file 15377</PRE> 15378<!--chtml else--> 15379<PRE> 15380CURSOR MOTION KEYS |EDITING KEYS 15381 ^B (Left Arrow) Back character | ^D Delete current character 15382 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character 15383 ^P (Up Arrow) Previous line | ^^ Set a mark 15384 ^N (Down Arrow) Next line | ^K Cut marked text or 15385 ^A Beginning of line | delete current line 15386 ^E End of line | ^U Paste text, undelete lines 15387 ^Y Previous page | cut with ^K, or unjustify 15388 ^V Next page |------------------------------------- 15389 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS 15390---------------------------------------| ^W <A HREF="h_composer_search">Whereis</A> (search text) 15391MESSAGE COMMANDS | GENERAL COMMANDS | ^T Spell checker 15392 ^C Cancel | ^G Get help | ^J <A HREF="h_compose_justify">Justify</A> paragraph 15393 | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen 15394 ^X Send | ^_ Alt. editor | ^R Read in a file 15395</PRE> 15396<!--chtml endif--> 15397 15398NOTE: The presence or absence of the following commands is determined 15399by "Feature-List" options in your Alpine configuration. Also, 15400some of these commands may be administratively disabled by your system 15401manager; if they don't work, please check with your local help desk 15402before reporting a bug. 15403<P> 15404<UL> 15405 <LI>Suspend (suspends Alpine and gives a system prompt) 15406 <LI>Alternate editor (allows you to compose with your own editor) 15407</UL> 15408<P> 15409 15410Alpine does not use the following keys: Ctrl-S, Ctrl-Q, Ctrl-], 15411Ctrl-\, ESC 15412<P> 15413 15414NOTE: For special handling of Ctrl-S and Ctrl-Q see special comments regarding 15415<A HREF="h_special_xon_xoff">"XOFF/XON"</A>. 15416<P> 15417<End of help on this topic> 15418</BODY> 15419</HTML> 15420======= h_composer_abook_nick ======= 15421<HTML> 15422<HEAD> 15423<TITLE>Addressbook Nickname Explained</TITLE> 15424</HEAD> 15425<BODY> 15426This is a short nickname for this address book entry. If it is used in 15427place of an address from the composer, the composer will fill in the 15428address(es) for the entry that matches the nickname. 15429<P> 15430 15431Look <A HREF="h_edit_nav_cmds">here</A> 15432to see the available Editing and Navigation commands. 15433<P> 15434<End of help on this topic> 15435</BODY> 15436</HTML> 15437======= h_composer_abook_full ======= 15438<HTML> 15439<HEAD> 15440<TITLE>Addressbook Fullname Explained</TITLE> 15441</HEAD> 15442<BODY> 15443This is the full name field for this entry. If this is going to be a 15444distribution list (more than one address), it should be a descriptive 15445phrase describing the list. It will be included in the mail header if you 15446put the list in the To: or CC: field, or in the To: line if you put the 15447list in the Lcc: field. It's OK to leave this field blank (and OK to 15448leave any of the other fields blank, too). If this address book entry is 15449going to be a simple entry with just one address, then this field is the 15450person's name. When you send mail to this entry, this is the field to the 15451left of the brackets. That is, it is the most readable part of the 15452address. For example, in the sample address: 15453<PRE> 15454 John Doe <jdoe@some.domain> 15455</PRE> 15456"John Doe" is the full name field. If you are sorting your address book 15457with one of the options that uses full names, then it might be useful to 15458enter the full name as "Last, First", for example: 15459<PRE> 15460 Doe, John 15461</PRE> 15462so that it will be sorted using Doe instead of John. This will be changed 15463back into John Doe when you use it. 15464<P> 15465Look <A HREF="h_edit_nav_cmds">here</A> 15466to see the available Editing and Navigation commands. 15467<P> 15468<End of help on this topic> 15469</BODY> 15470</HTML> 15471======= h_composer_abook_fcc ======= 15472<HTML> 15473<HEAD> 15474<TITLE>Addressbook Fcc Explained</TITLE> 15475</HEAD> 15476<BODY> 15477If this entry is the first one in the To: line of an outgoing message, 15478this field will be used for the Fcc (File Carbon Copy) instead of whatever 15479you would normally get (which depends on which 15480<A HREF="h_config_saved_msg_name_rule">"<!--#echo var="VAR_saved-msg-name-rule"-->"</A> 15481you've chosen). 15482<P> 15483If this field consists of two double quotes ("") that tells Alpine 15484that you don't want any Fcc associated with this entry. 15485<P> 15486Look <A HREF="h_edit_nav_cmds">here</A> 15487to see the available Editing and Navigation commands. 15488<P> 15489<End of help on this topic> 15490</BODY> 15491</HTML> 15492====== h_config_combined_abook_display ===== 15493<HTML> 15494<HEAD> 15495<TITLE>FEATURE: <!--#echo var="FEAT_combined-addrbook-display"--></TITLE> 15496</HEAD> 15497<BODY> 15498<H1>FEATURE: <!--#echo var="FEAT_combined-addrbook-display"--></H1> 15499 15500This feature affects the address book display screens. 15501Normally, expanding an address book from the ADDRESS BOOK LIST screen 15502will cause the remaining address books and directory servers to disappear 15503from the screen, leaving only the entries of the expanded address book. 15504If this feature is set, then the other address books will remain on the screen, 15505so that all of the address books can be present at once. 15506 15507<P> 15508The way that commands work won't be changed. 15509For example, the Select All command will select all of the entries in the 15510current address book, not all of the entries in all of the address books. 15511The WhereIs command will change a little. 15512It will search through all of the text on the screen plus all of the entries 15513from expanded address books. 15514 15515<P> 15516When this feature is set, the setting of the feature 15517<A HREF="h_config_expanded_addrbooks">"<!--#echo var="FEAT_expanded-view-of-addressbooks"-->"</A> 15518has an effect. 15519<P> 15520<End of help on this topic> 15521</BODY> 15522</HTML> 15523====== h_config_titlebar_color_style ===== 15524<HTML> 15525<HEAD> 15526<TITLE>OPTION: <!--#echo var="VAR_titlebar-color-style"--></TITLE> 15527</HEAD> 15528<BODY> 15529<H1>OPTION: <!--#echo var="VAR_titlebar-color-style"--></H1> 15530 15531This option affects the colors used to display the titlebar (the top 15532line on the screen) when viewing a message. 15533 15534<P> 15535The available options include: 15536<P> 15537 15538<DL> 15539<DT>default</DT> 15540<DD>The color of the titlebar will be the color you set for the 15541<A HREF="h_config_title_color">Title Color</A>. 15542The Title Color may be set by using the 15543<A HREF="h_color_setup">Setup Kolor</A> screen. 15544</DD> 15545 15546<DT>indexline</DT> 15547<DD>The color of the titlebar will be the same as the color of the 15548index line corresponding to the message being viewed. 15549The rules that determine what color the index line will be may be set 15550up by going to the Setup/Rules/Indexcolor screen. 15551If the index line for a message is not colored explicitly by the 15552Indexcolor rules, then the titlebar will be colored the same as for 15553the "default" option above (which is not the same color that 15554the index line itself will have). 15555</DD> 15556 15557<DT>reverse-indexline</DT> 15558<DD>This is similar to the "indexline" option except the 15559foreground and background colors from the corresponding index line will 15560be reversed. 15561For example, if the index line color is red letters on a white background, 15562then the titlebar will be white letters on a red background. 15563If the index line for a message is not colored explicitly by the 15564Indexcolor rules, then the titlebar will be colored the same as for 15565the "default" option above (which is not the same color that 15566the index line itself will have). 15567</DD> 15568</DL> 15569 15570<P> 15571 15572<UL> 15573<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 15574</UL><P> 15575<End of help on this topic> 15576</BODY> 15577</HTML> 15578====== h_config_index_color_style ===== 15579<HTML> 15580<HEAD> 15581<TITLE>OPTION: <!--#echo var="VAR_current-indexline-style"--></TITLE> 15582</HEAD> 15583<BODY> 15584<H1>OPTION: <!--#echo var="VAR_current-indexline-style"--></H1> 15585 15586This option affects the colors used to display the current line in the 15587MESSAGE INDEX screen. 15588If you do not have Index Color Rules defined, then this option will 15589have no effect in the index. 15590Those Rules may be defined by going to the Setup/Rules/Indexcolor screen. 15591<P> 15592If the option 15593<A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A> 15594is turned on and the 15595<A HREF="h_config_incunseen_color">Incoming Unseen Color</A> 15596is set to something other than the default, then 15597this option also affects the color used to display the current folder 15598in the Incoming FOLDER LIST screen. 15599 15600<P> 15601The available options include: 15602<P> 15603 15604<DL> 15605<DT>flip-colors</DT> 15606<DD>This is the default. 15607If an index line is colored because it matches one of your 15608Index Color Rules, then its colors will be reversed when it is the currently 15609highlighted line. 15610For example, if the line is normally red text on a blue background, then 15611when it is the current line it will be drawn as blue text on a red background. 15612<P> 15613The rest of the option values all revert to this flip-colors behavior if 15614there is no Reverse Color defined. 15615</DD> 15616 15617<DT>reverse</DT> 15618<DD>With this option the Reverse color is always used to highlight the 15619current line. 15620</DD> 15621 15622<DT>reverse-fg</DT> 15623<DD>The foreground part of the Reverse Color is used to highlight 15624the current line. 15625If this would cause the text to be unreadable (because the foreground and 15626background colors are the same) or if it would cause no change in the 15627color of the index line, then the colors are flipped instead. 15628<P> 15629Some people think this works particularly well if you use different 15630background colors to emphasize "interesting" lines, 15631but always with the same Normal foreground color, 15632and you use a different foreground color for the Reverse Color. 15633</DD> 15634 15635<DT>reverse-fg-no-ambiguity</DT> 15636<DD>With the "reverse-fg" rule above, it is possible that 15637the resulting color will be exactly the same as the regular Reverse 15638Color. 15639That can lead to some possible confusion because an 15640"interesting" 15641line that is the current line will be displayed exactly the same as a 15642non-interesting line that is current. 15643You can't tell whether the line is just a regular current line or if it is 15644an "interesting" current line by looking at the color. 15645Setting the option to this value removes that ambiguity. 15646It is the same as the "reverse-fg" setting unless the resulting 15647interesting current line would look just like a non-interesting current line. 15648In that case, the interesting line's colors are simply flipped (like in the 15649default behavior). 15650<P> 15651As an alternative way to preserve the line's interestingness in this case, 15652you may find that using both a different foreground and a different 15653background color for the interesting line will help. 15654</DD> 15655 15656<DT>reverse-bg</DT> 15657<DD>The background part of the Reverse Color is used to highlight 15658the current line. 15659If this would cause the text to be unreadable (because the foreground and 15660background colors are the same) or if it would cause no change in the 15661color of the index line, then the colors are flipped instead. 15662<P> 15663Some people think this works particularly well if you use different 15664foreground colors to emphasize "interesting" lines, 15665but always with the same Normal background color, 15666and you use a different background color for the Reverse Color. 15667</DD> 15668 15669<DT>reverse-bg-no-ambiguity</DT> 15670<DD>As with the "reverse-fg" case, the "reverse-bg" 15671rule may also result in a color that is exactly the same as the regular 15672Reverse Color. 15673Setting the option to this value removes that ambiguity. 15674It is the same as the "reverse-bg" setting unless the resulting 15675current line has the same color as the Reverse Color. 15676In that case, the interesting line's colors are simply flipped (like in the 15677default behavior). 15678</DD> 15679</DL> 15680 15681<P> 15682 15683<UL> 15684<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 15685</UL><P> 15686<End of help on this topic> 15687</BODY> 15688</HTML> 15689====== h_config_expanded_addrbooks ===== 15690<HTML> 15691<HEAD> 15692<TITLE>FEATURE: <!--#echo var="FEAT_expanded-view-of-addressbooks"--></TITLE> 15693</HEAD> 15694<BODY> 15695<H1>FEATURE: <!--#echo var="FEAT_expanded-view-of-addressbooks"--></H1> 15696 15697If multiple address books (either personal or global) are defined, and you 15698wish to have them all expanded implicitly upon entering the ADDRESS BOOK 15699screen, then set this feature. This feature will have no effect unless the 15700feature 15701<A HREF="h_config_combined_abook_display">"<!--#echo var="FEAT_combined-addrbook-display"-->"</A> 15702is also set. 15703<P> 15704<End of help on this topic> 15705</BODY> 15706</HTML> 15707====== h_config_combined_folder_display ===== 15708<HTML> 15709<HEAD> 15710<TITLE>FEATURE: <!--#echo var="FEAT_combined-folder-display"--></TITLE> 15711</HEAD> 15712<BODY> 15713<H1>FEATURE: <!--#echo var="FEAT_combined-folder-display"--></H1> 15714 15715This feature affects the folder list display screens. 15716Normally, each folder list is viewed within its collection only. This 15717command allows folder lists to be viewed within a single screen that 15718combines the contents of all collections. 15719 15720<P> 15721The way that commands work won't be changed. 15722For example, the Select All command will select all of the folders in the 15723current collection, not all of the entries in all of the collections. 15724The WhereIs command will change a little. 15725It will search through all of the folders in the current collection as well 15726as all the folder in any other expanded collection. 15727 15728<P> 15729When this feature is set, the setting of the feature 15730<A HREF="h_config_expanded_folders">"<!--#echo var="FEAT_expanded-view-of-folders"-->"</A> 15731has an effect. 15732<P> 15733<End of help on this topic> 15734</BODY> 15735</HTML> 15736====== h_config_combined_subdir_display ===== 15737<HTML> 15738<HEAD> 15739<TITLE>FEATURE: <!--#echo var="FEAT_combined-subdirectory-display"--></TITLE> 15740</HEAD> 15741<BODY> 15742<H1>FEATURE: <!--#echo var="FEAT_combined-subdirectory-display"--></H1> 15743 15744This feature affects the Folder List screen when 15745the 15746<A HREF="h_config_combined_folder_display">"<!--#echo var="FEAT_combined-folder-display"-->"</A> 15747feature is enabled. Normally, selecting a directory from the Folder 15748List takes you into a new screen displaying only the contents of 15749that directory. 15750 15751<P> 15752Enabling this feature will cause the contents of the selected 15753directory to be 15754displayed within the boundaries of the "Collection" it 15755is a part of. All previously displayed collections will remain 15756in the screen. 15757 15758<P> 15759The way that commands work won't be changed. 15760For example, the Select All command will select all of the folders in the 15761directory, as opposed to all of the entries in all of the collections. 15762The WhereIs command will change a little. 15763It will search through all of the folders in the current collection as well 15764as all the folder in any other expanded collection. 15765 15766<P> 15767<End of help on this topic> 15768</BODY> 15769</HTML> 15770====== h_config_separate_fold_dir_view ===== 15771<HTML> 15772<HEAD> 15773<TITLE>FEATURE: <!--#echo var="FEAT_separate-folder-and-directory-entries"--></TITLE> 15774</HEAD> 15775<BODY> 15776<H1>FEATURE: <!--#echo var="FEAT_separate-folder-and-directory-entries"--></H1> 15777 15778This feature affects folder collections wherein a folder 15779and directory can have the same name. By default, Alpine displays them 15780only once, denoting that it is both a folder and directory by appending 15781the folder name with the hierarchy character enclosed 15782in square brackets. 15783 15784 15785<P> 15786Enabling this feature will cause Alpine to display such names 15787separately marking the name representing a directory with a trailing 15788hierarchy delimiter (typically the slash, "/", character). 15789 15790<P> 15791The feature also alters the command set slightly. By default, the 15792right-arrow descends into the directory, while hitting the Return key will 15793cause the folder by that name to be opened. 15794 15795<P> 15796With this feature set, the Return key will open the highlighted folder, or 15797enter the highlighted directory. 15798 15799<P> 15800<End of help on this topic> 15801</BODY> 15802</HTML> 15803====== h_config_expanded_folders ===== 15804<HTML> 15805<HEAD> 15806<TITLE>FEATURE: <!--#echo var="FEAT_expanded-view-of-folders"--></TITLE> 15807</HEAD> 15808<BODY> 15809<H1>FEATURE: <!--#echo var="FEAT_expanded-view-of-folders"--></H1> 15810 15811If multiple folder collections are defined, and you 15812wish to have them all expanded implicitly upon entering the FOLDER LIST 15813screen, then set this feature. This feature will have no effect unless the 15814feature 15815<A HREF="h_config_combined_folder_display">"<!--#echo var="FEAT_combined-folder-display"-->"</A> 15816is also set. 15817<P> 15818<End of help on this topic> 15819</BODY> 15820</HTML> 15821======= h_config_ldap_server ======= 15822<HTML> 15823<HEAD> 15824<TITLE>LDAP OPTION: <!--#echo var="VAR_ldap-servers"--></TITLE> 15825</HEAD> 15826<BODY> 15827<H1>LDAP OPTION: <!--#echo var="VAR_ldap-servers"--></H1> 15828This is the name of the host where an LDAP server is running. 15829For redundancy, this may be a space-delimited set of server names, in which 15830case the first server that answers is used. 15831Each of the server names may be optionally followed by 15832a colon and a port number. 15833If this form is used then the port number configured below in the 15834<EM>port</EM> field is not used. 15835<P> 15836To find out whether your organization has its own LDAP server, 15837contact its computing support staff. 15838<P><UL> 15839<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 15840</UL> 15841<P> 15842<End of help on this topic> 15843</BODY> 15844</HTML> 15845======= h_config_ldap_base ======= 15846<HTML> 15847<HEAD> 15848<TITLE>LDAP OPTION: Search-Base</TITLE> 15849</HEAD> 15850<BODY> 15851<H1>LDAP OPTION: Search-Base</H1> 15852 15853This is the search base to be used on this server. It functions as a filter 15854by restricting your searches in the LDAP server database 15855to the specified contents of the specified fields. Without it, searches 15856submitted to this directory server may fail. It might be something 15857like: 15858 15859<PRE> 15860 O = <Your Organization Name>, C = US 15861</PRE> 15862or it might be blank. 15863(Some LDAP servers actually ignore anything specified here.) 15864<P> 15865If in doubt what parameters you should specify here, 15866contact the maintainers of the LDAP server. 15867<P><UL> 15868<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 15869</UL> 15870<P> 15871<End of help on this topic> 15872</BODY> 15873</HTML> 15874======= h_config_ldap_port ======= 15875<HTML> 15876<HEAD> 15877<TITLE>LDAP OPTION: Port</TITLE> 15878</HEAD> 15879<BODY> 15880<H1>LDAP OPTION: Port</H1> 15881 15882This is the TCP port number to be used with this LDAP server. If you leave 15883this blank port 389 will be used. 15884<P> 15885<End of help on this topic> 15886</BODY> 15887</HTML> 15888======= h_config_ldap_nick ======= 15889<HTML> 15890<HEAD> 15891<TITLE>LDAP OPTION: Nickname</TITLE> 15892</HEAD> 15893<BODY> 15894<H1>LDAP OPTION: Nickname</H1> 15895 15896This is a nickname to be used in displays. If you don't supply a 15897nickname the server name 15898(<A HREF="h_config_ldap_server">"<!--#echo var="VAR_ldap-servers"-->"</A>) 15899will be used instead. This option is strictly for your convenience. 15900<P> 15901<End of help on this topic> 15902</BODY> 15903</HTML> 15904======= h_config_ldap_binddn ======= 15905<HTML> 15906<HEAD> 15907<TITLE>LDAP OPTION: Bind-DN</TITLE> 15908</HEAD> 15909<BODY> 15910<H1>LDAP OPTION: Bind-DN</H1> 15911 15912You may need to authenticate to the LDAP server before you are able to use it. 15913This is the Distinguished Name to bind to when authenticating to this server. 15914Try leaving this blank until you know you need it. 15915<P> 15916Alpine only knows about LDAP Simple authentication. 15917It does not attempt LDAP SASL authentication. 15918The DN and password will be sent in the clear unless TLS encryption is 15919being used on this connection. 15920Because of this, you may want to set the LDAP feature 15921<A HREF="h_config_ldap_opts_tls">"Attempt-TLS-On-Connection"</A> 15922or the feature 15923<A HREF="h_config_ldap_opts_tlsmust">"Require-TLS-On-Connection"</A> 15924if you are going to be providing a password. 15925<P><UL> 15926<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 15927</UL> 15928<P> 15929<End of help on this topic> 15930</BODY> 15931</HTML> 15932======= h_config_ldap_opts_impl ======= 15933<HTML> 15934<HEAD> 15935<TITLE>LDAP FEATURE: Use-Implicitly-From-Composer</TITLE> 15936</HEAD> 15937<BODY> 15938<H1>LDAP FEATURE: Use-Implicitly-From-Composer</H1> 15939 15940Set this to have lookups done to this server implicitly from the composer. 15941If an address doesn't look like a fully-qualified address, it will be looked 15942up in your address books, and if it doesn't match a nickname there, then it 15943will be looked up on the LDAP servers that have this feature set. 15944The lookups will also be done when using the address completion feature 15945(TAB command) in the composer if any of the serves have this feature set. 15946Also see the LDAP feature 15947<A HREF="h_config_ldap_opts_rhs">"Lookup-Addrbook-Contents"</A> 15948and the Setup/Config feature 15949<A HREF="h_config_add_ldap">"<!--#echo var="FEAT_ldap-result-to-addrbook-add"-->"</A>. 15950<P> 15951<End of help on this topic> 15952</BODY> 15953</HTML> 15954======= h_config_ldap_opts_tls ======= 15955<HTML> 15956<HEAD> 15957<TITLE>LDAP FEATURE: Attempt-TLS-On-Connection</TITLE> 15958</HEAD> 15959<BODY> 15960<H1>LDAP FEATURE: Attempt-TLS-On-Connection</H1> 15961 15962When connecting to this server Alpine will attempt to use TLS encryption 15963on the connection. 15964Also see the closely related feature 15965<A HREF="h_config_ldap_opts_tlsmust">"Require-TLS-On-Connection"</A> 15966<P> 15967Note that if this option is set, then 15968<A HREF="h_config_ldap_opts_ldaps"> 15969"Require-LDAPS-On-Connection"</A> 15970can not be enabled for this server. You must disable this feature in 15971order to use 15972<A HREF="h_config_ldap_opts_ldaps"> 15973"Require-LDAPS-On-Connection"</A> 15974<P> 15975<End of help on this topic> 15976</BODY> 15977</HTML> 15978======= h_config_ldap_opts_tlsmust ======= 15979<HTML> 15980<HEAD> 15981<TITLE>LDAP FEATURE: Require-TLS-On-Connection</TITLE> 15982</HEAD> 15983<BODY> 15984<H1>LDAP FEATURE: Require-TLS-On-Connection</H1> 15985 15986When connecting to this server Alpine will attempt to use TLS encryption 15987on the connection. 15988If the StartTLS operation fails then the connection will not be used. 15989<P> 15990Note that if this option is set, then 15991<A HREF="h_config_ldap_opts_ldaps"> 15992"Require-LDAPS-On-Connection"</A> 15993can not be enabled for this server. You must disable this feature in 15994order to use 15995<A HREF="h_config_ldap_opts_ldaps"> 15996"Require-LDAPS-On-Connection"</A> 15997<P> 15998<End of help on this topic> 15999</BODY> 16000</HTML> 16001======= h_config_ldap_opts_ldaps ======= 16002<HTML> 16003<HEAD> 16004<TITLE>LDAP FEATURE: Require-LDAPS-On-Connection</TITLE> 16005</HEAD> 16006<BODY> 16007<H1>LDAP FEATURE: Require-LDAPS-On-Connection</H1> 16008 16009When connecting to this server Alpine will use LDAPS (LDAP over SSL/TLS) 16010on the connection. 16011<P> 16012This feature can not be used along with 16013<A HREF="h_config_ldap_opts_tlsmust">"Require-TLS-On-Connection"</A> 16014 or 16015<A HREF="h_config_ldap_opts_tls">"Attempt-TLS-On-Connection"</A>. 16016If you want to connect using StartTLS to this server, you must disable 16017this feature first. 16018<P> 16019<End of help on this topic> 16020</BODY> 16021</HTML> 16022====== h_config_ldap_opts_rhs ===== 16023<HTML> 16024<HEAD> 16025<TITLE>LDAP FEATURE: Lookup-Addrbook-Contents</TITLE> 16026</HEAD> 16027<BODY> 16028<H1>LDAP FEATURE: Lookup-Addrbook-Contents</H1> 16029 16030Normally implicit LDAP lookups from the composer are done only for the 16031strings you type in from the composer screen. In other words, you type in 16032something in the To or CC field and press return, then the string is looked up. 16033First that string is looked up in your address books. If a match is found 16034there, then the results of that match are looked up again. If you place 16035a string in your address book that you want to have looked up on the LDAP 16036directory server, you need to turn on this feature. If you set this feature 16037for a server, you almost always will also want to set the 16038<A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A> 16039feature. An example might serve to best illustrate this feature. 16040<P> 16041If an LDAP lookup of "William Clinton" normally returns an 16042entry with an 16043address of pres@whitehouse.gov, then you might put an entry in your address 16044book that looks like: 16045<P> 16046<CENTER><SAMP>Nickname = bill</SAMP></CENTER><BR> 16047<CENTER><SAMP>Address = "William Clinton"</SAMP></CENTER> 16048<P> 16049Now, when you type "bill" into an 16050address field in the composer Alpine will 16051find the "bill" entry in your address book. 16052It will replace "bill" with 16053"William Clinton". 16054It will then search for an entry with that nickname 16055in your address book and not find one. If this feature 16056is set, Alpine will then attempt to lookup 16057"William Clinton" on the LDAP server and find the entry with address 16058pres@whitehouse.gov. 16059<P> 16060A better way to accomplish the same thing is probably to use the feature 16061<A HREF="h_config_ldap_opts_ref">"Save-Search-Criteria-Not-Result"</A>. 16062<P> 16063<End of help on this topic> 16064</BODY> 16065</HTML> 16066====== h_config_ldap_opts_ref ===== 16067<HTML> 16068<HEAD> 16069<TITLE>LDAP FEATURE: Save-Search-Criteria-Not-Result</TITLE> 16070</HEAD> 16071<BODY> 16072<H1>LDAP FEATURE: Save-Search-Criteria-Not-Result</H1> 16073 16074Normally when you save the results of an LDAP directory lookup to your 16075address book the results of the lookup are saved. If this feature is set 16076and the entry being saved was found on this directory server, then the 16077search criteria is saved instead of the results of the search. When this 16078address book entry is used in the future, instead of copying the results 16079from the address book the directory lookup will be done again. This could 16080be useful if the copied result might become stale because the data on 16081the directory server changes (for example, the entry's email address changes). 16082You probably don't want to set this feature if the server is at all slow or 16083unreliable. 16084<P> 16085The way this actually works is that instead of saving the email address 16086in your address book, Alpine saves enough information to look up the same 16087directory entry again. In particular, it saves the server name and the 16088distinguished name of the entry. It's possible that the server administrators 16089might change the format of distinguished names on the server, or that the 16090entry might be removed from the server. If Alpine notices this, you will be warned 16091and a backup copy of the email address will be used. You may want to create 16092a new entry in this case, since you will get the annoying warning every 16093time you use the old entry. You may do that by Saving the entry to a new 16094nickname in the same address book. You will be asked whether or not you 16095want to use the backup email address. 16096<P> 16097A related feature in the Setup/Config screen is 16098<A HREF="h_config_add_ldap">"<!--#echo var="FEAT_ldap-result-to-addrbook-add"-->"</A>. 16099<P> 16100<End of help on this topic> 16101</BODY> 16102</HTML> 16103======= h_config_ldap_opts_nosub ======= 16104<HTML> 16105<HEAD> 16106<TITLE>LDAP FEATURE: Disable-Ad-Hoc-Space-Substitution</TITLE> 16107</HEAD> 16108<BODY> 16109<H1>LDAP FEATURE: Disable-Ad-Hoc-Space-Substitution</H1> 16110 16111Spaces in your input are normally handled specially. 16112Each space character is replaced 16113by 16114<P> 16115<CENTER><SAMP>* <SPACE></SAMP></CENTER> 16116<P> 16117in the search query (but not by "* <SPACE> *"). 16118The reason this is done is so the input string 16119<P> 16120<CENTER><SAMP>Greg Donald</SAMP></CENTER> 16121<P> 16122(which is converted to "Greg* Donald") will match 16123the names "Greg Donald", 16124"Gregory Donald", "Greg F. Donald", and 16125"Gregory F Donald"; but it won't match "Greg McDonald". 16126If the "Search-Rule" you were using was "begins-with", 16127then it would also match the name "Greg Donaldson". 16128<P> 16129Turning on this feature will disable this substitution. 16130<P> 16131<End of help on this topic> 16132</BODY> 16133</HTML> 16134====== h_config_ldap_searchtypes ======= 16135<HTML> 16136<HEAD> 16137<TITLE>LDAP OPTION: Search-Type</TITLE> 16138</HEAD> 16139<BODY> 16140<H1>LDAP OPTION: Search-Type</H1> 16141 16142This affects the way that LDAP searches are done. 16143In particular, this tells the server where to look for the string to be matched. 16144If set to "name" then the string that is being searched for will 16145be compared with the string in the 16146"Name" field on the server 16147(technically, it is the "commonname" field on the server). 16148"Surname" means we're looking for a 16149match in the "Surname" field on the 16150server (actually the "sn" field). 16151"Givenname" really is "givenname" 16152and "email" is the electronic mail address (this is actually the field 16153called "mail" or "electronicmail" on the server). 16154The other three types are combinations of 16155the types listed so far. "Name-or-email" 16156means the string should appear 16157in either the "name" field OR the "email" field. 16158Likewise, "surname-or-givenname" 16159means "surname" OR "givenname" 16160and "sur-or-given-or-name-or-email" means the obvious thing. 16161<P> 16162This search TYPE is combined with the 16163search <A HREF="h_config_ldap_searchrules">RULE</A> 16164to form the actual search query. 16165<P> 16166The usual default value for this 16167option is "sur-or-given-or-name-or-email". 16168This type of search may be slow on some servers. 16169Try "name-or-email", which is often 16170faster, or just "name" if the performance seems to be a problem. 16171<P> 16172Some servers have been configured with different attribute names for 16173these four fields. 16174In other words, instead of using the attribute name "mail" 16175for the email address field, the server might be configured to use something 16176else, for example, "rfc822mail" or "internetemailaddress". 16177Alpine can be configured to use these different attribute names by using 16178the four configuration options: 16179<P><UL> 16180<LI><A HREF="h_config_ldap_email_attr">"EmailAttribute"</A> 16181</UL> 16182<P><UL> 16183<LI><A HREF="h_config_ldap_cn_attr">"NameAttribute"</A> 16184</UL> 16185<P><UL> 16186<LI><A HREF="h_config_ldap_sn_attr">"SurnameAttribute"</A> 16187</UL> 16188<P><UL> 16189<LI><A HREF="h_config_ldap_gn_attr">"GivennameAttribute"</A> 16190</UL> 16191<P> 16192<End of help on this topic> 16193</BODY> 16194</HTML> 16195====== h_config_ldap_searchrules ======= 16196<HTML> 16197<HEAD> 16198<TITLE>LDAP OPTION: Search-Rule</TITLE> 16199</HEAD> 16200<BODY> 16201<H1>LDAP OPTION: Search-Rule</H1> 16202 16203This affects the way that LDAP searches are done. 16204If set to "equals" then 16205only exact matches count. 16206"Contains" means that the string you type in 16207is a substring of what you are matching against. 16208"Begins-with" and "ends-with" 16209mean that the string starts or ends with the string you type in. 16210<P> 16211Spaces in your input are normally handled specially, but you can turn that 16212special handling off with the 16213<A HREF="h_config_ldap_opts_nosub">"Disable-Ad-Hoc-Space-Substitution"</A> 16214feature. 16215<P> 16216The usual default value for this option is "begins-with". 16217<P> 16218<End of help on this topic> 16219</BODY> 16220</HTML> 16221======= h_config_ldap_email_attr ======= 16222<HTML> 16223<HEAD> 16224<TITLE>LDAP OPTION: EmailAttribute</TITLE> 16225</HEAD> 16226<BODY> 16227<H1>LDAP OPTION: EmailAttribute</H1> 16228 16229This is the name of the attribute that is searched for when looking for 16230an email address. The default value for this option is "mail" or 16231"electronicmail". 16232If the server you are using uses a different attribute name for the email 16233address, put that attribute name here. 16234<P> 16235This will affect the search filter used if your Search-Type is one that 16236contains a search for "email". 16237It will also cause the attribute value matching this attribute name to be used 16238as the email address when you look up an entry from the composer. 16239<P> 16240<End of help on this topic> 16241</BODY> 16242</HTML> 16243======= h_config_ldap_sn_attr ======= 16244<HTML> 16245<HEAD> 16246<TITLE>LDAP OPTION: SurnameAttribute</TITLE> 16247</HEAD> 16248<BODY> 16249<H1>LDAP OPTION: SurnameAttribute</H1> 16250 16251This is the name of the attribute that is searched for when looking for 16252the surname of the entry. The default value for this option is "sn". 16253If the server you are using uses a different attribute name for the surname, 16254put that attribute name here. 16255This will affect the search filter used if your Search-Type is one that 16256contains a search for "surname". 16257<P> 16258<End of help on this topic> 16259</BODY> 16260</HTML> 16261======= h_config_ldap_gn_attr ======= 16262<HTML> 16263<HEAD> 16264<TITLE>LDAP OPTION: GivennameAttribute</TITLE> 16265</HEAD> 16266<BODY> 16267<H1>LDAP OPTION: GivennameAttribute</H1> 16268 16269This is the name of the attribute that is searched for when looking for 16270the given name of the entry. The default value for this option is "givenname". 16271If the server you are using uses a different attribute name for the given name, 16272put that attribute name here. 16273This will affect the search filter used if your Search-Type is one that 16274contains a search for "givenname". 16275<P> 16276<End of help on this topic> 16277</BODY> 16278</HTML> 16279======= h_config_ldap_cn_attr ======= 16280<HTML> 16281<HEAD> 16282<TITLE>LDAP OPTION: NameAttribute</TITLE> 16283</HEAD> 16284<BODY> 16285<H1>LDAP OPTION: NameAttribute</H1> 16286 16287This is the name of the attribute that is searched for when looking for 16288the name of the entry. The default value for this option is "cn", which 16289stands for common name. 16290If the server you are using uses a different attribute name for the name, 16291put that attribute name here. 16292This will affect the search filter used if your Search-Type is one that 16293contains a search for "name". 16294<P> 16295<End of help on this topic> 16296</BODY> 16297</HTML> 16298======= h_config_ldap_time ======= 16299<HTML> 16300<HEAD> 16301<TITLE>LDAP OPTION: Timelimit</TITLE> 16302</HEAD> 16303<BODY> 16304<H1>LDAP OPTION: Timelimit</H1> 16305 16306This places a limit on the number of seconds the LDAP search will continue. 16307The default is 30 seconds. A value of 0 means no limit. Note that some servers 16308may place limits of their own on searches. 16309<P> 16310<End of help on this topic> 16311</BODY> 16312</HTML> 16313======= h_config_ldap_size ======= 16314<HTML> 16315<HEAD> 16316<TITLE>LDAP OPTION: Sizelimit</TITLE> 16317</HEAD> 16318<BODY> 16319<H1>LDAP OPTION: Sizelimit</H1> 16320 16321This places a limit on the number of entries returned by the LDAP server. 16322A value of 0 means no limit. The default is 0. Note that some servers 16323may place limits of their own on searches. 16324<P> 16325<End of help on this topic> 16326</BODY> 16327</HTML> 16328======= h_config_ldap_cust ======= 16329<HTML> 16330<HEAD> 16331<TITLE>LDAP OPTION: Custom-Search-Filter</TITLE> 16332</HEAD> 16333<BODY> 16334<H1>LDAP OPTION: Custom-Search-Filter</H1> 16335 16336This one is for advanced users only! If you define this, then the 16337"Search-Type" and "Search-Rule" defined are both ignored. 16338However, the feature 16339<A HREF="h_config_ldap_opts_nosub">"Disable-Ad-Hoc-Space-Substitution"</A> 16340is still in effect. 16341That is, the space substitution will take place even in a custom filter unless 16342you disable it. 16343<P> 16344If your LDAP service stops working and you suspect it might be because 16345of your custom filter, just delete this filter and try using the 16346"Search-Type" and "Search-Rule" instead. 16347Another option that sometimes causes trouble is the 16348<A HREF="h_config_ldap_base">"Search-Base"</A> option. 16349<P> 16350This variable may be set to the string representation of an LDAP search 16351filter (see RFC1960). In the places where you want the address string to be 16352substituted in, put a '%s' in this filter string. Here are some examples: 16353<P> 16354A "Search-Type" of "name" with "Search-Rule" of "begins-with" 16355is equivalent to the "Custom-Search-Filter" 16356<PRE> 16357 (cn=%s*) 16358</PRE> 16359When you try to match against the string "string" the program replaces 16360the "%s" with "string" (without the quotes). You may have multiple "%s"'s and 16361they will all be replaced with the string. There is a limit of 10 "%s"'s. 16362<P> 16363A "Search-Type" of "name-or-email" with "Search-Rule" 16364of "contains" is equivalent to 16365<PRE> 16366 (|(cn=*%s*)(mail=*%s*)) 16367</PRE> 16368<P> 16369If your server uses a different attribute <EM>name</EM> than 16370Alpine uses by default, 16371(for example, it uses "rfc822mail" instead of "mail"), 16372then you may be able to use one or more of the four attribute configuration 16373options instead of defining a custom filter: 16374<P><UL> 16375<LI><A HREF="h_config_ldap_email_attr">"EmailAttribute"</A> 16376</UL> 16377<P><UL> 16378<LI><A HREF="h_config_ldap_cn_attr">"NameAttribute"</A> 16379</UL> 16380<P><UL> 16381<LI><A HREF="h_config_ldap_sn_attr">"SurnameAttribute"</A> 16382</UL> 16383<P><UL> 16384<LI><A HREF="h_config_ldap_gn_attr">"GivennameAttribute"</A> 16385</UL> 16386<P> 16387<End of help on this topic> 16388</BODY> 16389</HTML> 16390======= h_composer_abook_comment ======= 16391<HTML> 16392<HEAD> 16393<TITLE>Addressbook Comment Explained</TITLE> 16394</HEAD> 16395<BODY> 16396This is a comment to help you remember what this entry is. The WhereIs 16397command searches comments so that it is easier to find an entry with a comment 16398you know about attached to it. This field is not used in the outgoing message. 16399<P> 16400Look <A HREF="h_edit_nav_cmds">here</A> 16401to see the available Editing and Navigation commands. 16402<P> 16403<End of help on this topic> 16404</BODY> 16405</HTML> 16406======= h_composer_abook_addrs ======= 16407<HTML> 16408<HEAD> 16409<TITLE>Addressbook Lists</TITLE> 16410</HEAD> 16411<BODY> 16412<H1>Addressbook Lists</H1> 16413 16414This is a list of addresses to send to when sending to this address book 16415entry. Each member of the list may be an address or another nickname from 16416any of your address books. If it is an address, it is OK to include the 16417full name field as well as the electronic address portion of that address. 16418For example, the following are all legitimate entries in this field: 16419 16420<DL><DT> </DT> 16421<DD>john (a nickname in your address book) 16422<DD>jdoe@some.domain 16423<DD>John Doe <jdoe@some.domain> 16424</DL> 16425 16426The addresses should be listed separated by commas, just like you would 16427enter them from the composer. 16428 16429<P> 16430 16431The only difference between a distribution list and a simple entry with a 16432single address, is that a distribution list has more than one address 16433listed in the Addresses: field, whereas a simple personal entry has just 16434one address. 16435 16436<P> 16437 16438For individual address book entries, if there is a full name in the 16439Fullname: field (filling in the Fullname: field is not required), it is 16440used. If the full name is specified in the Address: field and not in the 16441Fullname: field, then the full name from the Address: field is used. 16442 16443<P> 16444 16445If you type the nickname of a distribution list from one of your address 16446books in the Lcc: field, then the full name of that list is used in the 16447To: field. If you put a list in the To: or Cc: fields, that list will be 16448expanded into all of its addresses. If the list has a full name, then 16449that will appear at the beginning of the addresses. 16450 16451<DL><DT> </DT> 16452<DD>Sewing Club <john@somewhere>, nancy@something.else, Sal 16453<sal@here.there> 16454</DL> 16455 16456If the first address in the distribution list also has a full name, then 16457the list full name and that full name are combined into something like the 16458following: 16459 16460<DL><DT> </DT> 16461<DD>Sewing Club -- John Smith <john@somewhere> 16462</DL> 16463 16464 16465If you specify a list via Lcc, the full name is used in the To: line. If 16466you specify a list in the To: or Cc: fields, then it uses the same method 16467as for individual entries for filling in the full name. 16468 16469<P> 16470 16471For help with editing and navigation commands, check the Help for the 16472Nickname: field. 16473 16474<P> 16475<End of help on this topic> 16476</BODY> 16477</HTML> 16478======= h_config_xoauth2_client_id ======= 16479<HTML> 16480<HEAD> 16481<TITLE>Client-Id Explained</TITLE> 16482</HEAD> 16483<BODY> 16484<H1>Client-Id Explained</H1> 16485 16486If you have registered Alpine with your service provider to use the XOAUTH2 authenticator, or 16487someone has shared a client-id and client-secret with you, use this field to input the 16488client-id. 16489<P> 16490The Client-Id field is a string that your provider generates for the program 16491being registered. However, some providers allow different users to register 16492the same program. Users of the Mutt email program already do this to use 16493XOAUTH2 authentication in Gmail. 16494 16495<P> 16496<End of help on this topic> 16497</BODY> 16498</HTML> 16499======= h_config_xoauth2_client_secret ======= 16500<HTML> 16501<HEAD> 16502<TITLE>Client-Secret Explained</TITLE> 16503</HEAD> 16504<BODY> 16505<H1>Client-Secret Explained</H1> 16506 16507If you have registered Alpine with your service provider to use the XOAUTH2 authenticator, or 16508someone has shared a client-id and client-secret with you, use this field to input the 16509client-secret. Some servers require both a client-id and a client-secret, some other servers do 16510not require a client-secret. If a client-secret is required, use this field to add one. 16511 16512<P> The client-secret field is supposed to be kept secret, that is, not 16513shared with any of the users, but due to the open source nature of Alpine, 16514it is not possible to keep it secret in any meaningful way. The intention 16515of this field is so that only the coders of an app can use the codes given 16516to them and authenticate their users to the services they are requesting. 16517This means that other coders would not be able to impresonate that app, 16518and use it to steal data from those users. In the case of Alpine this is 16519not possible, as Alpine does not steal data from its users, so users are safe 16520sharing client-secrets. Just make sure you obtain your copy of Alpine from 16521a reputable provider or compile the source code by yourself. The official 16522source code of this project is located at 16523 16524<P><CENTER><A HREF="http://repo.or.cz/alpine.git">http://repo.or.cz/alpine.git</A>.</CENTER> 16525 16526<P> 16527<End of help on this topic> 16528</BODY> 16529</HTML> 16530======= h_config_xoauth2_tenant ======= 16531<HTML> 16532<HEAD> 16533<TITLE>Tenant Explained</TITLE> 16534</HEAD> 16535<BODY> 16536<H1>Tenant Explained</H1> 16537 16538The tenant is a way in which a service can either restrict an app to access 16539only certain portions of its service. For example, a service may allow 16540an app to have access to your work data, or school data, and not every app 16541is allowed to access this data, or the access is not allowed for all accounts, 16542but only those restructed in the tenant. 16543 16544<P> When Alpine registers with an email service provider, it does so with the 16545intention that you can use Alpine for any of your needs (work, school or 16546personal), and the client-id and tenant that it uses would allow you access to 16547only your work email, say, and not your personal email, because the app is 16548trusted only at work, and so the client-id and tenant are good for that 16549organization only. 16550<P> 16551<End of help on this topic> 16552</BODY> 16553</HTML> 16554======= h_config_xoauth2_flow ======= 16555<HTML> 16556<HEAD> 16557<TITLE>Flow Explained</TITLE> 16558</HEAD> 16559<BODY> 16560<H1>Flow Explained</H1> 16561 16562The first time you connect to a service to authorize Alpine access to your 16563email, you will have to do a certain number of steps, which typically involve 16564to login to your account using a browser, and agreeing to give Alpine certain 16565rights to access your account. 16566 16567<P> 16568How this process is going to be done depends on the service. Some services 16569allow you to give access to Alpine and later generate a code that you 16570input into Alpine, while others give you a code you have to use before you 16571approve access to Alpine to access your email. 16572 16573<P> An example of a service that gives you a code after you authorize 16574Alpine is Gmail, and this process is called internally as "Authorize". 16575An example of a service that gives you a code before you authorize Alpine 16576is Outlook, and this process is called "Device". However, some services, 16577like Outlook, offer both services, and you can choose which flow you would like 16578to use. You 16579can choose between the "Authorize&qupt; and "Device" in these servers. 16580If you forget to configure 16581this, Alpine will ask you in these situations which method to use before it starts 16582to setup the process to get your authrization. 16583 16584<P> 16585<End of help on this topic> 16586</BODY> 16587</HTML> 16588======= h_config_xoauth2_username ======= 16589<HTML> 16590<HEAD> 16591<TITLE>Username Explained</TITLE> 16592</HEAD> 16593<BODY> 16594<H1>Username Explained</H1> 16595 16596This variable is a list of usernames for which the configuration for the 16597given service is valid. You may have more than one username for which this 16598configuration is correct. 16599 16600<P> 16601Alpine will use the usernames in this list to associate your username with 16602the correct configuration in Alpine. If Alpine cannot determine which configuration 16603to use, Alpine will offer you a list of client-ids that you have configured 16604for that service and ask you to pick one. Your answer will be saved in your 16605.pinerc file. 16606 16607<P> 16608<End of help on this topic> 16609</BODY> 16610</HTML> 16611======= h_config_role_nick ======= 16612<HTML> 16613<HEAD> 16614<TITLE>Nickname Explained</TITLE> 16615</HEAD> 16616<BODY> 16617<H1>Nickname Explained</H1> 16618 16619This is a nickname to help you. 16620You should have a different nickname for each role you define. 16621The nickname will be used in the SETUP ROLE RULES screen to allow you to 16622pick a role to edit. 16623It will also be used when you send a message to let you know you are 16624sending with a different role than you use by default, and 16625it will be useful for choosing a role when composing with the Role command 16626or when composing with one of the Role Uses set to With Confirmation. 16627This field is not used in the outgoing message. 16628<P> 16629Look <A HREF="h_edit_nav_cmds">here</A> 16630to see the available Editing and Navigation commands. 16631<P> 16632<End of help on this topic> 16633</BODY> 16634</HTML> 16635======= h_config_role_comment ======= 16636<HTML> 16637<HEAD> 16638<TITLE>Comment Explained</TITLE> 16639</HEAD> 16640<BODY> 16641<H1>Comment Explained</H1> 16642 16643This is a comment to help you. 16644This comment does not play any functional role, it is simply an optional 16645comment to help you remember what the rule is for. 16646<P> 16647Look <A HREF="h_edit_nav_cmds">here</A> 16648to see the available Editing and Navigation commands. 16649<P> 16650<End of help on this topic> 16651</BODY> 16652</HTML> 16653======= h_config_other_nick ======= 16654<HTML> 16655<HEAD> 16656<TITLE>Nickname Explained</TITLE> 16657</HEAD> 16658<BODY> 16659<H1>Nickname Explained</H1> 16660 16661This is a nickname to help you. 16662You should have a different nickname for each rule you define. 16663The nickname will be used in the SETUP OTHER RULES screen to allow you to 16664pick a rule to edit. 16665<P> 16666Look <A HREF="h_edit_nav_cmds">here</A> 16667to see the available Editing and Navigation commands. 16668<P> 16669<End of help on this topic> 16670</BODY> 16671</HTML> 16672======= h_config_score_nick ======= 16673<HTML> 16674<HEAD> 16675<TITLE>Nickname Explained</TITLE> 16676</HEAD> 16677<BODY> 16678<H1>Nickname Explained</H1> 16679 16680This is a nickname to help you. 16681You should have a different nickname for each scoring rule you define. 16682The nickname will be used in the SETUP SCORING RULES screen to allow you to 16683pick a rule to edit. 16684<P> 16685Look <A HREF="h_edit_nav_cmds">here</A> 16686to see the available Editing and Navigation commands. 16687<P> 16688<End of help on this topic> 16689</BODY> 16690</HTML> 16691======= h_config_incol_nick ======= 16692<HTML> 16693<HEAD> 16694<TITLE>Nickname Explained</TITLE> 16695</HEAD> 16696<BODY> 16697<H1>Nickname Explained</H1> 16698 16699This is a nickname to help you. 16700You should have a different nickname for each color rule you define. 16701The nickname will be used in the SETUP INDEX COLOR RULES screen to allow you to 16702pick a rule to edit. 16703<P> 16704Look <A HREF="h_edit_nav_cmds">here</A> 16705to see the available Editing and Navigation commands. 16706<P> 16707<End of help on this topic> 16708</BODY> 16709</HTML> 16710======= h_config_filt_nick ======= 16711<HTML> 16712<HEAD> 16713<TITLE>Nickname Explained</TITLE> 16714</HEAD> 16715<BODY> 16716<H1>Nickname Explained</H1> 16717 16718This is a nickname to help you. 16719You should have a different nickname for each filtering rule you define. 16720The nickname will be used in the SETUP FILTERING RULES screen to allow you to 16721pick a rule to edit. 16722<P> 16723Look <A HREF="h_edit_nav_cmds">here</A> 16724to see the available Editing and Navigation commands. 16725<P> 16726<End of help on this topic> 16727</BODY> 16728</HTML> 16729======= h_config_score_topat ======= 16730<HTML> 16731<HEAD> 16732<TITLE>"To:" Pattern Explained</TITLE> 16733</HEAD> 16734<BODY> 16735<H1>"To:" Pattern Explained</H1> 16736 16737Any text you enter as the "To pattern" 16738will be compared to the recipients from the To: line of 16739the message being scored. 16740When the text you entered matches 16741all or part of the To: line of a message, then the Score Value 16742you have specified will be added to the score for the message. 16743(Any other non-blank parts of the Pattern must match, too.) 16744<P> 16745 16746You may enter a complete email address, part of an address, or a 16747list of addresses or partial addresses. 16748For example: 16749<P> 16750 16751<PRE> 16752 To pattern = friend@public.com 16753 16754 To pattern = rated.net 16755 16756 To pattern = xxx@adults.com 16757 admin@msn.com 16758 fool@motleyfool.com 16759</PRE> 16760 16761<P> 16762Each of those are valid To patterns. 16763<P> 16764 16765Messages match those patterns if any of the 16766addresses in the To: line of the message contains the pattern. 16767If the pattern is a list of patterns 16768(like the last example above) then it is a match if any of the patterns in 16769the list match any of the addresses in the To: line. 16770(It is not possible to specify two addresses that must <EM>BOTH</EM> be 16771present for a match. 16772It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM> 16773address2 must be present. 16774That is exactly what using a list does.) 16775<P> 16776 16777Some messages may be "bounced" to you, and will 16778have a "Resent-To:" header line. 16779If the message contains a Resent-To: line 16780and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on, 16781Alpine will look for 16782matches to your "To patterns" there, and <EM>NOT</EM> in 16783the original To: line. 16784<P> 16785 16786When entering a pattern, you may choose an address from your address book 16787with the "T" command. 16788<P> 16789 16790It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the 16791"!" "toggle NOT" command. 16792This changes the meaning of the To pattern so that it has the opposite meaning. 16793It will be considered a match if there are no matches between the 16794addresses in the To: line and the list of To patterns. 16795<P> 16796Don't make the mistake of putting the "!" in the data field for 16797the pattern. 16798For example, if you type the characters "!frizzle" into the To 16799pattern, the pattern will look like: 16800<P> 16801<PRE> 16802 To pattern = !frizzle 16803</PRE> 16804<P> 16805This means you want to match the 8 character sequence "!frizzle". 16806In order to match messages that do not have "frizzle" in 16807their To field, first type the characters "frizzle" followed 16808by carriage return for the value of the To pattern, then negate it 16809by typing the "!" command. 16810It should end up looking like 16811<P> 16812<PRE> 16813 ! To pattern = frizzle 16814</PRE> 16815<P> 16816You are not limited to using the six standard header patterns that are 16817normally shown (To, From, Sender, Cc, News, and Subject). 16818You may add any other header to a Pattern by 16819using the "eXtraHdr" command to specify a different 16820message header line; and then the Add or Change command to fill in 16821a pattern for the new header line, just like you would for a standard header. 16822<P> 16823A technicality: Since comma is the character used to separate multiple 16824values in a pattern field, you have to escape comma with a backslash (\) if 16825you want to include a literal comma in the field. 16826In other words, if you type a backslash followed by a comma it will 16827be interpreted as a comma by Alpine, instead of as a separator between 16828pattern values. 16829All other backslashes are literal backslashes and should not be escaped. 16830<P> 16831Look "<A HREF="h_rule_patterns">here</A>" 16832for more information on Patterns. 16833<P> 16834Look <A HREF="h_edit_nav_cmds">here</A> 16835to see the available Editing and Navigation commands. 16836<P> 16837<End of help on this topic> 16838</BODY> 16839</HTML> 16840======= h_config_incol_topat ======= 16841<HTML> 16842<HEAD> 16843<TITLE>"To:" Pattern Explained</TITLE> 16844</HEAD> 16845<BODY> 16846<H1>"To:" Pattern Explained</H1> 16847 16848Any text you enter as the "To pattern" 16849will be compared to the recipients from the To: lines of 16850the messages in the index. 16851When the text you entered matches 16852all or part of the To: line of a message, then the Index Line Color you have 16853specified will be used for that line in the index. 16854(Any other non-blank parts of the Pattern must match, too.) 16855<P> 16856 16857You may enter a complete email address, part of an address, or a 16858list of addresses or partial addresses. 16859For example: 16860<P> 16861 16862<PRE> 16863 To pattern = friend@public.com 16864 To pattern = rated.net 16865 To pattern = xxx@adults.com 16866 admin@msn.com 16867 fool@motleyfool.com 16868</PRE> 16869 16870<P> 16871Each of those are valid To patterns. 16872<P> 16873 16874Messages match those patterns if any of the 16875addresses in the To: line of the message contains the pattern. 16876If the pattern is a list of patterns 16877(like the last example above) then it is a match if any of the patterns in 16878the list match any of the addresses in the To: line. 16879(It is not possible to specify two addresses that must <EM>BOTH</EM> be 16880present for a match. 16881It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM> 16882address2 must be present. 16883That is exactly what using a list does.) 16884<P> 16885 16886Some messages may be "bounced" to you, and will 16887have a "Resent-To:" header line. 16888If the message contains a Resent-To: line 16889and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on, 16890Alpine will look for 16891matches to your "To patterns" there, and <EM>NOT</EM> in 16892the original To: line. 16893<P> 16894 16895When entering a pattern, you may choose an address from your address book 16896with the "T" command. 16897<P> 16898 16899It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the 16900"!" "toggle NOT" command. 16901This changes the meaning of the To pattern so that it has the opposite meaning. 16902It will be considered a match if there are no matches between the 16903addresses in the To: line and the list of To patterns. 16904<P> 16905Don't make the mistake of putting the "!" in the data field for 16906the pattern. 16907For example, if you type the characters "!frizzle" into the To 16908pattern, the pattern will look like: 16909<P> 16910<PRE> 16911 To pattern = !frizzle 16912</PRE> 16913<P> 16914This means you want to match the 8 character sequence "!frizzle". 16915In order to match messages that do not have "frizzle" in 16916their To field, first type the characters "frizzle" followed 16917by carriage return for the value of the To pattern, then negate it 16918by typing the "!" command. 16919It should end up looking like 16920<P> 16921<PRE> 16922 ! To pattern = frizzle 16923</PRE> 16924<P> 16925 16926You are not limited to using the six standard header patterns that are 16927normally shown (To, From, Sender, Cc, News, and Subject). 16928You may add any other header to a Pattern by 16929using the "eXtraHdr" command to specify a different 16930message header line; and then the Add or Change command to fill in 16931a pattern for the new header line, just like you would for a standard header. 16932<P> 16933A technicality: Since comma is the character used to separate multiple 16934values in a pattern field, you have to escape comma with a backslash (\) if 16935you want to include a literal comma in the field. 16936In other words, if you type a backslash followed by a comma it will 16937be interpreted as a comma by Alpine, instead of as a separator between 16938pattern values. 16939All other backslashes are literal backslashes and should not be escaped. 16940<P> 16941Look "<A HREF="h_rule_patterns">here</A>" 16942for more information on Patterns. 16943<P> 16944Look <A HREF="h_edit_nav_cmds">here</A> 16945to see the available Editing and Navigation commands. 16946<P> 16947<End of help on this topic> 16948</BODY> 16949</HTML> 16950======= h_config_other_topat ======= 16951<HTML> 16952<HEAD> 16953<TITLE>"To:" Pattern Explained</TITLE> 16954</HEAD> 16955<BODY> 16956<H1>"To:" Pattern Explained</H1> 16957 16958For some of the OTHER RULES actions, there is no message that is being 16959compared against. 16960If that is the case, then only the Current Folder Type is checked. 16961In particular, this To pattern is ignored. 16962Actions that fall into this category include both 16963Sort Order and Index Format. 16964<P> 16965A technicality: Since comma is the character used to separate multiple 16966values in a pattern field, you have to escape comma with a backslash (\) if 16967you want to include a literal comma in the field. 16968In other words, if you type a backslash followed by a comma it will 16969be interpreted as a comma by Alpine, instead of as a separator between 16970pattern values. 16971All other backslashes are literal backslashes and should not be escaped. 16972<P> 16973Look "<A HREF="h_rule_patterns">here</A>" 16974for more information on Patterns. 16975<P> 16976Look <A HREF="h_edit_nav_cmds">here</A> 16977to see the available Editing and Navigation commands. 16978<P> 16979<End of help on this topic> 16980</BODY> 16981</HTML> 16982======= h_config_filt_topat ======= 16983<HTML> 16984<HEAD> 16985<TITLE>"To:" Pattern Explained</TITLE> 16986</HEAD> 16987<BODY> 16988<H1>"To:" Pattern Explained</H1> 16989 16990Any text you enter as the "To pattern" 16991will be compared to the recipients from the To: line of 16992messages when Alpine opens folders. 16993When the text you entered matches 16994all or part of the To: line of a message, then the Filter Action you have 16995specified will be carried out. 16996(Any other non-blank parts of the Pattern must match, too.) 16997<P> 16998 16999You may enter a complete email address, part of an address, or a 17000list of addresses or partial addresses. 17001For example: 17002<P> 17003 17004<PRE> 17005 To pattern = friend@public.com 17006 To pattern = rated.net 17007 To pattern = xxx@adults.com 17008 admin@msn.com 17009 fool@motleyfool.com 17010</PRE> 17011 17012<P> 17013Each of those are valid To patterns. 17014<P> 17015 17016Messages match those patterns if any of the 17017addresses in the To: line of the message contains the pattern. 17018If the pattern is a list of patterns 17019(like the last example above) then it is a match if any of the patterns in 17020the list match any of the addresses in the To: line. 17021(It is not possible to specify two addresses that must <EM>BOTH</EM> be 17022present for a match. 17023It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM> 17024address2 must be present. 17025That is exactly what using a list does.) 17026<P> 17027 17028Some messages may be "bounced" to you, and will 17029have a "Resent-To:" header line. 17030If the message contains a Resent-To: line 17031and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on, 17032Alpine will look for 17033matches to your "To patterns" there, and <EM>NOT</EM> in 17034the original To: line. 17035<P> 17036 17037When entering a pattern, you may choose an address from your address book 17038with the "T" command. 17039<P> 17040 17041It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the 17042"!" "toggle NOT" command. 17043This changes the meaning of the To pattern so that it has the opposite meaning. 17044It will be considered a match if there are no matches between the 17045addresses in the To: line and the list of To patterns. 17046<P> 17047Don't make the mistake of putting the "!" in the data field for 17048the pattern. 17049For example, if you type the characters "!frizzle" into the To 17050pattern, the pattern will look like: 17051<P> 17052<PRE> 17053 To pattern = !frizzle 17054</PRE> 17055<P> 17056This means you want to match the 8 character sequence "!frizzle". 17057In order to match messages that do not have "frizzle" in 17058their To field, first type the characters "frizzle" followed 17059by carriage return for the value of the To pattern, then negate it 17060by typing the "!" command. 17061It should end up looking like 17062<P> 17063<PRE> 17064 ! To pattern = frizzle 17065</PRE> 17066<P> 17067 17068You are not limited to using the six standard header patterns that are 17069normally shown (To, From, Sender, Cc, News, and Subject). 17070You may add any other header to a Pattern by 17071using the "eXtraHdr" command to specify a different 17072message header line; and then the Add or Change command to fill in 17073a pattern for the new header line, just like you would for a standard header. 17074<P> 17075A technicality: Since comma is the character used to separate multiple 17076values in a pattern field, you have to escape comma with a backslash (\) if 17077you want to include a literal comma in the field. 17078In other words, if you type a backslash followed by a comma it will 17079be interpreted as a comma by Alpine, instead of as a separator between 17080pattern values. 17081All other backslashes are literal backslashes and should not be escaped. 17082<P> 17083Look "<A HREF="h_rule_patterns">here</A>" 17084for more information on Patterns. 17085<P> 17086Look <A HREF="h_edit_nav_cmds">here</A> 17087to see the available Editing and Navigation commands. 17088<P> 17089<End of help on this topic> 17090</BODY> 17091</HTML> 17092======= h_config_role_topat ======= 17093<HTML> 17094<HEAD> 17095<TITLE>"To:" Pattern Explained</TITLE> 17096</HEAD> 17097<BODY> 17098<H1>"To:" Pattern Explained</H1> 17099 17100Any text you enter as the "To pattern" 17101will be compared to the recipients from the To: line of 17102the message being replied to or forwarded. 17103(Any other non-blank parts of the Pattern must match, too.) 17104In the case of the Compose command, this pattern and the other header 17105patterns are ignored. 17106<P> 17107 17108You may enter a complete email address, part of an address, or a 17109list of addresses or partial addresses. 17110For example: 17111<P> 17112 17113<PRE> 17114 To pattern = friend@public.com 17115 To pattern = rated.net 17116 To pattern = xxx@adults.com 17117 admin@msn.com 17118 fool@motleyfool.com 17119</PRE> 17120 17121<P> 17122Each of those are valid To patterns. 17123<P> 17124 17125Messages match those patterns if any of the 17126addresses in the To: line of the message contains the pattern. 17127If the pattern is a list of patterns 17128(like the last example above) then it is a match if any of the patterns in 17129the list match any of the addresses in the To: line. 17130(It is not possible to specify two addresses that must <EM>BOTH</EM> be 17131present for a match. 17132It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM> 17133address2 must be present. 17134That is exactly what using a list does.) 17135<P> 17136 17137Some messages may be "bounced" to you, and will 17138have a "Resent-To:" header line. 17139If the message contains a Resent-To: line 17140and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on, 17141Alpine will look for 17142matches to your "To patterns" there, and <EM>NOT</EM> in 17143the original To: line. 17144<P> 17145 17146When entering a pattern, you may choose an address from your address book 17147with the "T" command. 17148<P> 17149 17150It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the 17151"!" "toggle NOT" command. 17152This changes the meaning of the To pattern so that it has the opposite meaning. 17153It will be considered a match if there are no matches between the 17154addresses in the To: line and the list of To patterns. 17155<P> 17156Don't make the mistake of putting the "!" in the data field for 17157the pattern. 17158For example, if you type the characters "!frizzle" into the To 17159pattern, the pattern will look like: 17160<P> 17161<PRE> 17162 To pattern = !frizzle 17163</PRE> 17164<P> 17165This means you want to match the 8 character sequence "!frizzle". 17166In order to match messages that do not have "frizzle" in 17167their To field, first type the characters "frizzle" followed 17168by carriage return for the value of the To pattern, then negate it 17169by typing the "!" command. 17170It should end up looking like 17171<P> 17172<PRE> 17173 ! To pattern = frizzle 17174</PRE> 17175<P> 17176 17177You are not limited to using the six standard header patterns that are 17178normally shown (To, From, Sender, Cc, News, and Subject). 17179You may add any other header to a Pattern by 17180using the "eXtraHdr" command to specify a different 17181message header line; and then the Add or Change command to fill in 17182a pattern for the new header line, just like you would for a standard header. 17183<P> 17184A technicality: Since comma is the character used to separate multiple 17185values in a pattern field, you have to escape comma with a backslash (\) if 17186you want to include a literal comma in the field. 17187In other words, if you type a backslash followed by a comma it will 17188be interpreted as a comma by Alpine, instead of as a separator between 17189pattern values. 17190All other backslashes are literal backslashes and should not be escaped. 17191<P> 17192Look "<A HREF="h_rule_patterns">here</A>" 17193for more information on Patterns. 17194<P> 17195Look <A HREF="h_edit_nav_cmds">here</A> 17196to see the available Editing and Navigation commands. 17197<P> 17198<End of help on this topic> 17199</BODY> 17200</HTML> 17201======= h_config_role_frompat ======= 17202<HTML> 17203<HEAD> 17204<TITLE>"From:" Pattern Explained</TITLE> 17205</HEAD> 17206<BODY> 17207<H1>"From:" Pattern Explained</H1> 17208 17209This is just like the "To pattern" except that it is compared with 17210the address in the From: line of the message 17211instead of the addresses from the To: line. 17212See the help for the To pattern for more information on header patterns. 17213<P> 17214Look "<A HREF="h_rule_patterns">here</A>" 17215for more information on Patterns. 17216<P> 17217Look <A HREF="h_edit_nav_cmds">here</A> 17218to see the available Editing and Navigation commands. 17219<P> 17220<End of help on this topic> 17221</BODY> 17222</HTML> 17223======= h_config_role_senderpat ======= 17224<HTML> 17225<HEAD> 17226<TITLE>"Sender:" Pattern Explained</TITLE> 17227</HEAD> 17228<BODY> 17229<H1>"Sender:" Pattern Explained</H1> 17230 17231This is just like the "To pattern" except that it is compared with 17232the address from the Sender: line of the message 17233instead of the addresses from the To: line. 17234See the help for the To pattern for more information on header patterns. 17235<P> 17236Look "<A HREF="h_rule_patterns">here</A>" 17237for more information on Patterns. 17238<P> 17239Look <A HREF="h_edit_nav_cmds">here</A> 17240to see the available Editing and Navigation commands. 17241<P> 17242<End of help on this topic> 17243</BODY> 17244</HTML> 17245======= h_config_role_ccpat ======= 17246<HTML> 17247<HEAD> 17248<TITLE>"Cc:" Pattern Explained</TITLE> 17249</HEAD> 17250<BODY> 17251<H1>"Cc:" Pattern Explained</H1> 17252 17253This is just like the "To pattern" except that it is compared with 17254the addresses from the Cc: line of the message 17255instead of the addresses from the To: line. 17256See the help for the To pattern for more information on header patterns. 17257<P> 17258Look "<A HREF="h_rule_patterns">here</A>" 17259for more information on Patterns. 17260<P> 17261Look <A HREF="h_edit_nav_cmds">here</A> 17262to see the available Editing and Navigation commands. 17263<P> 17264<End of help on this topic> 17265</BODY> 17266</HTML> 17267======= h_config_role_recippat ======= 17268<HTML> 17269<HEAD> 17270<TITLE>Recipient Pattern Explained</TITLE> 17271</HEAD> 17272<BODY> 17273<H1>Recipient Pattern Explained</H1> 17274 17275This is just like the "To pattern" except that it is compared with 17276the addresses from both the To: line and the Cc: line of the 17277message instead of just the addresses from the To: line. 17278In other words, it is considered a match if the pattern matches 17279<EM>EITHER</EM> an address in the To: line <EM>OR</EM> an address 17280in the Cc: line. 17281(Notice that defining the Recipient pattern does not have the same 17282effect as defining both the To and Cc patterns. 17283Recipient is To <EM>OR</EM> Cc; not To <EM>AND</EM> Cc. 17284It is equivalent to having two different rules; 17285one with a To pattern and the other with the same Cc pattern.) 17286<P> 17287A technicality: Since comma is the character used to separate multiple 17288values in a pattern field, you have to escape comma with a backslash (\) if 17289you want to include a literal comma in the field. 17290In other words, if you type a backslash followed by a comma it will 17291be interpreted as a comma by Alpine, instead of as a separator between 17292pattern values. 17293All other backslashes are literal backslashes and should not be escaped. 17294<P> 17295Look "<A HREF="h_rule_patterns">here</A>" 17296for more information on Patterns. 17297<P> 17298Look <A HREF="h_edit_nav_cmds">here</A> 17299to see the available Editing and Navigation commands. 17300<P> 17301<End of help on this topic> 17302</BODY> 17303</HTML> 17304======= h_config_role_particpat ======= 17305<HTML> 17306<HEAD> 17307<TITLE>Participant Pattern Explained</TITLE> 17308</HEAD> 17309<BODY> 17310<H1>Participant Pattern Explained</H1> 17311 17312This is just like the "To pattern" except that it is compared with 17313the addresses from the From: line, the To: line, and the Cc: line of the 17314message instead of just the addresses from the To: line. 17315In other words, it is considered a match if the pattern matches 17316<EM>EITHER</EM> an address in the From: line, <EM>OR</EM> an address 17317in the To: line, <EM>OR</EM> an address in the Cc: line. 17318(Notice that defining the Participant pattern does not have the same 17319effect as defining all of the From, To, and Cc patterns. 17320Participant is From <EM>OR</EM> To <EM>OR</EM> Cc; not 17321From <EM>AND</EM> To <EM>AND</EM> Cc. 17322It is equivalent to having three different rules; 17323one with a From pattern, another with the same To pattern, and a third with 17324the same Cc pattern.) 17325<P> 17326A technicality: Since comma is the character used to separate multiple 17327values in a pattern field, you have to escape comma with a backslash (\) if 17328you want to include a literal comma in the field. 17329In other words, if you type a backslash followed by a comma it will 17330be interpreted as a comma by Alpine, instead of as a separator between 17331pattern values. 17332All other backslashes are literal backslashes and should not be escaped. 17333<P> 17334Look "<A HREF="h_rule_patterns">here</A>" 17335for more information on Patterns. 17336<P> 17337Look <A HREF="h_edit_nav_cmds">here</A> 17338to see the available Editing and Navigation commands. 17339<P> 17340<End of help on this topic> 17341</BODY> 17342</HTML> 17343======= h_config_role_newspat ======= 17344<HTML> 17345<HEAD> 17346<TITLE>News Pattern Explained</TITLE> 17347</HEAD> 17348<BODY> 17349<H1>News Pattern Explained</H1> 17350 17351If this pattern is non-blank, then for this rule to be considered a 17352match, at least one of the newsgroups from 17353the Newsgroups line of the message must match this pattern. 17354If this pattern is a list of patterns, then at least one of the 17355newsgroups must match at least one of the patterns. 17356(Any other non-blank parts of the Pattern must match, too.) 17357<P> 17358It is possible to add a <EM>NOT</EM> to the News Pattern meaning with the 17359"!" "toggle NOT" command. 17360This changes the meaning of the News pattern so that it has the opposite meaning. 17361It will be considered a match if there are no matches between the 17362addresses in the Newsgroups: line and the list of News patterns. 17363<P> 17364Don't make the mistake of putting the "!" in the data field for 17365the pattern. 17366For example, if you type the characters "!frizzle" into the News 17367pattern, the pattern will look like: 17368<P> 17369<PRE> 17370 News pattern = !frizzle 17371</PRE> 17372<P> 17373This means you want to match the 8 character sequence "!frizzle". 17374In order to match messages that do not have "frizzle" in 17375their Newsgroups header, first type the characters "frizzle" followed 17376by carriage return for the value of the News pattern, then negate it 17377by typing the "!" command. 17378It should end up looking like 17379<P> 17380<PRE> 17381 ! News pattern = frizzle 17382</PRE> 17383<P> 17384A technicality: Since comma is the character used to separate multiple 17385values in a pattern field, you have to escape comma with a backslash (\) if 17386you want to include a literal comma in the field. 17387In other words, if you type a backslash followed by a comma it will 17388be interpreted as a comma by Alpine, instead of as a separator between 17389pattern values. 17390All other backslashes are literal backslashes and should not be escaped. 17391<P> 17392 17393Look "<A HREF="h_rule_patterns">here</A>" 17394for more information on Patterns. 17395<P> 17396Look <A HREF="h_edit_nav_cmds">here</A> 17397to see the available Editing and Navigation commands. 17398<P> 17399<End of help on this topic> 17400</BODY> 17401</HTML> 17402======= h_config_role_subjpat ======= 17403<HTML> 17404<HEAD> 17405<TITLE>"Subject:" Pattern Explained</TITLE> 17406</HEAD> 17407<BODY> 17408<H1>"Subject:" Pattern Explained</H1> 17409 17410This is similar to the other parts of the Pattern. 17411It is compared with 17412the contents from the Subject of the message. 17413<P> 17414Look "<A HREF="h_rule_patterns">here</A>" 17415for more information on Patterns. 17416<P> 17417It is possible to add a <EM>NOT</EM> to the Subject Pattern meaning with the 17418"!" "toggle NOT" command. 17419This changes the meaning of the Subject pattern so that it has the opposite meaning. 17420It will be considered a match if there are no matches between the 17421text in the Subject: line and the list of Subject patterns. 17422<P> 17423 17424If you wish to have a header pattern that is not one of the six standard 17425header patterns, you may add it with the "eXtraHdr" command. 17426<P> 17427A technicality: Since comma is the character used to separate multiple 17428values in a pattern field, you have to escape comma with a backslash (\) if 17429you want to include a literal comma in the field. 17430In other words, if you type a backslash followed by a comma it will 17431be interpreted as a comma by Alpine, instead of as a separator between 17432pattern values. 17433All other backslashes are literal backslashes and should not be escaped. 17434<P> 17435Look <A HREF="h_edit_nav_cmds">here</A> 17436to see the available Editing and Navigation commands. 17437<P> 17438<End of help on this topic> 17439</BODY> 17440</HTML> 17441======= h_config_role_alltextpat ======= 17442<HTML> 17443<HEAD> 17444<TITLE>AllText Pattern Explained</TITLE> 17445</HEAD> 17446<BODY> 17447<H1>AllText Pattern Explained</H1> 17448 17449This is similar to the header patterns. 17450Instead of comparing with text in a particular header field it 17451is compared with all of the text in the message header and body. 17452<P> 17453It is possible to add a <EM>NOT</EM> to the AllText Pattern meaning with the 17454"!" "toggle NOT" command. 17455This changes the meaning of the AllText pattern so that it has the opposite meaning. 17456It will be considered a match if there are no matches between the 17457text of the message and the list of AllText patterns. 17458<P> 17459Don't make the mistake of putting the "!" in the data field for 17460the pattern. 17461For example, if you type the characters "!frizzle" into the AllText 17462pattern, the pattern will look like: 17463<P> 17464<PRE> 17465 AllText pattern = !frizzle 17466</PRE> 17467<P> 17468This means you want to match the 8 character sequence "!frizzle". 17469In order to match messages that do not have "frizzle" in 17470the text of the message, first type the characters "frizzle" followed 17471by carriage return for the value of the AllText pattern, then negate it 17472by typing the "!" command. 17473It should end up looking like 17474<P> 17475<PRE> 17476 ! AllText pattern = frizzle 17477</PRE> 17478<P> 17479It is possible that you may notice degraded performance when using 17480AllText Patterns. 17481<P> 17482A technicality: Since comma is the character used to separate multiple 17483values in a pattern field, you have to escape comma with a backslash (\) if 17484you want to include a literal comma in the field. 17485In other words, if you type a backslash followed by a comma it will 17486be interpreted as a comma by Alpine, instead of as a separator between 17487pattern values. 17488All other backslashes are literal backslashes and should not be escaped. 17489<P> 17490Look "<A HREF="h_rule_patterns">here</A>" 17491for more information on Patterns. 17492<P> 17493Look <A HREF="h_edit_nav_cmds">here</A> 17494to see the available Editing and Navigation commands. 17495<P> 17496<End of help on this topic> 17497</BODY> 17498</HTML> 17499======= h_config_role_bodytextpat ======= 17500<HTML> 17501<HEAD> 17502<TITLE>BodyText Pattern Explained</TITLE> 17503</HEAD> 17504<BODY> 17505<H1>BodyText Pattern Explained</H1> 17506 17507This is similar to the header patterns. 17508Instead of comparing with text in a particular header field it 17509is compared with all of the text in the message body. 17510<P> 17511It is possible to add a <EM>NOT</EM> to the BodyText Pattern meaning with the 17512"!" "toggle NOT" command. 17513This changes the meaning of the BodyText pattern so that it has the opposite meaning. 17514It will be considered a match if there are no matches between the 17515text of the body of the message and the list of BodyText patterns. 17516<P> 17517Don't make the mistake of putting the "!" in the data field for 17518the pattern. 17519For example, if you type the characters "!frizzle" into the BodyText 17520pattern, the pattern will look like: 17521<P> 17522<PRE> 17523 BdyText pattern = !frizzle 17524</PRE> 17525<P> 17526This means you want to match the 8 character sequence "!frizzle". 17527In order to match messages that do not have "frizzle" in 17528their BodyText, first type the characters "frizzle" followed 17529by carriage return for the value of the BodyText pattern, then negate it 17530by typing the "!" command. 17531It should end up looking like 17532<P> 17533<PRE> 17534 ! BodyText pattern = frizzle 17535</PRE> 17536<P> 17537It is possible that you may notice degraded performance when using 17538BodyText Patterns. 17539<P> 17540A technicality: Since comma is the character used to separate multiple 17541values in a pattern field, you have to escape comma with a backslash (\) if 17542you want to include a literal comma in the field. 17543In other words, if you type a backslash followed by a comma it will 17544be interpreted as a comma by Alpine, instead of as a separator between 17545pattern values. 17546All other backslashes are literal backslashes and should not be escaped. 17547<P> 17548Look "<A HREF="h_rule_patterns">here</A>" 17549for more information on Patterns. 17550<P> 17551Look <A HREF="h_edit_nav_cmds">here</A> 17552to see the available Editing and Navigation commands. 17553<P> 17554<End of help on this topic> 17555</BODY> 17556</HTML> 17557======= h_config_role_charsetpat ======= 17558<HTML> 17559<HEAD> 17560<TITLE>Character Set Pattern Explained</TITLE> 17561</HEAD> 17562<BODY> 17563<H1>Character Set Pattern Explained</H1> 17564 17565A message may use one or more character sets. 17566This part of the Pattern matches messages that make use of 17567certain specified character sets. 17568It will be considered a match if a message uses any of the character 17569sets in the list you give here. 17570 17571<P> 17572When filling in a value for this field, you may use 17573the "T" command, which presents you with a large list of 17574possible character sets to choose from. 17575You may also just type in the name of a character set, and it need not 17576be one that Alpine knows about. 17577 17578<P> 17579Besides actual character set names (for example, ISO-8859-7, KOI8-R, or 17580GB2312) you may also use some shorthand names that Alpine provides. 17581These names are more understandable shorthand names for sets of 17582character set names. 17583Two examples are "Cyrillic" and "Greek". 17584Selecting one of these shorthand names is equivalent to selecting all of 17585the character sets that make up the set. 17586You can see all of these shorthand names and the lists of character sets 17587they stand for by typing the "T" command. 17588 17589<P> 17590For the purposes of this Pattern, 17591Alpine will search through a message for all of the text parts and 17592collect the character sets declared for each part. 17593It will also look in the Subject line for a character set used there. 17594Alpine does not actually look at the text of the message or the text 17595of the Subject to determine if a declared character set is actually 17596used, it looks only at the declarations themselves in the MIME part headers 17597and in the Subject. 17598 17599<P> 17600It is possible to add a <EM>NOT</EM> to the Character Set Pattern meaning with the 17601"!" "toggle NOT" command. 17602This changes the meaning of the Character Set pattern so that 17603it has the opposite meaning. 17604It will be considered a match if none of the character sets in the 17605list are used in a message. 17606<P> 17607Don't make the mistake of putting the "!" in the data field for 17608the pattern. 17609For example, if you type the characters "!GB2312" into the 17610Character Set pattern, the pattern will look like: 17611<P> 17612<PRE> 17613 Charset pattern = !GB2312 17614</PRE> 17615<P> 17616This means you want to match the 7 character sequence "!GB2312". 17617In order to match messages that do not have the 17618character set "GB2312" 17619set, first type the characters "GB2312" followed 17620by carriage return for the value of the Character Set pattern, then negate it 17621by typing the "!" command. 17622It should end up looking like 17623<P> 17624<PRE> 17625 ! Charset pattern = GB2312 17626</PRE> 17627<P> 17628A technicality: Since comma is the character used to separate multiple 17629values in a pattern field, you have to escape comma with a backslash (\) if 17630you want to include a literal comma in the field. 17631In other words, if you type a backslash followed by a comma it will 17632be interpreted as a comma by Alpine, instead of as a separator between 17633pattern values. 17634All other backslashes are literal backslashes and should not be escaped. 17635<P> 17636Look "<A HREF="h_rule_patterns">here</A>" 17637for more information on Patterns. 17638<P> 17639Look <A HREF="h_edit_nav_cmds">here</A> 17640to see the available Editing and Navigation commands. 17641<P> 17642<End of help on this topic> 17643</BODY> 17644</HTML> 17645======= h_config_role_keywordpat ======= 17646<HTML> 17647<HEAD> 17648<TITLE>Keyword Pattern Explained</TITLE> 17649</HEAD> 17650<BODY> 17651<H1>Keyword Pattern Explained</H1> 17652 17653A folder may have user-defined keywords. 17654These are similar to the Important flag, which the user may set using the 17655Flag command. 17656The difference is that the Important flag is always present for each folder. 17657User-defined keywords are picked by the user. 17658You may add new keywords by defining them in the 17659<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen. 17660After you have added a potential keyword with the <!--#echo var="VAR_keywords"--> option, 17661the Flag command may be used to set or clear the keyword on individual messages. 17662If you have given a keyword a nickname when configuring it, 17663that nickname may be used instead of the actual keyword. 17664 17665<P> 17666When filling in a value for this field, it may be easiest to use 17667the "T" command, which presents you with a list of the keywords 17668you have defined to choose from. 17669 17670<P> 17671This part of the Pattern matches messages with certain keywords set. 17672It will be considered a match if a message has any of the keywords in the 17673list set. 17674A keyword that you have not defined using the 17675<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen 17676will not be a match. 17677 17678<P> 17679It is possible to add a <EM>NOT</EM> to the Keyword Pattern meaning with the 17680"!" "toggle NOT" command. 17681This changes the meaning of the Keyword pattern so that it has the opposite meaning. 17682It will be considered a match if none of the keywords in the list are set 17683for a message. 17684A keyword that you have not defined using the 17685<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen 17686will not be a match, so a <EM>NOT</EM> of that keyword does match. 17687<P> 17688Don't make the mistake of putting the "!" in the data field for 17689the pattern. 17690For example, if you type the characters "!frizzle" into the Keyword 17691pattern, the pattern will look like: 17692<P> 17693<PRE> 17694 Keyword pattern = !frizzle 17695</PRE> 17696<P> 17697This means you want to match the 8 character sequence "!frizzle". 17698In order to match messages that do not have the keyword "frizzle" 17699set, first type the characters "frizzle" followed 17700by carriage return for the value of the Keyword pattern, then negate it 17701by typing the "!" command. 17702It should end up looking like 17703<P> 17704<PRE> 17705 ! Keyword pattern = frizzle 17706</PRE> 17707<P> 17708A technicality: Since comma is the character used to separate multiple 17709values in a pattern field, you have to escape comma with a backslash (\) if 17710you want to include a literal comma in the field. 17711In other words, if you type a backslash followed by a comma it will 17712be interpreted as a comma by Alpine, instead of as a separator between 17713pattern values. 17714All other backslashes are literal backslashes and should not be escaped. 17715<P> 17716Look "<A HREF="h_rule_patterns">here</A>" 17717for more information on Patterns. 17718<P> 17719Look <A HREF="h_edit_nav_cmds">here</A> 17720to see the available Editing and Navigation commands. 17721<P> 17722<End of help on this topic> 17723</BODY> 17724</HTML> 17725======= h_config_role_arbpat ======= 17726<HTML> 17727<HEAD> 17728<TITLE>Extra Header Patterns Explained</TITLE> 17729</HEAD> 17730<BODY> 17731<H1>Extra Header Patterns Explained</H1> 17732 17733The header patterns that come after the Participant pattern but before the 17734AllText pattern are extra header patterns that you have added to a rule's 17735Pattern. These are just like the other header patterns except that 17736the contents of the particular header listed on the left hand side will 17737be used for comparisons. 17738<P> 17739The "eXtraHdr" command may be used to add more of these 17740header patterns to the rule you are editing. 17741<P> 17742The "RemoveHdr" command may be used to delete the highlighted 17743extra header pattern from the rule you are editing. 17744<P> 17745It is possible to add a <EM>NOT</EM> to the Extra Header Pattern meaning with the 17746"!" "toggle NOT" command. 17747This changes the meaning of the pattern so that it has the opposite meaning. 17748It will be considered a match if there are no matches between the 17749text in the header line and the list of patterns. 17750<P> 17751Don't make the mistake of putting the "!" in the data field for 17752the pattern. 17753For example, if you type the characters "!frizzle" into the 17754pattern, the pattern will look like: 17755<P> 17756<PRE> 17757 Xyz pattern = !frizzle 17758</PRE> 17759<P> 17760This means you want to match the 8 character sequence "!frizzle". 17761In order to match messages that do not have "frizzle" in 17762their Xyz field, first type the characters "frizzle" followed 17763by carriage return for the value of the pattern, then negate it 17764by typing the "!" command. 17765It should end up looking like 17766<P> 17767<PRE> 17768 ! Xyz pattern = frizzle 17769</PRE> 17770 17771<P> 17772A technicality: Since comma is the character used to separate multiple 17773values in a pattern field, you have to escape comma with a backslash (\) if 17774you want to include a literal comma in the field. 17775In other words, if you type a backslash followed by a comma it will 17776be interpreted as a comma by Alpine, instead of as a separator between 17777pattern values. 17778All other backslashes are literal backslashes and should not be escaped. 17779<P> 17780Look "<A HREF="h_rule_patterns">here</A>" 17781for more information on Patterns. 17782<P> 17783Look <A HREF="h_edit_nav_cmds">here</A> 17784to see the available Editing and Navigation commands. 17785<P> 17786<End of help on this topic> 17787</BODY> 17788</HTML> 17789======= h_config_role_cat_cmd ======= 17790<HTML> 17791<HEAD> 17792<TITLE>Categorizer Command Explained</TITLE> 17793</HEAD> 17794<BODY> 17795<H1>Categorizer Command Explained</H1> 17796 17797This is a command that is run with its standard input set to the message 17798being checked and its standard output discarded. 17799The full directory path should be specified. 17800The command will be run and then its exit status will be checked against 17801the Exit Status Interval, which defaults to just the value zero. 17802If the exit status of the command falls in the interval, it is considered 17803a match, otherwise it is not a match. 17804<P> 17805 17806This option may actually be a list of commands. 17807The first one that exists and is executable is used. 17808That makes it possible to use the same configuration with Unix Alpine and 17809PC-Alpine. 17810<P> 17811 17812If none of the commands in the list exists and is executable then the rule 17813is <EM>not</EM> a match. 17814If it is possible that the command may not exist, you should be careful 17815to structure your rules so that nothing destructive 17816happens when the command does not exist. 17817For example, you might have a filter that filters away spam when there is 17818a match but does nothing when there is not a match. 17819That would cause no harm if the command didn't exist. 17820However, if you have a filter that filters away spam when there is not 17821a match and keeps it when there is a match, that would filter everything 17822if the categorizer command didn't exist. 17823<P> 17824Here is an <A HREF="h_config_role_cat_cmd_example">example</A> 17825setup for the bogofilter filter. 17826 17827<P> 17828Look "<A HREF="h_rule_patterns">here</A>" 17829for more information on Patterns. 17830<P> 17831Look <A HREF="h_edit_nav_cmds">here</A> 17832to see the available Editing and Navigation commands. 17833<P> 17834<End of help on this topic> 17835</BODY> 17836</HTML> 17837======= h_config_role_cat_cmd_example ======= 17838<HTML> 17839<HEAD> 17840<TITLE>Categorizer Command Example</TITLE> 17841</HEAD> 17842<BODY> 17843<H1>Categorizer Command Example</H1> 17844 17845Bogofilter 17846(<A HREF="http://bogofilter.sourceforge.net/">http://bogofilter.sourceforge.net/</A>) 17847is a mail filter that attempts to classify mail as spam or 17848non-spam using statistical analysis of the message content. 17849When run with no arguments and a message as standard input, it exits with 17850exit status 0 if it thinks a message is spam and 1 if it thinks 17851it is not spam. 17852To use bogofilter as your Categorizer Command you would simply set Command to 17853the pathname of the bogofilter program. 17854For example, 17855<P> 17856<CENTER><SAMP>Command = /usr/local/bin/bogofilter</SAMP></CENTER> 17857<P> 17858Exit status of zero is what you are interested in, so you'd set the 17859Exit Status Interval to 17860<P> 17861<CENTER><SAMP>Exit Status Interval = (0,0)</SAMP></CENTER> 17862<P> 17863 17864In order to prevent downloading an entire huge message to check for spam, you 17865might want to set the Character Limit to a few thousand characters (the 17866assumption being that the spam will reveal itself in those characters) 17867<P> 17868<CENTER><SAMP>Character Limit = 50000</SAMP></CENTER> 17869<P> 17870 17871You would probably use bogofilter in an Alpine Filter Rule, and have the action 17872be to move the message to a spam folder. 17873It would usually be wise to also check the "Message is Recent" 17874part of the rule so that messages are only checked when they first arrive, 17875and to restrict the Current Folder Type to just your INBOX. 17876The reason for checking only Recent messages is to save the time it takes 17877to run bogofilter on each message. 17878As an experiment, you might start out by using this in an Indexcolor Rule 17879instead of a Filter Rule. 17880In that case, you probably wouldn't check the Recent checkbox. 17881<P> 17882The use described above assumes that you are somehow maintaining bogofilter's 17883database of words associated with spam and non-spam messages. 17884One way to start your database would be to select a bunch of spam messages 17885in Alpine (you might Save spam messages to a special folder or use Alpine's 17886Select command to select several) and then Apply 17887(<A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>) 17888a pipe command to the spam messages. 17889For example, you could have a shell script or an alias 17890called <EM>this_is_spam</EM>, which would simply be the command 17891<P> 17892<CENTER><SAMP>bogofilter -s</SAMP></CENTER> 17893<P> 17894 17895It is probably best to use the pipe command's Raw Text, With Delimiter, 17896and Free Output options, 17897which are at the bottom of the screen when you type the pipe command. 17898That's because bogofilter expects the raw message as input, and uses 17899the Delimiters to tell when a new message starts. 17900You would not need to use a separate pipe for each message, because 17901bogofilter can handle multiple messages at once. 17902<P> 17903Similarly, you would select a group of non-spam messages 17904and run them through a <EM>this_is_nonspam</EM> script 17905that was something like 17906<P> 17907<CENTER><SAMP>bogofilter -n</SAMP></CENTER> 17908<P> 17909 17910For the more adventurous, the next step might be to automate the upkeep of 17911the bogofilter database. 17912It might make more sense to have bogofilter be part of the delivery process, 17913but it is also possible to do it entirely from within Alpine. 17914Instead of using just plain "bogofilter" as the Categorizer Command, 17915the "-u" argument will cause bogofilter to update the database. 17916<P> 17917<CENTER><SAMP>Command = /usr/local/bin/bogofilter -u</SAMP></CENTER> 17918<P> 17919You'd want a couple more aliases or shell scripts called something like 17920<EM>change_to_spam</EM> 17921<P> 17922<CENTER><SAMP>bogofilter -Ns</SAMP></CENTER> 17923<P> 17924and 17925<EM>change_to_nonspam</EM> 17926<P> 17927<CENTER><SAMP>bogofilter -Sn</SAMP></CENTER> 17928<P> 17929When you run across a message in your INBOX that should have been 17930classified as spam you would pipe it to the change_to_spam script, and 17931when you run across a message in your spam folder that should have been 17932left in your INBOX you would pipe it through change_to_nonspam. 17933 17934<P> 17935There is a technical problem with this approach. 17936Alpine may check your filters more than once. 17937In particular, every time you start Alpine the filters will be checked for 17938each message. 17939Also, if you have any filters that depend on message state (New, Deleted, etc.) 17940then Alpine will recheck for matches in messages that have changed state 17941at the time you close the folder and before expunging. 17942This is usually ok. 17943However, in this case it is a problem because the command 17944<P> 17945<CENTER><SAMP>Command = /usr/local/bin/bogofilter -u</SAMP></CENTER> 17946<P> 17947has the side effect of updating the database. 17948So you run the risk of updating the database multiple times for a single 17949message instead of updating it just once per message. 17950There are some ways to work around this problem. 17951What you need is a way to mark the message after you have run the filter. 17952One way to mark messages is with the use of a keyword (say "Bogo"). 17953Besides having the filter move the message to a spam folder, also have it 17954set the Bogo keyword. 17955(Note that you will have to set up the "Bogo" keyword in the 17956<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in Setup/Config.) 17957This rule can only set the Bogo keyword for the messages that it matches. 17958You will also need to add a second rule right after this one that 17959matches all the messages that don't have the Bogo keyword set 17960(put the keyword in the Keyword pattern and toggle 17961the Not with the ! command) 17962and takes the action of setting it. 17963Then change the "bogofilter -u" rule so that it won't be a match 17964(and so it won't re-run the bogofilter command) if the keyword is already 17965set. 17966<P> 17967What you will end up with is a rule that runs "bogofilter -u" 17968on all messages that don't have the Bogo keyword set. 17969This will have the side effect of inserting that message in the bogofilter 17970database, match or not. 17971If this rule matches (it is spam), the Bogo keyword will be set and 17972the message will be moved to a spam folder. 17973If it does not match, the 17974following rule will mark the message by turning on the keyword. 17975This second rule should be a non-terminating 17976(<A HREF="h_config_filt_opts_nonterm">Dont-Stop-Even-if-Rule-Matches</A>) 17977rule so that it doesn't stop the filtering process before the rest of 17978your rules are consulted. 17979 17980<P> 17981In summary, the first rule is something like 17982<PRE> 17983 Nickname = bogofilter -u rule 17984 Current Folder Type = 17985 (*) Specific 17986 Folder = INBOX 17987 17988 ! Keyword pattern = Bogo 17989 17990 External Categorizer Commands = 17991 Command = /usr/local/bin/bogofilter -u 17992 Exit Status Interval = (0,0) 17993 Character Limit = <No Value Set: using "-1"> (optionally set this) 17994 17995 Filter Action = 17996 (*) Move 17997 Folder = spam 17998 17999 Set These Keywords = Bogo 18000</PRE> 18001<P> 18002and the following rule is 18003<PRE> 18004 Nickname = Set Bogo Keyword 18005 Current Folder Type = 18006 (*) Specific 18007 Folder = INBOX 18008 18009 ! Keyword pattern = Bogo 18010 18011 Filter Action = 18012 (*) Just Set Message Status 18013 18014 Set These Keywords = Bogo 18015 18016 Features = 18017 [X] dont-stop-even-if-rule-matches 18018</PRE> 18019<P> 18020If it is possible for you to insert bogofilter in the delivery process instead 18021of having it called from Alpine you could prevent having to wait 18022for the bogofilter processing while you read your mail. 18023You would have bogofilter add a header to the message at the time of delivery 18024that identified it as spam or nonspam. 18025With this method, you could avoid using a Categorizer Command while running Alpine, 18026and just match on the header instead. 18027You might still want to use the scripts mentioned above to initialize the 18028database or to re-classify wrongly classified messages. 18029 18030<P> 18031Finally, it isn't for the faint-hearted, 18032but it is also possible to run bogofilter from PC-Alpine. 18033You can install Cygwin from 18034<A HREF="http://www.cygwin.com/">http://www.cygwin.com/</A> and 18035then compile bogofilter in the cygwin environment, and run it from 18036within PC-Alpine. 18037You would end up with a Categorizer command that looked something like 18038<P> 18039<CENTER><SAMP>Command = C:\cygwin\bin\bogofilter.exe -u</SAMP></CENTER> 18040<P> 18041Note that the ".exe" extension is explicit, 18042and that the bogofilter.exe executable should be in the same directory 18043as cygwin1.dll. 18044 18045<P> 18046<End of help on this topic> 18047</BODY> 18048</HTML> 18049======= h_config_role_cat_status ======= 18050<HTML> 18051<HEAD> 18052<TITLE>Exit Status Interval Explained</TITLE> 18053</HEAD> 18054<BODY> 18055<H1>Exit Status Interval Explained</H1> 18056 18057The categorizer command is run and the result is the exit status of 18058that command. 18059If that exit status falls in the Exit Status Interval 18060then it is considered a match, otherwise it is not a match. 18061Of course for the entire rule to match, it must also be checked against 18062the other defined parts of the Pattern. 18063<P> 18064The Exit Status Interval defaults to the single value 0 (zero). 18065If you define it, it should be set to something like: 18066<P> 18067<CENTER><SAMP>(min_exit_value,max_exit_value)</SAMP></CENTER> 18068<P> 18069where "min_exit_value" and "max_exit_value" are integers. 18070The special values "INF" and "-INF" may be used for large 18071positive and negative integers. 18072<P> 18073Actually, a list of intervals may be used if you wish. 18074A list would look like 18075<P> 18076<CENTER><SAMP>(min_exit_value1,max_exit_value1),(min_exit_value2,max_exit_value2),...</SAMP></CENTER> 18077<P> 18078When there is an Exit Status Interval defined, it is a match if the exit status 18079of the categorizer command is contained in any of the intervals. 18080The intervals include both endpoints. 18081<P> 18082The default interval is 18083<P> 18084<CENTER><SAMP>(0,0)</SAMP></CENTER> 18085<P> 18086and it matches only if the command exits with exit status equal to zero. 18087 18088<P> 18089Look "<A HREF="h_rule_patterns">here</A>" 18090for more information on Patterns. 18091<P> 18092Look <A HREF="h_edit_nav_cmds">here</A> 18093to see the available Editing and Navigation commands. 18094<P> 18095<End of help on this topic> 18096</BODY> 18097</HTML> 18098======= h_config_role_cat_limit ======= 18099<HTML> 18100<HEAD> 18101<TITLE>Character Limit Explained</TITLE> 18102</HEAD> 18103<BODY> 18104<H1>Character Limit Explained</H1> 18105 18106Setting this option makes it possible to limit how much of the message 18107is made available to the categorizer command as input. 18108The default value (-1) means that the entire message is fed to the 18109command. 18110A value of 0 (zero) means that only the headers of the message are 18111made available. 18112A positive integer means that the headers plus that many characters from 18113the body of the message are passed to the categorizer. 18114 18115<P> 18116Look "<A HREF="h_rule_patterns">here</A>" 18117for more information on Patterns. 18118<P> 18119Look <A HREF="h_edit_nav_cmds">here</A> 18120to see the available Editing and Navigation commands. 18121<P> 18122<End of help on this topic> 18123</BODY> 18124</HTML> 18125======= h_config_role_age ======= 18126<HTML> 18127<HEAD> 18128<TITLE>Age Interval Explained</TITLE> 18129</HEAD> 18130<BODY> 18131<H1>Age Interval Explained</H1> 18132 18133The Age Interval, if defined, is part of the Pattern. 18134If you use this, it should be set to something like: 18135<P> 18136<CENTER><SAMP>(min_age,max_age)</SAMP></CENTER> 18137<P> 18138where "min_age" and "max_age" are non-negative integers. 18139The special value "INF" may be used for the max value. 18140It represents infinity. 18141<P> 18142In rare cases it may be useful to use the more general form of the value, 18143which is a comma-separated list of intervals. 18144It would look something like: 18145<P> 18146<CENTER><SAMP>(min_age1,max_age1),(min_age2,max_age2),...</SAMP></CENTER> 18147<P> 18148When there is an Age Interval defined, it is a match if the age, in days, of 18149the message is contained in the interval. 18150The interval includes both endpoints. 18151If the option is set to a list of intervals then it is a match if the 18152age of the message is contained in any of the intervals. 18153<P> 18154Even though this option is called Age, it isn't actually 18155the <EM>age</EM> of the message. 18156Instead, it is how many days ago the message arrived in one of your folders. 18157If the current time is a little past midnight, then a message that arrived 18158just before midnight arrived yesterday, even though the message is only 18159a few minutes old. 18160By default, the date being used is not the date in the Date 18161header of the message. 18162It is the date that the message arrived in one of your folders. 18163When you Save a message from one folder to another that arrival date 18164is preserved. 18165If you would like to use the date in the Date header that is possible. 18166Turn on the option 18167<A HREF="h_config_filt_opts_sentdate">"Use-Date-Header-For-Age"</A> 18168near the bottom of the rule definition. 18169<P> 18170A value of 0 is today, 1 is yesterday, 2 is the day before yesterday, and so on. 18171The age interval 18172<P> 18173<CENTER><SAMP>(2,2)</SAMP></CENTER> 18174<P> 18175matches all messages that arrived on the day before yesterday. 18176The interval 18177<P> 18178<CENTER><SAMP>(180,INF)</SAMP></CENTER> 18179<P> 18180matches all messages that arrived at least 180 days before today. 18181The interval 18182<P> 18183<CENTER><SAMP>(0,1)</SAMP></CENTER> 18184<P> 18185matches all messages that arrived today or yesterday. 18186 18187<P> 18188Look "<A HREF="h_rule_patterns">here</A>" 18189for more information on Patterns. 18190<P> 18191Look <A HREF="h_edit_nav_cmds">here</A> 18192to see the available Editing and Navigation commands. 18193<P> 18194<End of help on this topic> 18195</BODY> 18196</HTML> 18197======= h_config_role_size ======= 18198<HTML> 18199<HEAD> 18200<TITLE>Size Interval Explained</TITLE> 18201</HEAD> 18202<BODY> 18203<H1>Size Interval Explained</H1> 18204 18205The Size Interval, if defined, is part of the Pattern. 18206If you use this, it should be set to something like: 18207<P> 18208<CENTER><SAMP>(min_size,max_size)</SAMP></CENTER> 18209<P> 18210where "min_size" and "max_size" are non-negative integers. 18211The special value "INF" may be used for the max value. 18212It represents infinity. 18213<P> 18214In rare cases it may be useful to use the more general form of the value, 18215which is a comma-separated list of intervals. 18216It would look something like: 18217<P> 18218<CENTER><SAMP>(min_size1,max_size1),(min_size2,max_size2),...</SAMP></CENTER> 18219<P> 18220When there is a Size Interval defined, it is a match if the size of 18221the message is contained in the interval. 18222The interval includes both endpoints. 18223If the option is set to a list of intervals then it is a match if the 18224size of the message is contained in any of the intervals. 18225<P> 18226The size interval 18227<P> 18228<CENTER><SAMP>(10000,50000)</SAMP></CENTER> 18229<P> 18230matches all messages with sizes greater than or equal to 10000, and less 18231than or equal to 50000. 18232The interval 18233<P> 18234<CENTER><SAMP>(100000,INF)</SAMP></CENTER> 18235<P> 18236matches all messages with sizes greater than or equal to 100000. 18237 18238<P> 18239Look "<A HREF="h_rule_patterns">here</A>" 18240for more information on Patterns. 18241<P> 18242Look <A HREF="h_edit_nav_cmds">here</A> 18243to see the available Editing and Navigation commands. 18244<P> 18245<End of help on this topic> 18246</BODY> 18247</HTML> 18248======= h_config_role_scorei ======= 18249<HTML> 18250<HEAD> 18251<TITLE>Score Interval Explained</TITLE> 18252</HEAD> 18253<BODY> 18254<H1>Score Interval Explained</H1> 18255 18256The Score Interval, if defined, is part of the Pattern. 18257If you use this, it should be set to something like: 18258<P> 18259<CENTER><SAMP>(min_score,max_score)</SAMP></CENTER> 18260<P> 18261where "min_score" and "max_score" are integers between 18262-32000 and 32000. 18263The special values "-INF" and "INF" may be used for 18264the min and max values. 18265These represent negative and positive infinity. 18266<P> 18267Actually, the value may be a list of intervals rather than just a 18268single interval if that is useful. 18269The elements of the list are separated by commas like: 18270<P> 18271<CENTER><SAMP>(min_score1,max_score1),(min_score2,max_score2),...</SAMP></CENTER> 18272<P> 18273When there is a Score Interval defined, it is a match if the score for 18274the message is contained in any of the intervals. 18275The intervals include both endpoints. 18276The score for a message is calculated by looking at every scoring rule 18277defined and adding up the Score Values for the rules that match the message. 18278Scoring rules are created using the 18279<A HREF="h_rules_score">"SETUP SCORING"</A> screen. 18280 18281<P> 18282Look "<A HREF="h_rule_patterns">here</A>" 18283for more information on Patterns. 18284<P> 18285Look <A HREF="h_edit_nav_cmds">here</A> 18286to see the available Editing and Navigation commands. 18287<P> 18288<End of help on this topic> 18289</BODY> 18290</HTML> 18291======= h_config_role_fldr_type ======= 18292<HTML> 18293<HEAD> 18294<TITLE>Current Folder Type Explained</TITLE> 18295</HEAD> 18296<BODY> 18297<H1>Current Folder Type Explained</H1> 18298 18299The Current Folder Type is part of the role's Pattern. 18300It refers to the type of the currently open folder, which is the folder 18301you were last looking at from the MESSAGE INDEX or MESSAGE TEXT screen. 18302In order for a role to be considered a match, the current folder must 18303be of the type you set here. 18304The three types "Any", "News", and "Email" are 18305all what you might think. 18306<P> 18307If the Current Folder Type for a role's Pattern is set to "News", for 18308example, then 18309that role will only be a match if the current folder is a newsgroup and 18310the rest of the Pattern matches. 18311The value "Specific" may be used when you want to limit the match 18312to a specific folder (not just a specific type of folder), or to a list of 18313specific folders. 18314<P> 18315In order to match a specific folder you Select the "Specific" 18316button <EM>AND</EM> fill in 18317the name (or list of names) of 18318the folder in the "Folder List" field. 18319If the current folder is any of the folders in the list, that is considered 18320a match. 18321The name of each folder in the list may be either "INBOX", 18322the technical specification 18323of the folder (like what appears in your configuration file) or, if the 18324folder is one of your incoming folders, it may be the nickname you've given 18325the folder. 18326Here are a couple samples of specific folder names: 18327<P> 18328<CENTER><SAMP>{monet.art.example.com/user=vincent}mail/art-class</SAMP></CENTER> 18329<P> 18330<CENTER><SAMP>{news.example.com/nntp/user=peter}#news.comp.mail.pine</SAMP></CENTER> 18331<P> 18332Observe that in order for an external folder (IMAP, POP, News) to be a match, 18333you must also add the /user= option in the definition of the incoming folder. 18334<P> 18335The easiest way to fill in the "Folder List" field is to use 18336the "T" command that is available when the "Folder List" line is 18337highlighted, or to use the "Take" command with the configuration 18338feature 18339<A HREF="h_config_enable_role_take">"<!--#echo var="FEAT_enable-rules-under-take"-->"</A> 18340turned on. 18341Note that you won't be able to edit the "Folder List" line unless the 18342Current Folder Type is set to "Specific", and any value that 18343"Folder List" has is ignored unless the type 18344is set to "Specific". 18345<P> 18346When reading a newsgroup, there may be a performance penalty 18347incurred when collecting the information necessary to check a Pattern. 18348For this reason, the default Current Folder Type is set to "Email". 18349<P> 18350Look "<A HREF="h_rule_patterns">here</A>" 18351for more information on Patterns. 18352<P> 18353Look <A HREF="h_edit_nav_cmds">here</A> 18354to see the available Editing and Navigation commands. 18355<P> 18356<End of help on this topic> 18357</BODY> 18358</HTML> 18359======= h_config_filt_rule_type ======= 18360<HTML> 18361<HEAD> 18362<TITLE>Filter Action Explained</TITLE> 18363</HEAD> 18364<BODY> 18365<H1>Filter Action Explained</H1> 18366 18367The Filter Action specifies the action to be taken when the Pattern is a 18368match. 18369It may be set to "Delete" "Move", or 18370"Just Set Message Status". 18371<P> 18372If it is set to "Delete", then the message that matches the 18373Pattern will be deleted from the open folder. 18374<P> 18375If it is set to "Move", then the name of the folder to which 18376the matching message should be moved is given in the "Folder List" field on the 18377next line of the screen. 18378A list of folders separated by commas may be given, in which case the 18379message will be copied to all of the folders in the list before it is 18380deleted. 18381<P> 18382If it is set to neither of those two values (it is set to the value 18383labeled "Just Set Message Status") then the message status 18384setting will happen 18385but the message will not be deleted or moved. 18386<P> 18387If you are Moving a message you may also set Message Status if you wish. 18388<P> 18389The easiest way to fill in the "Folder List" field is to use 18390the T command that is available when the "Folder List" line is 18391highlighted. 18392Note that you won't be able to edit the "Folder List" line unless the 18393Filter Action is set to "Move", and any value that 18394"Folder List" has is ignored unless the type 18395is set to "Move". 18396<P> 18397There are a few tokens that may be used in the names in the Folder List. 18398They are all related to the date on which the filtering is taking place. 18399The tokens are words surrounded by underscores. 18400For example, if you want your filter to move messages to a folder named 18401<P><CENTER><SAMP>abc-year-mon</SAMP></CENTER><P> 18402you could specify the folder as 18403<P><CENTER><SAMP>abc-_CURYEAR_-_CURMONTHABBREV_</SAMP></CENTER><P> 18404which would result in a file named something like 18405<P><CENTER><SAMP>abc-2004-oct</SAMP></CENTER><P> 18406or 18407<P><CENTER><SAMP>abc-_CURYEAR2DIGIT_-_CURMONTH2DIGIT_</SAMP></CENTER><P> 18408which would result in a file named something like 18409<P><CENTER><SAMP>abc-04-10</SAMP></CENTER><P> 18410The available tokens are listed 18411<A HREF="h_index_tokens">here</A>. 18412<P> 18413Look "<A HREF="h_rule_patterns">here</A>" 18414for more information on Patterns. 18415<P> 18416Look <A HREF="h_edit_nav_cmds">here</A> 18417to see the available Editing and Navigation commands. 18418<P> 18419<End of help on this topic> 18420</BODY> 18421</HTML> 18422======= h_config_score_fldr_type ======= 18423<HTML> 18424<HEAD> 18425<TITLE>Current Folder Type Explained</TITLE> 18426</HEAD> 18427<BODY> 18428<H1>Current Folder Type Explained</H1> 18429 18430The Current Folder Type is part of the scoring rule's Pattern. 18431It refers to the type of the folder that 18432the message being scored is in. 18433In order for a rule to be considered a match, the current folder must 18434be of the type you set here. 18435The three types "Any", "News", and "Email" are 18436all what you might think. 18437<P> 18438If the Current Folder Type for a Pattern is set to "News", for 18439example, then 18440that Pattern will only match if the current folder is a newsgroup and 18441the rest of the Pattern matches. 18442The value "Specific" may be used when you want to limit the match 18443to a specific folder (not just a specific type of folder), or to a list of 18444specific folders. 18445<P> 18446In order to match a specific folder you Select the "Specific" 18447button <EM>AND</EM> fill in 18448the name (or list of names) of 18449the folder in the "Folder List" field. 18450If the current folder is any of the folders in the list, that is considered 18451a match. 18452The name of each folder in the list may be either "INBOX", the technical specification 18453of the folder (like what appears in your configuration file) or, if the 18454folder is one of your incoming folders, it may be the nickname you've given 18455the folder. 18456Here are a couple samples of specific folder names: 18457<P> 18458<CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER> 18459<P> 18460<CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER> 18461<P> 18462The easiest way to fill in the "Folder List" field is to use 18463the T command that is available when the "Folder List" line is 18464highlighted. 18465Note that you won't be able to edit the "Folder List" line unless the 18466Current Folder Type is set to "Specific", and any value that 18467"Folder List" has is ignored unless the type 18468is set to "Specific". 18469<P> 18470When reading a newsgroup, there may be a performance penalty 18471incurred when collecting the information necessary to check a Pattern. 18472For this reason, the default Current Folder Type is set to "Email". 18473For example, if you have Index Line Coloring rules that have Score Intervals 18474defined then the scores for all the visible messages will need to be calculated. 18475If some of your Scoring rules have 18476a Current Folder Type of 18477"Any" or "News" this may cause the MESSAGE INDEX 18478screen to draw more slowly when in a newsgroup. 18479<P> 18480Look "<A HREF="h_rule_patterns">here</A>" 18481for more information on Patterns. 18482<P> 18483Look <A HREF="h_edit_nav_cmds">here</A> 18484to see the available Editing and Navigation commands. 18485<P> 18486<End of help on this topic> 18487</BODY> 18488</HTML> 18489======= h_config_other_fldr_type ======= 18490<HTML> 18491<HEAD> 18492<TITLE>Current Folder Type Explained</TITLE> 18493</HEAD> 18494<BODY> 18495<H1>Current Folder Type Explained</H1> 18496 18497The Current Folder Type is part of the rule's Pattern. 18498It refers to the type of the folder being viewed. 18499In order for a rule to be considered a match, the current folder must 18500be of the type you set here. 18501The three types "Any", "News", and "Email" are 18502all what you might think. 18503<P> 18504If the Current Folder Type for a Pattern is set to "News", for 18505example, then 18506that Pattern will only match if the current folder is a newsgroup. 18507The value "Specific" may be used when you want to limit the match 18508to a specific folder (not just a specific type of folder), or to a list of 18509specific folders. 18510<P> 18511In order to match a specific folder you Select the "Specific" 18512button <EM>AND</EM> fill in 18513the name (or list of names) of 18514the folder in the "Folder List" field. 18515If the current folder is any of the folders in the list, that is considered 18516a match. 18517The name of each folder in the list may be either "INBOX", the technical specification 18518of the folder (like what appears in your configuration file) or, if the 18519folder is one of your incoming folders, it may be the nickname you've given 18520the folder. 18521Here are a couple samples of specific folder names: 18522<P> 18523<CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER> 18524<P> 18525<CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER> 18526<P> 18527The easiest way to fill in the "Folder List" field is to use 18528the T command that is available when the "Folder List" line is 18529highlighted. 18530Note that you won't be able to edit the "Folder List" line unless the 18531Current Folder Type is set to "Specific", and any value that 18532"Folder List" has is ignored unless the type 18533is set to "Specific". 18534<P> 18535Look "<A HREF="h_rule_patterns">here</A>" 18536for more information on Patterns. 18537<P> 18538Look <A HREF="h_edit_nav_cmds">here</A> 18539to see the available Editing and Navigation commands. 18540<P> 18541<End of help on this topic> 18542</BODY> 18543</HTML> 18544======= h_config_incol_fldr_type ======= 18545<HTML> 18546<HEAD> 18547<TITLE>Current Folder Type Explained</TITLE> 18548</HEAD> 18549<BODY> 18550<H1>Current Folder Type Explained</H1> 18551 18552The Current Folder Type is part of the Line Coloring rule's Pattern. 18553It refers to the type of the folder for which the MESSAGE INDEX is 18554being viewed. 18555In order for a rule to be considered a match, the current folder must 18556be of the type you set here. 18557The three types "Any", "News", and "Email" are 18558all what you might think. 18559<P> 18560If the Current Folder Type for a Pattern is set to "News", for 18561example, then 18562that Pattern will only match if the current folder is a newsgroup and 18563the rest of the Pattern matches. 18564The value "Specific" may be used when you want to limit the match 18565to a specific folder (not just a specific type of folder), or to a list of 18566specific folders. 18567<P> 18568In order to match a specific folder you Select the "Specific" 18569button <EM>AND</EM> fill in 18570the name (or list of names) of 18571the folder in the "Folder List" field. 18572If the current folder is any of the folders in the list, that is considered 18573a match. 18574The name of each folder in the list may be either "INBOX", the technical specification 18575of the folder (like what appears in your configuration file) or, if the 18576folder is one of your incoming folders, it may be the nickname you've given 18577the folder. 18578Here are a couple samples of specific folder names: 18579<P> 18580<CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER> 18581<P> 18582<CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER> 18583<P> 18584The easiest way to fill in the "Folder List" field is to use 18585the T command that is available when the "Folder List" line is 18586highlighted. 18587Note that you won't be able to edit the "Folder List" line unless the 18588Current Folder Type is set to "Specific", and any value that 18589"Folder List" has is ignored unless the type 18590is set to "Specific". 18591<P> 18592When reading a newsgroup, there may be a performance penalty 18593incurred when collecting the information necessary to check a Pattern. 18594For this reason, the default Current Folder Type is set to "Email". 18595For example, a rule with a non-Normal Index Line Color 18596and a Current Folder Type of 18597"Any" or "News" may cause the MESSAGE INDEX 18598screen to draw more slowly when in a newsgroup. 18599<P> 18600Look "<A HREF="h_rule_patterns">here</A>" 18601for more information on Patterns. 18602<P> 18603Look <A HREF="h_edit_nav_cmds">here</A> 18604to see the available Editing and Navigation commands. 18605<P> 18606<End of help on this topic> 18607</BODY> 18608</HTML> 18609======= h_config_filt_fldr_type ======= 18610<HTML> 18611<HEAD> 18612<TITLE>Current Folder Type Explained</TITLE> 18613</HEAD> 18614<BODY> 18615<H1>Current Folder Type Explained</H1> 18616 18617The Current Folder Type is part of the Filtering rule's Pattern. 18618It refers to the type of the folder for which the filtering is being done. 18619In order for a rule to be considered a match, the current folder must 18620be of the type you set here. 18621The three types "Any", "News", and "Email" are 18622all what you might think. 18623<P> 18624If the Current Folder Type for a Pattern is set to "News", for 18625example, then 18626that Pattern will only match if the current folder is a newsgroup and 18627the rest of the Pattern matches. 18628The value "Specific" may be used when you want to limit the match 18629to a specific folder (not just a specific type of folder), or to a list of 18630specific folders. 18631<P> 18632In order to match a specific folder you Select the "Specific" 18633button <EM>AND</EM> fill in 18634the name (or list of names) of 18635the folder in the "Folder List" field. 18636If the current folder is any of the folders in the list, that is considered 18637a match. 18638The name of each folder in the list may be either "INBOX", the technical specification 18639of the folder (like what appears in your configuration file) or, if the 18640folder is one of your incoming folders, it may be the nickname you've given 18641the folder. 18642Here are a couple samples of specific folder names: 18643<P> 18644<CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER> 18645<P> 18646<CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER> 18647<P> 18648The easiest way to fill in the "Folder List" field is to use 18649the T command that is available when the "Folder List" line is 18650highlighted. 18651Note that you won't be able to edit the "Folder List" line unless the 18652Current Folder Type is set to "Specific", and any value that 18653"Folder List" has is ignored unless the type 18654is set to "Specific". 18655<P> 18656When reading a newsgroup, there may be a performance penalty 18657incurred when collecting the information necessary to check a Pattern. 18658For this reason, the default Current Folder Type is set to "Email". 18659For example, a rule with a Current Folder Type of either 18660"Any" or "News" may cause the filtering to happen 18661more slowly when opening a newsgroup. 18662<P> 18663Look "<A HREF="h_rule_patterns">here</A>" 18664for more information on Patterns. 18665<P> 18666Look <A HREF="h_edit_nav_cmds">here</A> 18667to see the available Editing and Navigation commands. 18668<P> 18669<End of help on this topic> 18670</BODY> 18671</HTML> 18672======= h_config_role_stat_imp ======= 18673<HTML> 18674<HEAD> 18675<TITLE>Message Important Status Explained</TITLE> 18676</HEAD> 18677<BODY> 18678<H1>Message Important Status Explained</H1> 18679 18680This part of the Pattern may have one of three possible values. 18681The default value is "Don't care", which matches any message. 18682The other two values are "Yes", which means the message must be 18683flagged "Important" in order to be a match; or "No", which 18684means the message must <EM>not</EM> be flagged "Important" in order 18685to be a match. 18686<P> 18687Look "<A HREF="h_rule_patterns">here</A>" 18688for more information on Patterns. 18689<P> 18690Look <A HREF="h_edit_nav_cmds">here</A> 18691to see the available Editing and Navigation commands. 18692<P> 18693<End of help on this topic> 18694</BODY> 18695</HTML> 18696======= h_config_role_stat_new ======= 18697<HTML> 18698<HEAD> 18699<TITLE>Message New Status Explained</TITLE> 18700</HEAD> 18701<BODY> 18702<H1>Message New Status Explained</H1> 18703 18704This part of the Pattern may have one of three possible values. 18705The default value is "Don't care", which matches any message. 18706The other two values are "Yes", which means the message must be 18707"New" in order to be a match; or "No", which 18708means the message must <EM>not</EM> be "New" in order 18709to be a match. 18710"New" is the same as <EM>Unseen</EM> and not "New" is the 18711same as <EM>Seen</EM>. 18712<P> 18713The nomenclature for New and Recent is a bit confusing: 18714<P> 18715New means that the message is Unseen. 18716It could have been in your mailbox for a long time but if you haven't looked 18717at it, it is still considered New. 18718That matches the default Alpine index display that shows an N for such a 18719message. 18720<P> 18721Recent means that the message was added to this folder since the last time 18722you opened the folder. 18723Alpine also shows an N by default for these types of messages. 18724If you were to run two copies of Alpine that opened a folder one right after 18725the other, a message would only show up as Recent in (at most) the first 18726Alpine session. 18727<P> 18728Look "<A HREF="h_rule_patterns">here</A>" 18729for more information on Patterns. 18730<P> 18731Look <A HREF="h_edit_nav_cmds">here</A> 18732to see the available Editing and Navigation commands. 18733<P> 18734<End of help on this topic> 18735</BODY> 18736</HTML> 18737======= h_config_role_stat_recent ======= 18738<HTML> 18739<HEAD> 18740<TITLE>Message Recent Status Explained</TITLE> 18741</HEAD> 18742<BODY> 18743<H1>Message Recent Status Explained</H1> 18744 18745This part of the Pattern may have one of three possible values. 18746The default value is "Don't care", which matches any message. 18747The other two values are "Yes", which means the message must be 18748"Recent" in order to be a match; or "No", which 18749means the message must <EM>not</EM> be "Recent" in order 18750to be a match. 18751"Recent" means that the message was added to the folder since 18752the last time the folder was opened. 18753If more than one mail client has the folder opened, the message will 18754appear to be "Recent" to only one of the clients. 18755<P> 18756The nomenclature for New and Recent is a bit confusing: 18757<P> 18758New means that the message is Unseen. 18759It could have been in your mailbox for a long time but if you haven't looked 18760at it, it is still considered New. 18761That matches the default Alpine index display that shows an N for such a 18762message. 18763<P> 18764Recent means that the message was added to this folder since the last time 18765you opened the folder. 18766Alpine also shows an N by default for these types of messages. 18767If you were to run two copies of Alpine that opened a folder one right after 18768the other, a message would only show up as Recent in (at most) the first 18769Alpine session. 18770<P> 18771Look "<A HREF="h_rule_patterns">here</A>" 18772for more information on Patterns. 18773<P> 18774Look <A HREF="h_edit_nav_cmds">here</A> 18775to see the available Editing and Navigation commands. 18776<P> 18777<End of help on this topic> 18778</BODY> 18779</HTML> 18780======= h_config_role_stat_del ======= 18781<HTML> 18782<HEAD> 18783<TITLE>Message Deleted Status Explained</TITLE> 18784</HEAD> 18785<BODY> 18786<H1>Message Deleted Status Explained</H1> 18787 18788This part of the Pattern may have one of three possible values. 18789The default value is "Don't care", which matches any message. 18790The other two values are "Yes", which means the message must be 18791marked "Deleted" in order to be a match; or "No", which 18792means the message must <EM>not</EM> be marked "Deleted" in order 18793to be a match. 18794<P> 18795If you are thinking of using this part of the Pattern as a way to prevent 18796messages from being filtered more than once in a Filter Pattern, 18797take a look at the Filter Option 18798<A HREF="h_config_filt_opts_notdel">"Move-Only-if-Not-Deleted"</A> 18799instead. 18800It should work better than using this field since it will hide the filtered 18801messages even if they are already Deleted. 18802That option is at the bottom of the Filter configuration screen. 18803<P> 18804Look "<A HREF="h_rule_patterns">here</A>" 18805for more information on Patterns. 18806<P> 18807Look <A HREF="h_edit_nav_cmds">here</A> 18808to see the available Editing and Navigation commands. 18809<P> 18810<End of help on this topic> 18811</BODY> 18812</HTML> 18813======= h_config_role_stat_ans ======= 18814<HTML> 18815<HEAD> 18816<TITLE>Message Answered Status Explained</TITLE> 18817</HEAD> 18818<BODY> 18819<H1>Message Answered Status Explained</H1> 18820 18821This part of the Pattern may have one of three possible values. 18822The default value is "Don't care", which matches any message. 18823The other two values are "Yes", which means the message must be 18824marked "Answered" in order to be a match; or "No", which 18825means the message must <EM>not</EM> be marked "Answered" in order 18826to be a match. 18827<P> 18828Look "<A HREF="h_rule_patterns">here</A>" 18829for more information on Patterns. 18830<P> 18831Look <A HREF="h_edit_nav_cmds">here</A> 18832to see the available Editing and Navigation commands. 18833<P> 18834<End of help on this topic> 18835</BODY> 18836</HTML> 18837======= h_config_role_abookfrom ======= 18838<HTML> 18839<HEAD> 18840<TITLE>Address in Address Book Explained</TITLE> 18841</HEAD> 18842<BODY> 18843<H1>Address in Address Book Explained</H1> 18844 18845This option gives you a way to match messages that contain an address 18846that is in one of your address books. 18847Only the simple entries in your address books are searched. 18848Address book distribution lists are ignored! 18849<P> 18850This part of the Pattern may have one of five possible values. 18851The default value is "Don't care", which matches any message. 18852The value "Yes, in any address book" means at least one of the addresses 18853from the message must be in at least one of your 18854address books in order to be a match. 18855The value "No, not in any address book" 18856means none of the addresses may 18857be in any of your address books in order to be a match. 18858<P> 18859The values "Yes, in specific address books" and 18860"No, not in any of specific address books" are similar but instead 18861of depending on all address books you are allowed to give a list of address 18862books to look in. 18863Usually this would be a single address book but it may be a 18864list of address books as well. 18865For each of these "specific" address book options you Select which 18866of the Specific options you want (Yes or No) <EM>AND</EM> fill in the 18867name (or list of names) of the address book in the 18868"Abook List" field. 18869The names to be used are those that appear in the ADDRESS BOOK LIST screen. 18870The easiest way to fill in the Abook List field it to use 18871the "T" command that is available when the "Abook List" 18872line is highlighted. 18873Note that you won't be able to edit the "Abook List" line unless the 18874option is set to one of the two "Specific", values. 18875<P> 18876The addresses from the message that are checked for are determined by the 18877setting you have for "Types of addresses to check for in address book". 18878If you set this to "From" the From address from the message will 18879be looked up in the address book. 18880If you set it to "To" instead then the To addresses will be used. 18881If any of the To addresses are in the address book then it is considered 18882a match for "Yes" or not a match for "No". 18883You could set it to both From and To, in which case all of the From and To 18884addresses are used. 18885The "Reply-To" and "Sender" cases are a little unusual. 18886Due to deficiencies in our tools, Reply-To uses the Reply-To address if it 18887exists or the From address if there is no Reply-To address. 18888Same for the Sender address. 18889<P> 18890Look "<A HREF="h_rule_patterns">here</A>" 18891for more information on Patterns. 18892<P> 18893Look <A HREF="h_edit_nav_cmds">here</A> 18894to see the available Editing and Navigation commands. 18895<P> 18896<End of help on this topic> 18897</BODY> 18898</HTML> 18899======= h_config_inabook_from ======= 18900<HTML> 18901<HEAD> 18902<TITLE>From</TITLE> 18903</HEAD> 18904<BODY> 18905<H1>From</H1> 18906 18907Setting the From line will cause the address from the From header line 18908of the message to be checked for in the address book. 18909<P> 18910<End of help on this topic> 18911</BODY> 18912</HTML> 18913======= h_config_inabook_replyto ======= 18914<HTML> 18915<HEAD> 18916<TITLE>Reply-To</TITLE> 18917</HEAD> 18918<BODY> 18919<H1>Reply-To</H1> 18920 18921Setting the Reply-To line will cause the address from the Reply-To header line 18922of the message to be checked for in the address book. 18923However, if there is no Reply-To header line in the message the From header 18924line will be used instead. 18925We understand this is dumb but we don't have an easy way around it. 18926<P> 18927<End of help on this topic> 18928</BODY> 18929</HTML> 18930======= h_config_inabook_sender ======= 18931<HTML> 18932<HEAD> 18933<TITLE>Sender</TITLE> 18934</HEAD> 18935<BODY> 18936<H1>Sender</H1> 18937 18938Setting the Sender line will cause the address from the Sender header line 18939of the message to be checked for in the address book. 18940However, if there is no Sender header line in the message the From header 18941line will be used instead. 18942We understand this is dumb but we don't have an easy way around it. 18943<P> 18944<End of help on this topic> 18945</BODY> 18946</HTML> 18947======= h_config_inabook_to ======= 18948<HTML> 18949<HEAD> 18950<TITLE>To</TITLE> 18951</HEAD> 18952<BODY> 18953<H1>To</H1> 18954 18955Setting the To line will cause the address from the To header line 18956of the message to be checked for in the address book. 18957<P> 18958<End of help on this topic> 18959</BODY> 18960</HTML> 18961======= h_config_inabook_cc ======= 18962<HTML> 18963<HEAD> 18964<TITLE>CC</TITLE> 18965</HEAD> 18966<BODY> 18967<H1>CC</H1> 18968 18969Setting the CC line will cause the address from the CC header line 18970of the message to be checked for in the address book. 18971<P> 18972<End of help on this topic> 18973</BODY> 18974</HTML> 18975======= h_config_role_stat_8bitsubj ======= 18976<HTML> 18977<HEAD> 18978<TITLE>Raw 8-bit in Subject Explained</TITLE> 18979</HEAD> 18980<BODY> 18981<H1>Raw 8-bit in Subject Explained</H1> 18982 18983It seems that lots of unwanted email contains unencoded 8-bit characters 18984in the Subject. 18985Normally, characters with the 8th bit set are not allowed in the Subject 18986header unless they are MIME-encoded. 18987This option gives you a way to match messages that have Subjects that 18988contain unencoded 8-bit characters. 18989<P> 18990This part of the Pattern may have one of three possible values. 18991The default value is "Don't care", which matches any message. 18992The other two values are "Yes", which means the Subject of 18993the message must contain unencoded 8-bit characters (characters with the 18994most significant bit set) 18995in order to be a match; or "No", which 18996means the Subject must <EM>not</EM> 18997contain unencoded 8-bit characters in order to be a match. 18998<P> 18999Look "<A HREF="h_rule_patterns">here</A>" 19000for more information on Patterns. 19001<P> 19002Look <A HREF="h_edit_nav_cmds">here</A> 19003to see the available Editing and Navigation commands. 19004<P> 19005<End of help on this topic> 19006</BODY> 19007</HTML> 19008======= h_config_role_bom ======= 19009<HTML> 19010<HEAD> 19011<TITLE>Beginning of Month</TITLE> 19012</HEAD> 19013<BODY> 19014<H1>Beginning of Month</H1> 19015 19016This option gives you a limited ability to take different actions depending on whether 19017this is the first time Alpine has been run this month or not. 19018Though it would be nice to have such an option available, this is not the 19019same as whether or not this is the first time a particular folder has been 19020opened this month. 19021If you want some action (probably Filtering) to take place in a folder each 19022month, then you will need to be sure that the folder is opened during the 19023first Alpine session of the month in order for this option to be helpful. 19024<P> 19025This part of the Pattern may have one of three possible values. 19026The default value is "Don't care", which matches any message. 19027The other two values are "Yes", which means this is the first 19028time Alpine has been run this month; 19029or "No", which 19030means this is not the first time Alpine has been run this month. 19031<P> 19032Look "<A HREF="h_rule_patterns">here</A>" 19033for more information on Patterns. 19034<P> 19035Here are some technical details. 19036The way that Alpine decides if it is the beginning of the month or not is 19037to compare today's date with the date stored in the 19038<A HREF="h_config_prune_date"><!--#echo var="VAR_last-time-prune-questioned"--></A> 19039variable in the config file. 19040If the month of today's date is later than the month stored in the variable, 19041then this is considered to be the first time you have run Alpine this month, and 19042that turns the Beginning of the Month option on. 19043<P> 19044Look <A HREF="h_edit_nav_cmds">here</A> 19045to see the available Editing and Navigation commands. 19046<P> 19047<End of help on this topic> 19048</BODY> 19049</HTML> 19050======= h_config_role_boy ======= 19051<HTML> 19052<HEAD> 19053<TITLE>Beginning of Year</TITLE> 19054</HEAD> 19055<BODY> 19056<H1>Beginning of Year</H1> 19057 19058This option gives you a limited ability to take different actions depending on whether 19059this is the first time Alpine has been run this year or not. 19060Though it would be nice to have such an option available, this is not the 19061same as whether or not this is the first time a particular folder has been 19062opened this year. 19063If you want some action (probably Filtering) to take place in a folder each 19064year, then you will need to be sure that the folder is opened during the 19065first Alpine session of the year in order for this option to be helpful. 19066<P> 19067This part of the Pattern may have one of three possible values. 19068The default value is "Don't care", which matches any message. 19069The other two values are "Yes", which means this is the first 19070time Alpine has been run this year; 19071or "No", which 19072means this is not the first time Alpine has been run this year. 19073<P> 19074Look "<A HREF="h_rule_patterns">here</A>" 19075for more information on Patterns. 19076<P> 19077Here are some technical details. 19078The way that Alpine decides if it is the beginning of the year or not is 19079to compare today's date with the date stored in the 19080<A HREF="h_config_prune_date"><!--#echo var="VAR_last-time-prune-questioned"--></A> 19081variable in the config file. 19082If the year of today's date is later than the year stored in the variable, 19083then this is considered to be the first time you have run Alpine this year, and 19084that turns the Beginning of the Year option on. 19085<P> 19086Look <A HREF="h_edit_nav_cmds">here</A> 19087to see the available Editing and Navigation commands. 19088<P> 19089<End of help on this topic> 19090</BODY> 19091</HTML> 19092======= h_config_role_inick ======= 19093<HTML> 19094<HEAD> 19095<TITLE>Initialize Values From Role Explained</TITLE> 19096</HEAD> 19097<BODY> 19098<H1>Initialize Values From Role Explained</H1> 19099 19100This is a power user feature. 19101You will usually want to leave this field empty. 19102The value of this field is the nickname of another one of your roles. 19103The Action values from that other role 19104are used as the initial values of the Action items for this role. 19105If you put something in any of the action fields for this role, that will 19106override whatever was in the corresponding field of the initializer role. 19107<P> 19108You might use this field if the "Action" part of one of your roles 19109is something you want to use in more than one role. 19110Instead of filling in those action values again for each role, you 19111may give the nickname of the role where the values are filled in. 19112It's just a shortcut way to define Role Actions. 19113<P> 19114Here's an example to help explain how this works. 19115Suppose you have a role with nickname "role1" and role1 has 19116(among other things) 19117<P> 19118<CENTER><SAMP>Set Reply-To = The Pres <president@example.com></SAMP></CENTER> 19119<P> 19120set. 19121If in "role2" you set "Initialize settings using role" to 19122"role1", then role2 will inherit the Set Reply-To value 19123from role1 by default (and any of the other inheritable action values 19124that are set). 19125So if role2 had 19126<P> 19127<CENTER><SAMP>Set Reply-To = <No Value Set></SAMP></CENTER> 19128<P> 19129defined, the Reply-To used with role2 would be "The Pres <president@example.com>" 19130However, if role2 had 19131<P> 19132<CENTER><SAMP>Set Reply-To = VP <vicepresident@example.com></SAMP></CENTER> 19133<P> 19134defined, then the Reply-To used with role2 would be "VP <vicepresident@example.com>" instead. 19135<P> 19136If you wish, 19137you may choose a nickname from your list of roles by using the 19138"T" command. 19139If the role you are using to initialize also has a role it initializes from, 19140then that initialization happens first. 19141That is, inheritance works as expected with the grandparent and 19142great-grandparent (and so on) roles having the expected effect. 19143<P> 19144Look <A HREF="h_edit_nav_cmds">here</A> 19145to see the available Editing and Navigation commands. 19146<P> 19147<End of help on this topic> 19148</BODY> 19149</HTML> 19150======= h_config_role_setfrom ======= 19151<HTML> 19152<HEAD> 19153<TITLE>Set From Explained</TITLE> 19154</HEAD> 19155<BODY> 19156<H1>Set From Explained</H1> 19157 19158This describes part of the action to be taken if the Pattern for this 19159role is a match. 19160This field consists of a single address that will be used as the From 19161address on the message you are sending. 19162This should be a fully-qualified address like 19163<P> 19164<CENTER><SAMP>Full Name <user@domain></SAMP></CENTER> 19165<P> 19166or just 19167<P> 19168<CENTER><SAMP>user@domain</SAMP></CENTER> 19169<P> 19170If you wish, 19171you may choose an address from your address book with the 19172"T" command. 19173<P> 19174If this is left blank, then your normal From address will be used. 19175<P> 19176You may also find it useful to add the changed From address to the 19177<a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a> 19178configuration option. 19179<P> 19180Look <A HREF="h_edit_nav_cmds">here</A> 19181to see the available Editing and Navigation commands. 19182<P> 19183<End of help on this topic> 19184</BODY> 19185</HTML> 19186======= h_config_role_setreplyto ======= 19187<HTML> 19188<HEAD> 19189<TITLE>Set Reply-To Explained</TITLE> 19190</HEAD> 19191<BODY> 19192<H1>Set Reply-To Explained</H1> 19193 19194This describes part of the action to be taken if the Pattern for this 19195role is a match. 19196This field consists of a single address that will be used as the Reply-To 19197address on the message you are sending. 19198This may be a fully-qualified address like 19199<P> 19200<CENTER><SAMP>Full Name <user@domain></SAMP></CENTER> 19201<P> 19202or just 19203<P> 19204<CENTER><SAMP>user@domain</SAMP></CENTER> 19205<P> 19206If you wish, 19207you may choose an address from your address book with the 19208"T" command. 19209<P> 19210If this is left blank, then there won't be a Reply-To address unless 19211you have configured one specially with the 19212"<A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>" 19213configuration option. 19214<P> 19215Look <A HREF="h_edit_nav_cmds">here</A> 19216to see the available Editing and Navigation commands. 19217<P> 19218<End of help on this topic> 19219</BODY> 19220</HTML> 19221======= h_config_role_setfcc ======= 19222<HTML> 19223<HEAD> 19224<TITLE>Set Fcc Explained</TITLE> 19225</HEAD> 19226<BODY> 19227<H1>Set Fcc Explained</H1> 19228 19229This describes part of the action to be taken if the Pattern for this 19230role is a match. 19231This field consists of a single folder name that will be used in 19232the Fcc field of the message you are sending. 19233You may put anything here that you would normally type into the Fcc 19234field from the composer. 19235<P> 19236In addition, an fcc of "" (two double quotation marks) means 19237no Fcc. 19238<P> 19239A blank field here means that Alpine will use its normal rules for deciding 19240the default value of the Fcc field. 19241For many roles, perhaps most, it may make more sense for you to use the 19242other Alpine facilities for setting the Fcc. 19243In particular, if you want the Fcc to depend on who you are sending the 19244message to then the <A HREF="h_config_fcc_rule">"<!--#echo var="VAR_fcc-name-rule"-->"</A> 19245is probably more useful. 19246In that case, you would want to leave the Fcc field here blank. 19247However, if you have a role that depends on who the message you are replying 19248to was From, or what address that message was sent to; 19249then it might make sense to set the Fcc for that role here. 19250<P> 19251If you wish, 19252you may choose a folder from your folder collections by using the 19253"T" command. 19254<P> 19255Look <A HREF="h_edit_nav_cmds">here</A> 19256to see the available Editing and Navigation commands. 19257<P> 19258<End of help on this topic> 19259</BODY> 19260</HTML> 19261======= h_config_role_usesmtp ======= 19262<HTML> 19263<HEAD> 19264<TITLE>Use SMTP Server Explained</TITLE> 19265</HEAD> 19266<BODY> 19267<H1>Use SMTP Server Explained</H1> 19268 19269This describes part of the action to be taken if the Pattern for this 19270role is a match. 19271If this field has a value, then it will be used as the SMTP server 19272to send mail when this role is being used (unless the SMTP server variable 19273is set in the system-wide fixed configuration file). 19274It has the same semantics as the 19275<A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A> 19276variable in the Setup/Config screen. 19277<P> 19278If you are using this to post from home when you are at home and from 19279work when you are at work you need to be careful about postponing messages. 19280When you postpone a composition that was using a role with this variable 19281set, the SMTP server list will be saved 19282with the postponed composition. 19283It cannot be changed later. 19284Because of this, you may want to make this a list of SMTP servers 19285with the preferred server at the front of the list and alternate servers 19286later in the list. 19287In your "Home" role you would put the home SMTP server first and 19288the work SMTP server last. 19289In your "Work" role you would put the work SMTP server first and 19290the home SMTP server last. 19291Then if you start a composition as "Work", postpone 19292it, and then later resume it from home the work SMTP server will fail but 19293the home SMTP server later in the list will succeed. 19294<P> 19295You may be able to simplify things by making the regular 19296<A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A> 19297variable in the Setup/Config screen a list instead of using roles 19298to set the SMTP server. 19299 19300<P> 19301Look <A HREF="h_edit_nav_cmds">here</A> 19302to see the available Editing and Navigation commands. 19303<P> 19304<End of help on this topic> 19305</BODY> 19306</HTML> 19307======= h_config_role_usenntp ======= 19308<HTML> 19309<HEAD> 19310<TITLE>Use NNTP Server Explained</TITLE> 19311</HEAD> 19312<BODY> 19313<H1>Use NNTP Server Explained</H1> 19314 19315This describes part of the action to be taken if the Pattern for this 19316role is a match. 19317If this field has a value, then it will be used as the NNTP server 19318to post to newsgroups when this role is being used (unless the NNTP server 19319variable 19320is set in the system-wide fixed configuration file). 19321It has the same semantics as the 19322<A HREF="h_config_nntp_server">"<!--#echo var="VAR_nntp-server"-->"</A> 19323variable in the Setup/Config screen. 19324<P> 19325This role setting can facilitate posting to the right nntp server for someone 19326who reads news from various news sources. The feature 19327<A HREF="h_config_predict_nntp_server">"<!--#echo var="FEAT_predict-nntp-server"-->"</A> 19328allows for setting the correct <!--#echo var="VAR_nntp-server"--> without having to individually 19329set a role for that <!--#echo var="VAR_nntp-server"-->, but for greater flexibility, setting 19330nntp servers for roles may be more desirable for some people. 19331<P> 19332If you are using this to post from home when you are at home and from 19333work when you are at work you need to be careful about postponing messages. 19334When you postpone a composition that was using a role with this variable 19335set, the NNTP server list will be saved 19336with the postponed composition. 19337It cannot be changed later. 19338Because of this, you may want to make this a list of NNTP servers 19339with the preferred server at the front of the list and alternate servers 19340later in the list. 19341In your "Home" role you would put the home NNTP server first and 19342the work NNTP server last. 19343In your "Work" role you would put the work NNTP server first and 19344the home NNTP server last. 19345Then if you start a composition as "Work", postpone 19346it, and then later resume it from home the work NNTP server will fail but 19347the home NNTP server later in the list will succeed. 19348<P> 19349You may be able to simplify things by making the regular 19350<A HREF="h_config_nntp_server">"<!--#echo var="VAR_nntp-server"-->"</A> 19351variable in the Setup/Config screen a list instead of using roles 19352to set the NNTP server. 19353 19354<P> 19355Look <A HREF="h_edit_nav_cmds">here</A> 19356to see the available Editing and Navigation commands. 19357<P> 19358<End of help on this topic> 19359</BODY> 19360</HTML> 19361======= h_config_role_setotherhdr ======= 19362<HTML> 19363<HEAD> 19364<TITLE>Set Other Headers Explained</TITLE> 19365</HEAD> 19366<BODY> 19367<H1>Set Other Headers Explained</H1> 19368 19369This describes part of the action to be taken if the Pattern for this 19370role is a match. 19371This field gives you a way to set values for headers besides 19372"From" and "Reply-To". 19373If you want to set either of those, use the specific 19374"Set From" and "Set Reply-To" settings above. 19375<P> 19376This field is similar to the 19377"<A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>" option. 19378Each header you specify here must include the header tag 19379("To:", "Approved:", etc.) 19380and may optionally include a value for that header. 19381In order to see these headers when you compose using this role you 19382must use the rich header 19383<!--chtml if pinemode="function_key"-->(F5) 19384<!--chtml else-->(Ctrl-R)<!--chtml endif--> command. 19385Here's an example that shows how you might set the To address. 19386<P> 19387<CENTER><SAMP>Set Other Hdrs = To: Full Name <user@domain></SAMP></CENTER> 19388<P> 19389Headers set in this way are different from headers set with the 19390<!--#echo var="VAR_customized-hdrs"--> option in that the value you give for a header here 19391will replace any value that already exists. 19392For example, if you are Replying to a message there will already be at 19393least one address in the To header (the address you are Replying to). 19394However, if you Reply using a role that sets the To header, that role's 19395To header value will be used instead. 19396<P> 19397Limitation: Because commas are used to separate the list of 19398Other Headers, it is not possible to have the value of a 19399header contain a comma; 19400nor is there currently an "escape" mechanism provided 19401to make this work. 19402<P> 19403Look <A HREF="h_edit_nav_cmds">here</A> 19404to see the available Editing and Navigation commands. 19405<P> 19406<End of help on this topic> 19407</BODY> 19408</HTML> 19409======= h_config_role_setlitsig ======= 19410<HTML> 19411<HEAD> 19412<TITLE>Set Literal Signature Explained</TITLE> 19413</HEAD> 19414<BODY> 19415<H1>Set Literal Signature Explained</H1> 19416 19417This describes part of the action to be taken if the Pattern for this 19418role is a match. 19419This field contains the actual text for your signature, as opposed to 19420the name of a file containing your signature. 19421If this is defined it takes precedence over any value set in the 19422"Set Signature" field. 19423<P> 19424This is simply a different way to store the signature. 19425The signature is stored inside your Alpine configuration file instead of in 19426a separate file. 19427Tokens work the same way they do with 19428<A HREF="h_config_role_setsig">Set Signature</A>, so refer to the 19429help text there for more information. 19430<P> 19431 19432The two character sequence \n (backslash followed by 19433the character n) will be used to signify a line-break in your signature. 19434You don't have to enter the \n, but it will be visible in the 19435CHANGE THIS ROLE RULE window after you are done editing the signature. 19436<P> 19437Look <A HREF="h_edit_nav_cmds">here</A> 19438to see the available Editing and Navigation commands. 19439<P> 19440<End of help on this topic> 19441</BODY> 19442</HTML> 19443======= h_config_role_setsig ======= 19444<HTML> 19445<HEAD> 19446<TITLE>Set Signature Explained</TITLE> 19447</HEAD> 19448<BODY> 19449<H1>Set Signature Explained</H1> 19450 19451This describes part of the action to be taken if the Pattern for this 19452role is a match. 19453<P> 19454If either the default <A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A> 19455option from Setup/Config 19456or the "Set LiteralSig" option for this role are defined, 19457then this option will be ignored. 19458You can tell that that is the case because the value of this 19459option will show up as 19460<P> 19461<CENTER><SAMP><Ignored: using LiteralSig instead></SAMP></CENTER> 19462<P> 19463You may either use all Literal Signatures (signatures stored in your 19464configuration file) throughout Alpine, or all signature files. 19465You can't mix the two. 19466<P> 19467This field consists of a filename that will be used as the signature 19468file when using this role. 19469<P> 19470If the filename is followed by a vertical bar (|) then instead 19471of reading the contents of the file the file is assumed to be a 19472program that will produce the text to be used on its standard output. 19473The program can't have any arguments and doesn't receive any input from Alpine, 19474but the rest of the processing works as if the contents came from a file. 19475<P> 19476Instead of storing the data in a local file, the 19477signature data may be stored remotely in an IMAP folder. 19478In order to do this, 19479you must use a remote name for the signature. 19480A remote signature name might look like: 19481<P> 19482<CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/sig3</SAMP></CENTER> 19483<P> 19484 19485The syntax used here is the same as the syntax used for a remote 19486<A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A>. 19487Note that you may not access an existing signature file remotely, 19488you have to create a new <EM>folder</EM> that contains the signature data. 19489If the name you use here for the signature data is a remote name, then when 19490you edit the file using the "F" command the data will 19491be saved remotely in the folder. 19492You aren't required to do anything special to create the folder, it 19493gets created if you use a remote name. 19494 19495<P> 19496If you type "F" you may edit the contents of the file (as opposed to 19497the name of the file) you have specified. 19498If you type "T" you may use a browser to choose an existing filename. 19499<P> 19500Besides containing regular text, a signature file may also 19501contain (or a signature program may produce) tokens that are replaced with text 19502that depends on the message you are replying to or forwarding. 19503The tokens all look like _word_ (a word surrounded by underscores). 19504For example, if the token 19505<P> 19506<CENTER><SAMP>_DATE_</SAMP></CENTER> 19507<P> 19508is included in the text of the signature file, then when you reply to 19509or forward a message, the token will be replaced with the actual date 19510the message you are replying to or forwarding was sent. 19511<P> 19512If you use a role that has a signature file for a plain composition 19513(that is, not a reply or forward) then there is no original message, so 19514any tokens that depend on the message will be replaced with nothing. 19515So if you want a signature file to be useful for new compositions it 19516shouldn't include any of the tokens that depend on the message being 19517replied to or forwarded. 19518<P> 19519The list of available tokens is 19520<A HREF="h_index_tokens">here</A>. 19521<P> 19522Actually, for the adventurous, there is a way to conditionally include text based 19523on whether or not a token would result in specific replacement text. 19524For example, you could include some text based on whether or not 19525the _NEWS_ token would result in any newsgroups if it was used. 19526It's explained in detail 19527<A HREF="h_reply_token_conditionals">here</A>. 19528<P> 19529In the very unlikely event that you want to include a literal token in 19530a signature file, you must precede it with a backslash character. 19531For example, to include the literal text _DATE_ you must actually use 19532\_DATE_. 19533It is not possible to have a literal backslash followed by an expanded token. 19534<P> 19535A blank field here means that Alpine will use its normal rules for deciding 19536which file (if any) to use for the signature file. 19537<P> 19538An alternate method for storing the signature is available in 19539<A HREF="h_config_role_setlitsig">Set Literal Signature</A>. 19540<P> 19541Look <A HREF="h_edit_nav_cmds">here</A> 19542to see the available Editing and Navigation commands. 19543<P> 19544<End of help on this topic> 19545</BODY> 19546</HTML> 19547======= h_config_role_settempl ======= 19548<HTML> 19549<HEAD> 19550<TITLE>Set Template Explained</TITLE> 19551</HEAD> 19552<BODY> 19553<H1>Set Template Explained</H1> 19554 19555This describes part of the action to be taken if the Pattern for this 19556role is a match. 19557This field consists of a filename that will be used as the template 19558file when using this role. 19559The template file is a file that is included at the top of the message you 19560are composing. 19561<P> 19562If the filename is followed by a vertical bar (|) then instead 19563of reading the contents of the file the file is assumed to be a 19564program that will produce the text to be used on its standard output. 19565The program can't have any arguments and doesn't receive any input from Alpine, 19566but the rest of the processing works as if the contents came from a file. 19567<P> 19568Instead of storing the data in a local file, the 19569template may be stored remotely in an IMAP folder. 19570In order to do this, 19571you must use a remote name for the template. 19572A remote template name might look like: 19573<P> 19574<CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/templ3</SAMP></CENTER> 19575<P> 19576 19577The syntax used here is the same as the syntax used for a remote 19578<A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A>. 19579Note that you may not access an existing template file remotely, 19580you have to create a new <EM>folder</EM> that contains the template data. 19581If the name you use here for the template is a remote name, then when 19582you edit the file using the "F" command the data will 19583be saved remotely in the folder. 19584You aren't required to do anything special to create the folder, it 19585gets created if you use a remote name. 19586<P> 19587If you type "F" you may edit the contents of the file (as opposed to 19588the name of the file) you have specified. 19589If you type "T" you may use a browser to choose an existing filename. 19590<P> 19591Besides containing regular text, the template file may also 19592contain (or a template file program may produce) tokens that are replaced with text 19593that depends on the message you are replying to or forwarding. 19594The tokens all look like _word_ (a word surrounded by underscores). 19595For example, if the token 19596<P> 19597<CENTER><SAMP>_DATE_</SAMP></CENTER> 19598<P> 19599is included in the text of the template file, then when you reply to 19600or forward a message, the token will be replaced with the actual date 19601the message you are replying to or forwarding was sent. 19602<P> 19603If you use a role that has a template file for a plain composition 19604(that is, not a reply or forward) then there is no original message, so 19605any tokens that depend on the message will be replaced with nothing. 19606So if you want a template file to be useful for new compositions it 19607shouldn't include any of the tokens that depend on the message being 19608replied to or forwarded. 19609<P> 19610The list of available tokens is 19611<A HREF="h_index_tokens">here</A>. 19612<P> 19613Actually, for the adventurous, there is a way to conditionally include text based 19614on whether or not a token would result in specific replacement text. 19615For example, you could include some text based on whether or not 19616the _NEWS_ token would result in any newsgroups if it was used. 19617It's explained in detail 19618<A HREF="h_reply_token_conditionals">here</A>. 19619<P> 19620In the very unlikely event that you want to include a literal token in 19621a template file, you must precede it with a backslash character. 19622For example, to include the literal text _DATE_ you must actually use 19623\_DATE_. 19624It is not possible to have a literal backslash followed by an expanded token. 19625<P> 19626A blank template field means that Alpine will not use a template file when 19627this role is being used. 19628<P> 19629Look <A HREF="h_edit_nav_cmds">here</A> 19630to see the available Editing and Navigation commands. 19631<P> 19632<End of help on this topic> 19633</BODY> 19634</HTML> 19635======= h_config_filt_stat_imp ======= 19636<HTML> 19637<HEAD> 19638<TITLE>Set Important Status Explained</TITLE> 19639</HEAD> 19640<BODY> 19641<H1>Set Important Status Explained</H1> 19642 19643This describes part of the action to be taken if the Pattern for this 19644filter is a match. 19645If set to "Don't change it" then this does nothing. 19646If set to "Set this state" then the Important flag is set 19647for the matching message. 19648If set to "Clear this state" then the Important flag is cleared 19649for the matching message. 19650The important flag usually causes an asterisk to show up in the MESSAGE 19651INDEX. 19652It may also be useful when selecting a set of messages 19653with the Select command. 19654<P> 19655Look <A HREF="h_edit_nav_cmds">here</A> 19656to see the available Editing and Navigation commands. 19657<P> 19658<End of help on this topic> 19659</BODY> 19660</HTML> 19661======= h_config_filt_stat_new ======= 19662<HTML> 19663<HEAD> 19664<TITLE>Set New Status Explained</TITLE> 19665</HEAD> 19666<BODY> 19667<H1>Set New Status Explained</H1> 19668 19669This describes part of the action to be taken if the Pattern for this 19670filter is a match. 19671If set to "Don't change it" then this does nothing. 19672If set to "Set this state" then the 19673matching message is marked New. 19674If set to "Clear this state" then the 19675matching message is marked Seen. 19676<P> 19677Look <A HREF="h_edit_nav_cmds">here</A> 19678to see the available Editing and Navigation commands. 19679<P> 19680<End of help on this topic> 19681</BODY> 19682</HTML> 19683======= h_config_filt_stat_ans ======= 19684<HTML> 19685<HEAD> 19686<TITLE>Set Answered Status Explained</TITLE> 19687</HEAD> 19688<BODY> 19689<H1>Set Answered Status Explained</H1> 19690 19691This describes part of the action to be taken if the Pattern for this 19692filter is a match. 19693If set to "Don't change it" then this does nothing. 19694If set to "Set this state" then the Answered flag is set 19695for the matching message. 19696If set to "Clear this state" then the Answered flag is cleared 19697for the matching message. 19698<P> 19699Look <A HREF="h_edit_nav_cmds">here</A> 19700to see the available Editing and Navigation commands. 19701<P> 19702<End of help on this topic> 19703</BODY> 19704</HTML> 19705======= h_config_filt_stat_del ======= 19706<HTML> 19707<HEAD> 19708<TITLE>Set Deleted Status Explained</TITLE> 19709</HEAD> 19710<BODY> 19711<H1>Set Deleted Status Explained</H1> 19712 19713This describes part of the action to be taken if the Pattern for this 19714filter is a match. 19715If set to "Don't change it" then this does nothing. 19716If set to "Set this state" then the 19717matching message is marked Deleted. 19718If set to "Clear this state" then the 19719matching message is marked UnDeleted. 19720<P> 19721You should not use this option unless you are prepared to have matching 19722messages expunged from the folder permanently. 19723For example, if you type the Expunge command, this filter is applied 19724before the expunge, so matching messages will be marked Deleted and then 19725will be permanently expunged from the folder. 19726However, since the index isn't redrawn in between the time that the message 19727is marked Deleted and the time that you are asked to expunge, the only 19728indication that you are expunging the message comes in the number of messages 19729being expunged. 19730The same thing may happen when you close a folder. 19731It is also possible that an expunge not initiated by you will 19732delete matching messages. 19733<P> 19734Look <A HREF="h_edit_nav_cmds">here</A> 19735to see the available Editing and Navigation commands. 19736<P> 19737<End of help on this topic> 19738</BODY> 19739</HTML> 19740======= h_config_role_scoreval ======= 19741<HTML> 19742<HEAD> 19743<TITLE>Score Value Explained</TITLE> 19744</HEAD> 19745<BODY> 19746<H1>Score Value Explained</H1> 19747 19748A message's score is the sum of the Score Values from all of the Scoring rules 19749with Patterns that match the message. 19750The value you give here is the Score Value associated with this rule. 19751A Score Value is an integer between -100 and 100, with the default 19752value of zero. 19753<P> 19754Alternatively, if the 19755<A HREF="h_config_role_scorehdrtok">"Score From Header"</A> 19756field is defined 19757(on the line right below the "Score Value" field) 19758then the "Score Value" is ignored and 19759the "Score From Header" field is used instead. 19760<P> 19761Look <A HREF="h_edit_nav_cmds">here</A> 19762to see the available Editing and Navigation commands. 19763<P> 19764<End of help on this topic> 19765</BODY> 19766</HTML> 19767======= h_config_role_scorehdrtok ======= 19768<HTML> 19769<HEAD> 19770<TITLE>Score Value From Header Explained</TITLE> 19771</HEAD> 19772<BODY> 19773<H1>Score Value From Header Explained</H1> 19774 19775This option provides a way to use a number that appears in the headers of your 19776messages as the message's score, or as a component of that score. 19777If this field is defined then it is used instead of the "Score Value". 19778The idea behind this option is that there may be a score embedded in the 19779headers of messages that has already been calculated outside of Alpine. 19780For example, messages delivered to you may contain an "X-Spam" header and 19781somewhere in that header there is a score. 19782<P> 19783The value for this option is the name of the header followed by parentheses 19784with two arguments inside: 19785<P> 19786<CENTER><SAMP>HeaderName(field_number,field_separators)</SAMP></CENTER> 19787<P> 19788No space is allowed between the comma and the start of the field_separators. 19789It would be interpreted as the first separator if it was there. 19790Field 0 is the whole line, Field 1 is the data up to the first separator, Field 2 19791starts after that and goes to the second separator, and so on. 19792It's easier to explain with examples. 19793<P> 19794<CENTER><SAMP>X-Spam(2," ")</SAMP></CENTER> 19795<P> 19796In the above example the header that is used is the "X-Spam" header. 19797The value of that header (the part after the colon and the space) is split 19798into fields separated by spaces. 19799<P> 19800<CENTER><SAMP>Field1 <space> Field2 <space> Field3 ...</SAMP></CENTER> 19801<P> 19802The second field is selected and converted to an integer. It only makes sense 19803if Field2 really is an integer. 19804<P> 19805Here's an example of a SpamAssassin header. 19806The exact look of the header will vary, but if your incoming mail 19807contains headers that look like the following 19808<P> 19809<CENTER><SAMP>X-Spam-Status: Yes, hits=10.6 tagged_above=-999.0 required=7.0 tests=BAYE...</SAMP></CENTER> 19810<P> 19811you might want to use the hits value as a score. 19812Since the score is an integer value you can't make use of the decimal part of 19813the number, but 19814you might split off the hits=10 part as a score by using the characters "=" 19815and "." as your separators. 19816<P> 19817<CENTER><SAMP>X-Spam-Status(2,"=.")</SAMP></CENTER> 19818<P> 19819The first field starts with the Y in Yes and goes until the "=" after 19820hits. 19821The second field is "10" so the score value would be 10. 19822<P> 19823Another example we've seen has headers that look like 19824<P> 19825<CENTER><SAMP>X-Spam: Gauge=IIIIIII, Probability=7%, Report=...</SAMP></CENTER> 19826<P> 19827Because there are two equals before the 7% the value 19828<P> 19829<CENTER><SAMP>X-Spam(3,"=%")</SAMP></CENTER> 19830<P> 19831should capture the probability as the score. 19832<P> 19833The Score From Header scoring value actually works just like the 19834regular Score Value in that the rest of the pattern has to match before 19835it is used and the scores from all the different scoring rules that 19836match for a particular message are added together. 19837When using the Score From Header method it may (or may not) make sense to 19838use only a single scoring rule with a pattern that matches every message. 19839<P> 19840Look <A HREF="h_edit_nav_cmds">here</A> 19841to see the available Editing and Navigation commands. 19842<P> 19843<End of help on this topic> 19844</BODY> 19845</HTML> 19846======= h_config_role_replyuse ======= 19847<HTML> 19848<HEAD> 19849<TITLE>Reply Use Explained</TITLE> 19850</HEAD> 19851<BODY> 19852<H1>Reply Use Explained</H1> 19853 19854This option determines how this particular role will be used when Replying 19855to a message. 19856There are three possible values for this option. 19857The value "Never" 19858means that this role will not be a candidate for use when Replying. 19859The role's Pattern will not be checked for a match, however the role will 19860be available to be manually switched to if there is a confirmation prompt. 19861<P> 19862 19863The options "With confirmation" and "Without confirmation" 19864mean that you do want to consider this role when Replying. 19865For either of these settings, the role's Pattern will be compared with 19866the message being replied to. 19867If there is a match then this role will either be used without confirmation 19868or will be the default when confirmation is asked for, depending on 19869which of the two options is selected. 19870If confirmation is requested, you will also have a chance to 19871manually change the role to any one of your other roles. 19872<P> 19873 19874You won't be prompted for confirmation if none of your role Patterns 19875match the message being replied to. 19876This is independent of the value of the current option. 19877The <A HREF="h_config_confirm_role"><!--#echo var="FEAT_confirm-role-even-for-default"--></A> 19878feature may be used to change this behavior. 19879<P> 19880<End of help on this topic> 19881</BODY> 19882</HTML> 19883======= h_config_role_forwarduse ======= 19884<HTML> 19885<HEAD> 19886<TITLE>Forward Use Explained</TITLE> 19887</HEAD> 19888<BODY> 19889<H1>Forward Use Explained</H1> 19890 19891This option determines how this particular role will be used when Forwarding 19892a message. 19893There are three possible values for this option. 19894The value "Never" 19895means that this role will not be a candidate for use when Forwarding. 19896The role's Pattern will not be checked for a match, however the role will 19897be available to be manually switched to if there is a confirmation prompt. 19898<P> 19899 19900The options "With confirmation" and "Without confirmation" 19901mean that you do want to consider this role when Forwarding. 19902For either of these settings, the role's Pattern will be compared with 19903the message being forwarded. 19904If there is a match then this role will either be used without confirmation 19905or will be the default when confirmation is asked for, depending on 19906which of the two options is selected. 19907If confirmation is requested, you will also have a chance to 19908manually change the role to any one of your other roles. 19909<P> 19910 19911You won't be prompted for confirmation if none of your role Patterns 19912match the message being forwarded. 19913This is independent of the value of the current option. 19914The <A HREF="h_config_confirm_role"><!--#echo var="FEAT_confirm-role-even-for-default"--></A> 19915feature may be used to change this behavior. 19916<P> 19917<End of help on this topic> 19918</BODY> 19919</HTML> 19920======= h_config_role_composeuse ======= 19921<HTML> 19922<HEAD> 19923<TITLE>Compose Use Explained</TITLE> 19924</HEAD> 19925<BODY> 19926<H1>Compose Use Explained</H1> 19927 19928This option determines how this particular role will be used when Composing 19929a new message using the "Compose" command. 19930This does not affect what happens when using the "Role" command 19931to compose a new message. 19932The "Role" command allows you to select a role from all of the 19933roles you have defined, regardless of what Uses you've assigned to those 19934roles. 19935<P> 19936 19937There are three possible values for this option. 19938The value "Never" 19939means that this role will not be a candidate for use when Composing. 19940The role's Current Folder Type will not be checked for a match, however the role 19941will be available to be manually switched to if there is a confirmation prompt. 19942<P> 19943 19944The options "With confirmation" and "Without confirmation" 19945mean that you do want to consider this role when Composing. 19946For either of these settings, 19947the role's Current Folder Type will be checked (since there is no message 19948to compare with, the rest of the Pattern is considered a match). 19949If there is a match then this role will either be used without confirmation 19950or will be the default when confirmation is asked for, depending on 19951which of the two options is selected. 19952If confirmation is requested, you will also have a chance to 19953manually change the role to any one of your other roles. 19954<P> 19955 19956When using the Compose command the role checking is a little different 19957because there is no message being replied to or forwarded. 19958Because of this the Current Folder Type is checked but the header pattern 19959fields, the AllText pattern, the BodyText pattern, and the Score Interval are all ignored. 19960A role is considered to be a match if it is a candidate for Compose Use and 19961its Current Folder Type matches the currently open folder. 19962This could be useful if you want to set a role based on the folder you 19963are reading, or the type of folder you are reading. 19964<P> 19965 19966You won't be prompted for confirmation if none of your role Patterns 19967are a match. 19968This is independent of the value of the current option. 19969The <A HREF="h_config_confirm_role"><!--#echo var="FEAT_confirm-role-even-for-default"--></A> 19970feature may be used to change this behavior. 19971<P> 19972<End of help on this topic> 19973</BODY> 19974</HTML> 19975======= h_config_filter_folder ======= 19976<HTML> 19977<HEAD> 19978<TITLE>Filter Folder Explained</TITLE> 19979</HEAD> 19980<BODY> 19981<H1>Filter Folder Explained</H1> 19982 19983When the Filter Action is set to "Move", 19984the folder or folders specified here will be used to store messages matching 19985the provided pattern. 19986 19987<P> 19988If you set the Filter Action to "Move" you must give a folder name 19989here. 19990 19991<P> 19992If you wish, 19993you may choose a folder from your folder collections by using the 19994"T" command. 19995<P> 19996Besides regular text, the folder name may also contain 19997tokens that are replaced with text representing the current date 19998when you run Alpine. 19999For example, if the folder name you use is 20000<P> 20001<CENTER><SAMP>abc-_CURYEAR_-_CURMONTHABBREV_</SAMP></CENTER> 20002<P> 20003that is replaced with something like 20004<P> 20005<CENTER><SAMP>abc-2004-oct</SAMP></CENTER> 20006<P> 20007Or, 20008<P> 20009<CENTER><SAMP>abc-_CURYEAR2DIGIT_-_CURMONTH2DIGIT_</SAMP></CENTER> 20010<P> 20011becomes 20012<P> 20013<CENTER><SAMP>abc-04-10</SAMP></CENTER> 20014<P> 20015The token names must be surrounded by underscores in order to be recognized 20016as tokens. 20017The tokens that may be used are those that are derived from the current date. 20018They're listed near the bottom of the list of tokens give 20019<A HREF="h_index_tokens">here</A>. 20020<P> 20021Look "<A HREF="h_rule_patterns">here</A>" 20022for more information on Patterns. 20023<P> 20024Look <A HREF="h_edit_nav_cmds">here</A> 20025to see the available Editing and Navigation commands. 20026<P> 20027<End of help on this topic> 20028</BODY> 20029</HTML> 20030======= h_config_filter_kw_set ======= 20031<HTML> 20032<HEAD> 20033<TITLE>Set These Keywords Explained</TITLE> 20034</HEAD> 20035<BODY> 20036<H1>Set These Keywords Explained</H1> 20037 20038This describes part of the action to be taken if the Pattern for this 20039filter is a match. 20040Read a little about keywords in the help text for the 20041<A HREF="h_common_flag">Flag</A> command. 20042This option is a list of keywords that will be Set when there is a match. 20043If you wish, you may choose keywords from the list of keywords you have 20044defined with the "T" command. 20045You may add new keywords by defining them in the 20046<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen. 20047If you have given a keyword a nickname when configuring it, 20048that nickname may be used instead of the actual keyword. 20049 20050<P> 20051Look <A HREF="h_edit_nav_cmds">here</A> 20052to see the available Editing and Navigation commands. 20053<P> 20054<End of help on this topic> 20055</BODY> 20056</HTML> 20057======= h_config_filter_kw_clr ======= 20058<HTML> 20059<HEAD> 20060<TITLE>Clear These Keywords Explained</TITLE> 20061</HEAD> 20062<BODY> 20063<H1>Clear These Keywords Explained</H1> 20064 20065This describes part of the action to be taken if the Pattern for this 20066filter is a match. 20067Read a little about keywords in the help text for the 20068<A HREF="h_common_flag">Flag</A> command. 20069This option is a list of keywords that will be Cleared when there is a match. 20070If you wish, you may choose keywords from the list of keywords you have 20071defined with the "T" command. 20072You may add new keywords by defining them in the 20073<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen. 20074If you have given a keyword a nickname when configuring it, 20075that nickname may be used instead of the actual keyword. 20076 20077<P> 20078Look <A HREF="h_edit_nav_cmds">here</A> 20079to see the available Editing and Navigation commands. 20080<P> 20081<End of help on this topic> 20082</BODY> 20083</HTML> 20084======= h_index_tokens ======= 20085<HTML> 20086<HEAD> 20087<TITLE>Tokens for Index and Replying</TITLE> 20088</HEAD> 20089<BODY> 20090 20091This set of special tokens may be used in the 20092<A HREF="h_config_index_format">"<!--#echo var="VAR_index-format"-->"</A> option, 20093in the <A HREF="h_config_reply_intro">"<!--#echo var="VAR_reply-leadin"-->"</A> option, 20094in signature files, 20095in template files used in 20096<A HREF="h_rules_roles">"roles"</A>, and in the folder name 20097that is the target of a Filter Rule. 20098Some of them aren't available in all situations. 20099<P> 20100The tokens are used as they appear below for the "<!--#echo var="VAR_index-format"-->" 20101option, but they must be surrounded by underscores for the 20102"<!--#echo var="VAR_reply-leadin"-->" option, in signature and template files, 20103and in the target of Filter Rules. 20104<P> 20105<P> 20106 20107<H1><EM>Tokens Available for all Cases (except Filter Rules)</EM></H1> 20108 20109<DL> 20110<DT>SUBJECT</DT> 20111<DD> 20112This token represents the Subject the sender gave the message. 20113Alternatives for use in the index screen are SHORTSUBJECT, 20114SUBJKEY, SHORTSUBJKEY, SUBJKEYINIT, SHORTSUBJKEYINIT, SUBJECTTEXT, 20115SUBJKEYTEXT, and SUBJKEYINITTEXT. 20116You may color the subject text in the MESSAGE INDEX screen differently by using the 20117<A HREF="h_config_index_subject_color">Index Subject Color</A> and the 20118<A HREF="h_config_index_opening_color">Index Opening Color</A> 20119options available from 20120the <A HREF="h_color_setup">Setup Kolor</A> screen. 20121</DD> 20122 20123<DT>FROM</DT> 20124<DD> 20125This token represents the personal name (or email address if the name 20126is unavailable) of the person specified in the message's "From:" 20127header field. 20128You may color the from text in the MESSAGE INDEX screen differently by using the 20129<A HREF="h_config_index_from_color">Index From Color</A> 20130option available from 20131the <A HREF="h_color_setup">Setup Kolor</A> screen. 20132</DD> 20133 20134<DT>ADDRESS</DT> 20135<DD> 20136This is similar to the "FROM" token, only it is always the 20137email address, never the personal name. 20138For example, "mailbox@domain". 20139</DD> 20140 20141<DT>MAILBOX</DT> 20142<DD> 20143This is the same as the "ADDRESS" except that the 20144domain part of the address is left off. 20145For example, "mailbox". 20146</DD> 20147 20148<DT>SENDER</DT> 20149<DD> 20150This token represents the personal name (or email address) of the person 20151listed in the message's "Sender:" header field. 20152</DD> 20153 20154<DT>TO</DT> 20155<DD> 20156This token represents the personal names (or email addresses if the names 20157are unavailable) of the persons specified in the 20158message's "To:" header field. 20159</DD> 20160 20161<DT>NEWSANDTO</DT> 20162<DD> 20163This token represents the newsgroups from the 20164message's "Newsgroups:" header field <EM>and</EM> 20165the personal names (or email addresses if the names 20166are unavailable) of the persons specified in the 20167message's "To:" header field. 20168</DD> 20169 20170<DT>TOANDNEWS</DT> 20171<DD> 20172Same as "NEWSANDTO" except in the opposite order. 20173</DD> 20174 20175<DT>NEWS</DT> 20176<DD> 20177This token represents the newsgroups from the 20178message's "Newsgroups:" header field. 20179</DD> 20180 20181<DT>CC</DT> 20182<DD> 20183This token represents the personal names (or email addresses if the names 20184are unavailable) of the persons specified in the 20185message's "Cc:" header field. 20186</DD> 20187 20188<DT>RECIPS</DT> 20189<DD> 20190This token represents the personal names (or email addresses if the names 20191are unavailable) of the persons specified in both the 20192message's "To:" header field and 20193the message's "Cc:" header field. 20194</DD> 20195 20196<DT>NEWSANDRECIPS</DT> 20197<DD> 20198This token represents the newsgroups from the 20199message's "Newsgroups:" header field <EM>and</EM> 20200the personal names (or email addresses if the names 20201are unavailable) of the persons specified in the 20202message's "To:" and "Cc:" header fields. 20203</DD> 20204 20205<DT>RECIPSANDNEWS</DT> 20206<DD> 20207Same as "NEWSANDRECIPS" except in the opposite order. 20208</DD> 20209 20210<DT>INIT</DT> 20211<DD> 20212This token represents the initials from the personal name 20213of the person specified in the message's "From:" 20214header field. 20215If there is no personal name, it is blank. 20216</DD> 20217 20218<DT>DATE</DT> 20219<DD> 20220This token represents the date on which the message was sent, according 20221to the "Date" header field. 20222It has the format MMM DD. For example, "Oct 23". 20223The feature 20224<A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A>, 20225which adjusts for the timezone the message was sent from, 20226may have an effect on the value of this token as well as the values of 20227all of the other DATE or TIME tokens. 20228Some of the DATE and TIME tokens are displayed in a locale-specific 20229way unless the option 20230<A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A> is set. 20231</DD> 20232 20233<DT>SMARTDATE</DT> 20234<DD> 20235This token represents the date on which the message was sent, according 20236to the "Date" header field. 20237It is "Today" if the message was sent today, 20238"Yesterday" for yesterday, 20239"Wednesday" if it was last Wednesday, and so on. If the 20240message is from last year and is more than six months old it includes the year, as well. 20241See the SMARTDATE alternatives below, as well. 20242</DD> 20243 20244<DT>SMARTTIME</DT> 20245<DD> 20246This token represents the most relevant elements of the date on which 20247the message was sent (according to the "Date" header field), 20248in a compact form. If the message was sent today, only the time is used 20249(e.g. "9:22am", "10:07pm"); if it was sent during 20250the past week, the day of the week and the hour are used 20251(e.g. "Wed09am", "Thu10pm"); other dates are 20252given as date, month, and year (e.g. "23Aug00", 20253"9Apr98"). 20254</DD> 20255 20256<DT>SMARTTIME24</DT> 20257<DD> 20258This token has the structure "day hour:minute" 20259(e.g. "Sun 19:03") for messages dated less than a week 20260from the current date, or "month day" (e.g. 20261"Nov 23") for messages dated less than 6 months 20262ago, or "day/month/year" (e.g "06/Jan/16") 20263for messages dated more than 6 months ago. It uses 9 characters 20264of the width of the screen, and it left aligned. 20265</DD> 20266 20267<DT>SMARTDATETIME</DT> 20268<DD> 20269This is a combination of SMARTDATE and SMARTTIME. 20270It is SMARTDATE unless the SMARTDATE value is "Today", in which 20271case it is SMARTTIME. 20272See the SMARTDATETIME alternatives below, as well. 20273</DD> 20274 20275<DT>DATEISO</DT> 20276<DD> 20277This token represents the date on which the message was sent, according 20278to the "Date" header field. 20279It has the format YYYY-MM-DD. For example, "1998-10-23". 20280</DD> 20281 20282<DT>SHORTDATEISO</DT> 20283<DD> 20284This token represents the date on which the message was sent, according 20285to the "Date" header field. 20286It has the format YY-MM-DD. For example, "98-10-23". 20287</DD> 20288 20289<DT>SHORTDATE1</DT> 20290<DD> 20291This token represents the date on which the message was sent, according 20292to the "Date" header field. 20293It has the format MM/DD/YY. For example, "10/23/98". 20294</DD> 20295 20296<DT>SHORTDATE2</DT> 20297<DD> 20298This token represents the date on which the message was sent, according 20299to the "Date" header field. 20300It has the format DD/MM/YY. For example, "23/10/98". 20301</DD> 20302 20303<DT>SHORTDATE3</DT> 20304<DD> 20305This token represents the date on which the message was sent, according 20306to the "Date" header field. 20307It has the format DD.MM.YY. For example, "23.10.98". 20308</DD> 20309 20310<DT>SHORTDATE4</DT> 20311<DD> 20312This token represents the date on which the message was sent, according 20313to the "Date" header field. 20314It has the format YY.MM.DD. For example, "98.10.23". 20315</DD> 20316 20317<DT>LONGDATE</DT> 20318<DD> 20319This token represents the date on which the message was sent, according 20320to the "Date" header field. 20321It has the format MMM DD, YYYY. For example, "Oct 23, 1998". 20322</DD> 20323 20324<DT>SMARTDATE alternatives</DT> 20325<DD> 20326There are several versions of SMARTDATE that are all the same except 20327for the way they format dates far in the past. 20328SMARTDATE formats the date using the information from your locale settings 20329to format the date string. It may end up formatting dates so that they look 20330like DATEISO tokens, or SHORTDATE2 tokens, or something else entirely. 20331The feature 20332<A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A> 20333may have an effect on the values of these tokens. 20334If you want more control you may use one of the following. 20335 <DL> 20336 <DT>SMARTDATE</DT> <DD>If the option 20337<A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A> is not set 20338then this will be locale specific. Control this with the 20339LC_TIME locale setting on a UNIX system. On Windows 20340the Regional Options control panel may be used to set the Short date 20341format. At the programming level, the strftime routine is what Alpine 20342uses to print the date. 20343If the <!--#echo var="FEAT_disable-index-locale-dates"--> option is set then this is equivalent 20344to SMARTDATES1.</DD> 20345 <DT>SMARTDATEISO</DT> <DD>DATEISO format. See text above.</DD> 20346 <DT>SMARTDATESHORTISO</DT> <DD>SHORTDATEISO format.</DD> 20347 <DT>SMARTDATES1</DT> <DD>SHORTDATE1 format.</DD> 20348 <DT>SMARTDATES2</DT> <DD>SHORTDATE2 format.</DD> 20349 <DT>SMARTDATES3</DT> <DD>SHORTDATE3 format.</DD> 20350 <DT>SMARTDATES4</DT> <DD>SHORTDATE4 format.</DD> 20351 </DL> 20352</DD> 20353 20354<DT>SMARTDATETIME alternatives</DT> 20355<DD> 20356There are several versions of SMARTDATETIME that are all very similar. 20357The ones that end in 24 use a 24-hour clock for Today's messages instead 20358of a 12-hour clock. 20359The other variation is 20360for the way they format dates far in the past. 20361SMARTDATETIME and SMARTDATETIME24 format the date using the information from your locale settings 20362to format the date string. It may end up formatting dates so that they look 20363like DATEISO tokens, or SHORTDATE2 tokens, or something else entirely. 20364The feature 20365<A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A> 20366may have an effect on the values of these tokens. 20367The possible choices are: 20368 <DL> 20369 <DT>SMARTDATETIME</DT> <DD>If the option 20370<A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A> is not set 20371then this will be locale specific. Control this with the 20372LC_TIME locale setting on a UNIX system. On Windows 20373the Regional Options control panel may be used to set the Short date 20374format. At the programming level, the strftime routine is what Alpine 20375uses to print the date. 20376If the <!--#echo var="FEAT_disable-index-locale-dates"--> option is set then this is equivalent 20377to SMARTDATETIMES1.</DD> 20378 <DT>SMARTDATETIME24</DT> <DD>Use TIME24 for Today</DD> 20379 <DT>SMARTDATETIMEISO</DT> <DD>DATEISO format. See text above.</DD> 20380 <DT>SMARTDATETIMEISO24</DT> <DD>Use TIME24 for Today</DD> 20381 <DT>SMARTDATETIMESHORTISO</DT> <DD>SHORTDATEISO format.</DD> 20382 <DT>SMARTDATETIMESHORTISO24</DT> <DD>Use TIME24 for Today</DD> 20383 <DT>SMARTDATETIMES1</DT> <DD>SHORTDATE1 format.</DD> 20384 <DT>SMARTDATETIMES124</DT> <DD>Use TIME24 for Today</DD> 20385 <DT>SMARTDATETIMES2</DT> <DD>SHORTDATE2 format.</DD> 20386 <DT>SMARTDATETIMES224</DT> <DD>Use TIME24 for Today</DD> 20387 <DT>SMARTDATETIMES3</DT> <DD>SHORTDATE3 format.</DD> 20388 <DT>SMARTDATETIMES324</DT> <DD>Use TIME24 for Today</DD> 20389 <DT>SMARTDATETIMES4</DT> <DD>SHORTDATE4 format.</DD> 20390 <DT>SMARTDATETIMES424</DT> <DD>Use TIME24 for Today</DD> 20391 </DL> 20392</DD> 20393 20394<DT>DAYDATE</DT> 20395<DD> 20396This token represents the date on which the message was sent, according 20397to the "Date" header field. 20398It looks like "Sat, 23 Oct 1998". 20399This token is never converted in any locale-specific way. 20400</DD> 20401 20402<DT>PREFDATE</DT> 20403<DD> 20404This token represents the date on which the message was sent, according 20405to the "Date" header field. 20406It is your operating system's idea of the preferred date representation for the current locale. 20407Internally it uses the %x version of the date from the strftime routine. 20408</DD> 20409 20410<DT>PREFTIME</DT> 20411<DD> 20412This token represents the time at which the message was sent, according 20413to the "Date" header field. 20414It is the preferred time representation for the current locale. 20415Internally it uses the %X version of the time from the strftime routine. 20416</DD> 20417 20418<DT>PREFDATETIME</DT> 20419<DD> 20420This token represents the date and time at which the message was sent, according 20421to the "Date" header field. 20422It is the preferred date and time representation for the current locale. 20423Internally it uses the %c version of the time from the strftime routine. 20424</DD> 20425 20426<DT>DAY</DT> 20427<DD> 20428This token represents the day of the month on which the message was sent, 20429according to the "Date" header field. 20430For example, "23" or "9". 20431</DD> 20432 20433<DT>DAY2DIGIT</DT> 20434<DD> 20435This token represents the day of the month on which the message was sent, 20436according to the "Date" header field. 20437For example, "23" or "09". 20438It is always 2 digits. 20439</DD> 20440 20441<DT>DAYORDINAL</DT> 20442<DD> 20443This token represents the ordinal number that is the day of 20444the month on which the message was sent, 20445according to the "Date" header field. 20446For example, "23rd" or "9th". 20447</DD> 20448 20449<DT>DAYOFWEEK</DT> 20450<DD> 20451This token represents the day of the week on which the message was sent, 20452according to the "Date" header field. 20453For example, "Sunday" or "Wednesday". 20454</DD> 20455 20456<DT>DAYOFWEEKABBREV</DT> 20457<DD> 20458This token represents the day of the week on which the message was sent, 20459according to the "Date" header field. 20460For example, "Sun" or "Wed". 20461</DD> 20462 20463<DT>MONTHABBREV</DT> 20464<DD> 20465This token represents the month the message was sent, according 20466to the "Date" header field. 20467For example, "Oct". 20468</DD> 20469 20470<DT>MONTHLONG</DT> 20471<DD> 20472This token represents the month in which the message was sent, according 20473to the "Date" header field. 20474For example, "October". 20475</DD> 20476 20477<DT>MONTH</DT> 20478<DD> 20479This token represents the month in which the message was sent, according 20480to the "Date" header field. 20481For example, "10" or "9". 20482</DD> 20483 20484<DT>MONTH2DIGIT</DT> 20485<DD> 20486This token represents the month in which the message was sent, according 20487to the "Date" header field. 20488For example, "10" or "09". 20489It is always 2 digits. 20490</DD> 20491 20492<DT>YEAR</DT> 20493<DD> 20494This token represents the year the message was sent, according 20495to the "Date" header field. 20496For example, "1998" or "2001". 20497</DD> 20498 20499<DT>YEAR2DIGIT</DT> 20500<DD> 20501This token represents the year the message was sent, according 20502to the "Date" header field. 20503For example, "98" or "01". 20504It is always 2 digits. 20505</DD> 20506 20507<DT>TIME24</DT> 20508<DD> 20509This token represents the time at which the message was sent, according 20510to the "Date" header field. 20511There is no adjustment made for different time zones, so you'll get 20512the time the message was sent according to the time zone the sender 20513was in. 20514It has the format HH:MM. For example, "17:28". 20515</DD> 20516 20517<DT>TIME12</DT> 20518<DD> 20519This token represents the time at which the message was sent, according 20520to the "Date" header field. 20521This time is for a 12 hour clock. 20522It has the format HH:MMpm. 20523For example, "5:28pm" or "11:13am". 20524</DD> 20525 20526<DT>TIMEZONE</DT> 20527<DD> 20528This token represents the numeric timezone from 20529the "Date" header field. 20530It has the format [+-]HHMM. For example, "-0800". 20531</DD> 20532 20533</DL> 20534 20535<P> 20536<H1><EM>Tokens Available Only for <!--#echo var="VAR_index-format"--></EM></H1> 20537 20538<DL> 20539<DT>MSGNO</DT> 20540<DD> 20541This token represents the message's current position in the folder that, 20542of course, may change as the folder is sorted or new mail arrives. 20543</DD> 20544 20545<DT>STATUS</DT> 20546<DD> 20547This token represents a three character wide field displaying various 20548aspects of the message's state. 20549The first character is either blank, 20550a '*' for message marked Important, or a '+' indicating a message 20551addressed directly to you (as opposed to your having received it via a 20552mailing list, for example). 20553When the feature 20554"<A HREF="h_config_mark_for_cc"><!--#echo var="FEAT_mark-for-cc"--></A>" 20555is set, if the first character would have been 20556blank then it will instead be a '-' if the message is cc'd to you. 20557The second character is typically blank, 20558though the arrow cursor may occupy it if either the 20559"<A HREF="h_config_force_low_speed"><!--#echo var="FEAT_assume-slow-link"--></A>" 20560or the 20561"<A HREF="h_config_force_arrow"><!--#echo var="FEAT_force-arrow-cursor"--></A>" feature 20562is set (or you actually are on a slow link). 20563The third character is either '<A HREF="h_flag_deleted">D</A>' (Deleted), 20564'<A HREF="h_flag_answered">A</A>' (Answered), 20565'<A HREF="h_flag_forwarded">F</A>' (Forwarded), 20566'<A HREF="h_flag_new">N</A>' (New), or blank. 20567<P> 20568If you are using a threaded view of the index and this message is at the 20569top of a collapsed portion of a thread, 20570then this token refers to all of the messages in the collapsed portion of 20571the thread instead of just the top message. 20572The first character will be a '*' if <EM>any</EM> of the messages in the thread 20573are marked Important, else a '+' if any of the messages are addressed 20574to you, else a '-' if any of the messages are cc'd to you. 20575The third character will be a 'D' if <EM>all</EM> of the messages 20576in the collapsed thread are marked deleted, 20577an 'A' if <EM>all</EM> of the messages 20578in the collapsed thread are marked answered, 20579it will be an 'N' if any of 20580the messages are undeleted and unseen, and it will be blank otherwise. 20581</DD> 20582 20583<DT>FULLSTATUS</DT> 20584<DD> 20585This token represents a less abbreviated alternative 20586to the "STATUS" token. 20587It is six characters wide. 20588The first character is '+', '-', or blank, the 20589second blank, the third either '*' or blank, the fourth 20590'<A HREF="h_flag_new">N</A>' or blank, 20591the fifth '<A HREF="h_flag_answered">A</A>' 20592or blank, and the sixth character is 20593either '<A HREF="h_flag_deleted">D</A>' or 20594blank. 20595<P> 20596If you are using a threaded view of the index and this message is at the 20597top of a collapsed portion of a thread, 20598then this token refers to all of the messages in the collapsed portion of 20599the thread instead of just the top message. 20600The first character is '+', '-', or blank depending on whether <EM>any</EM> 20601of the messages in the collapsed thread are addressed to you or cc'd to you. 20602The third character will be '*' if any of the messages are marked 20603Important. 20604The fourth character will be 'N' if all of the messages in the thread 20605are New, else 'n' if some of the messages in the thread are New, else blank. 20606The fifth character will be 'A' or 'a' or blank, and the sixth character 20607will be 'D' or 'd' or blank. 20608</DD> 20609 20610<DT>IMAPSTATUS</DT> 20611<DD> 20612This token represents an even less abbreviated alternative to the 20613"STATUS" token. 20614It differs from "FULLSTATUS" in only the fourth character, which is 20615an 'N' if the message is new to this folder since the last time 20616it was opened <EM>and</EM> it has not been viewed, an 'R' (Recent) if the message 20617is new to the folder and has been viewed, a 'U' (Unseen) if the message is not 20618new to the folder since it was last opened <EM>but</EM> has not been 20619viewed, or a blank if the message has been in the folder since it was 20620last opened and has been viewed. 20621<P> 20622If you are using a threaded view of the index and this message is at the 20623top of a collapsed portion of a thread, 20624then the fourth character will be 20625'N' if all of the messages in the thread are unseen and recent; 20626else 'n' if some of the messages in the thread are unseen and recent; 20627else 'U' if all of the messages in the thread are unseen and not recent; 20628else 'u' if some of the messages in the thread are unseen and not recent; 20629else 'R' if all of the messages in the thread are seen and recent; 20630else 'r' if some of the messages in the thread are seen and recent; 20631else blank. 20632</DD> 20633 20634<DT>SHORTIMAPSTATUS</DT> 20635<DD> 20636This is the same as the last four of the six characters of IMAPSTATUS, 20637so the '+' To Me information will be missing. 20638</DD> 20639 20640<DT>SIZE</DT> 20641<DD> 20642This token represents the total size, in bytes, of the message. 20643If a "K" (Kilobyte) 20644follows the number, the size is approximately 1,000 20645times that many bytes (rounded to the nearest 1,000). 20646If an "M" (Megabyte) follows the number, the size is approximately 206471,000,000 times that many bytes. 20648Commas are not used in this field. 20649This field is seven characters wide, including the enclosing parentheses. 20650Sizes are rounded when "K" or "M" is present. 20651The progression of sizes used looks like: 20652 20653<P> 20654<CENTER><SAMP>0 1 ... 9999 10K ... 999K 1.0M ... 99.9M 100M ... 2000M</SAMP></CENTER> 20655<P> 20656</DD> 20657 20658<DT>SIZECOMMA</DT> 20659<DD> 20660This token represents the total size, in bytes, of the message. 20661If a "K" (Kilobyte) 20662follows the number, the size is approximately 1,000 20663times that many bytes (rounded to the nearest 1,000). 20664If an "M" (Megabyte) follows the number, the size is approximately 206651,000,000 times that many bytes. 20666Commas are used if the number shown is 1,000 or greater. 20667The SIZECOMMA field is one character wider than the SIZE field. 20668Sizes are rounded when "K" or "M" is present. 20669The progression of sizes used looks like: 20670 20671<P> 20672<CENTER><SAMP>0 1 ... 99,999 100K ... 9,999K 10.0M ... 999.9M 1,000M ... 2,000M</SAMP></CENTER> 20673<P> 20674</DD> 20675 20676<DT>KSIZE</DT> 20677<DD> 20678This token represents the total size of the message, expressed in 20679kilobytes or megabytes, as most appropriate. 20680These are 1,024 byte kilobytes and 1,024 x 1,024 byte megabytes. 20681The progression of sizes used looks like: 20682 20683<P> 20684<CENTER><SAMP>0K 1K ... 1023K 1.0M ... 99.9M 100M ... 2047M</SAMP></CENTER> 20685<P> 20686</DD> 20687 20688<DT>SIZENARROW</DT> 20689<DD> 20690This token represents the total size, in bytes, of the message. 20691If a "K" (Kilobyte) 20692follows the number, the size is approximately 1,000 20693times that many bytes. 20694If an "M" (Megabyte) follows the number, the size is approximately 206951,000,000 times that many bytes. 20696If a "G" (Gigabyte) follows the number, the size is approximately 206971,000,000,000 times that many bytes. 20698This field uses only five characters of screen width, including the enclosing 20699parentheses. 20700The progression of sizes used looks like: 20701 20702<P> 20703<CENTER><SAMP>0 1 ... 999 1K ... 99K .1M ... .9M 1M ... 99M .1G ... .9G 1G 2G</SAMP></CENTER> 20704<P> 20705</DD> 20706 20707<DT>DESCRIPSIZE</DT> 20708<DD> 20709This token is intended to represent a more useful description of the 20710message than just its size, but it isn't very useful at this point. 20711The plus sign in this view means there are attachments. 20712Note that including this token in 20713the "<!--#echo var="VAR_index-format"-->" could slow down the 20714display a little while Alpine collects the necessary information. 20715</DD> 20716 20717<DT>SHORTSUBJECT</DT> 20718<DD> This token is the same as SUBJECT, but removes 20719text between "[" and "]". Typically text enclosed 20720between these characters corresponds to mailing list names, and may be 20721unnecessary or unwanted in some instances. 20722</DD> 20723 20724<DT>SUBJKEY</DT> 20725<DD> 20726This token is the same as the SUBJECT token unless keywords are set for 20727the message. 20728In that case, a list of keywords enclosed in braces will be prepended to 20729the subject of the message. 20730Only those keywords that you have defined in your 20731<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option 20732in Setup/Config are considered in the list. 20733In other words, keywords that have been set by some other means, perhaps 20734by another email program, won't show up unless included in 20735<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>. 20736Having this set in the <!--#echo var="VAR_index-format"--> will also cause the keywords to be 20737prepended to the subject in the MESSAGE TEXT screen. 20738If you have given a keyword a nickname 20739(<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>), that nickname is displayed 20740instead of the actual keyword. 20741The <A HREF="h_config_kw_braces"><!--#echo var="VAR_keyword-surrounding-chars"--></A> 20742option may be used to modify this token slightly. 20743It is also possible to color keywords in the index using the 20744Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>). 20745</DD> 20746 20747<DT>SHORTSUBJKEY</DT> 20748<DD> This token is the same as SUBJKEY, but it is based on 20749SHORTSUBJECT, instead of in SUBJECT. 20750</DD> 20751 20752<DT>SUBJKEYINIT</DT> 20753<DD> 20754This token is the same as the SUBJKEY token except that instead of 20755prepending a list of keywords to the subject, a list of first initials 20756of keywords will be prepended instead. 20757For example, if a message has the keywords <EM>Work</EM> and <EM>Now</EM> 20758set (or Work and Now are the Alpine nicknames of keywords that are set) 20759then the SUBJKEY token would cause a result like 20760<P> 20761<CENTER><SAMP>{Work Now} actual subject</SAMP></CENTER> 20762<P> 20763whereas the SUBJKEYINIT token would give 20764<P> 20765<CENTER><SAMP>{WN} actual subject</SAMP></CENTER> 20766<P> 20767Only those keywords that you have defined in your 20768<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option 20769in Setup/Config are considered in the list. 20770In other words, keywords that have been set by some other means, perhaps 20771by another email program, won't show up unless included in 20772<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>. 20773The <A HREF="h_config_kw_braces"><!--#echo var="VAR_keyword-surrounding-chars"--></A> 20774option may be used to modify this token slightly. 20775It is also possible to color keywords in the index using the 20776Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>). 20777</DD> 20778 20779<DT>SHORTSUBJKEYINIT</DT> 20780<DD> This token is the same as SUBJKEYINIT, but it is based on 20781SHORTSUBJECT, instead of in SUBJECT. 20782</DD> 20783 20784<DT>SUBJECTTEXT</DT> 20785<DD> 20786Same as SUBJECT but if there is room in the Subject field for more text, 20787the opening part of the text of the message is displayed after the subject. 20788The time needed to fetch the text may cause a performance problem 20789which can, of course, be avoided by using the SUBJECT version of 20790the Subject instead. 20791You may color this opening text differently by using the 20792<A HREF="h_config_index_opening_color">Index Opening Color</A> option available from 20793the <A HREF="h_color_setup">Setup Kolor</A> screen. 20794You may adjust the characters that are displayed between the Subject and the 20795opening text with the option 20796<A HREF="h_config_opening_sep"><!--#echo var="VAR_opening-text-separator-chars"--></A>. 20797</DD> 20798 20799<DT>SUBJKEYTEXT</DT> 20800<DD> 20801Same as SUBJKEY but with the opening message text. 20802</DD> 20803 20804<DT>OPENINGTEXT</DT> 20805<DD> 20806This is similar to SUBJECTTEXT. 20807Instead of combining the Subject and the opening text in a single 20808field in the index screen this token allows you to allocate a 20809separate column just for the opening text of the message. 20810The time needed to fetch this text may cause a performance problem. 20811You may color this opening text differently by using the 20812<A HREF="h_config_index_opening_color">Index Opening Color</A> option available from 20813the <A HREF="h_color_setup">Setup Kolor</A> screen. 20814</DD> 20815 20816<DT>OPENINGTEXTNQ</DT> 20817<DD> 20818This is very similar to OPENINGTEXT. 20819The NQ stands for No Quotes. 20820The only difference is that quoted text (lines beginning with >) is deleted. 20821For some messages this may be confusing. 20822For example, a message might have a line preceding some quoted 20823text that reads something like "On May 8th person A said." 20824That no longer makes sense after the quoted text is deleted and it 20825will appear that person A said whatever the text after the quote 20826is, even though that is really person B talking. 20827</DD> 20828 20829<DT>SUBJKEYINITTEXT</DT> 20830<DD> 20831Same as SUBJKEYINIT but with the opening message text. 20832</DD> 20833 20834<DT>KEY</DT> 20835<DD> 20836This is a space-delimited list of keywords that are set for the message. 20837Only those keywords that you have defined in your 20838<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option 20839in Setup/Config are considered in the list. 20840In other words, keywords that have been set by some other means, perhaps 20841by another email program, won't show up unless included in 20842<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>. 20843If you have given a keyword a nickname 20844(<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>), that nickname is displayed 20845instead of the actual keyword. 20846It is also possible to color keywords in the index using the 20847Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>). 20848This token defaults to an arbitrary width of 5. 20849You should set it to whatever width suits you using something 20850like KEY(17) in the <!--#echo var="VAR_index-format"-->. 20851</DD> 20852 20853<DT>KEYINIT</DT> 20854<DD> 20855This is a list of keyword initials that are set for the message. 20856If you have given a keyword a nickname 20857(<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>), the initial of that nickname 20858is displayed instead of the initial of the actual keyword. 20859It is also possible to color keyword initials in the index using the 20860Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>). 20861This token defaults to an arbitrary width of 2. 20862You should set it to whatever width suits you using something 20863like KEYINIT(3) in the <!--#echo var="VAR_index-format"-->. 20864</DD> 20865 20866<DT>PRIORITY</DT> 20867<DD> 20868The X-Priority header is a non-standard header that is used in a 20869somewhat standard way by many mail programs. 20870Alpine expects the value of this header to be a digit with a value 20871from 1 to 5, with 1 being the highest priority and 5 the lowest priority. 20872Since this priority is something that the sender sets it is only an indication 20873of the priority that the sender attaches to the mail and it is therefore almost 20874totally unreliable for use as a filtering criterion. 20875This token will display the numeric value of the priority if it is between 208761 and 5. 20877It will be suppressed (blank) if the value is 3, which is normal priority. 20878This token may be colored with the 20879<A HREF="h_config_index_pri_color">Index Priority Symbol Colors</A>. 20880</DD> 20881 20882<DT>PRIORITYALPHA</DT> 20883<DD> 20884This is a more verbose interpretation of the X-Priority field. 20885Once again nothing is displayed unless the value of the field 20886is 1, 2, 4, or 5. 20887The values displayed for those values are: 20888<P> 20889<TABLE> 20890<TR> <TD>1</TD> <TD>Highest</TD> </TR> 20891<TR> <TD>2</TD> <TD>High</TD> </TR> 20892<TR> <TD>4</TD> <TD>Low</TD> </TR> 20893<TR> <TD>5</TD> <TD>Lowest</TD> </TR> 20894</TABLE> 20895<P> 20896This token may be colored with the 20897<A HREF="h_config_index_pri_color">Index Priority Symbol Colors</A>. 20898</DD> 20899 20900<DT>PRIORITY!</DT> 20901<DD> 20902This is a one character, non-numeric version of the X-Priority field. 20903If the value of the X-Priority header is 1 or 2 an exclamation 20904point is displayed. 20905If the value is 4 or 5 a "v" (think down arrow) is displayed. 20906This token may be colored with the 20907<A HREF="h_config_index_pri_color">Index Priority Symbol Colors</A>. 20908</DD> 20909 20910<DT>ATT</DT> 20911<DD> 20912This is a one column wide field that represents the number of attachments 20913a message has. It will be blank if there are no attachments, a single 20914digit for one to nine attachments, or an asterisk for more than nine. 20915Note that including this token in 20916the "<!--#echo var="VAR_index-format"-->" could slow down the 20917display a little while Alpine collects the necessary information. 20918</DD> 20919 20920<DT>FROMORTO</DT> 20921<DD> 20922This token represents <EM>either</EM> the personal name (or email address) of 20923the person listed in the message's "From:" header 20924field, <EM>or</EM>, if that address is yours or one of your 20925<A HREF="h_config_alt_addresses">alternate addresses</A>, 20926the first person specified in the 20927message's "To:" header field 20928with the prefix "To: " prepended. 20929If the from address is yours and there is also no "To" address, 20930Alpine will use the address on the "Cc" line. 20931If there is no address there, either, Alpine will look for a newsgroup name 20932from the "Newsgroups" header field and put 20933that after the "To: " prefix. 20934</DD> 20935 20936<DT>FROMORTONOTNEWS</DT> 20937<DD> 20938This is almost the same as <EM>FROMORTO</EM>. 20939The difference is that newsgroups aren't considered. 20940When a message is from you, doesn't have a To or Cc, and does have 20941a Newsgroups header; this token will be your name instead of the name 20942of the newsgroup (like it would be with FROMORTO). 20943</DD> 20944 20945<DT>TEXT</DT> 20946<DD> 20947This is a different sort of token. 20948It allows you to display a label within each index line. 20949It will be the same fixed text for each line. 20950It is different from all the other tokens in that there is no space column 20951displayed after this token. 20952Instead, it is butted up against the following field. 20953It also has a different syntax. 20954The text to display is given following a colon after the 20955word "TEXT". 20956For example, 20957<P> 20958<CENTER><SAMP>TEXT:abc=</SAMP></CENTER> 20959<P> 20960would insert the literal text "abc=" (without the quotes) 20961into the index display line. 20962You must quote the text if it includes space characters, like 20963<P> 20964<CENTER><SAMP>TEXT:"abc = "</SAMP></CENTER> 20965<P> 20966</DD> 20967 20968<DT>HEADER</DT> 20969<DD> 20970This allows you to display the text from a particular header line in the 20971message. 20972The syntax for this token is substantially different from all the others 20973in order that you might be able to display a portion of the text following 20974a particular header. 20975The header name you are interested in is given following a colon 20976after the word "HEADER". 20977For example, 20978<P> 20979<CENTER><SAMP>HEADER:X-Spam</SAMP></CENTER> 20980<P> 20981would display the text of the X-Spam header, if any. 20982Like for other index tokens a width field may (and probably should) 20983follow this. 20984<P> 20985<CENTER><SAMP>HEADER:X-Spam(10)</SAMP></CENTER> 20986<P> 20987displays the first ten characters of the X-Spam header. 20988Unlike other index tokens, the syntax for HEADER is more flexible. 20989An optional second argument comes after a comma inside the parentheses. 20990It specifies the "field" number. 20991By default, the field separator is a space character. 20992No extra space characters are allowed in the argument list. 20993<P> 20994<CENTER><SAMP>HEADER:X-Spam(10,2)</SAMP></CENTER> 20995<P> 20996would display the second field, left-justified, in a 10 character 20997wide field. 20998The second field would consist of all the text after the first space 20999up to the next space or the end of the header. 21000The default field number is zero, which stands for the entire line. 21001There is also an optional third argument that is a list of field 21002separators. It defaults to a space character. 21003The example 21004<P> 21005<CENTER><SAMP>HEADER:X-Spam(10,2,:% )</SAMP></CENTER> 21006<P> 21007would cause the field separators to be any of colon, percent, 21008or space (there is a space character between the percent and the 21009right parenthesis). 21010The first field runs from the start of the header value up to the first 21011colon, percent, or space; the second goes from there to the next; and so on. 21012In order to use a comma character as a field separator you must escape 21013it by preceding it with a backslash (\). 21014The same is true of the backslash character itself. 21015There is one further optional argument. 21016It is an R or an L to specify right or left adjustment of the text 21017within the field. 21018The default is to left justify, however if you are displaying numbers 21019you might prefer to right justify. 21020<P> 21021Here's an example of a SpamAssassin header. 21022The exact look of the header will vary, but if your incoming mail 21023contains headers that look like the following 21024<P> 21025<CENTER><SAMP>X-Spam-Status: Yes, hits=10.6 tagged_above=-999.0 required=7.0 tests=BAYE...</SAMP></CENTER> 21026<P> 21027you might want to display the hits value. 21028The first field starts with the Y in Yes. 21029To get what you're interested in you might use "=" and 21030space as the field separators and display the third field, like 21031<P> 21032<CENTER><SAMP>HEADER:X-Spam-Status(4,3,= )</SAMP></CENTER> 21033<P> 21034or maybe you would break at the dot instead 21035<P> 21036<CENTER><SAMP>HEADER:X-Spam-Status(2,2,=.,R)</SAMP></CENTER> 21037<P> 21038Another example we've seen has headers that look like 21039<P> 21040<CENTER><SAMP>X-Spam: Gauge=IIIIIII, Probability=7%, Report=...</SAMP></CENTER> 21041<P> 21042Because there are two equals and a comma before the 7% and a comma 21043after it, the token 21044<P> 21045<CENTER><SAMP>HEADER:X-Spam(3,4,=\,,R)</SAMP></CENTER> 21046<P> 21047should display the probability (for example 7% or 83%) right justified 21048in a 3-wide field. 21049</DD> 21050 21051<DT>ARROW</DT> 21052<DD> 21053This gives an alternative way to display the current message in the 21054MESSAGE INDEX screen. 21055Usually the current message is indicated by the line being shown in 21056reverse video. 21057Instead, if the ARROW token is included in your <!--#echo var="VAR_index-format"-->, 21058the current line will include an "arrow" that 21059looks like 21060<P> 21061<CENTER><SAMP>-></SAMP></CENTER> 21062<P> 21063in the ARROW token's field. 21064For all of the non-current messages, the ARROW field will be filled 21065with blanks. 21066If you use the fixed-field width feature the length of the "arrow" 21067may be adjusted. 21068The arrow will be drawn as width-1 dashes followed by a greater than sign. 21069For example, if you use ARROW(3) you will get 21070<P> 21071<CENTER><SAMP>--></SAMP></CENTER> 21072<P> 21073and ARROW(1) will give you just 21074<P> 21075<CENTER><SAMP>></SAMP></CENTER> 21076<P> 21077It is also possible to set the color of the ARROW field. 21078By default (and for non-current messages) the arrow is colored the same 21079as the index line it is part of. 21080You may set it to be another color with the 21081<A HREF="h_config_index_arrow_color">Index Arrow Color</A> option available from 21082the <A HREF="h_color_setup">Setup Kolor</A> screen. 21083</DD> 21084 21085<DT>SCORE</DT> 21086<DD> 21087This gives the 21088<a href="h_rules_score">score</a> 21089of each message. 21090This will be six columns wide to accommodate the widest possible score. 21091You will probably want to use the <!--#echo var="VAR_index-format"--> fixed-field width feature 21092to limit the width of the field to the widest score that 21093you use (e.g. SCORE(3) if your scores are always between 0 and 999). 21094If you have not defined any score rules the scores will all be zero. 21095If any of your score rules contain AllText or BodyText patterns 21096then including SCORE in the <!--#echo var="VAR_index-format"--> 21097may slow down the display of the MESSAGE INDEX screen. 21098</DD> 21099</DL> 21100 21101<P> 21102<H1><EM>Tokens Available for all but <!--#echo var="VAR_index-format"--></EM></H1> 21103 21104<DL> 21105<DT>CURNEWS</DT> 21106<DD> 21107This token represents the current newsgroup if there is one. 21108For example, "comp.mail.pine". 21109</DD> 21110 21111<DT>MSGID</DT> 21112<DD> 21113This token represents the message ID of the message. 21114This token does not work with Filter Rule folder names. 21115</DD> 21116 21117<DT>CURDATE</DT> 21118<DD> 21119This token represents the current date. 21120It has the format MMM DD. For example, "Oct 23". 21121</DD> 21122 21123<DT>CURDATEISO</DT> 21124<DD> 21125This token represents the current date. 21126It has the format YYYY-MM-DD. For example, "1998-10-23". 21127</DD> 21128 21129<DT>CURDATEISOS</DT> 21130<DD> 21131This token represents the current date. 21132It has the format YY-MM-DD. For example, "98-10-23". 21133</DD> 21134 21135<DT>CURPREFDATE</DT> 21136<DD> 21137This token represents the current date. 21138It is your operating system's idea of the preferred date representation for the current locale. 21139Internally it uses the %x version of the date from the strftime routine. 21140</DD> 21141 21142<DT>CURPREFTIME</DT> 21143<DD> 21144This token represents the current time. 21145It is the preferred time representation for the current locale. 21146Internally it uses the %X version of the time from the strftime routine. 21147</DD> 21148 21149<DT>CURPREFDATETIME</DT> 21150<DD> 21151This token represents the current date and time. 21152It is the preferred date and time representation for the current locale. 21153Internally it uses the %c version of the time from the strftime routine. 21154</DD> 21155 21156<DT>CURTIME24</DT> 21157<DD> 21158This token represents the current time. 21159It has the format HH:MM. For example, "17:28". 21160</DD> 21161 21162<DT>CURTIME12</DT> 21163<DD> 21164This token represents the current time. 21165This time is for a 12 hour clock. 21166It has the format HH:MMpm. 21167For example, "5:28pm" or "11:13am". 21168</DD> 21169 21170<DT>CURDAY</DT> 21171<DD> 21172This token represents the current day of the month. 21173For example, "23" or "9". 21174</DD> 21175 21176<DT>CURDAY2DIGIT</DT> 21177<DD> 21178This token represents the current day of the month. 21179For example, "23" or "09". 21180It is always 2 digits. 21181</DD> 21182 21183<DT>CURDAYOFWEEK</DT> 21184<DD> 21185This token represents the current day of the week. 21186For example, "Sunday" or "Wednesday". 21187</DD> 21188 21189<DT>CURDAYOFWEEKABBREV</DT> 21190<DD> 21191This token represents the current day of the week. 21192For example, "Sun" or "Wed". 21193</DD> 21194 21195<DT>CURMONTH</DT> 21196<DD> 21197This token represents the current month. 21198For example, "10" or "9". 21199</DD> 21200 21201<DT>CURMONTH2DIGIT</DT> 21202<DD> 21203This token represents the current month. 21204For example, "10" or "09". 21205It is always 2 digits. 21206</DD> 21207 21208<DT>CURMONTHLONG</DT> 21209<DD> 21210This token represents the current month. 21211For example, "October". 21212</DD> 21213 21214<DT>CURMONTHABBREV</DT> 21215<DD> 21216This token represents the current month. 21217For example, "Oct". 21218</DD> 21219 21220<DT>CURYEAR</DT> 21221<DD> 21222This token represents the current year. 21223For example, "1998" or "2001". 21224</DD> 21225 21226<DT>CURYEAR2DIGIT</DT> 21227<DD> 21228This token represents the current year. 21229For example, "98" or "01". 21230It is always 2 digits. 21231</DD> 21232 21233<DT>LASTMONTH</DT> 21234<DD> 21235This token represents last month. 21236For example, if this is November (the 11th month), 21237it is equal to "10" or if this is October (the 10th month), 21238it is "9". 21239It is possible that this and the other tokens beginning with LASTMONTH 21240below could be useful when used with a Filtering Rule that 21241has the "Beginning of Month" option set. 21242</DD> 21243 21244<DT>LASTMONTH2DIGIT</DT> 21245<DD> 21246This token represents last month. 21247For example, if this is November (the 11th month), 21248it is equal to "10" or if this is October (the 10th month), 21249it is "09". 21250It is always 2 digits. 21251</DD> 21252 21253<DT>LASTMONTHLONG</DT> 21254<DD> 21255This token represents last month. 21256For example, if this is November the value is "October". 21257</DD> 21258 21259<DT>LASTMONTHABBREV</DT> 21260<DD> 21261This token represents last month. 21262For example, if this is November the value is "Oct". 21263</DD> 21264 21265<DT>LASTMONTHYEAR</DT> 21266<DD> 21267This token represents what the year was a month ago. 21268For example, if this is October, 1998, it is "1998". 21269If this is January, 1998, it is "1997". 21270</DD> 21271 21272<DT>LASTMONTHYEAR2DIGIT</DT> 21273<DD> 21274This token represents what the year was a month ago. 21275For example, if this is October, 1998, it is "98". 21276If this is January, 1998, it is "97". 21277</DD> 21278 21279<DT>LASTYEAR</DT> 21280<DD> 21281This token represents last year. 21282For example, if this is 1998, it equals "1997". 21283It is possible that this 21284could be useful when used with a Filtering Rule that 21285has the "Beginning of Year" option set. 21286</DD> 21287 21288<DT>LASTYEAR2DIGIT</DT> 21289<DD> 21290This token represents last year. 21291For example, if this is 1998, it equals "97". 21292It is always 2 digits. 21293</DD> 21294 21295<DT>ROLENICK</DT> 21296<DD> 21297This token represents the nickname of the 21298role currently being used. If no role is being used, 21299then no text will be printed for this token. 21300This token does not work with Filter Rule folder names. 21301</DD> 21302</DL> 21303 21304<P> 21305<H1><EM>Token Available Only for <!--#echo var="VAR_reply-leadin"--></EM></H1> 21306See the help for the 21307<A HREF="h_config_reply_intro">"<!--#echo var="VAR_reply-leadin"-->"</A> option 21308to see why you might want to use this. 21309Since the <!--#echo var="VAR_reply-leadin"--> contains free text this token 21310must be surrounded by underscores when used. 21311 21312<DL> 21313<DT>NEWLINE</DT> 21314<DD> 21315This is an end of line marker. 21316</DD> 21317</DL> 21318 21319<P> 21320<H1><EM>Token Available Only for Templates and Signatures</EM></H1> 21321 21322<DL> 21323<DT>CURSORPOS</DT> 21324<DD> 21325This token is different from the others. 21326When it is replaced it is replaced with nothing, but it sets an Alpine 21327internal variable that tells the composer to start with the cursor 21328positioned at the position where this token was. 21329If both the template file and the signature file contain 21330a "CURSORPOS" token, then the position in the template file 21331is used. 21332If there is a template file and neither it nor the signature file contains 21333a "CURSORPOS" token, then the cursor is positioned 21334after the end of the contents of the 21335template file when the composer starts up. 21336</DD> 21337</DL> 21338 21339<P> 21340<End of help on this topic> 21341</BODY> 21342</HTML> 21343======= h_reply_token_conditionals ======= 21344<HTML> 21345<HEAD> 21346<TITLE>Conditional Inclusion of Text for <!--#echo var="VAR_reply-leadin"-->, Signatures, and Templates</TITLE> 21347</HEAD> 21348<BODY> 21349<H1>Conditional Inclusion of Text for <!--#echo var="VAR_reply-leadin"-->, Signatures, and Templates</H1> 21350 21351Conditional text inclusion may be used with 21352the <A HREF="h_config_reply_intro">"<!--#echo var="VAR_reply-leadin"-->"</A> option, 21353in signature files, and in template files used in 21354<A HREF="h_rules_roles">"roles"</A>. 21355It may <EM>not</EM> be used with the 21356<A HREF="h_config_index_format">"<!--#echo var="VAR_index-format"-->"</A> option. 21357 21358<P> 21359There is a limited if-else capability for including text. 21360The if-else condition is based 21361on whether or not a given token would result in replacement text you 21362specify. 21363The syntax of this conditional inclusion is 21364<P> 21365<CENTER><SAMP>_token_(match_this, if_matched [ , if_not_matched ] )</SAMP></CENTER> 21366<P> 21367The left parenthesis must follow the underscore immediately, with no 21368intervening space. 21369It means the token is expanded and the results of that expansion are 21370compared against the "match_this" argument. 21371If there is an exact match, then the "if_matched" text is used 21372as the replacement text. 21373Otherwise, the "if_not_matched" text is used. 21374One of the most useful values for the "match_this" argument is 21375the empty string, "". 21376In that case the expansion is compared against the empty string. 21377<P> 21378Here's an example to make it clearer. 21379This text could be included in one of your template files: 21380<P> 21381<CENTER><SAMP>_NEWS_("", "I'm replying to email", "I'm replying to news")</SAMP></CENTER> 21382<P> 21383If that is included in a template file that you are using while replying 21384to a message (because you chose to use the role it was part of), 21385and that message has a newsgroup header and a newsgroup in that header, 21386then the text 21387<P> 21388<CENTER><SAMP>I'm replying to news</SAMP></CENTER> 21389<P> 21390will be included in the message you are about to compose. 21391On the other hand, if the message you are replying to does not have 21392a newsgroup, then the text 21393<P> 21394<CENTER><SAMP>I'm replying to email</SAMP></CENTER> 21395<P> 21396would be included instead. 21397This would also work in signature files and in 21398the "<!--#echo var="VAR_reply-leadin"-->" option. 21399If the "match_this", "if_matched", 21400or "if_not_matched" arguments contain 21401spaces, parentheses, or commas; 21402they have to be quoted with double quotation marks (like in the example 21403above). 21404If you want to include a literal quote (") in the text you must escape the 21405quote by preceding it with a backslash (\) character. 21406If you want to include a literal backslash character you must escape it 21407by preceding it with another backslash. 21408<P> 21409The comma followed by "if_not_matched" is optional. 21410If there is no "if_not_matched" 21411present then no text is included if the not_matched case is true. 21412Here's another example: 21413<P> 21414<CENTER><SAMP>_NEWS_("", "", "This msg was seen in group: _NEWS_.")</SAMP></CENTER> 21415<P> 21416Here you can see that tokens may appear in the arguments. 21417The same is true for tokens with the conditional parentheses. 21418They may appear in arguments, 21419though you do have to be careful to get the quoting and escaping of 21420nested double quotes correct. 21421If this was in the signature file being used and you were replying to a message 21422sent to comp.mail.pine the resulting text would be: 21423<P> 21424<CENTER><SAMP>This msg was seen in group: comp.mail.pine.</SAMP></CENTER> 21425<P> 21426If you were replying to a message that wasn't sent to any newsgroup the 21427resulting text would be a single blank line. 21428The reason you'd get a blank line is because the end of the line is 21429outside of the conditional, so is always included. 21430If you wanted to get rid of that blank line you could do so by moving 21431the end of line inside the conditional. 21432In other words, it's ok to have multi-line 21433"if_matched" or "if_not_matched" arguments in your 21434template file. 21435The text just continues until the next double quotation, even if it's not 21436on the same line. 21437<P> 21438Here's an example for use in the "<!--#echo var="VAR_reply-leadin"-->": 21439<P> 21440<CENTER><SAMP>On _DAYDATE_, _FROM__CURNEWS_("", "", "seen in _CURNEWS_,") wrote</SAMP></CENTER> 21441<P> 21442If this was in your <!--#echo var="VAR_reply-leadin"--> and you were replying to a message 21443while reading the newsgroup comp.mail.pine the resulting text would be: 21444<P> 21445<CENTER><SAMP>On Sat, 24 Oct 1998, Fred Flintstone, seen in comp.mail.pine, wrote:</SAMP></CENTER> 21446<P> 21447If you were replying to a message while reading an email folder instead 21448of a newsgroup the resulting leadin text would be 21449<P> 21450<CENTER><SAMP>On Sat, 24 Oct 1998, Fred Flintstone wrote:</SAMP></CENTER> 21451<P> 21452Here's one more (contrived) example illustrating a matching argument 21453that is not the empty string. 21454<P> 21455<CENTER><SAMP>_SMARTDATE_("Today", _SMARTDATE_, "On _DATE_") _FROM_ wrote:</SAMP></CENTER> 21456<P> 21457If this was the value of your "<!--#echo var="VAR_reply-leadin"-->" option and you 21458were replying to 21459a message that was sent today, then the value of the "<!--#echo var="VAR_reply-leadin"-->" 21460would be 21461<P> 21462<CENTER><SAMP>Today Fred Flintstone wrote:</SAMP></CENTER> 21463<P> 21464But if you were replying to a message sent on Oct. 27 (and that wasn't 21465today) you would get 21466<P> 21467<CENTER><SAMP>On Oct 27 Fred Flintstone wrote:</SAMP></CENTER> 21468<P> 21469 21470<End of help on this topic> 21471</BODY> 21472</HTML> 21473======= h_composer_cntxt_nick ======= 21474<HTML> 21475<HEAD> 21476<TITLE>Collection Nickname Explained</TITLE> 21477</HEAD> 21478<BODY> 21479<H1>Collection Edit Help -- Nickname Field</H1> 21480 21481This field is provided so you can add a short nickname to use when 21482referring to this collection within Alpine. Spaces are allowed, and 21483you don't need to use double-quotes. However, the double-quote 21484character is not allowed. 21485<P> 21486Look <A HREF="h_edit_nav_cmds">here</A> 21487to see the available Editing and Navigation commands. 21488<P> 21489<End of help on this topic> 21490</BODY> 21491</HTML> 21492======= h_folder_server_syntax ======= 21493<HTML> 21494<HEAD> 21495<TITLE>Server Name Syntax</TITLE> 21496</HEAD> 21497<BODY> 21498<H1>Server Name Syntax</H1> 21499 21500This help describes the syntax that may be used for server names 21501that may be associated with remote folders or SMTP servers. 21502 21503<P> 21504A server name is the hostname of the server. 21505It's a good idea to use the host's fully-qualified network name. 21506 21507<P> 21508<CENTER><SAMP>foo.example.com</SAMP></CENTER> 21509<P> 21510 21511However, IP addresses are allowed if surrounded 21512with square-brackets. 21513 21514<P> 21515<CENTER><SAMP>[127.0.0.1]</SAMP></CENTER> 21516<P> 21517 21518An optional network port number may be supplied by appending 21519a colon (:) followed by the port number 21520to the server name. 21521By default, the IMAP port number, 143, is used. 21522 21523<P> 21524<CENTER><SAMP>foo.example.com:port</SAMP></CENTER> 21525<P> 21526 21527Besides server name and optional port number, various other optional 21528parameters may be supplied that alter Alpine's interaction with the server. 21529A parameter is supplied by appending a slash (/) character followed by 21530the parameter's name and, 21531depending on the particular parameter, the value assigned to that 21532name, to the server name (and optional port number). 21533Parameter names are <EM>not</EM> case sensitive. 21534Currently supported parameters include: 21535 21536<DL> 21537 21538<DT>User</DT> 21539<DD>This parameter requires an associated value, and is intended to 21540provide the username identifier with which to establish the server 21541connection. 21542If your SMTP server offers SMTP AUTH authentication, adding this 21543parameter to the 21544<A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A> 21545option will cause Alpine to attempt to authenticate to the server using the 21546supplied username. 21547Similarly, if your NNTP server offers NNTP "AUTHINFO SASL" 21548or "AUTHINFO USER" authentication, adding this parameter to the 21549<A HREF="h_config_nntp_server"><!--#echo var="VAR_nntp-server"--></A> 21550option (or to the server name for any folder collection using NNTP) 21551will cause Alpine to attempt 21552to authenticate to the server using the supplied username. 21553An example might be: 21554 21555<P> 21556<CENTER><SAMP>/user=katie</SAMP></CENTER> 21557<P> 21558 21559</DD> 21560 21561<DT>STARTTLS</DT> 21562<DD> 21563This is a unary parameter indicating communication with the server must 21564take place over a TLS connection. If you use this parameter, Alpine will 21565establish an insecure connection to the server, and later will attempts to 21566use a secure encrypted connection. If the attempt to use TLS fails then 21567this parameter will cause the connection to fail instead of falling back 21568to an insecure connection. 21569<P> 21570Use this option when you are told to use STARTTLS. If you are told to use 21571SSL or TLS on port 993, use the /ssl unary parameter instead, and not this 21572parameter. Use this parameter when establishing a connection to a server 21573on an insecure port (normally port 143 for IMAP) and then needing to 21574establish a secure connection using STARTTLS. 21575 21576<P><A href="h_security_considerations">Learn more</A> about security 21577considerations when you use this option. 21578 21579<P> 21580<CENTER><SAMP>/starttls</SAMP></CENTER> 21581<P> 21582 21583</DD> 21584 21585<DT>SSL</DT> 21586<DD> 21587This is a unary parameter indicating communication with the server should 21588take place over a Secure Socket Layer connection. The server must support 21589this method, and be prepared to accept connections on the appropriate 21590port (993 by default). 21591Alpine must be linked with an SSL library for this option to be operational. 21592Using this option will make Alpine try to connect to the server using the 21593most secure encrypted SSL connection that both your version of Alpine and the 21594server support. 21595 21596<P> 21597<CENTER><SAMP>/ssl</SAMP></CENTER> 21598<P> 21599 21600</DD> 21601 21602<DT>TLS1</DT> 21603<DD> 21604This parameter indicates that the connection to the server will be made 21605over the SSL port, but using the TLSv1 protocol, instead of the usual 21606SSLv3 or SSLv2 protocols. 21607Alpine must be linked with an SSL library for this option to be operational. 21608 21609<P> 21610<CENTER><SAMP>/tls1</SAMP></CENTER> 21611<P> 21612</DD> 21613 21614<DT>TLS1_1</DT> 21615<DD> 21616This parameter indicates that the connection to the server will be made 21617over the SSL port, but using the TLSv1.1 protocol. 21618Alpine must be linked with an SSL library that supports this encryption 21619protocol for this option to be operational. 21620 21621<P> 21622<CENTER><SAMP>/tls1_1</SAMP></CENTER> 21623<P> 21624</DD> 21625 21626<DT>TLS1_2</DT> 21627<DD> 21628This parameter indicates that the connection to the server will be made 21629over the SSL port, but using the TLSv1.2 protocol. 21630Alpine must be linked with an SSL library that supports this encryption 21631protocol for this option to be operational. 21632 21633<P> 21634<CENTER><SAMP>/tls1_2</SAMP></CENTER> 21635<P> 21636</DD> 21637 21638<DT>TLS1_3</DT> 21639<DD> 21640This parameter indicates that the connection to the server will be made 21641over the SSL port, but using the TLSv1.3 protocol. 21642Alpine must be linked with an SSL library that supports this encryption 21643protocol for this option to be operational. 21644 21645<P> 21646<CENTER><SAMP>/tls1_3</SAMP></CENTER> 21647<P> 21648</DD> 21649 21650<DT>NoValidate-Cert</DT> 21651<DD>Do not validate certificates (for TLS or SSL connections) from the server. 21652This is needed if the server uses self-signed certificates or if Alpine 21653cannot validate the certificate for some other known reason. You should avoid 21654using this option, and instead install the certificate of the server, so you 21655are not a victim of a cracker-in-the-middle attack. 21656<P> 21657</DD> 21658 21659<DT>Anonymous</DT> 21660<DD>This is a unary parameter (that means it does not have a value) 21661indicating that the connection be logged in as 21662"anonymous" rather than a specific user. 21663Not all servers offer anonymous 21664access; those which do generally only offer read-only access to certain 21665"public" folders. 21666 21667<P> 21668<CENTER><SAMP>/anonymous</SAMP></CENTER> 21669<P> 21670 21671</DD> 21672 21673<DT>Secure</DT> 21674<DD>This is a unary parameter indicating that the connection use the 21675most secure authentication method mutually supported by Alpine and the 21676server. 21677Alpine is capable of authenticating connections to 21678the server using several methods. 21679By default, Alpine will attempt each 21680method until either a connection is established or the 21681list of methods is exhausted. 21682This parameter causes Alpine to instead fail 21683the connection if the first (generally most "secure") method fails. 21684 21685<P> 21686<CENTER><SAMP>/secure</SAMP></CENTER> 21687<P> 21688 21689</DD> 21690 21691<DT>Submit</DT> 21692<DD>This is a unary parameter for use with the 21693<A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A> option. 21694It indicates that the connection should be made to the Submit server 21695(<A HREF="http://www.ietf.org/rfc/rfc2476.txt">RFC 3676</A>) 21696(port 587) instead of the SMTP port (25). 21697At the time this help was written the submit option was equivalent to 21698specifying port 587. <A href="h_security_considerations">Learn more</A> 21699about security considerations when you use this option. 21700 21701<P> 21702<CENTER><SAMP>/submit</SAMP></CENTER> 21703<P> 21704or 21705<P> 21706<CENTER><SAMP>host:587</SAMP></CENTER> 21707<P> 21708 21709</DD> 21710 21711<DT>Debug</DT> 21712<DD>This is a unary parameter indicating that the connection be established 21713in a verbose mode. Basically, it causes Alpine to log the communication with 21714the server in Alpine's debug file. 21715Normally, the pine -d command-line flag would be used instead. 21716<P> 21717</DD> 21718 21719<DT>NoRsh</DT> 21720<DD>By default, Alpine attempts to login using "rsh", 21721the UNIX remote shell program. 21722Including "NoRsh" will cause connections to this server to skip 21723the "rsh" attempt. 21724This might be useful to avoid long timeouts caused by rsh firewalls, for 21725example. 21726<P> 21727</DD> 21728 21729<DT>Loser</DT> 21730<DD>This option makes sense only for IMAP servers that do not perform 21731a SEARCH command correctly. If your filtering rules 21732fail to filter some messages, that should have been filtered, then this 21733option will make Alpine download all data necessary data to perform that 21734search. There is a performance penalty when using this option. Downloading 21735the data to perform the search will take longer than requesting the IMAP 21736server to perform the filtering, but the filtering will be done correctly. 21737<P> 21738</DD> 21739 21740 21741<DT>Service</DT> 21742<DD>This parameter requires an associated value. The default value is 21743"IMAP" which indicates communication with the server based 21744on the IMAP4rev1 protocol (defined in RFC 3501 -- see 21745<A HREF="http://www.imap.org/docs/rfc3501.html">http://www.imap.org/docs/rfc3501.html</A>).</DD> 21746 21747Other service values include: 21748 <DL> 21749 <DT>NNTP</DT> 21750 <DD>This value indicates communication with the server takes place via 21751the Network News Transfer Protocol. Use this to define a collection 21752of newsgroups on a remote news server. So 21753 21754<P> 21755<CENTER><SAMP>/service=NNTP</SAMP></CENTER> 21756<P> 21757or just 21758<P> 21759<CENTER><SAMP>/NNTP</SAMP></CENTER> 21760<P> 21761 21762is the way to specify NNTP access. 21763<P> 21764 </DD> 21765 21766 <DT>POP3</DT> 21767 <DD>This value indicates communication with the server takes place via the 21768Post Office Protocol 3 protocol. 21769 21770<P> 21771<CENTER><SAMP>/service=POP3</SAMP></CENTER> 21772<P> 21773or just 21774<P> 21775<CENTER><SAMP>/POP3</SAMP></CENTER> 21776<P> 21777 21778Note that there are several important issues 21779to consider when selecting this option: 21780<OL> 21781 <LI> POP3 provides access to only your INBOX. In other words, 21782secondary folders such as your "saved-messages" are inaccessible. 21783 <LI> Alpine's implementation of POP3 does not follow the traditional POP 21784model and will leave your mail on the server. Refer to the 21785<A HREF="h_maildrop">Mail Drop</A> functionality for a possible way around this problem. 21786 <LI> See the discussion about new-mail checking in <A HREF="h_config_reopen_rule">"<!--#echo var="VAR_folder-reopen-rule"-->"</A>. 21787</OL> 21788</DD> 21789</DL> 21790</DL> 21791 21792<P> 21793Note that it is possible to include more than one parameter in a server 21794specification by concatenating the parameters. For example: 21795 21796<P> 21797<CENTER><SAMP>foo.example.com:port/user=katie/novalidate-cert/debug</SAMP></CENTER> 21798<P> 21799 21800<P> 21801<End of help on this topic> 21802</BODY> 21803</HTML> 21804======= h_security_considerations ======= 21805<HTML> 21806<HEAD> 21807<TITLE>SSL, TLS, STARTTLS and More Security Considerations</TITLE> 21808</HEAD> 21809<BODY> 21810<H1>SSL, TLS, STARTTLS and More Security Considerations</H1> 21811 21812The purpose of this text is to educate users on how to best choose 21813the type of security connection to a remote server using the SSL and TLS 21814encryption protocols. 21815 21816<P> 21817In the past, and when Alpine originally started to support encrypted connections 21818to remote servers, the /ssl modifier was needed, and it meant any of the SSLv2 21819or SSLv3 protocols. Those encryption protocols are considered not fully secure 21820anymore, and in fact, you might not be able to use them anymore. 21821 21822<P> Today the /ssl modifier means to use the most secure encryption 21823protocol between your version of Alpine and what the server supports. This 21824might mean more modern protocols, such as TLS 1.0, TLS 1.1, etc. As of 21825this writing, Alpine supports connection using TLS 1.3. These protocols 21826are considered more secure today and they should be preferred over the old 21827SSL protocols. 21828 21829<P> A source of confusion for Alpine users might be the meaning of the 21830modifier /tls with respect to the names of the encryption protocols, such 21831as TLS 1.2. The meaning of /tls is to start an encrypted connection to a 21832server after an insecure connection has been established, and we will 21833discuss this later in this help text. The preferred way flag is to use 21834/starttls, instead of /tls. 21835 21836<P>The best way to start an encrypted connection to a server is to use the 21837/ssl modifier. If your provider allows encrypted connections on port 993 21838for IMAP, or port 995 for POP3, or in port 465 for SMTP, just define your 21839server by adding the /ssl modifier and do not add the port to the server. 21840Alpine knows that the secure connection will be done in the correct port, 21841and will use the most secure encryption available between Alpine and the 21842server. You only need to use the port number when it is different from the 21843default port numbers for this type of connections, and those were given 21844above. 21845 21846<P>Most email service providers identify secure connections by saying 21847"SSL or TLS". In this case, use the /ssl modifier, and only use 21848the port number in case it is different to the ones above. 21849 21850<P>If your service provider says to use STARTTLS, then you need to use the 21851/starttls modifier. If your service provider gives you the option to use SSL or 21852TLS and to use STARTTLS choose the secure port and choose the /ssl 21853modifier. This is because connections using the /starttls modifier can be 21854attacked and your username and password can be stolen by a hacker. The next 21855paragraph describes in short how to do this. 21856 21857<P> When you use the /starttls modifier, Alpine connects insecurely to the 21858remote server. Because the connection is insecure, it is possible that you 21859connect to a different server, which connects you to the real server. This 21860is called "man-in-the-middle" attack, and so your communication 21861will pass through the hackers computer before it reaches the real target. 21862An example of a possible man-in-the-middle is your internet service provider, 21863or your employer in some instances. 21864This means that the hacker can modify the replies from the correct server 21865and give you the illusion of security before you are actually connected to 21866the secure server. Therefore, you might disclose your username and 21867password to the hacker before you establish a secure connection to the correct 21868server. 21869 21870<P> Therefore, if possible avoid using STARTTLS (for IMAP and POP) or SUBMIT 21871for SMTP (in port 587), as these are subject to attack. If possible 21872ask your provider for secure connections for SSL or TLS in the secure ports 21873993 for IMAP, 995 for POP or 465 for SMTP. 21874 21875<P> In the current state, even as of TLS 1.3, these protocols are considered 21876secure but they do not protect your privacy. For example your internet 21877service provider might track to which servers you are connecting securely. 21878Encryption protocols are evolving to not only protect the security of your 21879data, but also your privacy. 21880 21881<P> Other types of errors can lead to insecure connections. An example is 21882when the name of the server as provided by the user does not match the 21883name of the server in the certificate. 21884<A href="h_tls_validation_failure">Read more</A> about security errors 21885of this type and learn how to protect yourself against this type of 21886errors. 21887 21888<P> 21889<End of help on this topic> 21890</BODY> 21891</HTML> 21892======= h_composer_cntxt_server ======= 21893<HTML> 21894<HEAD> 21895<TITLE>Collection Server: Explained</TITLE> 21896</HEAD> 21897<BODY> 21898<H1>Collection Edit Help -- Server Field</H1> 21899 21900This collection's "Server:" definition indicates the 21901hostname of the server providing access to the folders in this 21902collection. 21903The syntax of this server name is the same as for other server names used 21904in remote folder names in 21905Alpine and is described 21906<A HREF="h_folder_server_syntax">here</A>. 21907 21908<P> 21909<End of help on this topic> 21910</BODY> 21911</HTML> 21912======= h_composer_cntxt_path ======= 21913<HTML> 21914<HEAD> 21915<TITLE>Collection Path: Explained</TITLE> 21916</HEAD> 21917<BODY> 21918<H1>Collection Edit Help -- Path Field</H1> 21919 21920The collection's "Path:" definition indicates the location 21921of the folders in this collection. If the path or any of its components 21922do not exist, Alpine will prompt you for their creation when exiting the 21923Add/Change screen. 21924 21925<P> 21926By default the path is interpreted as defining a section of your personal 21927folder area. This area and how you specify it are defined by the 21928server, if one is specified in the collection, or, typically, the home 21929directory if no server is defined. 21930 21931<P> 21932To define a collection outside the default "area", prefix 21933the path with the "namespace" to use when interpreting the 21934given path. If a namespace is specified, the Path begins with the 21935sharp, "#", character followed by the name of the namespace 21936and then the namespace's path-element-delimiter. Aside from the 21937path's format, namespaces can also imply access rights, content 21938policy, audience, location, and, occasionally, access methods. 21939 21940<P> 21941Each server exports its own set (possibly of size one) of 21942namespaces. Hence, it's likely communication with your server's 21943administrator will be required for specific configurations. Some of 21944the more common namespaces, however, include: 21945 21946<DL> 21947<DT>#news.</DT> 21948<DD>This specifies a set of folders in the newsgroup namespace. Newsgroup 21949names are hierarchically defined with each level delimited by a period. 21950</DD> 21951<DT>#public/</DT> 21952<DD>This specifies a folder area that the server may export to the general 21953public. 21954</DD> 21955<DT>#shared/</DT> 21956<DD>This specifies a folder area that the folder may export to groups 21957of users. 21958</DD> 21959<DT>#ftp/</DT> 21960<DD>This specifies a folder area that is the same as that it may have 21961exported via the "File Transfer Protocol". 21962</DD> 21963<DT>#mh/</DT> 21964<DD>This specifies the personal folder area associated with folders 21965and directories that were created using the MH message handling system. 21966</DD> 21967</DL> 21968<P> 21969 21970In addition, the server may support access to other user's folders, 21971provided you have suitable permissions. Common methods use a prefix 21972of either "~<VAR>user</VAR>/", or "/<VAR>user</VAR>/" to 21973indicate the root of the other user's folder area. 21974 21975<P> 21976No, nothing's simple. 21977 21978<P> 21979<End of help on this topic> 21980</BODY> 21981</HTML> 21982======= h_composer_cntxt_view ======= 21983<HTML> 21984<HEAD> 21985<TITLE>Collection View: Explained</TITLE> 21986</HEAD> 21987<BODY> 21988<H1>Collection Edit Help -- View Field</H1> 21989 21990The collection's "View:" definition provides a way to limit 21991the displayed list of folders within a collection. By default, only 21992folders that contain the specified characters anywhere in their name 21993are shown in the collection's folder list. 21994 21995<P> 21996Additionally, you can use a wildcard character to better control 21997the list of folders selected for display. The wildcard specifier is 21998the star, "*", character. 21999 22000<P> 22001So, for example, to define a collection of all folders ending with 22002"c", you'd specify a view of "*c" (without the 22003quote characters!). Or, similarly, to define a collection of folders 22004whose names start with "a" and end with "z", you'd 22005specify a view of "a*z". 22006 22007<P> 22008<End of help on this topic> 22009</BODY> 22010</HTML> 22011======= h_composer_abook_add_server ======= 22012<HTML> 22013<HEAD> 22014<TITLE>Addressbook Server Name Field Explained</TITLE> 22015</HEAD> 22016<BODY> 22017This field should be left blank if the address book is stored in a regular 22018file on this system. If it is a remote address book stored on an IMAP 22019server then this is the name of that IMAP server. 22020<P> 22021Look <A HREF="h_edit_nav_cmds">here</A> 22022to see the available Editing and Navigation commands. 22023<P> 22024<End of help on this topic> 22025</BODY> 22026</HTML> 22027======= h_composer_abook_add_folder ======= 22028<HTML> 22029<HEAD> 22030<TITLE>Addressbook Folder Name Field Explained</TITLE> 22031</HEAD> 22032<BODY> 22033For a remote address book (one for which the Server Name is filled in) 22034this is the name of a folder on the remote server. The address book data 22035will be stored in this folder. This folder should be used only for 22036storing this single address book, not for other address books or for 22037other messages. 22038<P> 22039For a local address book (one for which the Server Name is not filled in) 22040this is the name of a file in which the address book will be stored. 22041The file is in the same directory as the Alpine configuration file if the 22042configuration file is local. 22043If the configuration file is remote, then this will be in the home directory 22044for Unix Alpine and in the directory specified by the 22045"-aux local_directory" command line argument. 22046<P> 22047Look <A HREF="h_edit_nav_cmds">here</A> 22048to see the available Editing and Navigation commands. 22049<P> 22050<End of help on this topic> 22051</BODY> 22052</HTML> 22053======= h_composer_abook_add_nick ======= 22054<HTML> 22055<HEAD> 22056<TITLE>Addressbook NickName Field Explained</TITLE> 22057</HEAD> 22058<BODY> 22059This is just an optional nickname for this address book. If present, it 22060is used in some of the displays and error messages in the address book 22061maintenance screens. It is for your convenience only and serves no 22062other purpose. 22063<P> 22064Look <A HREF="h_edit_nav_cmds">here</A> 22065to see the available Editing and Navigation commands. 22066<P> 22067<End of help on this topic> 22068</BODY> 22069</HTML> 22070======= h_composer_qserv_cn ======= 22071<HTML> 22072<HEAD> 22073<TITLE>Directory Query Form Explained</TITLE> 22074</HEAD> 22075<BODY> 22076 22077Fill in as many of these fields as you wish to narrow down your 22078search. All the fields you fill in must match in order for an entry 22079to be returned. You may use the wildcard character "*" in 22080any of the fields, it matches any zero or more characters at that 22081point in the string. There are no implicit wildcards, so the match is 22082exact unless you include wildcards. 22083<P> 22084 22085Note that if an attribute isn't present at all, then the match will fail. 22086For example, if a server doesn't support the Locality attribute, then no 22087matter what you put in the Locality field (other than leaving it empty) 22088the search will fail. 22089<P> 22090 22091This field, the Common Name field, is typically a person's full name. 22092<P> 22093 22094<H1>EDITING and NAVIGATION COMMANDS</H1> 22095<!--chtml if pinemode="function_key"--> 22096<PRE> 22097CURSOR MOTION KEYS----------------------|EDITING KEYS------------------------- 22098^B (Left Arrow) Back character | ^D Delete current character 22099^F (Right Arrow) Forward character | ^H (DEL) Delete previous character 22100^P (Up Arrow) Previous line | 22101^N (Down Arrow) Next line | F9 Cut marked text or 22102^A Beginning of line | delete current line 22103^E End of line | F10 Undelete line(s) 22104F7 Previous page | 22105F8 Next page |------------------------------------- 22106^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS 22107----------------------------------------| 22108EXIT COMMANDS | GENERAL COMMANDS | F5 Restore previous search 22109F2 Cancel | F1 Get help | 22110F3 Search | ^Z Suspend | ^L Redraw Screen 22111</PRE> 22112<!--chtml else--> 22113<PRE> 22114CURSOR MOTION KEYS----------------------|EDITING KEYS------------------------- 22115^B (Left Arrow) Back character | ^D Delete current character 22116^F (Right Arrow) Forward character | ^H (DEL) Delete previous character 22117^P (Up Arrow) Previous line | 22118^N (Down Arrow) Next line | ^K Cut marked text or 22119^A Beginning of line | delete current line 22120^E End of line | ^U Undelete line(s) 22121^Y Previous page | 22122^V Next page |------------------------------------- 22123^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS 22124----------------------------------------| 22125EXIT COMMANDS | GENERAL COMMANDS | ^R Restore previous search 22126^C Cancel | ^G Get help | 22127^X Search | ^Z Suspend | ^L Redraw Screen 22128</PRE> 22129<!--chtml endif--> 22130<P><UL> 22131<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 22132</UL><P> 22133<End of help on this topic> 22134</BODY> 22135</HTML> 22136======= h_composer_qserv_sn ======= 22137 22138The Surname is usually the family name of a person. 22139 22140<End of help on this topic> 22141======= h_composer_qserv_gn ======= 22142 22143This is the part of a person's name that isn't the surname or initials. 22144 22145<End of help on this topic> 22146======= h_composer_qserv_mail ======= 22147 22148This is the email address of a person. 22149 22150<End of help on this topic> 22151======= h_composer_qserv_org ======= 22152 22153This is the organization a person belongs to. 22154 22155<End of help on this topic> 22156======= h_composer_qserv_unit ======= 22157 22158This is the organizational unit a person belongs to. 22159 22160<End of help on this topic> 22161======= h_composer_qserv_country ======= 22162 22163This is the country a person belongs to. 22164 22165<End of help on this topic> 22166======= h_composer_qserv_state ======= 22167 22168This is the state a person belongs to. 22169 22170<End of help on this topic> 22171======= h_composer_qserv_locality ======= 22172 22173This is the locality a person belongs to. 22174 22175<End of help on this topic> 22176======= h_composer_qserv_custom ======= 22177 22178This one is for advanced users only! If you put something in this field, 22179then the rest of the fields are ignored. 22180 22181This field may be set to the string representation of an LDAP search 22182filter (see RFC1960). Here are some examples: 22183 22184To search for an entry with a surname equal to "clinton" you could set 22185the custom filter to: 22186 22187 (sn=clinton) 22188 22189This is equivalent to putting "clinton" in the SurName field. 22190To search for an entry that has a surname that begins with "clint" and 22191has a givenname equal to "william" you could use: 22192 22193 (&(sn=clint*)(givenname=william)) 22194 22195This is equivalent to setting the SurName field to "clint*" and the 22196GivenName field to "william". 22197To search for an entry where either the common name OR the email address 22198contains "abcde" you could use: 22199 22200 (|(cn=*abcde*)(mail=*abcde*)) 22201 22202That isn't equivalent to anything you can do by setting the other fields 22203because of the OR. 22204 22205<End of help on this topic> 22206======= h_composer_qserv_qq ======= 22207 22208This one is a little different from the rest of the categories. It causes 22209a search to be formed from the configured search filter that you filled 22210in when you added the directory server to your configuration. It can also 22211be combined with the other fields if you'd like. 22212 22213<End of help on this topic> 22214======= h_address_format ======= 22215<HTML> 22216<HEAD> 22217<TITLE>INTERNET EMAIL ADDRESS FORMAT</TITLE> 22218</HEAD> 22219<BODY> 22220<H1>INTERNET EMAIL ADDRESS FORMAT</H1> 22221 22222A valid email address on the Internet has a username, an "@" sign, 22223and then a domain, with no spaces. 22224For example, jsmith@art.example.com might be the email address 22225of a person 22226with the username "jsmith" who has an account in the domain 22227"art.example.com". The number of dot-separated segments on the 22228right of the "@" sign can vary - a shorter example would be 22229isabelle@elsewhere.edu (the shortest possible form: here, only the 22230organization's domain is specified after the "@" sign); a longer 22231example would be 22232 jsingh@shakti.edutech.example.com 22233(here, the name of the host "shakti" in the domain 22234edutech.example.com is also specified). 22235<P> 22236If you do not know the exact email address of someone you want to write 22237to, ask them what it is using other means of communication than email; or 22238use the tools for 22239finding people's addresses that are available on the Internet. 22240<P> 22241If you are sending to someone on the same system as you are, you can leave 22242the "@" sign and all the information to its right off of the 22243address, and Alpine will fill it in automatically, 22244unless the feature 22245<A HREF="h_config_compose_rejects_unqual">"<!--#echo var="FEAT_compose-rejects-unqualified-addrs"-->"</A> is set in SETUP CONFIGURATION. 22246<P> 22247 22248When an email address you send a message to is not reachable -- either because 22249it is simply an incorrect address, or because email can temporarily not be 22250delivered to it due to a technical problem on the way to or at the recipient's 22251end -- you will almost always get an error notification email message back. 22252<P> 22253If you encounter problems with, or have questions about, email delivery or 22254email address syntax, contact your local network computing consultants. 22255<P><UL> 22256<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 22257</UL> 22258<P> 22259<End of help on this topic> 22260</BODY> 22261</HTML> 22262======= h_flag_user_flag ======= 22263<HTML> 22264<HEAD> 22265<TITLE>STATUS FLAG: User Defined Keyword</TITLE> 22266</HEAD> 22267<BODY> 22268<H1>STATUS FLAG: User Defined Keyword</h1> 22269 22270This is a keyword that is defined for this folder. 22271It was most likely defined by the owner of the folder. 22272Alpine will not set or clear this flag on its own. 22273 22274<P><UL> 22275<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 22276</UL><P> 22277<End of help on this topic> 22278</BODY> 22279</HTML> 22280======= h_flag_important ======= 22281<html> 22282<title>STATUS FLAG: Important</title> 22283<body> 22284<h1>STATUS FLAG: Important</h1> 22285 22286 22287The <EM>Important</EM> flag, indicated by an asterisk in Alpine's 22288MESSAGE INDEX 22289screen, can only be set by the user, and is intended to be used in 22290whatever fashion makes sense to you. You are the only one that can set or 22291clear it. 22292 22293<P> 22294<End of help on this topic> 22295</BODY> 22296</HTML> 22297======= h_flag_new ======= 22298<html> 22299<title>STATUS FLAG: New</title> 22300<body> 22301<h1>STATUS FLAG: New</h1> 22302 22303 22304The <EM>New</EM> flag, indicated by the letter 'N' in Alpine's 22305MESSAGE INDEX screen, 22306is automatically set when messages are delivered to your Inbox (or other 22307folder specified outside of Alpine). Likewise, it is cleared automatically 22308the first time you read the message it is associated with. 22309 22310<P> 22311Sometimes it's helpful in prioritizing your mail. For example, perhaps 22312a message isn't weighty enough to assign it an <A HREF="h_flag_important">Important</A> flag, but 22313you'd like to be reminded of it next time you read mail. This can be done 22314easily by <A HREF="h_common_flag">explicitly</A> resetting the <EM>New</EM> flag. 22315 22316 22317<P> 22318<End of help on this topic> 22319</BODY> 22320</HTML> 22321======= h_flag_answered ======= 22322<html> 22323<title>STATUS FLAG: Answered</title> 22324<body> 22325<h1>STATUS FLAG: Answered</h1> 22326 22327The <EM>Answered</EM> flag, indicated by the letter 'A' in Alpine's 22328MESSAGE INDEX 22329screen, is automatically set when you reply to a message. This flag is not 22330automatically cleared. 22331 22332<P> 22333<End of help on this topic> 22334</BODY> 22335</HTML> 22336======= h_flag_forwarded ======= 22337<html> 22338<title>STATUS FLAG: Forwarded</title> 22339<body> 22340<h1>STATUS FLAG: Forwarded</h1> 22341 22342The <EM>Forwarded</EM> flag, indicated by the letter 'F' in Alpine's 22343MESSAGE INDEX 22344screen, is automatically set when you forward a message. This flag is not 22345automatically cleared. 22346 22347<P> 22348<End of help on this topic> 22349</BODY> 22350</HTML> 22351======= h_flag_deleted ======= 22352<html> 22353<title>STATUS FLAG: Deleted</title> 22354<body> 22355<h1>STATUS FLAG: Deleted</h1> 22356 22357The <EM>Deleted</EM> flag, indicated by the letter 'D' in Alpine's 22358MESSAGE INDEX 22359screen, is set when you use the ""D Delete" command. 22360It is cleared 22361when you use the "U Undelete" command. 22362 22363<P> 22364Messages marked with this flag will be permanently removed from 22365the folder when you issue the <A HREF="h_index_cmd_expunge">Expunge</A> 22366command, or 22367when you indicate acceptance of their removal upon leaving the folder. 22368 22369<P> 22370Note, there can be other actions implicit in the 22371"D Delete" command, 22372such as advancing to the next message, that may be momentarily undesirable. 22373For this reason, it's sometimes useful to set or clear the <EM>Deleted</EM> 22374flag <A HREF="h_common_flag">explicitly</A>. 22375 22376<P> 22377<End of help on this topic> 22378</BODY> 22379</HTML> 22380====== h_config_incoming_timeo ====== 22381<HTML> 22382<HEAD> 22383<TITLE>OPTION: <!--#echo var="VAR_incoming-check-timeout"--></TITLE> 22384</HEAD> 22385<BODY> 22386<H1>OPTION: <!--#echo var="VAR_incoming-check-timeout"--></H1> 22387 22388This option has no effect unless the feature 22389<A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A> 22390is set, which in turn has no effect unless 22391<A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A> 22392is set. 22393<P> 22394Sets the time in seconds that Alpine will 22395attempt to open a network connection used for monitoring for Unseen 22396messages in Incoming Folders. The default is 5. 22397If a connection has not completed within this many seconds Alpine will 22398give up and consider it a failed connection. 22399<P> 22400<UL> 22401<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 22402</UL><P> 22403<End of help on this topic> 22404</BODY> 22405</HTML> 22406====== h_config_incoming_interv ====== 22407<HTML> 22408<HEAD> 22409<TITLE>OPTION: <!--#echo var="VAR_incoming-check-interval"--></TITLE> 22410</HEAD> 22411<BODY> 22412<H1>OPTION: <!--#echo var="VAR_incoming-check-interval"--></H1> 22413 22414This option has no effect unless the feature 22415<A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A> 22416is set, which in turn has no effect unless 22417<A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A> 22418is set. 22419<P> 22420This option specifies, in seconds, how often Alpine will check 22421for new mail and state changes in Incoming Folders when Incoming Folders 22422Checking is turned on. 22423The default is 3 minutes (180). 22424This value applies only to folders that are local to the system that 22425Alpine is running on or that are accessed using the IMAP protocol. 22426The similar option 22427<A HREF="h_config_incoming_second_interv"><!--#echo var="VAR_incoming-check-interval-secondary"--></A> 22428applies to all other monitored folders. 22429<P> 22430<UL> 22431<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 22432</UL><P> 22433<End of help on this topic> 22434</BODY> 22435</HTML> 22436====== h_config_incoming_second_interv ====== 22437<HTML> 22438<HEAD> 22439<TITLE>OPTION: <!--#echo var="VAR_incoming-check-interval-secondary"--></TITLE> 22440</HEAD> 22441<BODY> 22442<H1>OPTION: <!--#echo var="VAR_incoming-check-interval-secondary"--></H1> 22443 22444This option has no effect unless the feature 22445<A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A> 22446is set, which in turn has no effect unless 22447<A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A> 22448is set. 22449<P> 22450This option together with the option 22451<A HREF="h_config_incoming_interv"><!--#echo var="VAR_incoming-check-interval"--></A> 22452specifies, in seconds, how often Alpine will check 22453for new mail and state changes in Incoming Folders when Incoming Folders 22454Checking is turned on. 22455The default for this option is 3 minutes (180). 22456For folders that are local to this system or 22457that are accessed using the IMAP protocol 22458the value of the option 22459<A HREF="h_config_incoming_interv"><!--#echo var="VAR_incoming-check-interval"--></A> 22460is used. 22461For all other monitored folders, the value of this option is used. 22462<P> 22463The reason there are two separate options is because it is usually 22464less expensive to check local and IMAP folders than it is to check 22465other types, like POP or NNTP folders. 22466You may want to set this secondary value to a higher number than 22467the primary check interval. 22468<P> 22469<UL> 22470<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 22471</UL><P> 22472<End of help on this topic> 22473</BODY> 22474</HTML> 22475====== h_config_incoming_list ====== 22476<HTML> 22477<HEAD> 22478<TITLE>OPTION: <!--#echo var="VAR_incoming-check-list"--></TITLE> 22479</HEAD> 22480<BODY> 22481<H1>OPTION: <!--#echo var="VAR_incoming-check-list"--></H1> 22482 22483This option has no effect unless the feature 22484<A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A> 22485is set, which in turn has no effect unless 22486<A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A> 22487is set. 22488<P> 22489When monitoring the Incoming Message Folders for Unseen messages Alpine will 22490normally monitor all Incoming Folders. 22491You may use this option to restrict the list of monitored folders to a 22492subset of all Incoming Folders. 22493<P> 22494<UL> 22495<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 22496</UL><P> 22497<End of help on this topic> 22498</BODY> 22499</HTML> 22500====== h_config_pers_name ====== 22501<HTML> 22502<HEAD> 22503<TITLE>OPTION: <!--#echo var="VAR_personal-name"--></TITLE> 22504</HEAD> 22505<BODY> 22506<H1>OPTION: <!--#echo var="VAR_personal-name"--></H1> 22507 22508This value is used to determine the full name part of the "From" address 22509on messages you send. 22510<!--chtml if pinemode="os_windows"--> 22511 PC-Alpine requires that this be set in order to properly construct the "From" address. 22512<!--chtml else--> 22513 If unset, Unix Alpine will obtain your full name from 22514 the system password file. PC-Alpine, on the other hand, requires that this be set. 22515<!--chtml endif--> 22516<P> 22517If you want to change the value of what gets included in the From header 22518in messages you send (other than just the Personal Name) 22519look <A HREF="h_config_change_your_from">here</A> for a description. 22520<P><UL> 22521<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 22522</UL><P> 22523<End of help on this topic> 22524</BODY> 22525</HTML> 22526====== h_config_pruned_folders ====== 22527<html> 22528<header> 22529<title>OPTION: <!--#echo var="VAR_pruned-folders"--></title> 22530</header> 22531<body> 22532<h1>OPTION: <!--#echo var="VAR_pruned-folders"--></h1> 22533 22534This variable allows you to define a list of one or more folders that 22535Alpine will offer to prune for you in the same way it automatically offers 22536to prune your "sent-mail" folder each month. 22537Each folder in this list must be a folder in your default folder collection 22538(the first folder collection if you have more than one), and it is just 22539the relative name of the folder in the collection, not the fully-qualified name. 22540It is similar to sent-mail. 22541Instead of something like 22542<P> 22543<CENTER><SAMP><!--#echo var="VAR_pruned-folders"-->={servername}mail/folder</SAMP></CENTER> 22544<P> 22545the correct value to use would be 22546<P> 22547<CENTER><SAMP>folder</SAMP></CENTER> 22548<P> 22549There is an assumption here that your first collection is the folders in 22550<P> 22551<CENTER><SAMP>{servername}mail</SAMP></CENTER> 22552<P> 22553 22554Once a month, for each folder listed, Alpine will offer to move 22555the contents of the folder to a new folder of the same name but with 22556the previous month's date appended. Alpine will then look for any such 22557date-appended folder names created for a previous month, and offer each 22558one it finds for deletion. 22559<P> 22560 22561If you decline the first offer, no mail is moved and no new folder is 22562created. 22563<P> 22564 22565The new folders will be created 22566in your default folder collection. 22567<P> 22568 22569<UL> 22570<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 22571</UL><P> 22572<End of help on this topic> 22573</body> 22574</html> 22575====== h_config_upload_cmd ====== 22576<HTML> 22577<HEAD> 22578<TITLE>OPTION: <!--#echo var="VAR_upload-command"--></TITLE> 22579</HEAD> 22580<BODY> 22581<H1>OPTION: <!--#echo var="VAR_upload-command"--></H1> 22582 22583This option affects the behavior of the Composer's "Read File" 22584(^R in the message body) and "Attach File" (^J in the header) 22585commands. It specifies 22586a Unix program name, and any necessary command line arguments, that Alpine can 22587use to transfer files from your personal computer into messages that you are 22588composing.<P> 22589 22590<B>Note:</B> this facility is intended for use with serial line transfer 22591protocols, such as kermit, xmodem, or zmodem. It is <B>not</B> intended 22592to work with TCP/IP file transfer programs such as ftp.<P> 22593 22594If a program is specified, the commands listed above are modified to offer a 22595subcommand (^Y) to activate the transfer. Obviously, the Unix program 22596specified here must match the transfer program or protocol available on the 22597personal computer.<P> 22598 22599Alpine expects to exchange uploaded data via a file on your Unix system. When 22600the specified upload program finishes, Alpine expects the uploaded data to be 22601contained in this file.<P> 22602 22603When upload is invoked via the "Read File" subcommand, Alpine 22604generates a 22605temporary file name that it will pass to the specified Unix program. Alpine 22606will read the resulting uploaded text from this file and then delete it when 22607the upload command is finished.<P> 22608 22609When upload is invoked via the "Attach File" subcommand, Alpine will 22610prompt 22611you for the name of the file that is to contain the uploaded information that 22612it is to attach. Alpine will attach this file to the composition, but will 22613<B>not</B> delete this file after the upload command is finished.<P> 22614 22615The special token "_FILE_" may be included among the Unix program's 22616command 22617line arguments. Alpine will replace this symbol with the name of the file 22618being used to exchange the uploaded information. This token allows you to 22619position the file name where it is required in the Unix program's command 22620line arguments.<P> 22621 22622If the "_FILE_" token is not present in the specified command, the 22623temporary file's name is automatically appended to the specified Unix 22624program. In other words, you don't need to use "_FILE_" if it is the 22625<B>last</B> command line argument. 22626<P><UL> 22627<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 22628</UL><P> 22629<End of help on this topic> 22630</BODY> 22631</HTML> 22632====== h_config_upload_prefix ====== 22633<HTML> 22634<HEAD> 22635<TITLE>OPTION: <!--#echo var="VAR_upload-command-prefix"--></TITLE> 22636</HEAD> 22637<BODY> 22638<H1>OPTION: <!--#echo var="VAR_upload-command-prefix"--></H1> 22639 22640This option is used in conjunction with the <!--#echo var="VAR_upload-command"--> option. 22641It defines text to be written to the terminal emulator (via standard output) 22642immediately prior to starting upload command. This is useful for 22643integrated serial line file transfer agents that permit command passing 22644(e.g., Kermit's APC method).<P> 22645 22646The special token "_FILE_" may be included in the string specification. 22647That symbol will be replaced with the (Alpine-created) name of the temporary 22648file in which Alpine will expect to find the uploaded file. 22649<P><UL> 22650<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 22651</UL><P> 22652<End of help on this topic> 22653</BODY> 22654</HTML> 22655====== h_config_download_cmd ====== 22656<HTML> 22657<HEAD> 22658<TITLE>OPTION: <!--#echo var="VAR_download-command"--></TITLE> 22659</HEAD> 22660<BODY> 22661<H1>OPTION: <!--#echo var="VAR_download-command"--></H1> 22662 22663This option affects the behavior of the Export command. It specifies a Unix 22664program name, and any necessary command line arguments, that Alpine can use to 22665transfer the exported message to your personal computer's disk.<P> 22666Note: this facility is intended for use with serial line transfer 22667protocols, such as kermit, xmodem, or zmodem. It is <B>not</B> intended 22668to work with TCP/IP file transfer programs such as ftp.<P> 22669If a program is specified, the Export command is modified to offer a 22670subcommand (^V) to activate the transfer (in lieu of saving it to 22671 the machine where Alpine is running). Obviously, the Unix program 22672specified here must match the transfer program or protocol available on the 22673personal computer.<P> 22674 22675When this subcommand is selected and before Alpine invokes the specified Unix 22676program, Alpine will create a temporary file containing the text of the 22677exported message. Alpine uses this file to pass the exported message text to 22678the specified Unix program.<P> 22679 22680The special token "_FILE_" may be included among the Unix program's command 22681line arguments. Alpine will replace this symbol with the temporary file's name 22682before executing the Unix program. This token allows you to position the 22683file name where it is required in the Unix program's command line arguments. 22684<P> 22685If the "_FILE_" token is not present in the specified command, the 22686temporary file's name is automatically appended to the specified Unix 22687program. In other words, you don't need to use "_FILE_" if it is the 22688<B>last</B> command line argument. 22689<P><UL> 22690<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 22691</UL><P> 22692<End of help on this topic> 22693</BODY> 22694</HTML> 22695====== h_config_download_prefix ====== 22696<HTML> 22697<HEAD> 22698<TITLE>OPTION: <!--#echo var="VAR_download-command-prefix"--></TITLE> 22699</HEAD> 22700<BODY> 22701<H1>OPTION: <!--#echo var="VAR_download-command-prefix"--></H1> 22702 22703This option is used in conjunction with the <!--#echo var="VAR_download-command"--> option. 22704It defines text to be written to the terminal emulator (via standard output) 22705immediately prior to starting the download command. This is useful for 22706integrated serial line file transfer agents that permit command passing 22707(e.g., Kermit's APC method). 22708<P> 22709The special token "_FILE_" may be included in the string 22710specification. 22711That symbol will be replaced with the (Alpine-created) name of the temporary 22712file into which Alpine will place the message to be downloaded. 22713<P><UL> 22714<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 22715</UL><P> 22716<End of help on this topic> 22717</BODY> 22718</HTML> 22719====== h_config_mailcap_path ====== 22720<HTML> 22721<HEAD> 22722<TITLE>OPTION: <!--#echo var="VAR_mailcap-search-path"--></TITLE> 22723</HEAD> 22724<BODY> 22725<H1>OPTION: <!--#echo var="VAR_mailcap-search-path"--></H1> 22726This variable is used to replace Alpine's default mailcap file search path. 22727It takes one or more file names (full paths must be specified) in which to 22728look for mail capability data. The default search path can be found in this 22729<A HREF="h_news_config">Alpine Configuration</A> help, near the bottom. 22730If there is more than one file name listed, list members should be delimited 22731by 22732<!--chtml if pinemode="os_windows"--> 22733a semi-colon (;) under Windows; for example:<PRE> 22734 C:\MYCONFIG\MAILCAP.TXT;H:\NETCONFIG\MAILCAP.TXT 22735</PRE> 22736<!--chtml else--> 22737a colon (:) under UNIX; for example:<PRE> 22738 ~/.mailcap:/etc/mailcap:/usr/etc/mailcap:/usr/local/etc/mailcap 22739</PRE> 22740<!--chtml endif--> 22741<P><UL> 22742<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 22743</UL> 22744<P> 22745<End of help on this topic> 22746</BODY> 22747</HTML> 22748====== h_config_mimetype_path ====== 22749<HTML> 22750<HEAD> 22751<TITLE>OPTION: <!--#echo var="VAR_mimetype-search-path"--></TITLE> 22752</HEAD> 22753<BODY> 22754<H1>OPTION: <!--#echo var="VAR_mimetype-search-path"--></H1> 22755 22756This variable is used to replace Alpine's default mime.types file search path. 22757It takes one or more file names (full paths must be specified) in which to 22758look for file-name-extension to MIME type mapping data. The default search 22759path can be found in this 22760<A HREF="h_news_config">Alpine Configuration</A> help. 22761 22762<P> 22763 22764If there is more than one file name listed, list members should be delimited 22765by a colon (:) under UNIX and a semi-colon (;) under Windows. 22766<P> 22767<End of help on this topic> 22768</BODY></HTML> 22769====== h_config_system_certs_path ====== 22770<HTML> 22771<HEAD> 22772<TITLE>OPTION: <!--#echo var="VAR_system-certs-path"--></TITLE> 22773</HEAD> 22774<BODY> 22775<H1>OPTION: <!--#echo var="VAR_system-certs-path"--></H1> 22776 22777When Alpine is built to support secure connections to remote servers, a directory 22778must be reserved in the system to store certificates that will be used to validate 22779remote servers. This is normally configured at the time that Alpine is built, but 22780there might be circumstances under which a user might want to use a different 22781directory. For example, the directory might not be accessible, or has not been 22782updated and contains old certificates that have expired. 22783 22784<P> 22785This variable can be used to list 22786the directory where such certificates can be found. Alpine will use the first 22787directory in this list that exists in your system and can be accessed. This 22788allows for users to be able to use the same pinerc file in different systems. 22789 22790<P> 22791Example of values for this option might be: 22792 22793<PRE> 22794System CACerts Dir = /etc/ssl/certs 22795 /usr/local/ssl/certs 22796 C:\\libressl\\ssl\\certs 22797<PRE> 22798 22799<P> 22800In unix systems, the default location of the certificates for openssl can 22801be obtained by first executing the command 22802 22803<PRE>openssl version -d</PRE> 22804 22805and adding "/certs" to that value. In Windows the default location 22806for the certificates is C:\\libressl\\ssl\\certs. This value was set by 22807LibreSSL developers, and this option can be used to override this default. 22808 22809<P> 22810<End of help on this topic> 22811</BODY></HTML> 22812====== h_config_system_certs_file ====== 22813<HTML> 22814<HEAD> 22815<TITLE>OPTION: <!--#echo var="VAR_system-certs-file"--></TITLE> 22816</HEAD> 22817<BODY> 22818<H1>OPTION: <!--#echo var="VAR_system-certs-file"--></H1> 22819 22820This option sets the location of the container file that holds 22821certificate authority (CA) certificates. 22822Alpine will use the first 22823container in this list that exists in your system and can be accessed. This 22824allows for users to be able to use the same pinerc file in different systems. 22825 22826<P> 22827Example of values for this option might be: 22828 22829<PRE> 22830System CACerts File = /etc/ssl/certs/cert.pem 22831 /usr/local/ssl/ca-root-nss.crt 22832 C:\\libressl\\ssl\\certs\\cert.pem 22833<PRE> 22834 22835<P> 22836In unix systems, the default location of the certificates for openssl can 22837be obtained by first executing the command 22838 22839<PRE>openssl version -d</PRE> 22840 22841and adding "/certs" to that value. In Windows the default location 22842for the certificates is C:\\libressl\\ssl\\certs\\cert.pem. This value was set 22843by LibreSSL developers, and this option can be used to override this default. 22844 22845<P> 22846<End of help on this topic> 22847</BODY></HTML> 22848====== h_config_user_certs_path ====== 22849<HTML> 22850<HEAD> 22851<TITLE>OPTION: <!--#echo var="VAR_user-certs-path"--></TITLE> 22852</HEAD> 22853<BODY> 22854<H1>OPTION: <!--#echo var="VAR_user-certs-path"--></H1> 22855 22856(UNIX ALPINE ONLY) 22857This directory is used by Alpine to store certificates that a user 22858trusts. Alpine will use the first directory in this list that exists in your 22859system and can be accessed. This allows for users to be able to 22860use the same pinerc file in different systems. The default location 22861is ~/.alpine-certs. 22862 22863<P> 22864In addition to the certificates stored in this directory, Alpine also 22865trusts certificates saved in the container file referenced in the 22866configuration variable 22867<A HREF="h_config_user_certs_file"><!--#echo var="VAR_user-certs-file"--></A>. 22868 22869<P> 22870Example of values for this option might be: 22871 22872<PRE> 22873User Certs Dir = /home/fred/.alpine-certs 22874 C:\\Users\\Admin\\alpine-certs 22875<PRE> 22876 22877<P> 22878<End of help on this topic> 22879</BODY></HTML> 22880====== h_config_user_certs_file ====== 22881<HTML> 22882<HEAD> 22883<TITLE>OPTION: <!--#echo var="VAR_user-certs-file"--></TITLE> 22884</HEAD> 22885<BODY> 22886<H1>OPTION: <!--#echo var="VAR_user-certs-file"--></H1> 22887 22888(UNIX ALPINE ONLY) 22889This option sets the location of a container file that holds certificate 22890authority (CA) certificates that the user trusts. Its value is the 22891full path referencing the location of this file. Alpine will use the first 22892container in this list that exists and can be accessed in your system. This 22893allows for users to be able to use the same pinerc file in different 22894systems. The default location is ~/.alpine-certs/certs.pem. 22895 22896<P> 22897In addition to the certificates stored in this directory, Alpine also 22898trusts certificates saved in the directory referenced in the 22899configuration variable 22900<A HREF="h_config_user_certs_path"><!--#echo var="VAR_user-certs-path"--></A>. 22901 22902<P> 22903Example of values for this option might be: 22904 22905<PRE> 22906User Certs File = /home/fred/.alpine-certs/certs.pem 22907 C:\\libressl\\ssl\\certs\\cert.pem 22908<PRE> 22909 22910<P> 22911<End of help on this topic> 22912</BODY></HTML> 22913====== h_config_ssl_ciphers ====== 22914<HTML> 22915<HEAD> 22916<TITLE>OPTION: <!--#echo var="VAR_ssl-ciphers"--></TITLE> 22917</HEAD> 22918<BODY> 22919<H1>OPTION: <!--#echo var="VAR_ssl-ciphers"--></H1> 22920 22921(UNIX ALPINE ONLY) 22922This is a colon separated list of ciphers that your openssl or libressl 22923library supports and should use to negotiate a secure connection with a 22924remote SSL server. 22925 22926<P> 22927The list of ciphers supported by openssl can be obtained with the command 22928line command 22929 22930<P> 22931openssl ciphers 22932 22933<P> 22934Consult the manual page of the openssl ciphers command to see more 22935ways to specify groups of ciphers, such as RSA, or other groups of 22936ciphers. 22937 22938<P> 22939<End of help on this topic> 22940</BODY></HTML> 22941====== h_config_set_att_ansi ====== 22942<HTML><HEAD> 22943<TITLE>OPTION: Set printer to attached ansi printer</TITLE> 22944</HEAD> 22945<BODY> 22946<H1>OPTION: Set printer to attached ansi printer</H1> 22947 22948Type "S" to set your printer to "attached-to-ansi".<BR> 22949It is OK to include "attached-to-ansi" in your personal list below. 22950<P> 22951<End of help on this topic> 22952</BODY></HTML> 22953====== h_config_set_att_ansi2 ====== 22954<HTML><HEAD> 22955<TITLE>OPTION: Set printer to attached ansi printer (no formfeed)</TITLE> 22956</HEAD> 22957<BODY> 22958<H1>OPTION: Set printer to attached ansi printer (no formfeed)</H1> 22959 22960Type "S" to set your printer to "attached-to-ansi-no-formfeed".<BR> 22961It is OK to include "attached-to-ansi-no-formfeed" in your personal 22962list below. 22963 22964<P> 22965 22966This is the same as the "attached-to-ansi" option except that a 22967formfeed character will not be appended to the end of the print job. 22968If your printer already ejects the paper by itself at the end of the 22969job, you may prefer the "no-formfeed" form of this printer so that you 22970don't get an extra blank page between print jobs. 22971<P> 22972 22973<End of help on this topic> 22974</BODY></HTML> 22975====== h_config_set_att_wyse ====== 22976<HTML><HEAD> 22977<TITLE>OPTION: Set printer to attached Wyse60 printer</TITLE> 22978</HEAD> 22979<BODY> 22980<H1>OPTION: Set printer to attached Wyse60 printer</H1> 22981 22982Type "S" to set your printer to "attached-to-wyse".<BR> 22983It is OK to include "attached-to-wyse" in your personal list below. 22984<P> 22985This is very similar to "attached-to-ansi". 22986The only difference is in the control characters sent to turn the printer 22987on and off. 22988The ansi version of the printer uses ESC LEFT_BRACKET 5 i 22989to turn on the printer and ESC LEFT_BRACKET 4 i 22990to turn it off. 22991The Wyse version uses Ctrl-R for on, and Ctrl-T for off. 22992<End of help on this topic> 22993</BODY></HTML> 22994====== h_config_set_att_wyse2 ====== 22995<HTML><HEAD> 22996<TITLE>OPTION: Set printer to attached Wyse60 printer (no formfeed)</TITLE> 22997</HEAD> 22998<BODY> 22999<H1>OPTION: Set printer to attached Wyse60 printer (no formfeed)</H1> 23000 23001Type "S" to set your printer to "attached-to-wyse-no-formfeed".<BR> 23002It is OK to include "attached-to-wyse-no-formfeed" in your personal 23003list below. 23004 23005<P> 23006 23007This is the same as the "attached-to-wyse" option except that a 23008formfeed character will not be appended to the end of the print job. 23009If your printer already ejects the paper by itself at the end of the 23010job, you may prefer the "no-formfeed" form of this printer so that you 23011don't get an extra blank page between print jobs. 23012<P> 23013 23014<End of help on this topic> 23015</BODY></HTML> 23016====== h_config_set_stand_print ====== 23017<HTML> 23018<HEAD> 23019<TITLE>OPTION: Set default printer</TITLE> 23020</HEAD> 23021<H1>OPTION: Set default printer</H1> 23022<BODY> 23023Move to the printer you want and type "S" to set it to be your 23024default printer. This list is not modifiable by you and has been 23025set up by the system administrators. If there is more than one printer 23026listed in the Command List, you will be able to cycle through that 23027whole list at the time you print, starting with your default. 23028It is OK to include entries from this Standard list in your personal 23029list below. 23030<P> 23031<End of help on this topic> 23032</BODY> 23033</HTML> 23034====== h_config_set_custom_print ====== 23035<HTML> 23036<HEAD> 23037<TITLE>OPTION: Set default printer</TITLE> 23038</HEAD> 23039<H1>OPTION: Set default printer</H1> 23040<BODY> 23041You may add as many print commands as you want to your personal list. 23042Specify one of them as your default printer by moving to the printer 23043you want and typing "S". If there is more than one printer listed 23044in the Command List, you will be able to cycle through that list at 23045the time you print, starting with your default. It is OK to include 23046entries from the Standard list above or to include the command 23047"attached-to-ansi", "attached-to-ansi-no-formfeed", "attached-to-wyse", or 23048"attached-to-wyse-no-formfeed" as one of the entries here. 23049<P> 23050<End of help on this topic> 23051</BODY> 23052</HTML> 23053====== h_config_user_id ===== 23054<HTML> 23055<HEAD> 23056<TITLE>OPTION: <!--#echo var="VAR_user-id"--></TITLE> 23057</HEAD> 23058<BODY> 23059<H1>OPTION: <!--#echo var="VAR_user-id"--></H1> 23060 23061This value is used as part of the "From" address on messages you send. 23062It is also the default login name for remote IMAP server access. Set this 23063to the username part you want to appear on outgoing email. 23064<P> 23065If you want to change the value of what gets included in the From header 23066in messages you send (other than just the User ID) 23067look <A HREF="h_config_change_your_from">here</A> for a description. 23068 23069<P><UL> 23070<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 23071</UL><P> 23072<End of help on this topic> 23073</BODY> 23074</HTML> 23075====== h_config_user_dom ===== 23076<HTML> 23077<HEAD> 23078<TITLE>OPTION: <!--#echo var="VAR_user-domain"--></TITLE> 23079</HEAD> 23080<BODY> 23081<H1>OPTION: <!--#echo var="VAR_user-domain"--></H1> 23082 23083This value specifies the domain part (right-hand side) of your return 23084address on outgoing email and is also used as the default domain for email 23085composed to a local user. 23086<!--chtml if pinemode="os_windows"--> 23087 This value is required for PC-Alpine. If you are unsure as to what this should be, 23088 contact your local help desk, system administrator, or Internet Service Provider. 23089<!--chtml else--> 23090 If unset, Unix Alpine will obtain the domain from 23091 the system. Often this value will be set for your whole site by the 23092 system administrator.<P> 23093<!--chtml endif--> 23094If you set this, see also the <A HREF="h_config_quell_local_lookup"> 23095"<!--#echo var="FEAT_quell-user-lookup-in-passwd-file"-->"</A> feature. 23096<P> 23097If you want to change the value of what gets included in the From header 23098in messages you send (other than just the User Domain) 23099look <A HREF="h_config_change_your_from">here</A> for a description. 23100<P><UL> 23101<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 23102</UL><P> 23103<End of help on this topic> 23104</BODY> 23105</HTML> 23106====== h_config_smtp_server ===== 23107<HTML> 23108<HEAD> 23109<TITLE>OPTION: <!--#echo var="VAR_smtp-server"--></TITLE> 23110</HEAD> 23111<BODY> 23112<H1>OPTION: <!--#echo var="VAR_smtp-server"--></H1> 23113This value specifies the name of one or more SMTP 23114(Simple Mail Transfer Protocol) servers for sending mail. 23115<!--chtml if pinemode="os_windows"--> 23116You must have an SMTP server for use with PC-Alpine. 23117SMTP servers are 23118normally set up by a system administrator for use by all members of a given 23119campus or department. 23120Contact your local help desk to ask what SMTP 23121servers you should use. 23122<!--chtml else--> 23123Unix Alpine users may not need to set an SMTP server. 23124Alpine will attempt to execute the program (usually sendmail) that is used 23125to insert mail into the mail system. 23126If this works for you, you may leave this option blank. 23127If there is an SMTP server running on the Unix host you may be able to 23128improve sending performance slightly by setting the SMTP server option 23129to "localhost" or to the actual name of the Unix host. 23130<P> 23131If the Unix host doesn't work the way Alpine was expecting you will need to 23132set the value of this option. 23133SMTP servers are 23134normally set up by a system administrator for use by all members of a given 23135campus or department. 23136Contact your local help desk to ask what SMTP 23137servers you should use. 23138<!--chtml endif--> 23139<P> 23140Your SMTP server may offer SMTP AUTH authentication. 23141It may even require it. 23142If your SMTP server offers SMTP AUTH authentication you may specify a 23143"user" name parameter to cause Alpine to attempt to authenticate. 23144This parameter requires an associated value, 23145the username identifier with which to establish the server 23146connection. 23147An example might be: 23148 23149<P> 23150<CENTER><SAMP>smtpserver.example.com/user=katie</SAMP></CENTER> 23151<P> 23152 23153If AUTH authentication is offered by the server, this will cause Alpine to 23154attempt to use it. 23155If AUTH authentication is not offered by the server, this will cause Alpine 23156to fail sending with an error similar to: 23157 23158<P> 23159<CENTER><SAMP>Error: SMTP authentication not available</SAMP></CENTER> 23160<P> 23161 23162Another type of authentication that is used by some ISPs is called 23163"POP before SMTP" or "IMAP before SMTP", 23164which means that you have to authenticate 23165yourself to the POP or IMAP server by opening a mailbox before you 23166can send mail. 23167To do this, you usually only have to open your INBOX. 23168 23169<P> 23170You may tell Alpine to use the 23171<A HREF="http://www.ietf.org/rfc/rfc2476.txt">Message Submission</A> 23172port (587) instead of the SMTP port (25) by including the "submit" 23173parameter 23174in this option. 23175At this time "/submit" is simply equivalent to specifying 23176port 587, though it may imply more than that at some point in the future. 23177Some ISPs are blocking port 25 in order to reduce the amount of spam 23178being sent to their users. 23179You may find that the submit option allows you to get around such a block. 23180 23181<P> 23182<CENTER><SAMP>smtpserver.example.com/submit</SAMP></CENTER> 23183<P> 23184 23185To specify any non-standard port number on the SMTP server you may follow 23186the hostname with a colon followed by the portnumber. 23187 23188<P> 23189<CENTER><SAMP>smtpserver.example.com:12345</SAMP></CENTER> 23190<P> 23191 23192Normally, when a connection is made to the Smtp-Server Alpine will attempt 23193to negotiate a secure (encrypted) session using Transport Layer Security (TLS). 23194If that fails then a non-encrypted connection will be attempted instead. 23195You may specify that a TLS connection is required if you wish. 23196If you append "/starttls" to the name then the connection will fail 23197instead of falling back to a non-secure connection. 23198 23199<P> 23200<CENTER><SAMP>smtpserver.example.com/starttls</SAMP></CENTER> 23201<P> 23202 23203 23204For more details about server name possibilities see 23205<A HREF="h_folder_server_syntax">Server Name Syntax</A>. 23206<P> 23207 23208<UL> 23209<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 23210</UL> 23211<P> 23212<End of help on this topic> 23213</BODY> 23214</HTML> 23215====== h_config_nntp_server ===== 23216<HTML> 23217<HEAD> 23218<TITLE>OPTION: <!--#echo var="VAR_nntp-server"--></TITLE></HEAD> 23219<BODY> 23220<H1>OPTION: <!--#echo var="VAR_nntp-server"--></H1> 23221 23222This value specifies the name of one or more NNTP 23223(Network News Transfer Protocol) 23224servers for reading and posting USENET news. 23225NNTP servers are normally 23226set up by a system administrator for use by all members of a given campus 23227or department. 23228Contact your local help desk to ask what NNTP servers you should use. 23229<!--chtml if pinemode="os_windows"--><!--chtml else--> 23230Often Unix Alpine users will find that this variable has been 23231set for the whole system (and they don't have to worry about it). 23232<!--chtml endif--> 23233When you define an NNTP server here, Alpine implicitly defines a news 23234collection for you, assuming that server as the news server and assuming 23235that you will use the NNTP protocol and a local newsrc configuration file 23236for reading news. 23237For more about reading news with Alpine, see 23238<A HREF="h_reading_news">how to use Alpine to read news</A>. 23239<P> 23240Your NNTP server may offer NNTP "AUTHINFO SASL" 23241or "AUTHINFO USER" authentication. 23242It may even require it. 23243If your NNTP server does offer such authentication you may specify a user name 23244parameter to cause Alpine to attempt to authenticate. 23245The same is true for the server name in a folder collection that uses NNTP. 23246This parameter requires an associated value, 23247the username identifier with which to establish the server connection. 23248An example might be: 23249 23250<P> 23251<CENTER><SAMP>nntpserver.example.com/user=katie</SAMP></CENTER> 23252<P> 23253 23254If authentication is offered by the server, this will cause Alpine to 23255attempt to use it. 23256If authentication is not offered by the server, this will cause Alpine 23257to fail with an error similar to: 23258 23259<P> 23260<CENTER><SAMP>Error: NNTP authentication not available</SAMP></CENTER> 23261<P> 23262For more details about the server name possibilities see 23263<A HREF="h_folder_server_syntax">Server Name Syntax</A>. 23264<P><UL> 23265<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 23266</UL><P> 23267<End of help on this topic> 23268</BODY> 23269</HTML> 23270====== h_config_inbox_path ===== 23271<HTML> 23272<HEAD> 23273<TITLE>OPTION: <!--#echo var="VAR_inbox-path"--></TITLE> 23274</HEAD> 23275<BODY> 23276<H1>OPTION: <!--#echo var="VAR_inbox-path"--></H1> 23277 23278This value overrides the default value of your INBOX name/path/location. 23279<!--chtml if pinemode="os_windows"--> 23280PC-Alpine users must specify an inbox path and it must be a folder on an 23281IMAP server. 23282<!--chtml else--> 23283Unix and VMS Alpine users will often find that this variable 23284has been pre-configured by your system administrator. 23285<!--chtml endif--> 23286You may be able to specify an alternate INBOX that is either a local folder 23287or a folder on an IMAP server. 23288<P> 23289A typical remote <!--#echo var="VAR_inbox-path"--> entry would be: {monet.art.example.com}INBOX 23290where "monet.art.example.com" is replaced by the name of your IMAP 23291mail server. 23292<P> 23293See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for 23294details on the syntax of folder definitions. 23295<P> 23296See <A HREF="h_info_on_mbox">Missing mail and the mbox driver</A> if your 23297mail is disappearing. 23298<P><UL> 23299<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 23300</UL><P> 23301<End of help on this topic> 23302</BODY> 23303</HTML> 23304====== h_config_change_your_from ===== 23305<HTML> 23306<HEAD> 23307<TITLE>How to Change your From Address</TITLE> 23308</HEAD> 23309<BODY> 23310<H1>How to Change your From Address</H1> 23311 23312If the From address that Alpine includes in mail that you send is not correct, 23313you may want to configure a different default value for the From address. 23314You may follow these directions to change the default: 23315 23316<P> 23317<UL> 23318 <LI> Go to the Main Alpine Menu 23319 <LI> From there type the Setup Command 23320 <LI> From there type the Config Command 23321</UL> 23322 23323<P> 23324You've probably already seen this SETUP CONFIGURATION screen. 23325If not, there are many options you may want to set here. 23326To set the value of the From header you may use the 23327<A href="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A> option. 23328Find it by scrolling down a few pages or use the WhereIs command to 23329search for "customized". 23330You may want to read the help text associated with the option. 23331<P> 23332To add a custom From header, type the Add command and enter the 23333full header line, including the leading "From: ". 23334For example: 23335<P> 23336<CENTER><SAMP>From: Full Name <user@example.com></SAMP></CENTER> 23337<P> 23338Now exit the Setup command and try sending mail to yourself to see 23339what the From line looks like. 23340<P> 23341When you are in the composer you may edit the custom From line by typing 23342Ctrl-R while your cursor is in the headers of the message and then moving 23343to the From line and editing. 23344If you want to leave the default value the same but add the possibility 23345of being able to edit the header when you compose, add just the header 23346name without a value. 23347For example: 23348<P> 23349<CENTER><SAMP>From:</SAMP></CENTER> 23350<P> 23351If you change your From address you may also find it useful to add the 23352changed From address to the 23353<a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a> 23354configuration option. 23355<P> 23356<UL> 23357<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 23358</UL><P> 23359<End of help on this topic> 23360</BODY> 23361</HTML> 23362====== h_config_default_fcc ===== 23363<HTML> 23364<HEAD> 23365<TITLE>OPTION: <!--#echo var="VAR_default-fcc"--></TITLE> 23366</HEAD> 23367<BODY> 23368<H1>OPTION: <!--#echo var="VAR_default-fcc"--></H1> 23369 23370This value specifies where a copy of outgoing mail should be saved. If 23371this is not a path name, it will be in the default collection for saves. 23372Any valid folder specification, local or IMAP, is allowed. This default 23373folder carbon copy only applies when the 23374<A HREF="h_config_fcc_rule">"<!--#echo var="VAR_fcc-name-rule"-->"</A> 23375is set to use the default folder. 23376<!--chtml if pinemode="os_windows"--> 23377PC-Alpine default is "SENTMAIL" (normally stored as SENTMAIL.MTX) 23378<!--chtml else--> 23379Unix Alpine default 23380is normally "sent-mail" in the default folder collection. 23381<!--chtml endif--> 23382<P> 23383If you access your email through an IMAP server, especially if you often switch between Unix Alpine 23384and PC-Alpine, or between various desktop email systems, you may want to set this to a folder on your 23385IMAP server (remember that in order to later access this remote folder through Alpine, it 23386must be in a folder collection. See <A HREF="h_what_are_collections">Folder Collections Explained</a> 23387for more information). An example:<p> 23388<CENTER><SAMP>{monet.art.example.com}mail/sent-mail</SAMP></CENTER> 23389<P> 23390To suppress saving of outgoing mail, set: <!--#echo var="VAR_default-fcc"-->="" 23391<P> 23392See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for 23393details on the syntax of folder definitions. 23394<P> 23395<UL> 23396<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 23397</UL><P> 23398<End of help on this topic> 23399</BODY> 23400</HTML> 23401====== h_config_def_save_folder ===== 23402<HTML> 23403<HEAD> 23404<TITLE>OPTION: <!--#echo var="VAR_default-saved-msg-folder"--></TITLE> 23405</HEAD> 23406<BODY> 23407<H1>OPTION: <!--#echo var="VAR_default-saved-msg-folder"--></H1> 23408 23409This option determines the default folder name for save-message operations 23410("saves"). 23411<P> 23412If this is not a path name, it will be in the default collection for saves. 23413Any valid folder specification, local or IMAP, is allowed. This default 23414folder only applies when the 23415<A HREF="h_config_saved_msg_name_rule">"<!--#echo var="VAR_saved-msg-name-rule"-->"</A> 23416doesn't override it. 23417<!--chtml if pinemode="os_windows"--> 23418PC-Alpine default is "SAVEMAIL" (normally stored as SAVEMAIL.MTX). 23419<!--chtml else--> 23420Unix Alpine default 23421is normally "saved-messages" in the default folder collection. 23422<!--chtml endif--> 23423If you access your email through an IMAP server, especially if you often switch between Unix 23424and PC-Alpine, or between various desktop email systems, you may want to set this to a folder on an 23425IMAP server (remember that in order to later access this remote folder through Alpine, it 23426should be in a folder collection. See <A HREF="h_what_are_collections">Folder Collections Explained</a> 23427for more information). An example:<p> 23428<CENTER><SAMP>{monet.art.example.com}mail/saved-messages</SAMP></CENTER> 23429<P> 23430See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for 23431details on the syntax of folder definitions. 23432<P> 23433<UL> 23434<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 23435</UL><P> 23436<End of help on this topic> 23437</BODY> 23438</HTML> 23439====== h_config_postponed_folder ===== 23440<HTML> 23441<HEAD> 23442<TITLE>OPTION: <!--#echo var="VAR_postponed-folder"--></TITLE> 23443</HEAD> 23444<BODY> 23445<H1>OPTION: <!--#echo var="VAR_postponed-folder"--></H1> 23446 23447This value overrides the default name for the folder where postponed 23448messages are saved. If this is not a path name, it will be in the default 23449collection for message Saves. Any valid folder specification, local or 23450remote, is allowed. 23451PC-Alpine default 23452is "POSTPOND" (stored as POSTPOND.MTX). 23453The Unix Alpine default is normally "postponed-msgs" 23454in the default collection. 23455<P> 23456Tip: If you are using different installations of (PC-)Alpine -- for example, PC-Alpine on your personal 23457computer at home, and Unix Alpine on campus -- you can postpone a composition begun with one Alpine and 23458resume it later with the other if you set this option to the <B>same folder on the same IMAP host</B> 23459in all Alpine copies you use. 23460(Remember that in order to later access this remote folder through Alpine, it must be in a folder 23461collection. See <A HREF="h_what_are_collections">Folder Collections Extensions Explained</a> 23462for more information). An 23463example:<p> 23464<CENTER><SAMP>{monet.art.example.com}mail/postponed-msgs</SAMP></CENTER> 23465<P> 23466See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for 23467details on the syntax of folder definitions. 23468<P> 23469<UL> 23470<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 23471</UL><P> 23472<End of help on this topic> 23473</BODY> 23474</HTML> 23475====== h_config_read_message_folder ===== 23476<HTML> 23477<HEAD> 23478<TITLE>OPTION: <!--#echo var="VAR_read-message-folder"--></TITLE> 23479</HEAD> 23480<BODY> 23481<H1>OPTION: <!--#echo var="VAR_read-message-folder"--></H1> 23482 23483By virtue of specifying a folder name here, Alpine will be configured to 23484save all messages that you have read during a session into the designated 23485"read messages" folder. This allows you to more easily distinguish 23486between your really new email (in your INBOX) and those that you have 23487already read. Depending on how you define the 23488<A HREF="h_config_auto_read_msgs">"auto-move-read-messages"</A> 23489setting, you may or may not be asked when you quit 23490Alpine if you want read messages to be moved to this folder. In either 23491case, moving the messages means they will be deleted from your INBOX. 23492<P> 23493If this is not a path name, it will be in the default collection for 23494saves. Any valid folder specification, local or remote (via IMAP), is 23495allowed. There is no default for the name of the read message folder. 23496<P> 23497See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for 23498details on the syntax of folder definitions. 23499<P> 23500<UL> 23501<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 23502</UL><P> 23503<End of help on this topic> 23504</BODY> 23505</HTML> 23506====== h_config_form_folder ===== 23507<HTML> 23508<HEAD> 23509<TITLE>OPTION: <!--#echo var="VAR_form-letter-folder"--></TITLE> 23510</HEAD> 23511<BODY> 23512<H1>OPTION: <!--#echo var="VAR_form-letter-folder"--></H1> 23513 23514A "<!--#echo var="VAR_form-letter-folder"-->" is a mail folder that is intended to 23515contain messages that you have composed and that are intended to be 23516sent in their original form repeatedly. 23517 23518<P> 23519Setting this variable will alter Alpine's usual behavior when you 23520execute the Compose command. Normally, Alpine offers a chance to 23521continue a postponed or interrupted message should one or the other 23522exist. When this variable is set to a folder name that exists, Alpine 23523will also offer the chance to select a message from the folder to 23524insert into the composer (much like when continuing a postponed message). 23525The difference, however, is that Alpine will not automatically delete 23526the selected message from the Form Letter Folder. 23527<P> 23528Setting this variable will also affect Alpine's behavior when you 23529Postpone a message from the composer. Normally, Alpine simply stashes 23530the message away in your 23531"<A HREF="h_config_postponed_folder"><!--#echo var="VAR_postponed-folder"--></A>". 23532Regardless of the specified folder's existence, Alpine will ask which 23533folder you intend the message to be stored in. Choose the 23534"F" option to store the message in your Form Letter Folder. 23535This is the most common way to add a message to the folder. 23536 23537<P> 23538Another method of adding messages to the folder is via the Alpine 23539composer's <SAMP>Fcc:</SAMP> field. If you are sending a message that 23540you expect to send in the same form again, you can enter the Form 23541Letter Folder's name in this field. Alpine, as usual, will copy the 23542message as it's sent. Note, when you later select this message from 23543your Form Letter Folder, it will have the same recipients as the original 23544message. 23545 23546<P> 23547To delete a message from the Form Letter Folder, you can either select 23548the folder from a suitable FOLDER LIST screen, or use the Delete 23549command in the MESSAGE INDEX offered when selecting from the folder as 23550part of the Compose command. You can delete a Form Letter Folder just 23551as any other folder from a suitable FOLDER LIST screen. 23552 23553<P> 23554You may find that the <A HREF="h_rules_roles">"Roles"</A> 23555facility can be used 23556to replace the Form Letter Folder. 23557 23558<P> 23559See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for 23560details on the syntax of folder definitions. 23561 23562<P> 23563<UL> 23564<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 23565</UL><P> 23566<End of help on this topic> 23567</BODY> 23568</HTML> 23569====== h_config_archived_folders ===== 23570<HTML> 23571<HEAD> 23572<TITLE>OPTION: <!--#echo var="VAR_incoming-archive-folders"--></TITLE> 23573</HEAD> 23574<BODY> 23575<H1>OPTION: <!--#echo var="VAR_incoming-archive-folders"--></H1> 23576 23577This is like 23578<A HREF="h_config_read_message_folder"><!--#echo var="VAR_read-message-folder"--></A>, 23579only more general. You may archive 23580any of the folders in your incoming collection. This is a list of folder 23581pairs, with the first separated from the second in the pair by a space. 23582The first folder in a pair is the folder you want to archive, and the 23583second folder is the folder that read messages from the first should be 23584moved to. Depending on how you define the 23585<A HREF="h_config_auto_read_msgs">"auto-move-read-messages"</A> 23586setting, you may or may not be asked when you 23587leave the first folder if you want read messages to be moved to the 23588second folder. In either case, moving the messages means they will be 23589deleted from the first folder. 23590<P> 23591The name of the first folder in each pair can be either the technical 23592specification of the folder (like what appears in your configuration file) 23593or (much easier) the nickname that you gave the folder when you made it 23594an incoming folder. 23595<p> 23596For example:<p> 23597<CENTER><SAMP>{monet.art.example.com}inbox {monet.art.example.com}mail/inbox-archive</SAMP></CENTER> 23598<p>or, using nicknames:<p> 23599<CENTER><SAMP>inbox inbox-archive</SAMP></CENTER> 23600<P> 23601If these are not path names, they will be in the default collection for 23602saves. Any valid folder specification, local or remote (via IMAP), is 23603allowed. There is no default. 23604<P> 23605See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for 23606details on the syntax of folder definitions. 23607<P> 23608<UL> 23609<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 23610</UL><P> 23611<End of help on this topic> 23612</BODY> 23613</HTML> 23614====== h_config_newsrc_path ====== 23615<HTML> 23616<HEAD> 23617<TITLE>OPTION: <!--#echo var="VAR_newsrc-path"--></TITLE> 23618</HEAD> 23619<BODY> 23620<H1>OPTION: <!--#echo var="VAR_newsrc-path"--></H1> 23621 23622This option overrides the default name Alpine uses for your "newsrc" news 23623status and subscription file. If set, Alpine will take this value as the 23624full pathname for the desired newsrc file.<P> 23625 23626If this option is <B>not</B> set, 23627<!--chtml if pinemode="os_windows"--> 23628PC-Alpine looks first for $HOME\NEWSRC (where $HOME defaults to the root 23629of the current drive, e.g. "C:\") and then it looks in the same 23630directory as your pinerc file for NEWSRC. 23631<!--chtml else--> 23632Unix Alpine looks for the file ~/.newsrc (that is, the file named .newsrc in 23633your account's home directory). 23634<!--chtml endif--> 23635<P><UL> 23636<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 23637</UL> 23638<P> 23639<End of help on this topic> 23640</BODY> 23641</HTML> 23642====== h_config_literal_sig ===== 23643<HTML> 23644<HEAD> 23645<TITLE>OPTION: <!--#echo var="VAR_literal-signature"--></TITLE> 23646</HEAD> 23647<BODY> 23648<H1>OPTION: <!--#echo var="VAR_literal-signature"--></H1> 23649 23650With this option your actual signature, as opposed to 23651the name of a file containing your signature, 23652is stored in the Alpine configuration file. 23653If this is defined it takes precedence over the <!--#echo var="VAR_signature-file"--> option. 23654<P> 23655 23656This is simply a different way to store the signature. 23657The signature is stored inside your Alpine configuration file instead of in 23658a separate file. 23659Tokens work the same way they do with the 23660<A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A> so look there for 23661help. 23662<P> 23663 23664The Setup/Signature command on Alpine's MAIN MENU will edit 23665the "<!--#echo var="VAR_literal-signature"-->" by default. However, if no 23666"<!--#echo var="VAR_literal-signature"-->" is defined and the file named in the 23667"<!--#echo var="VAR_signature-file"-->" option exists, then the latter will be used 23668instead. 23669<P> 23670 23671The two character sequence \n (backslash followed by 23672the character n) will be used to signify a line-break in your signature. 23673You don't have to enter the \n, but it will be visible in the 23674SETUP CONFIGURATION window after you are done editing the signature. 23675 23676<P> 23677<UL> 23678<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 23679</UL><P> 23680<End of help on this topic> 23681</BODY> 23682</HTML> 23683====== h_config_signature_file ===== 23684<HTML> 23685<HEAD> 23686<TITLE>OPTION: <!--#echo var="VAR_signature-file"--></TITLE> 23687</HEAD> 23688<BODY> 23689<H1>OPTION: <!--#echo var="VAR_signature-file"--></H1> 23690 23691If a <A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A> option is defined, 23692then this "<!--#echo var="VAR_signature-file"-->" option will be ignored. 23693You can tell that that is the case because the value of the 23694"<!--#echo var="VAR_signature-file"-->" will show up as 23695<P> 23696<CENTER><SAMP><Ignored: using <!--#echo var="VAR_literal-signature"--> instead></SAMP></CENTER> 23697<P> 23698You may either use all Literal Signatures (signatures stored in your 23699configuration file) throughout Alpine, or all signature files. 23700You can't mix the two. 23701<P> 23702This is the name of a file that will be automatically inserted into 23703outgoing messages. 23704It typically contains information such as your 23705name, email address and organizational affiliation. 23706Alpine adds the 23707signature into the message as soon as you enter the composer so you 23708can choose to remove it or edit it on a message by message basis. 23709Signature file placement in message replies is controlled by the 23710"<A HREF="h_config_sig_at_bottom"><!--#echo var="FEAT_signature-at-bottom"--></A>" 23711setting in the feature list. 23712<P> 23713 23714The default file name is 23715<!--chtml if pinemode="os_windows"--> 23716"PINE.SIG" in the same directory as your PINERC file if your 23717PINERC file is a local file. 23718If your PINERC file is remote, then it will be in the directory specified 23719by the "-aux local_directory" command line option. 23720<!--chtml else--> 23721".signature". 23722<!--chtml endif--> 23723<P> 23724 23725To create or edit your signature file choose Setup from the MAIN MENU 23726and then select S for Signature (Main/Setup/Signature). This puts you 23727into the Signature Editor where you can enter a <EM>few</EM> lines of 23728text containing your identity and affiliation. 23729 23730<P> 23731If the filename is followed by a vertical bar (|) then instead 23732of reading the contents of the file the file is assumed to be a 23733program that will produce the text to be used on its standard output. 23734The program can't have any arguments and doesn't receive any input from Alpine, 23735but the rest of the processing works as if the contents came from a file. 23736 23737<P> 23738Instead of storing the data in a local file, the 23739signature data may be stored remotely in an IMAP folder. 23740In order to do this, 23741you must use a remote name for the file. 23742A remote <!--#echo var="VAR_signature-file"--> name might look like: 23743<P> 23744<CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/signature</SAMP></CENTER> 23745<P> 23746 23747The syntax used here is the same as the syntax used for remote configuration 23748files from the command line. 23749Note that you may not access an existing signature file remotely, 23750you have to create a new <EM>folder</EM> that contains the signature data. 23751If the name you use here for the signature file is a remote name, then when 23752you edit the file from the Setup/Signature command the data will be stored 23753remotely in the folder. 23754You aren't required to do anything special to create the folder, it 23755gets created automatically if you use a remote name. 23756 23757<P> 23758Besides regular text, the signature file may also contain 23759(or a signature program may produce) tokens that 23760are replaced with text that usually depends on the message you are replying 23761to or forwarding. 23762For example, if the signature file contains the token 23763<P> 23764<CENTER><SAMP>_DATE_</SAMP></CENTER> 23765<P> 23766anywhere in the text, then that token is replaced by the date 23767the message you are replying to or forwarding was sent. 23768If it contains 23769<P> 23770<CENTER><SAMP>_CURDATE_</SAMP></CENTER> 23771<P> 23772that is replaced with the current date. 23773The first is an example of a token that depends on the message you 23774are replying to (or forwarding) and the second is an example which 23775doesn't depend on anything other than the current date. 23776You have to be a little careful with this facility since tokens that 23777depend on the message you are replying to or forwarding will be replaced 23778by nothing in the case where you are composing a new message from scratch. 23779The use of <A HREF="h_rules_roles">"roles"</A> may help you 23780in this respect. 23781It allows you to use different signature files in different cases. 23782<P> 23783 23784The list of tokens available for use in the signature file is 23785<A HREF="h_index_tokens">here</A>. 23786<P> 23787 23788Instead of, or along with the use of "roles" to give you 23789different signature files in different situations, there is also 23790a way to conditionally include text based 23791on whether or not a token would result in specific replacement text. 23792For example, you could include some text based on whether or not 23793the _NEWS_ token would result in any newsgroups if it was used. 23794This is explained in detail 23795<A HREF="h_reply_token_conditionals">here</A>. 23796This isn't for the faint of heart. 23797<P> 23798In the very unlikely event that you want to include a literal token 23799in the signature you must precede it with a backslash character. 23800For example, 23801<P> 23802<CENTER><SAMP>\_DAYDATE_ = _DAYDATE_</SAMP></CENTER> 23803<P> 23804would produce something like 23805<P> 23806<CENTER><SAMP>_DAYDATE_ = Sat, 24 Oct 1998</SAMP></CENTER> 23807<P> 23808It is not possible to have a literal backslash followed by an expanded token. 23809<P> 23810An alternate method for storing the signature data is available by using the 23811<A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A> configuration option. 23812This variable will be used by default. 23813<P> 23814<UL> 23815<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 23816</UL><P> 23817<End of help on this topic> 23818</BODY> 23819</HTML> 23820====== h_config_init_cmd_list ===== 23821<HTML> 23822<HEAD> 23823<TITLE>OPTION: <!--#echo var="VAR_initial-keystroke-list"--></TITLE> 23824</HEAD> 23825<BODY> 23826<H1>OPTION: <!--#echo var="VAR_initial-keystroke-list"--></H1> 23827 23828The initial keystroke--or command--list option lets you start Alpine at 23829any place you like. 23830Whatever keystrokes you specify here will be executed 23831by Alpine upon startup as a macro. 23832The words SPACE, TAB, DOWN, UP, LEFT, and 23833RIGHT indicate the pressing of those keys. 23834CR indicates the pressing of the RETURN key. 23835F1 through F12 represent the function keys, and ^ followed 23836by a character indicates that key pressed along with the control key (in 23837other words, ^P means Ctrl-P). 23838As a shortcut notation, an element of the list may be several characters 23839surrounded by double-quotes ("). 23840That will be expanded into the individual keystrokes 23841(excluding the double-quote characters). 23842For example, the quoted-string 23843 23844<P><CENTER>"ABC"</CENTER> 23845 23846<P> 23847is interpreted the same as the three separate list members 23848 23849<P><CENTER>A and B and C</CENTER> 23850 23851<P> 23852which is also the same as 23853 23854<P><CENTER>A,B,C</CENTER> 23855 23856<P> 23857An example: To view message 1 on startup, 23858you could use an <!--#echo var="VAR_initial-keystroke-list"--> equal to 23859 23860<P><CENTER>I,J,1,CR,V</CENTER> 23861 23862<P> 23863An equivalent version of this is 23864 23865<P><CENTER>"IJ1",CR,V</CENTER> 23866 23867<P> 23868Restrictions: You cannot pre-type into the composer with the initial 23869keystroke list, and you cannot mix function key commands with letter 23870commands. 23871 23872<P><UL> 23873<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 23874</UL> 23875<P> 23876<End of help on this topic> 23877</BODY> 23878</HTML> 23879====== h_config_comp_hdrs ===== 23880<html> 23881<header> 23882<title>OPTION: <!--#echo var="VAR_default-composer-hdrs"--></title> 23883</header> 23884<body> 23885<h1>OPTION: <!--#echo var="VAR_default-composer-hdrs"--></h1> 23886 23887You can control which headers you want visible when composing outgoing 23888email using this option. 23889You can specify any of the regular set, any 23890<A HREF="h_compose_richhdr">Rich Header</A>, 23891or any <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A> 23892that you have already defined. 23893If you use this setting at all, you must specify all the 23894headers you want to see, you can't just add to the regular header set. 23895The default set is To:, Cc:, Attchmnt:, and Subject:.<p> 23896 23897Note that the "Newsgroups:" header will be abbreviated in the Composer 23898display, but should be spelled out in full here.<p> 23899<UL> 23900<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 23901</UL><P> 23902<End of help on this topic> 23903</body> 23904</html> 23905====== h_config_custom_hdrs ===== 23906<HTML> 23907<HEAD> 23908<TITLE>OPTION: <!--#echo var="VAR_customized-hdrs"--></TITLE> 23909</HEAD> 23910<BODY> 23911<H1>OPTION: <!--#echo var="VAR_customized-hdrs"--></H1> 23912 23913You may add your own custom headers to outgoing messages. 23914Each header you specify here must include the header tag 23915(<A HREF="h_composer_reply_to">Reply-To:</A>, Approved:, etc.) 23916and may optionally include a value for that header. 23917If you want to see these custom headers each time you compose a message, 23918you must add them to your 23919<A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A> list, 23920otherwise they become part 23921of the rich header set that you only see when you press the 23922<A HREF="h_compose_richhdr">Rich Header</A> 23923<!--chtml if pinemode="function_key"-->(F5) 23924<!--chtml else-->(Ctrl-R)<!--chtml endif--> command. 23925(If you are looking for a way to change which headers are <EM>displayed</EM> 23926when you view a message, take a look at the 23927<A HREF="h_config_viewer_headers"><!--#echo var="VAR_viewer-hdrs"--></A> 23928option instead.) 23929Here's an example that shows how you might set your From address 23930<P> 23931<CENTER><SAMP>From: Full Name <user@example.com></SAMP></CENTER> 23932<P> 23933and another showing how you might set a Reply-To address 23934<P> 23935<CENTER><SAMP>Reply-To: user@example.com</SAMP></CENTER> 23936<P> 23937You may also set non-standard header values here. 23938For example, you could add 23939<P> 23940<CENTER><SAMP>Organization: My Organization Name</SAMP></CENTER> 23941<P> 23942or even 23943<P> 23944<CENTER><SAMP>X-Favorite-Colors: Purple and Gold</SAMP></CENTER> 23945<P> 23946If you include a value after the colon then that header will be included 23947in your outgoing messages unless you delete it before sending. 23948If a header in the <!--#echo var="VAR_customized-hdrs"--> list has only a tag but no value, then 23949it will not be included in outgoing messages unless you edit a value 23950in manually. 23951For example, if 23952<P> 23953<CENTER><SAMP>Reply-To:</SAMP></CENTER> 23954<P> 23955is in the list, then the Reply-To header will be available for editing 23956but won't be included unless a value is added while in the composer. 23957<P> 23958It's actually a little more complicated than that. 23959The values of headers that you set with the <!--#echo var="VAR_customized-hdrs"--> option are 23960defaults. 23961If the message you are about to compose already has a value for a header, 23962that value is used instead of a value from your <!--#echo var="VAR_customized-hdrs"-->. 23963For example, if you are Replying to a message the Subject field 23964will already be filled in. 23965In that case, if the <!--#echo var="VAR_customized-hdrs"--> list contains a Subject line, the 23966custom subject will <EM>NOT</EM> be used. 23967The subject derived from the subject of the message you are Replying 23968to will be used instead. 23969<P> 23970It is also possible to make header setting even more complicated and more 23971automatic by using 23972<A HREF="h_rules_roles">Roles</A>, 23973but if all you want to do is set a default value for a header, you don't 23974need to think about Roles. 23975<P> 23976If you change your From address you may also find it useful to add the 23977changed From address to the 23978<a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a> 23979configuration option. 23980<P> 23981Limitation: Because commas are used to separate the list of 23982<!--#echo var="VAR_customized-hdrs"-->, it is not possible to have the value of a 23983header contain a comma. 23984Nor is there currently an "escape" mechanism provided 23985to make this work. 23986<P><UL> 23987<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 23988</UL> 23989<P> 23990<End of help on this topic> 23991</BODY> 23992</HTML> 23993====== h_config_viewer_headers ===== 23994<HTML> 23995<HEAD> 23996<TITLE>OPTION: <!--#echo var="VAR_viewer-hdrs"--></TITLE> 23997</HEAD> 23998<BODY> 23999<H1>OPTION: <!--#echo var="VAR_viewer-hdrs"--></H1> 24000 24001You may change the default list of headers that are viewed by listing 24002the headers you want to view here. If the headers in your 24003"<!--#echo var="VAR_viewer-hdrs"-->" list are present in the message, then they 24004will be shown. The order of the headers you list will be honored. If 24005the special value "all-except" is included as the first 24006header in the "<!--#echo var="VAR_viewer-hdrs"-->" list, then all headers in the 24007message except those in the list will be shown. The values are all 24008case insensitive. 24009 24010<P> 24011Note that once you put anything in the "<!--#echo var="VAR_viewer-hdrs"-->" list, 24012then the original default headers are ignored. So, if you just wanted 24013to add the header Organization to the list, you would have to list 24014Organization plus all of the other headers originally in the default 24015list. If you just included Organization and nothing else, then you 24016would see only the Organization header, nothing else. 24017 24018<P> 24019The default list of headers includes: 24020<UL> 24021 <LI>From 24022 <LI>Resent-From 24023 <LI>To 24024 <LI>Resent-To 24025 <LI>Cc 24026 <LI>Resent-cc 24027 <LI>Bcc 24028 <LI>Newsgroups 24029 <LI>Followup-To 24030 <LI>Date 24031 <LI>Resent-Date 24032 <LI>Subject 24033 <LI>Resent-Subject 24034 <LI>Reply-To 24035</UL> 24036 24037<P> 24038If you are looking for a way to control which headers are included in 24039outgoing mail and are visible or not in the composer, take a look at the 24040options 24041<A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A> 24042and <A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A> instead of 24043this option. 24044<P> 24045<UL> 24046<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 24047</UL><P> 24048<End of help on this topic> 24049</BODY> 24050</HTML> 24051====== h_config_viewer_margin_left ===== 24052<HTML> 24053<HEAD> 24054<TITLE>OPTION: <!--#echo var="VAR_viewer-margin-left"--></TITLE> 24055</HEAD> 24056<BODY> 24057<H1>OPTION: <!--#echo var="VAR_viewer-margin-left"--></H1> 24058 24059This variable controls the left-hand vertical margin's width in 24060Alpine's Message Viewing screen. 24061Its value is the number of space characters preceding each displayed line. 24062For consistency with 24063<A HREF="h_config_viewer_margin_right"><!--#echo var="VAR_viewer-margin-right"--></A>, 24064you may specify the column number to start in 24065(column numbering begins with number 1) 24066instead of the width of the margin by appending a lower case letter 24067"c" to the number. 24068For example, a value of "2c" means to start the text in column two, 24069which is entirely equivalent to a value of "1", which means to 24070leave a margin of 1 space. 24071<P> 24072The default is a left margin of 0 (zero). 24073Misconfigurations (for example, negative values or values with starting 24074left columns greater than the ending right column) 24075are silently ignored. 24076If the number of columns for text between the <!--#echo var="VAR_viewer-margin-left"--> and 24077the <!--#echo var="VAR_viewer-margin-right"--> is fewer than 8, then margins of zero will be used 24078instead. 24079 24080<P> 24081<End of help on this topic> 24082</BODY> 24083</HTML> 24084====== h_config_viewer_margin_right ===== 24085<HTML> 24086<HEAD> 24087<TITLE>OPTION: <!--#echo var="VAR_viewer-margin-right"--></TITLE> 24088</HEAD> 24089<BODY> 24090<H1>OPTION: <!--#echo var="VAR_viewer-margin-right"--></H1> 24091 24092This variable controls the right-hand vertical margin's width in 24093Alpine's Message Viewing screen. 24094Its value is the number of space characters following each displayed line. 24095You may specify the column number to end the text in 24096(column numbering begins with number 1) 24097instead of the width of the margin by appending a lower case letter 24098"c" to the number. 24099For example, a value of "76c" means to end the text in column 76. 24100If the screen is 80 characters wide, this is equivalent to a value 24101of "4", which means to leave a margin of 4 spaces. 24102However, if you use different size screens at different times, then these 24103two values are not equivalent. 24104<P> 24105The default right margin is 4. 24106Misconfigurations (for example, negative values or values with starting 24107left columns greater than the ending right column) 24108are silently ignored. 24109If the number of columns for text between the 24110<A HREF="h_config_viewer_margin_left"><!--#echo var="VAR_viewer-margin-left"--></A> and 24111the <!--#echo var="VAR_viewer-margin-right"--> is fewer than 8, then margins of zero will be used 24112instead. 24113 24114<P> 24115<End of help on this topic> 24116</BODY> 24117</HTML> 24118====== h_config_quote_suppression ===== 24119<HTML> 24120<HEAD> 24121<TITLE>OPTION: <!--#echo var="VAR_quote-suppression-threshold"--></TITLE> 24122</HEAD> 24123<BODY> 24124<H1>OPTION: <!--#echo var="VAR_quote-suppression-threshold"--></H1> 24125 24126This option should be used with care. 24127It will cause some of the quoted text to be eliminated from the 24128display when viewing a message in the MESSAGE TEXT screen. 24129For example, if you set the <!--#echo var="VAR_quote-suppression-threshold"--> to the 24130value "5", 24131this will cause quoted text that is longer than five lines to be truncated. 24132Quoted text of five or fewer consecutive lines will be displayed in its entirety. 24133Quoted text of more than six lines will have the first five lines displayed 24134followed by a line that looks something like 24135<P> 24136<CENTER><SAMP>[ 12 lines of quoted text hidden from view ]</SAMP></CENTER> 24137<P> 24138As a special case, if exactly one line of quoted text would be hidden, the 24139entire quote will be shown instead. 24140So for the above example, quoted text that is exactly six lines long will 24141will be shown in its entirety. 24142(In other words, instead of hiding a single line and adding a line 24143that announces that one line was hidden, the line is just shown.) 24144<P> 24145If the sender of a message has carefully chosen the quotes that he or she 24146includes, hiding those quotes may change the meaning of the message. 24147For that reason, Alpine requires that when you want to set the value of this 24148variable to something less than four lines, you actually have to set it 24149to the negative of that number. 24150So if you want to set this option to "3", you actually have to 24151set it to "-3". 24152The only purpose of this is to get you to think about whether or not you 24153really want to do this! 24154If you want to delete all quoted text you set the value of this option 24155to the special value "-10". 24156<P> 24157The legal values for this option are 24158<P> 24159<TABLE> 24160<TR> 24161 <TD> 0 </TD> 24162 <TD> Default, don't hide anything </TD> 24163</TR> 24164<TR> 24165 <TD> -1,-2,-3 </TD> 24166 <TD> Suppress quote lines past 1, 2, or 3 lines </TD> 24167</TR> 24168<TR> 24169 <TD> 4,5,6,... </TD> 24170 <TD> Suppress if more than that many lines </TD> 24171</TR> 24172<TR> 24173 <TD> -10 </TD> 24174 <TD> Suppress all quoted lines </TD> 24175</TR> 24176</TABLE> 24177<P> 24178If you set this option to a non-default value you may sometimes wish to 24179view the quoted text that is not shown. 24180When this is the case, the 24181<A HREF="h_common_hdrmode">HdrMode Command</A> 24182may be used to show the hidden text. 24183Typing the "H" command once will show the hidden text. 24184Typing a second "H" will also turn on Full Header mode. 24185The presence or absence of the HdrMode command is determined by the 24186<A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A> 24187Feature-List option in your Alpine configuration, so you will want to 24188be sure that is turned on if you use quote suppression. 24189<P> 24190For the purposes of this option, a quote is a line that begins with the 24191character ">". 24192<P> 24193Quotes are only suppressed when displaying a message on the screen. 24194The entire quote will be left intact when printing or forwarding or something 24195similar. 24196<P> 24197<End of help on this topic> 24198</BODY> 24199</HTML> 24200====== h_config_saved_msg_name_rule ===== 24201<HTML> 24202<HEAD> 24203<TITLE>OPTION: <!--#echo var="VAR_saved-msg-name-rule"--></TITLE> 24204</HEAD> 24205<BODY> 24206<H1>OPTION: <!--#echo var="VAR_saved-msg-name-rule"--></H1> 24207 24208This option determines the default folder name when saving 24209a message. 24210 24211<P> 24212The default option is "default-folder", which is the folder 24213called "saved-messages" in Unix Alpine and 24214"savemail" in PC-Alpine. To change the default folder, modify 24215the Alpine option called 24216<A HREF="h_config_def_save_folder">"<!--#echo var="VAR_default-saved-msg-folder"-->"</A>. 24217 24218<P> 24219Choosing any of the "by-" options cause Alpine to attempt to 24220get the chosen option's value for the message being saved (or for the 24221first message being saved if using an aggregrate save). 24222For example, if "by-from" is chosen, Alpine attempts to get the 24223value of who the message came from (i.e. the from address). 24224Alpine then attempts to save the message to a folder matching that value. 24225If "by-from" is chosen and no value is obtained, Alpine uses 24226"by-sender". 24227The opposite is also true. 24228If "by-recipient" is chosen and the message was posted to a 24229newsgroup, Alpine will use the newsgroup name. 24230If "by-replyto" is chosen and no value is obtained, Alpine uses 24231"by-from". 24232 24233<P> 24234If any of the "by-realname" options are chosen, Alpine will attempt 24235to use the personal name part of the address instead of the mailbox part. 24236If any of the "by-nick" options are chosen, the 24237address is looked up in your address book and if found, the 24238nickname for that entry is used. 24239Only simple address book entries are checked, not distribution lists. 24240Similarly, if any of the 24241"by-fcc" options are chosen, the fcc from the corresponding 24242address book entry is used. 24243If by-realname, or the by-nick or by-fcc lookups result in no value, 24244then if the chosen option ends with the "then-from", 24245"then-sender", "then-replyto", 24246or "then-recip" suffix, Alpine 24247reverts to the same behavior as "by-from", 24248"by-sender", "by-replyto", or "by-recip" 24249depending on which option was specified. 24250If the chosen option doesn't end with one of 24251the "then-" suffixes, then Alpine reverts to the default 24252folder when no match is found in the address book. 24253 24254<P> 24255Choosing the option called "last-folder-used", causes Alpine 24256to save to the folder that you saved to the last time you saved a 24257message. The first time you save a message in an Alpine session, Alpine 24258attempts to save the message to the default folder. 24259 24260<P> 24261Here is an example to make some of the options clearer. 24262If the message is From 24263<P> 24264<CENTER><SAMP>Fred Flintstone <flint@bedrock.org></SAMP></CENTER> 24265<P> 24266and this rule is set to "by-from", then the default folder offered 24267in the save dialog would be "flint". 24268<P> 24269If this rule is set to "by-realname-of-from" then the default would 24270be "Fred Flintstone". 24271<P> 24272If this rule is set to "by-nick-of-from" then Alpine will search 24273for the address "flint@bedrock.org" in your address book. 24274If an entry is found and it has a nickname associated with it, that nickname 24275will be offered as the default folder. 24276If not, the default saved message folder will be offered as the default. 24277<P> 24278If this rule is set to "by-fcc-of-from" then Alpine will search 24279for the address "flint@bedrock.org" in your address book. 24280If an entry is found and it has an Fcc associated with it, that Fcc 24281will be offered as the default folder. 24282If not, the default saved message folder will be offered as the default. 24283<P> 24284If this rule is set to "by-nick-of-from-then-from" then Alpine will search 24285for the address "flint@bedrock.org" in your address book. 24286If an entry is found and it has a nickname associated with it, that nickname 24287will be offered as the default folder. 24288If it is not found (or has no nickname) then the default offered will be 24289the same as it would be for the "by-from" rule. 24290That is, it would be "flint" 24291<P> 24292<UL> 24293<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 24294</UL><P> 24295<End of help on this topic> 24296</BODY> 24297</HTML> 24298====== h_config_fcc_rule ===== 24299<HTML> 24300<HEAD> 24301<TITLE>OPTION: <!--#echo var="VAR_fcc-name-rule"--></TITLE> 24302</HEAD> 24303<BODY> 24304<H1>OPTION: <!--#echo var="VAR_fcc-name-rule"--></H1> 24305 24306This option determines the default name for folder carbon copy. Choose 24307one: 24308 24309<DL> 24310<DT>default-fcc</DT> 24311<DD>This is the normal default, the value of which is set in the 24312"<!--#echo var="VAR_default-fcc"-->" variable as specified earlier in this 24313configuration. 24314</DD> 24315 24316<DT>last-fcc-used</DT> 24317<DD> Causes Alpine to use the folder that was last 24318used in the fcc field 24319</DD> 24320 24321<DT>by-nickname</DT> 24322<DD>Means that Alpine will use the nickname 24323from your address book that matches the first address in the To line. 24324If there is no match, it will use the value of the 24325"<!--#echo var="VAR_default-fcc"-->" variable. 24326</DD> 24327 24328<DT>by-recipient</DT> 24329<DD>Means Alpine will form a folder name 24330based on the left hand side of the first address in the To line. 24331</DD> 24332 24333<DT>by-nick-then-recip</DT> 24334<DD>Means that it will use the 24335matching nickname from your address book if there is one, otherwise it 24336will extract the recipient name from the address and use that (like 24337by-recipient). 24338</DD> 24339 24340<DT>current-folder</DT> 24341<DD>Causes a copy to be written to 24342the currently open folder, unless that is the INBOX. In the case 24343where the current folder is the INBOX, the "<!--#echo var="VAR_default-fcc"-->" is 24344used instead. 24345</DD> 24346</DL> 24347 24348<P> 24349Note: Whatever the fcc specified by the rule here, it will be 24350over-ridden by any fcc entries you have in your address book. 24351 24352<P> 24353<UL> 24354<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 24355</UL><P> 24356<End of help on this topic> 24357</BODY> 24358</HTML> 24359====== h_config_sort_key ===== 24360<HTML> 24361<HEAD> 24362<TITLE>OPTION: <!--#echo var="VAR_sort-key"--></TITLE> 24363</HEAD> 24364<BODY> 24365<H1>OPTION: <!--#echo var="VAR_sort-key"--></H1> 24366 24367This option determines the order in which messages will be displayed in 24368the MESSAGE INDEX screen. Choose from: 24369<P> 24370<UL> 24371 <LI> <A HREF="h_index_sort_arrival">Arrival</A> 24372 <LI> <A HREF="h_index_sort_date">Date</A> 24373 <LI> <A HREF="h_index_sort_subj">Subject</A> 24374 <LI> <A HREF="h_index_sort_ordsubj">OrderedSubj</A> 24375 <LI> <A HREF="h_index_sort_thread">Thread</A> 24376 <LI> <A HREF="h_index_sort_from">From</A> 24377 <LI> <A HREF="h_index_sort_size">Size</A> 24378 <LI> <A HREF="h_index_sort_score">Score</A> 24379 <LI> <A HREF="h_index_sort_to">To</A> 24380 <LI> <A HREF="h_index_sort_cc">Cc</A> 24381</UL> 24382 24383<P> 24384Each type of sort may also be reversed. 24385Normal default is by "Arrival". 24386 24387<P> 24388A possible point of confusion arises when you change the configuration 24389of the <!--#echo var="VAR_sort-key"-->. 24390The folder will normally be re-sorted when you go back to viewing the 24391index. 24392However, if you have manually sorted the folder with the 24393Sort 24394(<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->) 24395command, then it will not be re-sorted until the next time it is opened. 24396 24397<P> 24398<UL> 24399<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 24400</UL><P> 24401<End of help on this topic> 24402</BODY> 24403</HTML> 24404====== h_config_other_startup ===== 24405<HTML> 24406<HEAD> 24407<TITLE>OPTION: Set Startup Rule</TITLE> 24408</HEAD> 24409<BODY> 24410<H1>OPTION: Set Startup Rule</H1> 24411 24412This option determines which message will be the <EM>current message</EM> when 24413the folder is first opened. 24414It works the same way that the option 24415<A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A> 24416works, so look there for help. 24417It may be used for any folder, not just incoming folders. 24418 24419<P> 24420<UL> 24421<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 24422</UL><P> 24423<End of help on this topic> 24424</BODY> 24425</HTML> 24426====== h_config_perfolder_sort ===== 24427<HTML> 24428<HEAD> 24429<TITLE>Set Sort Order</TITLE> 24430</HEAD> 24431<BODY> 24432<H1>Set Sort Order</H1> 24433 24434This option determines the order in which messages will be displayed in 24435the MESSAGE INDEX screen when the Current Folder Type set in the 24436Pattern is a match. Choose from: 24437<P> 24438<UL> 24439 <LI> <A HREF="h_index_sort_default">Default</A> 24440 <LI> <A HREF="h_index_sort_arrival">Arrival</A> 24441 <LI> <A HREF="h_index_sort_date">Date</A> 24442 <LI> <A HREF="h_index_sort_subj">Subject</A> 24443 <LI> <A HREF="h_index_sort_ordsubj">OrderedSubj</A> 24444 <LI> <A HREF="h_index_sort_thread">Thread</A> 24445 <LI> <A HREF="h_index_sort_from">From</A> 24446 <LI> <A HREF="h_index_sort_size">Size</A> 24447 <LI> <A HREF="h_index_sort_score">Score</A> 24448 <LI> <A HREF="h_index_sort_to">To</A> 24449 <LI> <A HREF="h_index_sort_cc">Cc</A> 24450</UL> 24451 24452<P> 24453Each type of sort may also be reversed. 24454Normal default is by "Arrival". 24455 24456<P> 24457A possible point of confusion arises when you change the configuration 24458of the Sort Order for the currently open folder. 24459The folder will normally be re-sorted when you go back to viewing the 24460index. 24461However, if you have manually sorted the folder with the 24462Sort 24463(<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->) 24464command, then it will not be re-sorted until the next time it is opened. 24465 24466<P> 24467<UL> 24468<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 24469</UL><P> 24470<End of help on this topic> 24471</BODY> 24472</HTML> 24473====== h_config_fld_sort_rule ===== 24474<HTML> 24475<HEAD> 24476<TITLE>OPTION: <!--#echo var="VAR_folder-sort-rule"--></TITLE> 24477</HEAD> 24478<BODY> 24479<H1>OPTION: <!--#echo var="VAR_folder-sort-rule"--></H1> 24480 24481This option controls the order in which folder list entries will be 24482presented in the FOLDER LIST screen. Choose one of the following: 24483 24484<DL> 24485<DT>Alphabetical</DT> 24486<DD>sort by alphabetical name independent of type 24487</DD> 24488 24489<DT>Alpha-with-dirs-last</DT> 24490<DD>sort by alphabetical name grouping directory entries 24491to the end of the list 24492</DD> 24493 24494<DT>Alpha-with-dirs-first</DT> 24495<DD>sort by alphabetical name grouping directory entries 24496to the start of the list 24497</DD> 24498</DL> 24499 24500The normal default is "Alphabetical". 24501 24502<P> 24503<UL> 24504<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 24505</UL><P> 24506<End of help on this topic> 24507</BODY> 24508</HTML> 24509====== h_config_ab_sort_rule ===== 24510<HTML> 24511<HEAD> 24512<TITLE>OPTION: <!--#echo var="VAR_addrbook-sort-rule"--></a></TITLE> 24513</HEAD> 24514<BODY> 24515<H1>OPTION: <!--#echo var="VAR_addrbook-sort-rule"--></a></H1> 24516 24517This option controls the order in which address book entries will be 24518presented. Choose one of the following: 24519 24520<DL> 24521<DT>fullname</DT> 24522<DD>use fullname field, lists mixed in 24523</DD> 24524 24525<DT>fullname-with-lists-last</DT> 24526<DD>use fullname field, but put lists at end 24527</DD> 24528 24529<DT>nickname</DT> 24530<DD>use nickname field, lists mixed in 24531</DD> 24532 24533<DT>nickname-with-lists-last</DT> 24534<DD>use nickname field, but put lists at end 24535</DD> 24536 24537<DT>dont-sort</DT> 24538<DD>don't change order of file 24539</DD> 24540</DL> 24541 24542<P> 24543The normal default is "fullname-with-lists-last". 24544If you use an address book from more than one computer and those 24545computers sort the address book differently then the sort order 24546will be the order where the last change to the address book was 24547made. 24548There are two reasons the sorting might be different on different 24549systems. 24550First, the <!--#echo var="VAR_addrbook-sort-rule"--></a> may be set differently in the two 24551places. 24552Second, the collation rules on the two computers may be different. 24553For example, one system might ignore special characters while the other 24554doesn't or one may sort upper and lower case letters together while 24555the other doesn't. 24556In any case, the order you see is the order on the system where the 24557last change was made, for example by an address book edit or a 24558Take Address command. 24559 24560<P> 24561<UL> 24562<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 24563</UL><P> 24564<End of help on this topic> 24565</BODY> 24566</HTML> 24567====== h_config_post_char_set ===== 24568<HTML> 24569<HEAD> 24570<TITLE>OPTION: <!--#echo var="VAR_posting-character-set"--></TITLE> 24571</HEAD> 24572<BODY> 24573<H1>OPTION: <!--#echo var="VAR_posting-character-set"--></H1> 24574 24575The <!--#echo var="VAR_posting-character-set"--> configuration option is used 24576when sending messages. 24577 24578<P> 24579 24580When sending a message the text typed in the composer is 24581labeled with the character set specified by this option. 24582If the composed text is not fully representable in the 24583specified <!--#echo var="VAR_posting-character-set"-->, then it is labeled as "UTF-8." 24584instead; 24585 24586<P> 24587Attachments are labeled with your 24588<A HREF="h_config_key_char_set">"Keyboard Character Set"</A>. 24589 24590<P> 24591Generally, there should be little need to set this option. 24592If left unset, the 24593default behavior is to label composed text as specifically as 24594possible. That is, if the composed text has no non-ASCII characters, 24595it is labeled as "US-ASCII." Similarly, if it is composed of 24596only ISO-8859-15 characters, it is labeled as such. Alpine will 24597attempt to automatically detect a number of character sets including ISO-8859-15, 24598ISO-8859-1, ISO-8859-2, VISCII, KOI8-R, KOI8-U, ISO-8859-7, ISO-8859-6, 24599ISO-8859-8, TIS-620, ISO-2022-JP, GB2312, BIG5, and EUC-KR. 24600If the message contains a mix of character sets, 24601it is labeled as "UTF-8." 24602 24603<P> 24604 24605This setting is provided to allow you to force a particular character set that 24606Alpine does not automatically detect. For example, if a message is representable 24607in more than one character set then Alpine may choose a different default 24608than you want. 24609Lastly, by setting this option explicitly to 24610"UTF-8" all non-ASCII messages you send will be labeled as 24611"UTF-8" instead of something more specific. 24612 24613<P> 24614In the Setup/Config screen you may choose from a list of all the 24615character sets Alpine knows about by using the "T" ToCharsets command. 24616 24617<P> 24618The options 24619<A HREF="h_config_char_set">"Display Character Set"</A> 24620and <A HREF="h_config_key_char_set">"Keyboard Character Set"</A> 24621are closely related. 24622Setting the feature 24623<A HREF="h_config_use_system_translation">"Use System Translation"</A> 24624should cause this option to be ignored. 24625 24626<P> 24627<UL> 24628<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 24629</UL><P> 24630<End of help on this topic> 24631</BODY> 24632</HTML> 24633====== h_config_unk_char_set ===== 24634<HTML> 24635<HEAD> 24636<TITLE>OPTION: <!--#echo var="VAR_unknown-character-set"--></TITLE> 24637</HEAD> 24638<BODY> 24639<H1>OPTION: <!--#echo var="VAR_unknown-character-set"--></H1> 24640 24641The <!--#echo var="VAR_unknown-character-set"--> configuration option is used 24642when reading or replying to messages. 24643 24644<P> 24645 24646A text message should either be made up of all US-ASCII characters 24647or it should contain a charset label which tells the software which 24648character set encoding to use to interpret the message. 24649Sometimes a malformed message may be unlabeled but contain non-ascii text. 24650This message is outside of the standards so any attempt to read it could fail. 24651When Alpine attempts to read such a message it will try to interpret the 24652text in the character set you specify here. 24653For example, if you have correspondents who send you unlabeled messages that 24654are usually made up of characters from the WINDOWS-1251 character set, setting 24655this <!--#echo var="VAR_unknown-character-set"--> to <CODE>WINDOWS-1251</CODE> will 24656allow you to read those messages. 24657Of course, if the unlabeled message is actually in some other character set, 24658then you may see garbage on your screen. 24659<P> 24660Instead of just unlabeled text, this option also affects text which is labeled 24661with the charsets "X-Unknown", "MISSING_PARAMETER_VALUE" 24662or "US-ASCII". 24663 24664<P> 24665In the Setup/Config screen you may choose from a list of all the 24666character sets Alpine knows about by using the "T" ToCharsets command. 24667 24668<P> 24669<UL> 24670<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 24671</UL><P> 24672<End of help on this topic> 24673</BODY> 24674</HTML> 24675====== h_config_char_set ===== 24676<HTML> 24677<HEAD> 24678<TITLE>OPTION: Display Character Set</TITLE> 24679</HEAD> 24680<BODY> 24681<H1>OPTION: Display Character Set</H1> 24682 24683The Display Character Set configuration option is used when viewing messages. 24684<P> 24685Alpine uses Unicode characters internally and 24686it is a goal for Alpine to handle email in many different languages. 24687Alpine will properly display only left-to-right character sets 24688in a fixed-width font. Specifically, Alpine assumes that a fixed-width 24689font is in use, in the sense that 24690characters are assumed to take up zero, one, or two character cell 24691widths from left to right on the screen. This is true even in PC-Alpine. 24692<P> 24693 24694Alpine recognizes some local character sets that are right-to-left 24695(Arabic, Hebrew, and Thai) or not representable in a fixed-width font 24696(Arabic) and properly converts texts in these character sets to/from 24697Unicode; however, there are known display bugs with these character 24698sets. 24699<P> 24700 24701There are three possible configuration character settings and some 24702environment variable settings that can affect how Alpine 24703handles international characters. 24704The first two of these are only available in UNIX Alpine. 24705The three configuration options are 24706Display Character Set, 24707Keyboard Character Set, and 24708<!--#echo var="VAR_posting-character-set"-->. 24709The Keyboard Character Set defaults to being the same value 24710as the Display Character Set, and that is usually correct, because 24711the keyboard almost always produces characters in the same character set 24712as the display displays. 24713The Display Character Set is the character set that Alpine 24714will attempt to use when sending characters to the display. 24715<P> 24716 24717By default, the Display Character Set variable is not set and UNIX Alpine 24718will attempt to get this information from the environment. 24719In particular, the <CODE>nl_langinfo(CODESET)</CODE> call is used. 24720This usually depends on the setting of the environment variables LANG or LC_CTYPE. 24721An explicit configuration setting for Display Character Set will, 24722of course, override any default setting. 24723<P> 24724For PC-Alpine the Display Character Set 24725and the Keyboard Character Set 24726are always equivalent to <CODE>UTF-8</CODE> and this is not settable. 24727<P> 24728 24729It is probably best to use UNIX Alpine in a terminal emulator 24730capable of displaying UTF-8 characters, since that will allow you to 24731view just about any received text that is correctly formatted (note, 24732however, the above comments about known index display bugs with certain 24733character sets). You'll need to have an emulator that uses a UTF-8 font 24734and you'll need to set up your environment to use a UTF-8 charmap. For 24735example, on a Linux system you might include 24736<P> 24737<CENTER> <CODE>setenv LANG en_US.UTF-8</CODE> </CENTER> 24738<P> 24739 24740or something similar in your UNIX startup files. 24741You'd also have to select a UTF-8 font in your terminal emulator. 24742<P> 24743 24744The types of values that the character set variables may be set to are 24745<CODE>UTF-8</CODE>, <CODE>ISO-8859-1</CODE>, or <CODE>EUC-JP</CODE>. 24746The <CODE>ISO-2022</CODE> character sets are not supported for input or 24747for display, but as a special case, <CODE>ISO-2022-JP</CODE> is supported 24748for use only as a <!--#echo var="VAR_posting-character-set"-->. 24749In the Setup/Config screen you may choose from a list of all the 24750character sets Alpine knows about by using the "T" ToCharsets command. 24751Here is a list of many of the possible character sets: 24752 24753<P> 24754<TABLE> 24755<TR> <TD>UTF-8</TD> <TD>Unicode</TD> </TR> 24756<TR> <TD>US-ASCII</TD> <TD>7 bit American English characters</TD> </TR> 24757<TR> <TD>ISO-8859-1</TD> <TD>8 bit European "Latin 1" character set</TD> </TR> 24758<TR> <TD>ISO-8859-2</TD> <TD>8 bit European "Latin 2" character set</TD> </TR> 24759<TR> <TD>ISO-8859-3</TD> <TD>8 bit European "Latin 3" character set</TD> </TR> 24760<TR> <TD>ISO-8859-4</TD> <TD>8 bit European "Latin 4" character set</TD> </TR> 24761<TR> <TD>ISO-8859-5</TD> <TD>8 bit Latin and Cyrillic</TD> </TR> 24762<TR> <TD>ISO-8859-6</TD> <TD>8 bit Latin and Arabic</TD> </TR> 24763<TR> <TD>ISO-8859-7</TD> <TD>8 bit Latin and Greek</TD> </TR> 24764<TR> <TD>ISO-8859-8</TD> <TD>8 bit Latin and Hebrew</TD> </TR> 24765<TR> <TD>ISO-8859-9</TD> <TD>8 bit European "Latin 5" character set</TD> </TR> 24766<TR> <TD>ISO-8859-10</TD> <TD>8 bit European "Latin 6" character set</TD> </TR> 24767<TR> <TD>ISO-8859-11</TD> <TD>Latin and Thai</TD> </TR> 24768<TR> <TD>ISO-8859-12</TD> <TD>Reserved</TD> </TR> 24769<TR> <TD>ISO-8859-13</TD> <TD>8 bit European "Latin 7" character set</TD> </TR> 24770<TR> <TD>ISO-8859-14</TD> <TD>8 bit European "Latin 8" character set</TD> </TR> 24771<TR> <TD>ISO-8859-15</TD> <TD>8 bit European "Latin 9" character set</TD> </TR> 24772<TR> <TD>ISO-8859-16</TD> <TD>8 bit European "Latin 10" character set</TD> </TR> 24773<TR> <TD>KOI8-R</TD> <TD>8 bit Latin and Russian</TD> </TR> 24774<TR> <TD>KOI8-U</TD> <TD>8 bit Latin and Ukrainian</TD> </TR> 24775<TR> <TD>WINDOWS-1251</TD> <TD>8 bit Latin and Russian</TD> </TR> 24776<TR> <TD>TIS-620</TD> <TD>8 bit Latin and Thai</TD> </TR> 24777<TR> <TD>VISCII</TD> <TD>8 bit Latin and Vietnamese</TD> </TR> 24778<TR> <TD>GBK</TD> <TD>Latin and Chinese Simplified</TD> </TR> 24779<TR> <TD>GB2312</TD> <TD>Latin and Chinese Simplified</TD> </TR> 24780<TR> <TD>CN-GB</TD> <TD>Latin and Chinese Simplified</TD> </TR> 24781<TR> <TD>BIG5</TD> <TD>Latin and Chinese Traditional</TD> </TR> 24782<TR> <TD>BIG-5</TD> <TD>Latin and Chinese Traditional</TD> </TR> 24783<TR> <TD>EUC-JP</TD> <TD>Latin and Japanese</TD> </TR> 24784<TR> <TD>SHIFT-JIS</TD> <TD>Latin and Japanese</TD> </TR> 24785<TR> <TD>EUC-KR</TD> <TD>Latin and Korean</TD> </TR> 24786<TR> <TD>KSC5601</TD> <TD>Latin and Korean</TD> </TR> 24787</TABLE> 24788<P> 24789 24790When reading incoming email, Alpine understands many different 24791character sets and is able to convert the incoming mail into Unicode. 24792The Unicode will be converted to the Display Character Set 24793for display on your terminal. 24794Characters typed at the keyboard will be converted from the 24795Keyboard Character Set to Unicode for Alpine's internal 24796use. 24797You may find that you can read some malformed messages that do not 24798contain a character set label by setting the option 24799<A HREF="h_config_unk_char_set">"<!--#echo var="VAR_unknown-character-set"-->"</A>. 24800<P> 24801 24802The <!--#echo var="VAR_posting-character-set"--> is used when sending messages. 24803The default behavior obtained by leaving this variable unset is usually 24804what is wanted. In that default case, Alpine will attempt 24805to label the message with the most specific character set from the 24806rather arbitrary set 24807<P> 24808US-ASCII, ISO-8859-15, 24809ISO-8859-1, ISO-8859-2, VISCII, KOI8-R, KOI8-U, ISO-8859-7, ISO-8859-6, 24810ISO-8859-8, TIS-620, ISO-2022-JP, GB2312, BIG5, EUC-KR, and UTF-8. 24811<P> 24812 24813For example, if the message is made up of only US-ASCII characters, it 24814will be labeled US-ASCII. Otherwise, if it is all ISO-8859-15 characters, 24815that will be the label. If that doesn't work the same is tried for the 24816remaining members of the list. 24817 24818<P> 24819It might make sense to set <!--#echo var="VAR_posting-character-set"--> to an 24820explicit value instead. 24821For example, if you usually send messages in Greek, setting this 24822option to ISO-8859-7 will result in messages being labeled as 24823US-ASCII if there are no non-ascii characters, ISO-8859-7 if there 24824are only Greek characters, or UTF-8 if there are some characters 24825that aren't representable in ISO-8859-7. 24826Another possibility is to set this option explicitly to UTF-8. 24827In that case 24828Alpine labels only ascii messages as US-ASCII and all other 24829messages as UTF-8. 24830<P> 24831 24832The options 24833<A HREF="h_config_post_char_set">"<!--#echo var="VAR_posting-character-set"-->"</A> 24834and <A HREF="h_config_key_char_set">"Keyboard Character Set"</A> 24835are closely related to this option. 24836Setting the feature 24837<A HREF="h_config_use_system_translation">"Use System Translation"</A> 24838should cause this option to be ignored. 24839 24840<P> 24841When displaying a message, Alpine compares this setting to the character 24842set specified in the message. If not all of the 24843characters in the message can be displayed using the Display Character Set 24844then Alpine places an editorial 24845comment in the displayed text (enclosed in square-brackets) indicating 24846that some characters may not be displayed correctly. 24847This comment may be eliminated by turning on the option 24848<A HREF="h_config_quell_charset_warning"><!--#echo var="FEAT_quell-charset-warning"--></A>. 24849 24850<P> 24851<UL> 24852<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 24853</UL><P> 24854<End of help on this topic> 24855</BODY> 24856</HTML> 24857====== h_config_key_char_set ===== 24858<HTML> 24859<HEAD> 24860<TITLE>OPTION: Keyboard Character Set</TITLE> 24861</HEAD> 24862<BODY> 24863<H1>OPTION: Keyboard Character Set</H1> 24864 24865UNIX Alpine only. 24866<P> 24867The Keyboard Character Set identifies the character set of the characters 24868coming from your keyboard. 24869It defaults to having the same value as your 24870<A HREF="h_config_char_set">"Display Character Set"</A>, 24871which in turn defaults to a value obtained from your environment. 24872It is unlikely that you will need to use this option, because the keyboard 24873almost always produces the same kind of characters as the display displays. 24874 24875<P> 24876This character set is also used when accessing files in your local 24877file system. 24878The names of the files are assumed to be in the same character set as 24879what the keyboard produces, as well as the contents of the files. 24880 24881<P> 24882In the Setup/Config screen you may choose from a list of all the 24883character sets Alpine knows about by using the "T" ToCharsets command. 24884 24885<P> 24886The options 24887<A HREF="h_config_char_set">"Display Character Set"</A> 24888and <A HREF="h_config_post_char_set">"<!--#echo var="VAR_posting-character-set"-->"</A> 24889are closely related. 24890Setting the feature 24891<A HREF="h_config_use_system_translation">"Use System Translation"</A> 24892should cause this option to be ignored. 24893 24894<P> 24895<UL> 24896<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 24897</UL><P> 24898<End of help on this topic> 24899</BODY> 24900</HTML> 24901====== h_config_editor ===== 24902<HTML> 24903<HEAD> 24904<TITLE>OPTION: <!--#echo var="VAR_editor"--></TITLE> 24905</HEAD> 24906<BODY> 24907<H1>OPTION: <!--#echo var="VAR_editor"--></H1> 24908 24909<!--#echo var="VAR_editor"--> specifies the program invoked by ^_ in the Composer. This is 24910normally an alternative to Alpine's internal composer (Pico). You could use 24911this setting to specify an alternate editor to use occasionally or if you 24912have a favorite editor and want to use it all the time (see the 24913<A HREF="h_config_alt_ed_now">"<!--#echo var="FEAT_enable-alternate-editor-implicitly"-->"</A> setting). <P> 24914If you specify multiple editors for this option, ^_ will invoke the first one 24915of those specified that exists and is executable. When specifying a program 24916for use here, make sure that the format of the text it saves -- which, when 24917you exit it, will become the message body in Alpine -- is appropriate 24918for the body of an email message; avoid proprietary formats that may result in 24919a message body that the recipient of your message will be unable to decipher. 24920<P> 24921<!--chtml if pinemode="os_windows"--> 24922<!--chtml else--> 24923If you are in doubt about what editors are available on your system, or which 24924of them may be appropriate for specification here, ask your local computing 24925support staff. 24926<!--chtml endif--> 24927<P> 24928Note that if <a href="h_config_quell_flowed_text"><!--#echo var="FEAT_quell-flowed-text"--></a> is 24929unset, outgoing text will be set as flowed. In most cases this will be fine, 24930but if the editor has a "flowed text" mode, it would be best to 24931use that. 24932 24933<P><UL> 24934<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 24935</UL> 24936<P> 24937<End of help on this topic> 24938</BODY> 24939</HTML> 24940====== h_config_speller ===== 24941<HTML> 24942<HEAD> 24943<TITLE>OPTION: <!--#echo var="VAR_speller"--></TITLE> 24944</HEAD> 24945<BODY> 24946<H1>OPTION: <!--#echo var="VAR_speller"--></H1> 24947 24948UNIX Alpine only. 24949<P> 24950For PC-Alpine, you must install the aspell library code that you 24951may get from 24952<A HREF="http://aspell.net/win32/">http://aspell.net/win32/</A>. 24953<P> 24954This option affects the behavior of the ^T (spell check) command in the 24955Composer. It specifies the program invoked by ^T in the Composer. 24956By default, Alpine uses 24957<P> 24958<CENTER><SAMP>aspell --dont-backup --mode=email check</SAMP></CENTER> 24959<P> 24960if it knows where to find "aspell". 24961If there is no "aspell" command available but the command "ispell" is available 24962then the command used is 24963<P> 24964<CENTER><SAMP>ispell -l</SAMP></CENTER> 24965<P> 24966Otherwise, the ancient "spell" command is used. 24967<P> 24968If you specify a value for this command (with full pathname) then that is what 24969will be used instead of any of the defaults. 24970When invoking this 24971spell-checking program, Alpine appends a tempfile name (where the message is 24972passed) to the command line. Alpine expects the speller to correct the 24973spelling in that file. When you exit from that program Alpine will read the 24974tempfile back into the composer. 24975<P> 24976Don't set this speller option to the standard Unix spell command. 24977That won't work because spell works in a different way. 24978 24979<P> 24980<UL> 24981<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 24982</UL><P> 24983<End of help on this topic> 24984</BODY> 24985</HTML> 24986====== h_config_aspell_dictionary ===== 24987<HTML> 24988<HEAD> 24989<TITLE>OPTION: <!--#echo var="VAR_aspell-dictionary-list"--></TITLE> 24990</HEAD> 24991<BODY> 24992<H1>OPTION: <!--#echo var="VAR_aspell-dictionary-list"--></H1> 24993 24994PC Alpine only. 24995<P> 24996This option specifies a list of dictionaries you will use with 24997aspell. A sample entry is "en_US" for american english, or 24998"en_GB" for british english. 24999 25000<P> 25001<UL> 25002<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 25003</UL><P> 25004<End of help on this topic> 25005</BODY> 25006</HTML> 25007====== h_config_display_filters ===== 25008<HTML> 25009<HEAD> 25010<TITLE>OPTION: <!--#echo var="VAR_display-filters"--></TITLE> 25011</HEAD> 25012<BODY> 25013<H1>OPTION: <!--#echo var="VAR_display-filters"--></H1> 25014 25015This option defines a list of text-filtering commands (programs or 25016scripts) that may be used to filter text portions of received messages 25017prior to their use (e.g., presentation in the "MESSAGE TEXT" 25018display screen, exporting to a text file). 25019For security reasons, the full path name of the 25020filter command must be specified. 25021 25022<P> 25023The command is executed and the message is piped into its standard input. 25024The standard output of the command is read back by Alpine. The 25025"_TMPFILE_" token (see below) overrides this default behavior. 25026 25027<P> 25028The filter's use is based on the configured "trigger" string. The 25029format of a filter definition is: 25030 25031<P> 25032<CENTER><trigger> <command> <arguments></CENTER> 25033 25034<P> 25035You can specify as many filters as you wish, separating them with a comma. 25036Each filter can have only one trigger and command. Thus, two trigger 25037strings that invoke the same command require separate filter 25038specifications. 25039 25040<P> 25041The "trigger" is simply text that, if found in the message, 25042will invoke the associated command. If the trigger contains any space 25043characters, it must be placed within quotes. Likewise, should you 25044wish a filter to be invoked unconditionally, define the trigger as the 25045null string, "" (two consecutive double-quote characters). If the 25046trigger string is found anywhere in the text of the message the filter 25047is invoked. Placing the trigger text within the tokens defined below 25048changes where within the text the trigger must be before considering 25049it a match. 25050 25051<P> 25052Trigger Modifying Tokens: 25053<DL> 25054<DT>_CHARSET(<VAR>string</VAR>)_</DT> 25055<DD>This token tells Alpine to invoke the supplied command 25056if the text is in a character set matching <VAR>string</VAR> 25057(e.g., ISO-8859-2 or ISO-2022-JP). 25058</DD> 25059 25060 25061<DT>_LEADING(<VAR>string</VAR>)_</DT> 25062<DD>This token tells Alpine to invoke the supplied command 25063if the enclosed <VAR>string</VAR> is found to be the first 25064non-whitespace text. 25065<BR>NOTE: Quotes are necessary if <VAR>string</VAR> contains 25066the space character. 25067</DD> 25068 25069<DT>_BEGINNING(<VAR>string</VAR>)_</DT> 25070<DD>This token tells Alpine to invoke the supplied command 25071if the enclosed <VAR>string</VAR> is found at the beginning 25072of any line in the text. 25073<BR>NOTE: Quotes are necessary if <VAR>string</VAR> contains 25074the space character. 25075</DD> 25076</DL> 25077 25078<P> 25079The "command" and "arguments" portion is simply 25080the command line to be invoked if the trigger string is found. Below 25081are tokens that Alpine will recognize and replace with special values 25082when the command is actually invoked. 25083 25084<P> 25085Command Modifying Tokens: 25086 25087<DL> 25088<DT>_TMPFILE_</DT> 25089<DD>When the command is executed, this token is 25090replaced with the path and name of the temporary 25091file containing the text to be filtered. Alpine 25092expects the filter to replace this data with the 25093filter's result. 25094 25095<P> 25096NOTE: Use of this token implies that the text to 25097be filtered is not piped into standard input of the 25098executed command and its standard output is ignored. 25099Alpine restores the tty modes before invoking the 25100filter in case the filter interacts with the user 25101via its own standard input and output. 25102</DD> 25103 25104<DT>_RESULTFILE_</DT> 25105<DD>When the command is executed, this token is 25106replaced with the path and name of a temporary 25107file intended to contain a status message from the 25108filter. Alpine displays this in the message status 25109field. 25110</DD> 25111 25112<DT>_DATAFILE_</DT> 25113<DD>When the command is executed, this token is 25114replaced with the path and name of a temporary 25115file that Alpine creates once per session and deletes 25116upon exit. The file is intended to be used by the 25117filter to store state information between instances 25118of the filter. 25119</DD> 25120 25121<DT>_PREPENDKEY_</DT> 25122<DD>When the command is executed, this token indicates that a random 25123number will be passed down the input stream before the message text. 25124This number could be used as a session key. It is sent in this way to 25125improve security. The number is unique to the current Alpine session 25126and is only generated once per session. 25127</DD> 25128 25129<DT>_SILENT_</DT> 25130<DD>When the filter is executed, this token tells Alpine not to repaint 25131the screen while the command is being executed. This can be used with 25132filters that do not interact with the user, and therefore repainting 25133the screen is not necessary. 25134</DD> 25135</DL> 25136 25137<P> 25138The feature 25139<A HREF="h_config_disable_reset_disp"><!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></A> is related. 25140<P> 25141Performance caveat/considerations: 25142<BR> 25143Testing for the trigger and invoking the filter doesn't come for free. 25144There is overhead associated with searching for the trigger string, testing 25145for the filter's existence and actually piping the text through the filter. 25146The impact can be reduced if the Trigger Modifying Tokens above are 25147employed. 25148<P> 25149<End of help on this topic> 25150</BODY> 25151</HTML> 25152====== h_config_sending_filter ===== 25153<HTML> 25154<HEAD> 25155<TITLE>OPTION: <!--#echo var="VAR_sending-filters"--></TITLE> 25156</HEAD> 25157<BODY> 25158<H1>OPTION: <!--#echo var="VAR_sending-filters"--></H1> 25159 25160This option defines a list of text-filtering commands (programs and 25161scripts) that may be selectively invoked to process a message just before 25162it is sent. If set, the Composer's ^X (Send) command will allow you to 25163select which filter (or none) to apply to the message before it is sent. 25164For security reasons, the full path of the filter program must be 25165specified. 25166 25167<P> 25168Command Modifying Tokens: 25169 25170<DL> 25171<DT>_RECIPIENTS_</DT> 25172<DD>When the command is executed, this token is replaced 25173with the space delimited list of recipients of the 25174message being sent. 25175</DD> 25176 25177<DT>_TMPFILE_</DT> 25178<DD> 25179When the command is executed, this token is 25180replaced with the path and name of the temporary 25181file containing the text to be filtered. Alpine 25182expects the filter to replace this data with the 25183filter's result. 25184 25185<P> 25186NOTE: Use of this token implies that the text to 25187be filtered is not piped into standard input of the 25188executed command and its standard output is ignored. 25189Alpine restores the tty modes before invoking the 25190filter in case the filter interacts with the user 25191via its own standard input and output. 25192</DD> 25193 25194<DT>_RESULTFILE_</DT> 25195<DD>When the command is executed, this token is 25196replaced with the path and name of a temporary 25197file intended to contain a status message from the 25198filter. Alpine displays this in the message status 25199field. 25200</DD> 25201 25202<DT>_DATAFILE_</DT> 25203<DD>When the command is executed, this token is replaced 25204in the command line with the path and name of a 25205temporary file that Alpine creates once per session 25206and deletes upon exit. The file is intended to be 25207used by the filter to store state information between 25208instances of the filter. 25209</DD> 25210 25211<DT>_PREPENDKEY_</DT> 25212<DD>When the command is executed, this token indicates 25213that a random number will be passed down the input 25214stream before the message text. This number could 25215be used as a session key. It is sent in this way 25216to improve security. The number is unique to the 25217current Alpine session and is only generated once per 25218session. 25219</DD> 25220 25221<DT>_INCLUDEALLHDRS_</DT> 25222<DD>When the command is executed, this token indicates 25223that the headers of the message will be passed down the input stream 25224before the message text. 25225</DD> 25226 25227<DT>_MIMETYPE_</DT> 25228<DD>When the command is executed, this token is replaced in the 25229command name with a temporary file name used to accept any new MIME 25230Content-Type information necessitated by the output of the filter. 25231Upon the filter's exit, if the file contains new MIME type 25232information, Alpine verifies its format and replaces the outgoing 25233message's MIME type information with that contained in the file. This 25234is basically a cheap way of sending something other than Text/Plain. 25235</DD> 25236</DL> 25237 25238<P> 25239NOTE: Only the body text, which is visible in the Composer, is piped 25240through this filter. Attachments are not sent to the filter. 25241<P> 25242Sending filters are not used if the feature 25243<A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set. 25244<P> 25245<UL> 25246<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 25247</UL><P> 25248<End of help on this topic> 25249</BODY> 25250</HTML> 25251====== h_config_keywords ===== 25252<HTML> 25253<HEAD> 25254<TITLE>OPTION: <!--#echo var="VAR_keywords"--></TITLE> 25255</HEAD> 25256<BODY> 25257<H1>OPTION: <!--#echo var="VAR_keywords"--></H1> 25258 25259You may define your own set of keywords and optionally set them on a 25260message by message basis. 25261These are similar to the "Important" flag which the user 25262may set using the Flag command. 25263The difference is that the Important flag is always present for each folder. 25264User-defined keywords are chosen by the user. 25265You may set up the list of possible keywords here, or you may add keywords 25266from the Flag Details screen that you 25267can get to after typing the 25268Flag (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->*<!--chtml endif-->) 25269command. 25270After the keywords have been defined, 25271then you use the <A HREF="h_common_flag">Flag command</A> 25272to set or clear the keywords in each message. 25273The behavior of the flag command may be modified by using the 25274<A HREF="h_config_flag_screen_default">"<!--#echo var="FEAT_enable-flag-screen-implicitly"-->"</A> option or the 25275<A HREF="h_config_flag_screen_kw_shortcut">"<!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"-->"</A> option. 25276 25277<P> 25278Keywords may be used when Selecting messages (Select Keyword). 25279Keywords may also be used in the Patterns of Rules (Filters, Indexcolors, etc). 25280Filter Rules may be used to set keywords automatically. 25281Keywords may be displayed as part of the Subject of a message by using 25282the SUBJKEY or SUBJKEYINIT tokens in the 25283<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option. 25284The <A HREF="h_config_kw_braces"><!--#echo var="VAR_keyword-surrounding-chars"--></A> 25285option may be used to modify the display of keywords using 25286SUBJKEY and SUBJKEYINIT slightly. 25287Keywords may also be displayed in a column of their own in the MESSAGE INDEX 25288screen by using the KEY or KEYINIT tokens. 25289It is also possible to color keywords in the index using the 25290Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>). 25291Keywords are not supported by all mail servers. 25292 25293<P> 25294You may give keywords nicknames if you wish. 25295If the keyword definition you type in contains a SPACE character, then the 25296actual value of the keyword is everything after the last SPACE and the 25297nickname for that keyword is everything before the last SPACE. 25298For example, suppose you are trying to interoperate with another email program 25299that uses a particular keyword with an unpleasant name. 25300Maybe it uses a keyword called 25301<P> 25302<CENTER><SAMP>VendorName.SoftwareName.08</SAMP></CENTER> 25303<P> 25304but for you that keyword means that the message is work-related. 25305You could define a keyword to have the value 25306<P> 25307<CENTER><SAMP>Work VendorName.SoftwareName.08</SAMP></CENTER> 25308<P> 25309and then you would use the name "Work" when dealing with 25310that keyword in Alpine. 25311If you defined it as 25312<P> 25313<CENTER><SAMP>My Work VendorName.SoftwareName.08</SAMP></CENTER> 25314<P> 25315the nickname would be everything before the last SPACE, that is the nickname 25316would be "My Work". 25317<P> 25318Some commonly used keywords begin with dollar signs. 25319This presents a slight complication, because the dollar sign is normally used 25320to signify 25321<A HREF="h_news_config">environment variable expansion</A> 25322in the Alpine configuration. 25323In order to specify a keyword that begins with a dollar sign you must 25324precede the dollar sign with a second dollar sign to escape its special 25325meaning. 25326For example, if you want to include the keyword 25327<P> 25328<CENTER><SAMP>$Label1</SAMP></CENTER> 25329<P> 25330as one of your possible keywords, you must enter the text 25331<P> 25332<CENTER><SAMP>$$Label1</SAMP></CENTER> 25333<P> 25334 25335instead. 25336<P> 25337There are a couple limitations. 25338First, not all servers support keywords. 25339Second, some servers (including the IMAP server included with Alpine) 25340have a per folder limit on the number of keywords that may be defined. 25341This count commonly includes every keyword you have ever used in the 25342folder, even if it is no longer being used. 25343In other words, you can add keywords but you cannot remove them easily. 25344If you have changed keywords over the life of a folder and find that 25345you have reached such a limit, one possible solution might be to copy 25346all of the messages to a newly created folder (using Alpine) and then 25347delete the original and rename the new folder. 25348The reason this might work is that only the keywords currently set in 25349any of the messages will be used in the new folder, hopefully putting you 25350under the limit. 25351 25352<P> 25353<UL> 25354<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 25355</UL><P> 25356<End of help on this topic> 25357</BODY> 25358</HTML> 25359====== h_config_alt_addresses ===== 25360<HTML> 25361<HEAD> 25362<TITLE>OPTION: <!--#echo var="VAR_alt-addresses"--></TITLE> 25363</HEAD> 25364<BODY> 25365<H1>OPTION: <!--#echo var="VAR_alt-addresses"--></H1> 25366 25367This option provides a place for you to list alternate email addresses 25368you may have. 25369Each address in the list should be the actual email address part of an 25370address, without the full name field or the angle brackets. 25371For example: 25372 25373<P> 25374<CENTER><SAMP>user@example.com</SAMP></CENTER> 25375<P> 25376 25377The matching is case-insensitive, so this would match any of 25378<SAMP>User@example.com</SAMP>, <SAMP>user@Example.Com</SAMP>, or 25379<SAMP>USER@EXAMPLE.COM</SAMP> as well. 25380 25381<P> 25382If set, the option affects the behavior of the Reply 25383command and the "+" symbol in the MESSAGE INDEX, which denotes that 25384a message has been addressed specifically to you. 25385 25386<P> 25387In the default INDEX display 25388the personal name (or email address) of 25389the person listed in the message's "From:" header 25390field is usually displayed except when that address is yours or one of your 25391alternate addresses. 25392In that case you will usually see the name of 25393the first person specified in the 25394message's "To:" header field 25395with the prefix "To: " prepended. 25396 25397<P> 25398With respect to Reply, the reply-to-all option will exclude addresses 25399listed here. 25400 25401<P> 25402The feature 25403<A HREF="h_config_copy_to_to_from"><!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></A> 25404is somewhat related to this option. 25405 25406<P> 25407In addition to a list of actual addresses, 25408you may use regular expressions (as used with egrep with the ignore case flag) 25409to describe the addresses you want to match. 25410Alpine will somewhat arbitrarily interpret your entry as a regular 25411expression if it contains any of the characters 25412*, |, +, ?, {, [, ^, $, or \. 25413Otherwise, it will be treated literally. 25414The feature 25415<a href="h_config_disable_regex"><!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></a> 25416may be used to turn off regular expression processing regardless of whether or not 25417special characters appear in the entry. 25418 25419<P> 25420A description of how regular expressions work is beyond the 25421scope of this help text, but some examples follow. 25422 25423<P> 25424The entry 25425 25426<P> 25427<CENTER><SAMP>.*@example.com</SAMP></CENTER> 25428<P> 25429 25430in the <!--#echo var="VAR_alt-addresses"--> list would mean that any 25431address with a domain name of <SAMP>example.com</SAMP> (such as 25432<SAMP>fred@example.com</SAMP> or <SAMP>wilma@example.com</SAMP>) will be considered 25433one of your alternate addresses. 25434Strictly speaking, the dot in <SAMP>example.com</SAMP> ought to be escaped with 25435a backslash, as in <SAMP>example\.com</SAMP>, and a dollar sign anchor ought 25436to come at the end of the expression to prevent a match of <SAMP>example.com.org</SAMP>. 25437Complicating things further, the dollar sign 25438is special in the Alpine configuration (it signifies environment variable expansion) 25439so the dollar sign should be doubled or backslash escaped for Alpine's sake. 25440Quotes around the whole expression will not escape the dollar sign successfully. 25441So this example should look like 25442 25443<P> 25444<CENTER><SAMP>.*@example\.com$$</SAMP></CENTER> 25445<P> 25446 25447<P> 25448The entry 25449 25450<P> 25451<CENTER><SAMP>^fred[0-9]*@example.com$$</SAMP></CENTER> 25452<P> 25453 25454would match 25455<SAMP>fred3@example.com</SAMP> or <SAMP>fred17@example.com</SAMP> as well 25456as <SAMP>fred@example.com</SAMP>. 25457 25458<P> 25459You could match all addresses that look like 25460<SAMP>fred+stuff@example.com</SAMP> for any value of <SAMP>stuff</SAMP> with the 25461entry 25462 25463<P> 25464<CENTER><SAMP>^fred\+.*@example.com$$</SAMP></CENTER> 25465<P> 25466 25467Notice that you have to escape the plus sign with a backslash because plus 25468is a special character in regular expressions. 25469If you wanted to match plain <SAMP>fred</SAMP> as well as <SAMP>fred+stuff</SAMP> 25470the expression 25471 25472<P> 25473<CENTER><SAMP>^fred(()|\+.*)@example.com$$</SAMP></CENTER> 25474<P> 25475 25476would do it, but it would be easier to just add fred@example.com as a 25477separate entry. 25478 25479<P> 25480One more example, a match of all first-level subdomains, is given by 25481 25482<P> 25483<CENTER><SAMP>^fred@[[:alnum:]_-]*\.example\.com$$</SAMP></CENTER> 25484<P> 25485 25486<P> 25487Because the regular expression matching is based on an old library 25488(<SAMP>hs_regex</SAMP>) the regular expressions might not work exactly as you expect, 25489but they should be close. 25490 25491<P> 25492<UL> 25493<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 25494</UL><P> 25495<End of help on this topic> 25496</BODY> 25497</HTML> 25498====== h_config_abook_formats ===== 25499<HTML> 25500<HEAD> 25501<TITLE>OPTION: <!--#echo var="VAR_addressbook-formats"--></TITLE> 25502</HEAD> 25503<BODY> 25504<H1>OPTION: <!--#echo var="VAR_addressbook-formats"--></H1> 25505 25506This option specifies the format that address books are displayed in. 25507Normally, address books are displayed with the nicknames in the first 25508column, the fullnames in the second column, and addresses in the third 25509column. The system figures out reasonable defaults for the widths of 25510the columns. An address book may be given a different format by 25511listing special tokens in the order you want them to display. The 25512possible tokens are NICKNAME, FULLNAME, ADDRESS, FCC, and COMMENT. 25513So, for example, to get the default behavior you could list 25514 25515<P> 25516<CENTER><!--#echo var="VAR_addressbook-formats"-->=NICKNAME FULLNAME ADDRESS</CENTER> 25517 25518<P> 25519(You can also use the token DEFAULT to get the default behavior for 25520an address book format.) 25521 25522<P> 25523The tokens are separated by spaces. "<!--#echo var="VAR_addressbook-formats"-->" 25524is a list, so if you have more than one address book you may have a 25525separate format for each by putting its format at the corresponding 25526location in the "<!--#echo var="VAR_addressbook-formats"-->" list. 25527 25528<P> 25529 25530Listed first are the personal address books, then the global address 25531books. So, if you have two personal address books and one global 25532address book, you may have up to three formats in the 25533"<!--#echo var="VAR_addressbook-formats"-->" list. If 25534"<!--#echo var="VAR_addressbook-formats"-->" doesn't have as many elements as there 25535are address books, the last element is used repeatedly. 25536 25537<P> 25538 25539Each of the tokens may also be optionally followed by parentheses with 25540either a number or a percentage inside the parentheses. For example, 25541<SAMP>FULLNAME(13)</SAMP> means to allocate 13 characters of space to 25542the fullnames column, <SAMP>FULLNAME(20%)</SAMP> means to allocate 20% 25543of the available space (the screen width minus the space for 25544inter-column spaces) to the fullnames column, while plain 25545<SAMP>FULLNAME</SAMP> means the system will attempt to figure out a 25546reasonable number of columns. 25547 25548<P> 25549There are always 2 spaces between every column, so if you use 25550fixed column widths (like 13) you should remember to take that into 25551account. 25552 25553<P> 25554<UL> 25555<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 25556</UL><P> 25557<End of help on this topic> 25558</BODY> 25559</HTML> 25560====== h_config_set_index_format ===== 25561<HTML> 25562<HEAD> 25563<TITLE>Set Index Format</TITLE> 25564</HEAD> 25565<BODY> 25566<H1>Set Index Format</H1> 25567 25568This option is used to customize the content of lines in the 25569<A HREF="h_mail_index">MESSAGE INDEX screen</A>. 25570This action works exactly like the regular 25571"<!--#echo var="VAR_index-format"-->" option in the Setup/Config screen, 25572except that you can have a folder-specific value for it if you specify it here. 25573Consult the help for 25574"<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" 25575for more information. 25576 25577<P> 25578<UL> 25579<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 25580</UL><P> 25581<End of help on this topic> 25582</BODY> 25583</HTML> 25584====== h_config_index_format ===== 25585<HTML> 25586<HEAD> 25587<TITLE>OPTION: <!--#echo var="VAR_index-format"--></TITLE> 25588</HEAD> 25589<BODY> 25590<H1>OPTION: <!--#echo var="VAR_index-format"--></H1> 25591 25592This option is used to customize the content of lines in the 25593<A HREF="h_mail_index">MESSAGE INDEX screen</A>. Each line is intended 25594to convey some amount of immediately relevant information about each 25595message in the current folder. 25596<P> 25597 25598Alpine provides a pre-defined set of informational fields with 25599reasonable column widths automatically computed. You can, however, 25600replace this default set by listing special tokens in the order you 25601want them displayed. 25602<P> 25603 25604The list of available tokens is 25605<A HREF="h_index_tokens">here</A>. 25606<P> 25607 25608Spaces are used to separate listed tokens. Additionally, you can 25609specify how much of the screen's width the token's associated data 25610should occupy on the index line by appending to the token a pair of 25611parentheses enclosing either a number or percentage. For example, 25612"SUBJECT(13)" means to allocate 13 characters of space to the subject 25613column, and "SUBJECT(20%)" means to 25614allocate 20% of the available space 25615to the subjects column, while plain "SUBJECT" means the system will 25616attempt to figure out a reasonable amount of space. 25617<P> 25618 25619There is always one space between every pair of columns, so if you use fixed 25620column widths (like 13) you should remember to take that into account. 25621Several of the fields are virtually fixed-width, so it doesn't make 25622much sense to specify the width for them. The fields STATUS, 25623FULLSTATUS, IMAPSTATUS, MSGNO, the DATE fields, SIZE, 25624and DESCRIPSIZE all fall into that category. 25625You <EM>may</EM> specify widths for those if you wish, but 25626you're probably better off letting the system pick those widths. <P> 25627 25628<P> 25629The default is equivalent to: 25630 25631<P> 25632<CENTER><SAMP>STATUS MSGNO SMARTDATETIME24 FROMORTO(33%) SIZENARROW SUBJKEY(67%)</SAMP></CENTER> 25633 25634<P> 25635This means that the four fields without percentages will be allocated 25636first, and then 33% and 67% of the <EM>remaining</EM> space will go to 25637the from and subject fields. If one of those two fields is specified 25638as a percentage and the other is left for the system to choose, then 25639the percentage is taken as an absolute percentage of the screen, not 25640of the space remaining after allocating the first four columns. It 25641doesn't usually make sense to do it that way. If you leave off all 25642the widths, then the subject and from fields (if both are present) are 25643allocated space in a 2 to 1 ratio, which is almost exactly the same as 25644the default. 25645 25646<P> 25647What you are most likely to do with this configuration option is to 25648specify which fields appear at all, which order they appear in, and the 25649percentage of screen that is used for the from and subject fields if you 25650don't like the 2 to 1 default. 25651 25652<P> 25653If you want to retain the default format that Pine 4.64 had, use 25654 25655<P> 25656<CENTER><SAMP><!--#echo var="VAR_index-format"-->=STATUS MSGNO DATE FROMORTO(33%) SIZE SUBJKEY(67%)</SAMP></CENTER> 25657<P> 25658<EM>and</EM> set the feature 25659<A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A>. 25660<UL> 25661<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 25662</UL><P> 25663<End of help on this topic> 25664</BODY> 25665</HTML> 25666====== h_config_reply_intro ===== 25667<HTML> 25668<HEAD> 25669<TITLE>OPTION: <!--#echo var="VAR_reply-leadin"--></TITLE> 25670</HEAD> 25671<BODY> 25672<H1>OPTION: <!--#echo var="VAR_reply-leadin"--></H1> 25673 25674This option is used to customize the content of the introduction line 25675that is included when replying to a message and including the original 25676message in the reply. 25677The normal default (what you will get if you delete this variable) looks 25678something like: 25679<P> 25680<CENTER><SAMP>On Sat, 24 Oct 1998, Fred Flintstone wrote:</SAMP></CENTER> 25681<P> 25682where the day of the week is only included if it is available in the 25683original message. 25684You can replace this default with text of your own. 25685The text may contain tokens that are replaced with text 25686that depends on the message you are replying to. 25687For example, the default is equivalent to: 25688<P> 25689<CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:</SAMP></CENTER> 25690<P> 25691 25692Since this variable includes regular text mixed with special tokens 25693the tokens have to be surrounded by underscore characters. 25694For example, to use the token "<SAMP>PREFDATE</SAMP>" 25695you would need to use "<SAMP>_PREFDATE_</SAMP>", 25696not "<SAMP>PREFDATE</SAMP>". 25697<P> 25698The list of available tokens is 25699<A HREF="h_index_tokens">here</A>. 25700 25701<P> 25702By default, the text is all on a single line and is followed by a blank line. 25703If your "<!--#echo var="VAR_reply-leadin"-->" turns out to be longer 25704than 80 characters when replying to a particular message, it is shortened. 25705However, if you use the token 25706<P> 25707<CENTER><SAMP>_NEWLINE_</SAMP></CENTER> 25708<P> 25709 25710anywhere in the value, no end of line or blank line is appended, and no 25711shortening is done. 25712The _NEWLINE_ token may be used to get rid of the blank line following 25713the text, to add more blank lines, or to form a multi-line 25714"<!--#echo var="VAR_reply-leadin"-->". 25715To clarify how _NEWLINE_ works recall that the default value is: 25716<P> 25717<CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:</SAMP></CENTER> 25718<P> 25719 25720That is equivalent to 25721<P> 25722<CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:_NEWLINE__NEWLINE_</SAMP></CENTER> 25723<P> 25724 25725In the former case, two newlines are added automatically because 25726no _NEWLINE_ token appears in the value of the option (for backwards 25727compatibility). In the latter case, the newlines are explicit. 25728If you want to remove the blank line that follows the 25729"<!--#echo var="VAR_reply-leadin"-->" text use a single 25730_NEWLINE_ token like 25731<P> 25732<CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:_NEWLINE_</SAMP></CENTER> 25733<P> 25734 25735Because of the backwards compatibility problem, it is not possible to 25736remove all of the ends of lines, because then there will be no _NEWLINE_ tokens 25737and that will cause the automatic adding of two newlines! 25738If you want, you may embed newlines in the middle of the text, as well, 25739producing a multi-line "<!--#echo var="VAR_reply-leadin"-->". 25740 25741<P> 25742By default, no attempt is made to localize the date. 25743If you prefer a localized form you may find that one of the tokens 25744_PREFDATE_ or _PREFDATETIME_ is a satisfactory substitute. 25745If you want more control one of the many other date tokens, such as _DATEISO_, 25746might be better. 25747 25748<P> 25749For the adventurous, there is a way to conditionally include text based 25750on whether or not a token would result in specific replacement text. 25751For example, you could include some text based on whether or not 25752the _NEWS_ token would result in any newsgroups if it was used. 25753It's explained in detail 25754<A HREF="h_reply_token_conditionals">here</A>. 25755 25756<P> 25757In the very unlikely event that you want to include a literal token 25758in the introduction line you must precede it with a backslash character. 25759For example, 25760<P> 25761<CENTER><SAMP>\_DAYDATE_ = _DAYDATE_</SAMP></CENTER> 25762<P> 25763would produce something like 25764<P> 25765<CENTER><SAMP>_DAYDATE_ = Sat, 24 Oct 1998</SAMP></CENTER> 25766<P> 25767It is not possible to have a literal backslash followed by an expanded token. 25768<P> 25769<UL> 25770<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 25771</UL><P> 25772<End of help on this topic> 25773</BODY> 25774</HTML> 25775====== h_config_remote_abook_history ===== 25776<HTML> 25777<HEAD> 25778<TITLE>OPTION: <!--#echo var="VAR_remote-abook-history"--></TITLE> 25779</HEAD> 25780<BODY> 25781<H1>OPTION: <!--#echo var="VAR_remote-abook-history"--></H1> 25782 25783Sets how many extra copies of 25784remote address book 25785data will be kept in each remote address book folder. 25786The default is three. 25787These extra copies are simply old versions of the data. Each time a change 25788is made a new copy of the address book data is appended to the folder. Old 25789copies are trimmed, if possible, when Alpine exits. 25790An old copy can be put back into use by 25791deleting and expunging newer versions of the data from the folder. 25792Don't delete the first message from the folder. It is a special header 25793message for the remote address book and it must be there. 25794This is to prevent regular folders from being used as remote address book 25795folders and having their data destroyed. 25796<P> 25797This option is also used to determine how many extra copies of remote 25798Alpine configuration files are kept. 25799<P> 25800<UL> 25801<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 25802</UL><P> 25803<End of help on this topic> 25804</BODY> 25805</HTML> 25806====== h_config_remote_abook_validity ===== 25807<HTML> 25808<HEAD> 25809<TITLE>OPTION: <!--#echo var="VAR_remote-abook-validity"--></TITLE> 25810</HEAD> 25811<BODY> 25812<H1>OPTION: <!--#echo var="VAR_remote-abook-validity"--></H1> 25813 25814Sets the minimum number of minutes that a 25815remote address book will be considered up to date. 25816Whenever an entry contained in a remote address book is used, 25817if more than this many minutes have 25818passed since the last check the remote server will be queried to see if the 25819address book has changed. 25820If it has changed, the local copy is updated. 25821The default value is five minutes. 25822The special value of -1 means never check. 25823The special value of zero means only check when the address book is first 25824opened. 25825<P> 25826No matter what the value, the validity check is always done when the 25827address book is about to be changed by the user. 25828The check can be initiated manually by typing <EM>^L</EM> (Ctrl-L) 25829while in the address book maintenance screen for the remote address book. 25830<P> 25831<UL> 25832<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 25833</UL><P> 25834<End of help on this topic> 25835</BODY> 25836</HTML> 25837====== h_config_user_input_timeo ===== 25838<HTML> 25839<HEAD> 25840<TITLE>OPTION: <!--#echo var="VAR_user-input-timeout"--></TITLE> 25841</HEAD> 25842<BODY> 25843<H1>OPTION: <!--#echo var="VAR_user-input-timeout"--></H1> 25844 25845If this is set to an integer greater than zero, then this is the number 25846of <EM>hours</EM> to wait for user input before Alpine times out. 25847If Alpine is 25848in the midst of composing a message or is waiting for user response to 25849a question, then it will not timeout. 25850However, if Alpine is sitting idle waiting for 25851the user to tell it what to do next and the user does not give any 25852input for this many hours, Alpine will exit. 25853No expunging or moving of read 25854messages will take place. 25855It will exit similarly to the way it would exit 25856if it received a hangup signal. 25857This may be useful for cleaning up unused Alpine sessions that have been 25858forgotten by their owners. 25859The Alpine developers envision system administrators 25860setting this to a value of several hours (24?) so that it won't surprise 25861a user who didn't want to be disconnected. 25862<P> 25863<UL> 25864<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 25865</UL><P> 25866<End of help on this topic> 25867</BODY> 25868</HTML> 25869====== h_config_ssh_open_timeo ===== 25870<HTML> 25871<HEAD> 25872<TITLE>OPTION: <!--#echo var="VAR_ssh-open-timeout"--></TITLE> 25873</HEAD> 25874<BODY> 25875<H1>OPTION: <!--#echo var="VAR_ssh-open-timeout"--></H1> 25876 25877Sets the time in seconds that Alpine will 25878attempt to open a UNIX secure shell connection. 25879The default is 15, the minimum non-zero value is 5, 25880and the maximum is unlimited. If this is set to zero ssh connections 25881will be completely disabled. 25882<P> 25883<UL> 25884<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 25885</UL><P> 25886<End of help on this topic> 25887</BODY> 25888</HTML> 25889====== h_config_rsh_open_timeo ===== 25890<HTML> 25891<HEAD> 25892<TITLE>OPTION: <!--#echo var="VAR_rsh-open-timeout"--></TITLE> 25893</HEAD> 25894<BODY> 25895<H1>OPTION: <!--#echo var="VAR_rsh-open-timeout"--></H1> 25896 25897Sets the time in seconds that Alpine will 25898attempt to open a UNIX remote shell connection. 25899The default is 15, the minimum non-zero value is 5, 25900and the maximum is unlimited. If this is set to zero rsh connections 25901will be completely disabled. 25902This might be useful if rsh connections will never work in your environment 25903but are causing delays due to firewalls or some other reason. 25904<P> 25905<UL> 25906<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 25907</UL><P> 25908<End of help on this topic> 25909</BODY> 25910</HTML> 25911====== h_config_tcp_open_timeo ===== 25912<HTML> 25913<HEAD> 25914<TITLE>OPTION: <!--#echo var="VAR_tcp-open-timeout"--></TITLE> 25915</HEAD> 25916<BODY> 25917<H1>OPTION: <!--#echo var="VAR_tcp-open-timeout"--></H1> 25918 25919Sets the time in seconds that Alpine will 25920attempt to open a network connection. The default is 30, the minimum is 5, 25921and the maximum is system defined (typically 75). If a connection has not 25922completed within this many seconds Alpine will give up and consider it a 25923failed connection. 25924<P> 25925<UL> 25926<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 25927</UL><P> 25928<End of help on this topic> 25929</BODY> 25930</HTML> 25931====== h_config_tcp_readwarn_timeo ===== 25932<HTML> 25933<HEAD> 25934<TITLE>OPTION: <!--#echo var="VAR_tcp-read-warning-timeout"--></TITLE> 25935</HEAD> 25936<BODY> 25937<H1>OPTION: <!--#echo var="VAR_tcp-read-warning-timeout"--></H1> 25938 25939Sets the time in seconds that Alpine will 25940wait for a network read before warning you that things are moving slowly 25941and possibly giving you the option to break the connection. 25942The default is 15 seconds. The minimum is 5 seconds and the maximumn is 259431000 seconds. 25944<P> 25945Related option: <A HREF="h_config_tcp_query_timeo"><!--#echo var="VAR_tcp-query-timeout"--></A>. 25946<P> 25947<UL> 25948<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 25949</UL><P> 25950<End of help on this topic> 25951</BODY> 25952</HTML> 25953====== h_config_tcp_writewarn_timeo ===== 25954<HTML> 25955<HEAD> 25956<TITLE>OPTION: <!--#echo var="VAR_tcp-write-warning-timeout"--></TITLE> 25957</HEAD> 25958<BODY> 25959<H1>OPTION: <!--#echo var="VAR_tcp-write-warning-timeout"--></H1> 25960 25961Sets the time in seconds that Alpine will 25962wait for a network write before warning you that things are moving slowly 25963and possibly giving you the option to break the connection. 25964The default is 0 which means it is unset. If set to a non-zero value, the 25965minimum is 5 and the maximum is 1000. 25966<P> 25967Related option: <A HREF="h_config_tcp_query_timeo"><!--#echo var="VAR_tcp-query-timeout"--></A>. 25968<P> 25969<UL> 25970<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 25971</UL><P> 25972<End of help on this topic> 25973</BODY> 25974</HTML> 25975====== h_config_tcp_query_timeo ===== 25976<HTML> 25977<HEAD> 25978<TITLE>OPTION: <!--#echo var="VAR_tcp-query-timeout"--></TITLE> 25979</HEAD> 25980<BODY> 25981<H1>OPTION: <!--#echo var="VAR_tcp-query-timeout"--></H1> 25982 25983When Alpine times out a network read or write it will normally just display 25984a message saying "Still waiting". 25985However, if enough time has elapsed since it started waiting it will offer 25986to let you break the connection. 25987That amount of time is set by this option, which defaults to 60 seconds, 25988has a minimum of 5 seconds, and a maximum of 1000 seconds. 25989<P> 25990<UL> 25991<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 25992</UL><P> 25993<End of help on this topic> 25994</BODY> 25995</HTML> 25996====== h_config_quit_query_timeo ===== 25997<HTML> 25998<HEAD> 25999<TITLE>OPTION: <!--#echo var="VAR_close-connection-timeout"--></TITLE> 26000</HEAD> 26001<BODY> 26002<H1>OPTION: <!--#echo var="VAR_close-connection-timeout"--></H1> 26003 26004The original purpose of this option was to close a connection after this 26005much time has elapsed without response from the server. The problem this 26006generates is that a server might not reply on time due to a slow operation 26007(for example, sorting a large folder, or filtering messages, etc.) In those 26008situations it is desirable to wait for the server, even when this takes 26009a long time. 26010 26011<P> 26012In order to have a good compromise so that a user can distinguish between 26013when a connection is closed, therefore 26014we do not need to wait for it, and the operation that the user is waiting 26015for takes a long time, this option only applies to the 26016"NOOP" IMAP command. So, if a NOOP command has been issued, 26017and the connection does not return after the number of seconds configured 26018here, which must be at least the amount configured in the option 26019<a href="h_config_tcp_query_timeo"><!--#echo var="VAR_tcp-query-timeout"--></a>, 26020then Alpine will close the connection. 26021 26022<P> 26023Closing connections that have connectivity problems is a good idea. In an ideal 26024world, one would like all connections to be fast and reliable, so the amount 26025of time and effort put into parsing a folder to report its state when it is 26026opened is not wasted, so keeping connections alive is good, but the problem 26027with this is that waiting for a user to reply to a "keep connection 26028alive?" question can take a long time, and that might affect other 26029connections that could be closed because Alpine is not pinging them while it 26030is waiting for a reply from a user for a different connection. Therefore 26031setting this value helps to keep other connections alive, in case 26032you have several incoming folders in other servers. 26033 26034<P> 26035The default value for this option is 0, which means that no connections will 26036be closed automatically, so if you want connections to be closed automatically 26037you must set this option to a positive number bigger or equal than the 26038value of the option <!--#echo var="VAR_tcp-query-timeout"-->. 26039<P> 26040<UL> 26041<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26042</UL><P> 26043<End of help on this topic> 26044</BODY> 26045</HTML> 26046====== h_config_incoming_folders ===== 26047<HTML> 26048<HEAD> 26049<TITLE>OPTION: <!--#echo var="VAR_incoming-folders"--></TITLE> 26050</HEAD> 26051<BODY> 26052<H1>OPTION: <!--#echo var="VAR_incoming-folders"--></H1> 26053 26054This is a list of one or more folders other than <EM>INBOX</EM> that 26055may receive new messages. 26056It is related to the 26057<A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A> 26058feature. 26059This variable is normally manipulated with the Add, Delete, and Rename 26060commands in the FOLDER LIST for the Incoming Message Folders collection. 26061<P> 26062<UL> 26063<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26064</UL><P> 26065<End of help on this topic> 26066</BODY> 26067</HTML> 26068====== h_config_folder_spec ===== 26069<HTML> 26070<HEAD> 26071<TITLE>OPTION: <!--#echo var="VAR_folder-collections"--></TITLE> 26072</HEAD> 26073<BODY> 26074<H1>OPTION: <!--#echo var="VAR_folder-collections"--></H1> 26075 26076This is a list of one or more collections where saved mail is stored. 26077The first collection in this list is the default 26078collection for <EM>Save</EM>s, 26079including <A HREF="h_config_default_fcc"><!--#echo var="VAR_default-fcc"--></A>. 26080<P> 26081This variable is normally manipulated using the Setup/collectionList screen. 26082<P> 26083<UL> 26084<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26085</UL><P> 26086<End of help on this topic> 26087</BODY> 26088</HTML> 26089====== h_config_news_spec ===== 26090<HTML> 26091<HEAD> 26092<TITLE>OPTION: <!--#echo var="VAR_news-collections"--></TITLE> 26093</HEAD> 26094<BODY> 26095<H1>OPTION: <!--#echo var="VAR_news-collections"--></H1> 26096 26097This is a list of collections where news folders are located. 26098<P> 26099This variable is normally manipulated using the Setup/collectionList screen. 26100<P> 26101<UL> 26102<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26103</UL><P> 26104<End of help on this topic> 26105</BODY> 26106</HTML> 26107====== h_config_address_book ===== 26108<HTML> 26109<HEAD> 26110<TITLE>OPTION: <!--#echo var="VAR_address-book"--></TITLE> 26111</HEAD> 26112<BODY> 26113<H1>OPTION: <!--#echo var="VAR_address-book"--></H1> 26114 26115A list of personal address books. 26116Each entry in the list is an 26117optional nickname followed by a pathname or file name relative to the home 26118directory. 26119The nickname is separated from the rest of the line with whitespace. 26120Instead of a local pathname or file name, a remote folder name can be given. 26121This causes the address book to 26122be a Remote address book. 26123<P> 26124Use the Setup/AddressBook screen to modify this variable. 26125<P> 26126<UL> 26127<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26128</UL><P> 26129<End of help on this topic> 26130</BODY> 26131</HTML> 26132====== h_config_glob_addrbook ===== 26133<HTML> 26134<HEAD> 26135<TITLE>OPTION: <!--#echo var="VAR_global-address-book"--></TITLE> 26136</HEAD> 26137<BODY> 26138<H1>OPTION: <!--#echo var="VAR_global-address-book"--></H1> 26139 26140A list of shared address books. Each entry in the list is an 26141optional nickname followed by a pathname or file name relative to the home 26142directory. 26143A SPACE character separates the nickname from the rest of the line. 26144Instead of a local pathname or file name, a remote folder name can be given. 26145This causes the address book to 26146be a Remote address book. 26147Global address books are 26148defined to be ReadOnly. 26149<P> 26150Use the Setup/AddressBook screen to modify this variable. 26151<P> 26152<UL> 26153<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26154</UL><P> 26155<End of help on this topic> 26156</BODY> 26157</HTML> 26158====== h_config_last_vers ===== 26159<HTML> 26160<HEAD> 26161<TITLE>OPTION: <!--#echo var="VAR_last-version-used"--></TITLE> 26162</HEAD> 26163<BODY> 26164<H1>OPTION: <!--#echo var="VAR_last-version-used"--></H1> 26165 26166This is set automatically by Alpine. 26167It is used to keep track of the last version of Alpine that 26168was run by the user. 26169Whenever the version number increases, a new version message is printed out. 26170This may not be set in the system-wide configuration files. 26171<P> 26172<UL> 26173<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26174</UL><P> 26175<End of help on this topic> 26176</BODY> 26177</HTML> 26178====== h_config_printer ===== 26179<HTML> 26180<HEAD> 26181<TITLE>OPTION: Printer</TITLE> 26182</HEAD> 26183<BODY> 26184<H1>OPTION: Printer</H1> 26185 26186Your default printer selection. 26187<P> 26188Use the Setup/Printer screen to modify this variable. 26189<P> 26190<UL> 26191<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26192</UL><P> 26193<End of help on this topic> 26194</BODY> 26195</HTML> 26196====== h_config_print_cat ===== 26197<HTML> 26198<HEAD> 26199<TITLE>OPTION: <!--#echo var="VAR_personal-print-category"--></TITLE> 26200</HEAD> 26201<BODY> 26202<H1>OPTION: <!--#echo var="VAR_personal-print-category"--></H1> 26203 26204This is an internal Alpine variable. 26205It will be equal to 1, 2, or 3 depending on whether the default printer is 26206attached, standard, or a personal print command. 26207<P> 26208Use the Setup/Printer screen to modify this variable. 26209<P> 26210<UL> 26211<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26212</UL><P> 26213<End of help on this topic> 26214</BODY> 26215</HTML> 26216====== h_config_print_command ===== 26217<HTML> 26218<HEAD> 26219<TITLE>OPTION: <!--#echo var="VAR_personal-print-command"--></TITLE> 26220</HEAD> 26221<BODY> 26222<H1>OPTION: <!--#echo var="VAR_personal-print-command"--></H1> 26223 26224List of personal print commands. 26225<P> 26226Use the Setup/Printer screen to modify this variable. 26227<P> 26228<UL> 26229<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26230</UL><P> 26231<End of help on this topic> 26232</BODY> 26233</HTML> 26234====== h_config_pat_old ===== 26235<HTML> 26236<HEAD> 26237<TITLE>OPTION: Patterns</TITLE> 26238</HEAD> 26239<BODY> 26240<H1>OPTION: Patterns</H1> 26241 26242The option Patterns is obsolete in Alpine and in Pine 4.50 and later, replaced by the 26243options Patterns-Roles, Patterns-Filters, Patterns-Scores, Patterns-Indexcolors, 26244and Patterns-Other. 26245Patterns-Scores and Patterns-Filters have been replaced since then by 26246Patterns-Scores2 and Patterns-Filters2. 26247<P> 26248Use the Setup/Rules screens to modify these variable. 26249<P> 26250<UL> 26251<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26252</UL><P> 26253<End of help on this topic> 26254</BODY> 26255</HTML> 26256====== h_config_pat_roles ===== 26257<HTML> 26258<HEAD> 26259<TITLE>OPTION: <!--#echo var="VAR_patterns-roles"--></TITLE> 26260</HEAD> 26261<BODY> 26262<H1>OPTION: <!--#echo var="VAR_patterns-roles"--></H1> 26263 26264List of rules used for roles. 26265The option Patterns is obsolete in Alpine and in Pine 4.50 and later, replaced by this and 26266other options. 26267<P> 26268Use the Setup/Rules/Roles screen to modify this variable. 26269<P> 26270<UL> 26271<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26272</UL><P> 26273<End of help on this topic> 26274</BODY> 26275</HTML> 26276====== h_config_pat_filts ===== 26277<HTML> 26278<HEAD> 26279<TITLE>OPTION: <!--#echo var="VAR_patterns-filters2"--></TITLE> 26280</HEAD> 26281<BODY> 26282<H1>OPTION: <!--#echo var="VAR_patterns-filters2"--></H1> 26283 26284List of rules used for filters. 26285<P> 26286Use the Setup/Rules/Filters screen to modify this variable. 26287<P> 26288<UL> 26289<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26290</UL><P> 26291<End of help on this topic> 26292</BODY> 26293</HTML> 26294====== h_config_pat_scores ===== 26295<HTML> 26296<HEAD> 26297<TITLE>OPTION: <!--#echo var="VAR_patterns-scores2"--></TITLE> 26298</HEAD> 26299<BODY> 26300<H1>OPTION: <!--#echo var="VAR_patterns-scores2"--></H1> 26301 26302List of rules used for scoring. 26303<P> 26304Use the Setup/Rules/SetScores screen to modify this variable. 26305<P> 26306<UL> 26307<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26308</UL><P> 26309<End of help on this topic> 26310</BODY> 26311</HTML> 26312====== h_config_pat_other ===== 26313<HTML> 26314<HEAD> 26315<TITLE>OPTION: <!--#echo var="VAR_patterns-other"--></TITLE> 26316</HEAD> 26317<BODY> 26318<H1>OPTION: <!--#echo var="VAR_patterns-other"--></H1> 26319 26320List of rules used for miscellaneous configuration. 26321<P> 26322Use the Setup/Rules/Other screen to modify this variable. 26323<P> 26324<UL> 26325<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26326</UL><P> 26327<End of help on this topic> 26328</BODY> 26329</HTML> 26330====== h_config_pat_incols ===== 26331<HTML> 26332<HEAD> 26333<TITLE>OPTION: patterns-indexcolors</TITLE> 26334</HEAD> 26335<BODY> 26336<H1>OPTION: patterns-indexcolors</H1> 26337 26338List of rules used for coloring lines in the index. 26339<P> 26340Use the Setup/Rules/Indexcolor screen to modify this variable. 26341<P> 26342<UL> 26343<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26344</UL><P> 26345<End of help on this topic> 26346</BODY> 26347</HTML> 26348====== h_config_pat_srch ===== 26349<HTML> 26350<HEAD> 26351<TITLE>OPTION: patterns-search</TITLE> 26352</HEAD> 26353<BODY> 26354<H1>OPTION: patterns-search</H1> 26355 26356List of rules used only for searching with the Select command in the MESSAGE INDEX. 26357<P> 26358Use the Setup/Rules/searCh screen to modify this variable. 26359<P> 26360<UL> 26361<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26362</UL><P> 26363<End of help on this topic> 26364</BODY> 26365</HTML> 26366====== h_config_font_name ===== 26367<HTML> 26368<HEAD> 26369<TITLE>OPTION: Font Name</TITLE> 26370</HEAD> 26371<BODY> 26372<H1>OPTION: Font Name</H1> 26373 26374PC-Alpine only. 26375<P> 26376Name of normal font. 26377<P> 26378Use the pulldown Config menu to modify this variable. 26379<P> 26380<UL> 26381<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26382</UL><P> 26383<End of help on this topic> 26384</BODY> 26385</HTML> 26386====== h_config_font_size ===== 26387<HTML> 26388<HEAD> 26389<TITLE>OPTION: Font Size</TITLE> 26390</HEAD> 26391<BODY> 26392<H1>OPTION: Font Size</H1> 26393 26394PC-Alpine only. 26395<P> 26396Size of normal font. 26397<P> 26398Use the pulldown Config menu to modify this variable. 26399<P> 26400<UL> 26401<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26402</UL><P> 26403<End of help on this topic> 26404</BODY> 26405</HTML> 26406====== h_config_font_style ===== 26407<HTML> 26408<HEAD> 26409<TITLE>OPTION: Font Style</TITLE> 26410</HEAD> 26411<BODY> 26412<H1>OPTION: Font Style</H1> 26413 26414PC-Alpine only. 26415<P> 26416Style of normal font. 26417<P> 26418Use the pulldown Config menu to modify this variable. 26419<P> 26420<UL> 26421<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26422</UL><P> 26423<End of help on this topic> 26424</BODY> 26425</HTML> 26426====== h_config_font_char_set ===== 26427<HTML> 26428<HEAD> 26429<TITLE>OPTION: Font Character Set</TITLE> 26430</HEAD> 26431<BODY> 26432<H1>OPTION: Font Character Set</H1> 26433 26434PC-Alpine only. 26435<P> 26436Character set of normal font. 26437<P> 26438Use the pulldown Config menu to modify this variable. 26439<P> 26440<UL> 26441<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26442</UL><P> 26443<End of help on this topic> 26444</BODY> 26445</HTML> 26446====== h_config_print_font_name ===== 26447<HTML> 26448<HEAD> 26449<TITLE>OPTION: Print-Font-Name</TITLE> 26450</HEAD> 26451<BODY> 26452<H1>OPTION: Print-Font-Name</H1> 26453 26454PC-Alpine only. 26455<P> 26456Name of printer font. 26457<P> 26458Use the pulldown Config menu to modify this variable. 26459<P> 26460<UL> 26461<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26462</UL><P> 26463<End of help on this topic> 26464</BODY> 26465</HTML> 26466====== h_config_print_font_size ===== 26467<HTML> 26468<HEAD> 26469<TITLE>OPTION: Print-Font-Size</TITLE> 26470</HEAD> 26471<BODY> 26472<H1>OPTION: Print-Font-Size</H1> 26473 26474PC-Alpine only. 26475<P> 26476Size of printer font. 26477<P> 26478Use the pulldown Config menu to modify this variable. 26479<P> 26480<UL> 26481<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26482</UL><P> 26483<End of help on this topic> 26484</BODY> 26485</HTML> 26486====== h_config_print_font_style ===== 26487<HTML> 26488<HEAD> 26489<TITLE>OPTION: Print-Font-Style</TITLE> 26490</HEAD> 26491<BODY> 26492<H1>OPTION: Print-Font-Style</H1> 26493 26494PC-Alpine only. 26495<P> 26496Style of printer font. 26497<P> 26498Use the pulldown Config menu to modify this variable. 26499<P> 26500<UL> 26501<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26502</UL><P> 26503<End of help on this topic> 26504</BODY> 26505</HTML> 26506====== h_config_print_font_char_set ===== 26507<HTML> 26508<HEAD> 26509<TITLE>OPTION: Print-Font-Char-Set</TITLE> 26510</HEAD> 26511<BODY> 26512<H1>OPTION: Print-Font-Char-Set</H1> 26513 26514PC-Alpine only. 26515<P> 26516Character set of printer font. 26517<P> 26518Use the pulldown Config menu to modify this variable. 26519<P> 26520<UL> 26521<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26522</UL><P> 26523<End of help on this topic> 26524</BODY> 26525</HTML> 26526====== h_config_window_position ===== 26527<HTML> 26528<HEAD> 26529<TITLE>OPTION: Window-Position</TITLE> 26530</HEAD> 26531<BODY> 26532<H1>OPTION: Window-Position</H1> 26533 26534PC-Alpine only. 26535<P> 26536Position on the screen of the Alpine window. 26537<P> 26538Alpine normally maintains this variable itself, and it is set automatically. 26539This variable is provided to those who wish to use the same window position 26540across different machines from the same configuration. 26541<A HREF="h_config_winpos_in_config"><!--#echo var="FEAT_store-window-position-in-config"--></A> 26542must also be set for this setting to be used. 26543<P> 26544The format for this variable is of the form: <CODE>CxR+X+Y</CODE>, where 26545C is the number of columns, R is the number of rows, and X and Y specify the 26546top left corner of the window. 26547<P> 26548<UL> 26549<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26550</UL><P> 26551<End of help on this topic> 26552</BODY> 26553</HTML> 26554====== h_config_cursor_style ===== 26555<HTML> 26556<HEAD> 26557<TITLE>OPTION: Cursor Style</TITLE> 26558</HEAD> 26559<BODY> 26560<H1>OPTION: Cursor Style</H1> 26561 26562PC-Alpine only. 26563<P> 26564Cursor style. 26565<P> 26566Use the pulldown Config menu to modify this variable. 26567<P> 26568<UL> 26569<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26570</UL><P> 26571<End of help on this topic> 26572</BODY> 26573</HTML> 26574====== h_config_ldap_servers ===== 26575<HTML> 26576<HEAD> 26577<TITLE>OPTION: <!--#echo var="VAR_ldap-servers"--></TITLE> 26578</HEAD> 26579<BODY> 26580<H1>OPTION: <!--#echo var="VAR_ldap-servers"--></H1> 26581 26582List of LDAP servers and associated data. 26583<P> 26584Use the Setup/Directory screen to modify this variable. 26585<P> 26586<UL> 26587<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26588</UL><P> 26589<End of help on this topic> 26590</BODY> 26591</HTML> 26592====== h_config_sendmail_path ===== 26593<HTML> 26594<HEAD> 26595<TITLE>OPTION: <!--#echo var="VAR_sendmail-path"--></TITLE> 26596</HEAD> 26597<BODY> 26598<H1>OPTION: <!--#echo var="VAR_sendmail-path"--></H1> 26599 26600This names the path to an 26601alternative program, and any necessary arguments, to be used in posting 26602mail messages. See the Technical notes for more information. 26603<P> 26604<UL> 26605<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26606</UL><P> 26607<End of help on this topic> 26608</BODY> 26609</HTML> 26610====== h_config_oper_dir ===== 26611<HTML> 26612<HEAD> 26613<TITLE>OPTION: <!--#echo var="VAR_operating-dir"--></TITLE> 26614</HEAD> 26615<BODY> 26616<H1>OPTION: <!--#echo var="VAR_operating-dir"--></H1> 26617 26618This names the root of the 26619tree to which you are restricted when reading and writing folders and 26620files. It is usually used in the system-wide, 26621<EM>fixed</EM> configuration file. 26622<P> 26623<UL> 26624<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26625</UL><P> 26626<End of help on this topic> 26627</BODY> 26628</HTML> 26629====== h_config_rshpath ===== 26630<HTML> 26631<HEAD> 26632<TITLE>OPTION: <!--#echo var="VAR_rsh-path"--></TITLE> 26633</HEAD> 26634<BODY> 26635<H1>OPTION: <!--#echo var="VAR_rsh-path"--></H1> 26636 26637Sets the name of the command used to open a UNIX remote shell 26638connection. The default is typically <CODE>/usr/ucb/rsh</CODE>. 26639<P> 26640<UL> 26641<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26642</UL><P> 26643<End of help on this topic> 26644</BODY> 26645</HTML> 26646====== h_config_rshcmd ===== 26647<HTML> 26648<HEAD> 26649<TITLE>OPTION: <!--#echo var="VAR_rsh-command"--></TITLE> 26650</HEAD> 26651<BODY> 26652<H1>OPTION: <!--#echo var="VAR_rsh-command"--></H1> 26653 26654Sets the format of the command used to 26655open a UNIX remote shell connection. The default is 26656"%s %s -l %s exec /etc/r%sd". All four "%s" entries MUST exist in the 26657provided command. The first is for the command's pathname, the second is 26658for the host to connect to, the third is for the user to connect as, and 26659the fourth is for the connection method (typically <CODE>imap</CODE>). 26660<P> 26661<UL> 26662<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26663</UL><P> 26664<End of help on this topic> 26665</BODY> 26666</HTML> 26667====== h_config_sshpath ===== 26668<HTML> 26669<HEAD> 26670<TITLE>OPTION: <!--#echo var="VAR_ssh-path"--></TITLE> 26671</HEAD> 26672<BODY> 26673<H1>OPTION: <!--#echo var="VAR_ssh-path"--></H1> 26674 26675Sets the name of the command used to open a UNIX secure shell 26676connection. The default is typically <CODE>/usr/bin/ssh</CODE>. 26677<P> 26678<UL> 26679<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26680</UL><P> 26681<End of help on this topic> 26682</BODY> 26683</HTML> 26684====== h_config_sshcmd ===== 26685<HTML> 26686<HEAD> 26687<TITLE>OPTION: <!--#echo var="VAR_ssh-command"--></TITLE> 26688</HEAD> 26689<BODY> 26690<H1>OPTION: <!--#echo var="VAR_ssh-command"--></H1> 26691 26692Sets the format of the command used to 26693open a UNIX secure shell connection. The default is 26694"%s %s -l %s exec /etc/r%sd". All four "%s" entries MUST exist in the 26695provided command. The first is for the command's pathname, the second is 26696for the host to connect to, the third is for the user to connect as, and 26697the fourth is for the connection method (typically <CODE>imap</CODE>). 26698<P> 26699<UL> 26700<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26701</UL><P> 26702<End of help on this topic> 26703</BODY> 26704</HTML> 26705====== h_config_new_ver_quell ===== 26706<HTML> 26707<HEAD> 26708<TITLE>OPTION: <!--#echo var="VAR_new-version-threshold"--></TITLE> 26709</HEAD> 26710<BODY> 26711<H1>OPTION: <!--#echo var="VAR_new-version-threshold"--></H1> 26712 26713When a new version of Alpine is run for the first time it offers a 26714special explanatory screen to the user upon startup. This option 26715helps control when and if that special screen appears for users that 26716have previously run Alpine. It takes as its value an Alpine version 26717number. Alpine versions less than the specified value will suppress this 26718special screen while versions equal to or greater than that specified 26719will behave normally. 26720<P> 26721<UL> 26722<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26723</UL><P> 26724<End of help on this topic> 26725</BODY> 26726</HTML> 26727====== h_config_disable_drivers ===== 26728<HTML> 26729<HEAD> 26730<TITLE>OPTION: <!--#echo var="VAR_disable-these-drivers"--></TITLE> 26731</HEAD> 26732<BODY> 26733<H1>OPTION: <!--#echo var="VAR_disable-these-drivers"--></H1> 26734 26735This variable is a list of mail drivers that will be disabled. 26736The candidates for disabling are listed below. 26737There may be more in the future if you compile Alpine with 26738a newer version of the c-client library. 26739<P> 26740 26741<UL> 26742<LI> mbox 26743<LI> mbx 26744<LI> mh 26745<LI> mmdf 26746<LI> mtx 26747<LI> mx 26748<LI> news 26749<LI> phile 26750<LI> tenex 26751<LI> unix 26752</UL> 26753<P> 26754 26755The <EM>mbox</EM> driver enables the following behavior: if there is a 26756file called <CODE>mbox</CODE> 26757in your home directory, and if that file is either empty or in Unix mailbox 26758format, then every time you open <EM>INBOX</EM> the <EM>mbox</EM> driver 26759will automatically transfer mail from the system mail spool directory into the 26760<CODE>mbox</CODE> file and 26761delete it from the spool directory. If you disable the <EM>mbox</EM> driver, 26762this will not happen. 26763<P> 26764 26765It is not recommended to disable the driver that supports the system default 26766mailbox format. On most non-SCO systems, that driver is the 26767<EM>unix</EM> driver. 26768On most SCO systems, it is the <EM>mmdf</EM> driver. 26769The system default driver may be 26770configured to something else on your system; check with your system manager 26771for additional information. 26772<P> 26773 26774It is most likely not very useful for you to disable any of the drivers other 26775than possibly <EM>mbox</EM>. 26776You could disable some of the others if you know for 26777certain that you don't need them but the performance gain in doing so 26778is very modest. 26779<P> 26780<UL> 26781<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26782</UL><P> 26783<End of help on this topic> 26784</BODY> 26785</HTML> 26786====== h_config_disable_auths ===== 26787<HTML> 26788<HEAD> 26789<TITLE>OPTION: <!--#echo var="VAR_disable-these-authenticators"--></TITLE> 26790</HEAD> 26791<BODY> 26792<H1>OPTION: <!--#echo var="VAR_disable-these-authenticators"--></H1> 26793 26794This variable is a list of SASL (Simple Authentication and Security 26795Layer) authenticators that will be disabled. 26796SASL is a mechanism for 26797authenticating to IMAP, POP3, SMTP, and other network servers. 26798<P> 26799 26800Alpine matches its list of supported authenticators with the server to 26801determine the most secure authenticator that is supported by both. 26802If no matching authenticators are found, Alpine will revert to plaintext 26803login (or, in the case of SMTP, will be unable to authenticate at all). 26804<P> 26805The candidates for disabling can be found <A HREF="X-Alpine-Config:">here</A>. 26806<P> 26807 26808Normally, you will not disable any authenticators. 26809There are two exceptions: 26810<P> 26811<OL> 26812<LI> You use a broken server that advertises an authenticator, 26813but does not actually implement it. 26814<LI> You have a Kerberos-capable version of Alpine and the server is 26815also Kerberos-capable, but you can not obtain Kerberos 26816credentials on the server machine, thus you desire to disable 26817GSSAPI (which in turn disables Alpine's Kerberos support). 26818</OL> 26819<P> 26820It is never necessary to disable authenticators, since Alpine will try 26821other authenticators before giving up. 26822However, disabling the relevant authenticator avoids annoying error messages. 26823<P> 26824<UL> 26825<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26826</UL><P> 26827<End of help on this topic> 26828</BODY> 26829</HTML> 26830====== h_config_encryption_range ===== 26831<HTML> 26832<HEAD> 26833<TITLE>OPTION: <!--#echo var="VAR_encryption-protocol-range"--></TITLE> 26834</HEAD> 26835<BODY> 26836<H1>OPTION: <!--#echo var="VAR_encryption-protocol-range"--></H1> 26837 26838This option sets a range of encryption protocols that can be attempted when 26839Alpine will try to establish a secure connection using the SSL or TLS 26840protocols. 26841 26842<P> 26843Before a secure connection to an external server is established, Alpine and the 26844server will attempt to negotiate a secure connection. This part is known as the 26845"ClientHello". At that time Alpine will announce the version of 26846encryption that it would like to establish. The server can reject that, and announce 26847a different version of encryption. Once both the server and Alpine have found 26848a version of encryption that they both agree on, they will both use it to start 26849a secure connection. 26850 26851<P> 26852The use of the /ssl parameter in the definition of the server will make Alpine 26853attempt the highest encryption protocol that it can use, in agreement with the 26854server. However, using this option, you will set limits to the versions of 26855the protocols that are used. This would, for example, allow you to disable the use 26856of ssl3, in favor of more modern protocols. 26857 26858<P> 26859For purposes of this option, the protocols are sorted 26860as follows 26861 26862<P> 26863<CENTER> 26864no_min < ssl3 < tls1 < tls1_1 < tls1_2 < tls1_3 < no_max 26865</CENTER> 26866 26867<P> 26868For example, if you want to disable ssl3, all you have to do is to set the minimum 26869version to tls1, or any higher protocol. 26870 26871<P>The name of the parameters used to configure this option is the same as the 26872parameters that are added to the definition of a server to make it a secure 26873connection, and they are listed above for your reference. 26874 26875<P> 26876The special values "no_min" and "no_max" do not set values 26877for the minimum and maximum protocol versions, and Alpine will use the maximum 26878and minimum values of encryption protocols built into your SSL library. 26879 26880<P> 26881<UL> 26882<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26883</UL><P> 26884<End of help on this topic> 26885</BODY> 26886</HTML> 26887====== h_config_abook_metafile ===== 26888<HTML> 26889<HEAD> 26890<TITLE>OPTION: <!--#echo var="VAR_remote-abook-metafile"--></TITLE> 26891</HEAD> 26892<BODY> 26893<H1>OPTION: <!--#echo var="VAR_remote-abook-metafile"--></H1> 26894 26895This is usually set by Alpine and is the name of a file 26896that contains data about 26897remote address books and remote configuration files. 26898<P> 26899<UL> 26900<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26901</UL><P> 26902<End of help on this topic> 26903</BODY> 26904</HTML> 26905====== h_config_composer_wrap_column ===== 26906<HTML> 26907<HEAD> 26908<TITLE>OPTION: <!--#echo var="VAR_composer-wrap-column"--></TITLE> 26909</HEAD> 26910<BODY> 26911<H1>OPTION: <!--#echo var="VAR_composer-wrap-column"--></H1> 26912 26913 26914This option specifies an aspect of Alpine's Composer. This gives the 26915maximum width that auto-wrapped lines will have. It's also the maximum 26916width of lines justified using the <A HREF="h_compose_justify">^J 26917Justify</A> command. The normal default 26918is "74". The largest allowed setting is normally "80" 26919in order to 26920prevent very long lines from being sent in outgoing mail. When the mail 26921is actually sent, trailing spaces will be stripped off of each line. 26922 26923<P> 26924<UL> 26925<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26926</UL><P> 26927<End of help on this topic> 26928</BODY> 26929</HTML> 26930====== h_config_deadlets ===== 26931<HTML> 26932<HEAD> 26933<TITLE>OPTION: <!--#echo var="VAR_dead-letter-files"--></TITLE> 26934</HEAD> 26935<BODY> 26936<H1>OPTION: <!--#echo var="VAR_dead-letter-files"--></H1> 26937 26938 26939This option affects Alpine's behavior when you cancel a message being 26940composed. Alpine's usual behavior is to write the canceled message to 26941a file named 26942<!--chtml if pinemode="os_windows"--> 26943"DEADLETR", 26944<!--chtml else--> 26945"dead.letter" in your home directory, 26946<!--chtml endif--> 26947overwriting any previous message. 26948<P> 26949If you set this option to a value higher than one, then that many copies 26950of dead letter files will be saved. 26951For example, if you set this option to "3" then you may have 26952files named 26953<!--chtml if pinemode="os_windows"--> 26954"DEADLETR", 26955"DEADLETR2", and 26956"DEADLETR3". 26957<!--chtml else--> 26958"dead.letter", 26959"dead.letter2", and 26960"dead.letter3" in your home directory. 26961<!--chtml endif--> 26962In this example, the most recently cancelled message will be in 26963<!--chtml if pinemode="os_windows"--> 26964"DEADLETR", 26965<!--chtml else--> 26966"dead.letter", 26967<!--chtml endif--> 26968and the third most recently cancelled message will be in 26969<!--chtml if pinemode="os_windows"--> 26970"DEADLETR3". 26971<!--chtml else--> 26972"dead.letter3". 26973<!--chtml endif--> 26974The fourth most recently cancelled message will no longer be saved. 26975 26976<P> 26977If you set this option to zero, then NO record of canceled messages is 26978maintained. 26979<P> 26980If the feature 26981<A HREF="h_config_quell_dead_letter"><!--#echo var="FEAT_quell-dead-letter-on-cancel"--></A> 26982is set, that overrides whatever you set for this option. 26983If this option had existed at the time, then the Quell feature would not 26984have been added, but it is still there for backwards compatibility. 26985So, in order for this option to have the desired effect, make sure the 26986Quell feature is turned off. 26987 26988<P> 26989<UL> 26990<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 26991</UL><P> 26992<End of help on this topic> 26993</BODY> 26994</HTML> 26995====== h_config_maxremstream ===== 26996<HTML> 26997<HEAD> 26998<TITLE>OPTION: <!--#echo var="VAR_max-remote-connections"--></TITLE> 26999</HEAD> 27000<BODY> 27001<H1>OPTION: <!--#echo var="VAR_max-remote-connections"--></H1> 27002 27003This option affects low-level behavior of Alpine. 27004The default value for this option is <EM>3</EM>. 27005If your INBOX is accessed using the IMAP protocol 27006from an IMAP server, that connection is kept open throughout the 27007duration of your Alpine session, independent of the value of this option. 27008The same is true of any 27009<A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A> 27010you have defined. 27011This option controls Alpine's behavior when connecting to remote IMAP folders 27012other than your INBOX or your <!--#echo var="VAR_stay-open-folders"-->. 27013It specifies the maximum number of remote IMAP connections (other than 27014those mentioned above) that Alpine will use for accessing the rest of your 27015folders. 27016If you set this option to zero, you will turn off most remote connection 27017re-use. 27018It's difficult to understand exactly what this option does, and it is usually 27019fine to leave it set to its default value. 27020It is probably more likely that you will be interested in setting the 27021<A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A> option 27022instead of changing the value of this option. 27023A slightly longer explanation of what is going on with this option 27024is given in the next paragraphs. 27025 27026<P> 27027There are some time costs involved in opening and closing remote IMAP 27028folders, the main costs being the time you have to wait for the connection 27029to the server and the time for the folder to open. 27030Opening a folder may involve not only the time the server takes to do its 27031processing but time that Alpine uses to do filtering. 27032These times can vary widely. 27033They depend on how loaded the server is, how large 27034the folder being opened is, and how you set up filtering, among other things. 27035Once Alpine has opened a connection to a particular folder, it will attempt 27036to keep that connection open in case you use it again. 27037In order to do this, 27038Alpine will attempt to use the <!--#echo var="VAR_max-remote-connections"--> (the value of 27039this option) IMAP connections you have allotted for this purpose. 27040<P> 27041For example, suppose the value of this option is set to "2". 27042If your INBOX is accessed on a remote server using the IMAP protocol, that 27043doesn't count as one of the remote connections but it is always kept open. 27044If you then open another IMAP folder, that would be your first 27045remote connection counted as one of the <!--#echo var="VAR_max-remote-connections"--> connections. 27046If you open a third folder the second will be left open, in case you 27047return to it. 27048You won't be able to tell it has been left open. 27049It will appear to be closed when you leave the folder but the connection 27050will remain in the background. 27051Now suppose you go back to the second folder (the first folder after the 27052INBOX). 27053A connection to that folder is still open so you won't have to wait 27054for the startup time to open it. 27055Meanwhile, the connection to the third folder will be left behind. 27056Now, if you open a fourth folder, you will bump into the 27057<!--#echo var="VAR_max-remote-connections"--> limit, because this will be the third folder other 27058than INBOX and you have the option set to "2". 27059The connection that is being used for 27060the third folder will be re-used for this new fourth folder. 27061If you go back to the third folder after this, it is no longer already 27062connected when you get there. 27063You'll still save some time since Alpine will re-use the connection to the 27064fourth folder and you have already logged in on that connection, 27065but the folder will have to be re-opened from scratch. 27066<P> 27067If a folder is large and the startup cost is dominated by the time it takes 27068to open that folder or to run filters on it, then it will pay to make the 27069value of this option large enough to keep it open. 27070On the other hand, if you only revisit a handful of folders or if 27071the folders are small, then it might 27072make more sense to keep this number small so that the reconnect 27073time (the time to start up a new connection and authenticate) 27074is eliminated instead. 27075<P> 27076You may also need to consider the impact on the server. 27077On the surface, a larger number here may cause a larger impact on the 27078server, since you will have more connections open to the server. 27079On the other hand, not only will <EM>you</EM> be avoiding the startup costs 27080associated with reopening a folder, but the <EM>server</EM> will be 27081avoiding those costs as well. 27082<P> 27083When twenty five minutes pass without any active use of an IMAP connection 27084being saved for possible re-use, that connection will be shut down, 27085 27086<P> 27087<UL> 27088<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 27089</UL><P> 27090<End of help on this topic> 27091</BODY> 27092</HTML> 27093====== h_config_permlocked ===== 27094<HTML> 27095<HEAD> 27096<TITLE>OPTION: <!--#echo var="VAR_stay-open-folders"--></TITLE> 27097</HEAD> 27098<BODY> 27099<H1>OPTION: <!--#echo var="VAR_stay-open-folders"--></H1> 27100 27101This option affects low-level behavior of Alpine. 27102There is no default value for this option. 27103It is related to the options 27104<A HREF="h_config_preopen_stayopens">"<!--#echo var="FEAT_preopen-stayopen-folders"-->"</A>, 27105<A HREF="h_config_maxremstream">"<!--#echo var="VAR_max-remote-connections"-->"</A>, 27106and <A HREF="h_config_expunge_stayopens">"<!--#echo var="FEAT_offer-expunge-of-stayopen-folders"-->"</A>. 27107 27108<P> 27109Note: changes made to this list take effect the next time you open a 27110folder in the list. 27111 27112<P> 27113This is a list of folders that will be permanently kept open once they 27114are first opened. 27115The names in this list may be either the nickname of an Incoming folder 27116or the full technical specification of a folder. 27117The folders in this list need not be remote IMAP folders, they could usefully 27118be local folders, as well. 27119If a folder in the list is a newsgroup or is not accessed either locally 27120or via IMAP, then the entry will be ignored. 27121For example, folders accessed via NNTP or POP3 will not be kept open, since 27122the way that new mail is found with those protocols involves closing and 27123reopening the connection. 27124<P> 27125Once a Stay Open folder has been opened, new-mail checking will continue 27126to happen on that folder for the rest of the Alpine session. 27127Your INBOX is always implicitly included in this Stay-Open list and doesn't 27128need to be added explicitly. 27129<P> 27130Another difference that you may notice between a Stay Open folder and a 27131non-Stay Open folder is which message is selected as the current message 27132when you enter the folder index. 27133Normally, the starting position for an incoming folder (which most Stay Open 27134folders will likely be) is controlled by the 27135<A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A>. 27136However, if a folder is a Stay Open folder, when you re-enter the folder 27137after the first time the current message will be the same as it was when 27138you left the folder. 27139An exception is made if you use the TAB command to get to the folder. 27140In that case, the message number will be incremented by one from what it 27141was when you left the folder. 27142<P> 27143The above special behavior is thought to be useful. 27144However, it is special and different from what you might at first expect. 27145The feature 27146<A HREF="h_config_use_reg_start_for_stayopen"><!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></A> 27147may be used to turn off this special treatment. 27148<P> 27149If the message that was current when you left the folder no longer exists, 27150then the regular startup rule will be used instead. 27151 27152<P> 27153<UL> 27154<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 27155</UL><P> 27156<End of help on this topic> 27157</BODY> 27158</HTML> 27159====== h_config_viewer_overlap ===== 27160<html> 27161<header> 27162<title>OPTION: <!--#echo var="VAR_viewer-overlap"--></title> 27163</header> 27164<body> 27165<h1>OPTION: <!--#echo var="VAR_viewer-overlap"--></h1> 27166 27167This option specifies an aspect of Alpine's Message Viewing screen. When 27168the space bar is used to page forward in a message, the number of lines 27169specified by the "<!--#echo var="VAR_viewer-overlap"-->" variable will be repeated from the 27170bottom of the screen. That is, if this was set to two lines, then the 27171bottom two lines of the screen would be repeated on the top of the next 27172screen. The normal default value is "2".<p> 27173<UL> 27174<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 27175</UL><P> 27176<End of help on this topic> 27177</body> 27178</html> 27179====== h_config_scroll_margin ===== 27180<HTML> 27181<HEAD> 27182<TITLE>OPTION: <!--#echo var="VAR_scroll-margin"--></TITLE> 27183</HEAD> 27184<BODY> 27185<H1>OPTION: <!--#echo var="VAR_scroll-margin"--></H1> 27186 27187This option controls when Alpine's line-by-line scrolling occurs. 27188Typically, when a selected item is at the top or bottom screen edge 27189and the UP or DOWN (and Ctrl-P or Ctrl-N) keys are struck, the 27190displayed items are scrolled down or up by a single line. 27191 27192<P> 27193This option allows you to tell Alpine the number of lines from the top and 27194bottom screen edge that line-by-line paging should occur. For example, 27195setting this value to one (1) will cause Alpine to scroll the display 27196vertically when you move to select an item on the display's top or 27197bottom edge. 27198 27199<P> 27200By default, this variable is zero, indicating that scrolling happens 27201when you move up or down to select an item immediately off the display's 27202top or bottom edge. 27203 27204<P> 27205<UL> 27206<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 27207</UL><P> 27208<End of help on this topic> 27209</BODY> 27210</HTML> 27211====== h_config_wordseps ===== 27212<HTML> 27213<HEAD> 27214<TITLE>OPTION: <!--#echo var="VAR_composer-word-separators"--></TITLE> 27215</HEAD> 27216<BODY> 27217<H1>OPTION: <!--#echo var="VAR_composer-word-separators"--></H1> 27218 27219This option affects how a "word" is defined in the composer. 27220The definition of a word is used when using the Forward Word and Backward 27221Word commands in the composer, as well as when using the spell checker. 27222Whitespace is always considered a word separator. 27223Punctuation (like question marks, periods, commas, and so on) is always 27224a word separator if it comes at the end of a word. 27225By default, a punctuation character that is in the middle of a word does 27226not break up that word as long as the character before and the character 27227after it are both alphanumeric. 27228If you add a character to this option it will be considered a 27229word separator even when it occurs in the middle of an alphanumeric word. 27230For example, if you want to skip through each part of an address instead 27231of skipping the whole address at once you might want to include "@" 27232and "." in this list. 27233If you want the word-skipper to stop on each part of a UNIX filename you 27234could add "/" to the list. 27235The equal sign and dash are other possibilities you might find helpful. 27236<P> 27237<UL> 27238<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 27239</UL><P> 27240<End of help on this topic> 27241</BODY> 27242</HTML> 27243====== h_config_reply_indent_string ===== 27244<HTML> 27245<HEAD> 27246<TITLE>OPTION: <!--#echo var="VAR_reply-indent-string"--></TITLE> 27247</HEAD> 27248<BODY> 27249<H1>OPTION: <!--#echo var="VAR_reply-indent-string"--></H1> 27250 27251This option specifies an aspect of Alpine's Reply command. 27252When a message is replied to and the text of the message is included, the 27253included text usually has the string "> " prepended 27254to each line indicating it is quoted text. 27255(In case you haven't seen this before, "string" is a technical term 27256that means chunk of text.) 27257 27258<P> 27259Because of the introduction of <A HREF="h_config_quell_flowed_text">Flowed Text</A> 27260in 1999 and its wide-spread adoption since then, you will usually be better off if you 27261use one of the standard values, 27262"> " or ">", for this option. 27263 27264<P> 27265This option specifies a different value for that string. 27266If you wish to use a string that begins or ends with a space, 27267enclose the string in double quotes. 27268 27269<P> 27270Besides simple text, the prepended string can be based 27271on the message being replied to. 27272The following tokens are substituted for the message's corresponding value: 27273 27274<DL> 27275<DT>_FROM_</DT> 27276<DD>This token gets replaced with the message sender's "username". 27277If the name is longer than six characters, only the first six characters are 27278used. 27279</DD> 27280 27281<DT>_NICK_</DT> 27282<DD>This token gets replaced with the nickname of the message sender's 27283address as found in your addressbook. 27284If no addressbook entry is found, 27285Alpine replaces the characters "_NICK_" with nothing. 27286If the nickname is longer than six characters, only the first six characters are 27287used. 27288</DD> 27289 27290<DT>_INIT_</DT> 27291<DD>This token gets replaced with the initials of the sender of the message. 27292</DD> 27293 27294</DL> 27295 27296NOTE: When the 27297<A HREF="h_config_prefix_editing">"<!--#echo var="FEAT_enable-reply-indent-string-editing"-->"</A> 27298feature is enabled, you are given the opportunity to edit the string, whether 27299it is the default or one automatically generated using the above tokens. 27300<P> 27301If you change your <!--#echo var="VAR_reply-indent-string"--> 27302so that it is not equal to the default value of "> ", then 27303quoted text will not be flowed 27304(<A HREF="h_config_quell_flowed_text">Flowed Text</A>) 27305when you reply. 27306For this reason, we recommend that you leave your <!--#echo var="VAR_reply-indent-string"--> 27307set to the default value. 27308<P> 27309<UL> 27310<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 27311</UL><P> 27312<End of help on this topic> 27313</BODY> 27314</HTML> 27315====== h_config_quote_replace_string ===== 27316<HTML> 27317<HEAD> 27318<TITLE>OPTION: <!--#echo var="VAR_quote-replace-string"--></TITLE> 27319</HEAD> 27320<BODY> 27321<H1>OPTION: <!--#echo var="VAR_quote-replace-string"--></H1> 27322 27323This option specifies what string to use as a quote when <b>viewing</b> a 27324message. The standard way of quoting messages when replying is the string 27325"> " (quote space). 27326With this variable set, viewing a message will 27327replace occurrences of 27328"> " and ">" with the replacement string. 27329This setting works best when 27330<A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A> 27331or the equivalent setting in your correspondents' mail programs 27332is set to the default 27333"> ", but it will also work fine with the 27334<!--#echo var="VAR_reply-indent-string"--> set to ">". 27335<P> 27336By default, this setting will only work on messages that are flowed, which is 27337the default way of sending messages for many mail clients including 27338Alpine. Enable the feature 27339<A HREF="h_config_quote_replace_noflow"><!--#echo var="FEAT_quote-replace-nonflowed"--></A> 27340to also have quote-replacement performed on non-flowed messages. 27341<P> 27342 27343Setting this option will replace ">" and 27344"> " with the new setting. This string may include trailing 27345spaces. To preserve those spaces enclose the full string in double quotes. 27346<P> 27347No padding to separate the text of the message from the quote string is 27348added. This means that if you do not add trailing spaces to the value of 27349this variable, text will be displayed right next to the quote string, 27350which may be undesirable. This can be avoided by adding a new string 27351separated by a space from your selection of quote string replacement. This 27352last string will be used for padding. For example, setting this variable to 27353<br>">" " " has the effect of setting 27354">" as the <!--#echo var="VAR_quote-replace-string"-->, with the text padded by 27355a space from the last quote string to make it more readable. 27356<P> 27357One possible setting for this variable could be 27358" " (four spaces wrapped in quotes), which 27359would have the effect of indenting each level of quoting four spaces and 27360removing the ">"'s. Different levels of quoting could be made 27361more discernible by setting colors for quoted text. 27362<P> 27363Replying to or forwarding the viewed message will preserve the original 27364formatting of the message, so quote-replacement will not be performed on 27365messages that are being composed. 27366<P> 27367<UL> 27368<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 27369</UL><P> 27370<End of help on this topic> 27371</BODY> 27372</HTML> 27373====== h_config_empty_hdr_msg ===== 27374<HTML> 27375<HEAD> 27376<TITLE>OPTION: <!--#echo var="VAR_empty-header-message"--></TITLE> 27377</HEAD> 27378<BODY> 27379<H1>OPTION: <!--#echo var="VAR_empty-header-message"--></H1> 27380 27381When sending, if both the To and Cc fields are empty and you 27382are sending the message to a Bcc, 27383Alpine will put a special address in the To line. The default value is: 27384 27385<P> 27386<CENTER><SAMP>undisclosed-recipients: ;</SAMP></CENTER> 27387 27388<P> 27389The reason for this is to avoid embarrassment caused by some Internet 27390mail transfer software that interprets a "missing" 27391<SAMP>To:</SAMP> header as an error and replaces it with an 27392<SAMP>Apparently-to:</SAMP> header that may contain the addresses you 27393entered on the <SAMP>Bcc:</SAMP> line, defeating the purpose of the 27394Bcc. You may change the part of this message that comes before the 27395": ;" by setting the "<!--#echo var="VAR_empty-header-message"-->" 27396variable to something else. 27397 27398<P> 27399The normal default is "undisclosed-recipients". 27400 27401<P> 27402<UL> 27403<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 27404</UL><P> 27405<End of help on this topic> 27406</BODY> 27407</HTML> 27408====== h_config_status_msg_delay ===== 27409<HTML> 27410<HEAD> 27411<TITLE>OPTION: <!--#echo var="VAR_status-message-delay"--></TITLE> 27412</HEAD> 27413<BODY> 27414<H1>OPTION: <!--#echo var="VAR_status-message-delay"--></H1> 27415 27416This option has evolved over time, causing the possible values to be 27417counter-intuitive. 27418Read carefully before you set this option. 27419First we explain what the option does, then there is a longer discussion 27420following that. 27421<P> 27422If this is set to zero, the default value, it has <EM>no</EM> effect. 27423Positive and negative values serve two similar, but different purposes. 27424<P> 27425If it is set to a positive number, it causes the cursor to move to the 27426status line whenever a status message is printed and pause there for this 27427many seconds. 27428It will probably only be useful if the 27429<A HREF="h_config_show_cursor">"<!--#echo var="FEAT_show-cursor"-->"</A> feature is 27430also turned on. 27431Setting this option to a positive number can only be used to 27432<EM>increase</EM> the status message delay. 27433This may be useful for Braille displays, or other non-traditional displays. 27434<P> 27435If it is set to a negative number the interpretation is a bit complicated. 27436Negative numbers are used to <EM>decrease</EM> the amount of delay Alpine uses to 27437allow you to read important status messages. 27438Of course, this may cause you to miss some important messages. 27439If you see a message flash by but miss what it says you can use the 27440Journal command from the MAIN MENU to read it. 27441If you set this option to a negative value, the delay will be 27442no more than one second less than the absolute value 27443of the value you set. 27444So if you set it to -1, the delay will be no more than zero seconds, no 27445delay at all. 27446If you set it to -2, the delay will be no more than 1 second. 27447And so on, -3 is 2 seconds, -4 is 3 seconds, ... 27448If the delay that Alpine would have used by default is less than this delay, 27449then the smaller delay set by Alpine will be used. 27450Setting this option to a negative value can only reduce the amount of 27451delay, never increase it. 27452<P> 27453Here is a more detailed explanation. 27454Status messages are the messages that show up spontaneously in the 27455status message line, usually the third line from the bottom of the screen. 27456By default, Alpine assigns each status message it produces a minimum 27457display time. 27458Some status messages have a minimum display time of zero. 27459You can see an example of such a message by paging up in this help text 27460until you reach the top of the screen. 27461If you try to page past the top you will see the message 27462<P> 27463<CENTER><SAMP>[Already at start of help text]</SAMP></CENTER> 27464<P> 27465in the status line. 27466If there is another more important use of the status message line this message 27467might be replaced quickly, or it even might not be shown at all. 27468However, if there is no reason to get rid of the message, it might stay 27469there for several seconds while you read the help. 27470An example where it is replaced immediately happens when you page up in 27471the help text past the top of the screen, but then type the "WhereIs" 27472command right after paging up. 27473The message will disappear immediately without causing a delay (unless you 27474have set this option to a positive value) to allow you to type input for 27475the "WhereIs" command. 27476Since it isn't a very important message, Alpine has set its minimum display 27477time to zero seconds. 27478<P> 27479Other messages have minimum display times of three or more seconds. 27480These are usually error messages that Alpine thinks you ought to see. 27481For example, it might be a message about a failed Save or a failed folder open. 27482It is often the case that this minimum display time won't delay you in 27483any way because the status message line is not needed for another reason. 27484However, there are times when Alpine has to delay what it is doing in 27485order to display a status message for the minimum display time. 27486This happens when a message is being displayed and Alpine wants to ask 27487for input from the keyboard. 27488For example, when you Save a message you use the status message line. 27489You get a prompt there asking for the name of the folder to save to. 27490If there is a status message being displayed that has not 27491yet displayed for its minimum 27492time Alpine will display that status message surrounded with the characters 27493> and < to show you that it is delaying. 27494That might happen, for example, if you tried to save to a folder that 27495caused an error, then followed that immediately with another Save command. 27496You might find yourself waiting for a status message like 27497<P> 27498<CENTER><SAMP>[>Can't get write access to mailbox, access is readonly<]</SAMP></CENTER> 27499<P> 27500to finish displaying for three seconds. 27501If that is something you find happening to you frequently, you may use 27502negative values of this option to decrease or eliminate that delay, at 27503the risk of missing the message. 27504<P> 27505<UL> 27506<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 27507</UL><P> 27508<End of help on this topic> 27509</BODY> 27510</HTML> 27511====== h_config_active_msg_interval ===== 27512<HTML> 27513<HEAD> 27514<TITLE>OPTION: <!--#echo var="VAR_busy-cue-rate"--></TITLE> 27515</HEAD> 27516<BODY> 27517<H1>OPTION: <!--#echo var="VAR_busy-cue-rate"--></H1> 27518 27519When Alpine is delayed for some reason it usually shows that 27520something is happening with a small animated display in the status 27521message line near the bottom of the screen. 27522This option sets how frequently the characters (for example, a spinning bar) 27523in the active status message lines are updated. 27524At most, it can be set to be updated 20 times per second. 27525 27526<P> 27527Setting this value to zero will prevent display of the animations 27528altogether. 27529 27530<P> 27531The option <A HREF="h_config_use_boring_spinner"><!--#echo var="FEAT_busy-cue-spinner-only"--></A> 27532can be used to remove the randomness from this animated display. 27533 27534<P> 27535<UL> 27536<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 27537</UL><P> 27538<End of help on this topic> 27539</BODY> 27540</HTML> 27541====== h_config_mailchecknoncurr ===== 27542<HTML> 27543<HEADER> 27544<TITLE>OPTION: <!--#echo var="VAR_mail-check-interval-noncurrent"--></TITLE> 27545</HEADER> 27546<BODY> 27547<H1>OPTION: <!--#echo var="VAR_mail-check-interval-noncurrent"--></H1> 27548 27549This option is closely related to the 27550<A HREF="h_config_mailcheck">"<!--#echo var="VAR_mail-check-interval"-->"</A> 27551option, as well as the 27552<A HREF="h_config_quell_checks_comp">"<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->"</A> and 27553<A HREF="h_config_quell_checks_comp_inbox">"<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->"</A> options. 27554If the "<!--#echo var="VAR_mail-check-interval"-->" option is set to zero, then automatic 27555new-mail checking is disabled and this option will have no effect. 27556<P> 27557Normally this option is set to zero, which means that the value used will be 27558the same as the value for the "<!--#echo var="VAR_mail-check-interval"-->". 27559If you set this option to a value different from zero 27560(usually larger than the value for "<!--#echo var="VAR_mail-check-interval"-->") 27561then that is the check interval that will be used 27562for folders that are not the currently open folder or the INBOX. 27563You may not even have any folders that are noncurrent and not the INBOX. 27564If you do, it is likely that they are due to 27565<A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A> 27566you have configured. 27567This option also affects the rate of mail checking done on cached 27568connections to folders you previously had open but are no longer actively 27569using. 27570You aren't expected to understand that last sentence, but if you are interested 27571take a look at 27572<A HREF="h_config_maxremstream">"<!--#echo var="VAR_max-remote-connections"-->"</A> 27573and the related options. 27574<P> 27575<UL> 27576<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 27577</UL><P> 27578<End of help on this topic> 27579</BODY> 27580</HTML> 27581====== h_config_fifopath ===== 27582<HTML> 27583<HEADER> 27584<TITLE>OPTION: NewMail FIFO Path</TITLE> 27585</HEADER> 27586<BODY> 27587<H1>OPTION: NewMail FIFO Path</H1> 27588 27589This option is only available in UNIX Alpine. 27590However, there is a very similar feature built in to PC-Alpine. 27591In PC-Alpine's Config menu at the top of the screen 27592is an option called "New Mail Window". 27593<P> 27594You may have Alpine create a FIFO special file (also called a named pipe) where 27595it will send a one-line message each time a new message is received in 27596the current folder, the INBOX, or any open 27597<A HREF="h_config_permlocked"><!--#echo var="VAR_stay-open-folders"--></A>. 27598To protect against two different Alpines both writing to the same FIFO, Alpine 27599will only create the FIFO and write to it if it doesn't already exist. 27600<P> 27601A possible way to use this option would be to have a separate window 27602on your screen running the command 27603<P> 27604<CENTER><SAMP>cat filename</SAMP></CENTER> 27605<P> 27606where "filename" is the name of the file given for this option. 27607Because the file won't exist until after you start Alpine, you must <EM>first</EM> 27608start Alpine and <EM>then</EM> run the "cat" command. 27609You may be tempted to use "tail -f filename" to view the new 27610mail log. 27611However, the common implementations of the tail command will not do what you 27612are hoping. 27613<P> 27614The width of the messages produced for the FIFO may be altered with the 27615<A HREF="h_config_newmailwidth"><!--#echo var="VAR_newmail-window-width"--></A> option. 27616<P> 27617On some systems, fifos may only be created in a local filesystem. 27618In other words, they may not be in NFS filesystems. 27619This requirement is not universal. 27620If the system you are using supports it, it should work. 27621(It is often the case that your home directory is in an NFS filesystem. 27622If that is the case, you might try using a file in the "/tmp" 27623filesystem, which is usually a local filesystem.) 27624Even when it is possible to use an NFS-mounted filesystem as a place to name 27625the fifo (for example, your home directory), it will still be the case that 27626the reader (probably the "cat" command) and the 27627writer (Alpine) of the fifo must be running on the same system. 27628<P> 27629<UL> 27630<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 27631</UL><P> 27632<End of help on this topic> 27633</BODY> 27634</HTML> 27635====== h_config_newmailwidth ===== 27636<HTML> 27637<HEADER> 27638<TITLE>OPTION: <!--#echo var="VAR_newmail-window-width"--></TITLE> 27639</HEADER> 27640<BODY> 27641<H1>OPTION: <!--#echo var="VAR_newmail-window-width"--></H1> 27642 27643For UNIX Alpine, this option is only useful if you have turned on the 27644<A HREF="h_config_fifopath">NewMail FIFO Path</A> option. 27645That option causes new mail messages to be sent to a fifo file. 27646Those messages will be 80 characters wide by default. 27647You can change the width of those messages by changing this option. 27648For example, if you are reading those messages in another window you might 27649want to set this width to the width of that other window. 27650<P> 27651If you are using PC-Alpine, it has an option in the Config menu to turn 27652on the "New Mail Window". 27653This present option also controls the width of that window. 27654<P> 27655<UL> 27656<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 27657</UL><P> 27658<End of help on this topic> 27659</BODY> 27660</HTML> 27661====== h_config_mailcheck ===== 27662<HTML> 27663<HEADER> 27664<TITLE>OPTION: <!--#echo var="VAR_mail-check-interval"--></TITLE> 27665</HEADER> 27666<BODY> 27667<H1>OPTION: <!--#echo var="VAR_mail-check-interval"--></H1> 27668 27669This option specifies, in seconds, 27670how often Alpine will check for new mail. 27671If set to zero, new-mail checking is disabled. 27672(You can always manually force a new-mail check by typing ^L (Ctrl-L), which is also the command to refresh the screen, or by typing the Next command when the 27673current message is the last message of the folder.) 27674There is a minimum value for this option, normally 15 seconds. 27675The default value is normally 150 seconds. 27676The higher you set this option, the easier it is on the server. 27677<P> 27678There are some situations where automatic new-mail checking does not work. 27679See the discussion about new-mail checking in 27680<A HREF="h_config_reopen_rule">"<!--#echo var="VAR_folder-reopen-rule"-->"</A>. 27681<P> 27682The new-mail checking will not happen exactly at the frequency that you specify. 27683For example, Alpine may elect to defer a non-INBOX mail check if you 27684are busy typing. 27685Or, it may check more frequently than you have specified if that is 27686thought to be necessary to keep the server from closing the connection 27687to the folder due to inactivity. 27688If Alpine checks for new mail as a side effect of another command, it will reset 27689the timer, so that new-mail checking may seem to happen irregularly instead of 27690every X seconds like clockwork. 27691<P> 27692If you are anxious to know about new mail as soon as possible, set the check 27693interval low, and you'll know about the new mail by approximately 27694that amount of time after it arrives. 27695If you aren't so worried about knowing right away, set this option to a 27696higher value. 27697That will save the server some processing time and may save you some of 27698the time you spend waiting for new-mail checks to happen if you are 27699dealing with a slow server or slow network connection. 27700<P> 27701If you suspect that new-mail checking is causing slow downs for you, 27702you may want to look into the options 27703<A HREF="h_config_quell_checks_comp">"<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->"</A>, 27704<A HREF="h_config_quell_checks_comp_inbox">"<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->"</A> and 27705<A HREF="h_config_mailchecknoncurr">"<!--#echo var="VAR_mail-check-interval-noncurrent"-->"</A>, 27706which refine when mail checking is done. 27707<P> 27708If the mailbox being checked uses a <A HREF="h_maildrop">Mail Drop</A> then 27709there is a minimum time 27710(<A HREF="h_config_maildropcheck">"<!--#echo var="VAR_maildrop-check-minimum"-->"</A>) 27711between new-mail checks. 27712Because of this minimum you may notice that new mail does not 27713appear promptly when you expect it. 27714The reason for this is to protect the server from over-zealous opening and 27715closing of the Mail Drop folder, since that is a costly operation. 27716<P> 27717<UL> 27718<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 27719</UL><P> 27720<End of help on this topic> 27721</BODY> 27722</HTML> 27723====== h_config_quell_checks_comp ===== 27724<HTML> 27725<HEAD> 27726<TITLE>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"--></TITLE> 27727</HEAD> 27728<BODY> 27729<H1>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"--></H1> 27730 27731This option is closely related to the 27732<A HREF="h_config_mailcheck">"<!--#echo var="VAR_mail-check-interval"-->"</A> 27733option, the 27734<A HREF="h_config_mailchecknoncurr">"<!--#echo var="VAR_mail-check-interval-noncurrent"-->"</A> option, and 27735<A HREF="h_config_quell_checks_comp_inbox">"<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->"</A>. 27736<P> 27737If this option is set, then the normal new-mail checking that happens 27738while you are composing will not happen for folders other than your 27739INBOX (which depends on the setting 27740of "<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->"). 27741<P> 27742You might want to set this option if you are experiencing delays while 27743composing that you think might be related to the speed of the new-mail 27744checks. 27745<P> 27746Even with this option turned on, an occasional new-mail check may be done 27747in order to keep the server from killing the connection to the folder. 27748For example, IMAP servers may remove a connection to a folder if there 27749has been no activity on the connection for 30 minutes or more. 27750Instead of letting that happen, Alpine will check for new mail before the 2775130 minutes is up even though you have turned on this feature to quell 27752those checks. 27753<P> 27754Besides new-mail checks, checkpoint operations on the folders 27755will also be quelled when you set this option. 27756The purpose of checkpointing is to write the changes to a folder out to 27757disk periodically in order to avoid losing those changes when system or 27758software problems occur. 27759New-mail checking and checkpointing while you are not composing are not 27760affected by this option. 27761 27762<P> 27763<End of help on this topic> 27764</BODY> 27765</HTML> 27766====== h_config_quell_checks_comp_inbox ===== 27767<HTML> 27768<HEAD> 27769<TITLE>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-inbox"--></TITLE> 27770</HEAD> 27771<BODY> 27772<H1>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-inbox"--></H1> 27773 27774This option is closely related to the 27775<A HREF="h_config_mailcheck">"<!--#echo var="VAR_mail-check-interval"-->"</A> 27776option, the 27777<A HREF="h_config_mailchecknoncurr">"<!--#echo var="VAR_mail-check-interval-noncurrent"-->"</A> option, and 27778<A HREF="h_config_quell_checks_comp">"<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->"</A>. 27779<P> 27780If this option is set, then the normal new-mail checking that happens 27781while you are composing will not happen for your INBOX. 27782Checking of other folders is controlled in a similar way with the 27783"<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->" option. 27784<P> 27785You might want to set this option if you are experiencing delays while 27786composing that you think might be related to the speed of the new-mail 27787checks. 27788<P> 27789Even with this option turned on, an occasional new-mail check may be done 27790in order to keep the server from killing the connection to the folder. 27791For example, IMAP servers may remove a connection to a folder if there 27792has been no activity on the connection for 30 minutes or more. 27793Instead of letting that happen, Alpine will check for new mail before the 2779430 minutes is up even though you have turned on this feature to quell 27795those checks. 27796<P> 27797Besides new-mail checks, checkpoint operations on the INBOX 27798will also be quelled when you set this option. 27799The purpose of checkpointing is to write the changes to a folder out to 27800disk periodically in order to avoid losing those changes when system or 27801software problems occur. 27802New-mail checking and checkpointing while you are not composing are not 27803affected by this option. 27804<P> 27805<End of help on this topic> 27806</BODY> 27807</HTML> 27808====== h_config_maildropcheck ===== 27809<HTML> 27810<HEADER> 27811<TITLE>OPTION: <!--#echo var="VAR_maildrop-check-minimum"--></TITLE> 27812</HEADER> 27813<BODY> 27814<H1>OPTION: <!--#echo var="VAR_maildrop-check-minimum"--></H1> 27815 27816New-mail checking for a 27817<A HREF="h_maildrop">Mail Drop</A> is a little different from new 27818mail checking for a regular folder. 27819One of the differences is that the connection to the Mail Drop is not 27820kept open and so the cost of checking 27821(delay for you and additional load for the server) may be significant. 27822Because of this additional cost we set a minimum time that 27823must pass between checks. 27824This minimum only applies to the automatic checking done by Alpine. 27825If you force a check by typing ^L (Ctrl-L) or by typing the Next command when you are 27826at the end of a folder index, then the check is done right away. 27827<P> 27828This option specifies, in seconds, the <EM>minimum</EM> time between Mail Drop 27829new-mail checks. 27830You may want to set this minimum high in order to avoid experiencing some 27831of the delays associated with the checks. 27832Note that the time between checks is still controlled by the regular 27833<A HREF="h_config_mailcheck"><!--#echo var="VAR_mail-check-interval"--></A> option. 27834When Alpine is about to do an automatic check for new mail (because 27835the <!--#echo var="VAR_mail-check-interval"--> has expired) then if the time since the last 27836new-mail check 27837of any open Mail Drops has been greater than the <!--#echo var="VAR_maildrop-check-minimum"-->, 27838the Mail Drop is checked for new mail as well. 27839Therefore, it is only useful to set this option to a value that is higher 27840than the <!--#echo var="VAR_mail-check-interval"-->. 27841<P> 27842If this option is set to zero, automatic Mail Drop new-mail 27843checking is disabled. 27844There is a minimum value, normally 60 seconds. 27845The default value is normally 60 seconds as well. 27846This applies to the INBOX and to the currently open folder if that is 27847different from the INBOX. 27848 27849<P> 27850<UL> 27851<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 27852</UL><P> 27853<End of help on this topic> 27854</BODY> 27855</HTML> 27856====== h_config_nntprange ===== 27857<HTML> 27858<HEADER> 27859<TITLE>OPTION: <!--#echo var="VAR_nntp-range"--></TITLE> 27860</HEADER> 27861<BODY> 27862<H1>OPTION: <!--#echo var="VAR_nntp-range"--></H1> 27863 27864This option applies only to newsgroups accessed using the NNTP protocol. 27865It does not, for example, 27866apply to newsgroups accessed using an IMAP-to-NNTP proxy. 27867 27868<P> 27869When you open a connection to a News server using the NNTP protocol, you 27870normally have access to all of the articles in each newsgroup. 27871If a server keeps a large backlog of messages it may speed performance 27872some to restrict attention to only the newer messages in a group. 27873This option allows you to set how many article numbers should be checked 27874when opening a newsgroup. 27875You can think of "<!--#echo var="VAR_nntp-range"-->" as specifying the maximum number 27876of messages you ever want to see. 27877For example, if you only ever wanted to look at the last 500 messages in each 27878newsgroup you could set this option to 500. 27879In actuality, it isn't quite that. 27880Instead, for performance reasons, it specifies the range of article 27881numbers to be checked, beginning 27882with the highest numbered article and going backwards from there. 27883If there are messages that have been canceled or deleted 27884their article numbers are still counted as part of the range. 27885<P> 27886So, more precisely, setting the "<!--#echo var="VAR_nntp-range"-->" will cause article 27887numbers 27888<P><CENTER>last_article_number - <!--#echo var="VAR_nntp-range"--> + 1 through last_article_number</CENTER> 27889<P> 27890to be considered when reading a newsgroup. 27891The number of messages that show up in your index will be less than or equal 27892to the value of "<!--#echo var="VAR_nntp-range"-->". 27893 27894<P> 27895The purpose of this option is simply to speed up access when reading news. 27896The speedup comes because Alpine can ignore all but the last <!--#echo var="VAR_nntp-range"--> article 27897numbers, and can avoid downloading any information about the ignored articles. 27898There is a cost you pay for this speedup. 27899That cost is that there is no way for you to see those ignored articles. 27900The articles that come before the range you specify are invisible to you and 27901to Alpine, as if they did not exist at all. 27902There is no way to see those messages using, for example, an unexclude command 27903or something similar. 27904The only way to see those articles is to set this option high enough (or 27905set it to zero) and then to reopen the newsgroup. 27906 27907<P> 27908If this option is set to 0 (which is also the default), 27909then the range is unlimited. 27910This option applies globally to all NNTP servers and to all newsgroups 27911on those servers. 27912There is no way to set different values for different newsgroups or servers. 27913 27914<P> 27915<UL> 27916<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 27917</UL><P> 27918<End of help on this topic> 27919</BODY> 27920</HTML> 27921====== h_config_news_active ===== 27922<html> 27923<header> 27924<title>OPTION: <!--#echo var="VAR_news-active-file-path"--></title> 27925</header> 27926<body> 27927<h1>OPTION: <!--#echo var="VAR_news-active-file-path"--></h1> 27928 27929This option tells Alpine where to look for the "active file" for newsgroups 27930when accessing news locally, rather than via NNTP. The default path is 27931usually "/usr/lib/news/active".<p> 27932<UL> 27933<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 27934</UL><P> 27935<End of help on this topic> 27936</body> 27937</html> 27938====== h_config_news_spool ===== 27939<html> 27940<header> 27941<title>OPTION: <!--#echo var="VAR_news-spool-directory"--></title> 27942</header> 27943<body> 27944<h1>OPTION: <!--#echo var="VAR_news-spool-directory"--></h1> 27945 27946This option tells Alpine where to look for the "news spool" for newsgroups 27947when accessing news locally, rather than via NNTP. The default path is 27948usually "/var/spool/news".<p> 27949<UL> 27950<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 27951</UL><P> 27952<End of help on this topic> 27953</body> 27954</html> 27955====== h_config_image_viewer ===== 27956<html> 27957<header> 27958<title>OPTION: <!--#echo var="VAR_image-viewer"--></title> 27959</header> 27960<body> 27961<h1>OPTION: <!--#echo var="VAR_image-viewer"--></h1> 27962<body> 27963This option specifies the program Alpine should call to view MIME 27964attachments of type IMAGE (e.g. GIF or TIFF). The Image Viewer setting is 27965no longer needed, but remains for backward compatibility. The more 27966general method for associating external printing and viewing programs with 27967specific MIME data types is to use the system's (or your personal) 27968"mailcap" configuration file.<p> 27969<UL> 27970<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 27971</UL><P> 27972<End of help on this topic> 27973</body> 27974</html> 27975====== h_config_domain_name ===== 27976<HTML> 27977<HEAD> 27978<TITLE>OPTION: <!--#echo var="VAR_use-only-domain-name"--></TITLE> 27979</HEAD> 27980<BODY> 27981<H1>OPTION: <!--#echo var="VAR_use-only-domain-name"--></H1> 27982 27983This option is used only if the 27984<A HREF="h_config_user_dom">"<!--#echo var="VAR_user-domain"-->"</A> option is <B>not</B> 27985set. If set to "Yes" (and <!--#echo var="VAR_user-domain"--> is not used), then Alpine 27986strips the hostname from your return ("From") address and when 27987completing unqualified addresses that you enter into the composer. 27988<P> 27989If you set this, see also the <A HREF="h_config_quell_local_lookup"> 27990"<!--#echo var="FEAT_quell-user-lookup-in-passwd-file"-->"</A> feature. 27991 27992 27993<!--chtml if pinemode="os_windows"--> 27994<P>This option is not applicable to PC-Alpine. 27995<!--chtml else--> 27996<P> 27997<!--chtml endif--> 27998<UL> 27999<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 28000</UL> 28001<P> 28002<End of help on this topic> 28003</BODY> 28004</HTML> 28005====== h_config_prune_date ===== 28006<HTML> 28007<HEAD> 28008<TITLE>OPTION: Last-Time-Prune Question</TITLE> 28009</HEAD> 28010<BODY> 28011<H1>OPTION: Last-Time-Prune Question</H1> 28012 28013This value records the last time you were asked about deleting old 28014sent-mail. 28015It is set automatically by Alpine at the beginning of each month. 28016In the past, if you wished to suppress the monthly sent-mail 28017pruning feature, you could set this to a date in the future. 28018This value is relative to the year 1900, so 28019to set this, for example, to October 2005, use 105.10. 28020<P> 28021You can still do that if you wish, or you can use the 28022<A HREF="h_config_pruning_rule"><!--#echo var="VAR_pruning-rule"--></A> option, which is probably 28023a little more convenient to use. 28024<P> 28025<UL> 28026<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 28027</UL><P> 28028<End of help on this topic> 28029</BODY> 28030</HTML> 28031====== h_config_goto_default ===== 28032<HTML> 28033<HEAD> 28034<TITLE>OPTION: <!--#echo var="VAR_goto-default-rule"--></TITLE> 28035</HEAD> 28036<BODY> 28037<H1>OPTION: <!--#echo var="VAR_goto-default-rule"--></H1> 28038 28039This value affects Alpine's behavior when you use the Goto command. 28040Alpine's usual behavior has two parts. If your current folder is 28041"Inbox", Alpine will offer the last open folder as the 28042default. If the current folder is other than "Inbox", 28043"Inbox" is offered as the default. 28044 28045<P> 28046The available options include: 28047 28048<DL> 28049 28050 <DT>folder-in-first-collection</DT> 28051 28052 <DD> Alpine will offer the most recently visited folder in the default 28053collection found in the "Collection List" screen as the default. 28054</DD> 28055 28056 <DT> inbox-or-folder-in-first-collection</DT> 28057 28058 <DD> If the current folder is "Inbox", 28059Alpine will offer the most recently visited folder in the 28060default collection found in the "Collection List" screen. 28061If the current folder is other than "Inbox", 28062"Inbox" is offered as the default. 28063</DD> 28064 28065 <DT> inbox-or-folder-in-recent-collection</DT> 28066 28067 <DD> This is Alpine's default behavior. 28068If the current folder is "Inbox", 28069Alpine will offer the last open 28070folder as the default. 28071If the current folder is other than "Inbox", 28072"Inbox" is offered as the default. 28073</DD> 28074 28075 <DT> first-collection-with-inbox-default</DT> 28076 28077 <DD> Instead of offering the most recently visited folder in the default 28078collection, the default collection is offered but with "Inbox" as 28079the default folder. 28080If you type in a folder name it will be in the default collection. 28081If you simply accept the default, however, your "Inbox" will be opened. 28082</DD> 28083 28084 <DT> most-recent-folder</DT> 28085 28086 <DD> The last accepted value simply causes the most recently opened 28087folder to be offered as the default regardless of the currently opened 28088folder. 28089</DD> 28090</DL> 28091 28092<P> 28093NOTE: The default while a newsgroup is open remains the same; the last 28094open newsgroup. 28095 28096<P> 28097<UL> 28098<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 28099</UL><P> 28100<End of help on this topic> 28101</BODY> 28102</HTML> 28103====== h_config_thread_lastreply_char ===== 28104<HTML> 28105<HEAD> 28106<TITLE>OPTION: <!--#echo var="VAR_threading-lastreply-character"--></TITLE> 28107</HEAD> 28108<BODY> 28109<H1>OPTION: <!--#echo var="VAR_threading-lastreply-character"--></H1> 28110 28111The <!--#echo var="VAR_threading-lastreply-character"--> option has a small effect on the MESSAGE 28112INDEX display when using a 28113<A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A> 28114of "show-thread-structure", "mutt-like", or 28115"show-structure-in-from"; and sorting by Threads or OrderedSubject. 28116The value of this option is a single character. 28117This character is used instead of the vertical line character when there are 28118no more replies directly to the parent of the current message. 28119It can be used to "round-off" the bottom of the vertical line 28120by setting it to a character such as a backslash (\) or 28121a backquote (`). 28122The default value of this option is the backslash character (\). 28123This option may not be set to the Empty Value. 28124In that case, the default will be used instead. 28125 28126<P> 28127<UL> 28128<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 28129</UL><P> 28130<End of help on this topic> 28131</BODY> 28132</HTML> 28133====== h_config_thread_indicator_char ===== 28134<HTML> 28135<HEAD> 28136<TITLE>OPTION: <!--#echo var="VAR_threading-indicator-character"--></TITLE> 28137</HEAD> 28138<BODY> 28139<H1>OPTION: <!--#echo var="VAR_threading-indicator-character"--></H1> 28140 28141The <!--#echo var="VAR_threading-indicator-character"--> option has a small effect on the MESSAGE 28142INDEX display when using a 28143<A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A> other 28144than "none" and sorting by Threads or OrderedSubject. 28145The value of this option is a single character. 28146This character is used to indicate that part of a thread (a conversation) is 28147hidden beneath a message. 28148The message could be expanded 28149if desired with the "/" Collapse/Expand command. 28150By default, the value of this option is the greater than sign (>). 28151<P> 28152If this option is set to the Empty Value, then the column (and the following 28153blank column) will be deleted from the display. 28154 28155<P> 28156This option is closely related to the 28157<A HREF="h_config_thread_exp_char"><!--#echo var="VAR_threading-expanded-character"--></A> option. 28158Another similar option that affects the thread display is the 28159<A HREF="h_config_thread_lastreply_char"><!--#echo var="VAR_threading-lastreply-character"--></A> option. 28160 28161<P> 28162<UL> 28163<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 28164</UL><P> 28165<End of help on this topic> 28166</BODY> 28167</HTML> 28168====== h_config_thread_exp_char ===== 28169<HTML> 28170<HEAD> 28171<TITLE>OPTION: <!--#echo var="VAR_threading-expanded-character"--></TITLE> 28172</HEAD> 28173<BODY> 28174<H1>OPTION: <!--#echo var="VAR_threading-expanded-character"--></H1> 28175 28176The <!--#echo var="VAR_threading-expanded-character"--> option has a small effect on the MESSAGE 28177INDEX display when using a 28178<A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A> other 28179than "none". 28180The value of this option is a single character. 28181This character is used to indicate that part of a thread has been expanded 28182and could be collapsed if desired with 28183the "/" Collapse/Expand command. 28184By default, the value of this option is a dot (.). 28185<P> 28186If this option is set to the Empty Value, then the column (and the following 28187blank column) will be deleted from the display. 28188 28189<P> 28190This option is closely related to the 28191<A HREF="h_config_thread_indicator_char"><!--#echo var="VAR_threading-indicator-character"--></A> option. 28192Another similar option that affects the thread display is the 28193<A HREF="h_config_thread_lastreply_char"><!--#echo var="VAR_threading-lastreply-character"--></A> option. 28194 28195<P> 28196<UL> 28197<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 28198</UL><P> 28199<End of help on this topic> 28200</BODY> 28201</HTML> 28202====== h_config_thread_index_style ===== 28203<HTML> 28204<HEAD> 28205<TITLE>OPTION: <!--#echo var="VAR_threading-index-style"--></TITLE> 28206</HEAD> 28207<BODY> 28208<H1>OPTION: <!--#echo var="VAR_threading-index-style"--></H1> 28209 28210When a folder is sorted by Threads or OrderedSubject, 28211this option will affect the INDEX displays. 28212<P> 28213 28214The possible values for this option are: 28215 28216<DL> 28217<DT>regular-index-with-expanded-threads</DT> 28218<DD>This is the default display. 28219If the configuration option 28220<A HREF="h_config_thread_disp_style">"<!--#echo var="VAR_threading-display-style"-->"</A> 28221is set to something other than "none", then this setting 28222will cause Alpine to start off with a MESSAGE INDEX with all of 28223the threads expanded. 28224That is, each message will have a line in the MESSAGE INDEX display. 28225The Collapse/Expand command (/) may be used to manually collapse or 28226expand a thread or subthread (see also <A HREF="h_config_slash_coll_entire">"<!--#echo var="FEAT_slash-collapses-entire-thread"-->"</A>). 28227<P> 28228This setting affects the display when the folder is first threaded. 28229The collapsed state may also be re-initialized by re-sorting the folder manually 28230using the SortIndex command ($). 28231After re-sorting the threads will once again all be expanded, even if you 28232have previously collapsed some of them. 28233<P> 28234If "<!--#echo var="VAR_threading-display-style"-->" is set to "none", then 28235the display will be the regular default Alpine MESSAGE INDEX, but sorted 28236in a different order. 28237</DD> 28238 28239<DT>regular-index-with-collapsed-threads</DT> 28240<DD>If the configuration option 28241<A HREF="h_config_thread_disp_style">"<!--#echo var="VAR_threading-display-style"-->"</A> 28242is set to something other than "none", then this setting 28243will cause Alpine to start out with all of the threads collapsed instead of 28244starting out with all of the threads expanded. 28245The Collapse/Expand command (/) may be used to manually collapse or 28246expand a thread or subthread (see also <A HREF="h_config_slash_coll_entire">"<!--#echo var="FEAT_slash-collapses-entire-thread"-->"</A>). 28247<P> 28248This setting affects the display when the folder is first threaded. 28249The collapsed state may also be re-initialized by re-sorting the folder manually 28250using the SortIndex command ($). 28251After re-sorting the threads will once again all be collapsed, even if you 28252have previously expanded some of them. 28253</DD> 28254 28255<DT>separate-index-screen-always</DT> 28256<DD>With this setting and the next, you will see an index of threads 28257instead of an 28258index of messages, provided you have sorted by Threads or OrderedSubject. 28259<P> 28260The THREAD INDEX contains a '*' in the first column if any message in the thread 28261is marked Important. 28262If not, it contains a '+' if any message in the thread is to you. 28263The second column is blank. The third column contains a 'D' if all of the 28264messages in the thread are deleted. 28265Otherwise, it contains an 'N' if any of the messages in the thread are New. 28266<P> 28267When you view a particular thread from the THREAD INDEX you will be 28268in the MESSAGE INDEX display 28269but the index will only contain messages from the thread you are viewing. 28270</DD> 28271 28272<DT>separate-index-screen-except-for-single-messages</DT> 28273<DD>This is very similar to the option above. 28274When you are in the THREAD INDEX, one of the available commands 28275is "ViewThd". 28276With the setting "separate-index-screen-always" (the option above) 28277when you view a particular thread you will be in the 28278MESSAGE INDEX display and the index will only contain messages from 28279the thread you are viewing. 28280If the thread you are viewing consists of a single message, the MESSAGE INDEX 28281will be an index with only one message in it. 28282If you use this "separate-index-screen-except-for-single-messages" 28283setting instead, then that index that contains a single message 28284will be skipped and you will go directly from the THREAD INDEX into the 28285MESSAGE TEXT screen. 28286</DD> 28287 28288</DL> 28289 28290<P> 28291<UL> 28292<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 28293</UL><P> 28294<End of help on this topic> 28295</BODY> 28296</HTML> 28297====== h_config_thread_disp_style ===== 28298<HTML> 28299<HEAD> 28300<TITLE>OPTION: <!--#echo var="VAR_threading-display-style"--></TITLE> 28301</HEAD> 28302<BODY> 28303<H1>OPTION: <!--#echo var="VAR_threading-display-style"--></H1> 28304 28305When a folder is sorted by Threads or OrderedSubject, 28306this option will affect the MESSAGE INDEX display. 28307By default, Alpine will display the MESSAGE INDEX in the 28308"show-thread-structure" style if a folder is sorted 28309by Threads or OrderedSubject. 28310<P> 28311 28312The possible values for this option are: 28313 28314<DL> 28315<DT>none</DT> 28316<DD>Regular index display. 28317The same index line as would be displayed without threading is used. 28318The only difference will be in the order of the messages. 28319</DD> 28320 28321<DT>show-thread-structure</DT> 28322<DD>Threaded Subjects will be indented and vertical bars and horizontal 28323lines will be added to make it easier to see the relationships among 28324the messages in a thread (a conversation). 28325</DD> 28326 28327<DT>mutt-like</DT> 28328<DD>This is the same as the option above except that the Subject 28329is suppressed (is blank) if it matches the previous Subject in the thread. 28330The name comes from the email client <A HREF="http://www.mutt.org/">Mutt</A>. 28331Here is an example of what a mutt-like index might look like. 28332In this example, the first column represents the message number, the 28333<A HREF="h_config_thread_index_style"><!--#echo var="VAR_threading-index-style"--></A> 28334is set to "regular-index-with-expanded-threads", and the 28335<A HREF="h_config_thread_lastreply_char"><!--#echo var="VAR_threading-lastreply-character"--></A> 28336is set to a backslash: 28337<PRE> 28338 1 Some topic 28339 2 . Subject original message in thread 28340 3 |-> reply to 2 28341 4 . |-> another reply to 2 28342 5 . | \-> reply to 4 28343 6 . | \-> reply to 5 28344 7 | \-> reply to 6 28345 8 |-> another reply to 2 28346 9 . |->New subject another reply to 2 but with a New subject 28347 10 | |-> reply to 9 28348 11 | \-> another reply to 9 28349 12 | \-> reply to 11 28350 13 \-> final reply to 2 28351 14 Next topic 28352</PRE> 28353</DD> 28354 28355<DT>indent-subject-1</DT> 28356<DD>Threaded Subjects will be indented one space per level of the conversation. 28357The bars and lines that show up in the show-thread-structure display will 28358not be there with this style. 28359</DD> 28360 28361<DT>indent-subject-2</DT> 28362<DD>Same as above but indent two spaces per level instead of one space. 28363</DD> 28364 28365<DT>indent-from-1</DT> 28366<DD>Similar to indent-subject-1, except that instead of indenting the 28367Subject field one space the From field of a thread will be indented one 28368space per level of the conversation. 28369</DD> 28370 28371<DT>indent-from-2</DT> 28372<DD>Same as above but indent two spaces per level instead of one space. 28373</DD> 28374 28375<DT>show-structure-in-from</DT> 28376<DD>The structure of the thread is illustrated with indenting, vertical bars, 28377and horizontal lines just like with the show-thread-structure option, but 28378the From field is used to show the relationships instead of the Subject field. 28379</DD> 28380 28381</DL> 28382 28383<P> 28384<UL> 28385<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 28386</UL><P> 28387<End of help on this topic> 28388</BODY> 28389</HTML> 28390====== h_config_pruning_rule ===== 28391<HTML> 28392<HEAD> 28393<TITLE>OPTION: <!--#echo var="VAR_pruning-rule"--></TITLE> 28394</HEAD> 28395<BODY> 28396<H1>OPTION: <!--#echo var="VAR_pruning-rule"--></H1> 28397 28398By default, Alpine will ask at the beginning of each month whether or not 28399you want to rename your sent-mail folder to a name like sent-mail-month-year. 28400(See the feature <A HREF="h_config_prune_uses_iso"><!--#echo var="FEAT_prune-uses-yyyy-mm"--></A> to 28401change the format of the folder to sent-mail-yyyy-mm.) 28402It will also ask whether you would like to delete old sent-mail folders. 28403If you have defined 28404<A HREF="h_config_read_message_folder"><!--#echo var="VAR_read-message-folder"--></A> 28405or 28406<A HREF="h_config_pruned_folders"><!--#echo var="VAR_pruned-folders"--></A> 28407Alpine will also ask about pruning those folders. 28408<P> 28409 28410With this option you may provide an automatic answer to these questions. 28411The default value is to ask you what you'd like to do. 28412<P> 28413 28414The six possible values for this option are: 28415 28416<DL> 28417<DT>ask about rename, ask about deleting</DT> 28418<DD>This is the default. 28419Alpine will ask whether you want to rename the folders and whether you 28420want to delete each of the old folders. 28421</DD> 28422 28423<DT>ask about rename, don't delete</DT> 28424<DD>Alpine will ask whether you want to rename the folders, but won't 28425ask about or delete old folders. 28426</DD> 28427 28428<DT>always rename, ask about deleting</DT> 28429<DD>This means you want to always answer yes and have Alpine automatically 28430rename the folder if possible. 28431You will also be asked about deleting old folders. 28432</DD> 28433 28434<DT>always rename, don't delete</DT> 28435<DD>This means you want to always answer yes and have Alpine automatically 28436rename the folder if possible. 28437There will be no deleting of old folders. 28438</DD> 28439 28440<DT>don't rename, ask about deleting</DT> 28441<DD>This means you want to always answer no. 28442Alpine will not rename the folder. 28443You will be asked about deleting old folders. 28444</DD> 28445 28446<DT>don't rename, don't delete</DT> 28447<DD>This means you want to always answer no. 28448Alpine will not rename the folder. 28449There will be no deleting of old folders, either. 28450</DD> 28451</DL> 28452 28453<P> 28454<UL> 28455<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 28456</UL><P> 28457<End of help on this topic> 28458</BODY> 28459</HTML> 28460====== h_config_reopen_rule ===== 28461<HTML> 28462<HEAD> 28463<TITLE>OPTION: <!--#echo var="VAR_folder-reopen-rule"--></TITLE> 28464</HEAD> 28465<BODY> 28466<H1>OPTION: <!--#echo var="VAR_folder-reopen-rule"--></H1> 28467 28468Alpine normally checks for new mail in the currently open folder 28469and in the INBOX every few <A HREF="h_config_mailcheck">minutes</A>. 28470 28471<P> 28472There are some situations where automatic new-mail checking does not work. 28473For example, if a mail folder is opened using the POP protocol or a newsgroup 28474is being read using the NNTP protocol, then new-mail checking is disabled. 28475 28476<P> 28477It may be possible to check for new mail in these cases by reopening the 28478folder. 28479Alpine does not do this for you automatically, but you may do the commands 28480manually to cause this to happen. 28481You reopen by going back to the folder list screen from the message 28482index screen with the "<" command, 28483and then going back into the message index screen with 28484the ">" command. 28485(Actually, any method you would normally use to open a folder will work the 28486same as the "<" followed by ">" method. 28487For example, the GoTo Folder command will work, or you may use L to go to the 28488Folder List screen and Carriage Return to reopen the folder.) 28489 28490<P> 28491There are some cases where Alpine knows that reopening the folder should 28492be useful as a way to discover new mail. 28493At the time of this writing, connections made using the POP protocol, 28494news reading using the NNTP protocol, local news reading, and local 28495ReadOnly folders that are in the traditional UNIX or the MMDF format all 28496fall into this category. 28497There are other cases where it <EM>may</EM> be a way to discover new mail, but Alpine 28498has no way of knowing, so it might also just be an exercise in futility. 28499All remote, ReadOnly folders other than those listed just above fall into this 28500category. 28501The setting of this option together with the type of folder 28502controls how Alpine will react to the apparent attempt to reopen a folder. 28503 28504<P> 28505If you don't reopen, then you will just be back in 28506the message index with no change. 28507You left the index and came back, but the folder remained "open" 28508the whole time. 28509However, if you do reopen the folder, the folder is closed and then reopened. 28510In this case, the current state of the open folder is lost. 28511The New status, Important and Answered flags, 28512selected state, Zoom state, collapsed or expanded state of threads, 28513current message number, 28514and any other temporary state is all lost when the reopen happens. 28515For POP folders (but not NNTP newsgroups) the Deleted flags are also lost. 28516 28517<P> 28518In the possibilities listed below, the text says "POP/NNTP" in 28519several places. 28520That really implies the case where Alpine knows it is a good way to discover 28521new mail, which is more than just POP and NNTP, but POP and NNTP are 28522the cases of most interest. 28523This option probably has more possible values than it deserves. They are: 28524 28525<DL> 28526<DT>Always reopen</DT> 28527<DD>Alpine will not ask whether you want to reopen but will just do the reopen 28528whenever you type a command that implies a reopen, regardless of the 28529access method. 28530In other words, it is assumed you would always answer Yes if asked 28531about reopening. 28532</DD> 28533 28534<DT>Yes for POP/NNTP, Ask about other remote [Yes]</DT> 28535<DD>Alpine will assume a Yes answer if the access method is POP or NNTP, but 28536will ask you whether to reopen other remote folders, 28537with a default answer of Yes. 28538</DD> 28539 28540<DT>Yes for POP/NNTP, Ask about other remote [No]</DT> 28541<DD>Alpine will assume a Yes answer if the access method is POP or NNTP, but 28542will ask you whether to reopen other remote folders, 28543with a default answer of No. 28544</DD> 28545 28546<DT>Yes for POP/NNTP, No for other remote</DT> 28547<DD>Alpine will assume a Yes answer if the access method is POP or NNTP, and 28548will assume a No answer for all other remote folders. 28549</DD> 28550 28551<DT>Always ask [Yes]</DT> 28552<DD>Alpine will not differentiate based on access method. 28553It will always ask for all remote folders, with a default answer of Yes. 28554</DD> 28555 28556<DT>Always ask [No]</DT> 28557<DD>Alpine will not differentiate based on access method. 28558It will always ask for all remote folders, with a default answer of No. 28559</DD> 28560 28561<DT>Ask about POP/NNTP [Yes], No for other remote</DT> 28562<DD>Alpine will ask if the access method is POP or NNTP, with a default answer 28563of Yes. 28564It will never attempt to reopen other remote folders. 28565</DD> 28566 28567<DT>Ask about POP/NNTP [No], No for other remote</DT> 28568<DD>This is the default. 28569Alpine will ask if the access method is POP or NNTP, with a default answer 28570of No. 28571It will never attempt to reopen other remote folders. 28572</DD> 28573 28574<DT>Never reopen</DT> 28575<DD>Alpine will never attempt to reopen already open folders. 28576</DD> 28577</DL> 28578 28579<P> 28580Remember, wherever it says POP or NNTP above it really means POP or NNTP or 28581any of the other situations where it is likely that reopening is a good way 28582to discover new mail. 28583 28584<P> 28585There is an alternative that may be of useful in some situations. 28586Instead of manually checking for new mail you can set up a 28587<A HREF="h_maildrop">Mail Drop</A> 28588and automatically check for new mail. 28589 28590<P> 28591<UL> 28592<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 28593</UL><P> 28594<End of help on this topic> 28595</BODY> 28596</HTML> 28597====== h_config_inc_startup ===== 28598<HTML> 28599<HEAD> 28600<TITLE>OPTION: <!--#echo var="VAR_incoming-startup-rule"--></TITLE> 28601</HEAD> 28602<BODY> 28603<H1>OPTION: <!--#echo var="VAR_incoming-startup-rule"--></H1> 28604 28605This value affects Alpine's behavior when opening the "INBOX" or 28606one of the "INCOMING MESSAGE FOLDERS". 28607It determines which message will be the <EM>current message</EM> when 28608the folder is first opened. 28609The default value is "first-unseen". 28610 28611<P> 28612The seven possible values for this option are: 28613 28614<DL> 28615<DT>first-unseen</DT> 28616<DD>The current message is set to the first 28617unseen message that has not been marked deleted, or the last message if 28618all of the messages have been seen previously. 28619Messages which have not been seen or which have been seen but re-marked 28620as New are considered unseen messages. 28621See the note at the bottom of this help about newsgroups. 28622</DD> 28623 28624<DT>first-recent</DT> 28625<DD>Similar to the default, but rather than starting on the first 28626unseen message Alpine starts on the first <EM>recent</EM> message. 28627A message is recent if it arrived since the last time the folder was 28628open. This value causes the current message to be set to the first 28629recent message if there is one, otherwise to the last 28630message in the folder. 28631</DD> 28632 28633<DT>first-important</DT> 28634<DD>This will result in the current message being set to the first 28635message marked Important (but not Deleted). 28636If no messages are marked Important, then it will be the last message. 28637Messages are marked Important by <EM>you</EM>, not by the sender, using 28638the 28639<A HREF="h_common_flag">Flag command</A>. 28640Or they may be marked Important by an Alpine 28641<A HREF="h_mainhelp_filtering">Filter</A> 28642that you have set up. 28643</DD> 28644 28645<DT>first-important-or-unseen</DT> 28646<DD>This selects the first of the first unseen and the first important 28647messages. 28648</DD> 28649 28650<DT>first-important-or-recent</DT> 28651<DD>This selects the first of the first recent and the first important 28652messages. 28653</DD> 28654 28655<DT>first</DT> 28656<DD>Simply starts you on the <EM>first</EM> undeleted message in the folder. 28657If all messages are deleted you start on the last message. 28658</DD> 28659 28660<DT>last</DT> 28661<DD>Simply starts you on the <EM>last</EM> undeleted message in the folder 28662If all messages are deleted you start on the last message. 28663</DD> 28664</DL> 28665 28666<P> 28667NOTE: For newsgroups in the incoming collection, "first-unseen" and 28668"first-recent" are the same and are affected by whether or not the 28669feature 28670<A HREF="h_config_news_uses_recent">"<!--#echo var="FEAT_news-approximates-new-status"-->"</A> 28671is turned on. 28672Also, there is no permanent storage in news for an Important flag. 28673This means that no messages will be marked Important when a newsgroup is 28674first opened. 28675 28676<P> 28677<UL> 28678<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 28679</UL><P> 28680<End of help on this topic> 28681</BODY> 28682</HTML> 28683====== h_config_browser ===== 28684<HTML> 28685<HEAD> 28686<TITLE>OPTION: <!--#echo var="VAR_url-viewers"--></TITLE> 28687</HEAD> 28688<BODY> 28689<H1>OPTION: <!--#echo var="VAR_url-viewers"--></H1> 28690<!--chtml if pinemode="os_windows"--> 28691PC-Alpine users do not need to enter anything here, unless:<UL> 28692<LI> they want to override, for use with Alpine, the application defined 28693in the Windows operating system for handling URLs; or 28694<LI> they are (planning on) using the same configuration file with 28695Unix Alpine. 28696</UL> 28697<P> 28698Note that if using a viewer that has a space in its path, you should 28699use the DOS name for that directory or file. Example: 28700<PRE> 28701url-viewer=C:\Progra~1\mozilla\mozilla.exe 28702</PRE> 28703<HR><P> 28704<!--chtml endif--> 28705This option affects Alpine's handling of URLs that are found in 28706messages you read. Normally, only URLs Alpine can handle directly 28707are automatically offered for selection in the "Message 28708Text" screen. When one or more applications 28709capable of deciphering URLs on their command line are added here, Alpine 28710will choose the first available to display URLs it cannot handle directly. 28711A viewer's availability is based on its being specified with a <B>full 28712directory path</B> and the evaluation of any optionally supplied 28713parameters described below. 28714 28715<P> 28716Additionally, to support various connection methods and applications, each 28717entry in this list can optionally begin with one or more of 28718the following special tokens. The allowed tokens include: 28719 28720<P> 28721<DL> 28722<DT>_TEST(<VAR>test-string</VAR>)_</DT> 28723<DD> 28724The <VAR>test-string</VAR> is a shell command that Alpine will run to 28725evaluate a viewer's availability. The command specified by the test 28726string is run and if its resulting exit status is non-zero, Alpine will 28727not consider the associated viewer for use. 28728</DD> 28729 28730<DT>_SCHEME(<VAR>scheme-list</VAR>)_</DT> 28731<DD> 28732The <VAR>scheme-list</VAR> is a list of one or more (comma-delimited) 28733URL schemes that are to be used with the associated viewer. This is 28734the way to configure Alpine to recognize URLs other than the built-in set. 28735<P> 28736It can also be used to override Alpine's built-in handlers. 28737For example, you could specify "news" in the <VAR>scheme-list</VAR>, 28738and Alpine would use (provided it passed all other criteria) the associated 28739viewer when it encountered a URL of the form "news:comp.mail.pine". 28740 28741</DD> 28742</DL> 28743 28744<P> 28745By default, Alpine will simply append a space character followed by the 28746selected URL prior to launching the command in your specified SHELL. You can 28747optionally specify where in the command the selected URL should appear 28748by using the "_URL_" token. All occurrences found in the command 28749will be replaced with the selected URL before the command is handed 28750to the shell. If such replacement occurs, the default appending of the 28751selected URL does not take place. 28752 28753<P> 28754NOTE: If the viewer you specify has any command-line arguments, 28755including the "_URL_" token, you will need to add a 28756double-quote character before the command path and after the last 28757argument (see the "lynx" example below). 28758 28759<P> 28760So, here are some example entries: 28761<PRE> 28762url-viewers = _TEST("test -n '${DISPLAY}'")_ /usr/local/bin/netscape 28763 "/usr/local/bin/lynx _URL_" 28764 C:\BIN\NETSCAPE.BAT 28765</PRE> 28766<P> 28767This example shows that for the first viewer in the list to be used 28768the environment variable "DISPLAY" must be defined. If it 28769is, then the path and file "/usr/local/bin/netscape" must exist. 28770If neither condition is met, 28771then the path and file "/usr/local/bin/lynx" must exist. 28772If it does, then the "_URL_" token is replaced by the selected URL. 28773If the path to "lynx" is invalid, 28774then the final path and file C:\BIN\NETSCAPE.BAT must exist. 28775Note that the last 28776entry is a DOS/Windows path. This is one way to support Alpine running 28777on more than one architecture with the same configuration file.<P> 28778<P> 28779<!--chtml if pinemode="os_windows"--> 28780<!--chtml else--> 28781Note that depending on the type of browser used and the method of 28782its invocation (such as whether it will open in a separate window) from 28783the MESSAGE TEXT screen, the browser may "supplant" 28784the MESSAGE TEXT screen, and you will have to quit the browser to return to 28785it (for example, when using Lynx; to exit Lynx, use the "Q" command). 28786In other words, launching the browser from Alpine may make Alpine 28787"disappear" (although it is still "running") 28788until you close the browser again.<P> 28789<UL><LI><A HREF="h_config_browser_xterm">Defining <!--#echo var="VAR_url-viewers"--> in an X windows 28790environment: for advanced users and systems administrators</A> 28791</UL> 28792<!--chtml endif--> 28793<P>If you are unsure what browsers are available on your system or how to 28794specify them in Alpine's <!--#echo var="VAR_url-viewers"--> option for best usability, contact your 28795local computing support staff. 28796<P><UL> 28797<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 28798</UL> 28799<P> 28800<End of help on this topic> 28801</BODY> 28802</HTML> 28803====== h_config_history ===== 28804<HTML> 28805<HEAD> 28806<TITLE>OPTION: <!--#echo var="VAR_default-directories"--></TITLE> 28807</HEAD> 28808<BODY> 28809<H1>OPTION: <!--#echo var="VAR_default-directories"--></H1> 28810<P> 28811This option allows you to input a list of directories that Alpine will offer 28812for you to use when you are saving or exporting attachments. This is useful 28813when navigating to specific directories becomes too tedious, or when you 28814need to do this on a daily basis, and want Alpine to remember this on a 28815permanent basis. 28816<P> 28817The list of directories saved here can be accessed using the ^Y and ^V commands 28818in the save prompt for attachments, or the export command. 28819 28820<P><UL> 28821<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 28822</UL> 28823<P> 28824<End of help on this topic> 28825</BODY> 28826</HTML> 28827====== h_config_browser_xterm ===== 28828<HTML> 28829<HEAD> 28830<TITLE><!--#echo var="VAR_url-viewers"--> and X windows applications</TITLE> 28831</HEAD> 28832<BODY> 28833<H1>Defining <!--#echo var="VAR_url-viewers"--> in an X windows 28834environment: for advanced users and systems administrators</H1> 28835If you are using Alpine with an X-terminal (emulator) and want to define an 28836X windows-based application in <!--#echo var="VAR_url-viewers"-->, 28837you may want to do so in a manner that causes any <B>already</B> 28838invoked viewer application to be used for viewing URLs you select from Alpine 28839messages, and a <B>new</B> URL-viewer process to be 28840started <B>only</B> if the same application has <B>not already</B> 28841been launched -- for one reason, to avoid file-locking contentions among 28842multiple invocations of the same URL-viewer application. 28843(The example entries set in the help screen for the "<!--#echo var="VAR_url-viewers"-->" 28844option does not do this.) A method of doing that would be:<OL> 28845<LI> use 28846the _TEST(<VAR>test-string</VAR>)_ token in the <B>first</B> entry to 28847check (using commands appropriate for your Unix shell 28848in place of <VAR>test-string</VAR>) for the presence of a 28849lockfile created by the URL-viewer application -- which implies that the 28850application is already running, though this is not foolproof. 28851Following that in the same <!--#echo var="VAR_url-viewers"--> entry, specify the 28852application with its appropriate command line option(s) to 28853show the URL selected from the Alpine message in an already open window of 28854that application, or perhaps in a new window of that application. 28855 28856<LI> In the 28857<B>second</B> entry for the <!--#echo var="VAR_url-viewers"--> option, specify the same 28858application without those command line options, but this time using the 28859_TEST(...)_ token to check whether the environment variable "DISPLAY" 28860is defined. 28861<LI> If you will be using Alpine (with the same .pinerc file) outside of the X 28862windows environment (for instance, using VT-100 terminal emulation), you 28863may wish to specify a non-X windows URL-viewer application such as Lynx 28864as the last entry. 28865</OL><BR> 28866How exactly you define your <!--#echo var="VAR_url-viewers"--> entries to do this will depend on 28867the command shell, the URL-viewer application(s), and possibly the specific 28868version of the latter, you are using. 28869<P> 28870Relevant command 28871line options for the Netscape browser for showing URLs (selected from Alpine) 28872when Netscape is already running are discussed in the document 28873"Remote Control of UNIX Netscape" 28874found at the URL (as of 12 Aug. 1998): 28875<P> 28876 28877<CENTER><A HREF="http://home.netscape.com/newsref/std/x-remote.html">http://home.netscape.com/newsref/std/x-remote.html</A></CENTER> 28878 28879<P>(If the URL-viewer application is 28880<B>not</B> running on the same host as Alpine, but being launched from an 28881applications server, you may not be able to use the command line options for 28882using an existing invocation of the application in Alpine's <!--#echo var="VAR_url-viewers"--> entry.) 28883<P> 28884<!--chtml if this-method="shown-to-work"--> 28885An example using the Korn shell and the Netscape browser (first entry wrapped 28886because of its length, but should all appear on one line): 28887<P> 28888url-viewers = _TEST("test -L /myhomedir/.netscape/lock")_ "/usr/local/bin/netscape -remote 'openURL(_URL_, new-window)' &"<BR> 28889 28890_TEST("test -n '${DISPLAY}'")_ "/usr/local/bin/netscape &"<BR> 28891 "/usr/local/bin/lynx '_URL_'" 28892<P> 28893<!--chtml endif--> 28894<P> 28895<UL> 28896<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 28897</UL><P> 28898<End of help on this topic> 28899</BODY> 28900</HTML> 28901====== h_config_enable_full_hdr ===== 28902<HTML> 28903<HEAD> 28904<TITLE>FEATURE: <!--#echo var="FEAT_enable-full-header-cmd"--></TITLE> 28905</HEAD> 28906<BODY> 28907<H1>FEATURE: <!--#echo var="FEAT_enable-full-header-cmd"--></H1> 28908 28909This feature enables the "H Full Headers" command which toggles between 28910the display of all headers in the message and the normal edited view of 28911headers. The Full Header command also controls which headers are included 28912for Export, Pipe, Print, Forward, and Reply functions. (For Reply, the 28913Full Header mode will respect the 28914<A HREF="h_config_include_header">"Include-Headers-in-Reply"</A> 28915feature setting.) 28916<P> 28917If Full Header mode is turned on and you Forward a message, you will 28918be asked if you'd like to forward the message as an attachment, as opposed 28919to including the text of the message in the body of your new message. 28920<P> 28921If you have also turned on the 28922<A HREF="h_config_quote_suppression">"Quote Suppression"</A> 28923option then the Full Headers command actually rotates through three states 28924instead of just two. 28925The first is the normal view with long quotes suppressed. 28926The second is the normal view but with the long quotes included. 28927The last enables the display of all headers in the message. 28928When using Export, Pipe, Print, Forward, or Reply the quotes are 28929never suppressed, so the first two states are identical. 28930<P> 28931Normally, the Header Mode will reset 28932to the default behavior when moving to a new message. 28933The mode can be made to persist from message to message by setting the feature 28934<A HREF="h_config_quell_full_hdr_reset"><!--#echo var="FEAT_quell-full-header-auto-reset"--></A>. 28935<P> 28936<UL> 28937<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 28938</UL><P> 28939<End of help on this topic> 28940</BODY> 28941</HTML> 28942====== h_config_enable_full_hdr_and_text ===== 28943<HTML> 28944<HEAD> 28945<TITLE>FEATURE: <!--#echo var="FEAT_enable-full-header-and-text"--></TITLE> 28946</HEAD> 28947<BODY> 28948<H1>FEATURE: <!--#echo var="FEAT_enable-full-header-and-text"--></H1> 28949 28950This feature affects how the "H Full Headers" command displays 28951message text. If set, the raw message text will be displayed. This 28952especially affects MIME formatted email, where the entire MIME format 28953will be displayed. This feature similarly affects how messages are 28954included for the Export, Pipe, Print, Forward, and Reply functions. 28955<P> 28956When viewing a raw message that has attachments with this feature set, 28957you will not be able to view attachments without first leaving full 28958headers mode. This is because MIME parsing is not done on the raw message. 28959<P> 28960<UL> 28961<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 28962</UL><P> 28963<End of help on this topic> 28964</BODY> 28965</HTML> 28966====== h_config_enable_pipe ===== 28967<HTML> 28968<HEAD> 28969<TITLE>FEATURE: <!--#echo var="FEAT_enable-unix-pipe-cmd"--></TITLE> 28970</HEAD> 28971<BODY> 28972<H1>FEATURE: <!--#echo var="FEAT_enable-unix-pipe-cmd"--></H1> 28973 28974This feature enables the "| Pipe" command that sends the current message 28975to the specified command for external processing. 28976<P> 28977 28978A short description of how the pipe command works is given 28979<A HREF="h_pipe_command">here</A>. 28980 28981<P> 28982<UL> 28983<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 28984</UL><P> 28985<End of help on this topic> 28986</BODY> 28987</HTML> 28988====== h_config_quell_full_hdr_reset ===== 28989<HTML> 28990<HEAD> 28991<TITLE>FEATURE: <!--#echo var="FEAT_quell-full-header-auto-reset"--></TITLE> 28992</HEAD> 28993<BODY> 28994<H1>FEATURE: <!--#echo var="FEAT_quell-full-header-auto-reset"--></H1> 28995 28996The <A HREF="h_common_hdrmode">HdrMode Command</A> 28997normally resets to the default state when switching to a new message. 28998For example, if you've used the "H" command to turn on Full 28999Headers for a message you are viewing, and then you type the Next command 29000to look at the next message, the full headers will no longer be shown. 29001Setting this feature disables that reset. 29002Instead, the Header Mode remains the same from message to message. 29003 29004<P> 29005The presence or absence of the HdrMode command is determined by the 29006<A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A> 29007Feature-List option. 29008<P> 29009<UL> 29010<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 29011</UL><P> 29012<End of help on this topic> 29013</BODY> 29014</HTML> 29015====== h_config_enable_tab_complete ===== 29016<HTML> 29017<HEAD> 29018<TITLE>FEATURE: <!--#echo var="FEAT_enable-tab-completion"--></TITLE> 29019</HEAD> 29020<BODY> 29021<H1>FEATURE: <!--#echo var="FEAT_enable-tab-completion"--></H1> 29022 29023This feature enables the TAB key when at a prompt for a filename. In this 29024case, TAB will cause the partial name already entered to be automatically 29025completed, provided the partial name is unambiguous. 29026This feature is on by default. 29027<P> 29028Similarly, this feature also enables TAB completion of address book 29029nicknames when at a prompt for a nickname, 29030or when typing in an address field in the composer. 29031<P> 29032<End of help on this topic> 29033</BODY> 29034</HTML> 29035====== h_config_quit_wo_confirm ===== 29036<HTML> 29037<HEAD> 29038<TITLE>FEATURE: <!--#echo var="FEAT_quit-without-confirm"--></TITLE> 29039</HEAD> 29040<BODY> 29041<H1>FEATURE: <!--#echo var="FEAT_quit-without-confirm"--></H1> 29042 29043This feature controls whether or not Alpine will ask for confirmation when a 29044Quit command is received. 29045<P> 29046<End of help on this topic> 29047</BODY> 29048</HTML> 29049====== h_config_quote_replace_noflow ===== 29050<HTML> 29051<HEAD> 29052<TITLE>FEATURE: <!--#echo var="FEAT_quote-replace-nonflowed"--></TITLE> 29053</HEAD> 29054<BODY> 29055<H1>FEATURE: <!--#echo var="FEAT_quote-replace-nonflowed"--></H1> 29056 29057This feature, which is only active when 29058<A HREF="h_config_quote_replace_string"><!--#echo var="VAR_quote-replace-string"--></A> is 29059also set, 29060enables quote-replacement on non-flowed messages. It is off 29061by default because a non-flowed message is more dependent on its format, 29062and thus quote-replacement may cause less-than-pleasing results. 29063Setting this feature will cause quote-replacement similar to that of flowed 29064messages, but with the added possibility of long lines being wrapped 29065into new lines if the Quote-Replacement-String is longer than the string 29066it is replacing, which is "> ". 29067<P> 29068<End of help on this topic> 29069</BODY> 29070</HTML> 29071====== h_config_enable_jump ===== 29072<HTML> 29073<HEAD> 29074<TITLE>FEATURE: <!--#echo var="FEAT_enable-jump-shortcut"--></TITLE> 29075</HEAD> 29076<BODY> 29077<H1>FEATURE: <!--#echo var="FEAT_enable-jump-shortcut"--></H1> 29078 29079When this feature is set you may enter a number (followed by RETURN) 29080and jump to that message number, when in the MESSAGE INDEX or MESSAGE TEXT 29081screens. In other words, it obviates the need for typing the "J" for the 29082Jump command. 29083<P> 29084<End of help on this topic> 29085</BODY> 29086</HTML> 29087====== h_config_enable_alt_ed ===== 29088<HTML> 29089<HEAD> 29090<TITLE>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-cmd"--></TITLE> 29091</HEAD> 29092<BODY> 29093<H1>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-cmd"--></H1> 29094 29095If this feature is set (the default), and the 29096<A HREF="h_config_editor">"<!--#echo var="VAR_editor"-->"</A> option 29097<B>is not</B> set, entering 29098the ^_ (Ctrl-underscore) key while composing a message will prompt you 29099for the name of the editor you would like to use. 29100<P> 29101If the environment variable $EDITOR is set, its value will be offered as 29102a default. 29103<P> 29104If the <A HREF="h_config_editor">"<!--#echo var="VAR_editor"-->"</A> option 29105<B>is</B> set, the ^_ key will activate the specified 29106editor without prompting, in which case it is not necessary to 29107set the "<!--#echo var="FEAT_enable-alternate-editor-cmd"-->" feature. 29108<P> 29109<UL> 29110<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 29111</UL><P> 29112<End of help on this topic> 29113</BODY> 29114</HTML> 29115====== h_config_alt_ed_now ===== 29116<HTML> 29117<HEAD> 29118<TITLE>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-implicitly"--></TITLE> 29119</HEAD> 29120<BODY> 29121<H1>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-implicitly"--></H1> 29122 29123If this feature and the <A HREF="h_config_editor">"<!--#echo var="VAR_editor"-->"</A> 29124variable are both set, Alpine will 29125automatically activate the specified editor when the cursor is moved from 29126the header of the message being composed into the message text. For 29127replies, the alternate editor will be activated immediately. If this 29128feature is set but the "<!--#echo var="VAR_editor"-->" variable is not set, then Alpine will 29129automatically ask for the name of an alternate editor when the cursor 29130is moved out of the header being composed, or if a reply is being done. 29131 29132<P><UL> 29133<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 29134</UL> 29135<P> 29136<End of help on this topic> 29137</BODY> 29138</HTML> 29139====== h_config_enable_bounce ===== 29140<HTML> 29141<HEAD> 29142<TITLE>FEATURE: <!--#echo var="FEAT_enable-bounce-cmd"--></TITLE> 29143</HEAD> 29144<H1>FEATURE: <!--#echo var="FEAT_enable-bounce-cmd"--></H1> 29145<BODY> 29146 29147Setting this feature enables the "B Bounce" command, which will prompt 29148for an address and *remail* the message to the new recipient. This command 29149is used to re-direct messages that you have received in error, or need to 29150be redirected for some other reason (e.g. list moderation). The final 29151recipient will see a header indicating that you have Resent the msg, but 29152the message's From: header will show the original author of the message, 29153and replies to it will go back to that author, and not to you. 29154<P> 29155<End of help on this topic> 29156</BODY> 29157</HTML> 29158====== h_config_enable_agg_ops ===== 29159<HTML> 29160<HEAD> 29161<TITLE>FEATURE: <!--#echo var="FEAT_enable-aggregate-command-set"--></TITLE> 29162</HEAD> 29163<BODY> 29164<H1>FEATURE: <!--#echo var="FEAT_enable-aggregate-command-set"--></H1> 29165 29166When this feature is set you may use the commands and subcommands that relate to 29167performing operations on more than one message at a time. We call these 29168"aggregate operations". In particular, the 29169<!--chtml if pinemode="function_key"-->"F5 29170<!--chtml else-->"; 29171<!--chtml endif--> Select", 29172 29173<!--chtml if pinemode="function_key"--> 29174"F6 29175<!--chtml else--> 29176"A 29177<!--chtml endif--> 29178Apply", and 29179<!--chtml if pinemode="function_key"--> 29180"F4 29181<!--chtml else--> 29182"Z 29183<!--chtml endif--> 29184Zoom" commands are enabled by this feature. Select is used to 29185"tag" one or more messages meeting the specified criteria. Apply can 29186then be used to apply any message command to all of the selected/tagged 29187messages. Further, the Zoom command allows you to toggle the MESSAGE INDEX 29188view between just those Selected and all messages in the folder. 29189<P> 29190This feature also enables the 29191<!--chtml if pinemode="function_key"--> 29192"F7" 29193<!--chtml else--> 29194"^X" 29195<!--chtml endif--> 29196 29197subcommand in the MESSAGE INDEX 29198WhereIs command that causes all messages matching the WhereIs argument to 29199become selected; and the Select, Select Current, and ZoomMode commands in the 29200<A HREF="h_folder_maint">FOLDER LIST screen</A>. 29201<P> 29202Some related help topics are 29203<UL> 29204<LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A> 29205<LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>, 29206<LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>, 29207<LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>. 29208<LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and 29209<LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>. 29210</UL> 29211<P> 29212<UL> 29213<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 29214</UL><P> 29215<End of help on this topic> 29216</BODY> 29217</HTML> 29218 29219====== h_config_enable_flag ===== 29220<HTML> 29221<HEAD> 29222<TITLE>FEATURE: <!--#echo var="FEAT_enable-flag-cmd"--></TITLE> 29223</HEAD> 29224<BODY> 29225<H1>FEATURE: <!--#echo var="FEAT_enable-flag-cmd"--></H1> 29226 29227Setting this feature enables the 29228<A HREF="h_common_flag">"* Flag"</A> 29229command that allows you to 29230manipulate the status flags associated with a message. By default, Flag 29231will set the "Important" flag, which results in an asterisk being 29232displayed in column one of the MESSAGE INDEX for such messages. 29233<P> 29234<End of help on this topic> 29235</BODY> 29236</HTML> 29237====== h_config_flag_screen_default ===== 29238<HTML> 29239<HEAD> 29240<TITLE>FEATURE: <!--#echo var="FEAT_enable-flag-screen-implicitly"--></TITLE> 29241</HEAD> 29242<BODY> 29243<H1>FEATURE: <!--#echo var="FEAT_enable-flag-screen-implicitly"--></H1> 29244 29245The feature modifies the behavior of the 29246<a href="h_common_flag">Flag</a> 29247command (provided it too is 29248<A HREF="h_config_enable_flag">enabled</A>). 29249By default, when the "* Flag" command is selected, 29250Alpine offers a prompt to set one of several flags and also offers the 29251option of entering the detailed flag manipulation screen via the "^T" 29252key. Enabling this feature causes Alpine to immediately enter the detailed 29253flag screen rather than first offer the simple prompt. 29254The 29255<A HREF="h_config_flag_screen_kw_shortcut"><!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"--></A> option offers a slightly different way of setting keywords. 29256<P> 29257<End of help on this topic> 29258</BODY> 29259</HTML> 29260====== h_config_flag_screen_kw_shortcut ===== 29261<HTML> 29262<HEAD> 29263<TITLE>FEATURE: <!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"--></TITLE> 29264</HEAD> 29265<BODY> 29266<H1>FEATURE: <!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"--></H1> 29267 29268This feature modifies the behavior of the 29269<a href="h_common_flag">Flag</a> command 29270and the <A HREF="h_index_cmd_select">Select</A> command. 29271This feature is set by default. 29272When this feature is not set, when the "* Flag" command is selected, 29273Alpine offers a prompt to set one of several flags and also offers the 29274option of entering the detailed flag manipulation screen via the "^T" 29275key. 29276If you have 29277<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> 29278defined, then enabling this feature adds a shortcut way to set or unset 29279keywords. 29280You use "*" followed by the first letter of a keyword (or the nickname of 29281a keyword if you've given it a nickname) and that will set the keyword. 29282<P> 29283An example is easier to understand than the explanation. 29284The flag command can always be used to set the system flags. 29285For example, to set the Answered flag you would type 29286<P> 29287<CENTER><SAMP>* A</SAMP></CENTER> 29288<P> 29289Now suppose you have defined a keyword "Work" using the <!--#echo var="VAR_keywords"--> 29290option in the Config screen. 29291By default, to set a keyword like "Work" you would usually 29292have to go to the Flag Details screen using 29293the "^T To Flag Details" command. 29294Instead, if you have enabled this feature, you may type 29295<P> 29296<CENTER><SAMP>* W</SAMP></CENTER> 29297<P> 29298to set the Work flag, or 29299<P> 29300<CENTER><SAMP>* ! W</SAMP></CENTER> 29301<P> 29302to unset it. 29303Just like for the other flag setting commands, the case of the letter does 29304not matter, so "w" or "W" both set the "Work" 29305keyword. 29306<P> 29307Notice that you can only use this trick for one keyword that begins 29308with "W". 29309If you happen to have a "Work" keyword and another keyword that is 29310"WIFI" the "* W" command will set the first one in 29311your list of keywords. 29312Also, there are five letters that are reserved for system 29313flags and the NOT command. 29314If you type "* A" it will always set the Answered flag, not 29315your "Aardvark" keyword. 29316In order to set the "Aardvark" keyword you'll still have to use 29317the Flag Details screen. 29318<P> 29319Because enabling the 29320<A HREF="h_config_flag_screen_default"><!--#echo var="FEAT_enable-flag-screen-implicitly"--></A> 29321option causes Alpine to skip directly to the Flag Details screen when the 29322Flag command is used, 29323setting it will cause this feature to have no effect at all. 29324<P> 29325Similarly, when Selecting by Keyword, setting this option will allow you 29326to use Keyword initials instead of full keywords. 29327<P> 29328<End of help on this topic> 29329</BODY> 29330</HTML> 29331====== h_config_can_suspend ===== 29332<HTML> 29333<HEAD> 29334<TITLE>FEATURE: <!--#echo var="FEAT_enable-suspend"--></TITLE> 29335</HEAD> 29336<BODY> 29337<H1>FEATURE: <!--#echo var="FEAT_enable-suspend"--></H1> 29338 29339Setting this feature will allow you to type ^Z (Control Z) to 29340<!--chtml if pinemode="os_windows"--> 29341minimize Alpine into its icon, bringing into focus whatever 29342application is running behind the PC-Alpine window. 29343<!--chtml else--> 29344temporarily suspend Alpine. 29345 29346<P> 29347This does not exit Alpine, but puts it in the background to watch 29348for new mail and such. Normally, you type a command, such 29349as "fg" at your system prompt to return to your Alpine session. 29350 29351<P> 29352The <A HREF="h_config_suspend_spawns"><!--#echo var="FEAT_use-subshell-for-suspend"--></A> feature 29353adjusts whether Alpine is placed into the background of the shell its 29354running in or starts a news shell. 29355<!--chtml endif--> 29356 29357<P> 29358<UL> 29359<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 29360</UL><P> 29361<End of help on this topic> 29362</BODY> 29363</HTML> 29364====== h_config_take_lastfirst ====== 29365<HTML> 29366<HEAD> 29367<TITLE>FEATURE: <!--#echo var="FEAT_disable-take-last-comma-first"--></TITLE> 29368</HEAD> 29369<BODY> 29370<H1>FEATURE: <!--#echo var="FEAT_disable-take-last-comma-first"--></H1> 29371 29372Normally, when TakeAddr is used to copy an address from a message into 29373an address book entry, Alpine will attempt to rewrite the full name of the 29374address in the form 29375<P> 29376 29377 Last, First<P> 29378 29379instead of<P> 29380 29381 First Last 29382 29383<P> 29384It does this because many people find it useful to sort by Last name 29385instead of First name. If this feature is set, then the TakeAddr command 29386will not attempt to reverse the name in this manner. 29387<P> 29388<End of help on this topic> 29389</BODY></HTML> 29390====== h_config_disable_regex ====== 29391<HTML> 29392<HEAD> 29393<TITLE>FEATURE: <!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></TITLE> 29394</HEAD> 29395<BODY> 29396<H1>FEATURE: <!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></H1> 29397 29398Normally, the 29399<a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a> 29400option is interpreted as a regular expression. 29401One type of address that might cause trouble is an address that 29402contains a plus sign. 29403If you want to have an address with a plus as one of your 29404<!--#echo var="VAR_alt-addresses"--> 29405and you don't want to use regular expressions, then setting this 29406feature will cause Alpine to treat the addresses you list literally instead. 29407<P> 29408<End of help on this topic> 29409</BODY></HTML> 29410====== h_config_take_fullname ====== 29411<HTML> 29412<HEAD> 29413<TITLE>FEATURE: <!--#echo var="FEAT_disable-take-fullname-in-addresses"--></TITLE> 29414</HEAD> 29415<BODY> 29416<H1>FEATURE: <!--#echo var="FEAT_disable-take-fullname-in-addresses"--></H1> 29417 29418Normally, when TakeAddr is used to copy an address or addresses 29419from a message into an address book entry, Alpine will try to preserve 29420the full name associated with each address in the list of addresses. 29421The reason for this is so that if the entry is a list or later becomes a 29422list, then information about the individual addresses in the list 29423is preserved. 29424If you would rather just have the simple addresses in the list of addresses, 29425set this feature. For example, with the default setting you might 29426see something like this in the ADDRESS BOOK editor after you type TakeAddr 29427<P> 29428<PRE> 29429 Nickname : nick 29430 Fullname : Bedrock Elders 29431 Fcc : 29432 Comment : 29433 Addresses : Fred Flintstone <flint@bedrock.org>, 29434 Barney Rubble <rubble@bedrock.org> 29435</PRE> 29436<P> 29437but with this feature set it would look like 29438<P> 29439<PRE> 29440 Nickname : nick 29441 Fullname : Bedrock Elders 29442 Fcc : 29443 Comment : 29444 Addresses : flint@bedrock.org, 29445 rubble@bedrock.org 29446</PRE> 29447<P> 29448instead. Note the difference in the Addresses field. 29449<P> 29450<End of help on this topic> 29451</BODY></HTML> 29452====== h_config_print_from ====== 29453<HTML> 29454<HEAD> 29455<TITLE>FEATURE: <!--#echo var="FEAT_print-includes-from-line"--></TITLE> 29456</HEAD> 29457<BODY> 29458<H1>FEATURE: <!--#echo var="FEAT_print-includes-from-line"--></H1> 29459 29460If this feature is set, then the Berkeley-mail style From line is included 29461at the start of each message that is printed. This line looks something 29462like the following, with the address replaced by the address from the 29463From line of the message being printed: 29464<P> 29465 From user@domain.somewhere.com Mon May 13 2946614:11:06 1998 29467<P> 29468<End of help on this topic> 29469</BODY> 29470</HTML> 29471====== h_config_expanded_distlists ====== 29472<HTML> 29473<HEAD> 29474<TITLE>FEATURE: <!--#echo var="FEAT_expanded-view-of-distribution-lists"--></TITLE> 29475</HEAD> 29476<BODY> 29477<H1>FEATURE: <!--#echo var="FEAT_expanded-view-of-distribution-lists"--></H1> 29478If this feature is set, then distribution lists in the address book 29479screen will always be expanded automatically. 29480<P> 29481<End of help on this topic> 29482</BODY> 29483</HTML> 29484====== h_config_compose_news_wo_conf ====== 29485<HTML> 29486<HEAD> 29487<TITLE>FEATURE: <!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></TITLE> 29488</HEAD> 29489<BODY> 29490<H1>FEATURE: <!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></H1> 29491This feature controls one aspect of Alpine's Composer. If you enter the 29492composer while reading a newsgroup, you will normally be prompted to 29493determine whether you intend the new message to be posted to the current 29494newsgroup or not. If this feature is set, Alpine will not prompt you 29495in this situation, and will assume that you do indeed wish to post 29496to the newsgroup you are reading. 29497<P> 29498<End of help on this topic> 29499</BODY> 29500</HTML> 29501====== h_config_compose_rejects_unqual ====== 29502<HTML> 29503<HEAD> 29504<TITLE>FEATURE: <!--#echo var="FEAT_compose-rejects-unqualified-addrs"--></TITLE> 29505</HEAD> 29506<BODY> 29507<H1>FEATURE: <!--#echo var="FEAT_compose-rejects-unqualified-addrs"--></H1> 29508 29509This feature controls one aspect of the message composer; in particular, 29510what happens when an unqualified name is entered into an address header. 29511If set, unqualified names entered as addresses will be treated as errors 29512unless they match an addressbook nickname. Alpine will not attempt to turn 29513them into complete addresses by adding your local domain.<P> 29514 29515A complete (fully qualified) address is one containing a username followed 29516by an "@" ("at") symbol, followed by a domain name (e.g. 29517"jsmith@example.com"). An unqualified name is one <B>without</B> 29518the "@" symbol and domain name (e.g. "jsmith"). 29519 29520(See also <A HREF="h_address_format">Explanation of Address formats</A>.) 29521 29522<P> 29523 29524When you enter a fully qualified address, Alpine does not interpret or 29525modify it, but simply passes it on to the mail-transport-agent (MTA) for 29526your system. Alpine conforms to the Internet standards governing message 29527headers and will not send an unqualifed name to the MTA. Therefore, when 29528you enter an unqualified name, Alpine will normally attempt to turn it into 29529a fully qualified address, first by checking to see if you have entered a 29530matching nickname in your addressbook, or failing that, by simply adding 29531your own domain to the name entered. So if your address is 29532"jsmith@example.com" and you enter "fred", then (assuming 29533"fred" is not a nickname in your addressbook), Alpine will turn 29534that into "fred@example.com".<P> 29535 29536There are situations where it is not desirable for Alpine to interpret such 29537unqualified names as valid (local) addresses. For example, if "fred" 29538turned out to be a typo (intended to be an addressbook nickname), but 29539there actually was a "fred" in your local domain, the message might 29540be mis-delivered without your realizing it. In order to reduce the likelihood 29541of such accidents, setting this feature will cause Alpine to treat such 29542addresses as errors, and require that you explicitly enter the full local 29543address (e.g. "fred@example.com") or correct the name so that it 29544matches an address book nickname.<P> 29545 29546Consider this a safety feature against mis-directed mail. 29547<P> 29548<UL> 29549<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 29550</UL><P> 29551<End of help on this topic> 29552</BODY> 29553</HTML> 29554====== h_config_quell_local_lookup ====== 29555<HTML> 29556<HEAD> 29557<TITLE>FEATURE: <!--#echo var="FEAT_quell-user-lookup-in-passwd-file"--></TITLE> 29558</HEAD> 29559<BODY> 29560<H1>FEATURE: <!--#echo var="FEAT_quell-user-lookup-in-passwd-file"--></H1> 29561 29562This feature controls an aspect of Alpine's Composer, and if needed, will 29563usually be set by your system manager in Alpine's system-wide configuration 29564file. Specifically, if this feature is set, Alpine will not attempt to look 29565in the system password file to find a Full Name for the entered address. 29566<P> 29567Normally, names you enter into address fields (e.g. To: or Cc:) are 29568checked against your address book(s) to see if they match an address book 29569nickname. Failing that, (in Unix Alpine) the name is then checked against 29570the Unix password file. If the entered name matches a username in the 29571system password file, Alpine extracts the corresponding Full Name information 29572for that individual, and adds that to the address being entered. 29573<P> 29574However, password file matching can have surprising (incorrect) results if 29575other users of the system do not receive mail at the domain you are using. 29576That is, if either the 29577<A HREF="h_config_user_dom">"<!--#echo var="VAR_user-domain"-->"</A> or 29578<A HREF="h_config_domain_name">"<!--#echo var="VAR_use-only-domain-name"-->"</A> 29579option 29580is set such that the administrative domain of other users on the system 29581isn't accurately reflected, Alpine should be told that a passwd file match 29582is coincidental, and Full Name info will be incorrect. For example, a 29583personal name from the password file could get falsely paired with the 29584entered name as it is turned into an address in the configured domain. 29585<P> 29586If you are seeing this behavior, enabling this feature will prevent Unix 29587Alpine from looking up names in the password file to find the Full Name 29588for incomplete addresses you enter.<P> 29589<UL> 29590<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 29591</UL> 29592<P> 29593<End of help on this topic> 29594</BODY> 29595</HTML> 29596====== h_config_tab_checks_recent ====== 29597<HTML> 29598<HEAD> 29599<TITLE>FEATURE: <!--#echo var="FEAT_tab-checks-recent"--></TITLE> 29600</HEAD> 29601<BODY> 29602<H1>FEATURE: <!--#echo var="FEAT_tab-checks-recent"--></H1> 29603 29604In a FOLDER LIST screen, the TAB key usually just changes which 29605folder is highlighted. 29606If this feature is set, then the TAB key will cause the number of 29607recent messages and the total number of messages in the highlighted folder 29608to be displayed instead. 29609 29610<P> 29611<End of help on this topic> 29612</BODY> 29613</HTML> 29614====== h_config_maildrops_preserve_state ====== 29615<HTML> 29616<HEAD> 29617<TITLE>FEATURE: <!--#echo var="FEAT_maildrops-preserve-state"--></TITLE> 29618</HEAD> 29619<BODY> 29620<H1>FEATURE: <!--#echo var="FEAT_maildrops-preserve-state"--></H1> 29621 29622This feature affects the way <A HREF="h_maildrop">Mail Drops</A> work. 29623Normally, when mail is moved from a Mail Drop folder to a destination 29624folder, it is delivered as new mail. 29625Any Seen/New, Answered, Important/Flagged state that has changed will be 29626ignored. 29627All of the mail will be considered unSeen, unAnswered, and unImportant after 29628it is moved. 29629<P> 29630If this feature is set, then the state changes that have been made 29631to the messages in the Mail Drop folder will be preserved. 29632<P> 29633In any case, messages that are already marked Deleted when the 29634mail is to be moved from the Mail Drop will be ignored. 29635<P> 29636<End of help on this topic> 29637</BODY> 29638</HTML> 29639====== h_config_preopen_stayopens ====== 29640<HTML> 29641<HEAD> 29642<TITLE>FEATURE: <!--#echo var="FEAT_preopen-stayopen-folders"--></TITLE> 29643</HEAD> 29644<BODY> 29645<H1>FEATURE: <!--#echo var="FEAT_preopen-stayopen-folders"--></H1> 29646 29647This feature is related to the option 29648<A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A>. 29649Normally, Stay Open folders are only opened on demand, when the user 29650asks to open them. 29651From then on they are kept open for the duration of the session. 29652However, if this feature is set, then the Stay Open folders will all be 29653opened at startup, at the same time that the INBOX is opened. 29654 29655<P> 29656<End of help on this topic> 29657</BODY> 29658</HTML> 29659====== h_config_expunge_inbox ====== 29660<HTML> 29661<HEAD> 29662<TITLE>FEATURE: <!--#echo var="FEAT_offer-expunge-of-inbox"--></TITLE> 29663</HEAD> 29664<BODY> 29665<H1>FEATURE: <!--#echo var="FEAT_offer-expunge-of-inbox"--></H1> 29666 29667The INBOX is normally treated differently from regular folders in several 29668ways. 29669One of the differences is that the normal "close" sequence of 29670events is deferred until Alpine is exited, instead of happening when you 29671leave the INBOX to view another folder. 29672The "close" sequence normally includes the Expunging 29673of deleted messages 29674(either automatically or after a prompt, controlled by the features 29675<A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>, 29676<A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A>, and 29677<A HREF="h_config_expunge_manually"><!--#echo var="FEAT_expunge-only-manually"--></A>), and the 29678handling of the 29679<A HREF="h_config_read_message_folder"><!--#echo var="VAR_read-message-folder"--></A>. 29680 29681<P> 29682If this feature is set the "close" sequence handling will take 29683place every time you leave the INBOX. 29684The INBOX will still be kept open, but the offer to Expunge and the archiving 29685to the <!--#echo var="VAR_read-message-folder"--> 29686will take place each time you leave the INBOX instead of only once at the 29687end of the session. 29688 29689<P> 29690<End of help on this topic> 29691</BODY> 29692</HTML> 29693====== h_config_expunge_stayopens ====== 29694<HTML> 29695<HEAD> 29696<TITLE>FEATURE: <!--#echo var="FEAT_offer-expunge-of-stayopen-folders"--></TITLE> 29697</HEAD> 29698<BODY> 29699<H1>FEATURE: <!--#echo var="FEAT_offer-expunge-of-stayopen-folders"--></H1> 29700 29701This feature is related to the option 29702<A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A>. 29703Stay Open folders are treated differently from regular folders in several 29704ways. 29705One of the differences is that the normal "close" sequence of 29706events is deferred until Alpine is exited, instead of happening when you 29707leave the folder to view another folder. 29708The "close" sequence normally includes the Expunging 29709of deleted messages 29710(either automatically or after a prompt, controlled by the features 29711<A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>, 29712<A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A>, and 29713<A HREF="h_config_expunge_manually"><!--#echo var="FEAT_expunge-only-manually"--></A>), and the 29714handling of 29715<A HREF="h_config_archived_folders"><!--#echo var="VAR_incoming-archive-folders"--></A>. 29716 29717<P> 29718If this feature is set the "close" sequence handling will take 29719place when you leave the Stay Open folder. 29720The folder will still be kept open, but the offer to Expunge and the archiving 29721will take place each time you leave the folder instead of only once at the 29722end of the session. 29723This feature does not affect the INBOX, which will still only be processed 29724when you exit Alpine. 29725However, there is a similar feature that affects only the INBOX called 29726<A HREF="h_config_expunge_inbox">"<!--#echo var="FEAT_offer-expunge-of-inbox"-->"</A>. 29727 29728<P> 29729<End of help on this topic> 29730</BODY> 29731</HTML> 29732====== h_config_preserve_start_stop ====== 29733<HTML> 29734<HEAD> 29735<TITLE>FEATURE: <!--#echo var="FEAT_preserve-start-stop-characters"--></TITLE> 29736</HEAD> 29737<BODY> 29738<H1>FEATURE: <!--#echo var="FEAT_preserve-start-stop-characters"--></H1> 29739 29740This feature controls how special control key characters, typically 29741Ctrl-S and Ctrl-Q, are interpreted when input to Alpine. These characters 29742are known as the "stop" and "start" characters and are sometimes used in 29743communications paths to control data flow between devices that operate at 29744different speeds. 29745 29746<P> 29747 29748By default, Alpine turns the system's handling of these special characters 29749off except during printing. However, if you see Alpine reporting input errors 29750such as: 29751<P> 29752 [ Command "^Q" not defined for this screen.] 29753<P> 29754and, at the same time, see your display become garbled, then it is likely 29755that setting this option will solve the problem. Be aware, though, that 29756enabling this feature will also cause Alpine to ostensibly "hang" 29757whenever the Ctrl-S key combination is entered as the system is now 29758interpreting such input as a "stop output" command. To "start 29759output" again, simply type Ctrl-Q. 29760<P> 29761<End of help on this topic> 29762</BODY> 29763</HTML> 29764====== h_config_enable_incoming ====== 29765<HTML> 29766<HEAD> 29767<TITLE>FEATURE: <!--#echo var="FEAT_enable-incoming-folders"--></TITLE> 29768</HEAD> 29769<BODY> 29770<H1>FEATURE: <!--#echo var="FEAT_enable-incoming-folders"--></H1> 29771 29772Alpine's Incoming Message Folders collection 29773provides a convenient way to access multiple incoming folders. 29774It is also useful if you have accounts on multiple computers. 29775<P> 29776 29777If set, this feature defines a pseudo-folder collection called 29778"INCOMING MESSAGE FOLDERS". Initially, the only folder included 29779in this collection will be your INBOX, which will no longer show up in 29780your Default folder collection. 29781<P> 29782 29783You may add more folders to the Incoming Message Folders collection by 29784using the 29785<!--chtml if pinemode="function_key"--> 29786"F10 29787<!--chtml else--> 29788"A 29789<!--chtml endif--> 29790Add" command in the FOLDER LIST screen. You will be prompted for 29791the host the folder is stored on (which defaults to the same host used 29792for your INBOX), a nickname, and the actual folder name. Once a set 29793of Incoming Message Folders are defined, the TAB key (in MESSAGE INDEX 29794or MESSAGE TEXT screens) may be used to scan the folders for those 29795with Recent messages. If you add more folders to 29796your <!--#echo var="VAR_incoming-folders"--> collection, turning this feature back off will have 29797no effect. 29798<P> 29799NOTE: Normally the software that actually delivers mail (the stuff that happens 29800before Alpine is involved) is in a better position to do delivery filtering 29801than is Alpine itself. 29802If possible, you may want to look at programs such as 29803"filter" or "procmail", which are examples of delivery 29804filtering programs. 29805If you'd prefer to have Alpine do the filtering for you, you may set that 29806up. 29807Look <A HREF="h_rules_filter">here</A> for help with Alpine filtering. 29808<P> 29809<UL> 29810<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 29811</UL><P> 29812<End of help on this topic> 29813</BODY> 29814</HTML> 29815====== h_config_enable_incoming_checking ====== 29816<HTML> 29817<HEAD> 29818<TITLE>FEATURE: <!--#echo var="FEAT_enable-incoming-folders-checking"--></TITLE> 29819</HEAD> 29820<BODY> 29821<H1>FEATURE: <!--#echo var="FEAT_enable-incoming-folders-checking"--></H1> 29822 29823This feature is only operational if you have enabled the optional 29824<A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A> collection. 29825If you do have Incoming Message Folders and you also set this feature, 29826then the number of Unseen messages in each folder will be displayed 29827in the FOLDER LIST screen for the Incoming Message Folders. 29828The number of Unseen messages in a folder will be displayed in parentheses 29829to the right of the name of each folder. 29830If there are no Unseen messages in a folder then only the name 29831is displayed, not a set of parentheses with zero inside them. 29832A redraw command, Ctrl-L, can be used in the FOLDER LIST screen for 29833the Incoming Message Folders to cause an immediate update. 29834<P> 29835If a check for Unseen messages fails for a particular folder then Alpine 29836will no longer attempt to check that folder for the duration of the 29837session and this will be indicated by a question mark inside the 29838parentheses. 29839<P> 29840The features 29841<A HREF="h_config_incoming_checking_total"><!--#echo var="FEAT_incoming-checking-includes-total"--></A>, 29842<A HREF="h_config_incoming_checking_recent"><!--#echo var="FEAT_incoming-checking-uses-recent"--></A>, 29843<A HREF="h_config_incoming_list"><!--#echo var="VAR_incoming-check-list"--></A>, 29844<A HREF="h_config_incoming_interv"><!--#echo var="VAR_incoming-check-interval"--></A>, 29845<A HREF="h_config_incoming_second_interv"><!--#echo var="VAR_incoming-check-interval-secondary"--></A>, and 29846<A HREF="h_config_incoming_timeo"><!--#echo var="VAR_incoming-check-timeout"--></A> 29847all affect how this feature behaves. 29848<P> 29849<UL> 29850<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 29851</UL><P> 29852<End of help on this topic> 29853</BODY> 29854</HTML> 29855====== h_config_incoming_checking_total ====== 29856<HTML> 29857<HEAD> 29858<TITLE>FEATURE: <!--#echo var="FEAT_incoming-checking-includes-total"--></TITLE> 29859</HEAD> 29860<BODY> 29861<H1>FEATURE: <!--#echo var="FEAT_incoming-checking-includes-total"--></H1> 29862 29863This option has no effect unless the feature 29864<A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A> 29865is set, which in turn has no effect unless 29866<A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A> 29867is set. 29868<P> 29869When incoming folder checking is turned on the default is to display 29870the number of unseen messages in each folder. 29871More precisely, it is the number of undeleted unseen messages. 29872Using this option you may also display the total number of messages 29873in each folder. 29874Instead of a single number representing the number of unseen messages 29875you will get two numbers separated by a slash character. 29876The first is the number of unseen messages and the second is the 29877total number of messages. 29878<P> 29879You may also use the recent message count instead of the unseen message 29880count by turning on the feature 29881<A HREF="h_config_incoming_checking_recent"><!--#echo var="FEAT_incoming-checking-uses-recent"--></A>. 29882<P> 29883<UL> 29884<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 29885</UL><P> 29886<End of help on this topic> 29887</BODY> 29888</HTML> 29889====== h_config_incoming_checking_recent ====== 29890<HTML> 29891<HEAD> 29892<TITLE>FEATURE: <!--#echo var="FEAT_incoming-checking-uses-recent"--></TITLE> 29893</HEAD> 29894<BODY> 29895<H1>FEATURE: <!--#echo var="FEAT_incoming-checking-uses-recent"--></H1> 29896 29897This option has no effect unless the feature 29898<A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A> 29899is set, which in turn has no effect unless 29900<A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A> 29901is set. 29902<P> 29903When incoming folder checking is turned on the default is to display 29904the number of unseen messages in each folder. 29905More precisely, it is the number of undeleted unseen messages. 29906Using this option you may display the number of recent messages instead 29907of the number of unseen messages. 29908A message is only counted as recent if this is the first session to 29909see it, so the recent count might be less than the unseen count. 29910The difference between the two would be accounted for by the unseen messages 29911in the folder which were there previously but have not been looked at yet. 29912<P> 29913If you simultaneously run more than one email client at a time 29914(for example, you run more than one Alpine in parallel) then turning 29915this feature on can cause some confusion. 29916The confusion stems from the fact that each message is only considered to be 29917recent in one session. 29918That means that the counts of new messages may be different in the two 29919Alpines running side by side, because each incoming message will only be 29920counted as recent in one of the two sessions. 29921<P> 29922You may also display the total number of messages 29923in each folder by using the 29924<A HREF="h_config_incoming_checking_total"><!--#echo var="FEAT_incoming-checking-includes-total"--></A> 29925option. 29926<P> 29927<UL> 29928<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 29929</UL><P> 29930<End of help on this topic> 29931</BODY> 29932</HTML> 29933====== h_config_attach_in_reply ====== 29934<HTML> 29935<HEAD> 29936<TITLE>FEATURE: <!--#echo var="FEAT_include-attachments-in-reply"--></TITLE> 29937</HEAD> 29938<BODY> 29939<H1>FEATURE: <!--#echo var="FEAT_include-attachments-in-reply"--></H1> 29940 29941This feature controls an aspect of Alpine's Reply command. If set, any MIME 29942attachments that were part of the original message will automatically be 29943included in the Reply. 29944<P> 29945<End of help on this topic> 29946</BODY> 29947</HTML> 29948====== h_config_include_header ===== 29949<HTML> 29950<HEAD> 29951<TITLE>FEATURE: <!--#echo var="FEAT_include-header-in-reply"--></TITLE> 29952</HEAD> 29953<BODY> 29954<H1>FEATURE: <!--#echo var="FEAT_include-header-in-reply"--></H1> 29955 29956This feature controls an aspect of Alpine's Reply command. If set, and the 29957original message is being included in the reply, then headers from that 29958message will also be part of the reply. 29959<P> 29960<End of help on this topic> 29961</HEAD> 29962</HTML> 29963====== h_config_sig_at_bottom ===== 29964<HTML> 29965<HEAD> 29966<TITLE>FEATURE: <!--#echo var="FEAT_signature-at-bottom"--></TITLE> 29967</HEAD> 29968<BODY> 29969<H1>FEATURE: <!--#echo var="FEAT_signature-at-bottom"--></H1> 29970 29971This feature controls an aspect of Alpine's Reply command. If this feature 29972is set, and the original message is being included in the reply, then the 29973contents of your signature file (if any) will be inserted after the included 29974message. 29975<P> 29976This feature does not affect the results of a Forward command. 29977<P> 29978<End of help on this topic> 29979</BODY> 29980</HTML> 29981====== h_config_sigdashes ===== 29982<HTML> 29983<HEAD> 29984<TITLE>FEATURE: <!--#echo var="FEAT_enable-sigdashes"--></TITLE> 29985</HEAD> 29986<BODY> 29987<H1>FEATURE: <!--#echo var="FEAT_enable-sigdashes"--></H1> 29988 29989This feature enables support for the common USENET news convention 29990of preceding a message signature with the special line consisting of 29991the three characters "-- " (i.e., dash, dash, and space). 29992 29993<P> 29994When enabled and a 29995"<A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A>" exists, 29996Alpine will insert the special line before including the file's text (unless 29997the special line already exists somewhere in the file's text). 29998 29999<P> 30000In addition, when you Reply or Followup to a message containing one of 30001these special lines and choose to include its text, Alpine will observe 30002the convention of not including text beyond the special line in your 30003reply. 30004If <A HREF="h_config_enable_full_hdr">"Full Header"</A> 30005mode is enabled and turned on, then Alpine <EM>will</EM> 30006include the text beyond the special line regardless of the setting of 30007this feature. 30008 30009<P> 30010See also "<a href="h_config_strip_sigdashes"><!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></a>" 30011for a related feature. 30012 30013<P> 30014<UL> 30015<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 30016</UL><P> 30017<End of help on this topic> 30018</BODY> 30019</HTML> 30020====== h_config_new_thread_blank_subject ===== 30021<HTML> 30022<HEAD> 30023<TITLE>FEATURE: <!--#echo var="FEAT_new-thread-on-blank-subject"--></TITLE> 30024</HEAD> 30025<BODY> 30026<H1>FEATURE: <!--#echo var="FEAT_new-thread-on-blank-subject"--></H1> 30027 30028When this feature is enabled (the default) Alpine will create a new thread 30029every time that the subject line becomes empty at any time during composition. 30030 30031<P> 30032This behavior is particularly useful in case you are replying to a message. 30033Replying to a message causes the message to be in the same thread than the 30034original message that is being replied to. However, many authors want to create 30035a new message (in a different thread) while replying to a message, and they do 30036this by changing the full subject, by first deleting the original subject and 30037typing the new subject of the current message. 30038 30039<P> 30040Enabling this feature causes that any time that the subject is deleted, the 30041message being composed will be considered the first message of a new thread. 30042 30043<P> 30044<UL> 30045<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 30046</UL><P> 30047<End of help on this topic> 30048</BODY> 30049</HTML> 30050====== h_config_strip_sigdashes ===== 30051<HTML> 30052<HEAD> 30053<TITLE>FEATURE: <!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></TITLE> 30054</HEAD> 30055<BODY> 30056<H1>FEATURE: <!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></H1> 30057 30058This feature doesn't do anything if the feature 30059"<A HREF="h_config_sigdashes"><!--#echo var="FEAT_enable-sigdashes"--></A>" is turned on. 30060However, if the "<!--#echo var="FEAT_enable-sigdashes"-->" feature is not turned on, 30061then turning on this feature enables support for the convention 30062of not including text beyond the sigdashes line when Replying or Following 30063up to a message and including the text of that message. 30064If <A HREF="h_config_enable_full_hdr">"Full Header"</A> 30065mode is enabled and turned on, then Alpine <EM>will</EM> 30066include the text beyond the special line regardless of the setting of 30067this feature. 30068<P> 30069In other words, this is a way to turn on the signature stripping behavior 30070without also turning on the dashes-adding behavior. 30071<P> 30072<UL> 30073<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 30074</UL><P> 30075<End of help on this topic> 30076</BODY> 30077</HTML> 30078====== h_config_forward_as_attachment ===== 30079<HTML> 30080<HEAD> 30081<TITLE>FEATURE: <!--#echo var="FEAT_forward-as-attachment"--></TITLE> 30082</HEAD> 30083<BODY> 30084<H1>FEATURE: <!--#echo var="FEAT_forward-as-attachment"--></H1> 30085 30086This feature affects the way forwarded message text is handled. When set, rather than 30087include the text of the forwarded message below any additional text you provide in the 30088composer, the forwarded message is attached in its entirety to the message you send. 30089<P> 30090This is useful in that it keeps the text you provide in the composer distinct from the 30091text of the forwarded message. Similarly, it allows the recipient to 30092conveniently operate on the forwarded message. For example, they might reply directly to 30093the sender of the forwarded message, or process it as part of a spam report. 30094<UL> 30095<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 30096</UL><P> 30097<End of help on this topic> 30098</BODY> 30099</HTML> 30100====== h_config_preserve_field ===== 30101<HTML> 30102<HEAD> 30103<TITLE>FEATURE: <!--#echo var="FEAT_preserve-original-fields"--></TITLE> 30104</HEAD> 30105<BODY> 30106<H1>FEATURE: <!--#echo var="FEAT_preserve-original-fields"--></H1> 30107 30108This feature affects Alpine's behavior when one replies to a message. 30109When you receive a message, some or all of the recipients of the message 30110have been added to the To: and Cc: fields. If you reply to such message, 30111and this feature is disabled, then the original sender of the message is 30112added to the To: field, and all other recipients are added to the Cc: 30113field, while your address is added to the From: field. 30114 30115<P> 30116However, if this feature is enabled, then Alpine will preserve the 30117original fields as sent in the original message, so the Cc: and To: 30118fields will be preserved. The sender's address will be added to the To: 30119field, while your address is added to the From: field. 30120 30121<P> 30122The behavior of this feature is that replies to all messages will behave 30123in the way described above. If you only intend this to happen on a per 30124message basis, then keep this feature disabled, and when replying to a 30125message you will see a new option in the menu for the "Reply to all 30126recipients?" question. In this case, pressing "p" will 30127make Alpine toggle its question so you can preserve the To: and Cc: 30128fields for that message only. 30129 30130<UL> 30131<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 30132</UL><P> 30133<End of help on this topic> 30134</BODY> 30135</HTML> 30136====== h_config_sub_lists ===== 30137<HTML> 30138<HEAD> 30139<TITLE>FEATURE: <!--#echo var="FEAT_enable-partial-match-lists"--></TITLE> 30140</HEAD> 30141<BODY> 30142<H1>FEATURE: <!--#echo var="FEAT_enable-partial-match-lists"--></H1> 30143 30144This feature affects the subcommands available when Saving, 30145or when Opening a new folder. If set, the subcommand ^X ListMatches will be 30146available. This command allows you to type in a substring of the folder 30147you are looking for and when you type ^X it will display all folders 30148that contain that substring in their names. 30149This feature is set by default. 30150 30151<P> 30152<End of help on this topic> 30153</BODY> 30154</HTML> 30155====== h_config_scramble_message_id ===== 30156<HTML> 30157<HEAD> 30158<TITLE>FEATURE: <!--#echo var="FEAT_scramble-message-id"--></TITLE> 30159</HEAD> 30160<BODY> 30161<H1>FEATURE: <!--#echo var="FEAT_scramble-message-id"--></H1> 30162 30163If this feature is set, the message-id header value 30164will be transformed with a simple Rot13 transformation. 30165The result will still have the correct syntax for a Message-ID but the 30166part of the MessageID that is often a domain name will not be an actual 30167domain name because the letters will be scrambled. 30168<P> 30169It is possible (but unlikely?) that some spam detection 30170software will use that as a reason to reject the mail as spam. 30171It has also been reported that some spam detection software uses the 30172fact that there are no dots after the "@" as a reason to reject 30173messages. 30174If your PC-Alpine Message-ID is using a name without a dot that is because 30175that is what Windows thinks is your "Full computer name". 30176The method used to set this varies from one type of Windows to another but 30177check under Settings -> Control Panel -> System and 30178look for Network Identification or Computer Name or something similar. 30179How to set it is beyond the scope of Alpine. 30180 30181<P> 30182<End of help on this topic> 30183</BODY> 30184</HTML> 30185====== h_downgrade_multipart_to_text ===== 30186<HTML> 30187<HEAD> 30188<TITLE>FEATURE: <!--#echo var="FEAT_downgrade-multipart-to-text"--></TITLE> 30189</HEAD> 30190<BODY> 30191<H1>FEATURE: <!--#echo var="FEAT_downgrade-multipart-to-text"--></H1> 30192 30193<P> 30194This feature affects Alpine's behavior when sending mail. Internet 30195standards require Alpine to translate all non-ASCII characters in 30196messages that it sends using MIME encoding. This encoding can be 30197ostensibly broken for recipients if any agent between Alpine and the 30198recipient, such as an email list expander, appends text to the 30199message, such as list information or advertising. When sending such 30200messages Alpine attempts to protect such encoding by placing extra 30201MIME boundaries around the message text. 30202<P> 30203These extra boundaries are invisible to recipients that 30204use MIME-aware email programs (the vast majority). However, if 30205you correspond with users of email programs that are not MIME-aware, 30206or do not handle the extra boundaries gracefully, you can 30207use this feature to prevent Alpine from including the extra 30208MIME information. Of course, it will increase the likelihood 30209that non-ASCII text you send may appear corrupt to the recipient. 30210<P> 30211<End of help on this topic> 30212</BODY> 30213</HTML> 30214====== h_config_show_sort ===== 30215<HTML> 30216<HEAD> 30217<TITLE>FEATURE: <!--#echo var="FEAT_show-sort"--></TITLE> 30218</HEAD> 30219<BODY> 30220<H1>FEATURE: <!--#echo var="FEAT_show-sort"--></H1> 30221 30222If this feature is set and there is sufficient space on the screen, 30223a short indication of the current sort order will be 30224added in the titlebar (the top line on the screen), before the name 30225of the folder. 30226For example, with the default Arrival sort in effect, 30227the display would have the characters 30228 30229<P><CENTER>[A]</CENTER><P> 30230 30231added between the title of the screen and the folder name. 30232The letters are the same as the letters you may type to manually 30233sort a folder with the SortIndex command ($). 30234The letters in the table below are the ones that may show 30235up in the titlebar line. 30236<P> 30237<TABLE> 30238<TR> <TD> A </TD> <TD> <EM>A</EM>rrival </TD> </TR> 30239<TR> <TD> S </TD> <TD> <EM>S</EM>ubject </TD> </TR> 30240<TR> <TD> F </TD> <TD> <EM>F</EM>rom </TD> </TR> 30241<TR> <TD> T </TD> <TD> <EM>T</EM>o </TD> </TR> 30242<TR> <TD> C </TD> <TD> <EM>C</EM>c </TD> </TR> 30243<TR> <TD> D </TD> <TD> <EM>D</EM>ate </TD> </TR> 30244<TR> <TD> Z </TD> <TD> si<EM>Z</EM>e </TD> </TR> 30245<TR> <TD> O </TD> <TD> <EM>O</EM>rderedsubject </TD> </TR> 30246<TR> <TD> E </TD> <TD> scor<EM>E</EM> </TD> </TR> 30247<TR> <TD> H </TD> <TD> t<EM>H</EM>read </TD> </TR> 30248</TABLE> 30249<P> 30250If the sort order is Reversed, the letter above will be preceded by the letter 30251"R", for example 30252 30253<P><CENTER>[RS]</CENTER><P> 30254 30255means that a Reverse Subject sort is in effect. 30256For the case where the sort is in Reverse Arrival order, the "A" is 30257left out, and just an "R" is shown. 30258 30259<P><CENTER>[R]</CENTER> 30260 30261<P> 30262<End of help on this topic> 30263</BODY> 30264</HTML> 30265====== h_config_disable_reset_disp ===== 30266<HTML> 30267<HEAD> 30268<TITLE>FEATURE: <!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></TITLE> 30269</HEAD> 30270<BODY> 30271<H1>FEATURE: <!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></H1> 30272 30273UNIX Alpine only. 30274<P> 30275This feature affects Alpine's behavior when using 30276<A HREF="h_config_display_filters"><!--#echo var="VAR_display-filters"--></A>. 30277Normally, before the display filter is run, the terminal mode is reset 30278to what it was before you started Alpine. 30279This may be necessary if the filter requires the use of the terminal. 30280For example, it may need to interact with you. 30281If you set this feature, then the terminal mode will not be reset. 30282One thing that turning on this feature should fix is the coloring of 30283<A HREF="h_config_quote_color">quoted text</A> in the message view, which 30284breaks because the terminal reset resets the color state of the terminal. 30285 30286<P> 30287<End of help on this topic> 30288</BODY> 30289</HTML> 30290====== h_config_disable_sender ===== 30291<HTML> 30292<HEAD> 30293<TITLE>FEATURE: <!--#echo var="FEAT_disable-sender"--></TITLE> 30294</HEAD> 30295<BODY> 30296<H1>FEATURE: <!--#echo var="FEAT_disable-sender"--></H1> 30297 30298This feature affects Alpine's generation of the "Sender:" or 30299<A HREF="h_config_use_sender_not_x">"X-X-Sender"</A> 30300header fields. 30301Prior to version 2.24, Alpine generated such a header in situations where the 30302username or domain were not the same as 30303the "From:" header on the message. 30304With this feature set, 30305no "Sender:" or "X-X-Sender" header will be generated. 30306This may be desirable on a system that is virtually hosting many domains, 30307and the sysadmin has other methods available for tracking a message to 30308its originator. 30309<P> 30310See also <A HREF="h_config_allow_chg_from">"<!--#echo var="FEAT_allow-changing-from"-->"</A>. 30311 30312<P> 30313<End of help on this topic> 30314</BODY> 30315</HTML> 30316====== h_config_use_sender_not_x ===== 30317<HTML> 30318<HEAD> 30319<TITLE>FEATURE: <!--#echo var="FEAT_use-sender-not-x-sender"--></TITLE> 30320</HEAD> 30321<BODY> 30322<H1>FEATURE: <!--#echo var="FEAT_use-sender-not-x-sender"--></H1> 30323 30324Normally Alpine adds a header line 30325labeled "X-X-Sender", if the sender is 30326different from the From: line. 30327The standard specifies that this header 30328line should be labeled "Sender", not "X-X-Sender". 30329Setting this feature causes 30330"Sender" to be used instead of "X-X-Sender". 30331<P> 30332See also <A HREF="h_config_disable_sender">"<!--#echo var="FEAT_disable-sender"-->"</A>. 30333 30334<P> 30335<End of help on this topic> 30336</BODY> 30337</HTML> 30338====== h_config_use_fk ===== 30339<HTML> 30340<HEAD> 30341<TITLE>FEATURE: <!--#echo var="FEAT_use-function-keys"--></TITLE> 30342</HEAD> 30343<BODY> 30344<H1>FEATURE: <!--#echo var="FEAT_use-function-keys"--></H1> 30345 30346This feature specifies that Alpine will respond to function keys instead of 30347the normal single-letter commands. In this mode, the key menus at the 30348bottom of each screen will show function key designations instead of the 30349normal mnemonic key. 30350 30351<P> 30352<End of help on this topic> 30353</BODY> 30354</HTML> 30355====== h_config_cancel_confirm ===== 30356<HTML> 30357<HEAD> 30358<TITLE>FEATURE: <!--#echo var="FEAT_compose-cancel-confirm-uses-yes"--></TITLE> 30359</HEAD> 30360<BODY> 30361<H1>FEATURE: <!--#echo var="FEAT_compose-cancel-confirm-uses-yes"--></H1> 30362 30363This feature affects what happens when you type ^C to cancel a composition. 30364By default, if you attempt to cancel a composition by typing ^C, you will be 30365asked to confirm the cancellation by typing a "C" 30366for <EM>C</EM>onfirm. 30367It logically ought to be a "Y" for <EM>Y</EM>es, but that is 30368risky because the "^C Y" needed to cancel a message 30369is close (on the keyboard) to the "^X Y" needed to send a message. 30370<P> 30371If this feature is set the confirmation asked for 30372will be a "<EM>Y</EM>es" 30373instead of a "<EM>C</EM>onfirm" response. 30374 30375<P> 30376<End of help on this topic> 30377</BODY> 30378</HTML> 30379====== h_config_compose_maps_del ===== 30380<HTML> 30381<HEAD> 30382<TITLE>FEATURE: <!--#echo var="FEAT_compose-maps-delete-key-to-ctrl-d"--></TITLE> 30383</HEAD> 30384<BODY> 30385<H1>FEATURE: <!--#echo var="FEAT_compose-maps-delete-key-to-ctrl-d"--></H1> 30386 30387This feature affects the behavior of the DELETE key. 30388If set, Delete will be equivalent to ^D, and delete 30389the current character. Normally Alpine defines the Delete key 30390to be equivalent to ^H, which deletes the <EM>previous</EM> 30391character. 30392 30393<P> 30394<End of help on this topic> 30395</BODY> 30396</HTML> 30397====== h_config_compose_bg_post ===== 30398<HTML> 30399<HEAD> 30400<TITLE>FEATURE: <!--#echo var="FEAT_enable-background-sending"--></TITLE> 30401</HEAD> 30402<BODY> 30403<H1>FEATURE: <!--#echo var="FEAT_enable-background-sending"--></H1> 30404 30405This feature affects the behavior of Alpine's mail sending. If set, this 30406feature enables a subcommand in the composer's "Send?" confirmation 30407prompt. The subcommand allows you to tell Alpine to handle the actual 30408posting in the background. While this feature usually allows posting 30409to appear to happen very fast, it has no affect on the actual delivery 30410time it takes a message to arrive at its destination. 30411 30412<P> 30413Please Note: 30414<OL> 30415 <LI>This feature will have no effect if the feature 30416 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> 30417 is set. 30418 <LI>This feature isn't supported on all systems. All DOS and Windows, 30419 as well as several Unix ports, do not recognize this feature. 30420 <LI>Error handling is significantly different when this feature is 30421 enabled. Any message posting failure results in the message 30422 being appended to your "Interrupted" mail folder. When you 30423 type the <A HREF="h_common_compose">C</A>ompose command, 30424 Alpine will notice this folder and 30425 offer to extract any messages contained. Upon continuing a 30426 failed message, Alpine will display the nature of the failure 30427 in the status message line. 30428 <LI> <EM>WARNING</EM>: Under extreme conditions, it is possible 30429 for message data to 30430 get lost. <EM>Do</EM> <EM>not</EM> enable this feature 30431 if you typically run close to any sort of disk-space limits or quotas. 30432</OL> 30433<P> 30434<End of help on this topic> 30435</BODY> 30436</HTML> 30437====== h_config_compose_dsn ===== 30438<HTML> 30439<HEAD> 30440<TITLE>FEATURE: <!--#echo var="FEAT_enable-delivery-status-notification"--></TITLE> 30441</HEAD> 30442<BODY> 30443<H1>FEATURE: <!--#echo var="FEAT_enable-delivery-status-notification"--></H1> 30444 30445This feature affects the behavior of Alpine's mail sending. If set, this 30446feature enables a subcommand in the composer's "Send?" confirmation 30447prompt. The subcommand allows you to tell Alpine to request the type of 30448Delivery Status Notification (DSN) that you would like. Most users will 30449be happy with the default, and need not enable this feature. 30450<P> 30451If the feature 30452<A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set, 30453then this feature has no effect and the type of DSN is not selectable. 30454 30455<P> 30456Turning on this feature and then turning on the DSNOpts from the send 30457prompt reveals four on-off toggles at the bottom of the screen. 30458The "X" command toggles between NoErrRets and ErrRets. NoErrRets requests 30459that no notification be returned to you, even if there is a delivery 30460failure. The "D" key toggles between Delay and NoDelay. This tells the 30461server that you are willing (or not) to receive delay notifications, which 30462happen when there is an unusual delay at some mail server (in that mail 30463server's opinion). The "S" key toggles between Success and NoSuccess. 30464Success requests that you be sent a DSN message when the message is 30465successfully delivered to the recipients mailbox. Setting NoErrRets will 30466automatically turn off Delay and Success notification, and will flip the 30467toggles to show that. Similarly, turning on Delay and/or Success will 30468automatically toggle the "X" key to ErrRets. The fourth command, the 30469"H" key, toggles between RetHdrs and RetFull. RetFull requests that 30470the full message be returned in any failed DSN. RetHdrs requests that 30471only the headers be returned in any failed DSN. Notice that this command 30472applies only to failed delivery status reports. For delay or success 30473reports, the full message is never returned, only the headers are returned. 30474 30475<P> 30476If you don't enable the DSN feature or if you don't turn it on for a 30477particular message, the default is that you will be notified about failures, 30478you might be notified about delays, and you won't be notified about 30479successes. You will usually receive the full message back when there is 30480a failure. 30481 30482<P> 30483If you turn on the DSNOpts the default is to return as much information as 30484possible to you. That is, by default, the Success and Delay options are 30485turned on and the full message will be returned on failure. 30486 30487<P> 30488The sending prompt will display the current DSN request (if any) in a 30489shorthand form. It will be: 30490 30491<P><CENTER>[Never]</CENTER> 30492 30493<P> 30494if you have requested NoErrRets. Otherwise, it will look something like: 30495 30496<P><CENTER>[FDS-Hdrs]</CENTER> 30497 30498<P> 30499The "F" will always be there, indicating that you will be notified 30500of failures. (Alpine doesn't provide a way to request no failure notification 30501and at the same time request either success or delay notification. The only 30502way to request no failure notifications is to request no notifications at 30503all with NoErrRets.) The "D" and/or "S" will be present if you have 30504requested Delay and/or Success notification. If one of those is missing, 30505that means you are requesting no notification of the corresponding type. 30506After the dash it will say either Hdrs or Full. Hdrs means to return only 30507the headers and Full means to return the full message (applies to 30508failure notifications only). 30509 30510<P> 30511NOTE: This feature relies on your system's mail transport agent or 30512configured 30513<A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A> 30514having the negotiation mechanism introduced in 30515"Extended SMTP" (ESMTP) and the specific extension called 30516"Delivery Status Notification" (DSN). If the mail transport agent you 30517are using doesn't support DSN, a short warning will be shown to you on 30518the message line at the bottom of the screen after you send your message, 30519but your message will have been sent anyway. 30520 30521<P> 30522Note that DSNs don't provide a mechanism to request read receipts. That 30523is, if you request notification on success you are notified when the 30524message is delivered to the mailbox, not when the message is read. 30525 30526<P> 30527ESMTP allows for graceful migration to upgraded mail transfer agents, but 30528it is possible that this feature might cause problems for some servers. 30529 30530<P> 30531<End of help on this topic> 30532</BODY> 30533</HTML> 30534====== h_config_auto_zoom ===== 30535<HTML> 30536<HEAD> 30537<TITLE>FEATURE: <!--#echo var="FEAT_auto-zoom-after-select"--></TITLE> 30538</HEAD> 30539<BODY> 30540<H1>FEATURE: <!--#echo var="FEAT_auto-zoom-after-select"--></H1> 30541 30542This feature affects the behavior of the Select command. 30543If set, the select command will automatically perform a zoom 30544after the select is complete. 30545This feature is set by default. 30546<P> 30547Some related help topics are 30548<UL> 30549<LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A> 30550<LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>, 30551<LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>, 30552<LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>, and 30553<LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>. 30554<LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>. 30555</UL> 30556 30557<P> 30558<End of help on this topic> 30559</BODY> 30560</HTML> 30561====== h_config_auto_unzoom ===== 30562<HTML> 30563<HEAD> 30564<TITLE>FEATURE: <!--#echo var="FEAT_auto-unzoom-after-apply"--></TITLE> 30565</HEAD> 30566<BODY> 30567<H1>FEATURE: <!--#echo var="FEAT_auto-unzoom-after-apply"--></H1> 30568 30569This feature affects the behavior of the Apply command. If set, and if 30570you are currently looking at a Zoomed Index view of selected messages, 30571the Apply command will do the operation you specify, but then will 30572implicitly do an "UnZoom", so that you will automatically be back in 30573the normal Index view after the Apply. 30574This feature is set by default. 30575 30576<P> 30577Some related help topics are 30578<UL> 30579<LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A> 30580<LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>, 30581<LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>, 30582<LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>. 30583<LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and 30584<LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>. 30585</UL> 30586<P> 30587<End of help on this topic> 30588</BODY> 30589</HTML> 30590====== h_config_auto_unselect ===== 30591<HTML> 30592<HEAD> 30593<TITLE>FEATURE: <!--#echo var="FEAT_auto-unselect-after-apply"--></TITLE> 30594</HEAD> 30595<BODY> 30596<H1>FEATURE: <!--#echo var="FEAT_auto-unselect-after-apply"--></H1> 30597 30598This feature affects the behavior of the Apply command. If set, 30599the Apply command will do the operation you specify, but then will 30600implicitly do an "UnSelect All", so that you will automatically be back in 30601the normal Index view after the Apply. 30602 30603<P> 30604Some related help topics are 30605<UL> 30606<LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A> 30607<LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>, 30608<LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>, 30609<LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and 30610<LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>, and 30611<LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>. 30612</UL> 30613<P> 30614<End of help on this topic> 30615</BODY> 30616</HTML> 30617====== h_config_fast_recent ===== 30618<HTML> 30619<HEAD> 30620<TITLE>FEATURE: <!--#echo var="FEAT_enable-fast-recent-test"--></TITLE> 30621</HEAD> 30622<BODY> 30623<H1>FEATURE: <!--#echo var="FEAT_enable-fast-recent-test"--></H1> 30624 30625This feature controls the behavior of the TAB key when traversing folders 30626in the optional 30627<A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A> 30628collection or in optional <!--#echo var="VAR_news-collections"-->. 30629 30630<P> 30631When the TAB 30632(<A HREF="h_common_nextnew">NextNew</A>) 30633key is pressed, the default behavior is to 30634explicitly examine the status of the folder for the number of recent 30635messages (messages delivered since the last time it was viewed). 30636Depending on the size and number of messages in the folder, this test 30637can be time consuming. 30638 30639<P> 30640Enabling this feature will cause Alpine to only test for the existence of 30641any recent messages rather than to obtain the count. This is much faster 30642in many cases. The downside is that you're not given the number of recent 30643messages when prompted to view the next folder. 30644If the feature 30645<A HREF="h_config_tab_uses_unseen">"<!--#echo var="FEAT_tab-uses-unseen-for-next-folder"-->"</A> 30646is turned on, then the present feature will have no effect. 30647 30648<P> 30649<UL> 30650<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 30651</UL><P> 30652<End of help on this topic> 30653</BODY> 30654</HTML> 30655====== h_config_arrow_nav ===== 30656<HTML> 30657<HEAD> 30658<TITLE>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation"--></TITLE> 30659</HEAD> 30660<BODY> 30661<H1>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation"--></H1> 30662 30663This feature controls the behavior of the left and right arrow keys. 30664If set, the left and right arrow keys will operate like the usual 30665navigation keys < and >. 30666This feature is set by default. 30667 30668<P> 30669If you set this feature, and do not like the changed behavior of the up/down 30670arrow 30671keys when navigating through the FOLDER LIST screen -- 30672<B>first</B> from column to column, if more than one folder is 30673displayed per row, 30674and <B>then</B> from row to row -- you may either also wish to set the feature 30675"<A HREF="h_config_relaxed_arrow_nav"><!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></A>", 30676"<A HREF="h_config_single_list"><!--#echo var="FEAT_single-column-folder-list"--></A>", or 30677use the ^P/^N (instead of up/down arrow) keys to move up/down the list of 30678folders in each column. 30679<P> 30680<UL> 30681<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 30682</UL><P> 30683<End of help on this topic> 30684</BODY> 30685</HTML> 30686====== h_config_relaxed_arrow_nav ===== 30687<HTML> 30688<HEAD> 30689<TITLE>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></TITLE> 30690</HEAD> 30691<BODY> 30692<H1>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></H1> 30693 30694This feature controls the behavior of the left, right, up and down 30695arrow keys in the FOLDER LIST screen when the "<A 30696HREF="h_config_arrow_nav"><!--#echo var="FEAT_enable-arrow-navigation"--></A>" feature is 30697set. 30698This feature is set by default. 30699 30700<P> 30701 30702When this feature is set, the left and right 30703arrow keys in the FOLDER LIST screen 30704move the highlight bar to the left or right, and the up and 30705down arrows move it up or down. 30706 30707<P> 30708When the "<!--#echo var="FEAT_enable-arrow-navigation"-->" feature is set and this 30709feature is not set; 30710the left and right arrow keys in the Folder List screen strictly 30711track the commands bound to the '<' and '>' keys, and the up 30712and down arrow keys move the highlight bar to the previous and next 30713folder or directory name. 30714 30715<P> 30716<UL> 30717<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 30718</UL><P> 30719<End of help on this topic> 30720</BODY> 30721</HTML> 30722====== h_config_alt_compose_menu ===== 30723<HTML> 30724<HEAD> 30725<TITLE>FEATURE: <!--#echo var="FEAT_alternate-compose-menu"--></TITLE> 30726</HEAD> 30727<BODY> 30728<H1>FEATURE: <!--#echo var="FEAT_alternate-compose-menu"--></H1> 30729 30730This feature controls the menu that is displayed when Compose is selected. 30731If set, a list of options will be presented, with each option representing 30732the type of composition that could be used. This feature is most useful for 30733users who want to avoid being prompted with each option separately, or who 30734want to avoid the checking of remote postponed or form letter folders. 30735The possible types of composition are: 30736 30737<P> 30738New, for starting a new composition. Note that if New is selected and roles 30739are set, roles are checked for matches and applied according to the setting 30740of the matching role. 30741 30742<P> 30743Interrupted, for continuing an interrupted composition. This option is only 30744offered if an interrupted message folder is detected. 30745 30746<P> 30747Postponed, for continuing postponed compositions. This option is offered 30748if a <!--#echo var="VAR_postponed-folder"--> is set in the config REGARDLESS OF whether or not 30749the postponed folder actually exists. This option is especially handy 30750for avoiding having to check for the existence of a remote postponed folder. 30751 30752<P> 30753Form, for using form letters. This option is offered if the <!--#echo var="VAR_form-letter-folder"--> 30754is set in the config, and is not checked for existence for reasons similar 30755to those explained by the postponed option. 30756 30757<P> 30758setRole, for selecting a role to apply to a composition. 30759 30760<P> 30761<End of help on this topic> 30762</BODY> 30763</HTML> 30764====== h_config_alt_role_menu ===== 30765<HTML> 30766<HEAD> 30767<TITLE>FEATURE: <!--#echo var="FEAT_alternate-role-menu"--></TITLE> 30768</HEAD> 30769<BODY> 30770<H1>FEATURE: <!--#echo var="FEAT_alternate-role-menu"--></H1> 30771 30772Normally the <A HREF="h_common_role">Role Command</A> allows you to choose 30773a role and compose a new message using that role. 30774When this feature is set, the role command will first ask whether you want to 30775Compose a new message, Forward the current message, Reply to the 30776current message, or Bounce the current message. 30777If you are not in the MESSAGE INDEX and are not viewing a message, 30778then there is no current message and the question will be skipped. 30779After you have chosen to Compose, Forward, Reply, or Bounce you will 30780then choose the role to be used. 30781<P> 30782When Bouncing the "Set From" address is used for the 30783Resent-From header, the "Set Fcc" value is used for the Fcc 30784provided that the option 30785<A HREF="h_config_fcc_on_bounce">"<!--#echo var="FEAT_fcc-on-bounce"-->"</A> is turned on, 30786and the "Use SMTP Server" value is used for the SMTP server, if 30787set. 30788Other actions of the role are ignored when Bouncing. 30789 30790<P> 30791<End of help on this topic> 30792</BODY> 30793</HTML> 30794====== h_config_always_spell_check ===== 30795<HTML> 30796<HEAD> 30797<TITLE>FEATURE: <!--#echo var="FEAT_spell-check-before-sending"--></TITLE> 30798</HEAD> 30799<BODY> 30800<H1>FEATURE: <!--#echo var="FEAT_spell-check-before-sending"--></H1> 30801<P> 30802When this feature is set, every composed message will be spell-checked before 30803being sent. 30804<P> 30805<End of help on this topic> 30806</BODY> 30807</HTML> 30808====== h_config_quell_asterisks ===== 30809<HTML> 30810<HEAD> 30811<TITLE>FEATURE: <!--#echo var="FEAT_suppress-asterisks-in-password-prompt"--></TITLE> 30812</HEAD> 30813<BODY> 30814<H1>FEATURE: <!--#echo var="FEAT_suppress-asterisks-in-password-prompt"--></H1> 30815<P> 30816When you are running Alpine you will sometimes be asked for a password 30817in a prompt on the third line from the bottom of the screen. 30818Normally each password character you type will cause an asterisk to echo 30819on the screen. That gives you some feedback to know that your typing is 30820being recognized. 30821There is a very slight security risk in doing it this way because someone 30822watching over your shoulder might be able to see how many characters there 30823are in your password. 30824If you'd like to suppress the echoing of the asterisks set this feature. 30825<P> 30826<End of help on this topic> 30827</BODY> 30828</HTML> 30829====== h_config_quell_flowed_text ===== 30830<HTML> 30831<HEAD> 30832<TITLE>FEATURE: <!--#echo var="FEAT_quell-flowed-text"--></TITLE> 30833</HEAD> 30834<BODY> 30835<H1>FEATURE: <!--#echo var="FEAT_quell-flowed-text"--></H1> 30836<P> 30837Alpine generates flowed text where possible. 30838The method for generating flowed text is defined by 30839<A HREF="http://www.ietf.org/rfc/rfc3676.txt">RFC 3676</A>, 30840the benefit of doing so is 30841to send message text that can properly be viewed both on normal width displays 30842and on displays with smaller or larger than normal screen widths. 30843With flowed text, a space at the end of a line tells the receiving mail 30844client that the following line belongs to the same paragraph. 30845Quoted text will also be affected, with only the innermost 30846level of ">" quoting being followed by a space. 30847However, if you have changed the 30848<A HREF="h_config_reply_indent_string">"<!--#echo var="VAR_reply-indent-string"-->"</A> 30849so that it is not equal to the default value of "> ", then 30850quoted text will not be flowed. 30851For this reason, we recommend that you leave your 30852"<!--#echo var="VAR_reply-indent-string"-->" set to the default. 30853<P> 30854This feature turns off the generation of flowed text, as it might be 30855desired to more tightly control how a message is displayed on the receiving end. 30856<P> 30857If this feature is <EM>not</EM> set, you can control on a message by message 30858basis whether or not flowed text is generated. 30859You do this by typing ^V at the Send confirmation prompt that you get 30860after typing ^X to send a message. 30861^V is a toggle that turns flowing off and back on if typed again. 30862If for some reason flowing cannot be done on a particular message, then the 30863^V command will not be available. 30864This would be the case, for example, if this feature was set, or if your 30865"<!--#echo var="VAR_reply-indent-string"-->" was set to a non-default value. 30866If the feature 30867<A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set, 30868then the opportunity to control on a message by message basis 30869whether or not flowed text is generated is lost. 30870<P> 30871When this feature is not set and you have typed ^V to turn off flowing, 30872the Send confirmation prompt will change to look like 30873<P> 30874<CENTER><SAMP>Send message (not flowed)?</SAMP></CENTER> 30875<P> 30876<A HREF="h_config_strip_ws_before_send">"<!--#echo var="FEAT_strip-whitespace-before-send"-->"</A> will 30877also turn off the sending of flowed text messages, but it differs in that 30878it also trims all trailing white space from a message before sending it. 30879<P> 30880If alternate editors are used extensively, be aware that a message will still 30881be sent flowed if this feature is unset. In most cases this will be fine, 30882but if the editor has a "flowed text" mode, it would be best to 30883use that. 30884<P> 30885<End of help on this topic> 30886</BODY> 30887</HTML> 30888====== h_config_strip_ws_before_send ===== 30889<HTML> 30890<HEAD> 30891<TITLE>FEATURE: <!--#echo var="FEAT_strip-whitespace-before-send"--></TITLE> 30892</HEAD> 30893<BODY> 30894<H1>FEATURE: <!--#echo var="FEAT_strip-whitespace-before-send"--></H1> 30895<P> 30896By default, trailing whitespace is not stripped from 30897a message before sending. Trailing whitespace should have no effect on an 30898email message, and in flowed text can aid in delimiting paragraphs. 30899However, the old behavior of stripping trailing whitespace was in place 30900to better deal with older clients that couldn't handle certain types of 30901text encodings. This feature restores the old behavior 30902<P> 30903Trailing whitespace is of aid to flowed-text-formatted messages, which are 30904generated by default but can be turned off via the 30905<A HREF="h_config_quell_flowed_text">"<!--#echo var="FEAT_quell-flowed-text"-->"</A> feature. 30906<!--#echo var="FEAT_strip-whitespace-before-send"--> also has the effect of turning off sending 30907of flowed text. 30908<P> 30909<End of help on this topic> 30910</BODY> 30911</HTML> 30912====== h_config_alt_reply_menu ===== 30913<HTML> 30914<HEAD> 30915<TITLE>FEATURE: <!--#echo var="FEAT_alternate-reply-menu"--></TITLE> 30916</HEAD> 30917<BODY> 30918<H1>FEATURE: <!--#echo var="FEAT_alternate-reply-menu"--></H1> 30919 30920Note that if this option is enabled, then the option 30921<A HREF="h_config_auto_include_reply"><!--#echo var="FEAT_include-text-in-reply"--></A> 30922is ignored. See below to understand why. 30923<P> 30924When you reply to a message, a series of questions are asked that 30925determines how your reply will be handled by Alpine. This feature only 30926affects the result of the first question you are asked, and its purpose is 30927to set values that could override defaults set in Alpine's main 30928configuration screen. As a result, this menu allows you to configure even 30929more features than you would be able to do without this option. For 30930example, this menu always allows you to override or select a <A 30931HREF="h_rules_roles">Role</A> if you have defined one, or allows you to 30932override your indent string, regardless of if you have enabled 30933<A HREF="h_config_prefix_editing"><!--#echo var="FEAT_enable-reply-indent-string-editing"--></A>. 30934The full list of options can be found below. 30935<P> 30936Here is an example of how this option works. After you press Reply, 30937if you see "A Inc Attach" in the menu, it means that 30938if you press "A", then Alpine will include the attachments 30939of the original message, and the default is not to include them. 30940Conversely, if you see "A No Attach" 30941then by pressing "A" Alpine will not include 30942attachments in your reply, and the default is that Alpine will 30943include them in your reply. The value that you see when you 30944start your reply is controlled by the option 30945<A HREF="h_config_attach_in_reply"> 30946<!--#echo var="FEAT_include-attachments-in-reply"--> 30947</A>. If the feature is enabled, then Alpine will display 30948"A No Attach" to override the default behavior. You can 30949toggle between the two values of this option by pressing "A". 30950Remember that the value that you see in the menu is the action that will 30951be done when you press the associated command. 30952<P> 30953Below are your options: 30954<OL> 30955<LI><B>A</B>: This determines if Alpine will include or not the 30956attachments sent to you in the message that you are replying to. The default 30957is to use the value of the configuration option 30958<A HREF="h_config_attach_in_reply"><!--#echo var="FEAT_include-attachments-in-reply"--></A> and can be overridden by using this command. 30959 30960<LI><B>H</B>: This command determines if the headers of a message are 30961included in the body of the message that is being replied to. By default 30962Alpine will use the value of the configuration option 30963<A HREF="h_config_include_header"><!--#echo var="FEAT_include-header-in-reply"--></A>. 30964Observe that by toggling this option to include headers, text will be toggled 30965to be included by default. 30966 30967<LI><B>R</B>: Can be used to set a role different from the default. 30968 30969<LI><B>S</B>: Determines if Alpine will strip the signature from a 30970message. The default is to strip the signature when the message is not 30971viewed in headers mode, and you either have enabled 30972<A HREF="h_config_sigdashes"><!--#echo var="FEAT_enable-sigdashes"--></A> 30973or 30974<A HREF="h_config_strip_sigdashes"><!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></A>. 30975 30976<LI><B>Ctrl-R</B>: Can be used to edit the 30977<A HREF="h_config_reply_indent_string">"<!--#echo var="VAR_reply-indent-string"-->"</A>. 30978</OL> 30979<P> 30980In order to include the text of the original message in the reply 30981you either need to press 'y' to include the original text, or 'n' to 30982exclude it from the reply. Pressing return will execute the default 30983action, which is to include text only if the option 30984<A HREF="h_config_auto_include_reply"><!--#echo var="FEAT_include-text-in-reply"--></A> 30985is enabled. However, notice that the default is to include text if you edit the 30986reply indent string or if you explicitly set through this menu that you 30987want headers included in the reply message. 30988 30989<P> 30990<End of help on this topic> 30991</BODY> 30992</HTML> 30993====== h_config_del_from_dot ===== 30994<HTML> 30995<HEAD> 30996<TITLE>FEATURE: <!--#echo var="FEAT_compose-cut-from-cursor"--></TITLE> 30997</HEAD> 30998<BODY> 30999<H1>FEATURE: <!--#echo var="FEAT_compose-cut-from-cursor"--></H1> 31000 31001This feature controls the behavior of the Ctrl-K command in the composer. 31002If set, ^K will cut from the current cursor position to the end of the line, 31003rather than cutting the entire line. 31004 31005<P> 31006<End of help on this topic> 31007</BODY> 31008</HTML> 31009====== h_config_print_index ===== 31010<HTML> 31011<HEAD> 31012<TITLE>FEATURE: <!--#echo var="FEAT_print-index-enabled"--></TITLE> 31013</HEAD> 31014<BODY> 31015<H1>FEATURE: <!--#echo var="FEAT_print-index-enabled"--></H1> 31016 31017This feature controls the behavior of the Print command when in the 31018MESSAGE INDEX screen. If set, the print command will give you a prompt 31019asking if you wish to print the message index, or the currently highlighted 31020message. If not set, the message will be printed. 31021 31022<P> 31023<End of help on this topic> 31024</BODY> 31025</HTML> 31026====== h_config_allow_talk ===== 31027<HTML> 31028<HEAD> 31029<TITLE>FEATURE: <!--#echo var="FEAT_allow-talk"--></TITLE> 31030</HEAD> 31031<BODY> 31032<H1>FEATURE: <!--#echo var="FEAT_allow-talk"--></H1> 31033 31034UNIX Alpine only. 31035<P> 31036By default, permission for others to "talk" to your terminal is turned 31037off when you are running Alpine. When this feature is set, permission is 31038instead turned on. If enabled, you may see unexpected messages in the 31039middle of your Alpine screen from someone attempting to contact you via the 31040"talk" program. 31041 31042<P> 31043NOTE: The "talk" program has nothing to do with Alpine or email. The 31044talk daemon on your system will attempt to print a message on your screen 31045when someone else is trying to contact you. If you wish to see these 31046messages while you are running Alpine, you should enable this feature. 31047 31048<P> 31049If you do enable this feature and see a "talk" message, you must 31050suspend or quit Alpine before you can respond. 31051 31052<P> 31053<End of help on this topic> 31054</BODY> 31055</HTML> 31056====== h_config_send_filter_dflt ===== 31057<HTML> 31058<HEAD> 31059<TITLE>FEATURE: <!--#echo var="FEAT_compose-send-offers-first-filter"--></TITLE> 31060</HEAD> 31061<BODY> 31062<H1>FEATURE: <!--#echo var="FEAT_compose-send-offers-first-filter"--></H1> 31063If you have <A HREF="h_config_sending_filter">"<!--#echo var="VAR_sending-filters"-->"</A> 31064configured, setting this feature will cause 31065the first filter in the <!--#echo var="VAR_sending-filters"--> list to be offered as the default 31066instead of unfiltered, the usual default. 31067<P> 31068<UL> 31069<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 31070</UL><P> 31071<End of help on this topic> 31072</BODY> 31073</HTML> 31074====== h_config_custom_print ===== 31075<HTML> 31076<HEAD> 31077<TITLE>FEATURE: <!--#echo var="FEAT_print-offers-custom-cmd-prompt"--></TITLE> 31078</HEAD> 31079<BODY> 31080<H1>FEATURE: <!--#echo var="FEAT_print-offers-custom-cmd-prompt"--></H1> 31081 31082When this feature is set, the print command will have an additional 31083subcommand called "C CustomPrint". If selected, you will have 31084the opportunity to enter any system print command --instead of being 31085restricted to using those that have been previously configured in the 31086printer setup menu. 31087<P> 31088 31089<End of help on this topic> 31090</BODY> 31091</HTML> 31092====== h_config_enable_dot_files ===== 31093<HTML> 31094<HEAD> 31095<TITLE>FEATURE: <!--#echo var="FEAT_enable-dot-files"--></TITLE> 31096</HEAD> 31097<BODY> 31098<H1>FEATURE: <!--#echo var="FEAT_enable-dot-files"--></H1> 31099 31100When this feature is set, files beginning with dot (".") will be 31101visible in the file browser. For example, you'll be able to select them 31102when using the browser to add an attachment to a message. 31103<P> 31104<End of help on this topic> 31105</BODY> 31106</HTML> 31107====== h_config_enable_dot_folders ===== 31108<HTML> 31109<HEAD> 31110<TITLE>FEATURE: <!--#echo var="FEAT_enable-dot-folders"--></TITLE> 31111</HEAD> 31112<BODY> 31113<H1>FEATURE: <!--#echo var="FEAT_enable-dot-folders"--></H1> 31114 31115When this feature is set, folders beginning with dot (".") may be added 31116and viewed. 31117<P> 31118<End of help on this topic> 31119</BODY> 31120</HTML> 31121====== h_config_ff_between_msgs ===== 31122<HTML> 31123<HEAD> 31124<TITLE>FEATURE: <!--#echo var="FEAT_print-formfeed-between-messages"--></TITLE> 31125</HEAD> 31126<BODY> 31127<H1>FEATURE: <!--#echo var="FEAT_print-formfeed-between-messages"--></H1> 31128 31129Setting this feature causes a formfeed to be printed between messages when 31130printing multiple messages (with Apply Print command). 31131<P> 31132<End of help on this topic> 31133</BODY> 31134</HTML> 31135====== h_config_blank_keymenu ===== 31136<HTML> 31137<HEAD> 31138<TITLE>FEATURE: <!--#echo var="FEAT_disable-keymenu"--></TITLE> 31139</HEAD> 31140<BODY> 31141<H1>FEATURE: <!--#echo var="FEAT_disable-keymenu"--></H1> 31142 31143If this feature is set the command key menu that normally appears on the 31144bottom two lines of the screen will not usually be there. Asking for 31145help with ^G or ? will cause the key menu to appear instead of causing 31146the help message to come up. If you want to actually see the help text, 31147another ^G or ? will show it to you. After the key menu has popped 31148up with the help key it will remain there for an O for Other command but 31149disappear if any other command is typed. 31150<P> 31151<End of help on this topic> 31152</BODY> 31153</HTML> 31154====== h_config_enable_mouse ===== 31155<HTML> 31156<HEAD> 31157<TITLE>FEATURE: <!--#echo var="FEAT_enable-mouse-in-xterm"--></TITLE> 31158</HEAD> 31159<BODY> 31160<H1>FEATURE: <!--#echo var="FEAT_enable-mouse-in-xterm"--></H1> 31161 31162This feature controls whether or not an X terminal mouse can be used with 31163Alpine. If set, and the $DISPLAY variable indicates that an X terminal is 31164being used, the left mouse button on the mouse can be used to select text 31165or commands. 31166Clicking on a command at the bottom of the screen will behave as if you had 31167typed that command. 31168Clicking on an index line will move the current message highlight to 31169that line. 31170Double-clicking on an index line will view the message. 31171Double-clicking on a link will view the link. 31172<P> 31173This type of mouse support will also work in some terminal emulators which are 31174not actually X terminals, but which have extra code to support the xterm 31175style mouse. 31176For those emulators you not only need to turn this feature on but you also 31177have to set the $DISPLAY environment variable even though it isn't needed 31178for your terminal. 31179That will cause Alpine to think that it is an xterm and to properly interpret the 31180escape sequences sent by the mouse. 31181<P> 31182Note: if this feature is set, the behavior of X terminal cut-and-paste is 31183also modified. It is sometimes possible to hold the shift key down while clicking 31184left or middle mouse buttons for the normal xterm cut/paste operations. 31185There is also an Alpine command to toggle this mode on or off. 31186The command is Ctrl-\ (Control-backslash). 31187<P> 31188<End of help on this topic> 31189</BODY> 31190</HTML> 31191====== h_config_enable_xterm_newmail ===== 31192<HTML> 31193<HEAD> 31194<TITLE>FEATURE: <!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></TITLE> 31195</HEAD> 31196<BODY> 31197<H1>FEATURE: <!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></H1> 31198 31199This feature controls whether or not Alpine will attempt to announce new 31200mail arrival when it is running in an X terminal window and that window 31201is iconified. If set, and the $DISPLAY variable indicates that an X 31202terminal is being used, Alpine will send appropriate escape sequences to 31203the X terminal to modify the label on Alpine's icon to indicate that new 31204mail has arrived. Alpine will also modify the Alpine window's title to 31205indicate new mail. 31206See also <a href="h_config_enable_newmail_short_text"><!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></a>. 31207<P> 31208<End of help on this topic> 31209</BODY></HTML> 31210====== h_config_enable_newmail_short_text ===== 31211<HTML> 31212<HEAD> 31213<TITLE>FEATURE: <!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></TITLE> 31214</HEAD> 31215<BODY> 31216<H1>FEATURE: <!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></H1> 31217 31218This feature controls the text to be displayed in an icon in the event 31219of a new message arrival. Normally, the message will 31220be the one that is displayed on the screen. This feature shortens the 31221message to a count of the number of new messages in brackets. This may be 31222more useful for those who use the window's title bar in the task bar as a 31223new mail indicator. This feature is only useful if the 31224<A HREF="h_config_enable_xterm_newmail"><!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></A> 31225feature is also set. Like the <!--#echo var="FEAT_enable-newmail-in-xterm-icon"--> 31226feature, this feature is only relevant when run in an xterm environment. 31227<P> 31228<End of help on this topic> 31229</BODY></HTML> 31230====== h_config_copy_to_to_from ===== 31231<HTML> 31232<HEAD> 31233<TITLE>FEATURE: <!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></TITLE> 31234</HEAD> 31235<BODY> 31236<H1>FEATURE: <!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></H1> 31237 31238This feature affects the From address used when Replying to a message. 31239It is probably only useful if you have some 31240<a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a> 31241defined. 31242When enabled, it checks to see if any of the addresses in the To or Cc 31243fields of the message you are replying to is one of your addresses. 31244If it is, and there is only one of them, then that address is used as 31245the From address in the message you are composing. 31246In other words, you will be using a From address that is the same 31247as the To address that was used to get the mail to you in the first place. 31248 31249<P> 31250If a role is being used and it has a From address defined, that From address will 31251be used rather than the one derived from this feature. 31252 31253<P> 31254<UL> 31255<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 31256</UL><P> 31257<End of help on this topic> 31258</BODY> 31259</HTML> 31260====== h_config_prefix_editing ===== 31261<HTML> 31262<HEAD> 31263<TITLE>FEATURE: <!--#echo var="FEAT_enable-reply-indent-string-editing"--></TITLE> 31264</HEAD> 31265<BODY> 31266<H1>FEATURE: <!--#echo var="FEAT_enable-reply-indent-string-editing"--></H1> 31267 31268This feature affects the Reply command's "Include original message 31269in Reply?" prompt. When enabled, it causes the 31270"Edit Indent String" sub-command to appear which allows 31271you to edit the string Alpine would otherwise use to denote included 31272text from the message being replied to.<P> 31273 31274Thus, you can change Alpine's default message quote character (usually 31275an angle bracket) on a per message basis. So you could change your quoted message to 31276look, for example, like this:<p> 31277 31278<pre>On Tues, 26 Jan 1999, John Q. Smith wrote: 31279 31280John: I just wanted to say hello and to congratulate you 31281John: on a job well done!</pre><p> 31282 31283The configuration option 31284<A HREF="h_config_reply_indent_string">"<!--#echo var="VAR_reply-indent-string"-->"</A> 31285may be used to change what appears as the default string to be edited. 31286<P> 31287NOTE: Edited <!--#echo var="VAR_reply-indent-string"--> only apply to the message 31288currently being replied to. 31289<P> 31290If you change your <!--#echo var="VAR_reply-indent-string"--> 31291so that it is not equal to the default value of "> ", then 31292quoted text will not be flowed 31293(<A HREF="h_config_quell_flowed_text">Flowed Text</A>) 31294when you reply. 31295For this reason, we recommend that you leave your <!--#echo var="VAR_reply-indent-string"--> 31296set to the default value. 31297<P> 31298<UL> 31299<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 31300</UL><P> 31301<End of help on this topic> 31302</BODY> 31303</HTML> 31304====== h_config_enable_search_and_repl ===== 31305<HTML> 31306<HEAD> 31307<TITLE>FEATURE: <!--#echo var="FEAT_enable-search-and-replace"--></TITLE> 31308</HEAD> 31309<BODY> 31310<H1>FEATURE: <!--#echo var="FEAT_enable-search-and-replace"--></H1> 31311 31312This feature modifies the behavior of Alpine's composer. Setting this 31313feature causes Alpine to offer the "^R Replace" subcommand, which 31314allows you to search and replace text strings in a message you are composing, 31315inside the "^W Where is" command. 31316 31317<P> 31318 31319To search and replace text, first enter the text to be replaced at the 31320"Search: " prompt. Then, rather than pressing Enter to just search for that 31321text, press ^R, which turns the prompt into 31322 31323<P> 31324 31325Search (to replace): 31326 31327<P> 31328 31329and then press Enter. The cursor will highlight the first occurrence 31330of the text string you entered, and the prompt will show: 31331 31332<P> 31333 31334Replace "<your text string>" with : 31335 31336<P> 31337 31338where <your text string> is what you entered at the previous prompt; 31339here, enter the replacement text. To only replace the highlighted 31340occurrence, simply press Enter now; to replace all occurrences in the 31341message, press ^X (Repl All), then Enter. You will then be asked to confirm 31342each replacement. 31343 31344<P> 31345 31346The command ^R toggles between "Replace" and "Don't Replace"; its subcommand 31347^X toggles between "Replace All" and "Replace One." 31348 31349<P> 31350 31351If you previously searched for text in a message, it will be offered for 31352re-use as part of the prompt, shown in [ ] brackets. 31353 31354<P> 31355<End of help on this topic> 31356</BODY> 31357</HTML> 31358====== h_config_enable_view_attach ===== 31359<HTML> 31360<HEAD> 31361<TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-attachments"--></TITLE> 31362</HEAD> 31363<BODY> 31364<H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-attachments"--></H1> 31365 31366This feature modifies the behavior of Alpine's MESSAGE TEXT screen. 31367Setting this feature causes Alpine to present attachments in boldface. 31368The first available attachment is displayed in inverse. This is the 31369"selected" attachment. Pressing RETURN will cause Alpine to display 31370the selected attachment. Use the arrow keys to change which of the 31371attachments displayed in boldface is the current selection. 31372 31373<P> 31374 31375Speaking of arrow keys, the Up and Down Arrows will select the next 31376and previous attachments if one is available on the screen for selection. 31377Otherwise, they will simply adjust the viewed text one line up or down. 31378 31379<P> 31380 31381Similarly, when selectable items are present in a message, the Ctrl-F key 31382can be used to select the next item in the message independent of which 31383portion of the viewed message is currently displayed. The Ctrl-B key can 31384be used to select the previous item in the same way. 31385<P> 31386<End of help on this topic> 31387</BODY> 31388</HTML> 31389====== h_config_enable_y_print ===== 31390<HTML> 31391<HEAD> 31392<TITLE>FEATURE: <!--#echo var="FEAT_enable-print-via-y-command"--></TITLE> 31393</HEAD> 31394<BODY> 31395<H1>FEATURE: <!--#echo var="FEAT_enable-print-via-y-command"--></H1> 31396 31397This feature modifies the behavior of Alpine's Print command. 31398<P> 31399By default, Alpine's print command is available by pressing the "%" key. 31400(This command is a substantial change from Pine versions before 4.00 -- 31401where the print command was "Y" -- based on numerous complaints about 31402printing being invoked inadvertently, since Y also means "Yes.") 31403 31404<P> 31405 31406This feature is supplied to mitigate any disruption or anxiety users 31407might feel as a result of this change. 31408 31409<P> 31410 31411Enabling this feature will cause Alpine to recognize both the old 31412command, "Y" for Prynt, as well the new "%" method for invoking 31413printing. Note, key menu labels are not changed as a result of 31414enabling this feature. 31415 31416<P> 31417 31418<End of help on this topic> 31419</BODY> 31420</HTML> 31421====== h_config_enable_lessthan_exit ===== 31422<HTML> 31423<HEAD> 31424<TITLE>FEATURE: <!--#echo var="FEAT_enable-exit-via-lessthan-command"--></TITLE> 31425</HEAD> 31426<BODY> 31427<H1>FEATURE: <!--#echo var="FEAT_enable-exit-via-lessthan-command"--></H1> 31428 31429If this feature is set, then on screens where there is an Exit command 31430but no < command, the < key will perform the same function as the Exit 31431command. 31432This feature is set by default. 31433<P> 31434<End of help on this topic> 31435</BODY> 31436</HTML> 31437====== h_config_enable_view_url ===== 31438<HTML> 31439<HEAD> 31440<TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-urls"--></TITLE> 31441</HEAD> 31442<BODY> 31443<H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-urls"--></H1> 31444This feature modifies the behavior of Alpine's MESSAGE TEXT screen. 31445When this feature is set (the default) Alpine will select possible URLs from the 31446displayed text and display them in boldface for selection. 31447<P> 31448The first available URL is displayed in inverse. This is the 31449"selected" URL. Pressing RETURN will cause Alpine to display 31450the selected URL via either built-in means as with mailto:, imap:, 31451news:, and nntp:, or via an external application as defined 31452by the <A HREF="h_config_browser">"url-viewer"</A> 31453variable. 31454<P> 31455Use the arrow keys to change which of the URLs displayed in boldface 31456is the current selection. 31457<P> 31458Speaking of arrow keys, the Up and Down Arrows will select the next 31459and previous URL if one is available on the screen for selection (unless 31460you have set the feature 31461<A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>). 31462Otherwise, they will simply adjust the viewed text one line up or down. 31463<P> 31464Similarly, when selectable items are present in a message, the Ctrl-F 31465key can be used to select the next item in the message independent 31466of which portion of the viewed message is currently displayed. The 31467Ctrl-B key can be used to select the previous item in the same way. 31468<P> 31469<UL> 31470<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 31471</UL><P> 31472<End of help on this topic> 31473</BODY> 31474</HTML> 31475====== h_config_enable_view_web_host ===== 31476<HTML> 31477<HEAD> 31478<TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-web-hostnames"--></TITLE> 31479</HEAD> 31480<BODY> 31481<H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-web-hostnames"--></H1> 31482 31483This feature modifies the behavior of Alpine's MESSAGE TEXT screen. 31484When this feature is set (the default) Alpine will select possible web hostnames 31485from the displayed text and display them in boldface for selection. 31486This can be useful when you receive messages referencing World Wide Web 31487sites without the use of complete URLs; for example, specifying only 31488"www.some.site.com" (which will <B>not</B> become a 31489selectable 31490item by setting <A HREF="h_config_enable_view_url">"<!--#echo var="FEAT_enable-msg-view-urls"-->"</A>) 31491rather than explicitly 31492"http://www.some.site.com". 31493<P> 31494The first available hostname is displayed in inverse. This is the 31495"selected" hostname. Pressing RETURN will cause Alpine to display 31496the selected hostname via an external application as defined 31497by the <A HREF="h_config_browser">"url-viewer"</A> 31498variable. 31499<P> 31500Use the arrow keys (unless you have set the feature 31501<A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>) 31502to change which of the hostnames displayed in 31503boldface is the current selection. 31504<P> 31505Similarly, when selectable web hostnames are present in a message, the Ctrl-F 31506key can be used to select the next web hostname in the message independent 31507of which portion of the viewed message is currently displayed. The 31508Ctrl-B key can be used to select the previous web hostnames in the same way. 31509<P> 31510<UL> 31511<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 31512</UL><P> 31513<End of help on this topic> 31514</BODY> 31515</HTML> 31516====== h_config_enable_view_addresses ===== 31517<HTML> 31518<HEAD> 31519<TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-addresses"--></TITLE> 31520</HEAD> 31521<BODY> 31522<H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-addresses"--></H1> 31523 31524This feature modifies the behavior of Alpine's MESSAGE TEXT screen. 31525Setting this feature causes Alpine to select possible email addresses 31526from the displayed text and display them in boldface for selection. 31527 31528<P> 31529The first available email address is displayed in inverse. This is the 31530"selected" address. Pressing RETURN will cause Alpine to enter 31531the message composition screen with the To: field filled in with the 31532selected address. 31533<P> 31534Use the arrow keys (unless you have set the feature 31535<A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>) 31536to change which of the hostnames displayed in 31537boldface is the current selection. 31538<P> 31539Similarly, when selectable web hostnames are present in a message, the Ctrl-F 31540key can be used to select the next web hostname in the message independent 31541of which portion of the viewed message is currently displayed. The 31542Ctrl-B key can be used to select the previous web hostnames in the same way. 31543<P> 31544<UL> 31545<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 31546</UL><P> 31547<End of help on this topic> 31548</BODY> 31549</HTML> 31550====== h_external_loads_inline_images_only ===== 31551<HTML> 31552<HEAD> 31553<TITLE>FEATURE: <!--#echo var="FEAT_external-command-loads-inline-images-only"--></TITLE> 31554</HEAD> 31555<BODY> 31556<H1>FEATURE: <!--#echo var="FEAT_external-command-loads-inline-images-only"--></H1> 31557 31558Alpine allows you to pass a HTML message to the browser that you have configured in your 31559<A HREF="h_config_browser"><!--#echo var="VAR_url-viewers"--></A> variable. This allows 31560you to read a message outside of Alpine. This is desirable when Alpine does not display 31561html correctly, or when you wish to read the message and see the inline images in the message. 31562 31563<P> 31564An inline image is one that comes with the message and is necessary for the correct display of 31565the message. However, there are instances in which the source of an image will come from 31566external servers. If this feature is enabled (the default) then Alpine will only pass inline 31567images to the browser and will remove the link to external images, so only inline images will 31568be used to display the message, and no external image will be loaded. Alpine does this to protect 31569your privacy and security. 31570 31571<P> 31572Please note that messages are usually formatted by the sender so that they display correctly once 31573all images have been loaded. Enabling this feature might cause the message not to be correctly 31574displayed by your browser. 31575 31576<P> 31577Also consider security and privacy implications of opening an HTML message in a browser. You are 31578always protected when you do not use this feature, but you might not have the same level of 31579protection if you try to open a spam or scam using the html view. Also commercial email is 31580normally embedded with links to external images that let them, their partners, and your internet 31581service provider (which could be your employer or school) know that you opened their message or 31582connected to a web site, violating your privacy. 31583 31584<P> 31585If you are worried about your privacy and security, do not use an external viewer to open 31586html files, and keep using the internal mechanisms that Alpine provides to read messages. 31587 31588<P> 31589<End of help on this topic> 31590</BODY> 31591<HTML> 31592====== h_config_enable_view_arrows ===== 31593<HTML> 31594<HEAD> 31595<TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-forced-arrows"--></TITLE> 31596</HEAD> 31597<BODY> 31598<H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-forced-arrows"--></H1> 31599 31600This feature modifies Up and Down arrow key behavior in Alpine's 31601MESSAGE TEXT screen when selectable Attachments, URL's, or 31602web-hostnames are presented. Alpine's usual behavior is to move to 31603the next or previous selectable item if currently displayed or 31604simply to adjust the screen view by one line. 31605 31606<P> 31607 31608Setting this feature causes the UP and Down arrow key to behave as 31609if no selectable items were present in the message. 31610 31611<P> 31612 31613Note, the Ctrl-F (next selectable item) and Ctrl-B (previous selectable 31614item) functionality is unchanged. 31615<P> 31616 31617<End of help on this topic> 31618</BODY> 31619<HTML> 31620====== h_config_quell_charset_warning ===== 31621<HTML> 31622<HEAD> 31623<TITLE>FEATURE: <!--#echo var="FEAT_quell-charset-warning"--></TITLE> 31624</HEAD> 31625<BODY> 31626<H1>FEATURE: <!--#echo var="FEAT_quell-charset-warning"--></H1> 31627 31628By default, if the message you are viewing contains characters that are 31629not representable in your 31630<A HREF="h_config_char_set">"Display Character Set"</A> 31631then Alpine will 31632add a warning to the start of the displayed text. 31633If this option is set, then that editorial message will be suppressed. 31634<P> 31635Setting this feature also suppresses the comment about the character set 31636in header lines. 31637For example, when viewing a message you might see 31638<P> 31639<CENTER><SAMP>From: "[ISO-8859-2] Name" <address></SAMP></CENTER> 31640<P> 31641in the From header if your Character-Set is something other than ISO-8859-2. 31642If you set this feature, the comment about the character set will 31643no longer be there. 31644<P> 31645<End of help on this topic> 31646</BODY> 31647</HTML> 31648====== h_config_quell_host_after_url ===== 31649<HTML> 31650<HEAD> 31651<TITLE>FEATURE: <!--#echo var="FEAT_quell-server-after-link-in-html"--></TITLE> 31652</HEAD> 31653<BODY> 31654<H1>FEATURE: <!--#echo var="FEAT_quell-server-after-link-in-html"--></H1> 31655 31656By default, links in HTML text are displayed with the host the link 31657references appended, within square brackets, to the link text. Alpine 31658does this to help indicate where a link will take you, particularly when 31659the link text might suggest a different destination. 31660 31661<P> 31662Setting this feature will prevent the server name from being appended 31663to the displayed text. 31664 31665<P> 31666<End of help on this topic> 31667</BODY> 31668</HTML> 31669====== h_config_prefer_plain_text ===== 31670<HTML> 31671<HEAD> 31672<TITLE>FEATURE: <!--#echo var="FEAT_prefer-plain-text"--></TITLE> 31673</HEAD> 31674<BODY> 31675<H1>FEATURE: <!--#echo var="FEAT_prefer-plain-text"--></H1> 31676 31677A message being viewed may contain alternate versions of the same content. 31678Those alternate versions are supposed to be ordered by the sending software such that the 31679first alternative is the least preferred and the last alternative is the 31680most preferred. Alpine will normally display the most-preferred version that 31681it knows how to display. This is most often encountered where the two 31682alternate versions are a plain text version and an HTML version, with the 31683HTML version listed last as the most preferred. 31684<P> 31685If this option is set, then any plain text version will be preferred to 31686all other versions. 31687<P> 31688When viewing a message there is a command "A TogglePreferPlain", 31689which will temporarily change the sense of this option. 31690If this option is set you will first see the plain text version of a 31691message. 31692If you then type the "A" command, you will see the most preferred version, 31693most likely HTML, instead. 31694Typing the "A" command a second time will switch it back. 31695Alternatively, if the present option is not set you will originally see 31696the most preferred version of the message and typing "A" will switch to 31697the plain text version. 31698<P> 31699<End of help on this topic> 31700</BODY> 31701</HTML> 31702====== h_config_pass_control ===== 31703<HTML> 31704<HEAD> 31705<TITLE>FEATURE: <!--#echo var="FEAT_pass-control-characters-as-is"--></TITLE> 31706</HEAD> 31707<BODY> 31708<H1>FEATURE: <!--#echo var="FEAT_pass-control-characters-as-is"--></H1> 31709 31710It is probably not useful to set this option. 31711This is a legacy option left behind "just in case". 31712Multi-byte characters that have an octet that has the same 31713value as a control character are permitted through whether or not 31714this option is turned on. 31715<P> 31716This feature controls how certain characters contained in messages are 31717displayed. 31718If set, all characters in a message will be sent to the 31719screen. Normally, control characters are displayed as shown below to 31720avoid a garbled screen and to 31721avoid inadvertently changing terminal setup parameters. 31722Control characters are usually displayed as two character sequences like 31723<P><CENTER><SAMP> ^C </SAMP></CENTER><P> 31724for Control-C, 31725<P><CENTER><SAMP> ^[ </SAMP></CENTER><P> 31726for ESCAPE, 31727<P><CENTER><SAMP> ^? </SAMP></CENTER><P> 31728for DELETE, and 31729<P><CENTER><SAMP> ~E </SAMP></CENTER><P> 31730for the character with value 133 (0x85). 31731(The DEL character is displayed as ^?, regular control characters are displayed 31732as the character ^ followed by the character obtained by adding the 31733five low-order bits of the character to 0x40, and the C1 31734control characters 0x80 - 0x9F are displayed as the character ~ followed by the 31735character obtained by adding the 31736five low-order bits of the character to 0x40.) 31737Sometimes, in cases where changing a single control character into a 31738two-character sequence would confuse Alpine's display routines, 31739a question mark is substituted for the control character. 31740<P> 31741If you wish to filter out regular control characters but pass the 31742so-called C1 control characters (0x80 <= char < 0xA0) through unchanged, then 31743you may leave this feature unset and set the feature <A HREF="h_config_pass_c1_control"><!--#echo var="FEAT_pass-c1-control-characters-as-is"--></A> instead. 31744<P> 31745<End of help on this topic> 31746</BODY> 31747</HTML> 31748====== h_config_pass_c1_control ===== 31749<HTML> 31750<HEAD> 31751<TITLE>FEATURE: <!--#echo var="FEAT_pass-c1-control-characters-as-is"--></TITLE> 31752</HEAD> 31753<BODY> 31754<H1>FEATURE: <!--#echo var="FEAT_pass-c1-control-characters-as-is"--></H1> 31755 31756It is probably not useful to set this option. 31757This is a legacy option left behind "just in case". 31758Multi-byte characters that have an octet that has the same 31759value as a control character are permitted through whether or not 31760this option is turned on. 31761<P> 31762If the feature <A HREF="h_config_pass_control"><!--#echo var="FEAT_pass-control-characters-as-is"--></A> 31763is set, then this feature has no effect. 31764However, if you wish to filter out regular control characters but pass the 31765so-called C1 control characters (0x80 <= char < 0xA0) through unchanged, then 31766you may leave <A HREF="h_config_pass_control"><!--#echo var="FEAT_pass-control-characters-as-is"--></A> 31767unset and set this feature. 31768<P> 31769<End of help on this topic> 31770</BODY> 31771</HTML> 31772====== h_config_fcc_on_bounce ===== 31773<HTML> 31774<HEAD> 31775<TITLE>FEATURE: <!--#echo var="FEAT_fcc-on-bounce"--></TITLE> 31776</HEAD> 31777<BODY> 31778<H1>FEATURE: <!--#echo var="FEAT_fcc-on-bounce"--></H1> 31779 31780This feature controls an aspect of Alpine's behavior when bouncing a 31781message. If set, normal FCC ("File Carbon Copy") processing will be 31782done, just as if you had composed a message to the address you are 31783bouncing to. If not set, no FCC of the message will be saved. 31784<P> 31785<End of help on this topic> 31786</BODY> 31787</HTML> 31788====== h_config_show_cursor ===== 31789<HTML> 31790<HEAD> 31791<TITLE>FEATURE: <!--#echo var="FEAT_show-cursor"--></TITLE> 31792</HEAD> 31793<BODY> 31794<H1>FEATURE: <!--#echo var="FEAT_show-cursor"--></H1> 31795 31796This feature controls an aspect of Alpine's displays. If set, the system 31797cursor will move to convenient locations in the displays. For example, 31798to the beginning of the status field of the highlighted index line, or 31799to the highlighted word after a successful WhereIs command. It is intended 31800to draw your attention to an "interesting" spot on the screen. 31801<P> 31802<End of help on this topic> 31803</BODY> 31804</HTML> 31805====== h_config_sort_fcc_alpha ===== 31806<HTML> 31807<HEAD> 31808<TITLE>FEATURE: <!--#echo var="FEAT_sort-default-fcc-alpha"--></TITLE> 31809</HEAD> 31810<BODY> 31811<H1>FEATURE: <!--#echo var="FEAT_sort-default-fcc-alpha"--></H1> 31812 31813This feature controls an aspect of Alpine's FOLDER LIST screen. 31814If set, the default Fcc folder will be sorted alphabetically with the other 31815folders instead of appearing right after the INBOX. 31816<P> 31817<End of help on this topic> 31818</BODY> 31819</HTML> 31820====== h_config_sort_save_alpha ===== 31821<HTML> 31822<HEAD> 31823<TITLE>FEATURE: <!--#echo var="FEAT_sort-default-save-alpha"--></TITLE> 31824</HEAD> 31825<BODY> 31826<H1>FEATURE: <!--#echo var="FEAT_sort-default-save-alpha"--></H1> 31827 31828This feature controls an aspect of Alpine's FOLDER LIST screen. 31829If set, the default save folder will be sorted alphabetically with the other 31830folders instead of appearing right after the INBOX (and default FCC folder). 31831<P> 31832<End of help on this topic> 31833</BODY> 31834</HTML> 31835====== h_config_single_list ===== 31836<HTML> 31837<HEAD> 31838<TITLE>FEATURE: <!--#echo var="FEAT_single-column-folder-list"--></TITLE> 31839</HEAD> 31840<BODY> 31841<H1>FEATURE: <!--#echo var="FEAT_single-column-folder-list"--></H1> 31842 31843This feature controls an aspect of Alpine's FOLDER LIST screen. If set, 31844the folders will be listed one per line instead of several per line 31845in the FOLDER LIST display. 31846<P> 31847<End of help on this topic> 31848</BODY> 31849</HTML> 31850====== h_config_vertical_list ===== 31851<HTML> 31852<HEAD> 31853<TITLE>FEATURE: <!--#echo var="FEAT_vertical-folder-list"--></TITLE> 31854</HEAD> 31855<BODY> 31856<H1>FEATURE: <!--#echo var="FEAT_vertical-folder-list"--></H1> 31857 31858This feature controls an aspect of Alpine's FOLDER LIST screen. If set, 31859the folders will be listed alphabetically down the columns rather 31860than across the columns as is the default. 31861<P> 31862<End of help on this topic> 31863</BODY> 31864</HTML> 31865====== h_config_verbose_post ===== 31866<HTML> 31867<HEAD> 31868<TITLE>FEATURE: <!--#echo var="FEAT_enable-verbose-smtp-posting"--></TITLE> 31869</HEAD> 31870<BODY> 31871<H1>FEATURE: <!--#echo var="FEAT_enable-verbose-smtp-posting"--></H1> 31872This feature controls an aspect of Alpine's message sending. When enabled, 31873Alpine will send a VERB (i.e., VERBose) command early in the posting process 31874intended to cause the SMTP server to provide a more detailed account of 31875the transaction. This feature is typically only useful to system 31876administrators and other support personnel as an aid in troubleshooting 31877problems. 31878<P> 31879Note, this feature relies on a specific capability of the system's mail 31880transport agent or configured 31881<A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>. 31882It is possible that this 31883feature will cause problems for some transport agents, and may result in 31884sending failure. In addition, as the verbose output comes from the mail 31885transport agent, it is likely to vary from one system to another. 31886<P><UL> 31887<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 31888</UL><P> 31889<End of help on this topic> 31890</BODY> 31891</HTML> 31892====== h_config_auto_reply_to ===== 31893<HTML> 31894<HEAD> 31895<TITLE>FEATURE: <!--#echo var="FEAT_reply-always-uses-reply-to"--></TITLE> 31896</HEAD> 31897<BODY> 31898<H1>FEATURE: <!--#echo var="FEAT_reply-always-uses-reply-to"--></H1> 31899 31900This feature controls an aspect of Alpine's Reply command. If set, Alpine 31901will not prompt when a message being replied to contains a "Reply-To:" 31902header value, but will simply use its value (as opposed to using the 31903"From:" field's value). 31904 31905<P> 31906 31907Note: Using the "Reply-To:" address is usually the preferred behavior, 31908however, some mailing list managers choose to place the list's address in 31909the "Reply-To:" field of any message sent out to the list. In such 31910cases, this feature makes it all too easy for personal replies to be 31911inadvertently sent to the entire mail list, so be careful! 31912<P> 31913<End of help on this topic> 31914</BODY> 31915</HTML> 31916====== h_config_del_skips_del ===== 31917<HTML> 31918<HEAD> 31919<TITLE>FEATURE: <!--#echo var="FEAT_delete-skips-deleted"--></TITLE> 31920</HEAD> 31921<BODY> 31922<H1>FEATURE: <!--#echo var="FEAT_delete-skips-deleted"--></H1> 31923 31924This feature controls an aspect of Alpine's Delete command. If set, this 31925feature will cause the Delete command to advance past following messages that 31926are marked deleted. In other words, pressing "D" will both mark the 31927current message deleted and advance to the next message that is not marked 31928deleted. 31929This feature is set by default. 31930<P> 31931<End of help on this topic> 31932</BODY></HTML> 31933====== h_config_expunge_manually ===== 31934<HTML> 31935<HEAD> 31936<TITLE>FEATURE: <!--#echo var="FEAT_expunge-only-manually"--></TITLE> 31937</HEAD> 31938<BODY> 31939<H1>FEATURE: <!--#echo var="FEAT_expunge-only-manually"--></H1> 31940 31941Normally, when you close a folder that contains deleted messages you are 31942asked if you want to expunge those messages from the folder permanently. 31943If this feature is set, you won't be asked and the deleted messages will 31944remain in the folder. 31945If you choose to set this feature you will have to expunge the 31946messages manually using the eXpunge command, which you can use while 31947in the MESSAGE INDEX screen. 31948If you do not expunge deleted messages the size of your 31949folder will continue to increase until you are out of disk space. 31950<P> 31951<UL> 31952<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 31953</UL><P> 31954<End of help on this topic> 31955</BODY> 31956</HTML> 31957====== h_config_auto_expunge ===== 31958<HTML> 31959<HEAD> 31960<TITLE>FEATURE: <!--#echo var="FEAT_expunge-without-confirm"--></TITLE> 31961</HEAD> 31962<BODY> 31963<H1>FEATURE: <!--#echo var="FEAT_expunge-without-confirm"--></H1> 31964 31965This features controls an aspect of Alpine's eXpunge command. If set, you 31966will <B>not</B> be prompted to confirm your intent before the expunge takes 31967place. 31968Actually, this is only true for the INBOX folder and for folders in the 31969Incoming Folders collection. See the feature 31970<A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A>. 31971<P> 31972<UL> 31973<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 31974</UL><P> 31975<End of help on this topic> 31976</BODY> 31977</HTML> 31978====== h_config_full_auto_expunge ===== 31979<HTML> 31980<HEAD> 31981<TITLE>FEATURE: <!--#echo var="FEAT_expunge-without-confirm-everywhere"--></TITLE> 31982</HEAD> 31983<BODY> 31984<H1>FEATURE: <!--#echo var="FEAT_expunge-without-confirm-everywhere"--></H1> 31985 31986This features controls an aspect of Alpine's eXpunge command. If set, you 31987will <B>not</B> be prompted to confirm your intent before the expunge 31988takes place. This feature sets this behavior for all folders, unlike the 31989<A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A> 31990feature that works only for incoming folders. 31991<P> 31992<UL> 31993<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 31994</UL><P> 31995<End of help on this topic> 31996</BODY> 31997</HTML> 31998====== h_config_auto_read_msgs ===== 31999<HTML> 32000<HEAD> 32001<TITLE>FEATURE: <!--#echo var="FEAT_auto-move-read-msgs"--></TITLE> 32002</HEAD> 32003<BODY> 32004<H1>FEATURE: <!--#echo var="FEAT_auto-move-read-msgs"--></H1> 32005This feature controls an aspect of Alpine's behavior upon quitting. If set, 32006and the 32007<A HREF="h_config_read_message_folder">"<!--#echo var="VAR_read-message-folder"-->"</A> 32008option is also set, then Alpine will 32009automatically transfer all read messages to the designated folder and mark 32010them as deleted in the INBOX. Messages in the INBOX marked with an 32011"N" (meaning New, or unseen) are not affected. 32012<P> 32013<UL> 32014<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 32015</UL><P> 32016<End of help on this topic> 32017</BODY> 32018</HTML> 32019====== h_config_auto_fcc_only ===== 32020<HTML> 32021<HEAD> 32022<TITLE>FEATURE: <!--#echo var="FEAT_fcc-only-without-confirm"--></TITLE> 32023</HEAD> 32024<BODY> 32025<H1>FEATURE: <!--#echo var="FEAT_fcc-only-without-confirm"--></H1> 32026This features controls an aspect of Alpine's composer. 32027The only time this feature will be used is if you attempt to send mail 32028that has no recipients but does have an Fcc. 32029Normally, Alpine will ask if you really mean to copy the message only to 32030the Fcc. 32031That is, it asks if you really meant to have no recipients. 32032If this feature is set, you 32033will <B>not</B> be prompted to confirm your intent to make only a copy 32034of a message with no recipients. 32035<P> 32036This feature is closely related to 32037<A HREF="h_config_warn_if_no_to_or_cc"><!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></A>. 32038The difference between this feature and that feature is that this feature 32039considers a Bcc to be a recipient while that feature will ask for confirmation 32040even if there is a Bcc when there is no To, Cc, or Newsgroup. 32041The default values also differ. This feature defaults to asking the question 32042and you have to turn it off. 32043The <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--> feature defaults to not asking 32044unless you turn it on. 32045<P> 32046 32047<UL> 32048<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 32049</UL><P> 32050<End of help on this topic> 32051</BODY> 32052</HTML> 32053====== h_config_mark_fcc_seen ===== 32054<HTML> 32055<HEAD> 32056<TITLE>FEATURE: <!--#echo var="FEAT_mark-fcc-seen"--></TITLE> 32057</HEAD> 32058<BODY> 32059<H1>FEATURE: <!--#echo var="FEAT_mark-fcc-seen"--></H1> 32060 32061This features controls the way Fccs (File carbon copies) are 32062made of the messages you send. 32063 32064<P> 32065Normally, when Alpine saves a copy of a message you sent as an Fcc, that 32066copy will be marked as Unseen. 32067When you look at the folder it was saved in the message will appear to 32068be a New message until you read it. 32069When this feature is enabled, the message will be marked as having 32070been Seen. 32071 32072<P> 32073<UL> 32074<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 32075</UL><P> 32076<End of help on this topic> 32077</BODY> 32078</HTML> 32079====== h_config_no_fcc_attach ===== 32080<HTML> 32081<HEAD> 32082<TITLE>FEATURE: <!--#echo var="FEAT_fcc-without-attachments"--></TITLE> 32083</HEAD> 32084<BODY> 32085<H1>FEATURE: <!--#echo var="FEAT_fcc-without-attachments"--></H1> 32086 32087This features controls the way Fcc's (File carbon copies) are 32088made of the messages you send. 32089 32090<P> 32091Normally, Alpine saves an exact copy of your message as it was sent. 32092When this feature is enabled, the "body" of the message 32093you send (the text you type in the composer) is preserved in the 32094copy as before, however all attachments are replaced with text 32095explaining what had been sent rather than the attachments themselves. 32096 32097<P> 32098This feature also affects Alpine's "Send ?" confirmation prompt 32099in that a new "^F Fcc Attchmnts" option becomes available which 32100allows you to interactively set whether or not attachments are saved 32101to the Fcc'd copy. 32102 32103<P> 32104<UL> 32105<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 32106</UL><P> 32107<End of help on this topic> 32108</BODY> 32109</HTML> 32110====== h_config_read_in_newsrc_order ===== 32111<HTML> 32112<HEAD> 32113<TITLE>FEATURE: <!--#echo var="FEAT_news-read-in-newsrc-order"--></TITLE> 32114</HEAD> 32115<BODY> 32116<H1>FEATURE: <!--#echo var="FEAT_news-read-in-newsrc-order"--></H1> 32117 32118This feature controls the order in which newsgroups will be presented. If 32119set, they will be presented in the same order as they occur in your 32120<!--chtml if pinemode="os_windows"--> 32121"NEWSRC" 32122<!--chtml else--> 32123".newsrc" 32124<!--chtml endif--> 32125file (the default location of which can be changed with the 32126<A HREF="h_config_newsrc_path">"<!--#echo var="VAR_newsrc-path"-->"</A> option). 32127<P> 32128If not set, the newsgroups will be presented in alphabetical order. 32129<P> 32130<UL> 32131<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 32132</UL><P> 32133<End of help on this topic> 32134</BODY> 32135</HTML> 32136====== h_config_quell_tz_comment ===== 32137<HTML> 32138<HEAD> 32139<TITLE>FEATURE: <!--#echo var="FEAT_quell-timezone-comment-when-sending"--></TITLE> 32140</HEAD> 32141<BODY> 32142<H1>FEATURE: <!--#echo var="FEAT_quell-timezone-comment-when-sending"--></H1> 32143 32144Normally, when Alpine generates a Date header for outgoing mail, 32145it will try to include the symbolic timezone at the end of the 32146header inside parentheses. 32147The symbolic timezone is often three characters long, but on 32148some operating systems, it may be longer. 32149Apparently there are some SMTP servers in the world that will reject an 32150incoming message if it has a Date header longer than about 80 characters. 32151If this feature is set, the symbolic timezone normally generated by 32152Alpine will not be included. 32153You probably don't need to worry about this feature unless you run into 32154the problem described above. 32155 32156<P> 32157<End of help on this topic> 32158</BODY> 32159</HTML> 32160====== h_config_post_wo_validation ===== 32161<HTML> 32162<HEAD> 32163<TITLE>FEATURE: <!--#echo var="FEAT_news-post-without-validation"--></TITLE> 32164</HEAD> 32165<BODY> 32166<H1>FEATURE: <!--#echo var="FEAT_news-post-without-validation"--></H1> 32167 32168This feature controls whether the NNTP server is queried as newsgroups 32169are entered for posting. Validation over slow links (e.g. dialup using 32170SLIP or PPP) can cause delays. Set this feature to eliminate such delays. 32171<P> 32172<End of help on this topic> 32173</BODY> 32174</HTML> 32175====== h_config_send_wo_confirm ===== 32176<HTML> 32177<HEAD> 32178<TITLE>FEATURE: <!--#echo var="FEAT_send-without-confirm"--></TITLE> 32179</HEAD> 32180<BODY> 32181<H1>FEATURE: <!--#echo var="FEAT_send-without-confirm"--></H1> 32182 32183By default, when you send or post a message you will be asked to confirm 32184with a question that looks something like: 32185 32186<P> 32187<CENTER><SAMP>Send message?</SAMP></CENTER> 32188<P> 32189 32190If this feature is set, you 32191will <B>not</B> be prompted to confirm your intent to send 32192and your message will be sent. 32193<P> 32194If this feature is set it disables some possibilities and renders some 32195other features meaningless. 32196You will not be able to use 32197<A HREF="h_config_sending_filter">Sending Filters</A>, 32198Verbose sending mode, 32199<A HREF="h_config_compose_bg_post">Background Sending</A>, 32200<A HREF="h_config_compose_dsn">Delivery Status Notifications</A>, 32201or ^V to turn off the generation of flowed text for this message. 32202These options are normally available as suboptions in the Send prompt, but 32203with no Send prompt the options are gone. 32204 32205<P> 32206A somewhat related feature is 32207<A HREF="h_config_quell_post_prompt">"<!--#echo var="FEAT_quell-extra-post-prompt"-->"</A>, 32208which may be used to eliminate the extra confirmation 32209question when posting to a newsgroup. 32210<P> 32211<UL> 32212<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 32213</UL><P> 32214<End of help on this topic> 32215</BODY> 32216</HTML> 32217====== h_config_quell_filtering_done_message ===== 32218<HTML> 32219<HEAD> 32220<TITLE>FEATURE: <!--#echo var="FEAT_quell-filtering-done-message"--></TITLE> 32221</HEAD> 32222<BODY> 32223<H1>FEATURE: <!--#echo var="FEAT_quell-filtering-done-message"--></H1> 32224 32225If you use Filter Rules that move messages or set status of messages 32226you sometimes see a message from Alpine that looks like 32227 32228<P> 32229<CENTER><SAMP>filtering done</SAMP></CENTER> 32230<P> 32231 32232If this feature is set, this message will be suppressed. 32233If the feature 32234<A HREF="h_config_quell_filtering_messages"><!--#echo var="FEAT_quell-filtering-messages"--></A> 32235is set then this message will be suppressed regardless. 32236 32237<P> 32238<UL> 32239<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 32240</UL><P> 32241<End of help on this topic> 32242</BODY> 32243</HTML> 32244====== h_config_quell_filtering_messages ===== 32245<HTML> 32246<HEAD> 32247<TITLE>FEATURE: <!--#echo var="FEAT_quell-filtering-messages"--></TITLE> 32248</HEAD> 32249<BODY> 32250<H1>FEATURE: <!--#echo var="FEAT_quell-filtering-messages"--></H1> 32251 32252If you use Filter Rules that move messages or set status of messages 32253you sometimes see messages from Alpine that look like 32254 32255<P> 32256<CENTER><SAMP><filter name>: Moving 2 filtered messages to <folder name></SAMP></CENTER> 32257<P> 32258 32259or 32260 32261<P> 32262<CENTER><SAMP><filter name>: Setting flags in 5 messages</SAMP></CENTER> 32263<P> 32264 32265or 32266 32267<P> 32268<CENTER><SAMP>Processing filter <filter name></SAMP></CENTER> 32269<P> 32270 32271If this feature is set, these messages will be suppressed. 32272The feature 32273<A HREF="h_config_quell_filtering_done_message"><!--#echo var="FEAT_quell-filtering-done-message"--></A> 32274is related. 32275 32276<P> 32277<UL> 32278<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 32279</UL><P> 32280<End of help on this topic> 32281</BODY> 32282</HTML> 32283====== h_config_quell_post_prompt ===== 32284<HTML> 32285<HEAD> 32286<TITLE>FEATURE: <!--#echo var="FEAT_quell-extra-post-prompt"--></TITLE> 32287</HEAD> 32288<BODY> 32289<H1>FEATURE: <!--#echo var="FEAT_quell-extra-post-prompt"--></H1> 32290 32291By default, when you post a message to a newsgroup you are asked to confirm 32292that you want to post with the question 32293 32294<P> 32295<CENTER><SAMP>Posted message may go to thousands of readers. Really post?</SAMP></CENTER> 32296<P> 32297 32298If this feature is set, you 32299will <B>not</B> be prompted to confirm your intent to post to a newsgroup 32300and your message will be posted. 32301 32302<P> 32303<UL> 32304<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 32305</UL><P> 32306<End of help on this topic> 32307</BODY> 32308</HTML> 32309====== h_config_check_mail_onquit ===== 32310<HTML> 32311<HEAD> 32312<TITLE>FEATURE: <!--#echo var="FEAT_check-newmail-when-quitting"--></TITLE> 32313</HEAD> 32314<BODY> 32315<H1>FEATURE: <!--#echo var="FEAT_check-newmail-when-quitting"--></H1> 32316 32317If this feature is set, Alpine will check for new mail after you give the 32318Quit command. 32319If new mail has arrived since the previous check, you will be notified 32320and given the choice of quitting or not quitting. 32321<P> 32322<UL> 32323<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 32324</UL><P> 32325<End of help on this topic> 32326</BODY> 32327</HTML> 32328====== h_config_inbox_no_confirm ===== 32329<HTML> 32330<HEAD> 32331<TITLE>FEATURE: <!--#echo var="FEAT_return-to-inbox-without-confirm"--></TITLE> 32332</HEAD> 32333<BODY> 32334<H1>FEATURE: <!--#echo var="FEAT_return-to-inbox-without-confirm"--></H1> 32335 32336Normally, when you use the TAB <A HREF="h_common_nextnew">NextNew</A> 32337command and there are no more folders or newsgroups to visit, you are asked 32338if you want to return to the INBOX. 32339If this feature is set you will not be asked. 32340It will be assumed that you do want to return to the INBOX. 32341<P> 32342<UL> 32343<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 32344</UL><P> 32345<End of help on this topic> 32346</BODY> 32347</HTML> 32348====== h_config_dates_to_local ===== 32349<HTML> 32350<HEAD> 32351<TITLE>FEATURE: <!--#echo var="FEAT_convert-dates-to-localtime"--></TITLE> 32352</HEAD> 32353<BODY> 32354<H1>FEATURE: <!--#echo var="FEAT_convert-dates-to-localtime"--></H1> 32355 32356Normally, the message dates that you see in the 32357MESSAGE INDEX and MESSAGE VIEW are displayed in the timezone they were sent from. 32358For example, if a message was sent to you from a few timezones to the east 32359it might appear that it was sent from the future; 32360or if it was sent from somewhere to the west it might appear 32361as if it is from yesterday even though it was sent only a few minutes ago. 32362If this feature is set an attempt will be made to convert the dates 32363to your local timezone to be displayed. 32364<P> 32365Note that this does not affect the results of Select by Date or of 32366anything else other than these displayed dates. 32367When viewing the message you may look at the original unconverted value of the Date 32368header by using the <A HREF="h_common_hdrmode">HdrMode Command</A>. 32369<P> 32370<UL> 32371<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 32372</UL><P> 32373<End of help on this topic> 32374</BODY> 32375</HTML> 32376====== h_config_tab_no_prompt ===== 32377<HTML> 32378<HEAD> 32379<TITLE>FEATURE: <!--#echo var="FEAT_continue-tab-without-confirm"--></TITLE> 32380</HEAD> 32381<BODY> 32382<H1>FEATURE: <!--#echo var="FEAT_continue-tab-without-confirm"--></H1> 32383 32384Normally, when you use the TAB <A HREF="h_common_nextnew">NextNew</A> 32385command and there is a problem checking a folder, you are asked 32386whether you want to continue with the search in the following folder or not. 32387This question gives you a chance to stop the NextNew processing. 32388(The checking problem might be caused by the fact that the folder does not 32389exist, or by an authentication problem, or by a server problem 32390of some sort.) 32391<P> 32392 32393If this feature is set you will not be asked. 32394It will be assumed that you do want to continue. 32395<P> 32396<UL> 32397<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 32398</UL><P> 32399<End of help on this topic> 32400</BODY> 32401</HTML> 32402====== h_config_input_history ===== 32403<HTML> 32404<HEAD> 32405<TITLE>FEATURE: <!--#echo var="FEAT_disable-save-input-history"--></TITLE> 32406</HEAD> 32407<BODY> 32408<H1>FEATURE: <!--#echo var="FEAT_disable-save-input-history"--></H1> 32409 32410Many of the prompts that ask for input in the status line near the 32411bottom of the screen will respond to Up Arrow and Down Arrow 32412with the history of previous entries. 32413For example, in the MESSAGE INDEX screen when you use the WhereIs 32414command the text you entered will be remembered and can be recalled 32415by using the Up Arrow key. 32416Another example, when saving a message the folders saved to will 32417be remembered and can be recalled using the arrow keys. 32418<P> 32419In the Save prompt, some users prefer that the Up and Down arrow keys 32420be used for the Previous Collection and Next Collection commands 32421instead of for a history of previous saves. 32422If this option is set the Up and Down arrow keys will become synonyms for the 32423Previous Collection and Next Collection (^P and ^N) commands in the 32424prompt for the name of a folder to Save to or in the prompt for the 32425name of a folder to GoTo. 32426When this feature is not set (the default), ^P and ^N will change the 32427collection and the arrow keys will show the history. 32428<P> 32429<UL> 32430<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 32431</UL><P> 32432<End of help on this topic> 32433</BODY> 32434</HTML> 32435====== h_config_confirm_role ===== 32436<HTML> 32437<HEAD> 32438<TITLE>FEATURE: <!--#echo var="FEAT_confirm-role-even-for-default"--></TITLE> 32439</HEAD> 32440<BODY> 32441<H1>FEATURE: <!--#echo var="FEAT_confirm-role-even-for-default"--></H1> 32442 32443If you have roles, when you Reply to or Forward a message, or Compose 32444a new message, Alpine 32445will search through your roles for one that matches. 32446Normally, if no matches are found you will be placed into the composer 32447with no opportunity to select a role. 32448If this feature is set, then you will be asked to confirm that you don't 32449want a role. 32450This will give you the opportunity to select a role (with the ^T command). 32451If you confirm no role with a Return, you will be placed in 32452the composer with no role. 32453You may also confirm with either an "N" or a "Y". 32454These behave the same as if you pressed the Return. 32455(The "N" and "Y" answers are available because they 32456match what you might type if there was a role match.) 32457<P> 32458If you are using the alternate form of the Compose command called 32459"Role", then all of your roles will be available to you, 32460independent of the value of this feature and of the values set for all of 32461Reply Use, Forward Use, and Compose Use. 32462<P> 32463<UL> 32464<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 32465</UL><P> 32466<End of help on this topic> 32467</BODY> 32468</HTML> 32469====== h_config_news_cross_deletes ===== 32470<HTML> 32471<HEAD> 32472<TITLE>FEATURE: <!--#echo var="FEAT_news-deletes-across-groups"--></TITLE> 32473</HEAD> 32474<BODY> 32475<H1>FEATURE: <!--#echo var="FEAT_news-deletes-across-groups"--></H1> 32476 32477This feature controls what Alpine does when you delete a message in a 32478newsgroup that appears in more than one newsgroup. Such a message 32479is sometimes termed a "crossposting" in that it was posted 32480across several newsgroups. 32481 32482<P> 32483Alpine's default behavior when you delete such a message is to remove 32484only the copy in the current newsgroup from view when you use the 32485"Exclude" command or the next time you visit the newsgroup. 32486 32487<P> 32488Enabling this feature causes Alpine to remove every occurrence of the 32489message from all newsgroups it appears in and to which you are 32490subscribed. 32491 32492<P> 32493NOTE: As currently implemented, enabling this feature may increase the 32494time it takes the Expunge command and newsgroup closing to complete. 32495 32496<P> 32497<UL> 32498<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 32499</UL><P> 32500<End of help on this topic> 32501</BODY> 32502</HTML> 32503====== h_config_news_catchup ===== 32504<HTML> 32505<HEAD> 32506<TITLE>FEATURE: <!--#echo var="FEAT_news-offers-catchup-on-close"--></TITLE> 32507</HEAD> 32508<BODY> 32509<H1>FEATURE: <!--#echo var="FEAT_news-offers-catchup-on-close"--></H1> 32510 32511This feature controls what Alpine does as it closes a newsgroup. 32512When set, Alpine will offer to delete all messages from the newsgroup 32513as you are quitting Alpine or opening a new folder. 32514 32515<P> 32516This feature is useful if you typically read all the interesting messages 32517in a newsgroup each time you open it. This feature saves you from 32518having to delete each message in a newsgroup as you read it or from 32519selecting all the messages and doing an 32520<A HREF="h_config_enable_agg_ops">aggregate delete</A> before you 32521move on to the next folder or newsgroup. 32522 32523<P> 32524<UL> 32525<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 32526</UL><P> 32527<End of help on this topic> 32528</BODY> 32529</HTML> 32530====== h_config_next_thrd_wo_confirm ===== 32531<HTML> 32532<HEAD> 32533<TITLE>FEATURE: <!--#echo var="FEAT_next-thread-without-confirm"--></TITLE> 32534</HEAD> 32535<BODY> 32536<H1>FEATURE: <!--#echo var="FEAT_next-thread-without-confirm"--></H1> 32537 32538This feature controls an aspect of Alpine's Next and Prev commands in 32539the case where you are using one of the 32540"separate-index-screen" styles for the configuration option 32541<A HREF="h_config_thread_index_style">"<!--#echo var="VAR_threading-index-style"-->"</A> 32542and currently have the folder sorted by a Threaded or OrderedSubject sort. 32543When you are Viewing a particular thread you have a 32544MESSAGE INDEX of only the messages in that thread. 32545If you press the Next command with the last message in the thread highlighted 32546you will normally be asked if you want to "View next thread?", 32547assuming there is a next thread to view. 32548If this feature is set it will be assumed that you always want to view the 32549next thread and you won't be asked to confirm that. 32550Similarly, if the first message of the thread is highlighted and you 32551press the Prev command, this feature will prevent the question 32552"View previous thread". 32553<P> 32554This feature only has an effect in the MESSAGE INDEX screen. 32555If you then view a particular message from that screen and press the 32556Next command, you will be sent to the next thread without being asked, 32557independent of the setting of this feature. 32558<P> 32559The feature 32560<A HREF="h_config_auto_open_unread">"<!--#echo var="FEAT_auto-open-next-unread"-->"</A> also has some similar effects. 32561<P> 32562<End of help on this topic> 32563</BODY> 32564</HTML> 32565====== h_config_kw_braces ===== 32566<HTML> 32567<HEAD> 32568<TITLE>OPTION: <!--#echo var="VAR_keyword-surrounding-chars"--></TITLE> 32569</HEAD> 32570<BODY> 32571<H1>OPTION: <!--#echo var="VAR_keyword-surrounding-chars"--></H1> 32572 32573This option controls a minor aspect of Alpine's MESSAGE INDEX and MESSAGE 32574TEXT screens. 32575If you have modified the 32576"<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" option 32577so that either the "SUBJKEY" or "SUBJKEYINIT" tokens 32578are used to display keywords or their initials along with the Subject; then 32579this option may be used to modify the resulting display slightly. 32580By default, the keywords or initials displayed for these tokens will be 32581surrounded with curly braces ({ and }) and a trailing space. 32582For example, if keywords "Work" and "Now" are set for 32583a message, the "SUBJKEY" token will normally look like 32584<P> 32585<CENTER><SAMP>{Work Now} actual subject</SAMP></CENTER> 32586<P> 32587and the SUBJKEYINIT token would look like 32588<P> 32589<CENTER><SAMP>{WN} actual subject</SAMP></CENTER> 32590<P> 32591The default character before the keywords is the left brace ({) and the 32592default after the keywords is the right brace followed by a space (} ). 32593<P> 32594This option allows you to change that. 32595You should set it to two values separated by a space. 32596The values may be quoted if they include space characters. 32597So, for example, the default value could be specified explicitly by setting this 32598option to 32599<P> 32600<CENTER><SAMP><!--#echo var="VAR_keyword-surrounding-chars"-->="{" "} "</SAMP></CENTER> 32601<P> 32602The first part wouldn't need to be quoted (but it doesn't hurt). 32603The second part does need the quotes because it includes a space character. 32604If you wanted to change the braces to brackets you could use 32605<P> 32606<CENTER><SAMP><!--#echo var="VAR_keyword-surrounding-chars"-->="[" "] "</SAMP></CENTER> 32607<P> 32608Inside the quotes you can use backslash quote to mean quote, so 32609<P> 32610<CENTER><SAMP><!--#echo var="VAR_keyword-surrounding-chars"-->="\"" "\" "</SAMP></CENTER> 32611<P> 32612would produce 32613<P> 32614<CENTER><SAMP>"Work Now" actual subject</SAMP></CENTER> 32615<P> 32616It is also possible to color keywords in the index using the 32617Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>). 32618<P> 32619It is not possible to change the fact that a space character is used to 32620separate the keywords if more than one keyword is set for a message. 32621It is also not possible to change the fact that there are no separators 32622between the keyword initials if more than one keyword is set. 32623<P> 32624<End of help on this topic> 32625</BODY> 32626</HTML> 32627====== h_config_opening_sep ===== 32628<HTML> 32629<HEAD> 32630<TITLE>OPTION: <!--#echo var="VAR_opening-text-separator-chars"--></TITLE> 32631</HEAD> 32632<BODY> 32633<H1>OPTION: <!--#echo var="VAR_opening-text-separator-chars"--></H1> 32634 32635This option controls a minor aspect of Alpine's MESSAGE INDEX screen. 32636With some setups the text of the subject is followed 32637by the opening text of the message if there is any room available in the index line. 32638If you have configured your 32639<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option 32640to include one of the Subject tokens that causes this behavior 32641(SUBJECTTEXT, SUBJKEYTEXT, or SUBJKEYINITTEXT), then this option may be used 32642to modify what is displayed slightly. 32643By default, the Subject is separated from the opening text of the message by 32644the three characters space dash space; 32645<P> 32646<CENTER><SAMP>" - "</SAMP></CENTER> 32647<P> 32648Use this option to set it to something different. 32649The value must be quoted if it includes any space characters. 32650For example, the default value could be specified explicitly by setting this 32651option to 32652<P> 32653<CENTER><SAMP><!--#echo var="VAR_opening-text-separator-chars"-->=" - "</SAMP></CENTER> 32654<P> 32655<End of help on this topic> 32656</BODY> 32657</HTML> 32658====== h_config_select_wo_confirm ===== 32659<HTML> 32660<HEAD> 32661<TITLE>FEATURE: <!--#echo var="FEAT_select-without-confirm"--></TITLE> 32662</HEAD> 32663<BODY> 32664<H1>FEATURE: <!--#echo var="FEAT_select-without-confirm"--></H1> 32665 32666This feature controls an aspect of Alpine's Save, Export, and Goto commands. 32667These commands all take text input to specify the name of the folder or 32668file to be used, but allow you to press ^T for a list of possible names. 32669If set, the selected name will be used immediately, without further 32670opportunity to confirm or edit the name. 32671<P> 32672Some related help topics are 32673<UL> 32674<LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A> 32675<LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>, 32676<LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>, 32677<LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>. 32678<LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>, and 32679<LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>. 32680</UL> 32681<P> 32682<End of help on this topic> 32683</BODY> 32684</HTML> 32685====== h_config_save_part_wo_confirm ===== 32686<HTML> 32687<HEAD> 32688<TITLE>FEATURE: <!--#echo var="FEAT_save-partial-msg-without-confirm"--></TITLE> 32689</HEAD> 32690<BODY> 32691<H1>FEATURE: <!--#echo var="FEAT_save-partial-msg-without-confirm"--></H1> 32692 32693This feature controls an aspect of Alpine's Save command. 32694By default, when you Save a message that has some deleted parts, you will 32695be asked to confirm that you want to Save with a prompt that looks like: 32696<P> 32697<CENTER><SAMP>Saved copy will NOT include entire message! Continue?</SAMP></CENTER> 32698<P> 32699If this feature is set, you will not be asked. 32700<P> 32701<End of help on this topic> 32702</BODY> 32703</HTML> 32704====== h_config_use_resentto ===== 32705<HTML> 32706<HEAD> 32707<TITLE>FEATURE: <!--#echo var="FEAT_use-resent-to-in-rules"--></TITLE> 32708</HEAD> 32709<BODY> 32710<H1>FEATURE: <!--#echo var="FEAT_use-resent-to-in-rules"--></H1> 32711 32712This feature is turned off by default because turning it on causes problems 32713with some deficient IMAP servers. 32714In Alpine <A HREF="h_mainhelp_filtering">Filters</A> and other types of Rules, if the 32715<A HREF="h_rule_patterns">Pattern</A> 32716contains a To header pattern and this feature is turned on, 32717then a check is made in the message to see 32718if a Resent-To header is present, and that is used instead of the To header. 32719If this feature is not turned on, then the regular To header will always 32720be used. 32721 32722<P> 32723<End of help on this topic> 32724</BODY> 32725</HTML> 32726====== h_config_use_reg_start_for_stayopen ===== 32727<HTML> 32728<HEAD> 32729<TITLE>FEATURE: <!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></TITLE> 32730</HEAD> 32731<BODY> 32732<H1>FEATURE: <!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></H1> 32733 32734This feature affects which message is selected as the current message 32735when you enter a 32736<A HREF="h_config_permlocked">Stay Open</A> folder. 32737<P> 32738Normally, the starting position for an incoming folder (which most Stay Open 32739folders will likely be) is controlled by the 32740<A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A>. 32741However, if a folder is a Stay Open folder, when you re-enter the folder 32742after the first time the current message will be the same as it was when 32743you left the folder. 32744An exception is made if you use the TAB command to get to the folder. 32745In that case, the message number will be incremented by one from what it 32746was when you left the folder. 32747<P> 32748The above special behavior is thought to be useful. 32749However, it is special and different from what you might at first expect. 32750If this feature is set, then Stay Open folders will not be treated specially 32751as far as the startup rule is concerned. 32752 32753<P> 32754<End of help on this topic> 32755</BODY> 32756</HTML> 32757====== h_config_use_current_dir ===== 32758<HTML> 32759<HEAD> 32760<TITLE>FEATURE: <!--#echo var="FEAT_use-current-dir"--></TITLE> 32761</HEAD> 32762<BODY> 32763<H1>FEATURE: <!--#echo var="FEAT_use-current-dir"--></H1> 32764 32765This feature controls an aspect of several commands. 32766If set, your "current working directory" 32767<!--chtml if pinemode="running"--> 32768(which, at least for your current Alpine "session," 32769is "<!--#echo var="CURRENT_DIR"-->") 32770<!--chtml endif--> 32771will be used instead of your home directory 32772<!--chtml if pinemode="running"--> 32773(which, in the present configuration of your system, is 32774 "<!--#echo var="HOME_DIR"-->") 32775<!--chtml endif--> 32776for all of the following operations:<UL> 32777 <LI> Export in the MESSAGE INDEX and MESSAGE TEXT screens 32778 <LI> Attachment Save in the MESSAGE TEXT and ATTACHMENT TEXT screens 32779 <LI> <!--chtml if pinemode="function_key"-->F4 32780 <!--chtml else-->Ctrl-R 32781 <!--chtml endif--> file inclusion in the COMPOSER 32782 <LI> <!--chtml if pinemode="function_key"-->F5 32783 <!--chtml else-->Ctrl-J 32784 <!--chtml endif--> file attachment in the COMPOSER 32785</UL> 32786<!--chtml if pinemode="os_windows"--> 32787<P> 32788If you are starting PC-Alpine from a desktop icon or the Start menu, 32789you can set the "current drive" 32790by specifying it in the "Start in:" 32791box found in the Shortcut tab of the Properties. 32792<!--chtml endif--> 32793<P> 32794<UL> 32795<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 32796</UL> 32797 32798<P> 32799<End of help on this topic> 32800</BODY> 32801</HTML> 32802====== h_config_save_wont_delete ===== 32803<HTML> 32804<HEAD> 32805<TITLE>FEATURE: <!--#echo var="FEAT_save-will-not-delete"--></TITLE> 32806</HEAD> 32807<BODY> 32808<H1>FEATURE: <!--#echo var="FEAT_save-will-not-delete"--></H1> 32809 32810This feature controls one aspect of the Save command. If set, Save will 32811not mark the message "deleted" (its default behavior) after 32812it has been copied to the designated folder. 32813 32814<P> 32815<End of help on this topic> 32816</BODY> 32817</HTML> 32818====== h_config_use_boring_spinner ===== 32819<HTML> 32820<HEAD> 32821<TITLE>FEATURE: <!--#echo var="FEAT_busy-cue-spinner-only"--></TITLE> 32822</HEAD> 32823<BODY> 32824<H1>FEATURE: <!--#echo var="FEAT_busy-cue-spinner-only"--></H1> 32825 32826When Alpine is delayed for some reason it usually shows that 32827something is happening with a small animated display in the status 32828message line near the bottom of the screen. 32829Setting this feature will cause that animation to be the same 32830each time instead of having Alpine choose a random animation. 32831You may turn the animation off altogether by setting the 32832<A HREF="h_config_active_msg_interval"><!--#echo var="VAR_busy-cue-rate"--></A> 32833option to zero. 32834 32835<P> 32836<End of help on this topic> 32837</BODY> 32838</HTML> 32839====== h_config_unsel_wont_advance ===== 32840<HTML> 32841<HEAD> 32842<TITLE>FEATURE: <!--#echo var="FEAT_unselect-will-not-advance"--></TITLE> 32843</HEAD> 32844<BODY> 32845<H1>FEATURE: <!--#echo var="FEAT_unselect-will-not-advance"--></H1> 32846 32847This feature controls one aspect of the Unselect Current message command. 32848Normally, when the Unselect current message command (:) is typed when the 32849current message is selected, the message will be unselected and the next 32850message will become the current message. 32851If this feature is set, the cursor will not advance to the next message. 32852Instead, the current message will remain the current message after 32853unselecting. 32854 32855<P> 32856<End of help on this topic> 32857</BODY> 32858</HTML> 32859====== h_config_prune_uses_iso ===== 32860<HTML> 32861<HEAD> 32862<TITLE>FEATURE: <!--#echo var="FEAT_prune-uses-yyyy-mm"--></TITLE> 32863</HEAD> 32864<BODY> 32865<H1>FEATURE: <!--#echo var="FEAT_prune-uses-yyyy-mm"--></H1> 32866 32867By default, Alpine asks monthly whether or not you would like to rename 32868some folders to a new name containing the date. 32869It also asks whether or not you would like to delete some old folders. 32870See the <A HREF="h_config_pruning_rule"><!--#echo var="VAR_pruning-rule"--></A> option for an 32871explanation. 32872 32873<P> 32874By default, the name used when renaming a folder looks like 32875<P> 32876<CENTER><SAMP><foldername>-<month>-<year></SAMP></CENTER> 32877<P> 32878For example, the first time you run Alpine in May of 2004, 32879the folder "sent-mail" might be renamed to 32880<P> 32881<CENTER><SAMP>sent-mail-apr-2004</SAMP></CENTER> 32882<P> 32883If this feature is set, the name used will be of the form 32884<P> 32885<CENTER><SAMP><foldername>-<yyyy>-<mm></SAMP></CENTER> 32886<P> 32887where "yyyy" is the year and "mm" is the two-digit 32888month (01, 02, ..., 12). 32889For the April, 2004 example above, it would instead be 32890<P> 32891<CENTER><SAMP>sent-mail-2004-04</SAMP></CENTER> 32892<P> 32893because April is the 4th month of the year. 32894A reason you might want to set this feature is so that the folders 32895will sort in chronological order. 32896 32897<P> 32898<End of help on this topic> 32899</BODY> 32900</HTML> 32901====== h_config_save_advances ===== 32902<HTML> 32903<HEAD> 32904<TITLE>FEATURE: <!--#echo var="FEAT_save-will-advance"--></TITLE> 32905</HEAD> 32906<BODY> 32907<H1>FEATURE: <!--#echo var="FEAT_save-will-advance"--></H1> 32908 32909This feature controls one aspect of the Save command. If set, Save will 32910(in addition to copying the current message to the designated folder) also 32911advance to the next message. 32912 32913<P> 32914<End of help on this topic> 32915</BODY> 32916</HTML> 32917====== h_config_force_arrow ===== 32918<HTML> 32919<HEAD> 32920<TITLE>FEATURE: <!--#echo var="FEAT_force-arrow-cursor"--></TITLE> 32921</HEAD> 32922<BODY> 32923<H1>FEATURE: <!--#echo var="FEAT_force-arrow-cursor"--></H1> 32924 32925This feature affects Alpine's MESSAGE INDEX display routine. 32926If set, the normal inverse-video cursor will be 32927replaced by a simple "arrow" cursor, which normally occupies the 32928second column of the index display. 32929<P> 32930This is the same index cursor you get if you turn on 32931<A HREF="h_config_force_low_speed"><!--#echo var="FEAT_assume-slow-link"--></A>, but the index 32932line coloring will still be present if this feature is turned on and 32933<!--#echo var="FEAT_assume-slow-link"--> is off. 32934<P> 32935An alternative version of the Arrow cursor is available by including the 32936<A HREF="h_config_index_arrow_color">ARROW</A> 32937token in the 32938<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option. 32939<P> 32940It ought to be the case that this feature also affects the ATTACHMENT INDEX, 32941but that is not implemented. 32942 32943<P> 32944<End of help on this topic> 32945</BODY> 32946</HTML> 32947====== h_config_ignore_size ===== 32948<HTML> 32949<HEAD> 32950<TITLE>FEATURE: <!--#echo var="FEAT_ignore-size-changes"--></TITLE> 32951</HEAD> 32952<BODY> 32953<H1>FEATURE: <!--#echo var="FEAT_ignore-size-changes"--></H1> 32954 32955When you have an account residing in an IMAP server, Alpine records the 32956size of each message as reported by the server. However, when Alpine saves 32957a message in such IMAP server, Alpine will compute the size of the message 32958independently, from the data it received. If these two numbers do not 32959match for a message, Alpine asks you if you still want to take the risk of 32960saving such message, since data corruption or loss of data could result 32961from this save. 32962 32963<P> 32964Sometimes the root of this problem is that the IMAP server does not 32965compute sizes correctly, and there will not be loss of information when 32966saving such message. Enabling this feature will make Alpine ignore such 32967error and continue saving the message without producing any warnings or 32968ever stopping the process, as if there had not been any error. This option 32969applies to all IMAP servers that you use, so if you enable this feature, 32970size discrepancy warnings will not be given for any IMAP server you 32971connect to. 32972 32973<P> 32974Example of a server where you could reproduce this problem is the Gmail 32975IMAP server. Another example can be found in some versions of the Exchange 32976server. 32977 32978<P> 32979It is recommended that this feature be disabled most of the time and only 32980enabled when you find a server which you can determine that has the above 32981mentioned defect, but be disabled again after making the save operation 32982succeed. 32983 32984<P> 32985<End of help on this topic> 32986</BODY> 32987</HTML> 32988====== h_config_force_low_speed ===== 32989<HTML> 32990<HEAD> 32991<TITLE>FEATURE: <!--#echo var="FEAT_assume-slow-link"--></TITLE> 32992</HEAD> 32993<BODY> 32994<H1>FEATURE: <!--#echo var="FEAT_assume-slow-link"--></H1> 32995 32996UNIX Alpine only. 32997<P> 32998This feature affects Alpine's display routines. If set, the normal 32999inverse-video cursor (used to highlight the current item in a list) will be 33000replaced by an "arrow" cursor and other 33001screen update optimizations for 33002low-speed links (e.g. 2400 bps dialup connections) will be activated. 33003One of the optimizations is that colored index lines (set up with Indexcolor 33004Rules) will not be colored. 33005If you are just turning this feature on because you like using 33006the "arrow" cursor you may have an arrow cursor with index line 33007coloring by turning this feature off and the 33008<A HREF="h_config_force_arrow"><!--#echo var="FEAT_force-arrow-cursor"--></A> on. 33009 33010<P> 33011<End of help on this topic> 33012</BODY> 33013</HTML> 33014====== h_config_show_delay_cue ===== 33015<HTML> 33016<HEAD> 33017<TITLE>FEATURE: <!--#echo var="FEAT_enable-mail-check-cue"--></TITLE> 33018</HEAD> 33019<BODY> 33020<H1>FEATURE: <!--#echo var="FEAT_enable-mail-check-cue"--></H1> 33021 33022If set, this feature will cause an asterisk to appear in the upper 33023left-hand corner of the screen whenever Alpine checks for new mail. 33024Two asterisks whenever Alpine saves (checkpoints) the state of the current 33025mailbox to disk. 33026 33027<!--chtml if pinemode="os_windows"--> 33028<P> 33029In addition, PC-Alpine will display a less-than symbol, '<', when 33030it is trying to open a network connection (e.g, to open your INBOX 33031on an IMAP 33032server) or read from the network connection. A greater-than symbol, 33033will be displayed when PC-Alpine is trying to write to the network 33034connection (e.g, sending a command to your IMAP server). 33035<!--chtml endif--> 33036 33037<P> 33038<End of help on this topic> 33039</BODY> 33040</HTML> 33041====== h_config_color_style ===== 33042<HTML> 33043<HEAD> 33044<TITLE>OPTION: Color Style</TITLE> 33045</HEAD> 33046<BODY> 33047<H1>OPTION: Color Style</H1> 33048 33049UNIX Alpine only. 33050<P> 33051If the terminal or terminal emulator you are using is capable of displaying 33052colors, this option controls whether or not color will be used in Alpine. 33053If you turn color on and things are set up correctly, 33054you should see color appear on the screen immediately. 33055Modern terminal emulators are usually capable of displaying colors. 33056<P> 33057The available options include: 33058<P> 33059 33060<DL> 33061<DT>no-color</DT> 33062<DD>Don't use color. 33063</DD> 33064 33065<DT>use-termdef</DT> 33066<DD>In order to decide if your terminal is capable of color, Alpine looks in 33067the terminal capabilities database, TERMINFO or TERMCAP, depending on 33068how Alpine was compiled. 33069This is a good option to choose if you switch between a color and a non-color 33070terminal with the same Alpine configuration. 33071Alpine will know to use color on the color terminal because it is described 33072in the termcap entry, and Alpine will know to use black and white on the 33073non-color terminal. 33074The Alpine Technical Notes, distributed with the source code of Alpine 33075have more information on configuring a TERMCAP or TERMINFO 33076entry for color Alpine. 33077This is usually something a system administrator does. 33078</DD> 33079 33080<DT>force-ansi-8color</DT> 33081<DD>This is probably the setting that most people should use. 33082Because setting up a termcap entry is confusing and because the 33083terminal capabilities database is often not correctly configured for color, 33084this choice and the next may be easier for you to use. 33085If your terminal emulator responds to ANSI color escape sequences, which 33086many do, this option will cause Alpine to believe your terminal will respond 33087to the escape sequences that produce eight different foreground and background 33088colors. 33089The escape sequences used to set the foreground colors are 33090 33091 <P><CENTER>ESC [ 3 <color_number> m</CENTER><P> 33092 33093where the color_number is an ASCII digit between 0 and 7. 33094The numbers 0 through 7 should correspond to the colors black, red, green, 33095yellow, blue, magenta, cyan, and white. 33096Some terminal emulators use a pre-ANSI scheme that swaps 33097the colors blue and red and the colors yellow and cyan. 33098This will cause the default colors to be different, but other than that 33099things should work fine. 33100There is also a 9th color available, the last one shown, which is the default 33101color from the terminal emulator. 33102When used as a background color some people refer to this color as 33103"transparent", which is why the letters "TRAN" are 33104shown in the color swatch of the SETUP COLOR screen. 33105The foreground transparent color is shown as 33106the color of the "TRAN" text. 33107(The transparent color will not work correctly in a PC-Alpine configuration.) 33108The escape sequences used to set the background colors are the same 33109as for the foreground colors except a "4" replaces the "3". 33110The escape sequences for foreground and background default colors (transparent) 33111are 39m and 49m. 33112<P> 33113Note: With the Tera Term terminal emulator this setting works well. 33114You should also have the Tera Term "Full color" option turned OFF. 33115You may find the "Full color" option in Tera Term's "Setup" 33116menu, in the "Window" submenu. 33117</DD> 33118 33119<DT>force-ansi-16color</DT> 33120<DD>Many terminal emulators know about the same eight colors above 33121plus eight more. 33122This option attempts to use all 16 colors. 33123The same escape sequences as for the eight-color terminal are used 33124for the first eight colors. 33125The escape sequences used to set foreground colors 8-15 are the same as 33126for 0-7 except the "3" is replaced with a "9". 33127The background color sequences for colors 8-15 are the same as for 0-7 33128except the "4" is replaced with "10". 33129You can tell if the 16 colors are working by turning on this option 33130and then going into one of the color configuration screens, for example, 33131the configuration screen for Normal Color. 33132If you see 16 different colors to select from (plus a 17th for 33133the transparent color), it's working. 33134</DD> 33135 33136<DT>force-xterm-256color</DT> 33137<DD>Some versions of xterm (and some other terminal emulators) 33138have support for 256 colors. 33139The escape sequences used to set the foreground colors are 33140 33141 <P><CENTER>ESC [ 38 ; 5 ; <color_number> m</CENTER><P> 33142 33143where the color_number is an ASCII digit between 0 and 255. 33144Background colors are the same with the 38 replaced with a 48. 33145The numbers 0 through 15 are probably similar to the 16 color version 33146above, then comes a 6x6x6 color cube, followed by 24 colors of gray. 33147The terminal default (transparent) color is the 257th color at the bottom. 33148Some terminal emulators will misinterpret these escape sequences causing 33149the terminal to blink or overstrike characters or to do something else 33150undesirable. 33151<P> 33152The PuTTY terminal emulator has an option called "Allow terminal to 33153use xterm 256-colour mode" which allows PuTTY to work well with 33154this 256-color setting. 33155 33156</DD> 33157</DL> 33158 33159<P> 33160The normal default is "no-color". 33161<P> 33162 33163Once you've turned on color you may set the 33164colors of many objects on the screen individually. 33165For example, you may add colors to the status letters on the MESSAGE 33166INDEX page. 33167Most categories of color that Alpine supports are configurable here. 33168For example, "Normal Color" 33169is the color used to display most of the text in Alpine, and 33170"Reverse Color" is used to display highlighted text, such as the 33171current message in the MESSAGE INDEX. 33172<P> 33173Lines in the MESSAGE INDEX may also be colored. 33174Use Setup Rules to get to the Indexcolor configuration screen. 33175<P> 33176 33177<UL> 33178<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 33179</UL><P> 33180<End of help on this topic> 33181</BODY> 33182</HTML> 33183====== h_config_disable_index_locale_dates ===== 33184<HTML> 33185<HEAD> 33186<TITLE>FEATURE: <!--#echo var="FEAT_disable-index-locale-dates"--></TITLE> 33187</HEAD> 33188<BODY> 33189<H1>FEATURE: <!--#echo var="FEAT_disable-index-locale-dates"--></H1> 33190 33191This feature affects the display of dates in the MESSAGE INDEX. 33192Normally an attempt is made to localize the dates 33193used in the MESSAGE INDEX display to your locale. 33194This is controlled with the 33195LC_TIME locale setting on a UNIX system. 33196On Windows the Regional Options control panel may be used to set the date format. 33197At the programming level, Alpine is using the strftime routine 33198to print the parts of a date. 33199<P> 33200If this feature is set, dates are displayed in English and 33201with the conventions of the United States. 33202<P> 33203 33204<UL> 33205<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 33206</UL><P> 33207<End of help on this topic> 33208</BODY> 33209</HTML> 33210====== h_config_auto_open_unread ===== 33211<HTML> 33212<HEAD> 33213<TITLE>FEATURE: <!--#echo var="FEAT_auto-open-next-unread"--></TITLE> 33214</HEAD> 33215<BODY> 33216<H1>FEATURE: <!--#echo var="FEAT_auto-open-next-unread"--></H1> 33217 33218This feature controls the behavior of the TAB key when traversing folders 33219in the optional 33220<A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A> 33221collection or in optional <!--#echo var="VAR_news-collections"-->. 33222<P> 33223When the TAB 33224(<A HREF="h_common_nextnew">NextNew</A>) 33225key is pressed, and there 33226are no more unseen messages in the current (incoming message or news) 33227folder, Alpine will search the list of folders in the current collection for 33228one containing New or Recent (new since the last time the folder was 33229opened) messages. 33230This behavior may be modified slightly with the 33231<A HREF="h_config_tab_uses_unseen">"<!--#echo var="FEAT_tab-uses-unseen-for-next-folder"-->"</A> 33232feature that causes Alpine to look for Unseen messages instead of Recent 33233messages. 33234Normally, when such a folder is found, Alpine will ask 33235whether you wish to open the folder. If this feature is set, Alpine will 33236automatically open the folder without prompting. 33237<P> 33238This feature also affects some other similar situations. 33239If you have a 33240<A HREF="h_config_thread_index_style"><!--#echo var="VAR_threading-index-style"--></A> 33241that is equal to one of the "separate-" values, and you are 33242viewing a thread; then when you type the NextNew command and are at the 33243end of the current thread you will automatically go to the next thread 33244if this feature is set. 33245By default, you would be asked if you want to view the next thread. 33246You will also be asked at times whether or not you want to view the next 33247thread after you delete the last message in the thread. 33248Setting this feature will also cause that question to be skipped. 33249<P> 33250 33251<UL> 33252<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 33253</UL><P> 33254<End of help on this topic> 33255</BODY> 33256</HTML> 33257====== h_config_auto_include_reply ===== 33258<HTML> 33259<HEAD> 33260<TITLE>FEATURE: <!--#echo var="FEAT_include-text-in-reply"--></TITLE> 33261</HEAD> 33262<BODY> 33263<H1>FEATURE: <!--#echo var="FEAT_include-text-in-reply"--></H1> 33264 33265This feature controls an aspect of Alpine's Reply command. Normally, Alpine 33266will ask whether you wish to include the original message in your reply. 33267If this feature is set and the feature 33268<A HREF="h_config_prefix_editing">"<!--#echo var="FEAT_enable-reply-indent-string-editing"-->"</A> 33269is <EM>not</EM> set, then the original message will be included in the reply 33270automatically, without prompting. 33271<P> 33272<End of help on this topic> 33273</BODY> 33274</HTML> 33275====== h_config_select_in_bold ===== 33276<HTML> 33277<HEAD> 33278<TITLE>FEATURE: <!--#echo var="FEAT_show-selected-in-boldface"--></TITLE> 33279</HEAD> 33280<BODY> 33281<H1>FEATURE: <!--#echo var="FEAT_show-selected-in-boldface"--></H1> 33282 33283This feature controls an aspect of Alpine's 33284<A HREF="h_config_enable_agg_ops">"aggregate operation"</A> 33285commands; in 33286particular, the Select and WhereIs commands. Select and WhereIs (with the 33287^X subcommand) will search the current folder for messages meeting a 33288specified criteria, and "tag" the resulting messages with an 33289"X" in the 33290first column of the applicable lines in the MESSAGE INDEX. If this feature 33291is set, instead of using the "X" to denote a selected message, 33292Alpine will 33293attempt to display those index lines in boldface. Whether this is 33294preferable to the "X" will depend on personal taste and the type of 33295terminal being used. 33296<P> 33297<UL> 33298<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 33299</UL><P> 33300<End of help on this topic> 33301</BODY> 33302</HTML> 33303====== h_config_alt_auth ===== 33304<HTML> 33305<HEAD> 33306<TITLE>FEATURE: <!--#echo var="FEAT_try-alternative-authentication-driver-first"--></TITLE> 33307</HEAD> 33308<BODY> 33309<H1>FEATURE: <!--#echo var="FEAT_try-alternative-authentication-driver-first"--></H1> 33310 33311This feature affects how Alpine connects to IMAP servers. 33312Its utility has largely been overtaken by events, 33313but it may still be useful in some circumstances. 33314If you only connect to modern IMAP servers that support 33315"STARTTLS" you can ignore this feature. 33316 33317<P> 33318Details: 33319 33320<P> 33321By default, Alpine will attempt to connect to an IMAP server on the 33322normal IMAP service port (143), and if the server offers "Transport Layer 33323Security" (STARTTLS) and Alpine has been compiled with encryption capability, 33324then a secure (encrypted) session will be negotiated. 33325 33326<P> 33327With this feature enabled, before connecting on the normal IMAP port, Alpine 33328will first attempt to connect to an alternate IMAP service port (993) used 33329specifically for encrypted IMAP sessions via the Secure Sockets Layer 33330(SSL) or Transport Layer Security (TLS) method. 33331If the SSL attempt fails, Alpine will then try the default 33332behavior described in the previous paragraph. 33333 33334<P> 33335STARTTLS negotiation on the normal port is preferred, and supersedes the use of 33336SSL on port 993, but older servers may not provide STARTTLS support. 33337This feature may be convenient when accessing IMAP servers that do not support 33338STARTTLS, but do support SSL or TLS connections on port 993. 33339However, it is important to understand that with this feature enabled, 33340Alpine will <EM>attempt</EM> to make a secure connection if that is possible, 33341but it will proceed to make an insecure connection if that is the only 33342option offered by the server, or if the Alpine in question has been built 33343without encryption capability. 33344 33345<P> 33346Note that this feature specifies a per-user (or system-wide) default 33347behavior, but host/folder specification flags may be used to control the 33348behavior of any specific connection. 33349This feature interacts with some of 33350the possible host/folder path specification flags as follows: 33351 33352<P> 33353The <SAMP>/starttls</SAMP> host flag, for example, 33354 33355<P> 33356<CENTER><SAMP>{foo.example.com/starttls}INBOX</SAMP></CENTER> 33357<P> 33358will over-ride this feature for the specified host by bypassing the 33359SSL or TLS connection attempt. 33360Moreover, with <SAMP>/starttls</SAMP> specified, 33361the connection attempt will fail if the 33362service on port 143 does not offer TLS support. 33363 33364<P> 33365The <SAMP>/ssl</SAMP> host flag, for example, 33366 33367<P> 33368<CENTER><SAMP>{foo.example.com/ssl}INBOX</SAMP></CENTER> 33369<P> 33370will insist on an SSL or TLS connection for the specified host, 33371and will fail if the SSL or TLS service on port 993 is not available. 33372Alpine will not subsequently retry a connection 33373on port 143 if <SAMP>/ssl</SAMP> is specified. 33374 33375<P> 33376<UL> 33377<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 33378</UL><P> 33379<End of help on this topic> 33380</BODY> 33381</HTML> 33382====== h_config_file_dir ====== 33383<HTML> 33384<HEAD> 33385<TITLE>OPTION: File Directory</TITLE> 33386</HEAD> 33387<BODY> 33388<H1>OPTION: File Directory</H1> 33389 33390PC-Alpine only. 33391<P> 33392This value affects the Composer's "^J Attach" command, 33393the Attachment Index Screen's "S Save" command, and the 33394Message Index's "E Export" command. 33395 33396<P> 33397Normally, when a filename is supplied that lacks a leading "path" 33398component, Alpine assumes the file exists in the user's home directory. 33399Under Windows operating systems, this definition isn't always clear. This 33400feature allows you to explicitly set where Alpine should look for files 33401without a leading path. 33402 33403<P> 33404NOTE: this feature's value is ignored if either 33405<A HREF="h_config_use_current_dir"><!--#echo var="FEAT_use-current-dir"--></A> feature 33406is set or the PINERC has a value for the "<!--#echo var="VAR_operating-dir"-->" variable. 33407 33408<P> 33409<UL> 33410<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 33411</UL><P> 33412<End of help on this topic> 33413</BODY> 33414</HTML> 33415====== h_config_quote_all_froms ===== 33416<HTML> 33417<HEAD> 33418<TITLE>FEATURE: <!--#echo var="FEAT_save-will-quote-leading-froms"--></TITLE> 33419</HEAD> 33420<BODY> 33421<H1>FEATURE: <!--#echo var="FEAT_save-will-quote-leading-froms"--></H1> 33422 33423This feature controls an aspect of the Save command (and also the way 33424outgoing messages are saved to an FCC folder). If set, Alpine will add 33425a leading ">" character in front of message lines beginning with "From" 33426when they are saved to another folder, including lines syntactically 33427distinguishable from the type of message separator line commonly used on 33428Unix systems. 33429 33430<P> 33431The default behavior is that a ">" will be prepended only to lines 33432beginning with "From " that might otherwise be confused with a message 33433separator line on Unix systems. If pine is the only mail program you use, 33434this default is reasonable. If another program you use has trouble 33435displaying a message with an unquoted "From " saved by Alpine, you should 33436enable this feature. This feature only applies to the common Unix mailbox 33437format that uses message separator lines beginning with "From ". If 33438Alpine has been configured to use a different mailbox format (possibly 33439incompatible with other mail programs), then this issue does not arise, 33440and the feature is irrelevant. 33441 33442<P> 33443<End of help on this topic> 33444</BODY> 33445</HTML> 33446====== h_config_normal_color ===== 33447<HTML> 33448<HEAD> 33449<TITLE>OPTION: Normal Color</TITLE> 33450</HEAD> 33451<BODY> 33452<H1>OPTION: Normal Color</H1> 33453 33454Sets the color Alpine normally uses. 33455The foreground color is the color of the actual character and the 33456background color is the color of the area behind the character. 33457By default this color is black characters on a white background. 33458<P> 33459<A HREF="h_color_setup">Descriptions of the available commands</A> 33460<P> 33461Look <A HREF="h_edit_nav_cmds">here</A> 33462to see the available Editing and Navigation commands. 33463<P> 33464<End of help on this topic> 33465</BODY> 33466</HTML> 33467====== h_config_reverse_color ===== 33468<HTML> 33469<HEAD> 33470<TITLE>OPTION: Reverse Color</TITLE> 33471</HEAD> 33472<BODY> 33473<H1>OPTION: Reverse Color</H1> 33474 33475Sets the color Alpine uses for reverse video characters. 33476The foreground color is the color of the actual character and the 33477background color is the color of the area behind the character. 33478<P> 33479<A HREF="h_color_setup">Descriptions of the available commands</A> 33480<P> 33481Look <A HREF="h_edit_nav_cmds">here</A> 33482to see the available Editing and Navigation commands. 33483<P> 33484<End of help on this topic> 33485</BODY> 33486</HTML> 33487====== h_config_title_color ===== 33488<HTML> 33489<HEAD> 33490<TITLE>OPTION: Title Color</TITLE> 33491</HEAD> 33492<BODY> 33493<H1>OPTION: Title Color</H1> 33494 33495Sets the color Alpine uses for the titlebar (the top line on the screen). 33496The foreground color is the color of the actual character and the 33497background color is the color of the area behind the character. 33498By default, the Title Color is black characters on a yellow background. 33499<P> 33500The actual titlebar color may be different from the Title Color if 33501the option 33502<A HREF="h_config_titlebar_color_style">"<!--#echo var="VAR_titlebar-color-style"-->"</A> 33503is set to some value other than the default. 33504It may also be different if the current folder is closed and the 33505<A HREF="h_config_titleclosed_color">Title Closed Color</A> 33506color is set to something different from the Title Color. 33507<P> 33508<A HREF="h_color_setup">Descriptions of the available commands</A> 33509<P> 33510Look <A HREF="h_edit_nav_cmds">here</A> 33511to see the available Editing and Navigation commands. 33512<P> 33513<End of help on this topic> 33514</BODY> 33515</HTML> 33516====== h_config_titleclosed_color ===== 33517<HTML> 33518<HEAD> 33519<TITLE>OPTION: Title Closed Color</TITLE> 33520</HEAD> 33521<BODY> 33522<H1>OPTION: Title Closed Color</H1> 33523 33524Sets the color Alpine uses for the titlebar (the top line on the screen) 33525when the current folder is closed. 33526The foreground color is the color of the actual character and the 33527background color is the color of the area behind the character. 33528By default, the Title Color Closed Color is white characters on a red background. 33529<P> 33530By setting this color to something noticeable you will be alerted to the 33531fact that the current folder is closed, perhaps unexpectedly. 33532<P> 33533<End of help on this topic> 33534</BODY> 33535</HTML> 33536====== h_config_status_color ===== 33537<HTML> 33538<HEAD> 33539<TITLE>OPTION: Status Color</TITLE> 33540</HEAD> 33541<BODY> 33542<H1>OPTION: Status Color</H1> 33543 33544Sets the color Alpine uses for status messages written to the message 33545line near the bottom of the screen. 33546The foreground color is the color of the actual character and the 33547background color is the color of the area behind the character. 33548By default, the Status Color is the same as the Reverse Color. 33549<P> 33550<A HREF="h_color_setup">Descriptions of the available commands</A> 33551<P> 33552Look <A HREF="h_edit_nav_cmds">here</A> 33553to see the available Editing and Navigation commands. 33554<P> 33555<End of help on this topic> 33556</BODY> 33557</HTML> 33558====== h_config_index_opening_color ===== 33559<HTML> 33560<HEAD> 33561<TITLE>OPTION: Index Opening Color</TITLE> 33562</HEAD> 33563<BODY> 33564<H1>OPTION: Index Opening Color</H1> 33565 33566With some setups the text of the subject is followed 33567by the opening text of the message if there is any room available in the index line. 33568If you have configured your 33569<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option 33570to include one of the Subject tokens that causes this behavior 33571(SUBJECTTEXT, SUBJKEYTEXT, or SUBJKEYINITTEXT), you may set the color of 33572this opening text with this option. 33573This coloring takes place for all but the current index line, and the Opening 33574Color appears to be in front of any color from an Index Color Rule. 33575<P> 33576By default the Index Opening Color is gray characters on a white background. 33577 33578<P> 33579<A HREF="h_color_setup">Descriptions of the available commands</A> 33580<P> 33581Look <A HREF="h_edit_nav_cmds">here</A> 33582to see the available Editing and Navigation commands. 33583<P> 33584<End of help on this topic> 33585</BODY> 33586</HTML> 33587====== h_config_index_pri_color ===== 33588<HTML> 33589<HEAD> 33590<TITLE>OPTION: Index Priority Symbol Colors</TITLE> 33591</HEAD> 33592<BODY> 33593<H1>OPTION: Index Priority Symbol Colors</H1> 33594 33595The X-Priority header is a non-standard header that is used in a 33596somewhat standard way by many mail programs. 33597Alpine expects the value of this header to be a digit with a value 33598from 1 to 5, with 1 being the highest priority and 5 the lowest priority. 33599Alpine can be made to display an indication of this priority in 33600messages by use of one of the tokens 33601(<A HREF="h_index_tokens">Tokens for Index and Replying</A>) 33602PRIORITY, PRIORITYALPHA, or PRIORITY! in the 33603<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option. 33604 33605<P> 33606You may set the color used to draw these tokens by use of the colors 33607Index High Priority Symbol Color and Index Low Priority Symbol Color. 33608This coloring takes place for all but the current index line, and the Priority 33609Color appears to be in front of any color from an Index Color Rule. 33610If the priority has a value of 1 or 2 the High Priority color will be 33611used, 33612and if the value is 4 or 5 the Low Priority color will be used. 33613<P> 33614If you don't set these colors the index line will be colored in the same color as 33615the bulk of the index line. 33616 33617<P> 33618<A HREF="h_color_setup">Descriptions of the available commands</A> 33619<P> 33620Look <A HREF="h_edit_nav_cmds">here</A> 33621to see the available Editing and Navigation commands. 33622<P> 33623<End of help on this topic> 33624</BODY> 33625</HTML> 33626====== h_config_index_subject_color ===== 33627<HTML> 33628<HEAD> 33629<TITLE>OPTION: Index Subject Color</TITLE> 33630</HEAD> 33631<BODY> 33632<H1>OPTION: Index Subject Color</H1> 33633 33634You may set the color used to draw the Subject part of the index line. 33635This coloring takes place for all but the current index line, and the Subject 33636Color appears to be in front of any color from an Index Color Rule. 33637<P> 33638If you don't set this color it will be colored in the same color as 33639the bulk of the index line. 33640 33641<P> 33642<A HREF="h_color_setup">Descriptions of the available commands</A> 33643<P> 33644Look <A HREF="h_edit_nav_cmds">here</A> 33645to see the available Editing and Navigation commands. 33646<P> 33647<End of help on this topic> 33648</BODY> 33649</HTML> 33650====== h_config_index_from_color ===== 33651<HTML> 33652<HEAD> 33653<TITLE>OPTION: Index From Color</TITLE> 33654</HEAD> 33655<BODY> 33656<H1>OPTION: Index From Color</H1> 33657 33658You may set the color used to draw the From part of the index line. 33659This coloring takes place for all but the current index line, and the From 33660Color appears to be in front of any color from an Index Color Rule. 33661<P> 33662If you don't set this color it will be colored in the same color as 33663the bulk of the index line. 33664 33665<P> 33666<A HREF="h_color_setup">Descriptions of the available commands</A> 33667<P> 33668Look <A HREF="h_edit_nav_cmds">here</A> 33669to see the available Editing and Navigation commands. 33670<P> 33671<End of help on this topic> 33672</BODY> 33673</HTML> 33674====== h_config_index_arrow_color ===== 33675<HTML> 33676<HEAD> 33677<TITLE>OPTION: Index Arrow Color</TITLE> 33678</HEAD> 33679<BODY> 33680<H1>OPTION: Index Arrow Color</H1> 33681 33682If you have configured your 33683<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option 33684to include the "ARROW" token, you may set the color of 33685the arrow displayed with this option. 33686If you don't set the color it will be colored in the same color as 33687the bulk of the index line. 33688 33689<P> 33690<A HREF="h_color_setup">Descriptions of the available commands</A> 33691<P> 33692Look <A HREF="h_edit_nav_cmds">here</A> 33693to see the available Editing and Navigation commands. 33694<P> 33695<End of help on this topic> 33696</BODY> 33697</HTML> 33698====== h_config_index_color ===== 33699<HTML> 33700<HEAD> 33701<TITLE>OPTION: Index Colors</TITLE> 33702</HEAD> 33703<BODY> 33704<H1>OPTION: Index Colors</H1> 33705 33706You may add color to the single character symbols that give the status 33707of each message in the MESSAGE INDEX. 33708By default the characters "+", "*", "D", 33709"A", and "N" show up near the left hand side of the 33710screen depending on whether the message is addressed to you, and whether 33711the message is marked Important, is Deleted, is Answered, or is New. 33712The color for each of those characters may be specified by setting the 33713"Index-to-me" Symbol Color, 33714the "Index-important" Symbol Color, 33715the "Index-deleted" Symbol Color, 33716the "Index-answered" Symbol Color, 33717and the "Index-new" Symbol Color. 33718There are also two other symbol colors called "Index-recent" 33719and "Index-unseen". 33720These two colors will only be used if you have configured your 33721"<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" option 33722to include the "IMAPSTATUS" or "SHORTIMAPSTATUS" token. 33723<P> 33724The default colors for these symbols are: 33725<TABLE> 33726<TR> <TD> Index-to-me </TD> <TD> black on cyan </TD> </TR> 33727<TR> <TD> Index-important </TD> <TD> white on bright red </TD> </TR> 33728<TR> <TD> Index-deleted </TD> <TD> same as Normal Color </TD> </TR> 33729<TR> <TD> Index-answered </TD> <TD> bright red on yellow </TD> </TR> 33730<TR> <TD> Index-new </TD> <TD> white on magenta </TD> </TR> 33731<TR> <TD> Index-recent </TD> <TD> same as Normal Color </TD> </TR> 33732<TR> <TD> Index-unseen </TD> <TD> same as Normal Color </TD> </TR> 33733</TABLE> 33734<P> 33735Besides coloring the message status symbols, you may also color the 33736entire index line. 33737This is done by using the 33738<A HREF="h_rules_incols">SETUP INDEX LINE COLORS</A> screen, which you 33739may get to with the commands <EM>S</EM>etup/<EM>R</EM>ules/<EM>I</EM>ndexcolor. 33740When the entire line is colored that color will be "behind" the 33741status symbol colors talked about in the paragraph above. 33742<P> 33743You may also color 33744<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> 33745in the index using the 33746Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>); 33747the <A HREF="h_config_index_arrow_color">ARROW</A> cursor; 33748the Subject using 33749<A HREF="h_config_index_subject_color">Index Subject Color</A>; 33750the From field using 33751<A HREF="h_config_index_from_color">Index From Color</A>; 33752and the 33753<A HREF="h_config_index_opening_color">Index Opening</A> text. 33754<P> 33755<A HREF="h_color_setup">Descriptions of the available commands</A> 33756<P> 33757Look <A HREF="h_edit_nav_cmds">here</A> 33758to see the available Editing and Navigation commands. 33759<P> 33760<End of help on this topic> 33761</BODY> 33762</HTML> 33763====== h_config_metamsg_color ===== 33764<HTML> 33765<HEAD> 33766<TITLE>OPTION: Meta-Message Color</TITLE> 33767</HEAD> 33768<BODY> 33769<H1>OPTION: Meta-Message Color</H1> 33770 33771Sets the color Alpine uses in the MESSAGE TEXT screen for messages to you 33772that aren't part of the message itself. 33773For example, an attachment that isn't shown might produce a meta 33774message something like: 33775<P> 33776<CENTER><SAMP> [ Part 2, "comment" Text/PLAIN (Name: "file") ]</SAMP></CENTER> 33777<P> 33778If you set the 33779<A HREF="h_config_quote_suppression"><!--#echo var="VAR_quote-suppression-threshold"--></A> 33780option you might see 33781<P> 33782<CENTER><SAMP>[ 12 lines of quoted text hidden from view ]</SAMP></CENTER> 33783<P> 33784Warnings about suspicious looking URLs in HTML will also be colored 33785with this color. 33786<P> 33787The foreground color is the color of the actual character and the 33788background color is the color of the area behind the character. 33789By default, the Meta-Message Color is black characters on a yellow background. 33790<P> 33791<A HREF="h_color_setup">Descriptions of the available commands</A> 33792<P> 33793Look <A HREF="h_edit_nav_cmds">here</A> 33794to see the available Editing and Navigation commands. 33795<P> 33796<End of help on this topic> 33797</BODY> 33798</HTML> 33799====== h_config_keylabel_color ===== 33800<HTML> 33801<HEAD> 33802<TITLE>OPTION: KeyLabel Color</TITLE> 33803</HEAD> 33804<BODY> 33805<H1>OPTION: KeyLabel Color</H1> 33806 33807Sets the color Alpine uses for the labels of the keys in the two-line 33808menu at the bottom of the screen. 33809For example, some of the screens have a "P PrevMsg" command. 33810This option sets the color used when displaying "PrevMsg". 33811The foreground color is the color of the actual character and the 33812background color is the color of the area behind the character. 33813By default, the KeyLabel Color is the same as the Normal Color. 33814<P> 33815WARNING: Some terminal emulators have the property that the screen will scroll 33816down one line whenever a character is written to the character cell in the 33817lower right corner of the screen. 33818Alpine can usually avoid writing a character in that corner of the screen. 33819However, if you have defined a KeyLabel Color then Alpine does have to write 33820a character in that cell in order to color the cell correctly. 33821If you find that your display sometimes scrolls up a line this could be 33822the problem. 33823The most obvious symptom is probably that the titlebar at the top of the 33824screen scrolls off the screen. 33825Try setting KeyLabel Color to Default to see if that fixes the problem. 33826<P> 33827<A HREF="h_color_setup">Descriptions of the available commands</A> 33828<P> 33829Look <A HREF="h_edit_nav_cmds">here</A> 33830to see the available Editing and Navigation commands. 33831<P> 33832<End of help on this topic> 33833</BODY> 33834</HTML> 33835====== h_config_keyname_color ===== 33836<HTML> 33837<HEAD> 33838<TITLE>OPTION: KeyName Color</TITLE> 33839</HEAD> 33840<BODY> 33841<H1>OPTION: KeyName Color</H1> 33842 33843Sets the color Alpine uses for the names of the keys in the two-line 33844menu at the bottom of the screen. 33845For example, some of the screens have a "P PrevMsg" command. 33846This option sets the color used when displaying the "P". 33847The foreground color is the color of the actual character and the 33848background color is the color of the area behind the character. 33849By default, the KeyName Color is the same as the Reverse Color. 33850<P> 33851<A HREF="h_color_setup">Descriptions of the available commands</A> 33852<P> 33853Look <A HREF="h_edit_nav_cmds">here</A> 33854to see the available Editing and Navigation commands. 33855<P> 33856<End of help on this topic> 33857</BODY> 33858</HTML> 33859====== h_config_slctbl_color ===== 33860<HTML> 33861<HEAD> 33862<TITLE>OPTION: Selectable Item Color</TITLE> 33863</HEAD> 33864<BODY> 33865<H1>OPTION: Selectable Item Color</H1> 33866 33867Sets the color Alpine uses for selectable items, such as URLs. 33868The foreground color is the color of the actual character and the 33869background color is the color of the area behind the character. 33870By default, the Selectable Item Color is the same as the Normal Color, 33871except that it is bold. 33872<P> 33873<A HREF="h_color_setup">Descriptions of the available commands</A> 33874<P> 33875Look <A HREF="h_edit_nav_cmds">here</A> 33876to see the available Editing and Navigation commands. 33877<P> 33878<End of help on this topic> 33879</BODY> 33880</HTML> 33881====== h_config_quote_color ===== 33882<HTML> 33883<HEAD> 33884<TITLE>OPTION: Quote Colors</TITLE> 33885</HEAD> 33886<BODY> 33887<H1>OPTION: Quote Colors</H1> 33888 33889Sets the colors Alpine uses for coloring quoted text in the MESSAGE TEXT 33890screen. 33891If a line begins with a > character (or space followed by >) 33892it is considered a quote. 33893That line will be given the Quote1 Color (first level quote). 33894If there is a second level of quoting then the Quote2 Color will be used. 33895Alpine considers there to be a second level of quoting if that first > is 33896followed by another > (or space followed by >). 33897If there are characters other than whitespace and > signs, then it isn't 33898considered another level of quoting. 33899Similarly, if there is a third level of quoting the Quote3 Color will be 33900used. 33901If there are more levels after that the Quote Colors are re-used. 33902If you define all three colors then it would repeat like Color1, Color2, Color3, 33903Color1, Color2, Color3, ... 33904If you only define the first two it would be 33905Color1, Color2, Color1, Color2, ... 33906If you define only the Quote1 Color, then the entire quote would be that 33907color regardless of the quoting levels. 33908By default, the Quote1 Color is black characters on a greenish-blue background; 33909the Quote2 Color is black characters on a dull yellow background; and 33910the Quote3 Color is black characters on a green background. 33911<P> 33912<A HREF="h_color_setup">Descriptions of the available commands</A> 33913<P> 33914Look <A HREF="h_edit_nav_cmds">here</A> 33915to see the available Editing and Navigation commands. 33916<P> 33917<End of help on this topic> 33918</BODY> 33919</HTML> 33920====== h_config_folder_color ===== 33921<HTML> 33922<HEAD> 33923<TITLE>OPTION: Folder Color</TITLE> 33924</HEAD> 33925<BODY> 33926<H1>OPTION: Folder Color</H1> 33927 33928Sets the colors Alpine uses for coloring a folder in the FOLDER LIST 33929screen. By default, the Folder Color is the normal text color. 33930 33931<P> 33932If you set a color for this feature, other than the normal color 33933(the default), or a color for 33934<A HREF="h_config_directory_color">Directory Color</A>, then directories 33935will be colored according to the color specified in the 33936<A HREF="h_config_directory_color">Directory Color</A> option. In this 33937case, the color will be the only indication that the colored name 33938refers to a directory. The normal behavior is that Alpine 33939indicates that a name refers to a directory by appending a 33940separator (like "/" or ".") to the name of 33941the folder. 33942 33943<P> 33944If a folder is a directory, then the folder name will be painted 33945according to the color defined by this variable, and a separator 33946indicator (like "/" or ".") will be added 33947to the name. That 33948indicator will be painted according to the color defined in the 33949<A HREF="h_config_directory_color">Directory Color</A> option. 33950 33951<P> 33952<End of help on this topic> 33953</BODY> 33954</HTML> 33955====== h_config_directory_color ===== 33956<HTML> 33957<HEAD> 33958<TITLE>OPTION: Directory Color</TITLE> 33959</HEAD> 33960<BODY> 33961<H1>OPTION: Directory Color</H1> 33962 33963Sets the colors Alpine uses for coloring a directory in the FOLDER LIST 33964screen. By default, the Folder Color is the normal text color. 33965<P> 33966If you set a color for this feature, other than the normal color 33967(the default), or a color for 33968<A HREF="h_config_folder_color">Folder Color</A>, then folders 33969will be colored according to the color specified in the 33970<A HREF="h_config_folder_color">Folder Color</A> option. In this 33971case, the color will be the only indication that the colored name 33972refers to a directory. The normal behavior is that Alpine 33973indicates that a name refers to a directory by appending a 33974separator (like "/" or ".") to the name of 33975the folder. 33976<P> 33977If a folder is a directory, then the folder name will be painted 33978according to the color defined by the option 33979<A HREF="h_config_folder_color">Folder Color</A>, and the separator 33980indicator (like "/" or ".") will be added 33981after the name. That 33982indicator will be painted according to the color defined in this 33983option. 33984<P> 33985<End of help on this topic> 33986</BODY> 33987</HTML> 33988====== h_config_folder_list_color ===== 33989<HTML> 33990<HEAD> 33991<TITLE>OPTION: Folder-List Color</TITLE> 33992</HEAD> 33993<BODY> 33994<H1>OPTION: Folder-List Color</H1> 33995 33996Sets the colors Alpine uses for coloring normal text in the FOLDER LIST 33997screen. By default, the Folder-List Color is the normal text color. 33998<P> 33999This text refers to the informative text that Alpine displays so you 34000can recognize each collection. The color of the content of each collection 34001is determined by the options <A HREF="h_config_folder_color">Folder Color</A> 34002and <A HREF="h_config_directory_color">Directory Color</A>. 34003<P> 34004Unlike the options 34005<A HREF="h_config_folder_color">Folder Color</A> 34006and <A HREF="h_config_directory_color">Directory Color</A>, configuring 34007this option does not affect the way that Alpine reports folders, 34008directories and folders that are directories. 34009<P> 34010<End of help on this topic> 34011</BODY> 34012</HTML> 34013====== h_config_incunseen_color ===== 34014<HTML> 34015<HEAD> 34016<TITLE>OPTION: Incoming Unseen Color</TITLE> 34017</HEAD> 34018<BODY> 34019<H1>OPTION: Incoming Unseen Color</H1> 34020 34021If the option 34022<A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A> 34023is turned on it is possible to highlight the folders that contain 34024unseen messages by coloring them with this color. 34025By default, this is the same as the Normal Color and no highlighting is done. 34026<P> 34027Usually the "current" folder (the folder the cursor is on) 34028is highlighted using reverse video. 34029If the current folder is colored because it contains unseen messages then 34030the color used to show that it is also the current folder is controlled 34031by the 34032<A HREF="h_config_index_color_style"><!--#echo var="VAR_current-indexline-style"--></A> 34033feature at the top of the SETUP COLOR screen. 34034<P> 34035<A HREF="h_color_setup">Descriptions of the available commands</A> 34036<P> 34037Look <A HREF="h_edit_nav_cmds">here</A> 34038to see the available Editing and Navigation commands. 34039<P> 34040<End of help on this topic> 34041</BODY> 34042</HTML> 34043====== h_config_signature_color ===== 34044<HTML> 34045<HEAD> 34046<TITLE>OPTION: Signature Color</TITLE> 34047</HEAD> 34048<BODY> 34049<H1>OPTION: Signature Color</H1> 34050 34051Sets the color Alpine uses for coloring the signature in the MESSAGE TEXT 34052screen. According to USENET conventions, the signature is defined as the 34053paragraph following the "sigdashes", that is, the special line 34054consisting of the three characters 34055"-- " (i.e., dash, dash, and space). Alpine allows for one 34056empty line right after the sigdashes to be considered as part of the 34057signature. 34058By default, the Signature Color is blue characters on a white background. 34059<P> 34060<A HREF="h_color_setup">Descriptions of the available commands</A> 34061<P> 34062Look <A HREF="h_edit_nav_cmds">here</A> 34063to see the available Editing and Navigation commands. 34064<P> 34065<End of help on this topic> 34066</BODY> 34067</HTML> 34068====== h_config_prompt_color ===== 34069<HTML> 34070<HEAD> 34071<TITLE>OPTION: Prompt Color</TITLE> 34072</HEAD> 34073<BODY> 34074<H1>OPTION: Prompt Color</H1> 34075 34076Sets the color Alpine uses for confirmation prompts and questions that 34077appear in the status line near the bottom of the screen. 34078The foreground color is the color of the actual character and the 34079background color is the color of the area behind the character. 34080By default, the Prompt Color is the same as the Reverse Color. 34081<P> 34082<A HREF="h_color_setup">Descriptions of the available commands</A> 34083<P> 34084Look <A HREF="h_edit_nav_cmds">here</A> 34085to see the available Editing and Navigation commands. 34086<P> 34087<End of help on this topic> 34088</BODY> 34089</HTML> 34090====== h_config_header_general_color ===== 34091<HTML> 34092<HEAD> 34093<TITLE>OPTION: Header General Color</TITLE> 34094</HEAD> 34095<BODY> 34096<H1>OPTION: Header General Color</H1> 34097 34098Sets the color Alpine uses for the headers of a message in the MESSAGE TEXT 34099screen. 34100The foreground color is the color of the actual character and the 34101background color is the color of the area behind the character. 34102By default, this is the same as the Normal Color. 34103<P> 34104It is also possible to set the colors for specific header fields, for 34105example the Subject, using 34106<A HREF="h_config_customhdr_color"><!--#echo var="VAR_viewer-hdr-colors"--></A>. 34107If both a Header General Color and a specific Viewer Header Color are set 34108the specific color will override the general color, as you would expect. 34109<P> 34110<A HREF="h_color_setup">Descriptions of the available commands</A> 34111<P> 34112Look <A HREF="h_edit_nav_cmds">here</A> 34113to see the available Editing and Navigation commands. 34114<P> 34115<End of help on this topic> 34116</BODY> 34117</HTML> 34118====== h_config_incol ===== 34119<HTML> 34120<HEAD> 34121<TITLE>Index Line Color</TITLE> 34122</HEAD> 34123<BODY> 34124<H1>Index Line Color</H1> 34125 34126This option is used to set the color of a line in the index when the 34127message for that line matches the Pattern. 34128This colors the whole index line, except possibly the status letters, 34129which may be colored separately using the 34130<A HREF="h_color_setup">Setup Kolor</A> screen. 34131The foreground color is the color of the actual characters and the 34132background color is the color of the area behind the characters. 34133<P> 34134<A HREF="h_color_setup">Descriptions of the available commands</A> 34135<P> 34136Look <A HREF="h_edit_nav_cmds">here</A> 34137to see the available Editing and Navigation commands. 34138<P> 34139<End of help on this topic> 34140</BODY> 34141</HTML> 34142====== h_config_usetransparent_color ===== 34143<HTML> 34144<HEAD> 34145<TITLE>OPTION: Use Transparent Color</TITLE> 34146</HEAD> 34147<BODY> 34148<H1>OPTION: Use Transparent Color</H1> 34149 34150This is a special color supported by some terminal emulators. 34151It is intended to result in the default foreground or background color 34152from the terminal emulator. 34153This is the color the terminal was displaying characters in before you started Alpine. 34154The reason it is called Transparent is because you could set the foreground color 34155to some specific color, like Red, and then set the background color to the 34156Transparent Color. If it works as expected, the background color from the terminal 34157window in which Alpine is running will show through but with the Red characters 34158in the foreground. 34159<P> 34160<A HREF="h_color_setup">Descriptions of the available commands</A> 34161<P> 34162Look <A HREF="h_edit_nav_cmds">here</A> 34163to see the available Editing and Navigation commands. 34164<P> 34165<End of help on this topic> 34166</BODY> 34167</HTML> 34168====== h_config_usenormal_color ===== 34169<HTML> 34170<HEAD> 34171<TITLE>OPTION: Use Normal Color</TITLE> 34172</HEAD> 34173<BODY> 34174<H1>OPTION: Use Normal Color</H1> 34175 34176When you use this color value, the actual color used will be the same 34177as the corresponding Normal Color. 34178For example if your Normal Color is black on white and you set both 34179the foreground and background colors here to use the Normal Color, you'll 34180get black on white. If you later change the Normal Color to red on blue 34181this color will also change to red on blue. 34182<P> 34183<A HREF="h_color_setup">Descriptions of the available commands</A> 34184<P> 34185Look <A HREF="h_edit_nav_cmds">here</A> 34186to see the available Editing and Navigation commands. 34187<P> 34188<End of help on this topic> 34189</BODY> 34190</HTML> 34191====== h_config_usenone_color ===== 34192<HTML> 34193<HEAD> 34194<TITLE>OPTION: Use None Color</TITLE> 34195</HEAD> 34196<BODY> 34197<H1>OPTION: Use None Color</H1> 34198 34199This is a special color that simply means to leave the color alone. 34200It is useful for Index symbols and for Keyword Colors used in the Subject 34201field of an index line. 34202The most likely use is to set an explicit foreground color and then set 34203the background color to the None Color. 34204That will cause the symbol or keyword to be drawn in the foreground color 34205with a background equal to whatever color the rest of the index line is already 34206drawn in. 34207You will see no visible effect unless you have assigned Indexcolor Rules to 34208color index lines or you have set an actual color for the Reverse Color. 34209<P> 34210<A HREF="h_color_setup">Descriptions of the available commands</A> 34211<P> 34212Look <A HREF="h_edit_nav_cmds">here</A> 34213to see the available Editing and Navigation commands. 34214<P> 34215<End of help on this topic> 34216</BODY> 34217</HTML> 34218====== h_config_dflt_color ===== 34219<HTML> 34220<HEAD> 34221<TITLE>OPTION: Default Color</TITLE> 34222</HEAD> 34223<BODY> 34224<H1>OPTION: Default Color</H1> 34225 34226Setting default will cause the color to be the default color. 34227Unsetting default is normally done by choosing a color, but in some cases 34228you may want to declare the current default color to be your non-default 34229choice. 34230For example, the default Keyname Color is the same as the Reverse Color. 34231Whenever the Reverse Color changes the Keyname Color will also change, unless 34232you've changed it or unset the default box. 34233<P> 34234<A HREF="h_color_setup">Descriptions of the available commands</A> 34235<P> 34236Look <A HREF="h_edit_nav_cmds">here</A> 34237to see the available Editing and Navigation commands. 34238<P> 34239<End of help on this topic> 34240</BODY> 34241</HTML> 34242====== h_config_bold_slctbl ===== 34243<HTML> 34244<HEAD> 34245<TITLE>OPTION: Bold</TITLE> 34246</HEAD> 34247<BODY> 34248<H1>OPTION: Bold</H1> 34249 34250The color for this particular section may have the Bold attribute turned 34251on or off. 34252Setting bold will cause the characters to be bold. 34253<P> 34254<A HREF="h_color_setup">Descriptions of the available commands</A> 34255<P> 34256Look <A HREF="h_edit_nav_cmds">here</A> 34257to see the available Editing and Navigation commands. 34258<P> 34259<End of help on this topic> 34260</BODY> 34261</HTML> 34262====== h_config_kw_color ===== 34263<HTML> 34264<HEAD> 34265<TITLE>OPTION: Keyword Colors</TITLE> 34266</HEAD> 34267<BODY> 34268<H1>OPTION: Keyword Colors</H1> 34269 34270Sets the colors Alpine uses for Keyword fields in the MESSAGE INDEX screen. 34271Keywords are displayed as part of the Subject by default. 34272They are also displayed as part of the Subject if the tokens 34273"SUBJKEY", "SUBJKEYTEXT", "SUBJKEYINIT", or "SUBJKEYINITTEXT" are used in the 34274<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option. 34275Keywords may also be displayed in a column of their own in the MESSAGE INDEX 34276screen by using the "KEY" or "KEYINIT" tokens. 34277<P> 34278For example, you might have set up a Keyword 34279"Work" using the 34280<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen. 34281You could cause that Keyword to show up as a special color 34282by setting up the Keyword Color using this option, and then including it 34283in the MESSAGE INDEX screen using one of the tokens listed above in the 34284<!--#echo var="VAR_index-format"-->. 34285<P> 34286<A HREF="h_color_setup">Descriptions of the available commands</A> 34287<P> 34288Look <A HREF="h_edit_nav_cmds">here</A> 34289to see the available Editing and Navigation commands. 34290<P> 34291<End of help on this topic> 34292</BODY> 34293</HTML> 34294====== h_config_customhdr_color ===== 34295<HTML> 34296<HEAD> 34297<TITLE>OPTION: <!--#echo var="VAR_viewer-hdr-colors"--></TITLE> 34298</HEAD> 34299<BODY> 34300<H1>OPTION: <!--#echo var="VAR_viewer-hdr-colors"--></H1> 34301 34302Sets the colors Alpine uses for specific header fields in the MESSAGE TEXT screen. 34303For example, you may set the color of the Subject header or the From header. 34304The foreground color is the color of the actual character and the 34305background color is the color of the area behind the character. 34306<P> 34307In addition to setting the colors for particular headers (like the Subject) 34308you may also set a color to be used for all headers unless overridden by a 34309more specific Viewer Header Color. 34310To do this use the 34311<A HREF="h_config_header_general_color">Header General Color</A>. 34312<P> 34313For Header Colors, 34314there is an additional line on the 34315screen labeled "Pattern to match". 34316If you leave that blank, then the whole field for that header will 34317be colored. 34318However, if you give a pattern to match, the coloring will only take place 34319if there is a match for that pattern in the value of the field. 34320For example, if you are working on a color for the Subject header and 34321you fill in a pattern of "important", then only Subjects that 34322contain the word "important" will be colored. 34323<P> 34324If the pattern you enter is a comma-separated list of patterns, then coloring 34325happens if any of those patterns matches. 34326<P> 34327<A HREF="h_color_setup">Descriptions of the available commands</A> 34328<P> 34329Look <A HREF="h_edit_nav_cmds">here</A> 34330to see the available Editing and Navigation commands. 34331<P> 34332<End of help on this topic> 34333</BODY> 34334</HTML> 34335====== h_config_indextoken_color ===== 34336<HTML> 34337<HEAD> 34338<TITLE>OPTION: <!--#echo var="VAR_index-token-colors"--></TITLE> 34339</HEAD> 34340<BODY> 34341<H1>OPTION: <!--#echo var="VAR_index-token-colors"--></H1> 34342 34343This option allows you to set up the color in which any token, not specified by the 34344previous options, will be colored in the MESSAGE INDEX screen. 34345<P> 34346In order to use this option, you must press the "I" <B>IndxHdr</B> command, and add 34347a token that can be used in the index format. 34348The list of available tokens is <A HREF="h_index_tokens">here</A>. 34349<P> 34350If you fail to enter a valid token your entry will be ignored, and you will be asked to 34351enter a new one. Once you have entered a valid token, a line will be added to the 34352configuration screen that you can use to set up the colors in which that token will 34353be painted. This is done in the same way that you configure colors for other 34354variables. 34355 34356<A HREF="h_color_setup">Descriptions of the available commands</A> 34357<P> 34358Look <A HREF="h_edit_nav_cmds">here</A> 34359to see the available Editing and Navigation commands. 34360<P> 34361<End of help on this topic> 34362</BODY> 34363</HTML> 34364====== h_config_customhdr_pattern ===== 34365<HTML> 34366<HEAD> 34367<TITLE>OPTION: Viewer Header Color Pattern</TITLE> 34368</HEAD> 34369<BODY> 34370<H1>OPTION: Viewer Header Color Pattern</H1> 34371 34372If you leave this blank, then the whole field for the header will 34373be colored. 34374If you give a pattern to match, the coloring will only take place 34375if there is a match for that pattern in the value of the field. 34376For example, if you are working on a color for the Subject header and 34377you fill in a pattern of "important", then only Subjects that 34378contain the word "important" will be colored. 34379<P> 34380For address headers (like From and To) and for the Newsgroups header, 34381a pattern match will cause only the matched addresses or newsgroups to be 34382colored. 34383If there is no pattern to match, then all of the addresses or newsgroups 34384in the relevant header will be colored. 34385<P> 34386The matching pattern may be a comma-separated list of patterns to match 34387instead of a single pattern. 34388For example, you could use the pattern "important,urgent" which would 34389cause a match if either the word "important" or the word 34390"urgent" appeared in the value of the header. 34391You could list several comma-separated email addresses in the Header 34392From Color pattern so that those addresses will be colored when any of 34393them appear in the From header. 34394<P> 34395To add a new matching pattern or change the existing pattern use the 34396<!--chtml if pinemode="function_key"--> 34397"F4" 34398<!--chtml else--> 34399"C" 34400<!--chtml endif--> 34401"Change" command that is available when the "Pattern to 34402match" line is highlighted. 34403The 34404<!--chtml if pinemode="function_key"--> 34405"F10" 34406<!--chtml else--> 34407"D" 34408<!--chtml endif--> 34409"Delete" command may be used to quickly remove all patterns 34410for a particular header. 34411<P> 34412<End of help on this topic> 34413</BODY> 34414</HTML> 34415====== h_color_setup ===== 34416<HTML> 34417<HEAD> 34418<TITLE>SETUP COLOR COMMANDS</TITLE> 34419</HEAD> 34420<BODY> 34421<H1>SETUP COLOR COMMANDS</H1> 34422<!--chtml if pinemode="function_key"--> 34423<PRE> 34424Available Commands -- Group 1 34425------------------------------- 34426F1 Display this help text 34427F2 Show other available commands 34428F3 Exit to MAIN MENU 34429F4 Select the highlighted foreground or background color 34430F5 Move to previous line 34431F6 Move to next line 34432F7 Previous page 34433F8 Next page 34434F9 Add a config section for a header field 34435F10 Restore all default colors (for all sections) 34436F11 Print color configuration screen 34437F12 Whereis (search for word) 34438 34439Available Commands -- Group 2 34440------------------------------- 34441F1 Display this help text 34442F2 Show other available commands 34443F5 Delete config section for highlighted header field 34444F6 Shuffle the order of Header Color sections 34445</PRE> 34446<!--chtml else--> 34447<PRE> 34448General commands 34449------------------------------------------------- 34450 ? Display this help text E Exit back to MAIN MENU 34451 P Previous Line N Next Line 34452 - Previous page Spc (space bar) Next page 34453 W WhereIs (search for word) % Print color configuration screen 34454 34455Color Setup Commands 34456------------------------------------------------ 34457 * Select the highlighted foreground or background color 34458 A Add a config section for a header field 34459 D Delete config section for highlighted header field 34460 R Restore all default colors (for all sections) 34461 $ Shuffle the order of Header Color sections 34462</PRE> 34463<!--chtml endif--> 34464 34465<H2>Description of the Setup Color Screen</H2> 34466 34467From this screen you may turn on color and set the colors of 34468various parts of the Alpine display. 34469For help on turning on color move your cursor into the Color Style section 34470at the top of the Setup Color screen and ask for help. 34471 34472<P> 34473There are several sections in the Setup Color Screen. 34474At the top are some settings that handle the style of color used 34475with your terminal emulator (UNIX only), and some settings that 34476control how the current indexline and the titlebar are colored. 34477After that comes a long section called GENERAL COLORS that allows 34478you to set the color of many elements in the Alpine screens. 34479For example, the color of the titlebar, status messages, 34480selectable links, quotes and signatures in messages, and so on. 34481After that is a section called INDEX COLORS that allows you to 34482set the colors of various pieces of the displayed index lines in 34483the MESSAGE INDEX screen. 34484The next section is HEADER COLORS. This is for coloring headers of 34485messages in the MESSAGE TEXT screen in just about any way you would like. 34486Finally, the KEYWORD COLORS section allows you to highlight 34487<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> 34488in the MESSAGE INDEX screen. 34489 34490<P> 34491To change a color, highlight the color you want to change (for example, 34492the Status Color) by moving 34493the cursor into it. 34494You may want to read the help text for the color to see a brief description 34495of what you are coloring. 34496Then press "C" for Change to set the color to something new. 34497That will put you into a screen with two columns of colors, one for 34498the foreground color and one for the background color. 34499The foreground color is just the color you want the actual characters 34500to be and the background color is the color of the rest of the rectangle 34501behind the characters. 34502Select the foreground and background colors desired by using the Next and 34503Prev keys to highlight the color, and the * command to select it. 34504<P> 34505To set a color to its default value, set the X in the Default line at 34506the bottom of the list of colors. 34507<P> 34508 34509The HEADER COLORS section is a little bit different from the others. 34510Besides coloring the specific fields that Alpine knows about, you may also 34511color specific header fields when viewing a message in the MESSAGE TEXT 34512screen. 34513For example, you may color the Subject header a particular color. 34514There are a few commands for use with headers. 34515The "AddHeader" command adds a section to the color 34516configuration screen that allows you to set the color for that header. 34517You'll be asked for the name of the header field you want to color. 34518If you wanted to color the Subject, you would answer 34519with the word "subject". 34520Once you've added a header field, the color setting works just like the 34521other color fields, except that there is an additional line on the 34522configuration screen labeled "Pattern to match". 34523If you leave that blank, then the whole field for that header will always 34524be colored. 34525However, if you give a pattern to match, the coloring will only take place 34526if there is a match for that pattern in the value of the field. 34527For example, if you are working on a color for the Subject header and 34528you fill in a pattern of "important", then only Subjects that 34529contain the word "important" will be colored. 34530<P> 34531The "DeleteHdr" command removes a header section from the 34532configuration altogether. 34533The "Shuffle" command changes the order of header sections. 34534This is only necessary if you use header sections with pattern fields. 34535For example, if you have two Subject sections, one with one pattern and 34536another with another pattern, and the subject for a particular message 34537happens to match both, then the color from the first match is used. 34538<P> 34539 34540The command "RestoreDefs" will restore all of the default colors. 34541Each section will change to the default value used for that section when 34542color is first enabled. 34543When you restore all default colors the color settings for the Header Colors 34544will be unset (since that's the default), but the header fields you've 34545added will remain so that you may easily reset them. 34546In order to get rid of them completely you'd have to use 34547the "DeleteHdr" command. 34548 34549<P> 34550Remember that <A HREF="h_rules_incols">Index Line Colors</A> 34551may be set with matching rules and that is configured separately from 34552the rest of the color settings described here. 34553It is configured in the Setup/Rules/Indexcolors section of the configuration screen 34554instead of in the Setup/Kolor section. 34555 34556<P><UL> 34557<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 34558</UL><P> 34559<End of help on this topic> 34560</BODY> 34561</HTML> 34562====== h_config_news_uses_recent ====== 34563<HTML> 34564<HEAD> 34565<TITLE>FEATURE: <!--#echo var="FEAT_news-approximates-new-status"--></TITLE> 34566</HEAD> 34567<BODY> 34568<H1>FEATURE: <!--#echo var="FEAT_news-approximates-new-status"--></H1> 34569 34570This feature causes certain messages to be marked as "New" in the 34571MESSAGE INDEX of newsgroups. 34572This feature is set by default. 34573 34574<P> 34575 34576When opening a newsgroup, Alpine will consult your "newsrc" file and 34577determine the last message you have previously disposed of via the "D" 34578key. If this feature is set, any subsequent messages will be shown in the 34579Index with an "N", and the first of these messages will be highlighted. 34580Although this is only an approximation of true "New" or "Unseen" 34581status, it provides a useful cue to distinguish more-or-less recent 34582messages from those you have seen previously, but are not yet ready to 34583mark deleted. 34584 34585<P> 34586 34587Background: your "newsrc" file (used to store message status information 34588for newsgroups) is only capable of storing a single flag, and Alpine uses 34589this to record whether or not you are "done with" a message, as 34590indicated by marking the message as "Deleted". Unfortunately, this 34591means that Alpine has no way to record exactly which messages you have 34592previously seen, so it normally does not show the "N" status flag for 34593any messages in a newsgroup. This feature enables a starting 34594*approximation* of seen/unseen status that may be useful. 34595<P> 34596<End of help on this topic> 34597</BODY> 34598</HTML> 34599====== h_config_expose_hidden_config ===== 34600<HTML> 34601<HEAD> 34602<TITLE>FEATURE: <!--#echo var="FEAT_expose-hidden-config"--></TITLE> 34603</HEAD> 34604<BODY> 34605<H1>FEATURE: <!--#echo var="FEAT_expose-hidden-config"--></H1> 34606 34607If set, this causes configuration options and features that are normally 34608hidden from view to be editable in the Setup/Config screen. 34609 34610<P> 34611The purpose of this feature is to allow you to change configuration 34612features and variables that are normally hidden. 34613This is particularly useful if you are using a remote configuration, 34614where it is difficult to edit the contents manually, but it may also be used 34615on a local pinerc configuration file. 34616<P> 34617If set, several configuration variables and features that are normally 34618hidden from view will show up in the Setup/Configuration screen. 34619They will be at the bottom of the configuration screen. 34620You can find them by searching for the words "hidden configuration". 34621<P> 34622 34623Note that this is an advanced feature that should be used with care. 34624The reason that this part of the configuration is normally hidden is because 34625there is a significant potential for causing problems if you change these 34626variables. 34627If something breaks after a change try changing it back to see if that is 34628what is causing the problem. 34629There are also some variables that are normally hidden because they are 34630manipulated through Alpine in other ways. 34631For example, colors are normally set using the Setup/Kolors screen and 34632the "<!--#echo var="VAR_address-book"-->" variable is normally set using 34633the Setup/AddressBooks screen, so there is little reason to edit these directly. 34634The "<!--#echo var="VAR_incoming-folders"-->" variable is normally changed by using 34635the Add, Delete, and Rename commands in the FOLDER LIST screen, 34636and the "<!--#echo var="VAR_last-time-prune-questioned"-->" variable is normally used 34637internally by Alpine and not set directly by the user. 34638<P> 34639<UL> 34640<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 34641</UL><P> 34642<End of help on this topic> 34643</BODY> 34644</HTML> 34645====== h_config_disable_signature_edit ===== 34646<HTML> 34647<HEAD> 34648<TITLE>FEATURE: <!--#echo var="FEAT_disable-signature-edit-cmd"--></TITLE> 34649</HEAD> 34650<BODY> 34651<H1>FEATURE: <!--#echo var="FEAT_disable-signature-edit-cmd"--></H1> 34652 34653If set, this disables the editing of signature files from within 34654the Setup/Config screen. 34655<P> 34656<UL> 34657<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 34658</UL><P> 34659<End of help on this topic> 34660</BODY> 34661</HTML> 34662====== h_config_delete_before_writing ===== 34663<HTML> 34664<HEAD> 34665<TITLE>FEATURE: <!--#echo var="FEAT_enable-delete-before-writing"--></TITLE> 34666</HEAD> 34667<BODY> 34668<H1>FEATURE: <!--#echo var="FEAT_enable-delete-before-writing"--></H1> 34669 34670This feature controls a behavior of Alpine intended to workaround problems in 34671terminals where the marker for the end of inverse video cannot be overwritten, 34672but must be deleted, as a way to start inverse video again. 34673 34674<P> 34675When this feature is enabled, Alpine will delete a line before writing it, 34676therefore deleting the end of reverse video. Modern terminals do not require 34677enabling this feature, but some old terminals might require it. 34678<P> 34679<UL> 34680<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 34681</UL><P> 34682<End of help on this topic> 34683</BODY> 34684</HTML> 34685====== h_config_disable_roles_templateedit ===== 34686<HTML> 34687<HEAD> 34688<TITLE>FEATURE: <!--#echo var="FEAT_disable-roles-template-edit"--></TITLE> 34689</HEAD> 34690<BODY> 34691<H1>FEATURE: <!--#echo var="FEAT_disable-roles-template-edit"--></H1> 34692 34693If set, this disables the editing of template files within the 34694Role setup screen. 34695<P> 34696<UL> 34697<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 34698</UL><P> 34699<End of help on this topic> 34700</BODY> 34701</HTML> 34702====== h_config_disable_roles_sigedit ===== 34703<HTML> 34704<HEAD> 34705<TITLE>FEATURE: <!--#echo var="FEAT_disable-roles-sig-edit"--></TITLE> 34706</HEAD> 34707<BODY> 34708<H1>FEATURE: <!--#echo var="FEAT_disable-roles-sig-edit"--></H1> 34709 34710If set, this disables the editing of signature files within the 34711Role setup screen. 34712<P> 34713<UL> 34714<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 34715</UL><P> 34716<End of help on this topic> 34717</BODY> 34718</HTML> 34719====== h_config_disable_roles_setup ===== 34720<HTML> 34721<HEAD> 34722<TITLE>FEATURE: <!--#echo var="FEAT_disable-roles-setup-cmd"--></TITLE> 34723</HEAD> 34724<BODY> 34725<H1>FEATURE: <!--#echo var="FEAT_disable-roles-setup-cmd"--></H1> 34726 34727If set, this disables the Setup/Rules/Roles command. 34728<P> 34729<UL> 34730<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 34731</UL><P> 34732<End of help on this topic> 34733</BODY> 34734</HTML> 34735====== h_config_disable_pipes_in_templates ===== 34736<HTML> 34737<HEAD> 34738<TITLE>FEATURE: <!--#echo var="FEAT_disable-pipes-in-templates"--></TITLE> 34739</HEAD> 34740<BODY> 34741<H1>FEATURE: <!--#echo var="FEAT_disable-pipes-in-templates"--></H1> 34742 34743By default, if a template file name is followed by a vertical bar (|) then 34744that causes the file to be executed to produce the text for the template. 34745If this feature is set, then this is not allowed. 34746<P> 34747<UL> 34748<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 34749</UL><P> 34750<End of help on this topic> 34751</BODY> 34752</HTML> 34753====== h_config_disable_pipes_in_sigs ===== 34754<HTML> 34755<HEAD> 34756<TITLE>FEATURE: <!--#echo var="FEAT_disable-pipes-in-sigs"--></TITLE> 34757</HEAD> 34758<BODY> 34759<H1>FEATURE: <!--#echo var="FEAT_disable-pipes-in-sigs"--></H1> 34760 34761By default, if a signature file name is followed by a vertical bar (|) then 34762that causes the file to be executed to produce the text for the signature. 34763If this feature is set, then this is not allowed. 34764<P> 34765<UL> 34766<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 34767</UL><P> 34768<End of help on this topic> 34769</BODY> 34770</HTML> 34771====== h_config_disable_password_cmd ===== 34772<HTML> 34773<HEAD> 34774<TITLE>FEATURE: <!--#echo var="FEAT_disable-password-cmd"--></TITLE> 34775</HEAD> 34776<BODY> 34777<H1>FEATURE: <!--#echo var="FEAT_disable-password-cmd"--></H1> 34778 34779If set, then the Setup/Newpassword command is disabled. 34780<P> 34781<UL> 34782<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 34783</UL><P> 34784<End of help on this topic> 34785</BODY> 34786</HTML> 34787====== h_config_disable_password_caching ===== 34788<HTML> 34789<HEAD> 34790<TITLE>FEATURE: <!--#echo var="FEAT_disable-password-caching"--></TITLE> 34791</HEAD> 34792<BODY> 34793<H1>FEATURE: <!--#echo var="FEAT_disable-password-caching"--></H1> 34794 34795Normally, loginname/password combinations are cached in Alpine so that 34796you do not have to enter the same password more than once in a session. 34797A disadvantage to this approach is that the password must be stored in 34798the memory image of the running Alpine in order that it can be re-used. 34799In the event that Alpine crashes and produces a core dump, and that core 34800dump is readable by others, the loginname and password could be read 34801from the core dump. 34802<P> 34803If this feature is set, then the passwords will not be cached and you 34804will have to retype the password whenever Alpine needs it. 34805Even with this feature set there is still some chance that the core 34806file will contain a password, so care should be taken to make the 34807core files unreadable. 34808<P> 34809NOTE: If PASSFILE caching is enabled, this does not disable it. 34810That is a separate and independent feature. 34811<UL> 34812<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 34813</UL><P> 34814<End of help on this topic> 34815</BODY> 34816</HTML> 34817====== h_config_disable_password_file_saving ===== 34818<HTML> 34819<HEAD> 34820<TITLE>FEATURE: <!--#echo var="FEAT_disable-password-file-saving"--></TITLE> 34821</HEAD> 34822<BODY> 34823<H1>FEATURE: <!--#echo var="FEAT_disable-password-file-saving"--></H1> 34824 34825<P> This feature disables caching of passwords, even if your version of Alpine allows 34826saving passwords. For MAC OS users saving passwords is done using the Apple Key Chain, for 34827Windows users caching passwords is done using the internal Windows Credentials, and for 34828other users this is done by using the password file. In this feature, the phrase 34829"password file" is a misnomer and represents the way in which your system 34830stores passwords. 34831 34832<P> 34833Specifically, this feature changes the behavior of Alpine when a login name and password combination 34834for a specific server is not found in the password file. The default behavior is that 34835Alpine will ask the user if they wish to save this information in the password file for future 34836use. It is assumed that if a user created a password file it is because they intend 34837to use it, but in some instances a user might want to save some passwords and not others. 34838In this case, enabling this feature will make Alpine not add any more passwords to the 34839password file and will only use the passwords that it already saved. If you wish to allow 34840Alpine to save more passwords in the password file, disable this feature. 34841 34842<P> Regardless of which method Alpine uses to store passwords, this is done in a secure 34843way when compiled with OpenSSL or LibreSSL. This is very likely to be your version, and 34844you can check this by reading the encryption features 34845<A HREF="X-Alpine-Config:">supported</A> by Alpine. 34846 34847<P> 34848<UL> 34849<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 34850</UL><P> 34851<End of help on this topic> 34852</BODY> 34853</HTML> 34854====== h_config_disable_kb_lock ===== 34855<HTML> 34856<HEAD> 34857<TITLE>FEATURE: <!--#echo var="FEAT_disable-keyboard-lock-cmd"--></TITLE> 34858</HEAD> 34859<BODY> 34860<H1>FEATURE: <!--#echo var="FEAT_disable-keyboard-lock-cmd"--></H1> 34861 34862If set, then the Keyboard Lock command is removed from the MAIN MENU. 34863<P> 34864<UL> 34865<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 34866</UL><P> 34867<End of help on this topic> 34868</BODY> 34869</HTML> 34870====== h_config_disable_config_cmd ===== 34871<HTML> 34872<HEAD> 34873<TITLE>FEATURE: <!--#echo var="FEAT_disable-config-cmd"--></TITLE> 34874</HEAD> 34875<BODY> 34876<H1>FEATURE: <!--#echo var="FEAT_disable-config-cmd"--></H1> 34877 34878If set, then the Setup/Config screen is disabled. 34879<P> 34880<UL> 34881<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 34882</UL><P> 34883<End of help on this topic> 34884</BODY> 34885</HTML> 34886====== h_config_allow_chg_from ===== 34887<HTML> 34888<HEAD> 34889<TITLE>FEATURE: <!--#echo var="FEAT_allow-changing-from"--></TITLE> 34890</HEAD> 34891<BODY> 34892<H1>FEATURE: <!--#echo var="FEAT_allow-changing-from"--></H1> 34893 34894This feature affects Alpine's handling of the "From:" header field 34895in the "<A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>" configuration 34896option. 34897<P> 34898If this feature is set then the From line can be changed just like 34899all the other header fields that can be changed. 34900This feature defaults to <EM>ON</EM>. 34901<P> 34902Even with this feature turned ON (the default) you will not be able 34903to change the From header unless you add it to your list of 34904<A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>. 34905You may also want to change the 34906<A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A> 34907if you want the From header to always show up in the composer without 34908having to type the Rich Headers command first. 34909<P> 34910Note that many sites restrict the use of this feature in order to 34911reduce the chance of falsified addresses and misdirected mail. 34912If you want to change the value of what gets included in the From header 34913in messages you send 34914look <A HREF="h_config_change_your_from">here</A> for a description. 34915<P> 34916<UL> 34917<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 34918</UL><P> 34919<End of help on this topic> 34920</BODY> 34921</HTML> 34922====== h_config_disable_collate ===== 34923<HTML> 34924<HEAD> 34925<TITLE>FEATURE: <!--#echo var="FEAT_disable-setlocale-collate"--></TITLE> 34926</HEAD> 34927<BODY> 34928<H1>FEATURE: <!--#echo var="FEAT_disable-setlocale-collate"--></H1> 34929 34930This is a hard to understand feature that should only be used in rare cases. 34931Normally, the C function call 34932<P> 34933<CENTER><SAMP>setlocale(LC_COLLATE, "")</SAMP></CENTER> 34934<P> 34935is used by Alpine. 34936If you want to try turning it off, 34937setting this feature will turn it off. 34938This part of the locale has to do with the sort order 34939of characters in your locale. 34940<P> 34941<UL> 34942<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 34943</UL><P> 34944<End of help on this topic> 34945</BODY> 34946</HTML> 34947====== h_config_quell_attach_extra_prompt ===== 34948<HTML> 34949<HEAD> 34950<TITLE>FEATURE: <!--#echo var="FEAT_quell-attachment-extra-prompt"--></TITLE> 34951</HEAD> 34952<BODY> 34953<H1>FEATURE: <!--#echo var="FEAT_quell-attachment-extra-prompt"--></H1> 34954 34955By default, when you attempt to view an attachment externally 34956from the "Attachment View" screen, you are asked if you 34957really want to view the selected attachment. 34958 34959<P> 34960If this feature is set, you will <B>not</B> be prompted to confirm 34961your selection. Prior to Alpine and to Pine 4.50, the default behavior was to not 34962prompt. This feature was added for those wanting to preserve that 34963behavior (along with 34964<A HREF="h_config_quell_attach_ext_warn"><!--#echo var="FEAT_quell-attachment-extension-warn"--></A>). 34965 34966<P> 34967<UL> 34968<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 34969</UL><P> 34970<End of help on this topic> 34971</BODY> 34972</HTML> 34973====== h_config_quell_attach_ext_warn ===== 34974<HTML> 34975<HEAD> 34976<TITLE>FEATURE: <!--#echo var="FEAT_quell-attachment-extension-warn"--></TITLE> 34977</HEAD> 34978<BODY> 34979<H1>FEATURE: <!--#echo var="FEAT_quell-attachment-extension-warn"--></H1> 34980 34981<P> 34982This feature suppresses the extra warning you can get when trying 34983to view an attachment for which there is no mime-type match. Turning 34984on this feature will just run the program according to extension 34985instead of first warning the user that it will run according to the 34986file's extension. 34987<P> 34988This feature can be used along side 34989<A HREF="h_config_quell_attach_extra_prompt"><!--#echo var="FEAT_quell-attachment-extra-prompt"--></A> 34990to preserve the behavior exhibited in Pine versions prior to Pine 4.50. 34991<P> 34992<UL> 34993<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 34994</UL><P> 34995<End of help on this topic> 34996</BODY> 34997</HTML> 34998====== h_config_mailcap_params ===== 34999<HTML> 35000<HEAD> 35001<TITLE>FEATURE: <!--#echo var="FEAT_enable-mailcap-param-substitution"--></TITLE> 35002</HEAD> 35003<BODY> 35004<H1>FEATURE: <!--#echo var="FEAT_enable-mailcap-param-substitution"--></H1> 35005 35006If set, this will allow mailcap named parameter substitution to occur 35007in mailcap entries. 35008By default, this is turned off to prevent security problems that may occur 35009with some incorrect mailcap configurations. 35010For more information, see RFC1524 and look for "named parameters" in the 35011text of the RFC. 35012<P> 35013<UL> 35014<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35015</UL><P> 35016<End of help on this topic> 35017</BODY> 35018</HTML> 35019====== h_config_disable_shared ===== 35020<HTML> 35021<HEAD> 35022<TITLE>FEATURE: <!--#echo var="FEAT_disable-shared-namespaces"--></TITLE> 35023</HEAD> 35024<BODY> 35025<H1>FEATURE: <!--#echo var="FEAT_disable-shared-namespaces"--></H1> 35026 35027If this feature is set, the automatic search for namespaces "ftp", 35028"imapshared", and "imappublic" by the underlying library 35029will be disabled. 35030The reason this feature exists is because there are some implementations 35031of system password lookup routines that are very slow when presented with 35032a long loginname that does not exist. 35033This feature could be set to prevent the delay at startup time when the 35034names above are searched for in the password file. 35035<P> 35036<UL> 35037<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35038</UL><P> 35039<End of help on this topic> 35040</BODY> 35041</HTML> 35042====== h_config_hide_nntp_path ===== 35043<HTML> 35044<HEAD> 35045<TITLE>FEATURE: <!--#echo var="FEAT_hide-nntp-path"--></TITLE> 35046</HEAD> 35047<BODY> 35048<H1>FEATURE: <!--#echo var="FEAT_hide-nntp-path"--></H1> 35049 35050Normally the Path header that Alpine generates when posting to a newsgroup 35051contains the name of the computer from which the message is being sent and 35052the user name. 35053Some believe that this information is used by spammers. 35054If this feature is set, that information will be replaced with the text 35055<P> 35056<CENTER><SAMP>not-for-mail</SAMP></CENTER> 35057<P> 35058instead. 35059<P> 35060It should be noted that many servers being connected to will still reveal 35061the information that this feature attempts to protect. 35062<P> 35063<UL> 35064<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35065</UL><P> 35066<End of help on this topic> 35067</BODY> 35068</HTML> 35069====== h_config_no_bezerk_zone ===== 35070<HTML> 35071<HEAD> 35072<TITLE>FEATURE: <!--#echo var="FEAT_quell-berkeley-format-timezone"--></TITLE> 35073</HEAD> 35074<BODY> 35075<H1>FEATURE: <!--#echo var="FEAT_quell-berkeley-format-timezone"--></H1> 35076 35077POSIX mandates a timezone in UNIX mailbox format folder delimiters 35078(the line that begins with From <SPACE>). 35079Some versions of Berkeley mail have trouble with this, and don't recognize 35080the line as a message delimiter. 35081If this feature is set, the timezone will be left off the delimiter line. 35082<P> 35083<UL> 35084<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35085</UL><P> 35086<End of help on this topic> 35087</BODY> 35088</HTML> 35089====== h_config_quell_domain_warn ===== 35090<HTML> 35091<HEAD> 35092<TITLE>FEATURE: <!--#echo var="FEAT_quell-maildomain-warning"--></TITLE> 35093</HEAD> 35094<BODY> 35095<H1>FEATURE: <!--#echo var="FEAT_quell-maildomain-warning"--></H1> 35096 35097When your configuration is set up so that your domain name contains no dots, 35098it is usually a configuration error. 35099By default, Alpine will warn you about this when you start it up. 35100You will see a warning message that looks like 35101 35102<P> 35103<CENTER><SAMP>Incomplete maildomain "<domain>".</SAMP></CENTER> 35104 35105<P> 35106If this feature is set, the warning is turned off. 35107<P> 35108<UL> 35109<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35110</UL><P> 35111<End of help on this topic> 35112</BODY> 35113</HTML> 35114====== h_config_quell_imap_env ===== 35115<HTML> 35116<HEAD> 35117<TITLE>FEATURE: <!--#echo var="FEAT_quell-imap-envelope-update"--></TITLE> 35118</HEAD> 35119<BODY> 35120<H1>FEATURE: <!--#echo var="FEAT_quell-imap-envelope-update"--></H1> 35121 35122In the MESSAGE INDEX screen, if the open folder is being accessed 35123using IMAP, Alpine normally tries to paint the index lines on the screen 35124as soon as the information arrives from the IMAP server. 35125This means that the index information makes it onto the screen more quickly 35126than it otherwise would. 35127This sometimes results in behavior that bothers some users. 35128For example, when paging to a new page of the index, it may be possible for 35129the lines to be painted on the screen in a random order, rather than from 35130top to bottom. 35131<P> 35132 35133Setting this feature causes Alpine to wait for all of the information 35134to be gathered before it paints the index screen. 35135Once it collects all of the information, the screen will be painted quickly 35136from top to bottom. 35137<P> 35138<UL> 35139<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35140</UL><P> 35141<End of help on this topic> 35142</BODY> 35143</HTML> 35144====== h_config_quell_news_env ===== 35145<HTML> 35146<HEAD> 35147<TITLE>FEATURE: <!--#echo var="FEAT_quell-news-envelope-update"--></TITLE> 35148</HEAD> 35149<BODY> 35150<H1>FEATURE: <!--#echo var="FEAT_quell-news-envelope-update"--></H1> 35151 35152In the MESSAGE INDEX screen, if the open folder is being accessed 35153using NNTP (News), Alpine normally tries to paint the index lines on the screen 35154as soon as the information arrives from the NNTP server. 35155This means that the index information makes it onto the screen more quickly 35156than it otherwise would. 35157This sometimes results in behavior that bothers some users. 35158For example, when paging to a new page of the index, it may be possible for 35159the lines to be painted on the screen in a random order, rather than from 35160top to bottom. 35161<P> 35162 35163Setting this feature causes Alpine to wait for all of the information 35164to be gathered before it paints the index screen. 35165Once it collects all of the information, the screen will be painted quickly 35166from top to bottom. 35167<P> 35168<UL> 35169<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35170</UL><P> 35171<End of help on this topic> 35172</BODY> 35173</HTML> 35174====== h_config_quell_content_id ===== 35175<HTML> 35176<HEAD> 35177<TITLE>FEATURE: <!--#echo var="FEAT_quell-content-id"--></TITLE> 35178</HEAD> 35179<BODY> 35180<H1>FEATURE: <!--#echo var="FEAT_quell-content-id"--></H1> 35181 35182This feature changes the behavior of Alpine when sending messages. 35183It is intended to work around a bug in Microsoft's Outlook XP mail user 35184agent. 35185As of this writing, Microsoft has acknowledged the bug but 35186has not added it to the Knowledge Base. 35187We have been told that there will be a post-SP1 hotfix for Outlook XP. 35188This particular bug has bug fix number OfficeQFE:4781. 35189The nature of the bug is that messages with attachments that 35190contain a Content-ID header (which standard Alpine attachments do) 35191do not show the attachment indicator (a paperclip) when viewed with 35192Outlook XP. 35193So the user has no indication that the message contains an attachment. 35194 35195<P> 35196If this feature is set then Alpine will remove most Content-ID headers 35197before sending a message. 35198If an attachment is of type MESSAGE, then the existing Content-ID headers 35199inside the message will be left intact. 35200This would only happen with Alpine if a message was forwarded as an attachment 35201or if a message with a message attached was forwarded. 35202Similarly if an attachment of type MULTIPART/ALTERNATIVE is forwarded, 35203the Content-ID headers of the alternative parts will not be removed. 35204 35205<P> 35206Because the Content-ID header is a standard part of MIME it is possible 35207that setting this feature will break something. 35208For example, if an attachment has a Content-ID header that is necessary 35209for the correct functioning of that attachment, it is possible that Alpine 35210may remove that header when the attachment is forwarded. 35211However, it seems fairly safe at this time. 35212 35213<P> 35214<UL> 35215<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35216</UL><P> 35217<End of help on this topic> 35218</BODY> 35219</HTML> 35220====== h_config_winpos_in_config ===== 35221<HTML> 35222<HEAD> 35223<TITLE>FEATURE: <!--#echo var="FEAT_store-window-position-in-config"--></TITLE> 35224</HEAD> 35225<BODY> 35226<H1>FEATURE: <!--#echo var="FEAT_store-window-position-in-config"--></H1> 35227 35228PC-Alpine only. 35229<P> 35230 35231Normally, PC-Alpine will store its window size and position in the 35232Windows Registry. 35233This is convenient if you want to use the same remote 35234configuration from more than one PC. 35235If you use multiple configuration files to start PC-Alpine, you may want 35236to store the window size and position in the configuration file instead 35237of in the Registry. 35238Setting this feature causes the value to be stored in 35239<A HREF="h_config_window_position">Window-Position</A>. 35240 35241<P> 35242<UL> 35243<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35244</UL><P> 35245<End of help on this topic> 35246</BODY> 35247</HTML> 35248====== h_config_quell_ssl_largeblocks ===== 35249<HTML> 35250<HEAD> 35251<TITLE>FEATURE: <!--#echo var="FEAT_quell-ssl-largeblocks"--></TITLE> 35252</HEAD> 35253<BODY> 35254<H1>FEATURE: <!--#echo var="FEAT_quell-ssl-largeblocks"--></H1> 35255 35256PC-Alpine only. 35257<P> 35258This feature changes the behavior of fetching messages 35259and attachments so that the message data is fetched in chunks no larger 35260than 12K bytes. 35261This works around a bug in Microsoft's SSL/TLS support. 35262Some versions of Microsoft SSL are not able to read full-sized (16K) 35263SSL/TLS packets. 35264Some servers will send such packets and this will 35265cause PC-Alpine to crash with the error 35266 35267<P> 35268<CENTER><SAMP>incomplete SecBuffer exceeds maximum buffer size</SAMP></CENTER> 35269 35270<P> 35271Microsoft is aware of the problem and has developed a hotfix for it, it is 35272discussed in article 300562 in the Microsoft Knowledge Base. 35273<P> 35274<UL> 35275<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35276</UL><P> 35277<End of help on this topic> 35278</BODY> 35279</HTML> 35280====== h_config_quell_partial ===== 35281<HTML> 35282<HEAD> 35283<TITLE>FEATURE: <!--#echo var="FEAT_quell-partial-fetching"--></TITLE> 35284</HEAD> 35285<BODY> 35286<H1>FEATURE: <!--#echo var="FEAT_quell-partial-fetching"--></H1> 35287 35288Partial fetching is a feature of the IMAP protocol. 35289By default, Alpine 35290will use partial fetching when copying the contents of a message or attachment 35291from the IMAP server to Alpine. 35292This means that the fetch will be done in many 35293small chunks instead of one big chunk. The main benefit of this approach is 35294that the fetch becomes interruptible. That is, the user can type <EM>^C</EM> 35295to stop the fetch early. In some cases partial fetching may cause a performance 35296problem so that the fetching of data takes significantly longer when partial 35297fetching is used. Turning on this feature will turn off partial fetching. 35298<P> 35299<UL> 35300<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35301</UL><P> 35302<End of help on this topic> 35303</BODY> 35304</HTML> 35305====== h_config_quell_personal_name_prompt ===== 35306<HTML> 35307<HEAD> 35308<TITLE>FEATURE: <!--#echo var="FEAT_quell-personal-name-prompt"--></TITLE> 35309</HEAD> 35310<BODY> 35311<H1>FEATURE: <!--#echo var="FEAT_quell-personal-name-prompt"--></H1> 35312 35313PC-Alpine only. This feature quells the prompting for a 35314<A HREF="h_config_pers_name">personal name</A>. This 35315prompt normally happens before composing a message, and only happens when 35316there is no personal name already set. 35317<P> 35318<UL> 35319<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35320</UL><P> 35321<End of help on this topic> 35322</BODY> 35323</HTML> 35324====== h_config_quell_user_id_prompt ===== 35325<HTML> 35326<HEAD> 35327<TITLE>FEATURE: <!--#echo var="FEAT_quell-user-id-prompt"--></TITLE> 35328</HEAD> 35329<BODY> 35330<H1>FEATURE: <!--#echo var="FEAT_quell-user-id-prompt"--></H1> 35331 35332PC-Alpine only. This feature quells the prompting for a 35333<A HREF="h_config_user_id"><!--#echo var="VAR_user-id"--></A> 35334if the information can be obtained from the login name used 35335to open the INBOX. Normally, this prompt happens before composing 35336a message, and only happens when there is no user-id already set 35337in the configuration. 35338<P> 35339With this feature set, composing a message is only possible after 35340establishing a connection to the INBOX. 35341<P> 35342<UL> 35343<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35344</UL><P> 35345<End of help on this topic> 35346</BODY> 35347</HTML> 35348====== h_config_save_aggregates ===== 35349<HTML> 35350<HEAD> 35351<TITLE>FEATURE: <!--#echo var="FEAT_save-aggregates-copy-sequence"--></TITLE> 35352</HEAD> 35353<BODY> 35354<H1>FEATURE: <!--#echo var="FEAT_save-aggregates-copy-sequence"--></H1> 35355 35356This feature will optimize an aggregate copy operation, if 35357possible, by issuing a single IMAP <EM>COPY</EM> command with a 35358list of the messages to be copied. 35359This feature is set by default. 35360This may reduce network traffic and elapsed time for the Save. 35361<EM>However, many IMAP servers (including the UW IMAP server) do 35362not preserve the order of messages when this optimization is applied.</EM> 35363If this feature is not set, 35364Alpine will copy each message individually and the order of the messages 35365will be preserved. 35366<P> 35367<UL> 35368<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35369</UL><P> 35370<End of help on this topic> 35371</BODY> 35372</HTML> 35373====== h_config_use_system_translation ===== 35374<HTML> 35375<HEAD> 35376<TITLE>FEATURE: Use System Translation</TITLE> 35377</HEAD> 35378<BODY> 35379<H1>FEATURE: Use System Translation</H1> 35380 35381UNIX Alpine only. 35382<P> 35383Alpine normally uses its own internal software to convert between the multi-byte 35384representation of characters and the Unicode representation of those 35385same characters. 35386It converts from the multi-byte characters your keyboard produces to Unicode, 35387and from Unicode to the multi-byte characters your display expects. 35388Alpine also uses its own internal software to decide how much space on 35389the screen a particular Unicode character will occupy. 35390 35391<P> 35392Setting this feature tells Alpine to use the system-supplied routines to 35393perform these tasks instead. 35394In particular there are three tasks and three system routines that will 35395be used for these tasks. 35396 35397<P> 35398To convert from multi-byte to Unicode the routine 35399 35400<P> 35401<CENTER><SAMP>mbstowcs</SAMP></CENTER> 35402<P> 35403 35404is used. 35405To convert from Unicode to multi-byte the routine 35406 35407<P> 35408<CENTER><SAMP>wcrtomb</SAMP></CENTER> 35409<P> 35410 35411is used, if available, otherwise 35412 35413<P> 35414<CENTER><SAMP>wctomb</SAMP></CENTER> 35415<P> 35416 35417is used. 35418 35419And to find the screen width a particular Unicode character will 35420occupy the routine used is 35421 35422<P> 35423<CENTER><SAMP>wcwidth</SAMP></CENTER> 35424<P> 35425 35426This feature has been only lightly tested. 35427The internal routines should normally be used unless you run into 35428a problem that you think may be solved by using the system routines. 35429Note that your environment needs to be set up for these 35430routines to work correctly. 35431In particular, the LANG or LC_CTYPE variable in your environment will 35432need to be set. 35433 35434<P> 35435<UL> 35436<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35437</UL><P> 35438<End of help on this topic> 35439</BODY> 35440</HTML> 35441====== h_config_suspend_spawns ===== 35442<HTML> 35443<HEAD> 35444<TITLE>FEATURE: <!--#echo var="FEAT_use-subshell-for-suspend"--></TITLE> 35445</HEAD> 35446<BODY> 35447<H1>FEATURE: <!--#echo var="FEAT_use-subshell-for-suspend"--></H1> 35448 35449This feature affects Alpine's behavior when process suspension is enabled 35450and then activated via the Ctrl-Z key. Alpine suspension allows one to 35451temporarily interact with the operating system command "shell" 35452without 35453quitting Alpine, and then subsequently resume the still-active Alpine session. 35454<P> 35455 35456When the <A HREF="h_config_can_suspend">"<!--#echo var="FEAT_enable-suspend"-->"</A> feature 35457is set and subsequently the Ctrl-Z key 35458is pressed, Alpine will normally suspend itself and return temporary control 35459to Alpine's parent shell process. However, if this feature is set, Alpine 35460will instead create an inferior subshell process. This is useful when the 35461parent process is not intended to be used interactively. Examples include 35462invoking Alpine via the -e argument of the Unix "xterm" program, 35463or via a menu system.<P> 35464 35465Note that one typically resumes a suspended Alpine by entering the Unix 35466"fg" command, but if this feature is set, it will be necessary to 35467enter the "exit" command instead. 35468<P> 35469<UL> 35470<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35471</UL><P> 35472<End of help on this topic> 35473</BODY> 35474</HTML> 35475====== h_config_8bit_smtp ===== 35476<HTML> 35477<HEAD> 35478<TITLE>FEATURE: <!--#echo var="FEAT_enable-8bit-esmtp-negotiation"--></TITLE> 35479</HEAD> 35480<BODY> 35481<H1>FEATURE: <!--#echo var="FEAT_enable-8bit-esmtp-negotiation"--></H1> 35482 35483This feature affects Alpine's behavior when sending mail. 35484By default, this feature is set. 35485Internet standards 35486require that all electronic mail messages traversing the global Internet 35487consist of 7bit ASCII characters unless a pair of cooperating mail 35488transfer agents explicitly agree to allow 8bit messages. In general, 35489then, exchanging messages in non-ASCII characters requires MIME encoding. 35490<P> 35491However, there are now Internet standards that allow for unencoded 8bit 35492exchange of messages between cooperating systems. When this feature is set 35493Alpine will try to negotiate unencoded 8bit transmission during the 35494sending process. Should the negotiation fail, Alpine will fall back to its 35495ordinary encoding rules. 35496<P> 35497Note, this feature relies on your system's mail transport agent or 35498configured <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A> 35499having the negotiation mechanism introduced in 35500"Extended SMTP" (ESMTP) and the specific extension called 35501"8BITMIME". 35502<P> 35503ESMTP allows for graceful migration to upgraded mail transfer agents, but 35504it is possible that this feature might cause problems for some servers. 35505<P><UL> 35506<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35507</UL> 35508<P><End of help on this topic> 35509</BODY> 35510</HTML> 35511====== h_config_8bit_nntp ===== 35512<HTML> 35513<HEAD> 35514<TITLE>FEATURE: <!--#echo var="FEAT_enable-8bit-nntp-posting"--></TITLE> 35515</HEAD> 35516<BODY> 35517<H1>FEATURE: <!--#echo var="FEAT_enable-8bit-nntp-posting"--></H1> 35518 35519This feature affects Alpine's behavior when posting news. 35520 35521<P> 35522 35523The Internet standard for exchanging USENET news messages (RFC-1036) 35524specifies that USENET messages should conform to Internet mail standards 35525and contain only 7bit characters, but much of the news transport software 35526in use today is capable of successfully sending messages containing 8bit 35527characters. Hence, many people believe that it is appropriate to send 8bit 35528news messages without any MIME encoding. 35529 35530<P> 35531 35532Moreover, there is no Internet standard for explicitly negotiating 8bit 35533transfer, as there is for Internet email. Therefore, Alpine provides the 35534option of posting unencoded 8bit news messages, though not as the default. 35535Setting this feature will turn OFF Alpine's MIME encoding of newsgroup 35536postings that contain 8bit characters. 35537 35538<P> 35539 35540Note, articles may cross a path or pass through news transport software 35541that is unsafe or even hostile to 8bit characters. At best this will only 35542cause the posting to become garbled. The safest way to transmit 8bit 35543characters is to leave Alpine's MIME encoding turned on, but recipients 35544who lack MIME-aware tools are often annoyed when they receive MIME-encoded 35545messages. 35546<P> 35547<End of help on this topic> 35548</BODY> 35549</HTML> 35550====== h_config_mark_for_cc ===== 35551<HTML> 35552<HEAD> 35553<TITLE>FEATURE: <!--#echo var="FEAT_mark-for-cc"--></TITLE> 35554</HEAD> 35555<BODY> 35556<H1>FEATURE: <!--#echo var="FEAT_mark-for-cc"--></H1> 35557 35558This feature affects Alpine's MESSAGE INDEX display. 35559By default, a '+' is displayed in the first column if the 35560message is addressed directly to you. 35561When this feature is set and the message is not addressed to you, then a 35562'-' character is displayed if the message is instead Cc'd directly 35563to you. 35564 35565<P> 35566<UL> 35567<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35568</UL><P> 35569<End of help on this topic> 35570</BODY> 35571</HTML> 35572====== h_config_tab_uses_unseen ===== 35573<HTML> 35574<HEAD> 35575<TITLE>FEATURE: <!--#echo var="FEAT_tab-uses-unseen-for-next-folder"--></TITLE> 35576</HEAD> 35577<BODY> 35578<H1>FEATURE: <!--#echo var="FEAT_tab-uses-unseen-for-next-folder"--></H1> 35579 35580This feature affects Alpine's behavior when using the TAB 35581<A HREF="h_common_nextnew">NextNew Command</A> 35582to move from one folder to the next. 35583Alpine's usual behavior is to search for folders 35584with <EM>Recent</EM> messages in them. 35585Recent messages are messages that have arrived since the last time the 35586folder was opened. 35587 35588<P> 35589Setting this feature causes Alpine to search for <EM>Unseen</EM> 35590messages instead of Recent messages. 35591Unseen messages remain Unseen until you view them (or flag then as Seen with 35592the <A HREF="h_common_flag">Flag Command</A>). 35593Setting this feature allows you to locate messages you have not read 35594instead of only recently received messages. 35595When this feature is set, the feature 35596<A HREF="h_config_fast_recent">"<!--#echo var="FEAT_enable-fast-recent-test"-->"</A> 35597will have no effect, so the checking may be slower. 35598 35599<P> 35600Another reason why you might want to use this feature is that Alpine sometimes 35601opens folders implicitly behind the scenes, and this clears the 35602Recent status of all messages in the folder. 35603One example where this happens is when Saving or filtering a 35604message to another folder. 35605If that message has some <A HREF="h_config_keywords">keywords</A> 35606set, then because of some shortcomings 35607in the IMAP specification, the best way to ensure that those keywords are 35608still set in the saved copy of the message is to open the folder and 35609set the keywords explicitly. 35610Because this clears the Recent status of all messages in that folder the 35611folder will not be found by the NextNew command unless this feature is set. 35612 35613<P> 35614<End of help on this topic> 35615</BODY> 35616</HTML> 35617====== h_config_tab_new_only ===== 35618<HTML> 35619<HEAD> 35620<TITLE>FEATURE: <!--#echo var="FEAT_tab-visits-next-new-message-only"--></TITLE> 35621</HEAD> 35622<BODY> 35623<H1>FEATURE: <!--#echo var="FEAT_tab-visits-next-new-message-only"--></H1> 35624 35625This feature affects Alpine's behavior when using the TAB key to move from 35626one message to the next. Alpine's usual behavior is to select the next 35627unread message or message flagged as "Important". 35628 35629<P> 35630 35631Setting this feature causes Alpine to skip the messages flagged as important, 35632and select unread messages exclusively. Tab behavior when there are no 35633new messages left to select remains unchanged. 35634<P> 35635<End of help on this topic> 35636</BODY> 35637</HTML> 35638====== h_config_warn_if_subj_blank ===== 35639<HTML> 35640<HEAD> 35641<TITLE>FEATURE: <!--#echo var="FEAT_warn-if-blank-subject"--></TITLE> 35642</HEAD> 35643<BODY> 35644<H1>FEATURE: <!--#echo var="FEAT_warn-if-blank-subject"--></H1> 35645 35646This feature affects Alpine's behavior when you send a message being 35647composed. 35648If this option is set, Alpine will check to see if the message about to be sent 35649has a subject or not. 35650If not, you will be asked if you want to send the message anyway. 35651<P> 35652 35653<UL> 35654<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35655</UL><P> 35656<End of help on this topic> 35657</BODY> 35658</HTML> 35659====== h_config_warn_if_fcc_blank ===== 35660<HTML> 35661<HEAD> 35662<TITLE>FEATURE: <!--#echo var="FEAT_warn-if-blank-fcc"--></TITLE> 35663</HEAD> 35664<BODY> 35665<H1>FEATURE: <!--#echo var="FEAT_warn-if-blank-fcc"--></H1> 35666 35667This feature affects Alpine's behavior when you send a message being 35668composed. 35669If this option is set, Alpine will check to see if the message about to be sent 35670has an Fcc or not. 35671If not, you will be asked if you want to send the message anyway. 35672<P> 35673 35674<UL> 35675<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35676</UL><P> 35677<End of help on this topic> 35678</BODY> 35679</HTML> 35680====== h_config_warn_if_no_to_or_cc ===== 35681<HTML> 35682<HEAD> 35683<TITLE>FEATURE: <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></TITLE> 35684</HEAD> 35685<BODY> 35686<H1>FEATURE: <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></H1> 35687 35688This feature affects Alpine's behavior when you send a message being 35689composed. 35690If this option is set, Alpine will check to see if the message about to be sent 35691has either a To address, a Cc address, or a Newsgroup. 35692If none of these is set, 35693you will be asked if you want to send the message anyway. 35694<P> 35695 35696This feature is closely related to 35697<A HREF="h_config_auto_fcc_only"><!--#echo var="FEAT_fcc-only-without-confirm"--></A>. 35698Alpine will normally ask if you want to copy a message only to the Fcc. 35699This feature also applies to cases where there is a Bcc but still no To, Cc, 35700or Newsgroup. 35701If the <!--#echo var="FEAT_fcc-only-without-confirm"--> feature is set and you are sending a 35702message with only an Fcc, then you won't be asked about sending with 35703a blank To and Cc and Newsgroups header even if this feature is set. 35704Similarly, if you have already been asked if you want to send to the Fcc 35705only and you have answered Yes, then you won't be asked again about sending with 35706blank To, Cc, and Newsgroups headers even if this feature is set. 35707<P> 35708 35709<UL> 35710<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35711</UL><P> 35712<End of help on this topic> 35713</BODY> 35714</HTML> 35715====== h_config_quell_dead_letter ===== 35716<HTML> 35717<HEAD> 35718<TITLE>FEATURE: <!--#echo var="FEAT_quell-dead-letter-on-cancel"--></TITLE> 35719</HEAD> 35720<BODY> 35721<H1>FEATURE: <!--#echo var="FEAT_quell-dead-letter-on-cancel"--></H1> 35722 35723This feature affects Alpine's behavior when you cancel a message being 35724composed. Alpine's usual behavior is to write the canceled message to 35725a file named 35726<!--chtml if pinemode="os_windows"--> 35727"DEADLETR", 35728<!--chtml else--> 35729"dead.letter" in your home directory, 35730<!--chtml endif--> 35731overwriting any previous message. Under 35732some conditions (some routine), this can introduce a noticeable delay. 35733Setting this feature will cause Alpine NOT to write canceled compositions 35734into the file. 35735<P> 35736NOTE: Enabling this feature means NO record of canceled messages is 35737maintained. 35738<P> 35739This feature affects the newer option 35740<A HREF="h_config_deadlets"><!--#echo var="VAR_dead-letter-files"--></A>, which specifies the 35741number of dead letter files to keep around. 35742If this feature is set, then the <!--#echo var="VAR_dead-letter-files"--> option has no effect. 35743<P> 35744<UL> 35745<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35746</UL><P> 35747<End of help on this topic> 35748</BODY> 35749</HTML> 35750====== h_config_quell_beeps ===== 35751<HTML> 35752<HEAD> 35753<TITLE>FEATURE: <!--#echo var="FEAT_quell-status-message-beeping"--></TITLE> 35754</HEAD> 35755<BODY> 35756<H1>FEATURE: <!--#echo var="FEAT_quell-status-message-beeping"--></H1> 35757 35758This feature affects Alpine's behavior when it displays status message 35759(e.g., Error complaints, New mail warnings, etc). Setting this feature 35760will not affect the display of such messages, but will cause those that 35761emit a beep to become silent. 35762 35763<P> 35764<UL> 35765<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35766</UL><P> 35767<End of help on this topic> 35768</BODY> 35769</HTML> 35770====== h_config_suppress_user_agent ===== 35771<HTML> 35772<HEAD> 35773<TITLE>FEATURE: <!--#echo var="FEAT_suppress-user-agent-when-sending"--></TITLE> 35774</HEAD> 35775<BODY> 35776<H1>FEATURE: <!--#echo var="FEAT_suppress-user-agent-when-sending"--></H1> 35777 35778If this feature is set then Alpine will not generate a 35779<CODE>User-Agent</CODE> header in outgoing messages. 35780<P> 35781<UL> 35782<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35783</UL><P> 35784<End of help on this topic> 35785</BODY> 35786</HTML> 35787====== h_config_quell_lock_failure_warnings ===== 35788<HTML> 35789<HEAD> 35790<TITLE>FEATURE: <!--#echo var="FEAT_quell-lock-failure-warnings"--></TITLE> 35791</HEAD> 35792<BODY> 35793<H1>FEATURE: <!--#echo var="FEAT_quell-lock-failure-warnings"--></H1> 35794 35795This feature affects Alpine's behavior when it encounters a problem 35796acquiring a mail folder lock. Typically, a secondary file associated 35797with the mail folder being opened is created as part of the locking 35798process. On some systems, such file creation has been administratively 35799precluded by the system configuration. 35800<P> 35801Alpine issues a warning when such failures occur, which can become bothersome 35802if the system is configured to disallow such actions. Setting this 35803feature causes Alpine to remain silent when this part of lock creation fails. 35804<P> 35805WARNING: systems that have been configured in a way that precludes locking 35806introduce some risk of mail folder corruption when more than one program 35807attempts to modify the mail folder. This is most likely to occur to one's 35808INBOX or other incoming message folder. 35809<P> 35810See also <A HREF="h_info_on_locking">"What Systems Managers Need to Know about Alpine File Locking"</A>. 35811<P> 35812<UL> 35813<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35814</UL><P> 35815<End of help on this topic> 35816</BODY> 35817</HTML> 35818====== h_config_enable_role_take ====== 35819<HTML> 35820<HEAD> 35821<TITLE>FEATURE: <!--#echo var="FEAT_enable-rules-under-take"--></TITLE> 35822</HEAD> 35823<BODY> 35824<H1>FEATURE: <!--#echo var="FEAT_enable-rules-under-take"--></H1> 35825 35826Normally, the Take command takes addresses from a message and helps you 35827put them into your Address Book. 35828If you use Rules for Indexcolors, Roles, Filtering, or Scoring; 35829you may find it useful 35830to be able to Take information from a message's headers and put it into 35831a new Rule. 35832When this feature is set, you will be given an extra prompt that gives 35833you the choice to Take into the Address Book or Take into a rule. 35834<P><UL> 35835<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35836</UL> 35837<P> 35838<End of help on this topic> 35839</BODY> 35840</HTML> 35841====== h_config_enable_take_export ====== 35842<HTML> 35843<HEAD> 35844<TITLE>FEATURE: <!--#echo var="FEAT_enable-take-export"--></TITLE> 35845</HEAD> 35846<BODY> 35847<H1>FEATURE: <!--#echo var="FEAT_enable-take-export"--></H1> 35848 35849Normally, the Take command takes addresses from a message and helps you 35850put them into your Address Book. 35851When this feature is set, you will be given an extra prompt that gives you 35852the choice to Take addresses into a file instead of your Address 35853Book. 35854Only the user@domain_name part of the address is put in the file. 35855<P><UL> 35856<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35857</UL> 35858<P> 35859<End of help on this topic> 35860</BODY> 35861</HTML> 35862====== h_config_quell_folder_internal_msg ====== 35863<HTML> 35864<HEAD> 35865<TITLE>FEATURE: <!--#echo var="FEAT_quell-folder-internal-msg"--></TITLE> 35866</HEAD> 35867<BODY> 35868<H1>FEATURE: <!--#echo var="FEAT_quell-folder-internal-msg"--></H1> 35869 35870This feature determines whether or not Alpine will create 35871"pseudo messages" in folders that are in standard Unix or 35872MMDF format. <P> 35873 35874Alpine will normally create these pseudo messages when they are not already 35875present in a standard Unix or MMDF folder. Their purpose is to record 35876certain mailbox state data needed for correct IMAP and POP server 35877operation, and also for Alpine to be able to mark messages as Answered when 35878the Reply has been postponed.<P> 35879 35880Sites that do not use IMAP/POP for remote mail access, and that need to 35881support mail tools that are adversely affected by the presence of the 35882pseudo-messages (e.g. some mail notification tools) may enable this 35883feature to tell Alpine not to create them. Note that Alpine's 35884"Answered" flag 35885capability will be adversely affected if this is done.<P> 35886 35887Note too that, even if this feature is enabled, Alpine will not remove 35888pseudo-messages when it encounters them (e.g. those created by UW's imapd 35889or ipopd servers.) This feature has no effect on folders that are not in 35890standard Unix or MMDF format, as pseudo-messages are not needed in the 35891other formats to record mailbox state information. 35892<P><UL> 35893<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35894</UL> 35895<P> 35896<End of help on this topic> 35897</BODY> 35898</HTML> 35899====== h_config_mulnews_as_typed ====== 35900<HTML> 35901<HEAD> 35902<TITLE>FEATURE: <!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></TITLE> 35903</HEAD> 35904<BODY> 35905<H1>FEATURE: <!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></H1> 35906 35907This feature will be of little use to most users. 35908It has no effect unless the feature 35909<A HREF="h_config_enable_mulnewsrcs"><!--#echo var="FEAT_enable-multiple-newsrcs"--></A> 35910is set. 35911 35912When the <!--#echo var="FEAT_enable-multiple-newsrcs"--> feature is set 35913then the setting of this feature may have an effect on the names of the 35914newsrc files used. 35915Normally, the name of the news server will be canonicalized before it is 35916used in the newsrc file name. 35917For example, if you type the news server name 35918 35919<P> 35920<CENTER><SAMP>servername</SAMP></CENTER> 35921<P> 35922 35923it is likely that the canonical name will be something like 35924 35925<P> 35926<CENTER><SAMP>servername.example.com</SAMP></CENTER> 35927<P> 35928 35929Or it may be the case that 35930 35931<P> 35932<CENTER><SAMP>servername.example.com</SAMP></CENTER> 35933<P> 35934 35935is really an alias (a DNS CNAME) for 35936 35937<P> 35938<CENTER><SAMP>othername.example.com</SAMP></CENTER> 35939<P> 35940 35941If this feature is not set, then the canonicalized names will be used. 35942If this feature is set, then the name you typed in (or put in your 35943configuration) will be used. 35944 35945<P><UL> 35946<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35947</UL> 35948<P> 35949<End of help on this topic> 35950</BODY> 35951</HTML> 35952====== h_config_quell_empty_dirs ====== 35953<HTML> 35954<HEAD> 35955<TITLE>FEATURE: <!--#echo var="FEAT_quell-empty-directories"--></TITLE> 35956</HEAD> 35957<BODY> 35958<H1>FEATURE: <!--#echo var="FEAT_quell-empty-directories"--></H1> 35959 35960This feature causes Alpine to remove from the display any directories 35961that do not contain at least one file or directory. This can be useful 35962to prevent overly cluttered folder lists when a collection is stored on 35963a server that treats all names as both a folder and a directory. 35964 35965<P> 35966Note, enabling this feature can cause surprising behavior! For example, 35967you can still use Add to create a directory, but unless you immediately 35968enter that directory and create a folder, that newly created directory 35969may not be displayed next time you enter the folder list. 35970 35971<P> 35972The description above is not quite correct. 35973Only directories which potentially may hold messages are hidden if empty. 35974That is, a directory which is really just a directory and is not selectable 35975as a folder will not be hidden. 35976Such directories can occur on servers that treat most names as both a folder 35977and a directory. 35978These directories are typically created implicitly when a folder is created 35979inside a directory that does not yet exist. 35980 35981<P> 35982<UL> 35983<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 35984</UL><P> 35985<End of help on this topic> 35986</BODY> 35987</HTML> 35988====== h_config_termcap_wins ===== 35989<HTML> 35990<HEAD> 35991<TITLE>FEATURE: <!--#echo var="FEAT_termdef-takes-precedence"--></TITLE> 35992</HEAD> 35993<BODY> 35994<H1>FEATURE: <!--#echo var="FEAT_termdef-takes-precedence"--></H1> 35995 35996This feature may affect Alpine's low-level input routines. Termcap (or 35997terminfo, depending on how your copy of Alpine was compiled and linked) 35998is the name of the database that describes terminal capabilities. In 35999particular, it describes the sequences of characters that various keys 36000will emit. 36001 36002<P> 36003An example would be the Up Arrow key on the keyboard. Up 36004Arrow is not a distinct character on most Unix systems. When you press 36005the Up Arrow key a short sequence of characters are produced. This 36006sequence is supposed to be described in the termcap database by the 36007"ku" capability (or by the "kcuu1" capability if you 36008are using terminfo instead of termcap). 36009 36010<P> 36011By default, Alpine defines some terminal 36012escape sequences that are commonly used. For example, the sequence 36013"ESC O A" is recognized as an Up Arrow key. The sequence 36014"ESC [ A" 36015is also recognized as an Up Arrow key. These are chosen because common 36016terminals like VT100's or ANSI standard terminals produce these 36017sequences when you press the Up Arrow key. 36018 36019<P> 36020If your system's termcap 36021(terminfo) database assigns some other function to the sequence 36022"ESC O A" 36023it is usually ignored by Alpine. Also, if your termcap (terminfo) 36024database assigns a sequence that doesn't begin with an escape 36025character (<SAMP>ESC</SAMP>) it is usually ignored by Alpine. 36026This usually works fine 36027because most terminals emit the escape sequences that Alpine has defined 36028by default. We have also found that it is usually better to have these 36029defaults take precedence over the definitions contained in the database 36030because the defaults are more likely to be correct than the database. 36031 36032<P> 36033There are some terminals where this breaks down. If you want Alpine to 36034believe the definitions given in your termcap (terminfo) database in 36035preference to the defaults the Alpine itself sets up, then you may turn 36036this feature on. Then, sequences of characters that are defined in 36037both termcap (terminfo) and in Alpine's set of defaults will be 36038interpreted the way that termcap (terminfo) says they should be 36039interpreted. Also, if your terminal capabilities database assigns a 36040sequence that doesn't begin with escape, it will not be ignored. 36041 36042<P> 36043<UL> 36044<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 36045</UL><P> 36046<End of help on this topic> 36047</BODY> 36048</HTML> 36049====== h_config_cruise_mode ===== 36050<HTML> 36051<HEAD> 36052<TITLE>FEATURE: <!--#echo var="FEAT_enable-cruise-mode"--></TITLE> 36053</HEAD> 36054<BODY> 36055<H1>FEATURE: <!--#echo var="FEAT_enable-cruise-mode"--></H1> 36056 36057This feature affects Alpine's behavior when you hit the 36058"Space Bar" at 36059the end of a displayed message. Typically, Alpine complains that the end 36060of the text has already been reached. Setting this feature causes such 36061keystrokes to be interpreted as if the "Tab" key had been hit, thus 36062taking you to the next "interesting" message, 36063or scanning ahead to the 36064next incoming folder with "interesting" messages. 36065 36066<P> 36067<UL> 36068<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 36069</UL><P> 36070<End of help on this topic> 36071</BODY> 36072</HTML> 36073====== h_config_cruise_mode_delete ===== 36074<HTML> 36075<HEAD> 36076<TITLE>FEATURE: <!--#echo var="FEAT_enable-cruise-mode-delete"--></TITLE> 36077</HEAD> 36078<BODY> 36079<H1>FEATURE: <!--#echo var="FEAT_enable-cruise-mode-delete"--></H1> 36080 36081This feature modifies the behavior of Alpine's 36082<A HREF="h_config_cruise_mode">"<!--#echo var="FEAT_enable-cruise-mode"-->"</A> feature. 36083Setting this feature causes Alpine to implicitly delete read 36084messages when it moves on to display the next "interesting" message. 36085<P> 36086NOTE: Beware when enabling this feature AND the 36087<A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A> 36088feature. 36089<P> 36090<UL> 36091<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 36092</UL><P> 36093<End of help on this topic> 36094</BODY> 36095</HTML> 36096====== h_config_slash_coll_entire ===== 36097<HTML> 36098<HEAD> 36099<TITLE>FEATURE: <!--#echo var="FEAT_slash-collapses-entire-thread"--></TITLE> 36100</HEAD> 36101<BODY> 36102<H1>FEATURE: <!--#echo var="FEAT_slash-collapses-entire-thread"--></H1> 36103 36104The slash (/) command is available from the MESSAGE INDEX screen when 36105the folder is sorted by either Threads or OrderedSubject, and the 36106<A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A> 36107is set to something other than "none". 36108Normally, the slash command Collapses or Expands the subthread that 36109starts at the currently highlighted message, if any. 36110If this option is set, then the slash command Collapses or Expands the 36111<EM>entire</EM> current thread instead of just the subthread. 36112The current thread is simply the top-level thread that contains the 36113current message. 36114 36115<P> 36116<UL> 36117<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 36118</UL><P> 36119<End of help on this topic> 36120</BODY> 36121</HTML> 36122====== h_config_color_thrd_import ===== 36123<HTML> 36124<HEAD> 36125<TITLE>FEATURE: <!--#echo var="FEAT_thread-index-shows-important-color"--></TITLE> 36126</HEAD> 36127<BODY> 36128<H1>FEATURE: <!--#echo var="FEAT_thread-index-shows-important-color"--></H1> 36129 36130This option affects only the THREAD INDEX screen. 36131Whether or not you ever see a THREAD INDEX screen depends on the setting 36132of the configuration option 36133<A HREF="h_config_thread_index_style">"<!--#echo var="VAR_threading-index-style"-->"</A> 36134and on the sort order of the index. 36135 36136<P> 36137If a message within a thread is flagged as Important 36138and this option is set, then 36139the entire line in the THREAD INDEX will be colored the color of the 36140Index-important Symbol, which can be set using the 36141<A HREF="h_color_setup">Setup Kolor</A> screen. 36142 36143<P> 36144<UL> 36145<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 36146</UL><P> 36147<End of help on this topic> 36148</BODY> 36149</HTML> 36150====== h_config_allow_goto ===== 36151<HTML> 36152<HEAD> 36153<TITLE>FEATURE: <!--#echo var="FEAT_enable-goto-in-file-browser"--></TITLE> 36154</HEAD> 36155<BODY> 36156<H1>FEATURE: <!--#echo var="FEAT_enable-goto-in-file-browser"--></H1> 36157 36158This feature modifies the behavior of Alpine's file browser. Setting this 36159feature causes Alpine to offer the "G Goto" command in the file browser. 36160That is the default. 36161 36162<P> 36163 36164The Goto command allows you to explicitly type in the desired directory. 36165<P> 36166<End of help on this topic> 36167</BODY></HTML> 36168====== h_config_add_ldap ===== 36169<HTML> 36170<HEAD> 36171<TITLE>FEATURE: <!--#echo var="FEAT_ldap-result-to-addrbook-add"--></TITLE> 36172</HEAD> 36173<BODY> 36174<H1>FEATURE: <!--#echo var="FEAT_ldap-result-to-addrbook-add"--></H1> 36175 36176If both the Directory option 36177<A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A> 36178and this feature are set, 36179then when an implicit directory lookup is done from the 36180composer you will automatically be prompted to add the result of the 36181directory lookup to your address book. 36182<P> 36183<UL> 36184<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 36185</UL><P> 36186<End of help on this topic> 36187</BODY> 36188</HTML> 36189===== h_patterns_compat_behavior ===== 36190<HTML> 36191<HEAD> 36192<TITLE>Rules Behavior Changes in Pine 4.50</TITLE> 36193</HEAD> 36194<BODY> 36195<H1>Rules Behavior Changes in Pine 4.50</H1> 36196 36197In Alpine, Rules that contain unrecognized elements 36198are ignored. 36199In most cases, the unrecognized elements will be something that was 36200added as a new Rules feature in a later version of Alpine. 36201In versions of Pine <EM>prior</EM> to 4.50, Pine did <EM>not</EM> 36202ignore rules that contained unrecognized elements. 36203For example, a new element of Rules that was added in Pine 4.50 is 36204Age interval. 36205Suppose you add an Indexcolor rule, using version Pine 4.50 or later, that colors 36206all messages older than a week red. 36207Now, if you run Pine 4.44 using that same configuration file, it will not 36208recognize the Age interval and so will just ignore it. 36209That means that all messages will match that rule so all messages will 36210be colored red when using Pine version 4.44. 36211 36212<P> 36213This behavior was considered a bug so it is fixed in Alpine and Pine 4.50 and later. 36214However, since the behavior still exists in versions prior to Pine 4.50 and 36215since Filtering is a potentially destructive operation, another measure 36216was taken to attempt to avoid unintentional Filtering of messages. 36217The first time that you run Alpine or a Pine that is version 4.50 or greater, 36218the rules in your Filters configuration variable ("Patterns-Filters") 36219will be copied to a new Filters configuration variable 36220with a different name ("Patterns-Filters2"). 36221From then on, Alpine will continue to use the new 36222variable. 36223Of course, Pine version 4.44 or lower will continue to use the old 36224variable. 36225That means that if you are using Alpine 36226and also using a version of Pine that is older than 4.50, they will not 36227share the configuration information about Filters. 36228If you make a change in one version you won't see it in the other version. 36229 36230<P> 36231Since Scoring can be used to trigger Filtering, the same thing has been 36232done for Score rules. 36233The old configuration variable name is ("Patterns-Scores") 36234and the new name is ("Patterns-Scores2"). 36235The same is not true of Role, Indexcolor, and Other rules that are 36236thought to be less harmful when a mistake is made. 36237 36238<P> 36239<End of help on this topic> 36240</BODY> 36241</HTML> 36242======= h_config_filt_opts_sentdate ======= 36243<HTML> 36244<HEAD> 36245<TITLE>PATTERN FEATURE: Use-Date-Header-For-Age</TITLE> 36246</HEAD> 36247<BODY> 36248<H1>PATTERN FEATURE: Use-Date-Header-For-Age</H1> 36249 36250By default, the Age interval of a Pattern uses a message's time of 36251arrival to compute the age of the message. 36252If this feature is set, the date in the message's Date header will 36253be used instead. 36254<P> 36255<End of help on this topic> 36256</BODY> 36257</HTML> 36258======= h_config_filt_opts_notdel ======= 36259<HTML> 36260<HEAD> 36261<TITLE>FILTER FEATURE: Move-Only-if-Not-Deleted</TITLE> 36262</HEAD> 36263<BODY> 36264<H1>FILTER FEATURE: Move-Only-if-Not-Deleted</H1> 36265 36266If this option is set then a message will be moved into the 36267specified folder only if it is not marked for deletion. 36268This is useful if you have multiple Alpine sessions running 36269simultaneously and you don't want messages to be filtered into a 36270folder more than once. 36271It is also useful if you want to filter 36272only the "undeleted" messages in a newsgroup into a folder. 36273This method is not foolproof. 36274There may be cases where a message 36275gets marked deleted and so it is never filtered into the folder. 36276For example, if you deleted it in another Alpine session or another mail 36277program that didn't use the filtering rule. 36278<P> 36279This option has no effect if the Filter Action is not set to Move. 36280<P> 36281<End of help on this topic> 36282</BODY> 36283</HTML> 36284======= h_config_filt_opts_nonterm ======= 36285<HTML> 36286<HEAD> 36287<TITLE>FILTER FEATURE: Dont-Stop-Even-if-Rule-Matches</TITLE> 36288</HEAD> 36289<BODY> 36290<H1>FILTER FEATURE: Dont-Stop-Even-if-Rule-Matches</H1> 36291 36292If this option is set then this is a non-terminating rule. 36293Usually, for each message, Alpine searches through the Filter Rules until 36294a match is found and then it performs the action associated with that rule. 36295Rules following the match are not considered. 36296If this option is set then the search for matches will continue at the next 36297rule. 36298<P> 36299If a non-terminating rule matches then the actions associated with 36300that rule, except for any implied deletion of the message, are performed 36301before the match for the next rule is checked. 36302For example, if the non-terminating rule sets the Important status, then that 36303status will be set when the next rule is considered. 36304However, if the non-terminating rule Moves the message, the message will 36305actually be copied instead of copied and deleted so that it is still there 36306for the next rule. 36307A moved message is deleted after all the relevant rules have been checked. 36308The name of the "Move" action is confusing in this case because 36309a single message can be moved to more than one folder. 36310It turns the Move into a Copy instead, but it is still followed by a deletion 36311at the end. 36312<P> 36313This option may be useful if you want to have a single message filtered to 36314two different folders because it matches two different Patterns. 36315For example, suppose you normally filter messages to a particular mailing 36316list into one folder, and messages addressed directly to you into a second 36317folder. 36318If a message is sent to both you and the list (and you can tell that by 36319looking at the headers of the message) this option may give you a convenient 36320way to capture a copy to each folder. 36321(It may also cause you to capture two copies to each folder, 36322depending on whether your mail system delivers one or two copies of the 36323message to you and on how the list works.) 36324<P> 36325<End of help on this topic> 36326</BODY> 36327</HTML> 36328====== h_command_external_browser ===== 36329<HTML> 36330<HEAD> 36331<TITLE>The External Browser Command</TITLE> 36332</HEAD> 36333<BODY> 36334<H1>The External Browser Command</H1> 36335 36336<P> 36337A new command was added to Alpine that allows users to send HTML messages to be displayed 36338by a web browser. This is helpful when a user wants to see images in the context of the 36339message, or get a better display of the message than Alpine provides. 36340 36341<P> 36342The simplest way to use this command is to do as follows. While reading a message, 36343press the "V" to go to the <A href="h_attachment_screen">ATTACHMENT SCREEN</A>. 36344In that screen move the cursor until it is on top of a TEXT/HTML attachment and press the 36345"X" key. This will make Alpine launch the browser you have configured for 36346in the <a href="h_config_browser"><!--#echo var="VAR_url-viewers"--></a> variable, and 36347you should be able to read the message in your browser, as well as in Alpine. 36348 36349<P> If the message you sent to your browser has inline images, then the images attached to 36350the message that are necessary for the display of the message are also sent to the browser 36351for its display. 36352 36353<P> The text that follows will explain more details about this command, and is only 36354recommended for more advanced users. 36355 36356<h1><CENTER>Displaying Images</CENTER></h1> 36357 36358<P> First, we will talk about displaying images in an HTML file. Typically, HTML images 36359are displayed as the result of some specific code of the form 36360<center> 36361<PRE> 36362<img src="...">, 36363</PRE> 36364</center> 36365where the text between the quotes tells Alpine how to find the image. 36366If the source of the image is internal to the message, Alpine passes that image to the 36367browser. Otherwise Alpine erases the link to the image. This is done so that 36368you can be protected from a bad use of external images. Images can be used to track 36369that you read the message, or your location, devices you own, etc.. Since Alpine does 36370not open images in any messages, your 36371privacy is always protected this way. Therefore, when you do not pass the links to 36372external images to a browser, your privacy is being protected. However, doing this 36373might make the message not be displayed correctly, since when the message was 36374created the images were part of the formatted message, and not having images might make 36375this formatting look awkward. 36376 36377<P> If you would like that Alpine display all images, regardless of their source, and 36378regardless of the sender, then you need to disable the feature <a 36379href="h_external_loads_inline_images_only"><!--#echo var="FEAT_external-command-loads-inline-images-only"--></a>. 36380The message will display as intended, but you will leak information to the sender of the 36381message, as well as to your internet service provider, which could be your employer, or 36382school, etc. 36383 36384<P> Alpine provides an alternative mechanism to either send all links to the images to the 36385external browser or to send only those that are attached to the message you are trying to 36386display. In order to use this mechanism you must first enable 36387<a href="h_config_enable_view_attach"><!--#echo var="FEAT_enable-msg-view-attachments"--></a>. 36388This allows Alpine to add direct links to each attachments. If you want to send an HTML 36389attachment to an external browser, you would place the cursor over the attachment and press 36390the "Return" or "Enter" key to open the attachment. When you do that 36391you will see a prompt and menu which says 36392 36393<pre> 36394View selected Attachment ? 36395 Y [Yes] X External 36396^C Cancel N No 36397</pre> 36398 36399<P>In order to send this message to an external browser, you would press the "X" 36400key. This will change the prompt and menu to 36401 36402<pre> 36403View selected Attachment using external viewer including inline images only ? 36404 Y [Yes] X No eXternal 36405^C Cancel N No I All images 36406</pre> 36407 36408<P>This is telling you that if you answer "Yes" to this question, and external 36409browser will be used to send this messages, and only inline images, that is, those attached 36410in the message will be sent to the browser. If you would like to send all images in 36411this case, the menu tells you that you must press the "I" key. Pressing 36412that key changes the prompt and menu to 36413 36414<pre> 36415View selected Attachment using external viewer including all images ? 36416 Y [Yes] X No eXternal 36417^C Cancel N No I Inline imgs 36418</pre> 36419 36420<P>and as you can see the prompt says that if you press "Yes" then the message 36421will be sent to the browser including the source of all images, including those in 36422external servers. Notice that the "X" command now is a toggle. If you 36423were to press it now, you would return to the original prompt, 36424 36425<pre> 36426View selected Attachment ? 36427 Y [Yes] X External 36428^C Cancel N No 36429</pre> 36430 36431<P>which means that if you answer "Yes" at this time your message would not 36432be sent to your external browser for display, unless you have configured a mailcap 36433entry to display HTML files. 36434 36435<P> One of the lessons of this discussion is that if you never press the "X" 36436command in the ATTACHMENT SCREEN, and you never press the "X" command when 36437launching a viewer for an attachment in the MESSAGE TEXT screen, you will never use this 36438mechanism, and Alpine will resort to your already configured mechanisms to open HTML 36439text.This means you can live your life without worrying that Alpine will do anything 36440different because of this new feature. You do not have to use it, but if you do, you should 36441know the risks and advantages and decide when and how to use it. 36442 36443<h1><CENTER>Saving HTML Messages to Disk</CENTER></h1> 36444 36445<P> 36446No matter what your reason to send a message to an external web browser is, Alpine must 36447write your message to a file (and also all related inline images), and point your browser 36448to open that file. Alpine saves all your messages and auxiliary images in a subdirectory 36449of the ~/.alpine-html directory in unix-like Alpine, or the alpine-html folder in your home 36450directory in PC-Alpine. If Alpine cannot access these directories, or create folders 36451in them, then the full mechanism described above will fail, and you will not be able 36452to send messages to an external browser for display. 36453 36454<P> 36455Unfortunately browsers do not remove the file that Alpine created, nor the images 36456that Alpine saved in order to display this message, so if you use this mechanism often 36457you will create many directories and files which the browser will not remove. Alpine 36458will remove these files when you exit Alpine. Any temporary directory that Alpine 36459created that has existed for longer than 10 minutes will be automatically erased. 36460Alpine also erases these directories upon exiting. 36461 36462<P> 36463When Alpine creates a directory to house the files associated to a message that will 36464pass to an external browser, it tries to delete that directory later on, according to 36465the discussion above. What this means is that you should consider the contents of the 36466~/.alpine-html directory in unix-like Alpine and the alpine-html folder in PC-Alpine 36467as temporary, and not rely on their existence. If you attempt to save files in one of 36468these directories, chances are your data will be deleted by Alpine. Since deleting is 36469a destructive action, 36470every session of Alpine that you have open will only attempt to remove the directories 36471it created, with their content in them. If this operation fails, Alpine will not try 36472to investigate, nor will report to you, why the operation failed. Therefore, users 36473should periodically check their html directory to see if there is content there that 36474they wish to delete. 36475 36476<P> 36477<UL> 36478<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 36479</UL><P> 36480<End of help on this topic> 36481</BODY> 36482</HTML> 36483===== h_mainhelp_smime ====== 36484<HTML> 36485<HEAD> 36486<TITLE>S/MIME Overview</TITLE> 36487</HEAD> 36488<BODY> 36489<H1>S/MIME Overview</H1> 36490 36491S/MIME is a standard for the public key encryption and signing of email. 36492UNIX Alpine contains a basic implementation of S/MIME based on 36493the <A HREF="http://www.openssl.org/">OpenSSL</A> libraries. The 36494same support can be provided using the 36495<A HREF="http://www.libressl.org/">LibreSSL</A> libraries. The 36496support for S/MIME in PC-Alpine is fully based on the LibreSSL libraries. 36497To check if this version of Alpine supports S/MIME look at 36498<A HREF="X-Alpine-Config:">Supported Options in this Alpine</A> and look 36499for "S/MIME" under the "Encryption" heading. 36500<P> 36501Some limitations: 36502<UL> 36503 <LI> There is no provision for checking for CRLs 36504 (Certificate Revocation Lists) in Alpine. 36505 <LI> This built-in S/MIME implementation is not compatible with and does not help with PGP. 36506 <LI> There is no mechanism available for feeding either an entire incoming 36507 or an entire outgoing message to an external 36508 filter and using that external filter to do S/MIME or PGP processing. 36509 <LI> Because the implementation currently uses OpenSSL, there is only a very 36510 limited integration with the Mac OS Keychain (the storing and access of 36511 public certificates). 36512</UL> 36513<P> 36514The S/MIME configuration screen is reached by going to the Main Menu and typing 36515the "S Setup" command followed by "M S/MIME". 36516<P> 36517 36518<H2>S/MIME BASICS</H2> 36519 36520In order to digitally sign messages you send you must have a public/private key-pair. 36521This may be obtained from a public Certificate Authority (CA) such as Thawte, Verisign, Comodo, 36522or GoDaddy; or from a smaller CA such as a university which provides certificates for its 36523users or a company which provides certificates for its workers. 36524These certificates are bound to an email address, so the identity being verified is the 36525email address not a person's name. 36526<P> 36527Mail is signed by using the sender's private key, which only the owner of the private key 36528has access to. 36529The signature is verified using the signer's public key, which anyone can 36530have access to. 36531With Alpine, the first time you receive a signed message the public key of the 36532sender will be stored for future use. 36533 36534<P> 36535Mail is encrypted using the recipient's public key and decrypted by 36536the recipient with their private key. 36537 36538<P> 36539You need a key of your own in order to sign outgoing messages and to have others 36540encrypt messages sent to you. 36541You do not need a key of your own to verify signed messages sent by others or to 36542encrypt messages sent to others. 36543 36544<H2>ALPINE S/MIME CERTIFICATE STORAGE</H2> 36545 36546By default UNIX Alpine stores the certificates it uses in a directory in your 36547home directory. 36548The directory name is 36549<P> 36550<CENTER><SAMP>.alpine-smime</SAMP></CENTER> 36551<P> 36552For PC-Alpine, the equivalent directory is called 36553<CENTER><SAMP>alpine-smime</SAMP></CENTER> 36554and is also located under your home directory. 36555<P> 36556Within that directory are three subdirectories. 36557Each of the three subdirectories contains files with PEM-encoded contents, 36558the default format for OpenSSL. 36559The "<SAMP>public</SAMP>" directory contains public certificates. 36560The files within that directory have names that are email addresses with the 36561suffix "<SAMP>.crt</SAMP>" appended. 36562An example filename is 36563<P> 36564<CENTER><SAMP>user@example.com.crt</SAMP></CENTER> 36565<P> 36566The "<SAMP>private</SAMP>" directory contains private keys, probably just one for 36567your private key. 36568These are also email addresses but with the suffix "<SAMP>.key</SAMP>" instead. 36569The third directory is "<SAMP>ca</SAMP>" and it contains certificates for any Certificate 36570Authorities that you want to trust but that aren't contained in the set of system CAs. 36571Those files may have arbitrary names as long as they end with the 36572suffix "<SAMP>.crt</SAMP>". 36573 36574<H2>HOW TO SIGN AND ENCRYPT</H2> 36575 36576If you have a certificate you may sign outgoing messages. 36577After typing the Ctrl-X command to send a message you will see the prompt 36578<P> 36579<CENTER><SAMP>Send message?</SAMP></CENTER> 36580<P> 36581Available subcommands include "G Sign" and "E Encrypt". 36582Typing the "G" command will change the prompt to 36583<P> 36584<CENTER><SAMP>Send message (Signed)?</SAMP></CENTER> 36585<P> 36586Typing the "E" command will change the prompt to 36587<P> 36588<CENTER><SAMP>Send message (Encrypted)?</SAMP></CENTER> 36589<P> 36590You may even type both to get 36591<P> 36592<CENTER><SAMP>Send message (Encrypted, Signed)?</SAMP></CENTER> 36593<P> 36594 36595<H2>HOW TO READ SIGNED OR ENCRYPTED MESSAGES</H2> 36596 36597The reading of a signed message should not require any special action on 36598your part. 36599There should be an editorial addition at the start of the message which 36600says either 36601<P> 36602<CENTER><SAMP>This message was cryptographically signed.</SAMP></CENTER> 36603<P> 36604or 36605<P> 36606<CENTER><SAMP>This message was cryptographically signed but the signature could not be verified.</SAMP></CENTER> 36607<P> 36608If an encrypted message is sent to you the encrypted text will not 36609be shown. 36610You will have to type the "Ctrl-D Decrypt" command (from the screen where 36611you are viewing the message) and supply your passphrase when asked. 36612<P> 36613For a signed or encrypted message there is also a "Ctrl-E Security" command 36614which gives you some information about the certificate used to sign or encrypt the message. 36615 36616<H2>MISCELLANEOUS</H2> 36617 36618If you have access to a private certificate in the PKCS12 format, which 36619would sometimes be in a file with a ".p12" extension, then you can 36620use the following commands to generate private keys, public and certificate 36621authorities certificates. In the examples below, we assume that the 36622certificate in the p12 format is called "certificate.p12", and 36623that your email address is "your@address.com". 36624 36625<P> 36626In order to create a private key use the command 36627<P> 36628<CENTER><SAMP>openssl pkcs12 -in certificate.p12 -out your@address.com.key</SAMP></CENTER> 36629<P> 36630In order to create a public certificate use the command 36631<P> 36632<CENTER><SAMP> 36633openssl pkcs12 -in certificate.p12 -clcerts -nokeys -out your@address.com.crt 36634</SAMP></CENTER> 36635<P> 36636In order to create a certificate authority certificate use the command 36637<P> 36638<CENTER><SAMP> 36639openssl pkcs12 -in certificate.p12 -cacerts -nokeys -out certificate-ca.crt 36640</SAMP></CENTER> 36641 36642<P> If the previous command produces an empty file, it means that the 36643certificate authority was not included in the .p12 file, so you will have 36644to get it from some other sources. You will need these certificates, so 36645that you can validate correctly signatures. 36646 36647<P> 36648After you have exported these certificates and keys, you can use the import 36649command in Alpine, from the S/MIME configuration screen, 36650to import these certificates into Alpine. They will be available for use 36651as soon as you import them. 36652<P> 36653<End of help on this topic> 36654</BODY> 36655</HTML> 36656====== h_config_smime_pubcertdir ===== 36657<HTML> 36658<HEAD> 36659<TITLE>S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-directory"--></TITLE> 36660</HEAD> 36661<BODY> 36662<H1>S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-directory"--></H1> 36663 36664<P> 36665If the option 36666<A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A> 36667is set then this option will have no effect. 36668<P> 36669Normally, Public Certificates for use with S/MIME will be stored in the directory 36670which is the value of this option. 36671Those certificates will be stored in PEM format, one certificate per file. 36672The name of the file for the certificate corresponding to 36673<P> 36674<CENTER><SAMP>emailaddress</SAMP></CENTER> 36675<P> 36676should be 36677<P> 36678<CENTER><SAMP>emailaddress.crt</SAMP></CENTER> 36679<P> 36680For example, a file for user@example.com would be in the file 36681<P> 36682<CENTER><SAMP>user@example.com.crt</SAMP></CENTER> 36683<P> 36684in this directory. 36685<P> 36686Use the Setup/SMIME screen to modify this variable. 36687<P> 36688Typically, the public certificates that you have will come from S/MIME signed 36689messages that are sent to you. 36690Alpine will extract the public certificate from the signed message and store 36691it in the certificates directory. 36692These PEM format public certificates look something like: 36693<PRE> 36694-----BEGIN CERTIFICATE----- 36695MIIFvTCCBKWgAwIBAgIQD4fYFHVI8T20yN4nus097DANBgkqhkiG9w0BAQUFADCB 36696rjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2Ug 36697Q2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExho 36698... 366992b9KGqDyMWW/rjNnmpjzjT2ObGM7lRA8lke4FLOLajhrz4ogO3b4DFfAAM1VSZH8 36700D6sOwOLJZkLY8FRsfk63K+2EMzA2+qAzMKupgeTLqXIf 36701-----END CERTIFICATE----- 36702</PRE> 36703<P> 36704<UL> 36705<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 36706</UL><P> 36707<P> 36708<UL> 36709<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 36710</UL><P> 36711<End of help on this topic> 36712</BODY> 36713</HTML> 36714====== h_config_smime_pubcertcon ===== 36715<HTML> 36716<HEAD> 36717<TITLE>OPTION: <!--#echo var="VAR_smime-public-cert-container"--></TITLE> 36718</HEAD> 36719<BODY> 36720<H1>OPTION: <!--#echo var="VAR_smime-public-cert-container"--></H1> 36721 36722<P> 36723If this option is set it will be used instead of 36724<A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>. 36725<P> 36726This option gives you a way to store certificates remotely on an IMAP server 36727instead of storing the certificates one per file locally. 36728In order to do that you just give this option a remote folder name for a folder 36729which does not yet exist. 36730The name is similar to the name you might use for a remote configuration file. 36731A remote folder name might look something like: 36732<P> 36733<CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/publiccerts</SAMP></CENTER> 36734<P> 36735See 36736<A HREF="h_valid_folder_names">Valid Folder Names</A> for more information 36737about the syntax of folder names. 36738<P> 36739Use the Setup/SMIME screen to modify this variable. 36740<P> 36741<UL> 36742<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 36743</UL><P> 36744<P> 36745<UL> 36746<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 36747</UL><P> 36748<End of help on this topic> 36749</BODY> 36750</HTML> 36751====== h_config_smime_privkeydir ===== 36752<HTML> 36753<HEAD> 36754<TITLE>OPTION: <!--#echo var="VAR_smime-private-key-directory"--></TITLE> 36755</HEAD> 36756<BODY> 36757<H1>OPTION: <!--#echo var="VAR_smime-private-key-directory"--></H1> 36758 36759<P> 36760In order to sign outgoing S/MIME messages you will need a 36761personal digital ID certificate. 36762You will usually get such a certificate from a certificate authority such as 36763Thawte or CAcert. 36764(In order to encrypt outgoing messages you don't need a personal digital ID, you 36765need the public certificate of the recipient instead.) 36766If the option 36767<A HREF="h_config_smime_privkeycon"><!--#echo var="VAR_smime-private-key-container"--></A> 36768is set then this option will have no effect. 36769<P> 36770Normally, Private Keys for use with S/MIME will be stored in the directory 36771which is the value of this option. 36772Those certificates will be stored in PEM format, one certificate per file. 36773The name of the file for the certificate corresponding to your 36774<P> 36775<CENTER><SAMP>emailaddress</SAMP></CENTER> 36776<P> 36777should be 36778<P> 36779<CENTER><SAMP>emailaddress.key</SAMP></CENTER> 36780<P> 36781For example, if your address is user@example.com the name of the file would be 36782<P> 36783<CENTER><SAMP>user@example.com.key</SAMP></CENTER> 36784<P> 36785in this directory. 36786<P> 36787Use the Setup/SMIME screen to modify this variable. 36788<P> 36789Typically, the private key that you have will come from a Certificate 36790Authority. 36791The private key should be stored in a PEM format file that 36792looks something like: 36793<PRE> 36794-----BEGIN RSA PRIVATE KEY----- 36795Proc-Type: 4,ENCRYPTED 36796DEK-Info: DES-EDE3-CBC,2CBD328FD84CF5C6 36797 36798YBEXYLgLU9NJoc1V+vJ6UvcF08RX54S6jXsmgL0b5HGkudG6fhnmHkH7+UCvM5NI 36799SXO/F8iuZDfs1VGG0NyitkFZ0Zn2vfaGovBvm15gx24b2xnZDLRB7/bNZkurnK5k 36800VjAjZ2xXn2hFp2GJwqRdmxYNqsKGu52B99oti5HUWuZ2GFRaWjn5hYOqeApZE2uA 36801... 36802oSRqfI51UdSRt0tmGhHeTvybUVrHm9eKft8TTGf+qSBqzSc55CsmoVbRzw4Nfhix 36803m+4TJybNGNfAgOctSkEyY/OCb49fRRQTCBZVIhzLGGmpYmkO55HbIA== 36804-----END RSA PRIVATE KEY----- 36805</PRE> 36806<P> 36807<UL> 36808<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 36809</UL><P> 36810<P> 36811<UL> 36812<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 36813</UL><P> 36814<End of help on this topic> 36815</BODY> 36816</HTML> 36817====== h_config_smime_privkeycon ===== 36818<HTML> 36819<HEAD> 36820<TITLE>OPTION: <!--#echo var="VAR_smime-private-key-container"--></TITLE> 36821</HEAD> 36822<BODY> 36823<H1>OPTION: <!--#echo var="VAR_smime-private-key-container"--></H1> 36824 36825<P> 36826If this option is set it will be used instead of 36827<A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-directory"--></A>. 36828<P> 36829This option gives you a way to store keys remotely on an IMAP server 36830instead of storing the keys one per file locally. 36831In order to do that you just give this option a remote folder name for a folder 36832which does not yet exist. 36833The name is similar to the name you might use for a remote configuration file. 36834A remote folder name might look something like: 36835<P> 36836<CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/privatekeys</SAMP></CENTER> 36837<P> 36838See 36839<A HREF="h_valid_folder_names">Valid Folder Names</A> for more information 36840about the syntax of folder names. 36841<P> 36842Use the Setup/SMIME screen to modify this variable. 36843<P> 36844<UL> 36845<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 36846</UL><P> 36847<P> 36848<UL> 36849<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 36850</UL><P> 36851<End of help on this topic> 36852</BODY> 36853</HTML> 36854====== h_config_smime_cacertdir ===== 36855<HTML> 36856<HEAD> 36857<TITLE>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-directory"--></TITLE> 36858</HEAD> 36859<BODY> 36860<H1>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-directory"--></H1> 36861 36862<P> 36863If the option 36864<A HREF="h_config_smime_cacertcon"><!--#echo var="VAR_smime-cacert-container"--></A> 36865is set then this option will have no effect. 36866<P> 36867CACert is a shorthand name for certification authority certificate. 36868Normally Alpine will use the CACerts that are located in the standard system 36869location for CACerts. 36870It may be the case that one of your correspondents has a Digital ID which has 36871been signed by a certificate authority that is not in the regular set of system certificate 36872authorities. 36873You may supplement the system list by adding further certificates of your own. 36874These should be stored in the directory 36875which is the value of this option. 36876The certificates will be stored in PEM format, one certificate per file. 36877The names of the files can be anything ending in ".crt". 36878<P> 36879Use the Setup/SMIME screen to modify this variable. 36880<P> 36881These PEM format CA certificates look very similar to your public 36882certificates for particular email addresses 36883(<A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>). 36884<P> 36885<UL> 36886<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 36887</UL><P> 36888<P> 36889<UL> 36890<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 36891</UL><P> 36892<End of help on this topic> 36893</BODY> 36894</HTML> 36895====== h_config_smime_cacertcon ===== 36896<HTML> 36897<HEAD> 36898<TITLE>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-container"--></TITLE> 36899</HEAD> 36900<BODY> 36901<H1>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-container"--></H1> 36902 36903<P> 36904If this option is set it will be used instead of 36905<A HREF="h_config_smime_cacertdir"><!--#echo var="VAR_smime-cacert-directory"--></A>. 36906<P> 36907This option gives you a way to store certificates remotely on an IMAP server 36908instead of storing the certificates one per file locally. 36909In order to do that you just give this option a remote folder name for a folder 36910which does not yet exist. 36911The name is similar to the name you might use for a remote configuration file. 36912A remote folder name might look something like: 36913<P> 36914<CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/cacerts</SAMP></CENTER> 36915<P> 36916See 36917<A HREF="h_valid_folder_names">Valid Folder Names</A> for more information 36918about the syntax of folder names. 36919<P> 36920Use the Setup/SMIME screen to modify this variable. 36921<P> 36922<UL> 36923<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 36924</UL><P> 36925<P> 36926<UL> 36927<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 36928</UL><P> 36929<End of help on this topic> 36930</BODY> 36931</HTML> 36932========== h_config_smime_sign_by_default ========== 36933<HTML> 36934<HEAD> 36935<TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-sign-by-default"--></TITLE> 36936</HEAD> 36937<BODY> 36938<H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-sign-by-default"--></H1> 36939 36940<P> 36941This feature only has an effect if your version of Alpine includes 36942support for S/MIME. 36943It affects Alpine's behavior when you send a message. 36944If this option is set, the "Sign" option will default to ON when sending messages. 36945<P> 36946Only the default value is affected. 36947In any case, you may still toggle the Signing option on or off before sending 36948with the "G Sign" command (provided you have a personal digital ID 36949certificate). 36950<P> 36951<UL> 36952<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 36953</UL><P> 36954<P> 36955 36956<UL> 36957<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 36958</UL><P> 36959<End of help on this topic> 36960</BODY> 36961</HTML> 36962========== h_config_smime_use_cert_store ========== 36963<HTML> 36964<HEAD> 36965<TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-use-store-only"--></TITLE> 36966</HEAD> 36967<BODY> 36968<H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-use-store-only"--></H1> 36969 36970<P> 36971This feature only has an effect if your version of Alpine includes 36972support for S/MIME. 36973It affects Alpine's behavior when you validate a message, and should 36974not be disabled, unless you are performing a test. 36975<P> 36976There are two important aspects of validation: validation of the message 36977(that is, the message was not modified after it was sent) 36978as well as validation of the identity of the sender. This option has to 36979do with the latter. 36980<P> 36981In order to validate that the message came from the sender in the message 36982and not an impersonator, Alpine can 36983either use the certificates that come in the message, or the ones that 36984you have personally stored. If this feature is enabled (the default) then 36985Alpine will use certificates that you have already saved in your store 36986and not those that come in the message to validate the sender of the 36987message. In particular, the first time that you receive a signed message 36988from a sender, and their certificate does not validate against your 36989store, then you will be asked if you wish to save such certificate. If 36990you do not wish to save the certificate, then Alpine will fail to validate 36991the signature of the message. Otherwise, Alpine will proceed to validate 36992the signature of the message. This behavior helps you prevent against impersonation, because 36993it is assumed that you trust the certificates that you have saved, and 36994might not trust those that came with the message that you are validating. 36995<P> 36996<UL> 36997<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 36998</UL><P> 36999<P> 37000 37001<UL> 37002<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37003</UL><P> 37004<End of help on this topic> 37005</BODY> 37006</HTML> 37007========== h_config_smime_pubcerts_in_keychain ========== 37008<HTML> 37009<HEAD> 37010<TITLE>S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></TITLE> 37011</HEAD> 37012<BODY> 37013<H1>S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></H1> 37014 37015<P> 37016If this feature is set the Mac OS X default keychain will be used as the place 37017to store public certificates instead of a 37018<A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A> 37019or a 37020<A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>. 37021<P> 37022<UL> 37023<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 37024</UL><P> 37025<P> 37026<UL> 37027<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37028</UL><P> 37029<End of help on this topic> 37030</BODY> 37031</HTML> 37032========== h_config_smime_dont_do_smime ========== 37033<HTML> 37034<HEAD> 37035<TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-dont-do-smime"--></TITLE> 37036</HEAD> 37037<BODY> 37038<H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-dont-do-smime"--></H1> 37039 37040<P> 37041Setting this feature turns off all of Alpine's S/MIME support. 37042You might want to set this if you are having trouble due to the S/MIME support. 37043<P> 37044<UL> 37045<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 37046</UL><P> 37047<P> 37048 37049<UL> 37050<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37051</UL><P> 37052<End of help on this topic> 37053</BODY> 37054</HTML> 37055========== h_config_smime_encrypt_by_default ========== 37056<HTML> 37057<HEAD> 37058<TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-encrypt-by-default"--></TITLE> 37059</HEAD> 37060<BODY> 37061<H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-encrypt-by-default"--></H1> 37062 37063<P> 37064This feature only has an effect if your version of Alpine includes 37065support for S/MIME. 37066It affects Alpine's behavior when you send a message. 37067If this option is set, the "Encrypt" option will default to ON when sending messages. 37068<P> 37069Only the default value is affected. 37070In any case, you may still toggle the Encrypt option on or off before sending 37071with the "E Encrypt" command (provided you have a the public digital ID 37072for the recipient). 37073<P> 37074<UL> 37075<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 37076</UL><P> 37077<P> 37078 37079<UL> 37080<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37081</UL><P> 37082<End of help on this topic> 37083</BODY> 37084</HTML> 37085========== h_config_smime_remember_passphrase ========== 37086<HTML> 37087<HEAD> 37088<TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-remember-passphrase"--></TITLE> 37089</HEAD> 37090<BODY> 37091<H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-remember-passphrase"--></H1> 37092 37093<P> 37094This feature only has an effect if your version of Alpine includes 37095support for S/MIME. 37096If this option is set, you will only have to enter your passphrase for your private key 37097once during an Alpine session. 37098<P> 37099<UL> 37100<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 37101</UL><P> 37102<P> 37103 37104<UL> 37105<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37106</UL><P> 37107<End of help on this topic> 37108</BODY> 37109</HTML> 37110====== h_config_smime_transfer_pub_to_con ===== 37111<HTML> 37112<HEAD> 37113<TITLE>S/MIME: Transfer Public Certs to Container</TITLE> 37114</HEAD> 37115<BODY> 37116<H1>S/MIME: Transfer Public Certs to Container</H1> 37117 37118<P> 37119The Transfer command will copy the public certificates in your configured 37120<A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A> 37121to the container in your configured 37122<A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>. 37123This might be useful if you decide to switch from using a cert directory to a cert 37124container. 37125<P> 37126Warning: Any previous contents in the container will be lost. 37127<P> 37128<UL> 37129<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 37130</UL><P> 37131<P> 37132<UL> 37133<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37134</UL><P> 37135<End of help on this topic> 37136</BODY> 37137</HTML> 37138====== h_config_smime_transfer_pub_to_dir ===== 37139<HTML> 37140<HEAD> 37141<TITLE>S/MIME: Transfer Public Certs to Directory</TITLE> 37142</HEAD> 37143<BODY> 37144<H1>S/MIME: Transfer Public Certs to Directory</H1> 37145 37146<P> 37147The Transfer command will copy the public certificates in your configured 37148<A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A> 37149to the directory in your configured 37150<A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>. 37151This might be useful if you decide to switch from using a cert container to a cert 37152directory. 37153<P> 37154<UL> 37155<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 37156</UL><P> 37157<P> 37158<UL> 37159<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37160</UL><P> 37161<End of help on this topic> 37162</BODY> 37163</HTML> 37164====== h_config_smime_transfer_priv_to_con ===== 37165<HTML> 37166<HEAD> 37167<TITLE>S/MIME: Transfer Private Keys to Container</TITLE> 37168</HEAD> 37169<BODY> 37170<H1>S/MIME: Transfer Private Keys to Container</H1> 37171 37172<P> 37173The Transfer command will copy the private keys in your configured 37174<A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-directory"--></A>. 37175to the container in your configured 37176<A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-container"--></A>. 37177This might be useful if you decide to switch from using a key directory to a key 37178container. 37179<P> 37180Warning: Any previous contents in the container will be lost. 37181<P> 37182<UL> 37183<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 37184</UL><P> 37185<P> 37186<UL> 37187<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37188</UL><P> 37189<End of help on this topic> 37190</BODY> 37191</HTML> 37192====== h_config_smime_transfer_priv_to_dir ===== 37193<HTML> 37194<HEAD> 37195<TITLE>S/MIME: Transfer Private Keys to Directory</TITLE> 37196</HEAD> 37197<BODY> 37198<H1>S/MIME: Transfer Private Keys to Directory</H1> 37199 37200<P> 37201The Transfer command will copy the private keys in your configured 37202<A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-container"--></A>. 37203to the directory in your configured 37204<A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-directory"--></A>. 37205This might be useful if you decide to switch from using a key container to a key 37206directory. 37207<P> 37208<UL> 37209<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 37210</UL><P> 37211<P> 37212<UL> 37213<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37214</UL><P> 37215<End of help on this topic> 37216</BODY> 37217</HTML> 37218====== h_config_smime_transfer_cacert_to_con ===== 37219<HTML> 37220<HEAD> 37221<TITLE>S/MIME: Transfer CA Certs to Container</TITLE> 37222</HEAD> 37223<BODY> 37224<H1>S/MIME: Transfer CA Certs to Container</H1> 37225 37226<P> 37227The Transfer command will copy the CA certificates in your configured 37228<A HREF="h_config_smime_cacertdir"><!--#echo var="VAR_smime-cacert-directory"--></A> 37229to the container in your configured 37230<A HREF="h_config_smime_cacertcon"><!--#echo var="VAR_smime-cacert-container"--></A>. 37231This might be useful if you decide to switch from using a CA cert directory to a CA cert 37232container. 37233<P> 37234Warning: Any previous contents in the container will be lost. 37235<P> 37236<UL> 37237<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 37238</UL><P> 37239<P> 37240<UL> 37241<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37242</UL><P> 37243<End of help on this topic> 37244</BODY> 37245</HTML> 37246====== h_config_smime_transfer_cacert_to_dir ===== 37247<HTML> 37248<HEAD> 37249<TITLE>S/MIME: Transfer CA Certs to Directory</TITLE> 37250</HEAD> 37251<BODY> 37252<H1>S/MIME: Transfer CA Certs to Directory</H1> 37253 37254<P> 37255The Transfer command will copy the CA certificates in your configured 37256<A HREF="h_config_smime_cacertcon"><!--#echo var="VAR_smime-cacert-container"--></A>. 37257to the directory in your configured 37258<A HREF="h_config_smime_cacertdir"><!--#echo var="VAR_smime-cacert-directory"--></A>. 37259This might be useful if you decide to switch from using a CA cert container to a CA cert 37260directory. 37261<P> 37262<UL> 37263<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 37264</UL><P> 37265<P> 37266<UL> 37267<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37268</UL><P> 37269<End of help on this topic> 37270</BODY> 37271</HTML> 37272====== h_config_smime_transfer_pubcon_to_key ===== 37273<HTML> 37274<HEAD> 37275<TITLE>S/MIME: Transfer Public Certs to Keychain</TITLE> 37276</HEAD> 37277<BODY> 37278<H1>S/MIME: Transfer Public Certs to Keychain</H1> 37279 37280Mac OS X Alpine only. 37281<P> 37282The Transfer command will copy the public certificates in your configured 37283<A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A> 37284to your default Mac OS X Keychain. 37285This might be useful if you decide to switch from using a cert container to using 37286the Keychain to store your public certs, which you may do by using the 37287feature 37288<A HREF="h_config_smime_pubcerts_in_keychain">S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></A>. 37289<P> 37290<UL> 37291<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 37292</UL><P> 37293<P> 37294<UL> 37295<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37296</UL><P> 37297<End of help on this topic> 37298</BODY> 37299</HTML> 37300====== h_config_smime_transfer_pubkey_to_con ===== 37301<HTML> 37302<HEAD> 37303<TITLE>S/MIME: Transfer Public Certs to Keychain</TITLE> 37304</HEAD> 37305<BODY> 37306<H1>S/MIME: Transfer Public Certs to Keychain</H1> 37307 37308<P> 37309The Transfer command will copy the public certificates in your configured 37310<A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A> 37311to your default Mac OS X Keychain. 37312This might be useful if you decide to switch from using a cert container to using 37313the Keychain to store your public certs. 37314<P> 37315<UL> 37316<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 37317</UL><P> 37318<P> 37319<UL> 37320<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37321</UL><P> 37322<End of help on this topic> 37323</BODY> 37324</HTML> 37325====== h_config_smime_public_certificates ===== 37326<HTML> 37327<HEAD> 37328<TITLE>S/MIME: Manage Public Certificates</TITLE> 37329</HEAD> 37330<BODY> 37331<H1>S/MIME: Manage Public Certificates</H1> 37332 37333<P> 37334This menu item allows you to manage your public certificates, this 37335may include your own public certificate, but it normally includes 37336certificates of people you correspond with. These certificates are 37337saved by Alpine automatically when they are found in signed messages 37338that you receive. This interface allows you to manage them, by 37339giving you the option to delete them, or trust them (in the case 37340of self-signed certificates). 37341 37342<P> 37343Please note that Alpine will not validate a message that was sent to you 37344using a self-signed certificate, unless you decide to trust that certificate. 37345Internally, a certificate is trusted by copying it to the 37346<A HREF="h_config_smime_certificate_authorities">Certificate Authorities</A> 37347collection. If you decide that you want to stop trusting a self-signed 37348certificate, you must delete such certificate from such collection. 37349<P> 37350The <B>I</B> Import command available in this screen allows you to 37351import a command to this collection. 37352<P> 37353<UL> 37354<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 37355</UL><P> 37356<P> 37357<UL> 37358<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37359</UL><P> 37360<End of help on this topic> 37361</BODY> 37362</HTML> 37363====== h_config_smime_private_keys ===== 37364<HTML> 37365<HEAD> 37366<TITLE>S/MIME: Manage Private Keys</TITLE> 37367</HEAD> 37368<BODY> 37369<H1>S/MIME: Manage Private Keys</H1> 37370 37371<P> 37372This option allows you to manage your private key. Normally a person has only 37373one key, in the same way that a person only has one valid passport, or ID card, 37374at any given time. This option allows you to manage private keys. You can 37375delete them or import them. Additionally, you can view information 37376about your public certificate, such as the issuer and the dates of validity 37377of such certificate, among others. 37378 37379<P> 37380If you have more than one e-mail address for which you want to use the 37381same private key, you must add all those addresses to the private key at 37382the moment that the key is generated. When you receive a signed message using 37383a key generated for several e-mail addresses, Alpine will save a 37384certificate for each e-mail address included in such certificate. 37385<P> 37386The <B>I</B> Import command available in this screen allows you to 37387import a command to this collection. 37388<P> 37389<UL> 37390<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 37391</UL><P> 37392<P> 37393<UL> 37394<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37395</UL><P> 37396<End of help on this topic> 37397</BODY> 37398</HTML> 37399====== h_config_smime_certificate_authorities ===== 37400<HTML> 37401<HEAD> 37402<TITLE>S/MIME: Manage Certificate Authorities</TITLE> 37403</HEAD> 37404<BODY> 37405<H1>S/MIME: Manage Certificate Authorities</H1> 37406 37407<P> 37408This collection contains certificates that are needed to validate the 37409certificate of another person, and therefore contains certificates that 37410you trust. Typically a certificate is signed by another entity, called a 37411certificate authority. This option allows you to manage which certificates 37412you trust, allowing you to import them and to delete them or view information 37413about each certificate, such as the issuer and the dates of validity 37414of such certificate. 37415<P> 37416The <B>I</B> Import command available in this screen allows you to 37417import a command to this collection. 37418<P> 37419<UL> 37420<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 37421</UL><P> 37422<P> 37423<UL> 37424<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37425</UL><P> 37426<End of help on this topic> 37427</BODY> 37428</HTML> 37429====== h_config_smime_password_file_certificates ===== 37430<HTML> 37431<HEAD> 37432<TITLE>S/MIME: Manage Password File Certificates</TITLE> 37433</HEAD> 37434<BODY> 37435<H1>S/MIME: Manage Password File Certificates</H1> 37436 37437<P> 37438This option allows you to manage the certificates that are used to 37439encrypt and decrypt your password file. This is useful in case you 37440want to change the certificates used to encrypt your password file. 37441<P> 37442Depending on the version of Alpine that you used for the first time 37443to set this up, you might have had to enter a password to enter this 37444screen. In the case that you did not enter a password to enter this 37445screen, you should know two things that are important: 37446<UL> 37447<LI> If anyone takes control of your computer (for example, if you 37448left it unattended) then that person can add a password to your 37449password file and make it unreadable to you in the future. 37450<LI> If anyone can access your computer (this includes remote access) 37451then that person can steal your password file and decrypt it without 37452your help. This gives access to that person to the same services you 37453have access and such person can use your name to access that service. 37454In particular, that person can try to hack into your service provider 37455with your name on it, or that person could try to send spam with 37456your name. 37457</UL> 37458<P> Needless to say, this is not advisable. You should keep your 37459password file protected. In order to do so, all you need to do is use 37460the "Create Key" command to create a key. Once you do this, 37461Alpine will use that key, encrypted with the password used to create that 37462key, to protect your password file. 37463<P> 37464In this screen you can import a new key to encrypt your password file, 37465and read cryptographic information on your current key. 37466<P> 37467To import a new key press "RETURN" and enter the location of 37468the new key. You will be asked to enter the password of the new key. If 37469this part of the process is successful, Alpine will search for the 37470certificate that matches that key. If your key is named 37471"your_email@address.com.key", then Alpine will look for your 37472certificate in the same directory in the file named 37473"your_email@address.com.crt", otherwise it will look for it 37474as part of your key (that is, it will look to see if your certificate 37475is in the file "your_email@address.com.key"), if all of this 37476fails, Alpine will ask you to enter the location of the certificate 37477that matches the key you unlocked. If a certificate is found, it will be 37478used, and in this case, the password file will be read, decrypted with the 37479old key and encrypted with the new key. Once this is done, the new key and 37480certificates are saved, and the old keys are permanently deleted. 37481<P> 37482Alpine does not create a backup of your password file, or your old keys 37483that will be replaced. If you need to keep old copies, you will have to do 37484this operation outside Alpine. 37485<P> 37486Observe that you can use this screen to remove the password for the key. 37487As explained earlier, this is not advisable, but you can always restore the 37488password to encrypt your password file by creating a new key. 37489<P> 37490Be safe and keep your password file encrypted with a password. 37491<UL> 37492<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 37493</UL><P> 37494<P> 37495<UL> 37496<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37497</UL><P> 37498<End of help on this topic> 37499</BODY> 37500</HTML> 37501====== h_certificate_information ===== 37502<HTML> 37503<HEAD> 37504<TITLE>S/MIME: Certificate Information Screen</TITLE> 37505</HEAD> 37506<BODY> 37507<H1>S/MIME: Certificate Information Screen</H1> 37508 37509<P> 37510The CERTIFICATE INFORMATION screen shows you information contained in a certificate 37511such as its owner, e-mail address, issuer, and interval of validity, 37512among others. 37513<P> 37514In the case of public certificates, this screen shows you if there was a 37515failure when attempting to validate such message. If the certificate is 37516self-signed, then the <B>T</B> Trust command will be available, which 37517you can use to trust such certificate and make Alpine not fail validating 37518signatures signed with such certificate. 37519<P> 37520You can also mark a certificate deleted, with the <B>D</B> command, or 37521remove the deleted mark with the <B>U</B> undelete command. 37522<P> 37523In the case of your private key, Alpine shows you the information 37524from your public key. Additionally, Alpine allows you to see public 37525and private information about your key, with the <B>B</B> and 37526<B>R</B> commands respectively. 37527<UL> 37528<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 37529</UL><P> 37530<P> 37531<UL> 37532<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37533</UL><P> 37534<End of help on this topic> 37535</BODY> 37536</HTML> 37537====== h_config_smime_manage_public_menu ===== 37538<HTML> 37539<HEAD> 37540<TITLE>S/MIME: Menu of Commands to Manage Public Certificates</TITLE> 37541</HEAD> 37542<BODY> 37543<H1>S/MIME: Commands that Manage Public Certificates</H1> 37544 37545<P> 37546This screen allows you to manage your public certificates. 37547<P> 37548The format of this screen is as follows. There are five fields: The 37549leftmost field is normally empty, but it could contain the letter 37550"D" to indicate that that certificate has been marked for 37551deletion. The next field is the e-mail address of the owner of the 37552certificate, shown in its entirety. The third and fourth field are the 37553first and last day validity for that certificate, respectively. The date 37554is displayed in the user's locale unless the option 37555<A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A> 37556is set. In this case, the month, day and year are represented by two 37557digits, and the format used is mm/dd/yy. Finally, the fifth 37558field is what can be displayed of the MD5 hash of the certificate. You can 37559use any of the last three fields to distinguish between two certificates 37560for the same owner. 37561<P> 37562Available commands in this screen and a short description of what they 37563do follows. 37564<UL> 37565<LI> <B>I</B> Imports a public certificate to this collection. 37566<LI> <B>V</B> View information about a certificate such as the name of the person the 37567certificate was issued to, its dates of validity, and validity status. 37568<LI> <B>D</B> Marks a certificate deleted. 37569<LI> <B>U</B> Removes the deletion mark on a certificate. 37570<LI> <B>X</B> Removes all certificates marked deleted permanently (cannot be undone). 37571<LI> <B>T</B> This command is only available for self-signed certificates, and allows you to 37572trust a certificate by copying it to the collection of trusted certificates. 37573</UL> 37574<P> 37575All commands provide feedback to let you know about their success or failure. 37576<P> 37577<UL> 37578<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 37579</UL><P> 37580<P> 37581<UL> 37582<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37583</UL><P> 37584<End of help on this topic> 37585</BODY> 37586</HTML> 37587====== h_config_smime_manage_private_menu ===== 37588<HTML> 37589<HEAD> 37590<TITLE>S/MIME: Menu of Commands to Manage Private Keys</TITLE> 37591</HEAD> 37592<BODY> 37593<H1>S/MIME: Commands that Manage Private Keys</H1> 37594 37595<P> 37596This screen allows you to manage your private key. 37597<P> 37598The format of this screen is as follows. There are five fields: The 37599leftmost field is normally empty, but it could contain the letter 37600"D" to indicate that that certificate has been marked for 37601deletion. The next field is the e-mail address of the owner of the 37602certificate, shown in its entirety. The third field is the first day of 37603validity for that certificate; the fourth field in the last day that that 37604certificate is valid, and the fifth field is what can be displayed of the 37605MD5 hash of the public certificate corresponding to this private key. You 37606can use any of the last three fields to distinguish between two 37607certificates for the same owner. 37608<P> 37609Available commands and a short description of what they do follows. 37610<UL> 37611<LI> <B>I</B> Imports a new public key to this collection. 37612<LI> <B>V</B> View information about the public certificate corresponding to this 37613key. 37614<LI> <B>D</B> Marks a key to be deleted. 37615<LI> <B>U</B> Removes the deletion mark on a key. 37616<LI> <B>X</B> Removes all keys marked deleted permanently (cannot be undone). 37617Note that expunging a private key does not remove the public key, which must 37618be removed separately. 37619</UL> 37620<P> 37621All commands provide feedback to let you know about their success or failure. 37622<P> 37623<UL> 37624<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 37625</UL><P> 37626<P> 37627<UL> 37628<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37629</UL><P> 37630<End of help on this topic> 37631</BODY> 37632</HTML> 37633====== h_config_smime_manage_cacerts_menu ===== 37634<HTML> 37635<HEAD> 37636<TITLE>S/MIME: Menu of Commands to Manage Certificate Authorities</TITLE> 37637</HEAD> 37638<BODY> 37639<H1>S/MIME: Commands that Manage Certificate Authorities</H1> 37640 37641<P> 37642This screen allows you to manage your collection of certificates that you 37643trust. 37644<P> 37645The format of this screen is as follows. There are five fields: The 37646leftmost field is normally empty, but it could contain the letter 37647"D" to indicate that that certificate has been marked for 37648deletion. The next field is the e-mail address of the owner of the 37649certificate, shown in its entirety. The third field is the first day of 37650validity for that certificate; the fourth field in the last day that that 37651certificate is valid, and the fifth field is what can be displayed of the 37652MD5 hash of the certificate. You can use any of the last three fields to 37653distinguish between two certificates for the same owner. 37654<P> 37655Available commands and a short description of what they do follows. 37656<UL> 37657<LI> <B>I</B> Imports a trusted certificate to this collection. This is 37658done by reading the certificate and validating it. Once a certificate 37659is found to be valid, it is saved, adding the extension ".crt" 37660to the certificate, if necessary. 37661<LI> <B>V</B> View information about this certificate, such as its issuer 37662and validity dates. 37663<LI> <B>D</B> Marks a certificate to be deleted. 37664<LI> <B>U</B> Removes the deletion mark on a certificate. 37665<LI> <B>X</B> Removes all certificates marked deleted permanently (cannot be undone). 37666</UL> 37667<P> 37668All commands provide feedback to let you know about their success or failure. 37669<P> 37670<UL> 37671<LI><A HREF="h_mainhelp_smime">General S/MIME help</A> 37672</UL><P> 37673<P> 37674<UL> 37675<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37676</UL><P> 37677<End of help on this topic> 37678</BODY> 37679</HTML> 37680====== h_config_lame_list_mode ===== 37681<HTML> 37682<HEAD> 37683<TITLE>FEATURE: <!--#echo var="FEAT_enable-lame-list-mode"--></TITLE> 37684</HEAD> 37685<BODY> 37686<H1>FEATURE: <!--#echo var="FEAT_enable-lame-list-mode"--></H1> 37687 37688This feature modifies the method Alpine uses to ask your IMAP 37689server for folder names to display in the FOLDER LIST screen. 37690It is intended to compensate for a small set of IMAP servers that 37691are programmed to ignore a part of the request, and thus respond 37692to Alpine's query with nonsensical results. 37693<P> 37694 37695If you find that Alpine is erroneously displaying blank folder lists, 37696try enabling this feature. 37697<P> 37698 37699NOTE: Enabling this feature has consequences for the Goto and Save 37700commands. Many servers allow access to folders outside the area 37701reserved for your personal folders via some reserved character, 37702typically '#' (sharp), '~' (tilde) or '/' (slash). This mechanism 37703allows, at the Goto and Save prompts, quick access to folders 37704outside your personal folder collection without requiring a specific 37705collection definition. This behavior will generally not be available 37706when this feature is enabled. 37707 37708<P> 37709<UL> 37710<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37711</UL><P> 37712<End of help on this topic> 37713</BODY> 37714</HTML> 37715====== h_config_enable_mulnewsrcs ===== 37716<HTML> 37717<HEAD> 37718<TITLE>FEATURE: <!--#echo var="FEAT_enable-multiple-newsrcs"--></TITLE> 37719</HEAD> 37720<BODY> 37721<H1>FEATURE: <!--#echo var="FEAT_enable-multiple-newsrcs"--></H1> 37722 37723This feature makes it so Alpine can use multiple newsrcs based on 37724the news server being connected to, which allows for separate lists 37725of subscribed-to newsgroups. When this feature is not set, there is only 37726one list of newsgroups. 37727<P> 37728Under this feature, the name of a newsrc is based on the news server. 37729For example, if your <a href="h_config_newsrc_path"><!--#echo var="VAR_newsrc-path"--></a> 37730is set to ".newsrc", and the news server you are connecting to is 37731news.example.com, then the newsrc to be used is .newsrc-news.example.com. 37732Setting this feature for the first time will allow for the option of using 37733your old newsrc the next time you read news. 37734<P> 37735If this feature is set, then the feature 37736<A HREF="h_config_mulnews_as_typed"><!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></A> 37737also may affect the name of the newsrc file that is used. 37738<P> 37739<UL> 37740<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37741</UL><P> 37742<End of help on this topic> 37743</BODY> 37744</HTML> 37745======= h_ab_export_vcard ======= 37746<HTML> 37747<HEAD> 37748<TITLE>Address Book Export Format</TITLE> 37749</HEAD> 37750<BODY> 37751<H1>Address Book Export Format</H1> 37752 37753You are exporting address book data from Alpine to a file outside of Alpine. 37754You are being asked to choose the format of the export. 37755Here are the choices: 37756 37757<DL> 37758<DT><EM>A</EM>ddress List</DT> 37759<DD> 37760The addresses from the address book entries you are saving 37761from will be saved one address per line. 37762Address book lists (those with more than one address) will have 37763all of their addresses saved separately. 37764</DD> 37765 37766<DT><EM>V</EM>Card</DT> 37767<DD> 37768The entries will be saved in 37769<A HREF="h_whatis_vcard">vCard</A> format. 37770</DD> 37771 37772<DT><EM>T</EM>ab Separated</DT> 37773<DD> 37774The entries will be saved in tab-separated columns. 37775There will be just 4 columns of data that correspond to Alpine's 37776Nickname field, Full Name field, Address field, and Comment field. 37777It might prove useful to Select only the Simple, non-List address book 37778entries before Saving. 37779</DD> 37780 37781<DT><EM>^C</EM> Cancel</DT> 37782<DD> 37783Cancel out of the Save. 37784</DD> 37785 37786</DL> 37787 37788 37789<P> 37790<End of help on this topic> 37791</BODY> 37792</HTML> 37793====== h_config_predict_nntp_server ===== 37794<HTML> 37795<HEAD> 37796<TITLE>FEATURE: <!--#echo var="FEAT_predict-nntp-server"--></TITLE> 37797</HEAD> 37798<BODY> 37799<H1>FEATURE: <!--#echo var="FEAT_predict-nntp-server"--></H1> 37800 37801This feature allows Alpine to assume that the open NNTP server at the 37802time of composition is the NNTP server to which the message should be 37803posted. This is especially recommended when there are multiple News 37804collections. If this feature is not set, Alpine will try to post to the first server in 37805the <a href="h_config_nntp_server"><!--#echo var="VAR_nntp-server"--></a> variable. Setting 37806this feature also negates the need to add News collection servers to 37807the <!--#echo var="VAR_nntp-server"--> variable. 37808<P> 37809This feature can be especially handy when used in conjunction with 37810<a href="h_config_enable_mulnewsrcs"><!--#echo var="FEAT_enable-multiple-newsrcs"--></a>. 37811<P> 37812<UL> 37813<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37814</UL><P> 37815<End of help on this topic> 37816</BODY> 37817</HTML> 37818====== h_config_nntp_search_uses_overview ===== 37819<HTML> 37820<HEAD> 37821<TITLE>FEATURE: <!--#echo var="FEAT_nntp-search-uses-overview"--></TITLE> 37822</HEAD> 37823<BODY> 37824<H1>FEATURE: <!--#echo var="FEAT_nntp-search-uses-overview"--></H1> 37825 37826This feature should probably be turned on unless it causes trouble. 37827The results of the NNTP overview command (XOVER) may be used to help 37828with some searches in news groups. 37829It should result in quicker response time. 37830Turning this feature on apparently causes search results which are 37831different from what you would get with the feature turned off on some 37832servers. 37833<P> 37834<UL> 37835<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37836</UL><P> 37837<End of help on this topic> 37838</BODY> 37839</HTML> 37840====== h_config_thread_sorts_by_arrival ===== 37841<HTML> 37842<HEAD> 37843<TITLE>FEATURE: <!--#echo var="FEAT_thread-sorts-by-arrival"--></TITLE> 37844</HEAD> 37845<BODY> 37846<H1>FEATURE: <!--#echo var="FEAT_thread-sorts-by-arrival"--></H1> 37847 37848This feature affects how a threading sort arranges threads. The default way 37849to arrange threads is by the date of the earliest message in the thread. 37850This feature arranges threads by the last message to arrive in a thread. 37851<P> 37852This feature causes old threads that get recent messages to sort to the bottom, 37853where previously a message arrival to a thread would not rearrange the order of 37854that thread. 37855<P> 37856<UL> 37857<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37858</UL><P> 37859<End of help on this topic> 37860</BODY> 37861</HTML> 37862====== h_config_textplain_int ===== 37863<HTML> 37864<HEAD> 37865<TITLE>FEATURE: <!--#echo var="FEAT_show-plain-text-internally"--></TITLE> 37866</HEAD> 37867<BODY> 37868<H1>FEATURE: <!--#echo var="FEAT_show-plain-text-internally"--></H1> 37869 37870This feature modifies the method Alpine uses to display Text/Plain 37871MIME attachments from the Attachment Index screen. Normally, the 37872"View" command searches for any externally defined (usually 37873via the 37874"<A HREF="h_config_mailcap_path">Mailcap</A>" file) viewer, 37875and displays the selected text within that viewer. 37876 37877<P> 37878Enabling this feature causes Alpine to ignore any external viewer 37879settings and always display text with Alpine's internal viewer. 37880 37881<P> 37882<UL> 37883<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37884</UL><P> 37885<End of help on this topic> 37886</BODY> 37887</HTML> 37888====== h_config_wp_columns ===== 37889<HTML> 37890<HEAD> 37891<TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-columns"--></TITLE> 37892</HEAD> 37893<BODY> 37894<H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-columns"--></H1> 37895 37896Web Alpine only. 37897<P> 37898This configuration setting specifies the number of horizontal characters 37899used to format various WebAlpine pages. Smaller values will tend to reduce 37900the amount of horizontal scrolling required to view pages within narrow 37901browsers, such as those found on PDAs, and larger values will tend to 37902spread more information across the page. 37903 37904<P> 37905The Message List page uses the width to determine how many characters 37906to assign each field. Note, a smaller value may result in a disproportionate 37907amount of blank space between fields on each line. Similarly, a large 37908value may result in cramped fields or horizontal scrolling. 37909 37910<P> 37911The Message View page uses this value to determine when to wrap lines 37912in displayed message text. Note, a smaller value may result in jagged 37913right margins or confusing quoting. A larger value may cause lines of text to 37914run beyond the browser's right edge, requiring horizontal scrolling. 37915 37916<P> 37917<UL> 37918<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37919</UL><P> 37920<End of help on this topic> 37921</BODY> 37922</HTML> 37923====== h_config_wp_state ===== 37924<HTML> 37925<HEAD> 37926<TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-state"--></TITLE> 37927</HEAD> 37928<BODY> 37929<H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-state"--></H1> 37930 37931Web Alpine only. 37932<P> 37933Various aspects of cross-session state. 37934 37935<P> 37936<UL> 37937<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37938</UL><P> 37939<End of help on this topic> 37940</BODY> 37941</HTML> 37942====== h_config_wp_aggstate ===== 37943<HTML> 37944<HEAD> 37945<TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-aggstate"--></TITLE> 37946</HEAD> 37947<BODY> 37948<H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-aggstate"--></H1> 37949 37950Web Alpine only. 37951<P> 37952Aggregate operations tab state. 37953 37954<P> 37955<UL> 37956<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37957</UL><P> 37958<End of help on this topic> 37959</BODY> 37960</HTML> 37961====== h_config_wp_indexlines ===== 37962<HTML> 37963<HEAD> 37964<TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexlines"--></TITLE> 37965</HEAD> 37966<BODY> 37967<H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexlines"--></H1> 37968 37969Web Alpine only. 37970<P> 37971Number of index lines in table. 37972 37973<P> 37974<UL> 37975<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37976</UL><P> 37977<End of help on this topic> 37978</BODY> 37979</HTML> 37980====== h_config_wp_indexheight ===== 37981<HTML> 37982<HEAD> 37983<TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexheight"--></TITLE> 37984</HEAD> 37985<BODY> 37986<H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexheight"--></H1> 37987 37988Web Alpine only. 37989<P> 37990Index table row height. 37991 37992<P> 37993<UL> 37994<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 37995</UL><P> 37996<End of help on this topic> 37997</BODY> 37998</HTML> 37999====== h_config_rss_news ===== 38000<HTML> 38001<HEAD> 38002<TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_rss_news"--></TITLE> 38003</HEAD> 38004<BODY> 38005<H1>WEB ALPINE OPTION: <!--#echo var="VAR_rss-news"--></H1> 38006 38007Web Alpine only. 38008<P> 38009RSS News feed. 38010 38011<P> 38012<UL> 38013<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 38014</UL><P> 38015<End of help on this topic> 38016</BODY> 38017</HTML> 38018====== h_config_rss_weather ===== 38019<HTML> 38020<HEAD> 38021<TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_rss-weather"--></TITLE> 38022</HEAD> 38023<BODY> 38024<H1>WEB ALPINE OPTION: <!--#echo var="VAR_rss-weather"--></H1> 38025 38026Web Alpine only. 38027<P> 38028RSS Weather feed. 38029 38030<P> 38031<UL> 38032<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 38033</UL><P> 38034<End of help on this topic> 38035</BODY> 38036</HTML> 38037====== h_config_send_confirms_only_expanded ===== 38038<HTML> 38039<HEAD> 38040<TITLE>FEATURE: send-confirms-only-expanded</TITLE> 38041</HEAD> 38042<BODY> 38043<H1>FEATURE: send-confirms-only-expanded (Web Alpine Only)</H1> 38044 38045This Web Alpine option specifies whether or not a Send confirmations 38046happens when a composed message is readied for sending or not. The 38047default behavior is to not confirm that the nicknames were expanded to 38048the intended addresses. 38049 38050<P> 38051<UL> 38052<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 38053</UL><P> 38054<End of help on this topic> 38055</BODY> 38056</HTML> 38057====== h_config_enable_jump_command ===== 38058<HTML> 38059<HEAD> 38060<TITLE>FEATURE: enable-jump-command</TITLE> 38061</HEAD> 38062<BODY> 38063<H1>FEATURE: enable-jump-command (Web Alpine Only)</H1> 38064 38065This Web Alpine option specifies whether or not a Jump command is 38066offered in the Message List and Message View pages. The command is 38067implemented as an input field in the left column of the List and View 38068screens. 38069 38070<P> 38071When enabled and a number is entered in the input field while the 38072Message List is displayed, the Message List is reframed with the 38073specified message. While viewing a message, the message associated 38074with the specified message number is displayed. 38075 38076<P> 38077<UL> 38078<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 38079</UL><P> 38080<End of help on this topic> 38081</BODY> 38082</HTML> 38083====== h_config_enable_newmail_sound ===== 38084<HTML> 38085<HEAD> 38086<TITLE>FEATURE: enable-newmail-sound</TITLE> 38087</HEAD> 38088<BODY> 38089<H1>FEATURE: enable-newmail-sound (Web Alpine Only)</H1> 38090 38091This Web Alpine option specifies whether or not a sound file is sent 38092to the web browser along with the newmail notification message. 38093 38094 38095<P> 38096<UL> 38097<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 38098</UL><P> 38099<End of help on this topic> 38100</BODY> 38101</HTML> 38102====== h_config_render_html_internally ===== 38103<HTML> 38104<HEAD> 38105<TITLE>FEATURE: render-html-internally</TITLE> 38106</HEAD> 38107<BODY> 38108<H1>FEATURE: render-html-internally (Web Alpine Only)</H1> 38109 38110By default, Web Alpine will pass cleansed HTML text you receive in messages 38111to the browser for display (rendering). This feature causes Web Alpine to convert 38112the HTML text into plain text in the same way Unix and PC-Alpine do. 38113 38114 38115<P> 38116<UL> 38117<LI><A HREF="h_finding_help">Finding more information and requesting help</A> 38118</UL><P> 38119<End of help on this topic> 38120</BODY> 38121</HTML> 38122====== h_config_role_undo ===== 38123Yes, remember changes and exit back to list of roles; No, discard changes 38124made in this screen; ^C, cancel exit and stay in this config screen. 38125====== h_exit_editor ===== 38126S, save changes and exit from the editor; D, do not save changes but 38127do exit from the editor; or ^C, cancel exit and stay in the editor. 38128====== h_config_undo ===== 38129Yes, save changes and exit; No, exit without saving any changes made since 38130entering this CONFIGURATION screen; ^C, cancel exit and stay in config screen. 38131====== h_os_index_whereis ===== 38132Enter ^V or ^Y to go immediately to the last or first message in the index. 38133Or, enter the match string followed by RETURN. 38134====== h_os_index_whereis_agg ===== 38135Enter ^V or ^Y to go immediately to the last or first message in the index, 38136Or, enter the match string followed by RETURN (or ^X to select all matches). 38137=========== h_oe_add_full ================== 38138Type the full name of the person being added and press the RETURN key. 38139Press ^C to cancel addition. 38140=========== h_oe_add_nick ================== 38141Type a short nickname and press RETURN. A nickname is a short easy-to- 38142remember word, name or initials like "joe", or "wcfields." ^C to cancel. 38143========== h_oe_add_addr ================ 38144Type the e-mail address and press RETURN. 38145Press ^C to cancel addition. 38146========== h_oe_crlst_full ============== 38147Type a long name or description for the list that you are creating and 38148press RETURN. Press ^C to cancel creation of list. 38149=========== h_oe_crlst_nick ============= 38150Type a nickname (short, easy-to-remember name or single word) for the list 38151you are creating and press RETURN. Press ^C to cancel. 38152========== h_oe_crlst_addr ============== 38153Type an e-mail address, or a nickname already in the address book that you 38154want to be part of this list and press RETURN. 38155========== h_oe_adlst_addr ============= 38156Type an e-mail address or a nickname already in the address book that you 38157want to add to this list and press RETURN. 38158========== h_oe_editab_nick ============ 38159Change the nickname using the arrow keys and delete key. Press RETURN 38160when done. Press ^C to cancel editing and leave the nickname as it was. 38161========== h_oe_editab_full ============ 38162Change the full name using the arrow keys and delete key. Press RETURN 38163when done. Press ^C to cancel editing and leave the full name as it was. 38164========== h_oe_editab_addr ============ 38165Change the address using the arrow keys and delete key. Press RETURN 38166when done. Press ^C to cancel editing and leave the address as it was. 38167========== h_oe_editab_fcc ============ 38168Change the fcc using the arrow keys and delete key. Press RETURN when 38169done. Press ^C to cancel editing and leave the fcc as it was. 38170========== h_oe_editab_comment ============ 38171Change the comment field using the arrow keys and delete key. Press RETURN 38172when done. Press ^C to cancel editing and leave the comment as it was. 38173====== h_ab_forward ===== 38174Yes, expand nicknames and qualify local names with your current domain name; 38175No, leave nicknames and local names as is; ^C, cancel. 38176========== h_ab_export ========== 38177Type the name of a file to write the addresses into and 38178press RETURN. You may also specify an absolute path. Use ^C to cancel. 38179========== h_ab_edit_a_field ========== 38180Edit any of the fields of the currently selected entry by typing one of the 38181letters at the bottom of the screen. Press ^C to cancel edit. 38182====== h_ab_del_data_revert ===== 38183Press B to completely delete addrbook and revert to default, C to delete config 38184and revert while leaving data, or D to only delete data (make it empty). 38185====== h_ab_del_data_modify ===== 38186Press B to completely delete addrbook, C to delete configuration while leaving 38187data, or D to delete data (make it empty) but leave config. ^C to cancel. 38188====== h_ab_del_config_modify ===== 38189Yes, remove this address book from my configuration. 38190No, make no changes now. 38191====== h_ab_del_config_revert ===== 38192Yes, remove this address book from my config and revert to default. 38193No, make no changes now. 38194====== h_ab_del_default ===== 38195Yes, remove this default address book from my configuration. 38196No, make no changes now. 38197====== h_ab_really_delete ===== 38198Yes, delete the actual contents of the address book, not just the 38199configuration. No, don't delete the data after all, cancel and start over. 38200====== h_ab_del_ignore ===== 38201Press I to ignore all the default address books for this category. Press R to 38202remove this one address book and add the others to your personal list. 38203====== h_ab_del_dir_ignore ===== 38204Press I to ignore all the default directory servers for this category. 38205Press R to remove this one server and add the others to your personal list. 38206====== h_ab_copy_dups ===== 38207Yes, overwrite the existing entry. 38208No, skip duplicates but save the rest. Press ^C to cancel. 38209====== h_confirm_cancel ===== 38210Type C to Confirm that you want to abandon the message you are composing. 38211Type N or ^C to cancel out of the cancel and keep composing. 38212====== h_ab_text_or_vcard ===== 38213Text, start composer with displayed text already included. 38214VCard, start composer with address book entry attached as a vCard. ^C cancels. 38215====== h_ab_backup_or_ldap ===== 38216Backup, copy email address from entry and allow editing of it. 38217LDAP, copy LDAP search criteria, do not allow editing of it. ^C cancels. 38218====== h_ldap_text_or_vcard ===== 38219Text: export displayed text for selected entry. Address: export only the 38220email address. VCard: export entry in vCard format. ^C cancels. 38221====== h_ab_save_exp ===== 38222Save, save entry or entries to an address book. 38223Export, save to file outside of pine. ^C cancels save. 38224====== h_ab_add ===== 38225A, add a brand new entry to this address book. 38226E, edit the entry that is currently highlighted. ^C to cancel. 38227====== h_ab_shuf ===== 38228U, swap order of highlighted address book and the one above it. 38229D, swap order of highlighted address book and the one below it. ^C to cancel. 38230====== h_ab_shuf_up ===== 38231U, swap order of highlighted address book and the one above it. 38232Press ^C to cancel. 38233====== h_ab_shuf_down ===== 38234D, swap order of highlighted address book and the one below it. 38235Press ^C to cancel. 38236====== h_folder_prop ===== 38237Count is # of messages in the folder, Unseen means messages that have not 38238been read, New means messages that were Recently added to the folder. 38239====== h_role_shuf ===== 38240U, swap order of highlighted rule and the one above it. 38241D, swap order of highlighted rule and the one below it. ^C to cancel. 38242====== h_role_shuf_up ===== 38243U, swap order of highlighted rule and the one above it. 38244Press ^C to cancel. 38245====== h_role_shuf_down ===== 38246D, swap order of highlighted rule and the one below it. 38247Press ^C to cancel. 38248====== h_incoming_shuf ===== 38249B, swap order of highlighted directory and the one before it. 38250F, swap order of highlighted directory and the one after it. ^C to cancel. 38251====== h_incoming_shuf_up ===== 38252B, swap order of highlighted directory and the one before it. 38253Press ^C to cancel. 38254====== h_incoming_shuf_down ===== 38255F, swap order of highlighted directory and the one after it. 38256Press ^C to cancel. 38257====== h_dir_shuf ===== 38258U, swap order of highlighted directory and the one above it. 38259D, swap order of highlighted directory and the one below it. ^C to cancel. 38260====== h_dir_shuf_up ===== 38261U, swap order of highlighted directory and the one above it. 38262Press ^C to cancel. 38263====== h_dir_shuf_down ===== 38264D, swap order of highlighted directory and the one below it. 38265Press ^C to cancel. 38266====== h_hdrcolor_shuf ===== 38267U, swap order of highlighted Header Color and the one above it. 38268D, swap order of highlighted Header Color and the one below it. ^C to cancel. 38269====== h_hdrcolor_shuf_up ===== 38270U, swap order of highlighted Header Color and the one above it. 38271Press ^C to cancel. 38272====== h_hdrcolor_shuf_down ===== 38273D, swap order of highlighted Header Color and the one below it. 38274Press ^C to cancel. 38275========== h_oe_editab_al ============ 38276Change the address using the arrow keys and delete key. Press RETURN 38277when done. Press ^C to cancel editing and leave the address as it was. 38278========== h_dir_comp_search =============== 38279Type a string to look for just like you would in the composer. Your configured 38280rules for the servers with the implicit flag set will be used. 38281========== h_oe_searchab =============== 38282Type the word or name you want to search for and press RETURN. If you press 38283RETURN without entering anything the word in [] will be searched for. 38284========== h_oe_chooseabook ========== 38285Choose the address book you want to save the new entry in. 38286Use ^N or ^P to change address books. ^C to cancel. 38287========== h_oe_takeaddr ========== 38288Edit the e-mail address using the arrow and delete keys. Press RETURN 38289when done. Press ^C to cancel adding this entry to the address book. 38290========== h_oe_take_replace ========== 38291Press R to replace the old entry with this new data. You will still have 38292another chance to cancel. N to enter another nickname. ^C to cancel now. 38293========== h_oe_take_replace_or_add ========== 38294Press R to replace the old entry. Press A to add the selected addresses to 38295the old existing list. N to enter another nickname. ^C to cancel now. 38296========== h_oe_takename ========== 38297Edit the full name to be correct using the arrow and delete keys. Press RETURN 38298when done. Press ^C to cancel adding this entry to the address book. 38299========== h_oe_takenick ========== 38300Type a nickname (short easy-to-remember name, initials or single word) for this 38301entry in the address book and press RETURN. Press ^C to cancel addition. 38302========== h_oe_jump ========== 38303Type the message number you want to jump to and press RETURN. The word "end" 38304represents the last message. Press ^C to cancel jumping to another message. 38305========== h_oe_jump_thd ========== 38306Type the thread number you want to jump to and press RETURN. The word "end" 38307represents the last thread. Press ^C to cancel jumping to another thread. 38308========== h_oe_debuglevel ========== 38309Higher number shows more debugging details. 38310Press ^C if you want to cancel the change. 38311========== h_oe_broach ========== 38312Type the name of the folder you want to open and press RETURN. Press ^P/^N 38313to go to the previous/next collections in the list. Press ^C to cancel goto. 38314========== h_oe_foldsearch ========== 38315Type the text you want to search for in foldernames and press RETURN. If you 38316press RETURN without entering anything, any text in [] will be searched for. 38317========== h_oe_foldrename ========== 38318Change the old name of the folder to the new name using the arrow and 38319delete keys and press RETURN. Press ^C to cancel rename. 38320========== h_oe_login ========== 38321Enter your login name for the host you are opening the mailbox on. Just press 38322RETURN to use your login from this host as is, or edit it with delete key. 38323========== h_oe_passwd ========== 38324Type your password for the host and login shown as part of the prompt. 38325Press ^C to cancel opening folder. 38326========== h_oe_choosep ========== 38327Enter the number associated with the printer you want to select. Press ^C to 38328cancel the printer selection. The current selection is highlighted. 38329========== h_oe_customp ========== 38330Type the name of the Unix print command and press RETURN. Press ^C to 38331cancel the printer selection. 38332========== h_oe_searchview ========== 38333Type the word or name you want to search for and press RETURN. If you press 38334RETURN without entering anything the word in [] will be searched for. 38335========== h_oe_keylock ========== 38336The keyboard is in use and locked by another user. Only that user can 38337unlock this keyboard by typing the password. 38338========== h_wt_expire ========== 38339At the beginning of each month Alpine offers to rename your current sent-mail 38340folder to one named for the month so you have a sent-mail folder for each month 38341========== h_wt_delete_old ========== 38342It is the beginning of the month, and we need to conserve disk 38343space. Please delete any sent-mail that you do not need. 38344========== h_select_sort ========== 38345Select the order for sorting the index by typing the capitalized letter. 38346Arrival is by arrival in your mailbox; Date is by time/day message was sent. 38347========== h_no_F_arg ============ 38348Enter name of file to be opened. 38349 38350========== h_sticky_personal_name ========== 38351Type in your name as you want it to appear on outgoing email. This entry 38352will be saved into your Alpine configuration file. 38353========== h_sticky_inbox ============ 38354INBOX syntax is usually {complete.machine.name}INBOX 38355This entry will be saved in your Alpine configuration file. 38356========== h_sticky_smtp ============ 38357The name of the computer on your campus that relays your outgoing email 38358to the Internet. This entry will be saved in your Alpine configuration file. 38359========== h_sticky_user_id ========== 38360The username or login-id part of your email address. This entry will be 38361saved in your Alpine configuration file. 38362========== h_sticky_domain ========== 38363The domain part of your email address, NOT the name of your PC. This 38364entry will be saved in your Alpine configuration file. 38365========== h_bounce ========= 38366Enter the address or nickname of the intended recipient. Alpine will resend 38367the message, which will retain the original author's From: address. 38368========== h_incoming_add_folder_nickname ========= 38369Enter an (optional) nickname that will be used in lieu of the actual 38370host and folder names in the FOLDER LIST display. 38371========== h_anon_forward ========== 38372Enter the address of your intended recipient, or ^C to cancel. 38373Example: jsmith@somewhere.edu 38374========== h_news_subscribe ========== 38375Enter the name of the newsgroup to which you wish to subscribe, 38376or ^C to cancel. Example: comp.mail.pine 38377========== h_pipe_msg ========== 38378Enter the name of the Unix command to which you wish to send this 38379message, or ^C to cancel. 38380========== h_pipe_attach ========== 38381Enter the name of the Unix command to which you wish to send this 38382attachment, or ^C to cancel. 38383========== h_select_by_num ========== 38384Enter a list of message numbers (or number ranges), or ^C to cancel. "end" 38385is the last message. "." is the current message. Example: 1-.,7-9,11,19,35-end 38386========== h_select_by_gm_content ========== 38387Enter your search key in the same way that you would enter a search 38388key in the web interface for Gmail. 38389========== h_select_by_thrdnum ========== 38390Enter a list of message numbers (or number ranges), or ^C to cancel. "end" 38391is the last message. "." is the current message. Example: 1-.,7-9,11,19,35-end 38392========== h_select_txt_from ========== 38393Messages with From: headers containing the entered string will be selected. 38394^C to cancel. ^G again to see original options. 38395========== h_select_txt_not_from ========== 38396Messages without From: headers containing the entered string will be selected. 38397^C to cancel. ^G again to see original options. 38398========== h_select_txt_to ========== 38399Messages with To: headers containing the entered string will be selected. 38400^C to cancel. ^G again to see original options. 38401========== h_select_txt_not_to ========== 38402Messages without To: headers containing the entered string will be selected. 38403^C to cancel. ^G again to see original options. 38404========== h_select_txt_cc ========== 38405Messages with Cc: headers containing the entered string will be selected. 38406^C to cancel. ^G again to see original options. 38407========== h_select_txt_not_cc ========== 38408Messages without Cc: headers containing the entered string will be selected. 38409^C to cancel. ^G again to see original options. 38410========== h_select_txt_subj ========== 38411Messages with Subject: headers containing the entered string will be selected. 38412^C to cancel. ^X enters Subject: line of current message. 38413========== h_select_txt_not_subj ========== 38414Messages without Subject headers containing the entered string will be selected. 38415^C to cancel. ^X enters Subject: line of current message. 38416========== h_select_txt_all ========== 38417All messages containing the entered string will be selected. Headers and body, 38418but not encoded attachments, will be compared. Enter ^C to cancel. 38419========== h_select_txt_not_all ========== 38420All messages that don't contain the entered string will be selected. Headers 38421and body, but not encoded attachments, will be compared. Enter ^C to cancel. 38422========== h_select_txt_body ========== 38423All messages containing the entered string will be selected. Body text, but 38424not headers or encoded attachments, will be compared. ^C to cancel. 38425========== h_select_txt_not_body ========== 38426All messages that don't contain the entered string will be selected. Body 38427text, but not headers or encoded attachments, will be compared. ^C to cancel. 38428========== h_select_txt_recip ========== 38429Messages with Cc: or To: headers containing the entered string will be selected. 38430^C to cancel. ^G again to see original options. 38431========== h_select_txt_not_recip ========== 38432Messages without Cc: or To: headers containing the string will be selected. 38433^C to cancel. ^G again to see original options. 38434========== h_select_txt_partic ========== 38435Messages with Cc, To, or From headers containing the string will be selected. 38436^C to cancel. ^G again to see original options. 38437========== h_select_txt_not_partic ========== 38438Messages without Cc, To, or From headers containing the string will be selected. 38439^C to cancel. ^G again to see original options. 38440========== h_select_date ========== 38441If typed, date may be in DD-MMM-YYYY format (04-Jul-2006) or in ISO format 38442(2006-07-04). ^P/^N also changes default date. ^X enters date of current msg. 38443========== h_attach_index_whereis ========== 38444Enter some text that appears in the Attachment Index entry for the desired 38445attachment. The first attachment containing that text will be highlighted. 38446========== h_kb_lock ========== 38447Keystrokes entered here (up to a RETURN) comprise a password that must 38448be entered again later in order to unlock the keyboard. 38449========== h_compose_default ========== 38450N, compose a new message. R, set a role. 38451^C to cancel. 38452========== h_untranslatable ========== 38453Send using UTF-8 character set; Send but replace untranslatable characters 38454with question marks; return to the composer; or cancel message altogether. 38455========== h_compose_intrptd ========== 38456N, compose a new msg. I, continue interrupted msg. R, set a role. 38457^C to cancel. 38458========== h_compose_postponed ========== 38459N, compose a new message. P, continue postponed msg. R, set a role. 38460^C to cancel. 38461========== h_compose_intrptd_postponed ========== 38462N, compose a new msg. I, continue interrupted msg. P, continue postponed msg. 38463R, set a role. ^C to cancel. 38464========== h_compose_form ========== 38465N, compose a new message. F, use form letter. R, set a role. 38466^C to cancel. 38467========== h_compose_intrptd_form ========== 38468N, compose a new msg. I, continue interrupted msg. F, use form letter. 38469R, set a role. ^C to cancel. 38470========== h_compose_postponed_form ========== 38471N, compose a new message. P, continue postponed msg. F, use form letter. 38472R, set a role. ^C to cancel. 38473========== h_compose_intrptd_postponed_form ========== 38474N, compose a new msg. I, continue interrupted msg. P, continue postponed msg. 38475F, use form letter. R, set a role. ^C to cancel. 38476========== h_config_context_del_except ========== 38477If you delete the last exceptional collection you can only add it back by 38478manually editing the exceptions config file. 38479========== h_config_whereis ========== 38480To move quickly to a particular line, enter a search string or 38481^C to cancel. 38482========== h_config_edit_scorei ========== 38483Enter interval in the form (min,max). -INF and INF may be used to represent 38484-infinity and infinity. ^C to cancel change. RETURN to accept change. 38485========== h_config_add ========== 38486Enter desired value; use normal editing keys to modify (e.g. ^K, ^D). Just 38487pressing RETURN sets the Empty Value (this turns off any global default). 38488========== h_config_add_custom_color ========== 38489Enter a header fieldname. For example, "subject" or "from". 38490 38491========== h_config_add_pat_hdr ========== 38492Enter a header fieldname. For example, "reply-to" or "organization" or 38493any fieldname you want that isn't included already. 38494========== h_config_print_opt_choice ========== 38495You may edit either the initialization string (characters printed before 38496printing starts) or the trailer string. Choose one or ^C to cancel. 38497========== h_config_print_init ========== 38498Enter a C-style string for this. You may use common backslash escapes like 38499\\n for newline, \\ooo for octal character, and \\xhh for hex character. 38500========== h_config_change ========== 38501Edit the existing value using arrow keys, ^K to delete entire entry, ^D to 38502delete current (highlighted) character, etc. Enter ^C to cancel change. 38503========== h_config_replace_add ========== 38504Replace ignores the current default, Add places the current default in your 38505editing buffer as if you had typed it in. 38506========== h_config_insert_after ========== 38507Enter a nickname for this print command. (InsertBefore puts the new item 38508before the current line, InsertAfter puts it after the current line.) 38509========== h_config_print_cmd ========== 38510Enter command to be executed for the printer. Use normal editing keys 38511to modify, ^C to cancel, carriage return to accept current value. 38512========== h_config_role_del ========== 38513Answering Yes will remove this rule completely from your rules list. 38514========== h_config_role_addfile ========== 38515Type the name of a file to add to your configuration. You don't need to 38516use a file, you may add rules directly (with Add) without using a file. 38517========== h_config_role_delfile ========== 38518Answering Yes will remove this rule file completely from your rules list. 38519The rules data file itself will not be removed. 38520========== h_config_print_del ========== 38521Answering Yes will remove this printer completely from your printer list. 38522========== h_config_print_name_cmd ========== 38523You may edit the Nickname of this printer, the Command to be executed when 38524printing, or change the Options associated with this printer. 38525========== h_send_check_fcc ========== 38526Yes, send message without an Fcc. 38527No, return to composer. 38528========== h_send_check_subj ========== 38529Yes, send message without a Subject. 38530No, return to composer. 38531========== h_send_check_to_cc ========== 38532Yes, send message without a To address, or a Cc address, or a Newsgroup. 38533No, return to composer. 38534========== h_send_fcc_only ========== 38535Yes, copy message to Fcc only and send to NO recipients. 38536No, return to composer. 38537========== h_send_prompt ========== 38538Yes, send the message. 38539No or ^C, return to composer. 38540========== h_send_prompt_flowed ========== 38541Yes, send the message. No or ^C, return to composer. 38542What's Flowed? See Do Not Send Flowed Text in config screen. 38543========== h_send_prompt_dsn ========== 38544Yes, send the message. No or ^C, return to composer. 38545What's DSNOpts? See Enable Delivery Status Notification in config screen. 38546========== h_send_prompt_dsn_flowed ========== 38547Yes, send the message. No or ^C, return to composer. What's DSNOpts? See 38548Enable Delivery Status Notification. What's Flowed? See Do Not Send Flowed Text. 38549========== h_role_confirm ========== 38550Yes, use displayed role. No, compose without a role. 38551^C, cancel the message. ^T, select a role from your other eligible roles. 38552========== h_norole_confirm ========== 38553Return, compose without a role. 38554^C, cancel the message. ^T, select a role from your eligible roles. 38555========== h_custom_print ========== 38556Enter a Unix command that accepts its data on standard input. 38557Alpine will display any information the command sends to standard output. 38558========== h_convert_abooks_and_sigs ========== 38559You will be given the opportunity to convert address books and signature files 38560to remote configurations. 38561========== h_convert_abooks ========== 38562You will be given the opportunity to convert address books to remote 38563configurations. 38564========== h_flag_keyword ========== 38565Enter the name of the keyword you want to add for this folder. 38566No spaces, parentheses, braces, percents or asterisks are allowed. 38567========== h_select_keyword ========== 38568Enter the keyword you want to match, or use ^T to select a keyword from a list 38569of possible keywords for this folder. Use ! to look for non-matches instead. 38570========== h_type_keyword ========== 38571Enter the keyword you want to add. You may add a nickname in the next step. 38572No spaces, parentheses, braces, percents or asterisks are allowed. 38573========== h_type_keyword_nickname ========== 38574Enter an optional nickname for the keyword you want to add. 38575Type Carriage return to use the keyword name instead of a nickname. 38576========== h_convert_sigs ========== 38577You will be given the opportunity to convert signature files to remote 38578configurations. 38579========== h_convert_abook ========== 38580Yes is fairly safe. You will be ADDing a remote address book that is a copy 38581of the current address book. The current abook won't be removed automatically. 38582========== h_convert_sig ========== 38583Answering Yes copies the contents of the signature file into your Alpine 38584configuration file. After that, the contents of the file will not be used. 38585========== h_save_addman ========== 38586Enter the simple name of the folder you want to add. Carriage return to 38587accept what you have typed so far. ^C to get back to SELECT FOLDER screen. 38588========== h_reopen_folder ========== 38589Yes reopens the folder, as if you were starting over. This uncovers new mail. 38590No leaves the folder index as it was without discovering new mail. 38591========== h_convert_pinerc_server ========== 38592This is the name of the host (computer) where the remote Alpine configuration 38593will be stored. This should be an IMAP server that you have permission to use. 38594========== h_convert_pinerc_folder ========== 38595Enter the correct remote folder name. This folder is special and should 38596contain only configuration data. It shouldn't contain other mail messages. 38597========== h_role_compose ========== 38598Compose a New message, Reply to current message, Forward current message, or 38599Bounce message. Then you will be asked to choose one of your Roles to be used. 38600========== h_role_aggregate ========== 38601Compose a reply, or forward, or bounce the selected messages. Then you 38602will be asked to choose one of your Roles to be used for this operation. 38603========== h_save_size_changed ========== 38604The reported size of a message is not the same as the actual size. Answer Yes 38605to continue and hope for the best or No to Cancel the entire Save. 38606========== h_select_by_larger_size ========== 38607Enter a number or ^C to cancel. All messages greater than this many characters 38608in size will be selected. Examples: 2176, 1.53K (1530), or 3M (3000000). 38609========== h_select_by_smaller_size ========== 38610Enter a number or ^C to cancel. All messages less than this many characters 38611in size will be selected. Examples: 2176, 1.53K (1530), or 3M (3000000). 38612========== h_preserve_field ========== 38613Use 'p' to toggle between preserving or not preserving the original To: 38614and Cc: fields of the message. Enter ^C to cancel message. 38615========== h_privacy_policy ========== 38616x-alpine-http:http://alpine.x10host.com/privacy.html 38617========== h_apache_license ========== 38618x-alpine-http:http://alpine.x10host.com/legal/apache_license.html 38619 38620