# "james" as smtp server
**URL:** https://community.ciphermail.com/t/james-as-smtp-server/43
**Category:** Gateway
**Created:** [November 4, 2009, 10:35am UTC](https://community.ciphermail.com/t/james-as-smtp-server/43 "2009-11-04T10:35:26Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@lst\_hoe021](https://community.ciphermail.com/u/lst_hoe021)
#### Post date: [November 4, 2009, 10:35am UTC](https://community.ciphermail.com/t/james-as-smtp-server/43/1 "2009-11-04T10:35:26Z")
Hello
for our goal to integrate Djigzo on an existing mailserver it would be
nice to have the integrated Java SMTP-Server "james" directly
accepting incoming mail by smtp on a special port. I'm aware that one
should \*not\* do this internet-facing (in fact i wouldn't trust
anything but Postfix to do so :-), but for our internal network it
should be ok.
What we need for this is a allow/deny by IP-Address rule and set the
input SMTP channel to a address other than 127.0.0.1.
Is this reasonable or is this not recommended at all?
Many Thanks
Andreas
---
### Author:  [@martijn](https://community.ciphermail.com/u/martijn)
#### Post date: [November 4, 2009, 10:53am UTC](https://community.ciphermail.com/t/james-as-smtp-server/43/2 "2009-11-04T10:53:13Z")
Yes that's possible. You must add the IP range if you want to relay to
external recipients to \ in config.xml:
example:
\ 127.0.0.0/8, 192.168.178.0/24 \
Note that Postfix is much better at mail queuing. The MPA queue blocks
incoming email when the queue exceeds 2000 items (can be changed in the
config). The MPA will start accepting email when the queue empties. If
you have large bursts of incoming email it's better to let Postfix do
the queuing.
Kind regards,
Martijn Brinkers
lst\_hoe02(a)kwsoft.de wrote:
> **ยทยทยท**
>
> > Hello
> >
> > for our goal to integrate Djigzo on an existing mailserver it would be
> > nice to have the integrated Java SMTP-Server "james" directly
> > accepting incoming mail by smtp on a special port. I'm aware that one
> > should \*not\* do this internet-facing (in fact i wouldn't trust
> > anything but Postfix to do so :-), but for our internal network it
> > should be ok.
> >
> > What we need for this is a allow/deny by IP-Address rule and set the
> > input SMTP channel to a address other than 127.0.0.1.
> >
> > Is this reasonable or is this not recommended at all?
> >
> > Many Thanks
> >
> > Andreas
> >
> > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
> > Users mailing list
> > Users(a)lists.djigzo.com
> > [http://lists.djigzo.com/lists/listinfo/users](http://lists.djigzo.com/lists/listinfo/users)
>
> --
> Djigzo open source email encryption
---
### Author:  [@lst\_hoe021](https://community.ciphermail.com/u/lst_hoe021)
#### Post date: [November 4, 2009, 4:28pm UTC](https://community.ciphermail.com/t/james-as-smtp-server/43/3 "2009-11-04T16:28:14Z")
Zitat von Martijn Brinkers \:
> Yes that's possible. You must add the IP range if you want to relay
> to external recipients to \ in config.xml:
>
> example:
>
> \ 127.0.0.0/8, 192.168.178.0/24 \
>
> Note that Postfix is much better at mail queuing. The MPA queue
> blocks incoming email when the queue exceeds 2000 items (can be
> changed in the config). The MPA will start accepting email when the
> queue empties. If you have large bursts of incoming email it's
> better to let Postfix do the queuing.
Okay, understand. I will also have a look for other adjustment like
concurrency and the like, but as said it is used only in the internal
network on a non standard port.
Regards
Andreas