For your site I doubt performance will really be an issue no matter what
you do. My setup is a little more complex, so I've simplified somewhat.
I'm not checking the messageid against the sender/recipient right now to
make sure those two match up, i'm just checking the messageid's straight.
Also
Yes it is possible and better about performance ! I have a few users
2-3 max and all on the same local network. I'm very interesting in
your proposition. So you make an association in the database between
the message id and the local user mailbox, is this right ?
You use qpsmtpd as the outg
Thanks for your response,
So I should develop a script that read headers and then deliver to the
correct mailbox. Then I should place a line like :
email-address : "| script-to-deliver-to-the-correct-mailbox.sh"
in /etc/aliases ? Should I add some header when I deliver to a
maildir ? Can
If you force your users to send outgoing mail via your mailserver (via
policy/SPF/etc), you can store it in a database on its way out, and then
query the database as you're receiving email. I've been playing around
with this on my system so that these responses get whitelisted and don't
invoke
On Tue, 6 May 2008, John Peacock wrote:
[EMAIL PROTECTED] wrote:
I have multiple maildir mailbox, I want to deliver new mail in the mailbox
containing the previous message (reply, thread, ...).
I strongly recommend against implementing this in a qpsmtpd delivery plugin.
Normally, you want
[EMAIL PROTECTED] wrote:
I have multiple maildir mailbox, I want to deliver new mail in the
mailbox containing the previous message (reply, thread, ...).
I strongly recommend against implementing this in a qpsmtpd delivery
plugin. Normally, you want delivery to do as little work as possible s
