On 08/28/2014 02:26 PM, Eric Shubert wrote:
Thanks for this explanation Rick. Now knowing how this actually works, I
think I'll join you in being peeved about it. Not knowing any better, I
would have presumed that the user d-q files would have been processed
before the domain d-q files. Makes me
One thing to remember, and one of my pet peeves...
Out of all of the files in ~vpopmail/domains/example.com/ only one,
.qmail-default has anything to do with the vpopmail delivery process.
When qmail-local tries to deliver a message to the domain it looks at
all of the .qmail-* files in the
On 08/27/2014 11:24 PM, Rick Widmer wrote:
One thing to remember, and one of my pet peeves...
Out of all of the files in ~vpopmail/domains/example.com/ only one,
.qmail-default has anything to do with the vpopmail delivery process.
When qmail-local tries to deliver a message to the domain it
On 8/28/2014 7:26 AM, Eric Shubert wrote:
On 08/27/2014 11:24 PM, Rick Widmer wrote:
One thing to remember, and one of my pet peeves...
Out of all of the files in ~vpopmail/domains/example.com/ only one,
.qmail-default has anything to do with the vpopmail delivery process.
When qmail-local
Rick,
At issue was that qmail only processes the .qmail-alias files in the domain
directory. It then hands off to vdelivermail via the .qmail-default file in
the domain directory.
The vdelivermail program is what parses the user/.qmail file for delivery
instructions. While that file follows
On Aug 27, 2014, at 10:00 AM, Eric Shubert e...@shubes.net wrote:
On 08/25/2014 05:48 PM, Charles Sprickman wrote:
I block the spam before it enters the system using simscan.
Thanks - not an option here since I need to allow users to opt in or out,
etc.
The simcontrol file allows you to
Charles,
It's been a long time since I've worked in that code, but here are some quick
thoughts:
1) There's already code reading the headers, searching for mail loops by
looking at the Delivered-To header. You could tap into that code.
2) You could look at simscan.c to see how they're
