Julian Mehnle wrote:
In the old times of the Internet where a.com (everybody) could send a
message and claim it to come from x.com, forwarders would have to take no
responsibility for what domains are used as the sender addresses of the
mail they forward. As a result, everybody could simply
Alessandro Vesely [EMAIL PROTECTED] wrote:
It is still not clear why one would rewrite senders. SPF should work
if everybody takes the burden of declaring what are the mail servers
they use.
Suppose I have an account with the CPAN project and thus have the e-mail
address [EMAIL PROTECTED].
Although courier has the ability to detect loops (by checking the number
of headers) I'd like to see a little enhancement to the logic. I'd like
courier to detect when it is sending mail to itself, abort delivery
(still leave it in the queue though) and emit an error.
The reason why I want
Hi,
The code from courier 0.47 contains a broken auth_ldap_enumerate
function which would never work properly for more than one user (which
kinda defeats the purpose of the function...).
The attached patch fixes the code.
Regards,
Rob
--
rob holland - [ [EMAIL PROTECTED] ]
[ 5251 4FAC D684
On Friday 19 November 2004 01:24 am, Zach White wrote:
I would still like to know why courier is attempting to do DNS
lookups when there is a smarthost. This would make courier completely
worthless in one of my environments. Not every mail server has a
connection to the internet, and it's not
Please help me find the simple thing I am overlooking. I'm going crazy.
No matter what I do, maildrop always returns 0x06. When mail comes to the
server, it of course fills the deferred queue, but if I cat a message on the
command line and pipe that to maildrop it returns 0x06, the .mailfilter
An off-list reply led me to maildrop -V (level). This is an output of V 4.
There seemed to be no more information in V 10, so I added this. Right
after the message evaluates (either true or false) it returns 0x06. I don't
see why...
/home/shanford/Maildir/.System.SpamAlert/cur/$cat 1 |
Is there any known incompatibility between Maildrop-1.5.3 and Sparc64 or
other 64-bit architectures? Or OpenBSD 3.6?
I have torn the mailing list archives apart and cannot tell why I'm still
having this problem:
http://marc.theaimsgroup.com/?l=courier-usersm=110087545019920w=2
Maildrop seems to
Hi,
is there already any debian pkg for courier-analog out anywhere? Also
having courier 0.47 as a debian pkg would be very nice!
Thanks for your attention!
Peter
---
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD
Hanford, Seth writes:
maildrop: signal 0x06
You'll have to look up what's signal 6 on OpenBSD. On Linux it's SIGABRT,
which obviously is not what it is on OpenBSD.
Once you know what the signal is, then you can try to figure out why you're
getting it.
pgptXJjcq3o4E.pgp
Description: PGP
Sam Varshavchik wrote:
Julian Mehnle writes:
Alessandro Vesely [EMAIL PROTECTED] wrote:
It is still not clear why one would rewrite senders. SPF should work
if everybody takes the burden of declaring what are the mail servers
they use.
Suppose I have an account with the CPAN project and thus have
Is there a simple way that I could trigger a SQL update upon a successful
login? With our current system, we update the database to log the last
successful POP3/IMAP auth into the mail server. Is there a clever way that
I could use the current Courier Authlib framework to do the same thing?
I recently migrated my mail server (different boxes, old box was
running freebsd 4.10 and courier 0.45.2 and current server runs
freebsd 5.3 and courier 0.45.4) mail client is squirrelmail.
I observe the following errors 1. When trying to sendmails
2.
On Nov 12, 2004, at 4:15 PM PST, [EMAIL PROTECTED] wrote:
From: Sam Varshavchik [EMAIL PROTECTED]
Date: November 12, 2004 4:15:58 PM PST
To: [EMAIL PROTECTED]
Subject: Re: [courier-users] Can Courier call external mailers for
certain outgoing addresses?
Greg Earle writes:
overloaded central
14 matches
Mail list logo
