Hello John,
On Sun, 12 Aug 2012 12:17:13 +1000, John Kenyon wrote:
I was thinking it should only restore for the domains that you have
set to receive email for i.e. mydomains
you are right. This makes sense. Update model/search/search.php from
the the master branch
(https://bitbucket.org/jsuto/piler/get/master.tar.gz),
and be sure to add all your domains on
http://piler.yoursite.com/index.php?route=domain/domain
The webui will enumerate the 'domain' list and tries to match the
recipient
address on the list.
For example, say there was multiple recipients and one was a
[email protected], the restore at the moment will send try to send a
copy to [email protected], but we are not archiving for Hotmail.com
how did you set up the mail forwarding to piler? Does
archive@yourdomain in the To: or Cc: field? And is the original
recipient different than the 'regular user' himself?
No the regular user, is the original recipient.
Mail forwarding to piler is performed using the qmail-tap patch for
qmail http://www.inter7.com/index.php?page=qmailtap
http://www.inter7.com/qmailtap/qmail-tap.diff
It looks ok. If you reinject the restore emails to the usual mail
stream then
piler will get them again. However before restoring, piler adds a
special
header that prevents the message to be archived again.
If you have a similar setup, then it's possible by editing SMARTHOST
and SMARTHOST_PORT
to forward emails to a path that skips piler.
+-----------+ +-------------+
---> | mx server | -----> | mail server |
+-----------+ | +-------------+
| ^
| |
| +-------------+
---> | piler |
+-------------+
OR if your mail server supports it, you can add a rule that archive
everything
except emails coming from a certain IP-address. Anyway piler has a
mechanism to
prevent archiving already archived emails.
Janos
