On 07 2 2005 at 6:46 pm -0500, Jay Lee wrote:
>When running ./configure, add the --without-ipv6 option. Even if your
>system is not configured with an IPv6 address, if that option is not
>specified, courier will log the ipv6 address.
Thanks. Both systems are running gentoo linux, which just rec
This vulnerability occurs when an E-mail contains a single 'CR' character
within the E-mail headers (as opposed to a 'CR' followed by an 'LF', which
is used to end a line in SMTP). Outlook can treat this as the end of the
headers, which would allow Outlook to see a virus that was embedded in the
h
Ben Kennedy said:
> On a potentially related note: I have two machines running courier. One
> of them logs like this:
>
> Feb 7 18:34:07 basil courieresmtpd: started,ip=[66.11.173.61]
>
> while the other like this:
>
> Feb 7 18:34:07 minty courieresmtpd: started,ip=[:::66.11.173.61]
>
> T
Ben Kennedy writes:
On 07 2 2005 at 6:36 pm -0500, Bill Taroli wrote:
I seem to recall this is a more generic couriertcpd option, not specific
to the logger. It is mentioned in the tcpd manpage.
Pardon me and thank you Bill, you're right. I was being shortsighted
when interpreting the contents of
On 07 2 2005 at 6:36 pm -0500, Bill Taroli wrote:
>I seem to recall this is a more generic couriertcpd option, not specific
>to the logger. It is mentioned in the tcpd manpage.
Pardon me and thank you Bill, you're right. I was being shortsighted
when interpreting the contents of that env var ju
I seem to recall this is a more generic couriertcpd option, not specific
to the logger. It is mentioned in the tcpd manpage.
Bill
Ben Kennedy wrote:
The courierlogger man page does not mention -noidentlookup as a valid
option. I've had this in my /etc/courier/esmtpd for quite some time now:
TCPD
The courierlogger man page does not mention -noidentlookup as a valid
option. I've had this in my /etc/courier/esmtpd for quite some time now:
TCPDOPTS="-stderrlogger=/usr/sbin/courierlogger -noidentlookup"
I think the advice came from this list, but I'm not sure. Is this
actually having no eff
From: Sam Varshavchik [mailto:[EMAIL PROTECTED]
>
> Bowie Bailey writes:
>
> >INFO: LOGOUT, user=bowieb, ip=[127.0.0.1], headers=0, body=0
> >INFO: LOGIN, user=confmdtest, ip=[127.0.0.1], protocol=SMAP1
> >INFO: LOGOUT, user=confmdtest, ip=[127.0.0.1], headers=0, body=0
> >make[1]
On Mon, 07 Feb 2005 18:33:14 +0100, Dark Night Rider wrote:
> the problem is in the
> authentication, a session of telnet localhost 110,
> when trying login, appears the following message in
> log "pop3d: LOGIN FAILED, [EMAIL PROTECTED],
> ip=[::1 ] "As I can diagnose and correct this error?
In
Hello list,
in http://sourceforge.net/mailarchive/message.php?msg_id=8647394 I
asked if it is possible to configure courier to try to deliver messages
over IPv6 first and only if that fails to use IPv4 instead.
In http://sourceforge.net/mailarchive/message.php?msg_id=8647396 Sam
described, that n
I have installed postfix, postgresql and to courier,
at the moment I can create mails accounts with virtual
domains and to receive (see in log
of/var/mail/maillog), the problem is in the
authentication, a session of telnet localhost 110,
when trying login, appears the following message in
log "pop3
Sander Holthaus - Orange XL writes:
My bad:
The same can be said on other private address-spaces. If I know that I
CANNOT reach any network using private address-spaces, why should I allow
someone to send mail whose MX-server(s) is/are in such an address space?
This can only be abused or point
My bad:
The same can be said on other private address-spaces. If I know that I
CANNOT reach any network using private address-spaces, why should I allow
someone to send mail whose MX-server(s) is/are in such an address space?
This can only be abused or point to configuration errors.
Kind Regards,
> Sander Holthaus wrote:
> > Would it be possible or would you consider making a bofh-option to
> > refuse such addresses?
>
> Why don't you do what Sam already suggested on 2005-01-19?
I did. And it is working, but it is not a permanent and foolproof sollution.
The problem is:
Sam Varshavchik
Sander Holthaus wrote:
> Would it be possible or would you consider making a bofh-option to
> refuse such addresses?
Why don't you do what Sam already suggested on 2005-01-19?
Sam Varshavchik wrote:
> I'm not aware of anything that technically prohibits such an MX record.
>
> But they can be eas
I was testing my anti-virus and mail-filters setup on
http://www.webmail.us/testvirus (previously testvirus.org). Apparently, they
still seem to use testvirus.org mail-addresses as the sender of these
addresses resulting in:
517-Domain does not exist: testvirus.org.
517 Invalid domain, see ftp://
> >>
> >> But they can be easily stopped. You must enable BOFHCHECKDNS, and
> >> put "badmx 127.0.0.1" in the bofh file.
> >> The man pages give more information.
> >
> > Thanks! Can I use whildcard in that expression, e.g. badmx
> 127.0.0.*
> > And
>
> No.
>
> > what about those domains th
Hi, I'm trying to compile new courier-authlib package on a vanilla Mandrake
10.0 (official) with command:
rpm -ta courier-authlib-0.53.tar.bz2
but compilation failed with:
.
Compiling gdbmobj3.c
Linking libgdbmobj.la
Linking libgdbmobjs.la
Compiling testgdbm.C
Linking testgdbm
rm -f libshgdbmob
18 matches
Mail list logo
