es, and 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-Pi
decoding From: $fromline; error:
$@");
}
# ... any more processing you wish to do in filter_end
}
--
Jan-Pieter Cornet
"Any sufficiently advanced incompetence is indistinguishable from malice."
- Grey's Law
signature.asc
Description: OpenPGP digital si
formatted
properly.
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.
--
J
your domain blocked, either 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
Sys
t;>
>> https://www.youtube.com/watch?v=koRRqOJcaHs
Funny thing is, this method of both accepting AND rejecting is actually
observed in practice :)
There are a number of trap hosts that reject a message after data, AND send the
received mail back to the sender's network as
will need to modify this SpamC.pm as it uses a modular Mimedefang.pm, but
the changes should be trivial.
--
Jan-Pieter Cornet
"Any sufficiently advanced incompetence is indistinguishable from malice."
- Grey's Law
package MailFilter::SpamC;
# provide spamc interface to spamassa
nless you're doing something silly (eg: do not use connection 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
"Any sufficiently adva
ns.2rad.net. So you'd see that extra name server depending on whether the
caching name servers where you're sending the queries, previously queried that
domain. Normally, domains wouldn't exhibit this sort of behaviour (and if you
want my advice - d
all (and it contains the value 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
will stop that. No
need for any patches in mimedefang:
https://code.launchpad.net/~jimpop/mailman/dmarc-reject
--
Jan-Pieter Cornet
"If you're doing nothing wrong, you have nothing to hide from the giant
surveillance apparatus the governme
table Received:
> formats (assuming no one has mucked 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
age5121882
Or in the case of SPF, more likely this:
http://thumbs.dreamstime.com/thumblarge_593/1300952810s9s08A.jpg
:-)
--
Jan-Pieter Cornet
"Most seasonal greetings are sent by spammers and phishers."
signature.asc
Description: OpenPGP digital signature
___
rt DMARC...
Note that you should 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.&qu
sn't even do its
> "ADSP" extension coding correctly:
ADSP is almost dead, and widely considered dangerous. Nobody in his right mind
should be using it anymore.
--
Jan-Pieter Cornet
"Most seasonal greetings are sent by spammers and phishers."
signature.asc
Descript
ilMacros{auth_authen} ) {
# connection has authenticated
...
}
Unless you are doing this check in filter_sender() or filter_recipient() (which
is really unlikely if you're doing content filtering), then you will have to
call read_commands_file() before doing the test.
--
sScannerMessageRoutines)) {
sub entity_contains_virus ($) {
if (!defined(@VirusScannerEntityRoutines)) {
--
Jan-Pieter Cornet
SSL is only keeping your connection safe from hackers, crooks and three
letter agencies by the least secured, least likely to refuse money from
strangers, and least bully
ule to
deliver @spamfolder.local to this mailer.
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
Systeembeheer XS4ALL In
thenticated (so if spam is sent out via a weak password,
you at least know whose password was compromised).
--
Jan-Pieter Cornet
Systeembeheer XS4ALL Internet bv
Internet: www.xs4all.nl
Contact: www.xs4all.nl/contact
signature.asc
Description: OpenPGP digital signature
__
nt putting it in a subroutine (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
S
7;reset' the configuration by doing '%Conf = ()'
The only disadvantage that I can see is that with globals, you get a protection
against typo's if you declare all your globals, so
$SlightlyMispeledVariableName will trigger an error, where
$Conf{SlightleyMispeldVariabelN
up like this. But it could be really useful, and make
it very easy to integrate mimedefang with additional milters, allowing
mimedefang to even control the behaviour of the other milter.
--
Jan-Pieter Cornet
"People are continuously reinventing the flat tyre".
__
my $constant = $AUTOLOAD;
$constant =~ s/.*:://;
die "Undefined constant $constant"; # or possibly croak()
}
(Marcus: see the thread that starts here for the background:
http://lists.roaringpenguin.com/pipermail/mimedefang/2011-February/03
, you'll
+# get a warning from the eval below (on modern perl versions).
+
+my $value = eval "Unix::Syslog::$name()";
+return $value;
+}
}
1;
(just to cut legal corners (is this really necessary?): patch is now public
domain,
Sys::Sylog works better, I suggest you use that instead (if you
installed Unix::Syslog especially for this, remove it).
> If I put my change in and just let it use Sys::Syslog, would that actually
> work?
Yes.
> What would I lose by doing that?
The ability to easily upgrad
-D < /tmp/JunkMail.msg to
> compare the score with what I add in my mail header. (yes, I tried with the
> defang user as well).
> Any suggestion or hint to solve that problem are welcomed.
hint: $SALocalTestsOnly
--
Jan-Pieter Cornet
Systeembeheer XS4ALL Internet bv
Internet: www.xs4all
variables, is between filter_begin, filter, filter_multipart and filter_end. If
you do that, make sure you know where to initialize those variables.
--
Jan-Pieter Cornet
Systeembeheer XS4ALL Internet bv
Internet: www.xs4all.nl
Contact: www.xs4all.nl/contact
_
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
Systeembeheer XS4ALL Internet bv
Int
start of the section to be filter_begin, filter, 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
Systeembe
;t lost (hah, google
and deleting data??!), it's just not publicly available. Google will
surely dish up the info if they get abuse complaints. (... or a visit
from the feds. Or a request from a big law firm. Or a request from any
law en
ent received header. You can delete
previous Received: headers, though.
What you could do is resubmit the mail locally, possibly using
resend_message(@Recipients), after suitably altering $RealRelayAddr
and $RealRelayHostname.
--
Jan-Pieter Cornet
"People are continuously reinventing the flat t
ght user in the ssh_config 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
"People are continuously
ut last time I did test, it didn't work
(in sendmail 8.13). Rewriting to multiple addresses could only be done
through the aliases file, not the virtusertable file.
Which leaves only the mimedefang solution...
--
Jan-Pieter Cornet
Systeembeheer XS4ALL Internet bv
Inte
your mail
server is pushing each message through spamassassin twice).
--
Jan-Pieter Cornet
"People are continuously reinventing the flat tyre".
___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is N
the
reader...
sub read_with_timeout {
my ($sock, $buf, $len, %opts) = @_;
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,
informative than a random bit of spam.
--
Jan-Pieter Cornet
!! 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 allo
r "use strict" and "use
warnings" (yes, even in produktion - warnings end up in the maillog
anyway).
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" val
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 thi
ing a question on, for example, this mailinglist, 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
!! Disclamer: T
ver, you really meant "per SMTP session" information, for
example to remember state between "RCPT" commands, then David's
suggestions are perfect. Particularly, do look at "MAINTAINING STATE" in
the manual.
--
Jan-Pieter Cornet
!! Disclamer: The addressee of this
...
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 Cornet
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the echelon and data retention systems. Please !!
!!
lable in
> filter_end? Or do we have to create a state file in CWD?
I refer you to the excellent documentation 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]&g
}[0] eq "local" )
$mailbox = $RecipientMailers{$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. !!
!!
On Thu, Feb 01, 2007 at 07:59:21AM -0800, Kenneth Porter wrote:
> --On Wednesday, January 31, 2007 10:54 PM +0100 Jan-Pieter Cornet
> <[EMAIL PROTECTED]> wrote:
>
> >By the way, if you hate bounce spam, you could always deploy
> >BATV (http://mipassoc.org/batv
525.html
I'm actually refactoring that code as I write this, to do another
quota check late in the delivery process, to also check the quota
on the spambox, if applicable. To cut down on backscatter.
--
Jan-Pieter Cornet <[EMAIL PROTECTED]>
!! Disclamer: The addressee of this email i
es often enough.
By the way, if you hate bounce spam, you could 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 ec
urpose of
backscatter prevention, but we cannot reduce it to zero 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 retentio
mail 8.13.8.
So in your case, there should 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]>
!! Di
do a DNS query for
"example.com.contacts.abuse.net": TXT records are contact addresses, A
records list the number of contacts, and HINFO tells you if the contact
is actually listed ("lookup") or if it just returns you the default
record ("default"). If you get the
imit
the number of compromised home boxes.
If you want to make this user-adjustable, 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
t subscribers on your domain using a single message,
that message will get a 550 error after data, which might lead to
ALL subscribers being removed from the list... even though the message
said something like "550 successfully delivered to <[EMAIL PROTECTED]> and
<[EMAIL PROTECTED]
to lame email clients, it sounds like it would be
> >> a lot of trouble.
>
> Both the inbound and outbound MTA scan 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)
know that I got the bill 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 mes
along with any other *.cf files you want to use.
(This assumes spamassassin actually uses /etc/mail/spamassassin,
and mimedefang uses /etc/mail. Substitute the appropriate paths for
your setup, if necessary)
--
Jan-Pieter Cornet <[EMAIL PROTECTED]>
!! Disclamer: The addressee of this email
ok Express still didn't support imap anyway...
Hell, if we could just teach users 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
ssimilar
> spam settings, but due to lame email clients, it sounds like it would be
> a lot of trouble.
Erm... what do you care about insufficiently conforming email clients on
your incoming mail server? There shouldn't be any clients talking to
that MTA directly anyway.
--
Jan-Pieter C
introduce another
threshhold score above which you can junk messages instead of
delivering or rejecting them.
Oh, and a fifth 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. O
e queue file until any milters 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 PROT
lter')
See the README file in your 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 mes
utes (your peers have the option to use that timeout to
cache outgoing sendmail 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
interesting milter API additions that
I'd love to get access to via MIMEDefang, though :) (notably
SMFIP_RCPT_REJ and smfi_chgfrom())
Also configuration can be made easier using xxfi_negotiate (well, in
the long run. In the short term it will only get more complicated,
of course).
--
ecify, if windows thinks it is HTML, it will be rendered
as HTML.
(workarounds: firefox, and/or Ubuntu (insert your favorite linux distro)).
--
Jan-Pieter Cornet <[EMAIL PROTECTED]>
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the ech
r... I don't really think it's 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 <[
r address.
If you want to solve it RFC compliant, you can do two things:
either move the mail for the "other" recipients to a spamfolder (or
just junk it), or, slightly more work:
in case you have multiple recipients, reject combinations of postmaster
and abuse with other users at filter_r
t
try to squeeze out a few microseconds of optimization for a complex
monstrosity that is very hard to produce, impossible 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 lang
>get('Received', -1);
...
Note: the above code is untested. The regular expression matches
a sendmail-style Received line:
Received: from HELO (reverse.dns [i.p.ad.dr] (may be forged))
Have fun,
--
Jan-Pieter Cornet <[EMAIL PROTECTED]>
!! Disclamer:
out. It will allow milters
> to change the envelope sender (not that MIMEDefang supports that yet!)
It can be done 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 s
t"
calls with "DBI->connect_cached" calls, you're fine. This will keep
the connections open, opening "lazily", and automatically checking if
the connection is still active when you need it.
--
Jan-Pieter Cornet <[EMAIL PROTECTED]>
!! Disclamer: The addressee
s case.
> Any help / thoughts / suggestions are much 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]>
!!
line, but
that wasn't the issue here).
--
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 messag
ess definition
further if you like, but I'm sure you can guess what it means.
Note: 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
there's an online archive, but now I cannot find the message
where this idea of checking HELO and envelope sender originated.
I believe RfG mentioned 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]&
s to, say,
/usr/share/spamassassin/10_misc.cf to define the report format,
those changes 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: Th
t myself if I can find a round tuit, and install
it for my test-userbase.
--
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 s
rver for sending
> their outbound mail.
>
> Am I correct?
Yup.
And in the general case, internal_networks will be the same 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 p
hat always contains whatever you see
in the Received header, including the "(may be forged)".
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 <[EMA
y cool (preferably fast) way to figure out what's
> missing so I can get it corrected?
Not really, 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 configura
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::Co
top (or second?) "Received by" header?
Add the IP address of mailrelay1 (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&quo
should be possible 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 inte
ned, so I
didn't want 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 <[E
ade more
> accessible to the unwashed masses.
>
> Not convinced that better integration of SA and MdF settings is a
> bad thing, but I do agree that getting internal_networks right is
> something a lot of people seem to botch up.
I'm not convinced MIMEDefang is the ideal spam er
providing your own version in another directory.
But then again I'm biased, because I wrote a modular filter framework.
--
Jan-Pieter Cornet <[EMAIL PROTECTED]>
!! Disclamer: The addressee of this email is not the intended recipient. !!
!! This is only a test of the ech
, with very occasional
peaks to 15.
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
using clamd, you reduce
the amount of spam, so spamassassin, 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 syste
really need support
builtin to mimedefang 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 mes
d features available from the perl interface,
and possibly modify our interface to follow suit. I don't even bother
to diff the example file to the previous release anymore...
--
Jan-Pieter Cornet <[EMAIL PROTECTED]>
!! Disclamer: The addressee
ggest getting a local perl hacker 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 da
ang explicitly
(then you'll have to use the -a switch 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 retentio
reading of the sendmail source: yes, every EHLO or
HELO command causes a milter call.
Haven't tested it, though.
--
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
nning 3.1.4, and it doesn't
> do this. I 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
y
start the sendmail binary. Maybe even just as a convenience for the
"-v" switch.
You really 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.
l after
processing the message, but it does not propagate the error... it
just bounces 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
exe files, for example.
(That said, I'm trying to do the same, by moving the actual delivery
to MIMEDefang. "Impossible" is not in my dictionary. This will be a huge
speedup improvement, especially since it's combined with md_check_against_
smtp_server anyway, but it w
exceed your available RAM.
> I am also doing SpamCop, DCC, Pyzor, and Razor2. I know these can take time
> is that maybe my problem, if so what should I remove and/or add?
Time is a problem insofar that it makes it more likely that multiple
MD slaves run at the same time... each tak
t?
Yup, that is correct. All functions dealing with the complete email
message (filter_begin, filter, 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 onl
If there's still interest, I can still do so.
--
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 !!
!! a
pipermail/mimedefang/2006-February/029634.html
Maybe that also happens in your case?
--
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 messa
ositives, even if just a few. There
are always well-meaning idiots using really really broken and outdated
setups, that get caught up in the cracks.
In the end, I just do what I think is right, carefully reading the RFCs
and my logfiles, but taking neither as gospel.
--
Jan-Pieter Cornet <[EMA
g 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]
ection. For any other violation, even if it's a local policy violation,
you are allowed to reject the HELO/EHLO argument.
--
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
1 - 100 of 304 matches
Mail list logo
