| 1 |
Template: echolot/address
|
| 2 |
Type: string
|
| 3 |
_Description: E-mail address of your pinger
|
| 4 |
Email to this address must reach your pinger somehow. Either it gets
|
| 5 |
delivered to your box directly or you have fetchmail installed or some
|
| 6 |
other way.
|
| 7 |
|
| 8 |
Template: echolot/operator
|
| 9 |
Type: string
|
| 10 |
_Description: Operator address for your pinger
|
| 11 |
Specify an address for the pinger operator.
|
| 12 |
|
| 13 |
Template: echolot/sitename
|
| 14 |
Type: string
|
| 15 |
_Description: Site name
|
| 16 |
Choose a name for your pinger site. This will be shown in all pages
|
| 17 |
echolot produces.
|
| 18 |
|
| 19 |
Template: echolot/addnow
|
| 20 |
Type: boolean
|
| 21 |
Default: true
|
| 22 |
_Description: Add known remailers?
|
| 23 |
This package has a built in list of some remailers. If you want they can
|
| 24 |
be added to Echolot's database now. Otherwise you have to populate it by
|
| 25 |
hand.
|
| 26 |
.
|
| 27 |
If you choose to add them Echolot will also fetch keys and configuration
|
| 28 |
data immediatly.
|
| 29 |
|
| 30 |
Template: echolot/recipient_delimiter
|
| 31 |
Type: string
|
| 32 |
_Description: Recipient delimiter
|
| 33 |
Echolot strongly recommends using user defined mailboxes, i.e. mail sent
|
| 34 |
to echolot+<somerandomstring>@yourdomain should reach echolot too.
|
| 35 |
.
|
| 36 |
In postfix this can be done by adding
|
| 37 |
recipient_delimiter = +
|
| 38 |
to your main.cf file. (If you know the procedure for other MTAs, please
|
| 39 |
file a wishlist bug)
|
| 40 |
.
|
| 41 |
If you cannot or do not want to enable this please use an empty string.
|
Parent Directory
| 
Revision Log