如何做系列(5)-james mail安装总结

安装james还是比较复杂的，我们在EC2上花费了差不多一天，发现不能发送邮件到外网，后续又陆续花了几天的时间，才成功搭建james邮件服务器。

现在愿意把我们的经历分享出来，让大家参考一下。

　由于项目需要部署在Linux上，而又使用到Apache James作邮件服务器，因此总结了一下在Linux上部署Apache James的步骤，写得比较凌乱。

在Linux上部署Apache James

前提工作：

1）由于Apache James邮件服务需要用到1024以下的端口，因此请用root用户登录进行部署。

2）需要先安装JDK1.5或以上版本，部署前请确保您的JDK环境变量如JAVA_HOME等已经设置好。

3）James 启动时，其SMTP 服务默认在 25 端口启动，POP3 服务默认在 110 端口启动， NNTP 服务默认在 119 端口启动, 请确保这些端口未被占用。Linux下查过这些端口是否被占用的命令是：lsof -i:端口号，例如：

[root@nhslj-app ~]# lsof -i:25

COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME

sendmail 3268 root 4u IPv4 8650 TCP nhslj-app:smtp (LISTEN)

这表示25端口正在被sendmail服务占用。

关闭SendMail服务：

一般RedHat的系统安装时都会默认安装了sendmail邮件服务，因此在部署Apache James时，需要把sendmail关闭。可以通过以下方法来关闭sendmail，以防止系统重启时又自动启动sendmail服务。

1）用chkconfig --list sendmail命令查看sendmail的情况：

[root@susun177 ~]# chkconfig --list sendmail

sendmail 0:关闭 1:关闭 2:启用 3:关闭 4:启用 5:启用 6:关闭

2）通过chkconfig sendmail off命令来关闭sendmail的启动：

[root@susun177 ~]# chkconfig sendmail off

3）这时再用chkconfig --list sendmail命令可以查看到sendmail的所有启动级别都已经关闭了：

[root@susun177 ~]# chkconfig --list sendmail

sendmail 0:关闭 1:关闭 2:关闭 3:关闭 4:关闭 5:关闭 6:关闭

这样，即使重新启动Linux系统，sendmail服务也不会自动启动了。

前期工作做完了，接下来就是部署Apache James了。

使用的james版本是james-binary-2.3.2.1

1）解压Apache James包（apache-james-2.3.2.tar.gz）：

[root@susun177 local]# tar zxvf apache-james-2.3.2.tar.gz

解压后，会多了一个目录james-2.3.2

2）进入james-2.3.2/bin目录，运行run.sh，生成james的配置文件config.xml：

[root@susun177 bin]# sh run.sh

run.sh: line 37: /usr/local/james-2.3.2/bin/phoenix.sh: 权限不够

权限不够（估计是解压后run.sh文件没有赋予执行权限），可以执行以下命令：

[root@susun177 bin]# chmod +x run.sh phoenix.sh

然后再次运行run.sh命令：

[root@susun177 bin]# sh run.sh

Using PHOENIX_HOME: /usr/local/james-2.3.2

Using PHOENIX_TMPDIR: /usr/local/james-2.3.2/temp

Using JAVA_HOME: /usr/java/jdk1.5.0

Running Phoenix:

Phoenix 4.2

James Mail Server 2.3.2

Remote Manager Service started plain:4555

POP3 Service started plain:110

SMTP Service started plain:25

NNTP Service started plain:119

FetchMail Disabled

说明James启动成功。

3）按Ctrl + C退出James，编辑config.xml文件。生成的config.xml放置在../james-2.3.2/apps/james/SAR- INF目录下。关于James的config.xml的修改，网上很多资料，请自行查阅。在这里，只写关键的修改：

A）找到<servernames autodetect="true" autodetectIP="true"> 设成

autodetect="false" autodetectIP="false"

autodetct设为true会自动侦测你的主机名,设成false会用你指定的server name。

