Ok, I got it now, surprise.
What went wrong: It worked the first time.
What's wrong with this: It shouldn't had happend and failed the first time.
Why: Cause the mailet Redirect causes a new mail to be spooled.
How I got this: The doc of Redirect mentions another mailet: Resend. The
doc of
I don't get it. I've tested as much as I could - and now always get this
error. Seems I got somewhat different last time it worked as I can't get
it to work at all now. So I guess it's really into how the name gets
generated - time to dig deep into code.
Matt
Am 28.05.2019 um 17:43 schrieb
Hey Garry,
I appreciate your effort. I don't think any of your questions are
stupid, in fact, as you said: let's go on systematically.
About the NICs: the VM emulates a Intel PRO/1000 MT Desktop (82540EM).
The physical host the VM runs on has a Intel(R) 82583V Gigabit Network
Connection,
Hey Matt
Sorry I missed some of the earlier emails in the chain. However, we can look at
your VM versus real machine systematically. The obvious first difference is the
way the network cards are described and/or used. For example, on my antsle VMs,
they share through the host on the 10.1.1
Hey there,
I ran another test on another real machine instead of a VM - and
surprisingly I encountered the same issue. So it seems somethings
different on a real machine than on a vm causing this issue. Anyone
knows how the "name" of a mail is composed in the first place and how it
could be
Hey Garry,
please use webarchive or server-user-thread. to download the whole
thread - I already explained the reason why I "somewhat have to" set it
up this way.
Long story short: unix uses local mail as to report output of background
/ service processes. It's up the process how this is
Why are you trying to redirect the mail from ‘webmas...@mydomain.com’ to
‘a.randome.u...@mydomain.com’ anyhow? Isn’tthere an alias set up? I was just
configuring postfix on another machine, not my james server, and I noted a
virtualiases configuration for that purpose. I am recalling an aliases
Well, seems it doesn't work in the real world.
The way I mentioned worked in a VM so far - but after I upgraded my
root-server and did the same I know get this issue:
INFO | jvm 1 | 2019/05/26 20:58:02 | INFO 20:58:02,242 |
org.apache.james.protocols.netty.BasicChannelUpstreamHandler |
Hey there, Matt here again.
Long time since my last update on this topic, but now I got a pretty
easy solution.
On May 22nd OpenSUSE 15.1 was released, and with this new update I again
looked at my "problem" about how to deal with apache and other local
mail. Instead of my initial thoughts
Hey there,
I don't know if my last reply was sent, but I couldn't find it by checking
web-archive. So apologies if this is a double-post.
About the matchers mentioned by Benoit:
I already begun to implement a RemoteAddrMatcher myself as I couldn't find any
while digging through the source,
Hi,
Have a look to:
- SenderIsLocal (based on the mail address of the sender)
- SenderHostIs + SenderHostIsLocal (based on the domain of the sender)
- You can already do some matching on the IP of the sender using
RemoteAddrInNetwork. Assuming you have well defined IPs, that you can
configure
Hey there, Matt here.
So, I wrote a test matcher to see what the different methods return. I
got three results:
- mail from localhost for localuser
- mail from localhost for external target
- mail from external source for localuser
I user InetAddress.getByName and as I set up sendmail as
So I dug through some code and found some points where I might could get
started:
The interface org.apache.mailet.Mail offeres the methods one might could
write a matcher and a mailet on:
String org.apache.mailet.Mail.getRemoteHost()
String org.apache.mailet.Mail.getRemoteAddr()
void
Hello Benoit,
thanks for your enormous effort you take into trying to help us with
such questions.
About the JIRA you filed, I guess that's what I looking for, as I
thought such SetRecipient(s) would already exist.
I came also up with a bit simpler description about my problem: I know
the
Don't worry, I already feel overwhelmed with a single application and
several collegues contributing on it with me!
Concerning the JPAMailRepository, thank you very much for your proposal!
I do believe it is really nice as it allows JPA users to no more rely on
file-system based storage API at
As soon as I have gotten our Direct Project implementation to work with James
3.x.0 (I am compilinga against the 3.2.0 release jars), I can look at working
the JPA MailRepository angle. Unfortunately, other production issues and
upgrade tasks have taken priority. You know how it is when you
Hi Garry,
To answer your previous email:
At Linagora we rely on "LDAP user repository".
Yes, we are currently limited to "a mailAddres" -> "a mailbox account".
Shared mailboxes is not supported so far. That being said
"RecipientRewrite tables" successfully enables concepts like "Alias",
"Mail
A couple of questions. First, what is your usersrepository? If you store user
info in the database, yes, you would have to store each user in there. If you
store it in LDAP, you could store each entry as an inetOrgPerson object, or a
subclass of that, with a mailbox entry for that person. Then
Hello Matt,
So as far as I understand your main need would be:
```
WHEN I send an email
THEN it is stored in *myMagicRecipient* INBOX
Regardless of original recipients
```
Quite surprisingly such a "Overwrite envelop" feature is missing...
Here is the JIRA:
Hello Benoit,
let me try to re-phrase my goal:
I've set up a clean install of opensuse 15.0 on my test-rig, named it
glados, assigned it to my domain cryptearth.de, set sendmail as
nullclient along with james 3.2.0 and want to collect any mail dropped
by sendmail into a specific mailbox. The
Hi Matt,
I read the all thread but feel quite confuse about what you try to achieve.
Could you describe it again? (`When ... Then ...` syntax can really help!)
Don't be using regex rewrites - I guess nobody understand what it does.
Maybe you are interested by domain rewrites? Or do you want
Hey there, Matt here again.
So, I think a found a possible solution without any source-file mods but
only clever mailet-config in mailetcontainer.xml.
As I dug through the source I found the standard mailets for
RecipientIsLocal. Then I found RecipientIsRegex (I might need some help
here).
So, as far as I dug through the code, it seems to come down to
MailetContext.isLocalEmail(MailAddress) wich is checked by
RecipientIsLocal (wich I guess also involve somehow a check of
isLocalServer(Domain). In transport-processor there is the line
I looked into LocalDelivery.java, but I
Currently I'm just using out-of-the-box after clean build. I'll have a look at
the mentioned class and the mailetcontainer. Maybe I'll find my way around.
Good James is written in Java - the one language I really know.
Thanks for the point in a possible direction. I'll report back when I got
24 matches
Mail list logo
