Jeff Potter writes:
There's nothing technically wrong with changing the quoting prefix,
however I'd venture a guess that a lot more software expect
">Return-Path:" then the number of broken software written by
Microsoft (as hard as this may be to believe).
In short: more stuff is likely to brea
I've been semi-succesfull in setting up Courier and Amavisd-new. Everything
works, except that amavisd-new (running as a courierfilter) cannot seem to
add any headers to the message. I don't have a clue where to look for a
solution, besides the config-file and file-permissions, any suggestions?
There's nothing technically wrong with changing the quoting prefix,
however I'd venture a guess that a lot more software expect
">Return-Path:" then the number of broken software written by
Microsoft (as hard as this may be to believe).
In short: more stuff is likely to break than would get fixe
Mitch (WebCob) writes:
Now I have a problem that maybe is related to enabling badmime? Not sure...
I think this goes beyond badmime and is just badmessage - incomplete mail
part of a bad spam engine? I get messages like these:
Received: from adsl-67-118-200-105.dsl.sktn01.pacbell.net ([67.118.200.
Jeff Potter writes:
Sam,
Is there any problem with changing the quoting of erroneous
"Return-Path" headers from ">Return-path:" to "X-Return-path"?
(Courier escapes incoming messages with stray "Return-path" headers.)
That is, change submit.c line 1302 to be:
1299:// Quote Re
John Bossert writes:
I want to strip the machine name for a specific user's email address,
effectively changing
From: [EMAIL PROTECTED] to
From: [EMAIL PROTECTED]
leaving all other addresses alone.
maildropfilter(5) says (and empirical data seems to confirm) that any
changes to the FROM variab
ok - maybe I opened myself up to this problem...
I set :
opt BOFHBADMIME=accept
because I have a large number of clients who regularly communicate with
people who use accents and so on in their email subjects - and despite being
against rfc, it works...
Now I have a problem that maybe is relate
Sam,
Is there any problem with changing the quoting of erroneous
"Return-Path" headers from ">Return-path:" to "X-Return-path"?
(Courier escapes incoming messages with stray "Return-path" headers.)
That is, change submit.c line 1302 to be:
1299:// Quote Return-Path:'s at this
I want to strip the machine name for a specific user's email address,
effectively changing
From: [EMAIL PROTECTED] to
From: [EMAIL PROTECTED]
leaving all other addresses alone.
maildropfilter(5) says (and empirical data seems to confirm) that any
changes to the FROM variable within a mailfilter
Jeff Gamsby wrote:
Hello,
I would like to only allow incoming mail from a certain host.
I'm not sure how to do this with courier.
I don't want courier to accept mail directly,
but to come from another machine. I want all mail to come and go
through a single machine, which has a virus wall and sp
Hello,
I would like to only allow incoming mail from a certain host.
I'm not sure how to do this with courier.
I don't want courier to accept mail directly,
but to come from another machine. I want all mail to come and go
through a single machine, which has a virus wall and spam filter. Is
this
Bill Williamson wrote:
contents of ~/.rpmmacros:
---
%_topdir/home/batkiwi/rpm
%_without_fax true
%_without_pgsql true
%_without_ldap true
Don't put those macros in your ".rpmmacros" file. Rather, build courier
with the --without arguments:
rpmbuild -ta --without fax --withou
Hi,
when certain mail servers connect or I want to send via tls/ssl with my
client I get this:
Apr 30 09:55:48 zer00 courieresmtpd: courieresmtpd: STARTTLS failed:
couriertls: accept: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong
version number
hm I did create an esmtpd.pem file.
whats w
13 matches
Mail list logo
