Domain Configuration Editor
The domain configuration editor can be reached via the Setup Primary domain… menu selection and allows you to enter several key pieces of information regarding your domain setup. Your primary domain is the default domain name and set of configuration options that your users will use to send and receive their email. Only one primary domain can be configured, but MDaemon can manage mail for any number of Secondary Domains (MDaemon PRO only), and store mail for any number of Domain Gateways as well.
The Domain Configuration editor is a tabbed dialog containing the following sections, which are necessary for configuring MDaemon v8.
Domain
This dialog contains your Primary Domain's name and IP address, and your HELO domain name and machine name.
Delivery
Here you will specify the degree to which you want MDaemon itself to handle delivery of mail versus relaying mail to an ISP or gateway host for them to deliver for you.
Ports
On this dialog, the ports that MDaemon will monitor and use for SMTP and POP email delivery are designated. You will also designate the port on which MDaemon will listen for IMAP events, and the UDP port used for querying DNS servers. In most cases the default settings will not need to be changed. However, being able to configure these port settings is useful when attempting to integrate MDaemon with various other products that you may be using on your system.
DNS
This dialog is used for designating a primary and backup DNS server's IP address. It also contains various controls governing MDaemon's handling of MX and A records and SMTP errors that are encountered during mail delivery.
Timers
This area contains various time limits that MDaemon will observe while connecting to remote hosts, waiting for protocol dialogs, waiting for DNS server responses, and so on. In addition, this dialog contains the Maximum Message Hop Count limit, which is used to help prevent messages from being caught in a delivery loop.
Sessions
Here you will designate the maximum number of concurrent session threads that MDaemon will use for sending and receiving SMTP, POP, and IMAP mail. You will also designate the number of messages that MDaemon will attempt to send/receive at the same time. In addition, if you so choose, you can set a limit on the number of outbound SMTP messages that will be spooled per session thread.
Dequeue
Use the Dequeue tab to have MDaemon automatically send ETRN, QSND, or similar commands to an ISP in order to have them dequeue email that you may have them "holding" for you so that you can receive this sort of email via SMTP rather than DomainPOP.
Archival
Use the Archival tab to save a copy of all inbound and outbound mail that MDaemon processes. You can also choose whether this archive will include Mailing List or MultiPOP messages or omit them.
Pruning
This tab is used for denoting the amount of time that an account may remain inactive before it will be deleted. It also contains controls for limiting how long messages may be stored.
Pre-Processing
This dialog is used to designate the path to any program that you may want MDaemon to run immediately before processing and delivering of mail. Here you can also set parameters for MDaemon's actions related to this process.
Unknown Local Mail
This dialog contains various settings that you can use to control what MDaemon will do with messages that arrive at the server addressed to a Local domain but to an unknown or undefined user's mailbox. The various control choices include: sending the email message back to the sender, sending it to the Postmaster, putting it in the Bad Message queue, and forwarding the message to another host. These controls may be set to act individually or in any combination.
Primary Domain Properties
Primary domain name
Enter your primary domain name here. This is the default domain name used when creating new accounts. Typically, the value entered here will be the registered Internet domain name that a DNS server resolves to the IP address of the local machine running the server, or a qualified alias of that name.
Alternatively, you may choose to use a fictitious domain name for your Primary Domain Name (such as "company.mail") in some situations. When configuring your server in this way it may be necessary to use the Header Translation feature, and/or the Domain Name Replacement Engine, to enable proper mail distribution.
HELO domain name
This Domain name will be used in the SMTP HELO/EHLO instruction when sending mail. In most cases, this will be your Primary Domain Name.
Machine name
This name will be inserted into a message's Received headers. When you are using more that one machine for a particular domain (as a backup server, for example) it can sometimes be more difficult to track a message's path through the system with only IP addresses and domain names in the headers-it is more difficult to tell which machines handled the message. Inserting a name into the headers that specifically identifies each machine that processes the message can make this easier. If you do not provide a specific identifier in this control then the Primary domain name will be used.
Primary Domain IP
This is the Primary Domain's IP address.
Bind listening sockets to this IP only
Selecting this switch causes MDaemon to bind its listening network sockets using the specific IP address found in the Domain IP text box. Ordinarily, this control will only need to be used in certain circumstances when hosting multiple domains.
Mail Delivery Options
Always send every outbound email to the server specified below
Select this option if you want all outbound email, regardless of its destination domain, to be spooled to a gateway host for routed delivery. If selected, all outbound email will be sent to the host specified in the ISP or smart host's IP or domain name field. Typically, this feature is useful during high volume periods when direct message delivery would result in an excessive taxation of server resources.
Try direct delivery but send problem emails to the server specified below
Click this option if you want to spool only undeliverable outbound email to the gateway host specified in the ISP or smart host's IP or domain name field. Undeliverable mail is email destined for hosts that could not be resolved to an actual IP address (such as an unregistered gateway to a remote network) or email destined for a host that was resolved properly but could not be connected to directly or is refusing direct connections. Rather than return such mail to its originator, this option causes MDaemon to pass the message off to a more powerful MTA. Sometimes the mail system run by your ISP may have routed methods of mail delivery to which your local server may not have direct access.
Mail Server
Specify your ISP or mail host's domain name or IP address here. This is generally the SMTP server on your ISP.
Access to the above mail server requires a log in
As an added security measure, some ISPs require their customers to log in before they are allowed to send mail through the ISPs servers. If your ISP or mail host requires this then use this option to specify your login credentials.
User name
Enter you ISP user name or login here.
Password
Use this option to specify your ISP or mail host login password.
Access to the above mail server requires a POP mailbox check
As an added security measure, some ISPs require their customers to log in to a POP mailbox before they are allowed to send mail through the ISPs servers. If your ISP or mail host requires this then click this button to open the POP Check dialog on which you can specify your login credentials. See the POP Check dialog below.
Always send all outbound email directly to the recipient's mail server
When this option is chosen, MDaemon will attempt to deliver all mail directly instead of passing it to another host. MDaemon will place undeliverable messages into its Retry System and continue to attempt to deliver them according to the parameters and time intervals that you set in the Retry Configuration dialog. You can access this dialog by clicking the Click here to configure how undeliverable mail is handled button.
Click here to configure how undeliverable mail is handled
Click this button to open the Retry Configuration dialog from which you can designate how often MDaemon will attempt to deliver messages that encounter problems during the delivery process. You can also specify a time interval after which the attempts will cease, and what to do with these messages after the final attempt is made. See the Retry Configuration dialog below.
Perform a POP check before sending waiting mail
Click this checkbox if you are required to perform a POP check before sending waiting mail.
Host name or IP address
Enter the host or IP address to which you wish to connect.
POP logon
This is the POP account's logon or account name.
POP password
This is the account's POP password.
Retry Frequency
Keep message in the primary queue for at least XX minutes
This setting governs the length of time a message will remain in the primary queue before being removed and placed in the retry queue. The primary queue will generally attempt to deliver the message quicker and more frequently than the retry queue.
Retry sending undeliverable mail once every XX minutes
This setting determines how frequently the messages in the retry queue are processed.
Inform the sender when message is placed in retry queue
This switch will inform the sender when his/her message is removed and placed in the retry queue. The text of this message can be found (and edited) in the DELWARN.DAT file.
Inform the sender when subsequent delivery attempts fail
If a delivery attempt of a message in the retry queue fails, a message explaining this fact will be dispatched to the sender of the message. The text of this message can be found (and edited) in the DELWARN.DAT file.
Include original message when informing sender
Click this option to include the original message as an attachment in the above notification messages to the sender.
Ultimate Fate of Undeliverable Mail
If a message is still undeliverable after XX days then:
This setting determines the number of days that a message can remain in the retry queue before being removed.
Place the undeliverable message in the bad message queue
Once a message has reached the time limit set in the If A Message Is Still Undeliverable After xx Days Then: control, a copy of that message will be moved to the bad message directory if this switch is enabled.
Inform the sender that the message could not be delivered
Once a message has reached the time limit set in the If A Message Is Still Undeliverable After xx Days Then: control, this switch will cause MDaemon to send a message to the sender informing them that the message has been permanently removed from the server. The text of this message can be found (and edited) in the DELERR.DAT file.
Inform the postmaster that the message could not be delivered
If this switch is enabled, the postmaster will be notified when a message has been permanently removed from the retry system.
. . . unless it's an MDaemon auto-generated message
The retry system will never inform MDaemon when an auto-generated message fails to be delivered. However, because such information may be useful to the postmaster, he or she will be informed when these messages cannot be delivered. Click this checkbox if you do not want the postmaster to be informed when auto-generated messages cannot be delivered. Examples of auto-generated messages are return-receipt notifications, auto-responder generated messages, results of account processing, and so on.
Include original message when informing sender
Click this option to include the original message as an attachment in the delivery failure messages to the sender.
Create outbound SMTP events using this TCP port
This port will be used when mail is sent to other SMTP servers.
Listen for inbound ODMR events using this TCP port
MDaemon will monitor this port for incoming On-Demand Mail Relay (ODMR) connections such as ATRN from Domain Gateways.
Dedicated SSL port for SMTP
This is the port dedicated to SMTP mail sessions using a Secure Sockets Layer (SSL) connection. See SSL & Certificates for more information.
POP/IMAP Server Ports (IMAP Available in MDaemon Pro only)
Listen for inbound POP events on this TCP port
MDaemon will monitor this port for incoming connections from remote POP clients.
Create outbound POP events using this TCP port
This port will be used when mail is retrieved from POP3 servers.
Dedicated SSL port for POP
This is the port dedicated to POP3 mail clients using a Secure Sockets Layer (SSL) connection. See SSL & Certificates for more information.Listen for inbound IMAP events on this TCP port
MDaemon will monitor this port for incoming IMAP requests.
Dedicated SSL port for IMAP
This is the port dedicated to IMAP mail clients using a Secure Sockets Layer (SSL) connection. See SSL & Certificates for more information.
DNS/LDAP/WebAdmin Server Ports
Query DNS servers using this UDP port
Enter the Port you want MDaemon to use for sending and receiving data grams to the DNS server.
LDAP port for database & address book posting
MDaemon will post database and address book information to your LDAP server on this port.
Listen for WebAdmin connections on this TCP port
This is the port that MDaemon will monitor for WebAdmin connections.
Return port settings to defaults
This button returns all the port settings to their standard values.
Bind to new port values now
When you alter the values of any of the port settings you will need to press this button to have your changes take immediate effect. Otherwise, your changes will not be put into place until the next time the server is started.
DNS Server Settings
Try to use DNS servers defined in windows TCP/IP settings
Windows sometimes keeps a DNS server IP address in the local TCP/IP configuration. If this is the case on your computer then you can check this option. If MDaemon cannot find a locally maintained DNS server it will continue on and use the ones specified on this screen.
Primary DNS server IP address
Enter the IP address of the DNS server that you want MDaemon to query for 'A' and 'MX' records. In order to ensure proper operation this entry must be specified.
Backup DNS server IP address
Enter the IP address of the backup or secondary DNS server that you want MDaemon to query for 'A' and 'MX' records. This entry is optional but recommended.
Retry failed lookup attempts this many times
If a lookup attempt fails, this is the number of times that MDaemon will repeat the attempt. If you have designated a backup DNS server, both servers will be included in each lookup attempt.
MX Record Processing
Immediately return mail when DNS says A record domain does not exist
Click this option to cause MDaemon to immediately return a message when a DNS lookup shows that the A record domain doesn't exist.
Query DNS servers for 'MX' records when delivering mail
Enable this control if you want MDaemon to query your designated DNS servers for 'MX' records when it is attempting to deliver mail.
Use 'A' record IP addresses found within 'MX' record packets
Click this checkbox if you want MDaemon to attempt delivery to 'A' record IP addresses when such are discovered during 'MX' record processing.
Send message to next MX host when an SMTP error occurs
With this function active, MDaemon will continue to attempt message delivery to the next 'MX' hosts even if the current 'MX' returns a fatal SMTP error.
Abort delivery if MX returns 5XX after RCPT command
Normally, MDaemon will continue to attempt to deliver messages to each MX host when receiving a 5XX response to the RCPT command during an SMTP session. Click this checkbox if you want MDaemon to abort the delivery attempt when receiving such a response.
Immediately return mail when DNS says domain does not exist
Click here to cause MDaemon to immediately return a message if a DNS lookup returns a "Domain Does Not Exist" message. This will prevent that sort of mail from needlessly going into the delivery retry cycle.
Local Lookup Tables
Hosts file…
Before querying the DNS servers, MDaemon will first attempt to resolve an address by processing the Windows HOSTS file. If this file contains the IP address of the domain in question, MDaemon will not need to query the DNS server.
Edit MXCACHE file
Click this button to view or edit the MXCACHE.DAT file with MDaemon's text editor.
Edit hosts File
Click this button to view or edit the HOSTS file with MDaemon's text editor.
Event Timers (IMAP options available in Pro version only)
Wait XX seconds for sockets to connect before giving up
After initiating a connection request MDaemon will wait this many seconds for the remote system to accept the connection. If the remote system does not respond within this time frame MDaemon will send the message to either the Gateway Host or Retry Queue depending upon which option you have chosen on the Domain/ISP tab of the Domain Configuration Editor.
Wait XX seconds for protocol dialog to start before giving up
Once a connection has been established with a remote host, this is the number of seconds that MDaemon will wait for the remote host to begin the SMTP or POP3 protocol dialog. If the remote host does not begin the protocol session within this time frame MDaemon will send the message to either the Gateway Host or Retry Queue depending upon which option you have chosen on the Domain/ISP tab of the Domain Configuration Editor.
Wait XX seconds for MX DNS server responses
While using DNS services to resolve 'MX' hosts for remote domains, MDaemon will wait for responses to its 'MX' queries for this number of seconds. If the DNS server does not respond within this time frame MDaemon will attempt to deliver the message to the IP address specified in the remote host's 'A' DNS record. If that attempt fails MDaemon will send the message to either the Gateway Host or Retry Queue depending upon which option you have chosen on the Domain/ISP tab of the Domain Configuration Editor.
Wait XX seconds for A-record DNS server responses
This timer governs how long MDaemon will wait while attempting to resolve a remote host's IP address. If the attempt fails, MDaemon will send the message to either the Gateway Host or Retry Queue depending upon which option you have chosen on the Domain/ISP tab of the Domain Configuration Editor.
SMTP and POP sessions timeout after XX inactive minutes
If a successfully connected and operating session remains inactive (no i/o) for this length of time, MDaemon will abort the transaction. MDaemon will try again at the next scheduled processing interval.
IMAP sessions timeout after XX inactive minutes
If an IMAP session has no activity for this number of minutes, MDaemon will close the session.
IMAP NOOP and IDLE commands trigger 1 minute inactivity timeout
When this checkbox is enabled, the IMAP inactivity timer will be set to one minute when a NOOP or IDLE command is encountered. Some IMAP clients will issue NOOP commands simply to keep sessions open even though there is no actual mail transaction activity going on. This feature will prevent such sessions from remaining active and thus will reduce resources consumed, which can be extremely useful for higher volume IMAP based mail sites.
Loop Detection and Control
Maximum message hop count (1-100)
RFC standards stipulate that a mail server must stamp each message each time that it is processed. These stamps can be counted and used as a stopgap measure against recursive mail loops that can sometimes be caused by errant configurations. If undetected, these looping message delivery cycles will consume your resources. By counting the number times the message has been processed, such messages can be detected and placed in the bad message directory. The assumption is that if a message hasn't reached its recipient after being processed by a given number of mail servers then there is probably a mail loop in progress. Most likely, the default setting of this control should be sufficient to prevent mail loops and will not need to be changed.
Latency
Latency - XX milliseconds
This is the delay in milliseconds between POP/SMTP/IMAP protocol commands. This is useful for preventing high-speed connections from processing data faster than the recipient can extract it. This delay takes effect only during the POP/SMTP/IMAP protocol command sequence - the actual transfer of a mail message file is already fully buffered.
SMTP
Maximum concurrent SMTP outbound sessions
The value entered here represents the maximum possible outbound SMTP sessions that will be created when it is time to send outbound mail. Each session will send outbound messages until either the queue is empty or the Max SMTP outbound messages spooled per session setting has been reached. For example, if the outbound mail queue has twenty messages waiting when it is time to send mail and the value of this setting is five, then five sessions will be simultaneously created and each will consecutively deliver four messages.
You should experiment with the number of sessions that yield the best performance for your bandwidth. It is possible to specify so many sessions that your bandwidth will be overloaded or your Windows machine will run out of resources and you will lose delivery efficiency. Remember, each SMTP session created by MDaemon will deliver messages consecutively and therefore four sessions delivering two messages each might perform better and faster than eight threads delivering only one message each. A good place to start would be five to ten threads when using a 28.8k modem and ten to fifteen for ISDN.
Maximum SMTP outbound messages spooled per session
This setting places a limit on the number of individual messages that each session will send before it stops delivering mail and frees itself from memory. Ordinarily, you should leave this control set to zero, which will cause each session to continue delivering messages until the queue is empty.
Maximum concurrent SMTP inbound sessions
This value controls the number of concurrent inbound SMTP sessions that the server will accept before it begins responding with a "Server Too Busy" message.
POP/IMAP (IMAP option available in Pro version only)
Maximum concurrent POP outbound sessions
The value entered here represents the maximum possible outbound POP sessions that will be created when it is time to collect DomainPOP and MultiPOP mail. Each session will collect this type of mail until all DomainPOP and MultiPOP servers have been processed, and all mail has been collected. For example, if there are fifteen MultiPOP sessions amongst all of your users and the value of this setting is set to three, then each session will collect mail from five MultiPOP sources.
You should experiment with the number of sessions to determine what number will yield the best performance for your bandwidth. It is possible to specify so many sessions that your bandwidth will be overloaded, or your Windows machine will run out of resources and you will lose processing efficiency. Remember that each POP sessions created by MDaemon will collect mail until all sources have been exhausted. Therefore, four sessions collecting mail from twenty sources might perform better and faster than twenty sessions collecting from a single source. A good place to start would be two to five sessions with a 28.8 modem and five to ten for ISDN.
Maximum concurrent POP/IMAP inbound sessions
This value controls the maximum number of concurrent POP and IMAP inbound mail sessions that the server will accept before it begins responding with a "Server Too Busy" message.
Dequeue Engine
Signal ISP to dequeue waiting mail
When it is time to process remote mail MDaemon can connect to any server on any port and send any string that you wish to send. This is useful when you need to signal a remote server to release your mail by sending some string to them. For example, ATRN, ETRN, or QSND. You can also use this feature when a FINGER or TELNET session is briefly required in order for your ISP to determine that you are online.
Send signal once every [xx] times remote mail is processed
By default the dequeue signal will be sent each time that remote mail is processed. Entering a number into this control will prevent the dequeue signal from being sent every time. It will be sent every x number of times as designated. For example, setting this value to "3" would cause the signal to be sent every third time that remote mail is processed.
Remote Server
Send signal to this remote host
This is the host to which you wish to connect to signal the release of your mail.
Use this TCP port
Enter the port on which you wish to make the connection. The default is 25 (the SMTP port), which is appropriate for the ETRN or QSND signaling method. Port 366 is typically used for ATRN, and port 79 is used for FINGER.
Dequeue Instruction
Send this string to host
This control is for specifying the text string that needs to be sent in order for your email to be released. For example, the ETRN method requires the text "ETRN" followed by the domain name of the site being queued. Other methods require different text to be sent. Consult your ISP if you need more information on what to send to unlock your mail queue.
Send SMTP "EHLO" before transmitting string to host
If you enable this checkbox then you should be connecting to an SMTP server to signal release of your mail. This switch causes an SMTP session to be initiated with the specified host and allows the session to progress just beyond the SMTP "EHLO" stage before sending the unlock string.
I must authenticate before sending the dequeue signal (required for ATRN)
As a security measure, in order to prevent unauthorized users from attempting to dequeue their customers' email, some ISPs require their customers to authenticate themselves via ESMTP AUTH before sending the dequeue signal. If this is the case for your ISP, you can open the Dequeue AUTH dialog by clicking this button. There you can enter the required authentication information. See Dequeue AUTH below.
Session Windows
Hide dequeue session windows while they are in progress
Click this checkbox if you want to hide sessions windows while they are in progress.
switched on and working. If the value entered is an IP address and
not a domain name then the connection will be made using that IP address.
On-Demand Mail Relay (ODMR)
We believe that the best relay (queue/dequeue) method currently available for hosting your email is On-Demand Mail Relay (ODMR). This method is superior to ETRN and other methods in that in requires authentication before mail is dequeued. Further, it utilizes a new ESMTP command called ATRN that does not require the client (customer) to have a static IP address because it immediately reverses the flow of data between the client and server (provider) and despools the messages without having to make a new connection to do so (unlike ETRN).
MDaemon fully supports ODMR on the client side via using the ATRN command and authentication controls on the Dequeue tab, and on the server side using the Domain Gateways features on the ATRN / AUTH tab of the Gateway Editor.
Many mail servers do not yet support ODMR, therefore you should check with your provider before attempting to use it.
Dequeue Authentication
Use ESMTP AUTH when sending dequeue signal to host
Besides requiring their customers to authenticate themselves before sending mail, some ISPs require their customers to authenticate themselves before sending the signal to dequeue any incoming mail that is being held for them. If you are required to do this then click this checkbox to cause MDaemon to send your authentication information before attempting to collect any queued email.
AUTH logon
If authentication is required before sending the signal to dequeue your mail, place the required AUTH logon parameter here.
AUTH shared secret
Enter the password used in the AUTH shared secret required by your ISP.
Archive Settings
Archive a copy of all inbound/outbound mail
This switch enables the archival engine. Activating it will cause a copy of every inbound and outbound message that passes through the server to be sent to the address(es) specified in the control following.
Send a copy of every inbound/outbound email to these addresses
Enter one or more addresses to which you wish to send archival messages. Multiple addresses must be separated by a comma. You may specify Local and Remote addresses and Address Aliases.
Include MDaemon mailing list messages in the archive also
Select this switch if you want archived mail to include your mailing list messages.
Include MultiPOP collected mail in the archive also
Select this switch if you want archived mail to include messages collected through MDaemon's MultiPOP feature.
Label archive messages with "(archive copy)" in message subject
Enable this switch if you want to include "(Archive Copy)" in the Subject: header of archived mail.
DOMAIN CONFIGURATION EDITOR 53
Archive to Public Folders (MDaemon PRO only)
Archive inbound mail
Click this check box to save a copy of all inbound messages in the Mail Archive public folder. By default, this folder is only accessible only by the Postmaster via IMAP. If you want to alter the permissions or grant access to more users you can do so from the Access Control List on the Public Folders dialog.
…archive based on recipient address
Click this option if you want the inbound mail archive to be categorized by the recipient's email address.
Archive outbound mail
Click this check box to save a copy of all outbound messages in the Mail Archive public folder. By default, this folder is only accessible only by the Postmaster via IMAP. If you want to alter the permissions or grant access to more users you can do so from the Access Control List on the Public Folders dialog.
…archive based on sender address
Click this option if you want the outbound mail archive to be categorized by the sender's email address.
Provide separate archives for each MDaemon domain
Click this option if you want to maintain a separate archive for each domain.
The options in the first section of this dialog are used to designate when or if inactive accounts or old messages belonging to this domain will be deleted by MDaemon. Each day at midnight MDaemon will remove all messages and accounts that have exceeded the time limits stated. There are similar controls used for setting these limits for your other domains on the Secondary Domains dialog. There are also controls on the Account Editor that can be used to override these settings for individual accounts. The remaining options are global, applying to all domains.
Account and Old Mail Pruning
Automatically delete account if inactive for XX days (0 = never)
Specify the number of days that you wish to allow an account belonging to this domain to be inactive before it will be deleted. A value of "0" in this control means that accounts will never be deleted due to inactivity.
Delete messages older than XX days (0 = never)
A value specified in this control is the number of days that any given message may reside in a user's mailbox before it will be deleted by MDaemon automatically. A value of "0" means that messages will never be deleted due to their age.
Purge deleted IMAP messages older than XX days (0 = never)
Use this control to specify the number days that you wish to allow IMAP messages that are flagged for deletion to remain in your users' folders. Messages flagged for deletion longer than this number of days will be purged from their mailboxes. A value of "0" means that messages flagged for deletion will never be purged due to their age.
Delete old messages from IMAP folders as well
Click this checkbox if you want the "Delete messages older than…" control to apply to messages in IMAP folders as well. When this control is disabled, messages contained in IMAP folders will not be deleted, regardless of their age.
Public folder pruning
Delete messages older than XX days (0=never)
Specify a number of days in this option if you want old messages to be deleted from Public Folders.
Content Filter Cleanup
Delete all quarantined files
Click this option if you want all quarantined file attachments to be deleted each night.
Delete all quarantined messages
Click this option if you want all quarantined messages to be deleted each night.
Delete all restricted attachments
Click this option if you want all restricted attachments to be deleted each night.
Local/Remote Queue Pre-processing
Just before processing the (local/remote) mail queue run this program
This field specifies a program path and name that will be executed just prior to the processing and delivery of any RFC-822 messages that might be in the local or remote message queues. If complete path information is not provided, MDaemon will first search for the executable in the MDaemon directory, then in the Windows System directory, next in the Windows directory, and finally the directories listed in the PATH environment variable.
…suspend all operations for xx seconds
The value entered here determines how MDaemon will behave while the specified program is in progress. MDaemon can be configured to pause its execution thread for the number of seconds specified while waiting for the process thread to return. If the process returns before the number of seconds has elapsed, MDaemon will resume its execution thread immediately. Enter the numeral zero in this control and MDaemon will not suspend operations at all. Entering "-1" will cause MDaemon to wait until the process returns, no matter how long that might be.
Don't execute when queue is empty
Enable this switch if you do not want the specified program to run when the queue is empty.
Force process to terminate
Sometimes the process you need to run may not terminate on its own. This switch will cause MDaemon to force the session to terminate once the time specified in …Suspend All Operations For XX Seconds has elapsed. This switch does not work if the elapsed time interval is set to "-1".
Run process in a hidden window
Click this checkbox if you want the process to run in a hidden window.
What To Do With Mail For Unknown Local Users
Route message back to sender
Messages that arrive at the server destined for unknown yet supposedly local users will be returned to the message originator if this option is activated.
Send message to the "Postmaster" user
Messages that arrive at the server destined for unknown yet supposedly local users will be forwarded to whatever user has been aliased as the postmaster.
Place message in bad message directory
Messages that arrive at the server destined for unknown yet supposedly local users will be routed to the bad message directory.
Advanced Options
Enable advanced options
Click this checkbox to enable the following advanced mail routing properties.
Send the message to this host
If a mail host is specified here, messages addressed to unknown local users will be sent to it.
Use this address in SMTP envelope
This address will be used in the SMTP "Mail From:" statement used during the session handshaking with the accepting host. Normally the sender of the message is used in this portion of the SMTP envelope. If you require an empty command (MAIL FROM <>) then enter "[trash]" into this control.
Use this TCP port
MDaemon will send this message on the TCP port specified here rather than the default SMTP outbound port.
