On 05/09/2014 12:53 PM, [email protected] wrote:
On 05/09/2014 11:19 AM, [email protected] wrote:
Are you sure that both .qmail-default and .qmail are not used in the
delivery process? I'm seeing each email processed by both files as each
email has a dspam tag (.qmail-default) and also is logged by maildrop
(.qmail).
That said, I do have the servers set up to do the test you suggest.
I wouldn't bet my life on it, so no I'm not positive. It doesn't make
sense to me though that both would be invoked. So much for making sense.
Upon further review, it appears to me now that you're correct. The
domain's .qmail-default is used first, invoking vdelivermail, which then
must invoke the user's .qmail file if it exists. I need to do a little
more digging in the source to see what's really going on.
In the meantime, can you do a little more testing? I'm guessing that the
attachments are making it to the queue and they're being dropped during
delivery. Can you verify this? We'll simply need to track this thing
through the various stages to see where the problem is.
I'm guessing the problem is between dspam and vdelivermail. That's just
a guess though.
--
-Eric 'shubes'
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Sadly, the reason for my sporadic invocation of help on this issue and the
inability to test as I would please, is because it is unpredictable and
getting clients' clients to resend the offending emails more than once is
like herding cats. One person simply refused. However, I've got everything
set up to catch the offending software during delivery and will let you
know when possible.
In your estimation, if there indeed was a problem between dspam and
vdelivermail, how would one address this issue?
Thanks for your help, EricS.
EricB.
---------------------------------------------------------------------
I understand your situation. Diagnostics are tough when things aren't
easily reproduced.
One thing you might try is to use "tee" to capture what's going through
the pipes.
For instance, you could have this in .qmail-default:
| tee -a /tmp/pre-dspam.log | /usr/local/bin/dspamc --user "$EXT@$HOST"
--deliver=stdout | tee -a /tmp/post-dspam.log |
/home/vpopmail/bin/vdelivermail '' bounce-no-mailbox
This should give you 2 files, pre-dspam.log and post-dspam.log. These
will get to be pretty big, so make sure you don't fill up a filesystem.
You could use the same technique in the .qmail file. The "tee" command
is very handy at times for capturing what goes through pipes. :)
I'll let you know if I think of something else.
--
-Eric 'shubes'
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
