Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
server:mail [2020/07/01 21:54] – grasshopper | server:mail [2023/02/18 14:02] – New section on Recipients, for Keyop digital man | ||
---|---|---|---|
Line 16: | Line 16: | ||
The SMTP server also supports the SEND, SAML and SOML commands for delivering instant messages (a.k.a. telegrams) to users of the BBS. | The SMTP server also supports the SEND, SAML and SOML commands for delivering instant messages (a.k.a. telegrams) to users of the BBS. | ||
+ | |||
+ | ==== Recipients ==== | ||
+ | When receiving email messages via SMTP, the Synchronet mail server can match recipient names to a BBS user account by their alias or optionally, their real name. | ||
+ | |||
+ | === Special Characters === | ||
+ | Non-alphanumeric characters are ignored when matching recipient names to BBS user aliases. So for example, the following will all match the user " | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | |||
+ | === Real Names === | ||
+ | When matching recipient names to BBS real names (if so enabled by the sysop by setting SCFG-> | ||
+ | |||
+ | === Special Aliases === | ||
+ | Recipient names configured in '' | ||
+ | |||
+ | === User Number === | ||
+ | Receiving by user account number is also optionally supported, not not encouraged and disabled by default. | ||
==== Special Prefixes ==== | ==== Special Prefixes ==== | ||
Line 47: | Line 66: | ||
The Synchronet Mail Server recognizes the incoming special address format: ''//< | The Synchronet Mail Server recognizes the incoming special address format: ''//< | ||
- | The //< | + | The //< |
- | sent to the destination user. If the tag matches a line in the '' | + | sent to the destination user. If the tag matches a line in the '' |
- | This feature allows you (the sysop) to easily create and use " | + | This feature allows you (the sysop) to easily create and use " |
==== Anti-SPAM ==== | ==== Anti-SPAM ==== | ||
Line 135: | Line 154: | ||
^ Key ^ Default Value ^ Description ^ | ^ Key ^ Default Value ^ Description ^ | ||
- | | Interface | + | | AutoStart |
- | | POP3Interface | + | | Interface |
- | | OutboundInterface | 0.0.0.0 | + | | POP3Interface |
+ | | OutboundInterface | [global] | ||
| SMTPPort | | SMTPPort | ||
| SubmissionPort | | SubmissionPort | ||
Line 144: | Line 164: | ||
| TLSPOP3Port | | TLSPOP3Port | ||
| MaxClients | | MaxClients | ||
+ | | MaxConcurrentConnections | 0 | Maximum number of concurrent connections (without login) from the same IP address (0 = unlimited) | | ||
| MaxInactivity | | MaxInactivity | ||
| MaxDeliveryAttempts | 50 | Maximum number of outbound mail delivery attempts before mail is bounced back to sender | | | MaxDeliveryAttempts | 50 | Maximum number of outbound mail delivery attempts before mail is bounced back to sender | | ||
Line 153: | Line 174: | ||
| MaxMsgsWaiting | | MaxMsgsWaiting | ||
| ConnectTimeout | | ConnectTimeout | ||
- | | HostName | + | | HostName |
- | | TempDirectory | + | | TempDirectory |
| RelayServer | | RelayServer | ||
| RelayPort | | RelayPort | ||
Line 167: | Line 188: | ||
| InboundSound | | InboundSound | ||
| OutboundSound | | OutboundSound | ||
- | | NewMailNotice | + | | JavaScript* |
- | | ForwardNotice | + | | LogLevel |
- | | JavaScript* | + | | BindRetryCount |
- | | LogLevel | + | | BindRetryDelay |
- | | BindRetryCount | + | | LoginAttempt* |
- | | BindRetryDelay | + | |
- | | LoginAttempt* | + | |
| Options | | Options | ||
Line 212: | Line 231: | ||
| NO_RECYCLE | | NO_RECYCLE | ||
| KILL_READ_SPAM | | KILL_READ_SPAM | ||
- | | MUTE | Disable all sound (WAV) files from playing | | ||
- | |||
- | ===== Email Security ===== | ||
- | |||
- | In order to prevent one's emails from being labeled as SPAM, or worse, rejected, one can setup email security through a DNS. More and more Servers are starting to reject email that is not being secured to prove that it has come from a reliable source and not some spammer. This section will walk through the steps of securing your email server. | ||
- | |||
- | //Note: This section assumes one owns a domain name and that domain name is the name to be used for one's BBS. If one uses synchro.net for emailing purposes, this will not apply in that case.// | ||
- | |||
- | ==== Dynamic IP Address - No problem ==== | ||
- | - Find a Dynamic Domain Server (DDNS) provider | ||
- | - There are many out there. There are even some free ones that will give at least one address which is all that is needed | ||
- | - This provider should provide directions on this initial setup | ||
- | - Setup an " | ||
- | - This name won't be visible and serves as just a target for one's owned domain name to point to | ||
- | - Next step is to setup records on the owned Domain Name | ||
- | |||
- | ==== Domain Name Records Setup ==== | ||
- | - Log into one's provider of the domain name | ||
- | - Create an " | ||
- | - Create a " | ||
- | - This should point to the address created in the DDNS provider | ||
- | - Create another " | ||
- | - This should also point to the address created in the DDNS provider | ||
- | - Create a " | ||
- | - This should point to the ' | ||
- | - Next is to setup the " | ||
- | |||
- | ==== Creating the ' | ||
- | - Still logged into one's provider of the owned domain name, create a " | ||
- | - The host name should be the " | ||
- | - The TXT Value will contain the information that will state which domain names and IPs are OK if email comes from one of those. One will want to include all possible Domain Name/IP addresses that could serve up email. This part takes a little more effort to get the text right. Thankfully there are free tools available on the internet that will generate the SPF text for you. These are a couple of those sites. | ||
- | - https:// | ||
- | - https:// | ||
- | - Create another " | ||
- | - The host name for this record has to be _dmarc | ||
- | - The value specifies where to send reports of abuse of one's domain name. | ||
- | - There is an online tool to help with the creation of the value of this record: | ||
- | - https:// | ||
- | - Create yet another " | ||
- | - This record will allow for the verification of the signage on the email that is placed by the MTA((Mail Transport Agent)) using a private key and the DKIM record has the public key. Thus emails can be verified against the DNS record. | ||
- | - **Note:** DKIM capabilities is currently __not__ available in Synchronet. | ||
- | - None-the-less, | ||
- | === Validation Check === | ||
- | * There are a couple of sites that can help with validating that the records are setup correctly: | ||
- | * https:// | ||
- | * https:// | ||
- | * Check for any errors and correct them. If most every check turns up ' | ||
- | * //Note: If your SPF record doesn' | ||