> ...
> FEATURE(local_procmail, `/usr/bin/procmail')
> MAILER(procmail)
> MAILER(local)
> ...
You don't need MAILER(procmail) if you are using FEATURE(local_procmail).
On the other hand, procmail as a local mailer will only read the user's
~/.procmailrc, *not* the system wide one. If you want to
> Outside the jail, it worked fine. inside the jail, sendto failed with a
> EINVAL error.
See:
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/26506
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubs
> i know, but what is happening is that all these applications
> (including sendmail and our ssh, for what matters)
> are broken in that they look for an record just for making
> a connection.
Can you try this patch for sendmail?
--- domain.c.orig Sat Aug 2 09:27:09 2003
+++ domain.c
pmc> While it is true that the said sendmail-option solves the problem
pmc> (if sendmail is new enough to understand it), I could nowhere find
pmc> information on how to fix the bug in the nameserver - that is,
pmc> in the nameserver that is packaged with FreeBSD 4.4 or 4.7.
FreeBSD's nameserver i
peterjeremy> One of my systems insists on trying to deliver mail directly
peterjeremy> to A record addresses rather than via MX records. I've tried
peterjeremy> comparing the configuration with a system that works sanely
peterjeremy> and can't find any explanation for this behaviour. Does this
pe
lists> Now just if I could get Sendmail to not do those dang identd checks
lists> all the time...
Add this to your .mc file:
define(`confTO_IDENT', `0')
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
dan> I am using ipf with "pass out from any to any/pass out from any to
dan> any".
Unfortunately, I use ipfw/ip6fw so I don't know if my guesses are correct.
That rule only appears to handle outbound connections (therefore allowing
the sendmail client to open an outbound connection to the local
dan> sm_gethostbyname(localhost, 28)... localhost
dan> alias: localhost.example.org
dan> addr: IPv6:::1
dan> makeconnection (localhost.example.org. [IPv6:::1].25 (28))
dan> makeconnection: fd=6
dan> *** delay occurs here.
dan> Connect failed (Operation timed out with localhost.example.org.);
da
I see two related problems with your DNS setup:
dan> dns_getcanonname: trying m20.example.org. (A)
dan> ;; res_querydomain(m20.example.org, , 1, 1)
dan> ;; res_query(m20.example.org., 1, 1)
dan> ;; res_mkquery(0, m20.example.org., 1, 1)
dan> ;; res_send()
dan> ;; ->>HEADER<<- opcode: QUERY, statu
dan> [dan@xeon:~] $ echo 'hi there' | mail -v [EMAIL PROTECTED]
dan> [EMAIL PROTECTED] Connecting to localhost.example.org. via
dan> relay...
dan>
dan> 220 xeon.example.org ESMTP Sendmail 8.12.5/8.12.5; Thu, 29 Aug 2002
dan> 08:32:14 -0400 (EDT)
That's either IDENT or DNS.
1. Does the same
pjklist> Funny thing about that, I actually created a /var/run/named directory
pjklist> for just the purpose of running named in a 'sandbox', chowned the
pjklist> directory bind:bind, and because I forgot to set the pid file path in
pjklist> named.conf, I see that it seems to write named.pid (o
dap> I suggest that the version of sendmail configs shipped with FreeBSD
dap> should default to having WorkAroundBroken set by default.
--- start of forwarded message (RFC 934 encapsulation) ---
From: Gregory Neil Shapiro <[EMAIL PROTECTED]>
Subject: cvs commit: src/
>> I suggest that the version of sendmail configs shipped with FreeBSD
>> should default to having WorkAroundBroken set by default.
ticso> That would break v6 support and only works for sendmail just to handle
ticso> broken nameservers.
This does not break IPv6 support. It does however poss
wkb> Apr 22 09:29:50 freebie sendmail[253]: File descriptors missing on startup:
stdout, stderr; Bad file descriptor
sendmail always checks it's first three fd's at startup to avoid the
problem that has just come to light in the FreeBSD security announcement.
This is what is logged if sendmail h
brent> I've been searching for info regarding mounting the same device
brent> to multiple locations in the filesystem, i.e...
brent> # mount /dev/ad0s1e /usr
brent> # mount -r /dev/ad0s1e /var/jail//usr
brent> # mount -r /dev/ad0s1e /var/jail//usr
I can't comment on this specifically but
evms> I wrote this a while ago, but, if anyone is interested, please
evms> take a look: this module implements a system call that takes
evms> a u_int_32t. This system call, named killjail, kills all processes
evms> which belong to the jail which uses that particular IP address.
evms> I included i
poige> Yes, I saw this info here:
poige> http://www.sendmail.org/m4/features.html#relay_mail_frombut most
poige> valuable part of my question was about the purpose or the idea behind
poige> this, cause it's not too clear to me why allowing relayi
poige> I noticed that some mailers (sendmail, postfix) in case they allow
poige> relayingforsomedomain.zonealsoallowrelayingfor
poige> subdomain-of.somedomain.zone.
poige> I can accept this as reasonable behavior but would like to know how to
poige> deny it! :) Also I
18 matches
Mail list logo