autodetectIP设为true会为你的servername加上ip。

B）设置servername 将默认的为localhost改成你的server名字如king.cn：

然后修改Linux的hosts主机设置文件：

[root@susun177 SAR-INF]# vi /etc/hosts

在打开的文件添加一行，然后保存：

192.168.1.177 king.cn king

注意：第一个为IP地址第二个为主机域名第三个为主机名称

提示：名字后面应该要加上.com或者.cn这样163等邮件服务器才不会拒绝的。

C）注释掉

<processor> relay-denied </processor>

<notice>550 - Requested action not taken: relaying denied</notice>

</mailet>

D）配置DNS Server，先通过netstat命令查看dns配置

注意，此处坑，EC2需要在服务器设置中开通相应的端口，DNS也是有端口的。使用谷歌的公共DNS比较保险 8.8.8.8或者 8.8.4.4

[root@susun177 SAR-INF]# netstat -rn

Kernel IP routing table

Destination Gateway Genmask Flags MSS Window irtt Iface

192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0

169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0

找到<dnsserver>，在<servers>里最前面添加一行： <server>192.168.1.0</server> ，同时设置autodiscover为false。

<!--

-->

</servers>

<autodiscover>false</autodiscover>

<authoritative>false</authoritative>

</dnsserver>

E）修改James数据库连接字符串：

注意，此处我们选择我把数据保存在数据库里面，后面我使用数据库做了一套邮件系统管理系统

<data-source name="maildb" class="org.apache.james.util.dbcp.JdbcDataSource">

<driver>oracle.jdbc.driver.OracleDriver</driver>

<dburl>jdbc:oracle:thin:@192.168.1.17:1521:hello</dburl>

<user>hello</user>

<password>kitty</password>

<keep-alive>select 1 from dual</keep-alive>

</data-source>

以上用的是oracle数据库，如果是其他数据库，则需要修改为对应的数据库连接驱动，以及数据库用户信息。

注意：一定要记得配置<keep-alive>，该参数的意思是，在使用连接池的连接之前，是否需要验证该连接是否有效。之前，我没有设置该参数，结果总是出现收不到邮件的问题。

4）优化一下James内存，在../james-2.3.2/bi/phoenix.sh加入：

# Set Heap Size 2007-0818,fix OutOfMemory bug while transporting big mail

PHOENIX_JVM_OPTS="$PHOENIX_JVM_OPTS -Xms128M -Xmx512M -XX:PermSize=64M -XX:MaxPermSize=128M"

修改../james-2.3.2/conf/wrapper.conf的jvm配置，设置初始内存128M,最大内存512M

# Initial Java Heap Size (in MB)

#wrapper.java.initmemory=16

wrapper.java.initmemory=128

# Maximum Java Heap Size (in MB)

#wrapper.java.maxmemory=64

wrapper.java.maxmemory=512

5）复制数据库驱动到../james-2.3.2/lib目录下，我用的是oracle数据库，驱动包为：ojdbc14.jar

6）重启Apache James服务。

7）最后，进入邮件系统全局管理，将系统的域名改为上述的server name。

8）如无意外一切OK。

我们执行lsof命令

root@ip-172-31-34-34:/var/lib/tomcat7/webapps# lsof -i :110

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME

java 30161 root 111u IPv6 134610 0t0 TCP *:pop3 (LISTEN)

root@ip-172-31-34-34:/var/lib/tomcat7/webapps# lsof -i :119

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME

java 30161 root 112u IPv6 134612 0t0 TCP *:nntp (LISTEN)

root@ip-172-31-34-34:/var/lib/tomcat7/webapps# lsof -i :25

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME

java 30161 root 109u IPv6 134611 0t0 TCP *:smtp (LISTEN)

三个端口都已经有java在监听，说明我们的邮件是可以运行了。

