Soeren D. Schulze wrote:
Hello,
I found the following patch:
http://da.andaka.org/Doku/imapspamfilter.html
To describe it briefly, it automatically trains the SPAM filter when the
user moves messages to a SPAM or HAM folder.
First, what do you think about this in principal?
I see
Soeren D. Schulze wrote:
Alessandro Vesely wrote:
Soeren D. Schulze wrote:
I found the following patch:
http://da.andaka.org/Doku/imapspamfilter.html
To describe it briefly, it automatically trains the SPAM filter when
the user moves messages to a SPAM or HAM folder.
[...]
In addition
mouss wrote:
3- never block your own users with methods designed for inbound mail.
This includes DNSBLs, spamassassin rules, ... etc.
One exception is when you have methods that can determine that mail
is being sent by automated malaware. Viruses, e.g., are dropped from
external relays and
mouss wrote:
Alessandro Vesely wrote:
mouss wrote:
3- never block your own users with methods designed for inbound mail.
This includes DNSBLs, spamassassin rules, ... etc.
One exception is when you have methods that can determine that mail
is being sent by automated malaware. Viruses
Michelle Konzack wrote:
[...] taking the sources from UNSTABLE and building it under STABLE
works for me since ages. (but you must choose very carefull WHICH
packages you backport, specialy now with glibc 2.5/2.6 which can hit
you heavily)
As an alternative, I used equiv once and installed a
Mike Horwath wrote:
On Jul 25, 2007, at 7:49 AM, Pawel Tecza wrote:
Hi Sam,
Do you intend to release a next stable version of your Courier
under the terms of the GPLv3 or you still stay under the GPLv2?
Ack, I sure hope not.
To hope not is a generically negative way of thinking.
After
mattias jonsson wrote:
yes exactly
how to add mailboxes on courier mail server
i use ubuntu server
I use debian, and compile courier from sources. Doesn't ubuntu provide scripts?
I don't add users very often, hence I prefer doing it manually from the console.
The scripts I attach use the
Sam Varshavchik wrote:
Lindsay Haisley writes:
Sam, what about making this a user-configurable setting
in /etc/courier/esmtpd or some other config file?
I'll look into it.
There's an old patch here
[courier-users] Problem (and patch for) 534 Message header size, or ... error
From: Jarle
Matthias Wimmer wrote:
The better solution would be to configure courier to not pass mails to
the filters, that are received from clients.
Thus, any client will be able to spread a virus as soon as it catches it.
Sam Varshavchik wrote:
Gordon Messmer writes:
Sam, you've mentioned before that refactoring the code to run filters
after rewriting the message would be difficult, but wouldn't you just
need to move the run_filter block of code later in
SubmitFile::MessageEnd? That would give filters
Bernd Wurst wrote:
Am Mittwoch, 3. Oktober 2007 schrieb Jean-Christophe Boggio:
I would like to reject mails when To: match a regex
(for example, I receive several mails addressed to
[EMAIL PROTECTED], the number part being random).
I know these are always spams.
Is there a way to do this ?
M Core wrote:
I think the question is - HOW do I CC or TO an email message to a
different mail directory? I suspect this is the problem with TO
/home/username/Maildir.
(Note that TO or CC does work if it is in the user's directory that the
email is being sent to e.g. TO $HOME/Maildir, or
M Core wrote:
I think the question is - HOW do I CC or TO an email message to a
different mail directory? I suspect this is the problem with TO
/home/username/Maildir.
(Note that TO or CC does work if it is in the user's directory that the
email is being sent to e.g. TO $HOME/Maildir, or
Enda Cronnolly wrote:
Sam Varshavchik wrote:
There are several fixed limits: a maximum size of 5000 characters per
line,
and 100,000 bytes maximum total size of all headers. These limits are
fixed
I don't see more than 200 characters per line in the 1,600bytes of headers
for the
Gordan Bobic wrote:
But now that you mentioned it - is there a way to make Courier make an
additional check?
e.g. it receives a message:
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Normally, this is not too plausible to check if from is for a non-locally
hosted domain, but if from
Gordan Bobic wrote:
On Fri, 19 Oct 2007, Alessandro Vesely wrote:
Gordan Bobic wrote:
But now that you mentioned it - is there a way to make Courier make an
additional check?
e.g. it receives a message:
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Normally, this is not too plausible
Johnny C. Lam wrote:
Gordan Bobic wrote:
It would also be worth checking if MAIL FROM: is the same as From: and
RCPT TO: is the same as To:. Can anyone think of why these would ever
be inconsistent in a valid email?
The first argument to MAIL FROM: is the mailbox where errors and DSNs
Gordan Bobic wrote:
Leigh S. Jones, KR6X wrote:
No one has mentioned that it's necessary to wait until
the possible spammer identifies his target to know
whether the target has him whitelisted.
Gordan wrote:
Whitelists aren't really practicaly on big setups. You need to block a
lot before
, and end users only see the latter. It
would be enough to routinely rewrite, say,
Return-Path: [EMAIL PROTECTED]
From: Alessandro Vesely [EMAIL PROTECTED]
into
Return-Path: [EMAIL PROTECTED]
From: lists.sourceforge.net for Alessandro Vesely [EMAIL PROTECTED]
whenever the domain parts
Gordon Messmer wrote:
Gordan Bobic wrote:
And at the end of the day, SPF just isn't all that effective anyway.
When you can reduce your spam influx by 2-3 orders of magnitude using
more sensible and cheaper methods, what is the point of bothering with
more questionable methods?
[EMAIL PROTECTED] wrote:
Just out of interest, does SPF break with multi-homed senders as well, or
are multiple SPF records a valid (and more importantly, commonly supported
by MTAs) configuration?
They're perfectly valid, of course. If you look at my SPF record
you'll see why I've never had
Bernd Wurst wrote:
Hi.
Am Montag, 5. November 2007 schrieb Alessandro Vesely:
SPF is fairly effective at what it was designed to do.
I'm not sure what you mean by fairly. It is not effective.
It was designed to be widely adopted and it is not.
SPF can only get spread if the forwarding
Bernd Wurst wrote:
If one of my customers
forwards mail to his other account at some other company, the destination
server rejects my message because the sender's address is still set to the
original sender (that sent the message to me) and I am not listed as a valid
sender for the
Bernd Wurst wrote:
Hallo.
Am Samstag, 10. November 2007 schrieb Sam Varshavchik:
... and reverse DNS of its IP address.
To be complete:
Courier does not check reverse lookup AFAIK and I would not recommand
checking
this.
that is the same recommendation that RFC2821 makes:
An
niclas wrote:
smtp2-1.tng.de has address 213.178.66.95
95.66.178.213.in-addr.arpa domain name pointer smtp2-1.tng.de.
smtp2.tng.de has address 213.178.64.96
smtp2.tng.de has address 213.178.64.95
Host 96.64.178.213.in-addr.arpa not found: 3(NXDOMAIN)
Host 95.64.178.213.in-addr.arpa not
niclas wrote:
as BOFHCHECKHELO is 1 per default, courier-mta is not an RFC-compliant
mail-server.
I found no bofh file in courier's default install.
Did you install from the source tarball or download a configured package?
Mark Constable wrote:
On Thursday 03 January 2008 22:00:15 Jay Lee wrote:
[...] Last I heard, GnuTLS is significantly slower at
encryption than OpenSSL.
I haven't been able to find a recent benchmark, despite the following assertion:
GnuTLS has been benchmarked against OpenSSL and GnuTLS is
Sam Varshavchik wrote:
Alessandro Vesely writes:
TLS is the alive encryption standard that SSL was. TLS proposes new
features, such as the Server Name Indication (SNI) extension, that
enables virtual secure servers
http://tools.ietf.org/html/rfc4366#section-3.1
(See it at work on a web
Mark Constable wrote:
If the MTA's local delivery agent handled the encryption,
using a public key supplied by and from the users homedir,
it would eliminate any other user on the system from
interferring with the messages. Sure, Google Mail engineers
and hacked LDA's could intercept messages
Mark Constable wrote:
Jan 25 10:33:19 mail courieresmtpd: error,
relay=:::216.82.241.83,
from=[EMAIL PROTECTED]:
517 SPF fail [EMAIL PROTECTED]:
Address does not pass the Sender Policy Framework
# dig +short txt x.com.au
x.com.au. TXT v=spf1 +a:mx2.x.com.au
Mark Constable wrote:
On 25 Jan 2008 16:29, Alessandro Vesely wrote:
What was the HELO name they used? Perhaps you can
retrieve the newmsg log entry for that message.
I couldn't find a related message to this particular SPF
fail log entry but, separate issue, wouldn't the message
Mark Constable wrote:
On 25 Jan 2008 16:29, Alessandro Vesely wrote:
The include:spf.messagelabs.com actually evaluates
spf.messagelabs.com, which happens to have a TXT rec
v=spf1 exists:%{ir}.nets.messagelabs.com
In the macro, i stands for IP, r for reverse, thus
that becomes exists
Bertrand Presles wrote:
I'd like to change the names of the default folders generated at maildir
creation (which are by default Draft, Junk, Sent, Templates,
Trash).
Ok. See the documentation for your mail client.
I know that I can do it using my client... But I want it to be DEFAULT
We all know how SPF breaks forwarding. Some even say that forwarding has
been broken since rfc1123 deprecated source routing in the envelope return
path, in 1989. Anyway, it is broken now. That's why I'm asking to this
list for any comments, thoughts, and insights that may lead to fix
Gordon Messmer wrote:
Alessandro Vesely wrote:
More or less, that's it. The Anti-Spam Research Group might have been a
more suitable list for this topic, but I'd rather seek practical advice. Any?
Look at SRS?
http://www.openspf.org/SRS
SRS solves a number of cases for large
Francisco Corella wrote:
I'm trying to use .courier to forward mail to an
archival mailbox, but I can't make it work. The
forwarding fails with a 513 Relaying denied
message in /var/log/maillog.
It looks as if the receiving host (machine 3) does not accept messages for
relaying. That is,
Arturo 'Buanzo' Busleiman wrote:
Johnny C. Lam wrote:
| Could you expand on the description of the problem you're trying to
| solve, or give an example? Your subject line asks one thing, but your
| message body asks something else.
Of course. Sorry I was not clear enough. I want some users
Francisco Corella wrote:
OK, let me restate the first configuration, which shows the problem
most clearly. Machine 1 receives messages for someuser, and I want to
use /home/someuser/.courier in machine 1 to forward them to machine 2
and machine 3.
If I put the following two lines in
Jeff Jansen wrote:
Mário Gamito [EMAIL PROTECTED] wrote on 2008-Feb-12:
What I was told to do (*sigh*) is to authenticate, create, etc. the
users in a MS SQL SERVER.
Any chance you can have a slight typo and report that you
successfully got courier working with MY SQL SERVER as instructed?
Sam Varshavchik wrote:
I just enabled the Wiki page on Sourceforge, and I'll add a link to it
from www.courier-mta.org a little bit later. Looks like the default
settings are wide open, anyone can edit pages in the public portion of
the wiki, so have fun:
niclas wrote:
By default courier-mta block MX with bad return address which is a good
thing :-)
this in fact breaks RFC
I don't think there is an RFC specifying that a server must accept
whatever crap. http://tools.ietf.org/html/rfc2821#section-3.3 just
says that If the [return-path]
rupert wrote:
ISDIR=0
# Let's check if /home/vmail/domain.tld/username exists
`if [ -d $VHOME/$USERDOMAIN/$ACCOUNT ];then ISDIR=1; fi`
Setting a variable in a child process has no effect. Try
`test -d $VHOME/$USERDOMAIN/$ACCOUNT`
if (!$RETURNCODE)
{
ISDIR=1;
}
Jay Lee wrote:
On Mon, Mar 3, 2008 at 9:06 AM, Leigh S. Jones, KR6X [EMAIL PROTECTED]
wrote:
First of all, the whitelisting and manual blacklisting is done by adding IP
blocks to a file in the directory /etc/courier/smtpaccess.
If not using webadmin, I'd advise using different files for
This was obviously intended to the list
Original Message
Subject:Re: [courier-users] how to whitelist rbl blacklisted e-mail
Date: Mon, 03 Mar 2008 17:35:33 -0200
From: Enrique Verdes [EMAIL PROTECTED]
To: Alessandro Vesely [EMAIL PROTECTED]
Alessandro Vesely
rupert wrote:
On Mon, Mar 3, 2008 at 8:04 PM, Alessandro Vesely [EMAIL PROTECTED] wrote:
rupert wrote:
ISDIR=0
# Let's check if /home/vmail/domain.tld/username exists
`if [ -d $VHOME/$USERDOMAIN/$ACCOUNT ];then ISDIR=1; fi`
Setting a variable in a child process has no effect. Try
rupert wrote:
On Tue, Mar 4, 2008 at 10:05 AM, Alessandro Vesely [EMAIL PROTECTED] wrote:
/etc/maildroprc(12): ISDIR=0
maildrop: Filtering through `if [ -d $VHOME/$USERDOMAIN/$ACCOUNT
];then ISDIR=1; fi`
In order to get results from a subprocess one can
* check its return code
rupert wrote:
Now I only would like postfix to execute the query for the quota which
ist located in the user table,
I heard postfix has add-ons for quota, but I have no idea how they
work. Perhaps someone else, possibly on one of the postfix mailing lists?
Sam Varshavchik wrote:
Jimmy Ott writes:
if ( !/^X-Spam-Flag: YES/:h )
{
cc [EMAIL PROTECTED]
}
[.. rearranged ..]
mail1.ourcompany.org[xxx.xxx.xxx.xxx] said: 550 5.7.1 local domain
specified from non-local IP (in reply to end of DATA command))
Courier has no role
Bernd Wurst wrote:
One is to
remove the (seemingly) very outdated and unsupported AC_PROG_SYSCONFTOOL
Macro from configure.in. When googling for this macro, I only find people
complaining about broken courier compiles, so this should be removed, IMHO.
I googled for that and got
Bernd Wurst wrote:
On Thursday 06 March 2008, Alessandro Vesely wrote:
[AC_PROG_SYSCONFTOOL]
http://www.courier-mta.org/sysconftool/sysconftool.1.html
So the question is: What's the way to got that this tool (it's in the courier
distribution) gets used? Simply running autoconf complains
Hi Bernd,
Bernd Wurst wrote:
Here again, Gentoo patches some stuff that IMHO could be done upstream.
Attached is a patch file that replaces pam_stack.so with PAM's include
feature. This is the way to go with current PAM versions (Don't remember the
version it was introduced). PAM 0.99 and
tovis wrote:
I can send/receive receive faxes - front end is apache2 and squirrelmail.
For now I have stucked on faxmail. I was deleted the first line from
default configuration file /etc/courier/faxrc (rw^ . 1), and check for
faxmail, as [EMAIL PROTECTED], but result was an SMTP 513 error.
tovis wrote:
After some probes I have managed to send a simple email from user1 to
user2 resides on the same host (interesting sendmail is accept
[EMAIL PROTECTED] address, what wasn't accepted from fetchmail).
The command line is probably more user friendly on than port 25.
I have
formed
tovis wrote:
1. How can I makemime header From: with characters different from
ASCII,
I mean national characters iso-8859-2 or utf-8?
When I'm use makemime ... -a From: Kökény Tüske
[EMAIL PROTECTED]
I have funny chacters as a result, instead of ö,é,ü receiving a mail.
Those
Bernd Wurst wrote:
On Thursday 13 March 2008, Alessandro Vesely wrote:
[Headers as utf-8]
All these standards are changing, but it will take decades before
everyone agrees on a worldwide charset (probably klingon, if not utf-8.)
Well, I do not know of any mail application that has memorable
tovis wrote:
What should be the right domain name for local delivery, in case of no
real domain?
You may try and configure localhost as a real TLD and machine name in
a local view of your local DNS server. I'm not sure it's the easiest
way, though.
Could some one figure out what is wrong or
Authmysql needs to be revamped. I'd propose to accept any local-part
that can be the target of an RCPT TO command (also for imap/pop
logins.) Apparently, that implies not only allowing single quotes, but
also quoted string. Thus, one could patch authmysqllib.c so that,
e.g., Roger's
/2006/jan/addslashes-versus-mysql-real-escape-string
I'd use mysql_real_escape_string(), if available. See
http://bugs.mysql.com/bug.php?id=10214
quote who=Alessandro Vesely
Authmysql needs to be revamped. I'd propose to accept any local-part
that can be the target of an RCPT TO command (also
tovis wrote:
What should be the right domain name for local delivery, in case of no
real domain?
You may try and configure localhost as a real TLD and machine name in
a local view of your local DNS server. I'm not sure it's the easiest
way, though.
I have no DNS server, I would rather do
Leigh S. Jones, KR6X ha scritto:
Thus, the message comes to you ostensibly from the sender, but the
IP address that the message is received from is that of the list relay.
Thus it appears to the Courier SPF-checking mechanism that the
sender has been aliased by a spammer.
Since you have
Arturo 'Buanzo' Busleiman wrote:
Alessandro Vesely wrote:
| IMHO there is no reason to discard softfail (~all) while allowing
| neutral (?all). I cannot find google in http://spf-all.com/
So what would your recommendation be, then? How would you modify this
settings?
opt BOFHSPFHELO
Gordon Messmer wrote:
Alessandro Vesely wrote:
I'd use mysql_real_escape_string(), if available. See
http://bugs.mysql.com/bug.php?id=10214
No, you should never use any escape function on user input if it can be
helped. Prepared statements are the most convenient, fastest, and most
kemas henry wrote:
I look in courier-authlib configuration, I can't find where to
differentiate pop3 login and imap login. seems to me they all use the
same method.
Is there any other way to achieve this?
Checkout LDAP_AUXOPTIONS in your authldaprc file.
Finally, I managed to get my hands on that code :-)
Gordon Messmer wrote:
Alessandro Vesely wrote:
Indeed, to use prepared statements would be itself a good reason to review
that code. It was added in MySQL 4.1.2, the auth code still has a conditional
part for older MySQL versions. Should I
Sam Varshavchik wrote:
Alessandro Vesely writes:
* use mysql escape function also in a number of other places; the
MySQL team took years to get it straight...
Well, I don't think they got it right. There's no bounds checking in
mysql_real_escape_string! The documentation claims you
Gordon Messmer wrote:
Alessandro Vesely wrote:
On the other hand, we cannot guarantee that prepared statements work
in *all* cases.
Why not?
Some forms of queries don't work. E.g. you cannot have parameters
markers on bot sides of an comparison, as in WHERE ? = ?, for
mysql_stmt_prepare
To recap,
Matt Comer wrote: (Sat, 15 Mar 2008 09:04:20 -0400 (EDT))
quote who=Alessandro Vesely
Authmysql needs to be revamped. I'd propose to accept any local-part
that can be the target of an RCPT TO command
[context log, with localpart=info's]
authd: SQL query: SELECT email, , clear, uid
Gordon Messmer wrote:
Peter Burden wrote:
It may be worth using the MySQL function mysql_real_escape_string() which
should handle anything that could cause problems. Programmatically this
would be much less effort than using prepared statements which require a
considerable amount of coding.
Sam Varshavchik wrote:
Set up a subdomain zone in one of your domains, and use the script to
populate the zone file, then set up Courier to use it as a DNS blacklist.
Fine. (Some suggest sub-subdomains, as backscatter.dnsbl.example.com.)
Q: is it publicly accessible, and mentioned in the
Joe Laffey wrote:
opt BOFHSPFHARDERROR=fail
[...]
BOFHSPFHARDERROR=fail to remove the default softfail in that variable.
Sounds slightly nonsensical, as a ~all doesn't have a decent chance
to be amended within the few days that a temporary failure can keep a
given message in the remote
Joe Laffey wrote:
On Wed, 30 Apr 2008, Alessandro Vesely wrote:
Joe Laffey wrote:
opt BOFHSPFHARDERROR=fail
[...]
BOFHSPFHARDERROR=fail to remove the default softfail in that variable.
Sounds slightly nonsensical, as a ~all doesn't have a decent chance
to be amended within the few days
Sam Varshavchik wrote:
Alessandro Vesely writes:
Sam Varshavchik wrote:
Alessandro Vesely writes:
* use mysql escape function also in a number of other places; the
MySQL team took years to get it straight...
Well, I don't think they got it right. There's no bounds checking
Leon de Jager wrote:
I am having trouble with a courier-imap/courier-authlib (mysql)
(courier-imap-4.3.1.tar.bz2 and courier-authlib-0.60.4.tar.bz2).
May 16 07:52:41 mailserver authdaemond: SQL query: SELECT username,
clear, user_id, group_id, home, maildir, quota,
I don't recall this subject having been discussed on this list.
Anyway, the expired draft is apparently coming back.
Original Message
Subject: BATV pseudo-Last Call
Date: Fri, 16 May 2008 21:59:33 -0700
From: Dave Crocker [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
Sam Varshavchik wrote:
I think that, in general, this is a good idea, but it should not be
necessary to present this in such a convoluted manner. Furthermore I do
not see even a need to have any standard for this. A given mail server
can start generating time-expired bounce addresses that
Michelle Konzack wrote:
It seems that I must shutdonw courier-mta for the benefit
of exim which i realy do not like after along period. :-(
What kind of control does exim allow on in/out messages?
On a different level, you might control output messages rates by
configuring traffic control
Sam Varshavchik wrote:
mouss writes:
Sam Varshavchik wrote:
[snip]
That's unrealistic. the user-part in MAIL FROM has a length
limitation which goes against secure signatures. the other question
is why would this be needed (I mean, is it really worth the
trouble?)...
isn't
[EMAIL
Lindsay Haisley wrote:
I just had a serious security breach here.
[...]
I have a very few customers who require authenticated SMTP. All others
use their ISPs' SMTP servers. On top of this, customers are able to set
their own mailbox passwords, and some don't understand about proper
I wrote on Sat, 15 Mar 2008 15:10:11 +0100:
Matt Comer wrote:
I agree, but with one possible caveat: most RDBMSs allow you to configure
the quoting behavior away from the default if you want. I am not a mysql
expert, but if mysql allows the quote character (default \ for mysql)
then authmysql
Owen O' Shaughnessy wrote:
My customer receives daily mailings from an advisor, but receives
corrupted characters in the message.
The character set being used is iso-8859-1
When the message is received by courier it is sent using content
transfer encoding 7 bit.
When the message is
Sam Varshavchik writes:
Paweł Tęcza writes:
So, my question is: why don't you set SENDER='[EMAIL PROTECTED]'
or SENDER='[EMAIL PROTECTED]' or something similar if SENDER
variable is empty?
In that case, if user's forward is broken, then Courier is trying
to deliver a DSN message to a
Sam Varshavchik wrote:
Alessandro Vesely writes:
sensible information, coordinating mail filters, et cetera. Besides
properly setting the Return-Path, a policy might need to mandate a
specific outgoing IP, a smart relay, some kind of authorization token,
or other features.
Would
A series of patches are being released after Dan Kaminsky announced a
possible DNS poisoning technique. See
http://news.cnet.com/8301-10789_3-9985815-57.html
http://www.us-cert.gov/cas/techalerts/TA08-190B.html
http://tools.ietf.org/html/draft-ietf-dnsext-forgery-resilience
Courier users
Sam Varshavchik wrote:
• Switch to versionless shared libraries.
Out of curiosity, what's the rationale behind that decision?
--
-
Sponsored by: SourceForge.net Community Choice
Dani Crisan wrote:
Hello,
I have just installed Postfix+Courier+Mysql using this:
http://flurdy.com/docs/postfix/#data
First a have created in Mysql 2 users (they are also system users), and
then created another user:
INSERT INTO users (id,name,maildir,clear) VALUES ('[EMAIL
Dani Crisan wrote:
Hello,
Jul 18 16:02:35 mail authdaemond: authmysql: trying this module
Jul 18 16:02:35 mail authdaemond: SQL query: SELECT id, crypt, , uid,
gid, home, concat(home,'/',maildir), , name, FROM users WHERE id =
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] AND
Sam Varshavchik wrote:
Michelle Konzack writes:
Since Bug# are autogenerated by the BTS software, spamer could push any
Bug# into my BTS, I like to install some software/script or whatever
which block numbers which do not exist in the BTS.
(Why can't you just authorize the BTS sender?)
Bowie Bailey wrote:
Jay Lee wrote:
Is this functionally any different from an alias? (besides using
maildrop for forwarding)
Technically yes since Courier accepts the message and starts delivery
instructions instead of just re-queueing it to the alias. So for
instance, if he runs spam
Bruce Cheng wrote:
Dear all,
I currently use Postf 2.5.1, Cyrus SASL 2.1.22, courier-imap 4.4.1,
Authlib 0.61 and Maildrop 2.04 version in Centos 5.2 x86_64, it runs
well.
I have the question on DEFAULT_DOMAIN of Authlib settings. We can
log in as 'user' without domains to COURIER-IMAP
Bruce Cheng wrote:
2008/8/1 Alessandro Vesely [EMAIL PROTECTED]:
I have the question on DEFAULT_DOMAIN of Authlib settings. We can
log in as 'user' without domains to COURIER-IMAP SERVER, but we can
not log in as 'user' without domains to SASL authentication, we have
to log in as '[EMAIL
Aidas Kasparas wrote:
Gordon Messmer wrote:
Sam Varshavchik wrote:
You can't. Alias lookup happens immediately upon the receipt of the
recipient's address. Since the alias address is no longer needed, it
does not get stored anywhere.
It does get stored in the control file, doesn't it?
Gordon Messmer wrote:
Alessandro Vesely wrote:
Gordon used to maintain a pretty-received patch to do exactly that.
Who, me? I don't remember any such patch.
My sloppy memory obviously can't cope with virtual companionships :-(
My apologies for letting that loose...
For the record
Mark Constable ha scritto:
I'm somewhat stunned this has not been more of a noticable problem for
anyone using SPF... and that I haven't noticed it myself until now even
though we've been using SPF for the past year.
Well, it has been the source *many* discussions, and many consider this to
be
Mark Constable wrote:
That state of affairs is obviously wrong...
Absolutely. A sidebar at http://www.openspf.org/SRS says...
[...] if you do check SPF, and you wish to
reject messages that fail SPF, then you must do one of two things
to avoid rejecting legitimate mail:
. whitelist
After compiling --with-gnutls, the thunderbird imap client
prompts for a certificate required by the server. After
recompiling with the attached patch this does not happen.
--- tcpd/libcouriergnutls.original.c2008-07-12 20:40:45.0 +0200
+++ tcpd/libcouriergnutls.c 2008-08-24
Mark Constable wrote:
. whitelist forwarder IP addresses
. use forwarders that rewrite the sender
It is also possible to do both of them. Rather than patching an SRS
implementation into Courier, I'd be out to enhance authlib in order to
allow easier management of whitelisting: [...]
Sam Varshavchik wrote:
Mail forwarding is not a random event. Mail forwarding occurs,
presumably, at the ultimate recipient's request. It is the ultimate
recipient that places the forwarding in place, so that the recipient's
mail gets forwarded to a different destination.
That forwarding
Julian Mehnle wrote:
Alessandro Vesely wrote:
Rewriting the sender's address currently works, but is wrong for
backup MXes. Isn't there room for designing a better solution?
One should always be able to fully trust one's backup MXes, not only for
_that_ reason but also because you want
Sam Varshavchik ha scritto:
Alessandro Vesely writes:
Currently, the only way that one can concede forwarding is by IP address.
That's beside the point.
It is a problem. What if the remote host could log in?
The bottom line is this. Your email address is
[EMAIL PROTECTED] If you need
J. Pablo Fernández wrote:
Hello,
Is it possible to make Courier accept relay for mails sent from
localhost? If so, how?
Programs using sendmail can do it with no worries, with a Return-Path
that defaults to [EMAIL PROTECTED] If you use virtual domains
you're probably better off setting up
201 - 300 of 648 matches
Mail list logo
