Configuring Message Queue

All MailBee Message Queue configuration is stored in "mmq.ini" file which resides in the same directory where MailBee Message Queue is installed. This file has several sections:

Section [Main]
- LicenseKey - (required) you get it when download or register MailBee Message Queue
- QueueDirPath - (required) path to folder where message files are stored. This is the same path you should use as argument of SendToQueue method of MailBee.SMTP object
- ServiceName - (required) - the name to set for the service. Usually, "MailBee Message Queue". You can change it if you need to have multiple instances of MMQ (running simultaneously if desired)
Section [Logging]
- Enablelogging - (default is No). If "Yes", logging is on
- LoggingLevel - (default is 1). If LoggingLevel = 2, more detailed info is written into log file (and the file grows in size faster)
- LogFilePath - (default is "mmq_log.txt" in the current directory, which is usually "WINNT\SYSTEM32" for NT services, the actual path may differ depending on your system configuration). Path to file which will be used as log file. This file will be overwritten each time MailBee Message Queue service starts
Section [Timings]
- PollingInterval - (default = 1 sec). Specifies how often (in seconds) MailBee Message Queue checks for new files in queue folder
- SendsPerSecond - (default = 10).
  Zero value means "send messages at maximum possible speed".
  Nonzero value specifies the number of messages to be sent during an interval of one second (i.e. if SendPerSecond = 5, five messages will be sent each second). This option allows to limit message-sending rate for those SMTP servers which reject massive sending requests considering them to be hacker attack.
  If SMTP server you are using is capable of processing unlimited number of requests, you may set this value to 0
- SendsPerSession - (default = 20).
  Zero value means "send all available messages within one SMTP session".
  Nonzero value specifies maximum number of messages which can be sent during one connection to the SMTP server. Use this option if your SMTP server limits maximum number of sends per connection.
- Timeout - (default = 30 sec). How long (in seconds) to wait for response from SMTP server before raising an error. You might consider decrease this time for local SMTP server (located on the same machine or within local network where MailBee Message Queue service is running) because local systems should respond much faster and even 5-second delay usually designates an error of some kind
- MaxThreadCount - (default = 1, max = 64). Specifies the maximum number of threads to be used to send the mail messages to SMTP server. Setting this parameter to a higher value may increase the speed of sending messages to SMTP server.
Section [SMTP]
- ServerName - (default - "localhost"). Host name of SMTP server, like "mail.server.com"
- DomainName - (default - "null"). If assigned to any value different from "null", this name will be used as argument to SMTP HELO or EHLO command. Otherwise, host name of the machine running MailBee Message Queue will be used. Usually you can leave default value for this parameter
- PortNumber - (default=25). Most SMTP servers operate on port 25
- UserName - (no default value). if AuthMethod property is not 0, UserName and Password should be specified
- Password - (no default value). if AuthMethod property is not 0, UserName and Password should be specified
- AuthMethod - (default = 0). Specifies authentication method to be used during SMTP authentication. "0" means "no authentication". Other values require UserName and Password properties set. The following options are available for AuthMethod property:
  - 0 - No Authentication (UserName/Password not required)
  - 1 - PLAIN;
  - 2 - LOGIN;
  - 3 - CRAM_MD5;
  - 4 - NTLM;
  - 5 - MSN.
  CRAM_MD5, NTLM, MSN authentication types provide higher level of security because user password is encrypted before transmitting to SMTP server
Section [Problems]
- KillUnsentMessages - (default is "No"). If the message was not sent because SMTP server rejected it for some reason (recipient or sender is not valid, message is too big and so on), MailBee Message Queue can either delete it (kill) or rename it to the file with ".bad" (MailBee Unsent) extension. By default (KillUnsentMessages = "No") unsent messages are renamed.
  Note: you can rename these files back to ".eml" to force MailBee Message Queue to resend them. This makes sense if SMTP server configuration has changed since sending failure, so unsent message now fits in delivery constraints of this SMTP server