Multiple outgoing gateways are possible.
the outgoing tag is the name of the queue that will hold messages being
processed by the RemoteDelivery Mailet (deployed doc is misleading). Use
distinct one per RemoteDelivery mailet.
If you don't want to enforce ssl/tls, don't use the startTls/sslEnable
tag. Btw, I suspect bad bugs there.
for filtering..., current matchers can help, but sieve is not
operational atm.
Take care if you don't use /%user/%domain and experiment...
What do you mean with "user+box@..." ?
On 27/10/13 01:24, Robin Bankhead wrote:
Hi Eric, thanks for the reply.
I should have been reading up on the mailets, than answer for that part
was right there:
http://james.apache.org/server/3/dev-provided-mailets.html#RemoteDelivery
So it appears I could take care of outgoing gateways like this:
<mailet match="SenderIsRegex=.*@outgoingdomain1.com"
class="RemoteDelivery">
<outgoing>?</outgoing>
<gateway>mail.outgoingdomain1.com:465</gateway>
<gatewayUsername>myname</gatewayUsername>
<gatewayPassword>secret</gatewayPassword>
<startTls>true</startTls>
<sslEnable>true></sslEnable>
</mailet>
We would have more than one outgoing sender-domain, so I could do one of
these for each (right?).
Not quite sure how the <outgoing> tag is supposed to be filled, but I
expect I will find it with more reading ;)
The <startTls> and <sslEnable> tags have the same description on that
page, are both needed?
If that's all in order, then it leaves the issue of local delivery --
and of filtering, if (as I now see is the case) sieve is out of action atm.
I did come up with a simple method of getting everything delivered into
the same maildir: simply declare a concrete path instead of
"[...]/%user/%domain" in mailbox-maildir.properties. However that
doesn't allow them to be delivered into a subdir, just INBOX for all.
Does James support the "user+box@..." style of next-hop addressing by
any chance? If so that might be usable in conjunction with recipient
rewriting.
Robin Bankhead
Quoting Eric Charles <e...@apache.org>:
Not sure if this can help?
http://james.apache.org/server/3/config-recipientrewritetable.html
http://james.apache.org/server/3/feature-mailetcontainer.html
On 12/10/13 02:17, Robin Bankhead wrote:
Hello,
I'm currently exploring James as a replacement for our old mail setup.
In the current setup (using Demon Turnpike client/server) you could
call it virtual hosting because we are fetching mail for a number of
virtual domains into a single mailbox and sending *from* all those
domains via our authed ISP SMTP gateway. There is one "primary" domain
that we use for most outgoing and all internal mail (among different
email-names on that domain).
To replicate this using James, I propose to continue having a single
IMAP mailbox with various domains and their users having their own
folderspaces within it (the reason being that mail is often moved around
among these entities within the store and nobody wants to be either
forwarding everything or logging in/out constantly).
It's the intricacies of the SMTP setup that I think will be
tricky/impossible. The questions:
1. If I define the local (virtual) domains/usernames in domainlist.xml
(and add them via the cli), can the SMTP server be made to route them
all into a single IMAP store? Which is the correct mechanism for this?
(I thought sieve, but that seems in a state of flux and I genuinely
can't tell whether there is a functional implementation of it right now
in the 3.0beta4 code.)
2. Does the SMTP server (or other component) have any way of also
functioning as a client; that is, could it, instead of just relaying
outgoing mail, submit it to an upstream SMTP gateway (i.e. the proper
one for the message's FROM domain), including performing auth to that
gateway?
3. Because of the multiple domains involved, can the upstream server be
chosen from a list based on the FROM address domain?
I'm also looking at implementing 2 and 3 on the client side, but that's
proving pretty tricky too and I'd hate myself for not enquiring if there
was a solution in the code I'm already working with ;)
I hope I explained myself reasonably. Thanks for your time reading, and
any advice.
Robin Bankhead
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
