If you read the manual you'd know. Look for BOFHBADMIME.
Also, using Outlook Express with HTML emails enabled won't help much,
you should consider getting your users to use a secure e-mail client,
one that works.
On 26/03/2004, at 7:54 PM, Lion wrote:
I run the Courier 0.45.2, and all is OK,
Hallo group.
Is there a easy way to keep a copy of all email messages that passes
through a courier mail server?
Our company requires us to do this from now on.
I am still running:
courier-imapd-0.39.2-1.7.1
courier-webmail-0.39.2-1.7.1
courier-maildrop-0.39.2-1.7.1
Pierre Ossman writes:
Sam Varshavchik wrote:
Pierre Ossman writes:
If I write a filter that modifies the file courier gives it to parse,
will
courier then use that modified file or the original copy?
No. This is not going to work.
Do you have an idea of an approach that will work? I
Sam Varshavchik [EMAIL PROTECTED] writes:
Download: http://www.courier-mta.org/download.php#beta
[ ... ]
There's a slight error in the ChangeLog file for all 45.2 releases.
Near the top of that file, the release number is stated as this:
0.42.2
It should be 0.45.2.
--
Lloyd Zusman
There are definitely bugs, especially with the option that archives all
E-mails, so you should upgrade.
Is upgrading effortless if I use RPM's or will it be a major hassle?
--
Bertus Keyser
PhiBlue Technologies
Bryanston
Tel +27 11 706 0339
Fax +27 11 706 8753
www.phiblue.com
Sam Varshavchik [EMAIL PROTECTED] writes:
Lloyd Zusman writes:
Because of this, I would like to propose that the above test in
courier/configure be modified as follows (or at least similarly):
if $CONFIG_SHELL -c ulimit -v 0
then
ULIMIT='ulimit -v'
else
i use courier 0.37.3 (with debian woody)
when i try to reach webadmin with my webbrowser, i obtain a web page like:- [#BADPASS=ERROR: Invalid password#] [#---#] --courier 0.37.3 - Administrative LoginAdministrative password:NOTE: Cookies must be enabled from this point on
and if i try a password
Hello.
Is it possible touse spamassasin as courier
filter?
If not, how can I use spamassassin with maildrop?
links to any guides will be very helpful...
Thanks!
- Lion
From: Sam Varshavchik [mailto:[EMAIL PROTECTED]
Bowie Bailey writes:
What should I do to completely remove Courier so that I can have a clean
install?
rm -rf /usr/lib/courier, and also in your case rm -rf /etc/courier
Perfect. I was able to do a clean install of Courier-0.45.2 with
From: Drew Gibson [mailto:[EMAIL PROTECTED]
I went through the duplicate... issue a few days ago...
Installing the new RPM created a backup of the
/etc/courier/esmtpacceptmailfor.dir/default file which was read by
courier on startup and was, of course, a duplicate. (but not fatally
so)
Hello.
Is it possible to use spamassasin as courier filter?
If not, how can I use spamassassin with maildrop? links to any guides =
will be very helpful...
I invoke it using maildrop by adding the following line to
~/.mailfilter:
xfilter /usr/bin/spamc
I used to invoke it globally, but
From: Lion [mailto:[EMAIL PROTECTED]
Hello.
Is it possible to use spamassasin as courier filter?
Check out Amavisd-new (http://www.ijs.si/software/amavisd/). It
interfaces with SpamAssassin and quite a few virus scanners and is
pretty easy to integrate with Courier.
Keep in mind that a
Charles Fry wrote:
I invoke it using maildrop by adding the following line to
~/.mailfilter:
xfilter /usr/bin/spamc
I used to invoke it globally, but then realized I didn't want to check
mail that would never be delivered to a valid user, and this was the
only obvious way I saw to do this. If
Hello all,
I have the following problem: If I try to send an
email with sqwebmail and exim I get the following answer:
exim: @???pha.dyndns.tv - bad address: domain missing or malformed
My doname is alpha.dyndns.tv, I use the plainauth module (with PAM).
I have checked the sendit.sh script
Sam Varshavchik wrote:
Bertus Keyser @ PhiBlue writes:
Hallo group.
Is there a easy way to keep a copy of all email messages that passes
through a courier mail server?
Our company requires us to do this from now on.
I am still running:
courier-imapd-0.39.2-1.7.1
courier-webmail-0.39.2-1.7.1
Hello,
Currently running Courier 0.44.2 as a backup MX for several of my
domains, and I notice this (extremely) repetitive cycle of messages in
my maillog. Presumably this is because the server is trying to deliver
original (spam) messages, getting a failure because the users don't
exist or
Hi,
I've looked through the documentation, the mailing list archives, and
Google, and have not found an answer to my question, so I am posting it
here:
Is there away to eliminate double bounces?
I am specifically concerned with the following scenario: Spam sent to
inexistant local addresses is
I came across a particularly nasty fatal error in courier (5.0.0?):
'UNKNOWN ERROR - no further description is available'
Which seems to come from localmail.c line 359:
strcpy(errptr, UNKNOWN ERROR - no further description is available);
Can someone please give me a bit of insight as to what is
If you look in the courierd-file, you'll see this, which is what you are
looking for (I think):
##NAME: ARCHIVEDIR:0
#
# This is the big-brother option that saves a copy of EACH and EVERY
# message passing through the system. Uncomment ARCHIVEDIR, and after
# a message is delivered, its queue
You should be able to modify the .spec file and then re-tar and bzip2 the
file before building the rpms. Just edit the .spec and remove the cgi-bin
and html reqs. Installing with --nodeps will lead to problems down the
road when you go to upgrade.
Jay
~
Jay Lee
Network
Bertus Keyser @ PhiBlue writes:
There are definitely bugs, especially with the option that archives all
E-mails, so you should upgrade.
Is upgrading effortless if I use RPM's or will it be a major hassle?
Yes, provided that you have a well-managed production/development
environment.
Well-managed
Dennis Berger writes:
There are definitely bugs, especially with the option that archives
all E-mails, so you should upgrade.
maybe you tell us the option? ;-) that archives all emails
ARCHIVEDIR in the courierd configuration file.
pgp0.pgp
Description: PGP signature
pascal carrie writes:
HTML content follows
i use courier 0.37.3 (with debian woody)
This is an ancient version.
I doubt that anyone has been interested in it for at least a couple of
years.
pgp0.pgp
Description: PGP signature
Kevin Murphy writes:
I've seen postings about this before, but I don't recall the solutions
(nor can I find them when searching through the list archives). So my
question is, plain and simply, how do I stop this from happening?
I don't want this kind of unnecessary activity on the server, nor
I invoke it using maildrop by adding the following line to
~/.mailfilter:
xfilter /usr/bin/spamc
I used to invoke it globally, but then realized I didn't want to check
mail that would never be delivered to a valid user, and this was the
only obvious way I saw to do this. If
Roger Ward writes:
About 0.7% of our email has this error when delivering at the domain level...
I have NEVER seen it happen at the 'user' level... keep in mind that the
'domains' and 'users' are both authmysql accounts.
Everything works normally most of the time, and while I have reached some
Charles Fry wrote:
I invoke it using maildrop by adding the following line to
~/.mailfilter:
xfilter /usr/bin/spamc
I used to invoke it globally, but then realized I didn't want to check
mail that would never be delivered to a valid user, and this was the
only obvious way I saw to do this. If
On Mar 26, 2004, at 6:46 PM, Sam Varshavchik wrote:
There are two problems here.
One is that you have the machine name set to penguin. You must
always use a fully-qualified domain name. Adjust your me and/or
locals and/or default configuration files accordingly.
Secondly you do need a local
28 matches
Mail list logo