配置完了之后，发现内网发送邮件可以，外网就不行，经过配置之后又可以了，也不知道哪里的问题，可能是DNS的问题，导致服务器寻址不到，报550错误，在最后我给出了完整的配置。

数据库数据表：表都是james自动生成的

inbox表字段：

用户表：

用户列表

邮件列表

增加邮箱用户

下面我给出配置全文：根据这个配置一定可以发送邮件到外网

<?xml version="1.0"?>

<!DOCTYPE config [

<!ENTITY listserverConfig SYSTEM "../conf/james-listmanager.xml">

<!ENTITY listserverStores SYSTEM "../conf/james-liststores.xml">

<!ENTITY fetchmailConfig SYSTEM "../conf/james-fetchmail.xml">

<!ENTITY smtphandlerchainConfig SYSTEM "../conf/james-smtphandlerchain.xml">

<!--

Licensed to the Apache Software Foundation (ASF) under one

or more contributor license agreements. See the NOTICE file

distributed with this work for additional information

regarding copyright ownership. The ASF licenses this file

to you under the Apache License, Version 2.0 (the

"License"); you may not use this file except in compliance

with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,

software distributed under the License is distributed on an

"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY

KIND, either express or implied. See the License for the

specific language governing permissions and limitations

under the License.

-->

<James>

<postmaster>Postmaster@yourdomain.com</postmaster>

<servername>yourdomain.com</servername>

</servernames>

<!-- <inboxRepository>

</inboxRepository>

-->

</inboxRepository>

<!--

</inboxRepository>

-->

<!--

</inboxRepository>

-->

</James>

&fetchmailConfig;

<mailetpackage>org.apache.james.transport.mailets</mailetpackage>

<mailetpackage>org.apache.james.transport.mailets.smime</mailetpackage>

</mailetpackages>

<matcherpackage>org.apache.james.transport.matchers</matcherpackage>

<matcherpackage>org.apache.james.transport.matchers.smime</matcherpackage>

</matcherpackages>

<!--

</mailet>

-->

<!--

</mailet>

-->

<processor> virus </processor>

</mailet>

<!--

<inline>heads</inline>

<passThrough>false</passThrough>

<prefix>[REJECTED]</prefix>

The Security Policy of XXX does not allow to forward messages containing attachments having any of the extensions .exe, .com, .bat, .cmd, .pif, .scr, .vbs, .avi, .mp3, .mpeg, .shs, therefore your message has been rejected.

Please don't reply to this e-mail as it has been automatically sent by the antivirus system.

Regards, Postmaster XXX.YYY

.....................................

</notice>

</mailet>

-->

<!--

<repositoryPath>db://maildb</repositoryPath>

<whitelistManagerAddress>whitelist.manager@xxx.yyy</whitelistManagerAddress>

<displayFlag>display</displayFlag>

<insertFlag>insert</insertFlag>

<removeFlag>remove</removeFlag>

</mailet>

-->

<!--

<repositoryPath> db://maildb </repositoryPath>

</mailet>

-->

<!--

<repositoryPath> db://maildb </repositoryPath>

</mailet>

-->

<!--

<keyStorePassword>myKeyStorePass</keyStorePassword>

<keyAlias>myKeyAlias</keyAlias>

<keyAliasPassword>myKeyPass</keyAliasPassword>

</mailet>

<keyStorePassword>myKeyStorePass</keyStorePassword>

<strip>false</strip>

</mailet>

-->

<!--

<!- 1:1 mapping ->

<mapping>morgoth@middle-earth=sauron@mordor</mapping>

<!- 1:n mapping ->

<mapping>istari@middle-earth=saruman@isengard;radigast;gandalf</mapping>

<!- DSN mapping ->

<mapping>boromir@osgilliath=error:550 Requested action not taken: no such user here</mapping>

<!- regex based mapping ->

<mapping>*@osgilliath=regex:(.*)@osgilliath:${1}@minas-tirith</mapping>

<!- both standard and regex mapping ->

<mapping>ring@*=onering@mordor;regex:ring@(.*):ring@${1}</mapping>

<!- conditional regex mapping example ->

<mapping>*@listserver=regex:(.*)-on@listserver:${1}-subscribe@listserver;

regex:(.*)-off@listserver:${1}-unsubscribe@listserver

</mapping>

</mailet>

-->

<processor> transport </processor>

</mailet>

</mailet>

<!-- White List:

If you use block lists, you will probably want to check

for known permitted senders. This is particularly true

if you use more aggressive block lists, such as SPEWS,

that are prone to block entire subnets without regard

for non-spamming senders.

-->

<processor> transport </processor>

</mailet>

<!--

<processor> transport </processor>

</mailet>

-->

<!--

<mailet match="SenderIs=goodboy@goodhost"

class="ToProcessor">

<processor> transport </processor>

</mailet>

-->

<mailet match="InSpammerBlacklist=query.bondedsender.org."

class="ToProcessor">

<processor> transport </processor>

</mailet>

<!--

<processor> transport </processor>

</mailet>

-->

<!--

<processor> transport </processor>

</mailet>

-->

<mailet match="InSpammerBlacklist=dnsbl.njabl.org."

class="ToProcessor">

<notice>550 Requested action not taken: rejected - see http://njabl.org/ </notice>

</mailet>

<!--

-->

<!--

<repositoryPath>db://maildb</repositoryPath>

<headerName>X-MessageIsSpamProbability</headerName>

</mailet>

<mailet match="CompareNumericHeaderValue=X-MessageIsSpamProbability > 0.90" class="SetMailAttribute" onMatchException="noMatch">

</mailet>

<mailet match="CompareNumericHeaderValue=X-MessageIsSpamProbability > 0.90" class="SetMimeHeader" onMatchException="noMatch">

<name>X-MessageIsSpam</name>

</mailet>

<mailet match="CompareNumericHeaderValue=X-MessageIsSpamProbability > 0.99" class="ToProcessor" onMatchException="noMatch">

<notice>Spam not accepted</notice>

</mailet>

-->

<processor> transport </processor>

</mailet>

</processor>

<!--

-->

<!--

-->

<repositoryPath> file://var/mail/error/</repositoryPath>

<!--

<repositoryPath> db://maildb/deadletter/error </repositoryPath>

-->

</mailet>

</processor>

<!--

&listserverConfig;

-->

<name>X-UserIsAuth</name>

</mailet>

<name>X-WasSigned</name>

</mailet>

<!--

<keyStoreFileName>path.keystore</keyStoreFileName>

<keyStorePassword>myKeyStorePass</keyStorePassword>

<keyAlias>myKeyAlias</keyAlias>

<keyAliasPassword>myKeyPass</keyAliasPassword>

<signerName>XXX Trusted Server</signerName>

</mailet>

-->

<!--

<sender>postmaster</sender>

<replyTo>postmaster</replyTo>

<attachment>message</attachment>

<prefix>[OVER QUOTA WARNING]</prefix>

When receiving the attached message, your mailbox is larger than 20 MB, which is the maximum allowed quota. The mailbox will not be blocked, but we ask you to empty it ASAP.

It is likely that you have set, in your mail client account, the option "leave a copy of messages on server". For any help ask your administrators.

Regards, Postmaster XXX.YYY

.....................................

</message>

</mailet>

-->

<processor> local-address-error </processor>

<notice>550 - Requested action not taken: no such user here</notice>

</mailet>

<!-- <mailet match="RemoteAddrNotInNetwork=127.0.0.1" class="ToProcessor">

<processor> relay-denied </processor>

<notice>550 - Requested action not taken: relaying denied</notice>

</mailet>

-->

<outgoing> db://maildb/spool/outgoing </outgoing>

<!-- 5 day retry period, with 4 attempts in the first

hour, two more within the first 6 hours, and then

every 6 hours for the rest of the period. -->

<delayTime> 5 minutes </delayTime>

<delayTime> 10 minutes </delayTime>

<delayTime> 45 minutes </delayTime>

<delayTime> 2 hours </delayTime>

<delayTime> 3 hours </delayTime>

<delayTime> 6 hours </delayTime>

<sendpartial>false</sendpartial>

<bounceProcessor>bounces</bounceProcessor>

<!--

<gateway> smtp.gmail.com </gateway>

-->

<!--

<gatewayusername>login</gatewayusername>

-->

<mail.smtp.localhost>yourdomain.com</mail.smtp.localhost>

</mailet>

</processor>

<!--

-->

<!--

-->

<!--

-->

<repositoryPath> db://maildb/deadletter/spam </repositoryPath>

</mailet>

</processor>

<org.apache.james.infected>true, bouncing</org.apache.james.infected>

</mailet>

<inline>heads</inline>

<notice> Warning: We were unable to deliver the message below because it was found infected by virus(es). </notice>

</mailet>

</processor>

<!--

-->

<!--

</mailet>

-->

<!--

-->

<repositoryPath> db://maildb/deadletter/address-error </repositoryPath>

</mailet>

</processor>

<!-- As of James v2.2, this processor can be deprecated by using the <authorizedAddresses> tag

in the SMTP Server, and rejecting the message in the protocol transaction. -->

<!--

</mailet>

-->

<!--

-->

<repositoryPath> db://maildb/deadletter/relay-denied </repositoryPath>

</mailet>

</processor>

<passThrough>false</passThrough>

<!--

<prefix>[bounce]</prefix>

-->

<!--

<attachment>heads</attachment>

-->

<!--

<messageString>Here is [machine]. I'm not able to deliver this message.</messageString>

-->

</mailet>

</processor>

</spoolmanager>

</servers>

<autodiscover>false</autodiscover>

<authoritative>false</authoritative>

</dnsserver>

<!--

-->

<!--

-->

<helloName autodetect="false">yourdomain.com</helloName>

<administrator_accounts>

</administrator_accounts>

<!--

<prompt>james></prompt>

-->

</handler>

</remotemanager>

<!--

-->

<!--

-->

<helloName autodetect="false">yourdomain.com</helloName>

</handler>

</pop3server>

<!-- port 25 is the well-known/IANA registered port for SMTP

<!--

-->

<helloName autodetect="false">yourdomain.com</helloName>

<!-- Uncomment this if you want to require SMTP authentication.

supported values:

true: required but announced only to not authorizedAddresses

false: don't use AUTH

announce: like true, but always announce AUTH capability to clients

The correct behaviour per RFC value would be false or announce

but we still support true for backward compatibility and because

some webmail client fails when AUTH is announced but no authentication

information has been provided

-->

<!-- Uncomment this if you want to authorize specific addresses/networks.

If you use SMTP AUTH, addresses that match those specified here will

be permitted to relay without SMTP AUTH. If you do not use SMTP

AUTH, and you specify addreses here, then only addresses that match

those specified will be permitted to relay.

Addresses may be specified as a an IP address or domain name, with an

optional netmask, e.g.,

127.*, 127.0.0.0/8, 127.0.0.0/255.0.0.0, and localhost/8 are all the same

See also the RemoteAddrNotInNetwork matcher in the transport processor.

You would generally use one OR the other approach.

-->

<!--

-->

<!--

&smtphandlerchainConfig;

-->

</handler>

</smtpserver>

<!-- NNTP-specific: if you disable the NNTP Server, you should also set the nntp-repository's

threadCount to 0, otherwise there will be threads active and polling -->

<!-- THE NNTP PROTOCOL IS EXPERIMENTAL AND NOT AS WELL TESTED AS SMTP AND POP3 IN THIS RELEASE.

The James project recommends that you check the James web site for updates to the NNTP

service. -->

<!--

-->

<!--

-->

<helloName autodetect="false">yourdomain.com</helloName>

<authRequired>false</authRequired>

</handler>

</nntpserver>

<nntp-repository>

<readOnly>false</readOnly>

<rootPath>file://var/nntp/groups</rootPath>

<articleIDPath>file://var/nntp/articleid</articleIDPath>

<articleIDDomainSuffix>news.james.apache.org</articleIDDomainSuffix>

<!-- Groups here will be added to those found in the file system,

but removing groups from here will NOT remove them from the

server. Change <newsgroups> to <newsgroups only="true"> to

restrict newsgroups to ONLY those found in this list. -->

<newsgroup>org.apache.james.dev</newsgroup>

<newsgroup>org.apache.james.user</newsgroup>

<newsgroup>org.apache.avalon.dev</newsgroup>

<newsgroup>org.apache.avalon.user</newsgroup>

</newsgroups>

<spool>

<spoolPath>file://var/nntp/spool</spoolPath>

</configuration>

</spool>

</nntp-repository>

<!-- before being processed.

-->

<!--

-->

</protocols>

<types>

</types>

</repository>

</protocols>

<types>

<type>SPOOL</type>

</types>

</repository>

</protocols>

<types>

</types>

<sqlFile>file://conf/sqlResources.xml</sqlFile>

<!--

-->

</config>

</repository>

</protocols>

<types>

<type>SPOOL</type>

</types>

<sqlFile>file://conf/sqlResources.xml</sqlFile>

<!--

-->

</config>

</repository>

<protocol>dbfile</protocol>

</protocols>

<types>

</types>

<sqlFile>file://conf/sqlResources.xml</sqlFile>

<filestore>file://var/dbmail</filestore>

</config>

</repository>

<protocol>dbfile</protocol>

</protocols>

<types>

<type>SPOOL</type>

</types>

<sqlFile>file://conf/sqlResources.xml</sqlFile>

<filestore>file://var/dbmail</filestore>

</config>

</repository>

</protocols>

<types>

</types>

</repository>

</protocols>

<types>

<type>OBJECT</type>

</types>

<model>SYNCHRONOUS</model>

<model>ASYNCHRONOUS</model>

<model>CACHE</model>

</models>

</repository>

</protocols>

<types>

<type>STREAM</type>

</types>

<model>SYNCHRONOUS</model>

<model>ASYNCHRONOUS</model>

<model>CACHE</model>

</models>

</repository>

</repositories>

</mailstore>

<users-store>

<!--

</repository>

-->

<sqlFile>file://conf/sqlResources.xml</sqlFile>

</repository>

<!--

&listserverStores;

-->

</users-store>

<database-connections>

<!--

James has previously used an in-house connection pool, Mordred.

Mordred is being deprecated in favor of Jakarta Commons DBCP.

To use DBCP: org.apache.james.util.dbcp.JdbcDataSource

To use Mordred: org.apache.james.util.mordred.JdbcDataSource

Change it back, of course, to use Mordred.

NOTE: DBCP is configured to recover from a database server outage.

This, alone, may be reason for you to give it a try.

-->

<!--

<data-source name="maildb" class="org.apache.james.util.dbcp.JdbcDataSource">

<driver>org.apache.derby.jdbc.EmbeddedDriver</driver>

<dburl>jdbc:derby:../apps/james/var/derbydb;create=true</dburl>

</data-source>

-->

<data-source name="maildb" class="org.apache.james.util.dbcp.JdbcDataSource">

<driver>com.mysql.jdbc.Driver</driver>

<dburl>jdbc:mysql://127.0.0.1/mail?autoReconnect=true</dburl>

<user>yourdomain</user>

<password>yourdomain</password>

</data-source>

<!--

<data-source name="maildb" class="org.apache.james.util.dbcp.JdbcDataSource">

<driver>com.inet.tds.TdsDriver</driver>

<dburl>jdbc:inetdae7:127.0.0.1?database=James</dburl>

<user>sa_james</user>

<password>blahblah</password>

</data-source>

-->

<!--

<data-source name="maildb" class="org.apache.james.util.dbcp.JdbcDataSource">

<driver>org.hsqldb.jdbcDriver</driver>

<dburl>jdbc:hsqldb:target/data/hsqldb</dburl>

</data-source>

-->

</database-connections>

<idle-timeout>300000</idle-timeout>

<max-connections>30</max-connections>

</connections>

<server-sockets>

<ssl-factory>

<file>conf/keystore</file>

<password>yourdomain</password>

<key-password>yourdomain</key-password>

<authenticate-client>false</authenticate-client>

</keystore>

</ssl-factory>

</factory>

</server-sockets>

<client-sockets>

</client-sockets>

</sockets>

<thread-manager>

<thread-group>

<name>default</name>

<is-daemon>false</is-daemon>

<max-threads>100</max-threads>

<min-threads>20</min-threads>

<min-spare-threads>20</min-spare-threads>

</thread-group>

</thread-manager>

</config>

如何做系列(5)-james mail安装总结相关推荐

Git学习系列之Windows上安装Git之后的一些配置（图文详解）
不多说,直接上干货! 前面博客 Git学习系列之Windows上安装Git详细步骤(图文详解) 第一次使用Git时,需要对Git进行一些配置,以方便使用Git. 不过,这种配置工作只需要进行一次便可, ...
《⑨也懂系列：GNU Emacs安装教程Ver.2》世界著名的顶级全能文本编辑器
备注:我的全部文章首发在自己的独立博客(http://rsreland.net)上,编程相关文章会同步到这里,不过文章的维护是优先那边.然后本篇文章的地址是:http://rsreland.net/a ...
Redis6 系列一简介与安装
Redis6 系列一简介与安装穆成祥千缘科技 1. NoSQL数据库简介 1.1. 技术发展技术的分类 1.解决功能性的问题:Java.Jsp.RDBMS.Tomcat.HTML. ...
ScienceImage科思图科技发布NDI Studio 4K系列最新固件下载及安装--4K Full NDI双向编解码器
ScienceImage科思图科技发布NDI Studio 4K系列最新固件下载及安装–4K Full NDI双向编解码器系列 ScienceImage科思图所有NDI设备均支持NDI 5功能 Sci ...
CA ARCserve Backup系列（3）—安装代理（Linux篇）
step1.将安装光盘挂载 mount /dev/cdrom /mnt/ step2.执行安装cd /mnt/DataMoverandAgent/Linux ./install ########### ...
openresty开发系列2--nginx的简单安装，正向、反向代理及常用命令和信号控制介绍...
openresty开发系列2--nginx的简单安装,正向.反向代理及常用命令和信号控制介绍一.nginx的安装下载及编译安装 1.Nginx下载:nginx-1.13.0.tar.gz,下载到:/ ...
乐鑫代理-启明云端分享ESP32系列教程之一：安装虚拟机及Ubuntu
安装虚拟机软件 1.1下载VMWare Workstation (推荐使用VMWare Workstation 14 Pro,14.1及以上版本) 将下方网址复制至浏览器打开: 下载 VMware W ...
SonarQube系列一、Linux安装与部署
来源:https://www.cnblogs.com/7tiny/p/11269774.html [前言] 随着项目团队规模日益壮大,项目代码量也越来越多.且不说团队成员编码水平层次不齐,即便是老手, ...
hadoop安装hive及配置mysql_Hadoop系列之Hive(数据仓库)安装配置
Hadoop系列之Hive(数据仓库)安装配置 1.在NameNode安装 cd /root/soft tar zxvf apache-hive-0.13.1-bin.tar.gz mv apache ...

如何做系列(5)-james mail安装总结

如何做系列(5)-james mail安装总结相关推荐

最新文章

热门文章