ict.ken.be

select domain,count (*)
from actionqueue_smtpinfo (nolock)
where actionqueueid in
(select id from actionqueue (nolock) where state<>30)
group by domain
order by 2 desc

State 27 of actionqueue refers to What does state 27 complaints.
These issues can be solved by adding a complaint box.

Adding these settings :

• POPSERVER_COMPLAINTS
• POPLOGIN_COMPLAINTS
• POPPWD_COMPLAINTS

• Go to the following page http://yourinstallation/optireport/login.aspx
• Enter your credentials
• Accept the installation of the ActiveX component
• Start one of the tools, this will download the necessary exe files locally

• Download the ocx file at the following location http://yourinstallation/optireport/optilaunch.ocx
• Save the file under C:
• Open a DOS prompt, make sure the root path is set to C:
• Type the following command: regsvr32 optilaunch.ocx
• Start the tools 

• Download the package at the following location http://yourinstallation/optireport/optilaunch.cab
• Unzip the cab file
• Put all .dll files in the following directory:

o   For 32 bit systems: C:\Windows\System32

o   For 64 bit systems: C:\Windows\SysWOW64

• Put the other two files in C:
• Open a DOS prompt, make sure the root path is set to C:
• Type the following command: regsvr32 optilaunch.ocx
• Start the tools

This list should be used as a guideline and is not reflecting the newest versions of Messagent.

• ACTIONQUEUE 

This table serves as the outqueue for the email channel. Every record contains the definition for one email to be send.

•   ACTIONQUEUE_SMTPINFO

This table contains additional information for every failed ACTIONQUEUE record.

•   ACTIONQUEUE_STATES

Lookup table containing the different actionqueue states

• ACTIONRESULT

Internally used by Mailagent

• API_EVENTLOG

Table with logging for Automation API events

• CAMPAIGN_MAILS

Express: Link between Campaign and Email

• CAMPAIGN_STATES

Deprecated, different campaign states

• CAMPAIGNS

Table containing all campaign definitions

• CAMPAIGNTRIGGERFLAGS

Table containing the triggers that can launch a ‘triggered’ campaign.

• CHANNELAGENTINSTANCES

Contains instances of channelagent that are currently running. Filled by the channelagent at startup, allows the user to select one of the specific instances

• CHANNELBATCH

Table that contains the different data batches, delivered to external channel.

• CHANNELCAMPAIGNS

Link between channel and campaigns

• CHANNELINQUEUE

Queue that stores incoming events on a Messagent channelAgent. Every record represents one incoming event.

• CHANNELMODPARAMS

Parameters required by custom channel modules. Custom modules automatically enter their parameters inside this table at registration.

• CHANNELMODS

Installed channel modules

• CHANNELOUTQUEUE

Queue that stores outgoing events, every record represent one outbound channel event.

• CHANNELPARAMS

Parameters defined by the user for a certain channel

• CHANNELS

Channel definitions

• COMMONXML

Deprecated, contained global xml information

• DATASPACES

Defintion of dataspaces.

• EXPORT_FILES

Overview of files generated by the export module

• EXPORT_IDS

Overview of id’s of records that are linked to a certain export file. Used for differential exports and for tracking.

• EXPORT_JOBLOGS

Deprecated

• EXPORT_JOBS

Deprecated

• EXPORT_LOGS

Deprecated

• EXPORTS

Defintion of Exports

• FIELDS

Table containing additional information about Fields in the lists (multiselect, options,..)

• FLAGS

Storage for all platform interactions.

• GATE_LOGS

Logging for external API Gate calls.

• GATES

Defintion of gates (API)

• INCIDENTS

Table tracking all online 1:1 that occurred, when a 1:1 operation fails within the platform this table will contain an incident record with all relevant information.

• LABELS

Table containing labels (text replacements used in emails)

• LANGUAGES

Lookup table containing all used languages

• LISTLINKS

Table describing the relation in between lists

• LISTS

Table describing all lists

• MAIL_ARTICLES

Table describing what articles are used in a certain email (Automation)

• MAILS

Table containing all emails / pages

• MAILTREE

Table containing the different tree structures

• MODULES

Table containing the current state of all backoffice modules. Every backoffice modules registeres at a configurable interval in this table.

• NAMESPACES

Lookup table used to categorize labels

• OP_EVENTS

Table tracking user actions within the Messagent tools.

• OP_GROUPS

Table containing all groups defined in the system

• OP_RIGHTS

Table containing the rights users have on the different assets

• OP_USERS

Table containing all (business) users

• OPTIONLISTS

Table containing all optionlists. An optionlist is a definition of key/values that can be used to translate fields values.

• OPTIONS

Table containing the key values pair for the optionlists when they are stored within the messagent database model.

• PROBES

Table containing custom sensors

• REPORTCACHE

Caching table contains aggregated reporting information per campaign. Generated and maintained by the reporting

• REPORTCACHEDEF

Caching table contains aggregated reporting information per campaign. Generated and maintained by the reporting

• SEGMENTIDIMPORTS

Overview of all imports that occurred on a static segment

• SEGMENTIDS

Overview of all ids that are linked to a static segment

• SEGMENTS

Defintion of both static as dynamic segments

• SETTINGS

Table containing system wide configuration options

• SHAREDVARS

Table containing values for Shared Variables, used in campaign flows.

• SURVEY_DEPLOYS

Table containing deployment of surveys.

• SURVEY_INCIDENTS

Table containing incidents created by 1:1 actions within surveys

• SURVEY_STYLES

Table containing styles that are used witin surveys

• SURVEYS

Table containing all survey definitions

• WEBFOLDERS

Table containing the definition of webfolders.

Je kan de conditie testuser=1 gebruiken in een segment.
Bij een test activatie krijgen enkel de users met "testuser=1" in het profiel de mail.

SYSTEM.TEST=1 wil zeggen dat flow in test staat (werk niet steeds correct vanuit een mailtje) 
SYSTEM.DEBUG=1 is waar voor de urls die uit previewvenster van campaigner komen
SYSTEM.MAILAGENT is de optiext-url url de settings

of

[(IF(SYSTEM.TESTMAIL=1,'*TESTMAIL*','')]

When using the SIM Designer on Windows 7 the page is blanco. This bug is related to a Microsoft DHTML control.

A patch can be found on :

DHTML Editing Control for Applications Redistributable Package (x86)