On 2012-08-02 4:37 PM, John Nemeth wrote:
http://lists.roaringpenguin.com/pipermail/mimedefang/2005-April/026563.html
http://lists.roaringpenguin.com/pipermail/mimedefang/2005-September/028147.html
http://lists.roaringpenguin.com/pipermail/mimedefang/2006-June/030475.html
On Wed, 01 Aug 2012 14:56:49 -0500
Ben Kamen bka...@benjammin.net wrote:
Ok and that's where I get lost in where SA starts and MD ends (blame
the amount of time it's been since I was last deeply in this which is
no where as deeply as you or most others on this list - I miss it.
not sure why,
Am 01.08.2012 21:56, schrieb Ben Kamen:
On 2012-08-01 7:22 AM, David F. Skoll wrote:
On Wed, 01 Aug 2012 01:23:33 -0500
Ben Kamen bka...@benjammin.net wrote:
But I don't see any place explicitly calling out
~dest_user/.spamassassin/userprefs in any form (still looking)
You won't see that
On 8/2/2012 12:00 PM, Tilman Schmidt wrote:
Perhaps it could be taught, though. I guess you could add some Perl
code to the mimedefang-filter script to - check the domain part of
destination addresses whether it is delivered locally (eg. by looking
it up in local-host-names) - if so, look up
On Thu, 02 Aug 2012 13:13:45 -0400
Kevin A. McGrail kmcgr...@pccc.com wrote:
Or just shell out and run sendmail -bv [email address]
Which may not work 100%. MD runs as defang and sendmail -bv is not
guaranteed to be accurate for non-root users:
$ /usr/sbin/sendmail -bv d...@roaringpenguin.com
Am 02.08.2012 19:13, schrieb Kevin A. McGrail:
On 8/2/2012 12:00 PM, Tilman Schmidt wrote:
Perhaps it could be taught, though. I guess you could add some Perl
code to the mimedefang-filter script to - check the domain part of
destination addresses whether it is delivered locally (eg. by
it up in local-host-names) - if so, look up the local part in aliases
and/or virtusertable to find if it is delivered to a local shell user
- if found, look in that user's home directory for a
.spamassassin/userprefs file - if it exists, use it.
This whole discussion assumes that each
I suppose you could enforce the former by telling sendmail to temp fail
RCPT commands after the first, to get messages in one recipient at a
time.
I suppose local policies could enforce the latter.
That would eliminate the main difficulties.
That's brilliant. I wonder if most MTAs will
On Thu, 02 Aug 2012 16:56:24 -0400
Kevin A. McGrail kmcgr...@pccc.com wrote:
I suppose you could enforce the former by telling sendmail to temp
fail RCPT commands after the first, to get messages in one
recipient at a time.
That's brilliant. I wonder if most MTAs will properly handle
s/brilliant/brilliant, but evil and certainly inadvisable/
Agreed, though I actually meant brilliant with the steepled hands and
the raised eyebrow and perhaps a maniacal laugh.
I just liked the simplicity of it and agree completely that the
recipient stream is the way to go.
regards,
KAM
On Wed, 01 Aug 2012 01:23:33 -0500
Ben Kamen bka...@benjammin.net wrote:
But what's weird is that I updated /etc/mail/spamassassin/local.cf
with my settings and that seems to be the one in use even
You probably need to do md-mx-ctrl reread to have MD notice the changes.
But I don't see any
On 7/31/2012 10:35 PM, Ben Kamen wrote:
Quick yes/no...
when using SA though MD, does SA still check the user_prefs (for
white/blacklisting) in the
destination user's homedir/.spamassassin/ directory?
I whitelisted *@domain.com and just got an email still marked as spam
by SA.
Annoying
On 2012-08-01 7:22 AM, David F. Skoll wrote:
On Wed, 01 Aug 2012 01:23:33 -0500
Ben Kamen bka...@benjammin.net wrote:
But what's weird is that I updated /etc/mail/spamassassin/local.cf
with my settings and that seems to be the one in use even
You probably need to do md-mx-ctrl reread to have
Quick yes/no...
when using SA though MD, does SA still check the user_prefs (for
white/blacklisting) in the
destination user's homedir/.spamassassin/ directory?
I whitelisted *@domain.com and just got an email still marked as spam by SA.
Thanks,
-Ben
--
Ben Kamen - O.D.T., S.P.
14 matches
Mail list logo
