nd can be turned off completely
just by removing one line from MailFilter::Settings.pm.
Just a suggestion... and making MD even more modern with better OO sounds good
to me. I've basically done this to make it a bit more manageable, back in the
days when I started using this.
--
Jan-Pieter Corne
.. any more processing you wish to do in filter_end
}
--
Jan-Pieter Cornet <joh...@xs4all.nl>
"Any sufficiently advanced incompetence is indistinguishable from malice."
- Grey's Law
signature.asc
Description: OpenPGP digital signature
rly.
How about every message for which $SuspiciousCharsInBody is true?
Tried that briefly and turned it off again. Can't remember why, probably
because of false positives (that was in 2004). We currently ignore suspicious
characters in body, don't even log it.
--
Jan-Pieter Cornet <joh...@xs4a
her explicitly or implicitly as
spam-detection algorithms get too many of the same HTML headers, and they start
treating it as spam.
So, just... no.
> Also, please let us know who this is, so the rest of us can block
> their mail...
--
Jan-Pieter Cornet <joh...@xs4all.net>
Syste
sender's network as spam feedback. Quite useful.
--
Jan-Pieter Cornet <joh...@xs4all.net>
Systeembeheer XS4ALL Internet bv
www.xs4all.nl
signature.asc
Description: OpenPGP digital signature
___
NOTE: If there is a disclaimer or other legal boilerpla
s it uses a modular Mimedefang.pm, but
the changes should be trivial.
--
Jan-Pieter Cornet <joh...@xs4all.nl>
"Any sufficiently advanced incompetence is indistinguishable from malice."
- Grey's Law
package MailFilter::SpamC;
# provide spamc interface to spamassassin, ca
tracking. You
wouldn't need to in this case).
Or as others have suggested, use rfc1918 non-routable IP space on a separate
vlan interface to shield your internal mail server.
--
Jan-Pieter Cornet joh...@xs4all.nl
Any sufficiently advanced incompetence is indistinguishable from malice
the extra nameserver, it'll only cause confusion).
--
Jan-Pieter Cornet joh...@xs4all.nl
Any sufficiently advanced incompetence is indistinguishable from malice.
- Grey's Law
signature.asc
Description: OpenPGP digital signature
___
NOTE
that is in sendmail macro
${client_addr} )
--
Jan-Pieter Cornet
If you're doing nothing wrong, you have nothing to hide from the giant
surveillance apparatus the government's been hiding. -- Stephen Colbert
signature.asc
Description: OpenPGP digital signature
/dmarc-reject
--
Jan-Pieter Cornet
If you're doing nothing wrong, you have nothing to hide from the giant
surveillance apparatus the government's been hiding. -- Stephen Colbert
signature.asc
Description: OpenPGP digital signature
___
NOTE
with HReceived: in their
sendmail.cf file)…
No, milter will give you the message as received, without the first Received
header added.
--
Jan-Pieter Cornet
If you're doing nothing wrong, you have nothing to hide from the giant
surveillance apparatus the government's been hiding. -- Stephen Colbert
be careful before using DMARC on your own domain, though.
Notably, it breaks mail to mailinglists... it's most effective on domains that
are often the victim of phishing.
--
Jan-Pieter Cornet
Most seasonal greetings are sent by spammers and phishers.
signature.asc
Description: OpenPGP digital
should be using it anymore.
--
Jan-Pieter Cornet
Most seasonal greetings are sent by spammers and phishers.
signature.asc
Description: OpenPGP digital signature
___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message
installed it yet).
I am seeing this on 5.16 as well.
That's very likely caused by these statements:
sub message_contains_virus () {
[...]
if (!defined(@VirusScannerMessageRoutines)) {
sub entity_contains_virus ($) {
if (!defined(@VirusScannerEntityRoutines)) {
--
Jan-Pieter Cornet
SSL
.
Then for all users that do not wish to receive a mail, we replace the recipient
with username@spamfolder.local.
Required just a few custom patches to mail.local, and some sendmail.cf hackery.
--
Jan-Pieter Cornet joh...@xs4all.net
Systeembeheer XS4ALL Internet bv
Internet: www.xs4all.nl
was compromised).
--
Jan-Pieter Cornet joh...@xs4all.net
Systeembeheer XS4ALL Internet bv
Internet: www.xs4all.nl
Contact: www.xs4all.nl/contact
signature.asc
Description: OpenPGP digital signature
___
NOTE: If there is a disclaimer or other legal
(unless you want to
localise the scope of the exported functions/variables, which currently doesn't
work really well, but is most certainly NOT what you intended here).
Just put 'use' statements at the top of your script.
- --
Jan-Pieter Cornet
SSL is only keeping your connection safe from hackers
a protection
against typo's if you declare all your globals, so
$SlightlyMispeledVariableName will trigger an error, where
$Conf{SlightleyMispeldVariabelName} won't trigger a warning, except possibly
for use of undefined value.
--
Jan-Pieter Cornet joh...@xs4all.net
Systeembeheer XS4ALL Internet
.
--
Jan-Pieter Cornet joh...@xs4all.nl
People are continuously reinventing the flat tyre.
___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID. You may ignore it.
Visit http://www.mimedefang.org and http
the thread that starts here for the background:
http://lists.roaringpenguin.com/pipermail/mimedefang/2011-February/036098.html )
--
Jan-Pieter Cornet joh...@xs4all.net
Systeembeheer XS4ALL Internet bv
Internet: www.xs4all.nl
Contact: www.xs4all.nl/contact
-Pieter Cornet joh...@xs4all.net
Systeembeheer XS4ALL Internet bv
Internet: www.xs4all.nl
Contact: www.xs4all.nl/contact
___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID. You may ignore it.
Visit http
it use Sys::Syslog, would that actually
work?
Yes.
What would I lose by doing that?
The ability to easily upgrade when a new mimedefang version comes out.
--
Jan-Pieter Cornet joh...@xs4all.net
Systeembeheer XS4ALL Internet bv
Internet: www.xs4all.nl
Contact: www.xs4all.nl/contact
as well).
Any suggestion or hint to solve that problem are welcomed.
hint: $SALocalTestsOnly
--
Jan-Pieter Cornet joh...@xs4all.net
Systeembeheer XS4ALL Internet bv
Internet: www.xs4all.nl
Contact: www.xs4all.nl/contact
___
NOTE
and filter_end. If
you do that, make sure you know where to initialize those variables.
--
Jan-Pieter Cornet joh...@xs4all.net
Systeembeheer XS4ALL Internet bv
Internet: www.xs4all.nl
Contact: www.xs4all.nl/contact
___
NOTE: If there is a disclaimer or other legal
a slightly different view. I consider the documentation
accurate, but occasionally unclear when used as a reference manual. I
do not believe that the fact that I'm not a native english speaker has
much to do with this, but that might be hubris on my part :)
--
Jan-Pieter Cornet joh...@xs4all.net
, filter_multipart and
filter_end.
(I can't recall exactly - I know I did some work on this section of
the manpage because of the introduction of read_commands_file(), could
be this is partly my fault).
--
Jan-Pieter Cornet joh...@xs4all.net
Systeembeheer XS4ALL Internet bv
Internet: www.xs4all.nl
.
What you could do is resubmit the mail locally, possibly using
resend_message(@Recipients), after suitably altering $RealRelayAddr
and $RealRelayHostname.
--
Jan-Pieter Cornet joh...@xs4all.nl
People are continuously reinventing the flat tyre.
___
NOTE
. (... or a visit
from the feds. Or a request from a big law firm. Or a request from any
law enforcement agency anywhere on earth. Even from China or Pakistan.)
--
Jan-Pieter Cornet joh...@xs4all.nl
People are continuously reinventing the flat tyre
file, like this:
Host your-mimedefang-running-host.domain.tld
User root
On unix, the ssh config file is in $HOME/.ssh/config. I suppose
there's something similar on cygwin.
--
Jan-Pieter Cornet joh...@xs4all.nl
People are continuously reinventing the flat tyre
message through spamassassin twice).
--
Jan-Pieter Cornet joh...@xs4all.nl
People are continuously reinventing the flat tyre.
___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID. You may ignore
) = @_;
IO::Select-new($sock)-can_read( $opts{timeout} || 0)
or return undef;
return $sock-sysread($buf, $len);
}
That should do it. No guarantees, if it breaks, you get to keep both
pieces, YMMV, etc.
--
Jan-Pieter Cornet joh...@xs4all.net
Systeembeheer XS4ALL Internet bv
of spam.
--
Jan-Pieter Cornet joh...@xs4all.nl
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please !!
!! archive this message indefinitely to allow verification of the logs
).
Every case I've seen where such unpredictable behaviour was seen, which
could not be (easily) reproduced while testing, was a case of state
variables leaking values from one call to the next.
--
Jan-Pieter Cornet joh...@xs4all.nl
!! Disclamer: The addressee of this email is not the intended recipient
, using only
ascii characters to write english.
The test used by Richard Laager is the only correct way to do this:
first convert to unicode, then test to see if there are illegal
characters present.
--
Jan-Pieter Cornet joh...@xs4all.nl
!! Disclamer: The addressee of this email is not the intended
On Fri, Apr 17, 2009 at 09:07:23AM -0400, Kevin A. McGrail wrote:
On Fri, Apr 17, 2009 at 11:16:14AM +0200, Jan Pieter Cornet wrote:
On Thu, Apr 16, 2009 at 10:37:33PM -0400, Kevin A. McGrail wrote:
Richard,
I've been looking at this and the code seems to work but I wonder if you
suggestions are perfect. Particularly, do look at MAINTAINING STATE in
the manual.
--
Jan-Pieter Cornet joh...@xs4all.nl
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please !!
!! archive this message
scan_for_virus {
...
if ( $SendmailMacros{daemon_name} =~ /noscan$/ ) {
md_syslog('warning', $MsgID: No virus scanning);
return;
}
...
That said, if you want to differentiate on if the user is authenticated
or not, then do so, using the code Joseph gave.
--
Jan-Pieter
available in
man mimedefang-filter and some clues in my previous message on
this subject. The one you replied to, even...
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention
{$recip}[2];
...
I'm sure there is more, but those are the things that I could use.
Well, have fun! :)
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please
be no problem.
The same cannot necessarily be said about upgrades to sendmail 8.14,
though. I believe a libmilter from sendmail 8.13 will work on
sendmail 8.14, but I haven't tested it myself.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended
without
causing a lot of grief in lost emails.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please !!
!! archive this message indefinitely to allow verification
always deploy
BATV (http://mipassoc.org/batv/) locally, and reject fake
bounces.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please !!
!! archive this message
, though, the ISP has got
to have the proper hardware to do that kind of filtering with per-
tunnel specific properties, and not all hardware is up to that.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test
is actually listed (lookup) or if it just returns you the default
record (default). If you get the default it's likely best to fall
back to WHOIS info.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon
conforming email clients on
your incoming mail server? There shouldn't be any clients talking to
that MTA directly anyway.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems
not to be stupid the entire spam
problem would vanish overnight too...
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please !!
!! archive this message indefinitely
/etc/mail. Substitute the appropriate paths for
your setup, if necessary)
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please !!
!! archive this message
for that storage (109T)
just this morning? :)
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please !!
!! archive this message indefinitely to allow verification
for spam so I currently have the
users sending though the outbound MTA.
I suppose the outbound MTA has only one spamfiltering setting: the one
you (the administrator) choose. It should not depend on the recipient,
so it's a lot easier to configure.
--
Jan-Pieter Cornet [EMAIL PROTECTED
from the list... even though the message
said something like 550 successfully delivered to [EMAIL PROTECTED] and
[EMAIL PROTECTED], but rejected by [EMAIL PROTECTED].
Drusilla and Xander would still be out of luck...
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee
option is to detect this possibility at filter_recipient
time, and tempfail recipients that have a filter profile that isn't
on par with the filter of the first recipient. Optionally only for
hosts that have some sort of flag set.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee
sendmail cf directory.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please !!
!! archive this message indefinitely to allow verification of the logs
have sig-
naled acceptance of the message. PostMilter
is useful only when sendmail is running as
an SMTP server; in all other situations it
acts the same as True.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer
connections. It's polite to leave it
at the maximum recommended MCI_CACHE_TIMEOUT, which is 10 minutes.
(But in over 80% of the cases you'd be polite to spammers...)
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only
a problem when you autodetect
your modules, and uses the autodetected syslog available to log an
error for example about an unreadable filter, without consulting any
user preferences in the user supplied (but unreadable) filter :)
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee
with mimedefang, just not very easy. In fact, it's ugly.
You'll have to tell sendmail to discard the message, and then resubmit
it to sendmail with another envelope sender.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test
-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please !!
!! archive this message indefinitely to allow verification of the logs
to maintain,
and will likely remain buggy in unforseen ways (like - there are
all sorts of sendmail compiled-in limits that you run into if you
really push the borders of the cf language).
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient
if
the connection is still active when you need it.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please !!
!! archive this message indefinitely to allow verification
appreciated!!
By far your best option is simply to remove the backup (secondary)
MX from the DNS. Using fallback MX not under your control is really
outdated these days.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only
: This talks about the header, not envelope. Multiple addresses
aren't allowed on the RCPT To: envelope.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please
).
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please !!
!! archive this message indefinitely to allow verification of the logs
DSL lines that do not allow you to
change reverse DNS, but that do operate their own domain, properly
pointing back to their own mailserver on their DSL line, are allowed
through.
I'll even patch that myself if I can find a round tuit, and install
it for my test-userbase.
--
Jan-Pieter Cornet
will be lost.
You should only ever make changes to your site-specific files, like
local.cf, or sa-mimedefang.cf in case of mimedefang.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data
it... but it'd take too much time right now
to search all of his posts in my current archive.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please !!
!! archive
).
On the other hand, if you're running a caching nameserver, since
sendmail already performed the lookup, it's practically always
instantaneous to lookup again.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test
as
trusted_networks, so you don't have to set them both, necessarily. But
it might be good practice to set them both explicitly, even if just for
documentation purposes.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient
On Sun, Dec 03, 2006 at 09:55:34PM +0200, Yizhar Hurwitz wrote:
From: Jan-Pieter Cornet [EMAIL PROTECTED]
Add the IP address of mailrelay1 (as seen by your mimedefang server)
to the trusted_networks config in spamassassin. See:
man Mail::SpamAssassin::Conf
Yes, I think that this is exactly
, unless you count:
grep -r RULENAME {/var/lib,/usr{,/local}/share,/etc}/spamassassin
(but see man spamassassin for the list of directories where your
spamassassin takes its configuration from).
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended
(as seen by your mimedefang server)
to the trusted_networks config in spamassassin. See:
man Mail::SpamAssassin::Conf
Note that that doesn't set $Helo or $RelayAddr in mimedefang, it will
only fix things up for spamassassin.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee
to mess with undocumented non-forward compatibility issues.
If I ever suggested that it's better to re-implement spamc in perl
(I seem to recall I did), then that was based on the assumption that
the spamd protocol was documented and easy.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer
to
create a standalone perl version of spamc.
However, I probably won't bother... unless we can show that the overhead
is significant.
Oh, I'm using IPC::Open2 to write to and read from spamc, and prevent
tempfiles and executions via the shell. If you're interested, let me
know.
--
Jan-Pieter Cornet
at the moment either...
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please !!
!! archive this message indefinitely to allow verification of the logs
, which comes later (i presume?)
will detect less spam.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please !!
!! archive this message indefinitely to allow
.
Of course, if every email is run through spamassassin, there probably
isn't a lot to gain.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please !!
!! archive
.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please !!
!! archive this message indefinitely to allow verification of the logs
a lot of people seem to botch up.
I'm not convinced MIMEDefang is the ideal spam eradication product
for the unwashed masses.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention
to code it if you can't do it
yourself. Or a good book on perl, it's really not that hard...
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please !!
!! archive
on mimedefang and add
{msg_size} to the Milter.macros.envfrom).
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please !!
!! archive this message indefinitely to allow
don't want interactive delivery, anyway. You want some
sort of best-effort error-propagationable (*) delivery attempt,
falling back to queued delivery if it isn't happening pronto.
(*) yes, I'm aware propagationable isn't a word :)
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer
will check when it was added, and (yuck) make MIMEDefang check
the version and not pass the LOCAL_STATE_DIR into the constructor. :-(
In 3.1.5, I just checked (released aug 29th)
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient
, filter_multipart and filter_end) are
run in the same slave process.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please !!
!! archive this message indefinitely to allow
not measurable, so maybe I'm overreacting.
Hmm... I just realised that the last time I brought this up,
somebody suggested putting it on a public cvs or svn, I considered
that I good idea.. and... never came around to doing that.
If there's still interest, I can still do so.
--
Jan-Pieter Cornet
(such as one of my users
having a third-party web-site generate an email on behalf of the user.)
Oh, there will be broken web forms somewhere that send email with
whatever someone will type in a form. It remains to be seen whether
those are legitimate.
--
Jan-Pieter Cornet [EMAIL PROTECTED
and my logfiles, but taking neither as gospel.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please !!
!! archive this message indefinitely to allow verification
that isn't ideal either, because it will
block wellbehaved SOHO mailservers on DSL lines from really crappy
providers (without properly functioning outgoing mailservers,
and without a possibility to change the reverse DNS name).
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disc lamer: The addressee
On Tue, Jul 11, 2006 at 02:30:22PM -0400, Paul Russell wrote:
On 11 Jul 2006, Jan-Pieter Cornet [EMAIL PROTECTED] wrote:
Also note that I'm not aware of any SMTP server implementation that
actually enforces syntactic checks on the HELO or EHLO argument out
of the box (resulting in lots
On Tue, Jul 11, 2006 at 12:37:44PM +0200, Steffen Kaiser wrote:
On Tue, 11 Jul 2006, Jan-Pieter Cornet wrote:
So, based on this latter paragraph, it is entirely OK to reject
after EHLO 127.0.0.1, since that is not a properly formatted EHLO
argument. RFC821 has similar restrictions
,
domain2 is local to server2, and has server2 as the only MX.
And it works just as well.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disc lamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please !!
!! archive
to your reliability :)
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disc lamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please !!
!! archive this message indefinitely to allow verification of the logs
{((ord$)%32-1)/$_%3}(9,
3,1)]),5,1)='`'lt$;$f.eig;# Jan-Pieter Cornet
___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID. You may ignore it.
Visit http://www.mimedefang.org
the transaction ID when the mail is accepted). Your sendmail log
should include that.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disc lamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please !!
!! archive this message
On Thu, Jun 15, 2006 at 03:18:11PM +0200, Jan-Pieter Cornet wrote:
Also: I have a patch against MIME::Parser to support a max_depth
limit
I promised to get back on this. The patch is now available at:
http://www.xs4all.nl/~johnpc/MIME-tools-5.420-maxdepth.patch
This includes a test to test
but that doesn't include tests for max_depth). I hopefully
have a chance to finish that this evening... (otherwise it'll have
to wait until tuesday, or someone should step forward and take over).
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disc lamer: The addressee of this email is not the intended
).
But I'm just speculating here: handwaving, educated guesses, some
astrology, and reading the intestines of a freshly slaughtered goat,
which is the first thing to consult in case of sendmail troubles
anyway.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disc lamer: The addressee of this email
;
...
store($hashref, filename);
(or $arrayref, or $AnyComplexObjectYoudLikeToStoreExceptOpenFilehandles)
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disc lamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please
: MIMEDefang is good enough (as I already said in my previous
message :)
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disc lamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please !!
!! archive this message indefinitely
for body rules at all.
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disc lamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please !!
!! archive this message indefinitely to allow verification of the logs
what you mean here. Although this
does the same, but this is trickier to maintain. (If you add or
remove a rule you have to update the count. Also the brackets
aren't necessary).
Hope this helps!
--
Jan-Pieter Cornet [EMAIL PROTECTED]
!! Disc lamer: The addressee of this email is not the intended
compare those numbers further because the list
archive goes back a lot further than the spam archive, but even
then... the numbers above already show that this test, in itself,
has an extremely high FP ratio. This test is not adding anything
decisive to your tests.
--
Jan-Pieter Cornet [EMAIL
1 - 100 of 256 matches
Mail list logo
