Minicom Advanced Systems CMG-DCM manual Incoming mail setup

Page 49

Operator's guide

Incoming mail setup

This page enables you to set up the DCM to retrieve e-mail from a POP3 or IMAP server on the network, either unencrypted or secured using TLS (transport-layer security.) If you do not need the DCM to be able to fetch mail, select None from the net.mail.in.type drop-down menu and ignore the remaining settings.

net.mail.in.password : The password needed to log in to the mail server.

net.mail.in.port : The number of the port to connect to on the mail server. This generally depends on the protocol used to retrieve mail:

•

•

For pop3 mail, this port will normally be 110, or 995 for secure POP3 over TLS.

For imap mail, this port will normally be 143, or 993 for secure IMAP over TLS.

net.mail.in.server : The hostname or IP address of the mail server.

net.mail.in.tls : Select yes to encrypt the incoming mail channel with TLS, no to leave communications unencrypted.

net.mail.in.type : Select pop-3or imap to use that protocol to retrieve mail from the server. If you do not need the DCM to be able to receive mail, select None.

net.mail.in.username : The username needed to log in to the mail server.

December 2005

49

Image 49

Contents CMG-DCM Table of Contents December Inside the DCM Introduction CMG-DCM Inside the DCM Network services Serial port servicesSee .4, Connecting to a local network for full details Power supply Installing the CMG-DCMOverview Connecting over a serial link Connecting to a single computer192.168.0.x Connecting over EthernetConnecting over USB Using an internal modemConnecting to a local network Gcfgdbset option-namenew-value Connecting to the Internet Wi-FiSetting up the CMG-DCM Connecting digitizers and external hardwareWeb setup Setting up digitizers Using Scream General notes UsageDCM as a data store Gnblocks port-number Page CMG-DCM DCM as a GCF data source Accessing the DCM command line through gcfout Sensor arrays DCM as a network data hub Communicating with digitizers Configuring digitizers Data storage and retrieval Using miniSEED format Real-time data transmission CD1.0 and CD1.1 Troubleshooting DCM installations Cannot connect to the DCMs Scream! server Cannot see the DCMs Web site over Http or HttpsCannot Gcfping the DCMs Scream! server DCM is not receiving any data streams Can Gcfping the DCMs Scream! server, but no data appearsDCM is receiving streams, but they do not contain any data Use the Serial port configuration → port name Web page, or143032 up 34 min, load average 1.24, 1.32 General Configuration optionsDisk CMG-DCM Serial port configuration CMG-DCM Page Ethernet port Network configurationStatic routes DNS setup Incoming mail setup Outgoing mail setup Remote access Administrators PPP Mgetty Scream Data transferAutoDRM Scream! ClientHttp client Http serverCD1.0 CD1.1 CD1.1 subframe configuration DSS Server configuration Seed Page CMG-DCM Data Viewer ActionsStream list Icon barDigitizer Setup General digitizer settings Digitizer output control CMG-DCM Trigger criteria CMG-DCM Tap # Rate Bandwidth Samples/s Auxiliary Mux channels Sensor mass control Partition, and format disk Disk toolsCheck disk filesystem Flush flashCamera Disk filesRecent Log Entries Summary Network configurationData Out Port, Serial Port A, Serial Port B DNS configurationTamper lines Flash StatusDisk Status Software Versions Inside the DCM File systems CMG-DCM Command line tools Configuration Digitizer console access Data flow MonitoringDigitizer status Tamper lines Over the Internet Updating the DCMFrom the hard disk Removing support packagesFirmware Libgconfigdb Appendix A.1 Modular DCM units Appendix a Connector pinoutsPort a and B Data OUT portNetwork connector USB connectorDM/AM module output Appendix A.2 Integrated DCM unitsAppendix B.1 Sensor response codes Appendix B Sensor and digitizer typesDigitizer Appendix B.2 Digitizer type codes