re
after. I think the bottom line is that you're trying to make a MTA do
things it was not meant to do.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
internal submission by IP
address or port. For either approach you need a separate smtpd(8)
listener defined in master.cf. There's a commented example for
submission (port 587) in your master.cf already.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ent domain. If
it really has to be nailed down, use restriction classes, so that a
check_recipient_access lookup (for the one recipient domain) invokes
a check_sender_access (or other, client is best if you can use it)
whitelist. The full scoop is available at:
http://www.postfix.org/RESTR
h subdomains." When is
eventually? :)
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
map -q "lookup-key-string" maptype:mapname
When the desired result is returned, it will work.
> But then the users complained that the mail wasn't being delivered to
> their IMAP mailbox, and it was being forwarded to the blackberry /
> vodafone address around ten times!
Con
his is not a Postfix issue at all, sounds like POP3. Consult the
documentation for and logs from your POP3/IMAP server software.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
fix documentation is not going to cover
advanced subjects in other software, such as a mysql backend in
Dovecot. For that, see:
http://wiki.dovecot.org/
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
obsolete, and superceded by
> smtpd_tls_security_level.
Oops, perhaps the OP needed smtp_tls_security_level to replace this?
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
class. You accept mail for valid recipients, reject for
others.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
u have good reason to do so.
(Okay, we CAN guess that a process limit of 10 might cause problems
like this, disregard what I said at first. :) )
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
iple source files into a single DB?
Another suggestion, try adding CDB support and using that, see
CDB_README.html .
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
se tables in to one?
Look at that server's local copy of postconf(5) documentation for
information specific it its version of Postfix. If it honors the
$virtual_alias_maps setting at all, $virtual_maps is deprecated.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
and skip the transport_maps.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
tings.
Jeroen would say, if your postconf -n is more than 30 lines, you are
either an expert, or you have done it all wrong. :)
Consider starting over with a simple config.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
>
> Is it a bug in the documentation?
No, only in your understanding. Consider the difference between a
"maildir" and a "maildir file". A maildir is the directory structure
of maildir/{cur,new.tmp}/ which contains individual files, each
containing exactly one message.
ocked using zen.spamhaus.org;
> >
> > Q2: Is a "blocked using" entry written for each DNSBL for which
> > there is a hit? If not, how is it determined which DNSBL will
> > get credit?
>
> The first DNSBL that responds.
Could it be changed to the highest-scored DNSBL?
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
garding the original question in this thread, I would have
recommended MX records of equal priority, and not CNAMEs. This
doesn't seem like a necessary use for a CNAME.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
A mail
server is not really one of them. It wouldn't hurt to have dnsmasq
running on the Postfix host, but a recursive resolver like named is
best. Yes, dnsmasq will cache lookups, and cache hits will improve
your performance substantially.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
tfwd.
>
> Must admit im a little lost here. (sorry)... if anyone can assist
> with an example so we can see how it works?
http://postfwd.org/quick.html
http://postfwd.org/doc.html
http://www.postfix.org/SMTPD_POLICY_README.html
As to how to implement this in postfwd, this is not the rig
ing on content,
other options are available, including restriction classes and
policy servers:
http://www.postfix.org/RESTRICTION_CLASS_README.html
http://www.postfix.org/SMTPD_POLICY_README.html
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
er credentials.
If you really have a need or desire to run your own MTA, I suggest
these fine links as a starting point:
http://www.postfix.org/BASIC_CONFIGURATION_README.html
http://www.postfix.org/SOHO_README.html
If you just want email to work with your Frontier address, I would
suggest staying
on": main.cf and
master.cf. The others are probably the ones which are there for
information and reference. (YMMV, if you have included files of
similar names in your configuration.)
(I'm familiar with the package build script that Rich is talking
about.)
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ADME.html document.
HTML links will be found on www.postfix.org and in your own local
html_directory copy.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ble hacks you are trying to do. We don't know what
you're really wanting to accomplish.
I suspect you need one of these three:
1. A more recent Postfix
2. A different MTA altogether
3. A more reasonable goal
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
/VIRTUAL_README.html
http://www.postfix.org/ADDRESS_CLASS_README.html#virtual_mailbox_class
http://www.postfix.org/MYSQL_README.html
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
My setup is
> Postfix
> Mailscanner
Bad idea, Mailscanner, and not supported on this list.
> Clamav
> Spamassasin
> Mailwatch
And you don't seem to understand much about how all the parts fit
together. Mail admin is very difficult!
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
t list.dsbl.org,
DSBL has been gone for almost three years now.
> reject_rbl_client bl.spamcop.net,
> reject_rbl_client cbl.abuseat.org,
CBL is included in Zen. The second lookup against CBL data is
unlikely to block anything, and it IS more load on CBL's
infrastructure.
> reject
ormation. Was this
rejected session on your main port 25 smtpd(8), or might it have
arrived on a different port with -o overrides?
Show master.cf with comments removed, and the final_sender_access
file.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
through sed(1) if desired,
or just save them in a year/month/day directory tree, such that the
year would be part of the pathname.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
rver to do the lookup and return "DISCARD".
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
anks a lot. It works.
For the record and your own information, your assumption in the OP
was wrong: smtp_* settings have nothing to do with smtpd(8), the
Postfix SMTP server. Those settings are for smtp(8), the client.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
commands". Since an attempt to make an SMTP
> connection to such a system is probably in error, a server returning
>a 554 response on connection opening SHOULD provide enough
>information in the reply text to facilitate debugging of the sending
>system.
>
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
_tls_security_level = may
> smtpd_tls_session_cache_database =
> btree:/var/lib/postfix/smtpd_tls_session_cache
> tls_random_source = dev:/dev/urandom
> transport_maps = hash:/etc/postfix/transport
What's in there, and why?
I'd suggest that you tear it down and start over using this:
http://www.postfix.org/BASIC_CONFIGURATION_README.html
and add on as needed, such as the SASL and TLS.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
CLASS_README.html#relay_domain_class
(second time today I have posted that link :) )
> i'm adding my postconf output, but i think my problem is more
> fundamental.
Yikes! The list guidelines ask for "postconf -n" *not* full postconf
output! I didn't read that.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
554 clientspam
> 192.168.1.100 OK
> 192.168 554 Take a hike!
> 64.1.16.3 OK
This is safe enough as you have it here. However, you should review
this document:
http://www.postfix.org/SMTPD_ACCESS_README.html#danger
(the whole thing, but parti
from source, even correctly done,
interferes with OS features like this "alternatives" thing. It is
well worth your while to spend some time learning how properly to
manage your OS before undertaking mail admin.
With Redhat-based systems, I suggest using Simon Mudd's SRPMs for a
rec
e forward and reverse DNS do not match? I
Yes.
> thought I've seen cases where forward and reverse did not match but
> it still showed a hostname for the client.
No.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
his address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
K mail is getting delivered, for now anyway.
[1] http://www.spamhaus.org/faq/answers.lasso?section=Spamhaus%20XBL
and the equivalent PBL page
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ouldn't last email be forwarded to [10.0.0.202]:52345,since it is
> specified in /etc/postfix/sender_relay ?
No. It is rejected as described in "ADDRESS_CLASS_README.html".
What are you trying to do with all this? Start out with a clear
description of the real-world goal you want to achieve. Also, review
"DEBUG_README.html#mail" before following up. These pages are in your
own html_directory or online at www.postfix.org.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
unix - - n - - error
> > retry unix - - n - - error
> > discard unix - - n - - discard
> > local unix - n n - - local
> > virtual unix - n n - - virtual
> > lmtp unix - - n - - lmtp
> > anvil unix - - n - 1 anvil
> > scacheunix - - n - 1 scache
> > maildrop unix - n n - - pipe
> > flags=ODRhu user=popmail:popmail argv=/usr/bin/maildrop -w 90 -d
> > ${user}@${nexthop}
> >${extension} ${recipient} ${user} ${nexthop}
> > cyrus unix - n n - - pipe
> > user=cyrus argv=/cyrus/bin/deliver -e -r ${sender} -m ${extension}
> > ${user}
> > old-cyrus unix - n n - - pipe
> > flags=R user=cyrus argv=/cyrus/bin/deliver -e -m ${extension} ${user}
> >
> > -- mechanisms on localhost --
> > 250-AUTH PLAIN LOGIN
> > 250-AUTH=PLAIN LOGIN
> >
> >
> > -- end of saslfinger output --
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
es?)
http://www.postfix.org/DEBUG_README.html#mail
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ch as gmail.com. Good luck.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
il-gw0-f54.google.com (mail-gw0-f54.google.com
> [74.125.83.54]) by tuna.theoceanwindow-bv.com (Postfix) with ESMTP
mail-iy0-f182.google.com[209.85.210.182] is not the same as
mail-gw0-f54.google.com[74.125.83.54]
> id 11AB65C23 for ; Sat, 14 May 2011 22:37:41
> -0400 (EDT)"
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
umentation I tend to believe Sophos does provide a patched
> Postfix.
It could be a restriction class.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
50 DSN
quit
221 2.0.0 Bye
Connection closed by foreign host.
rob0@cardinal:~$ date
Tue May 31 13:07:21 UTC 2011
This connection should have been logged, about a minute or two before
13:07:21 UTC. If not
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
list as a check_recipient_access lookup.
http://www.postfix.org/SMTPD_ACCESS_README.html
http://www.postfix.org/access.5.html
http://www.postfix.org/postconf.5.html#check_recipient_access
If further help is needed:
http://www.postfix.org/DEBUG_README.html#mail
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ing it.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
petent mail admins. Those mistakes are exacerbating the spam
problem.
> But this, as far as I understood, is off-topic, so I'll discuss
> offlist. :)
As Stan mentioned (thanks Stan), this would be welcome on SDLU:
http://spammers.dontlike.us/
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
problem and goal will not help.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ADME?
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
Internet for help
in keeping the old install running, but when things go wrong, as they
surely will, the costs will skyrocket in ways not yet imagined.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
flist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
On Sun, Jun 05, 2011 at 09:21:21AM -0400, Wietse Venema wrote:
> /dev/rob0:
> > On Fri, Jun 03, 2011 at 01:09:28PM -0400, Wietse Venema wrote:
> > > postscreen_whitelist_interfaces matters only for clients that
> > > are not yet whitelisted (or that have expired).
On Sun, Jun 05, 2011 at 10:21:38AM -0400, Wietse Venema wrote:
> /dev/rob0:
> > Jun 5 01:50:46 cardinal postfix/postscreen[15628]: CONNECT from
> > [174.37.3.121]:33695 to [216.23.247.74]:25
> > Jun 5 01:50:52 cardinal postfix/postscreen[15628]: PASS OLD
> > [174.37
I
hope the presentation is of interest.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
use
courier-imap for that. Questions regarding courier-imap should be
directed to an appropriate forum. (This one is not.)
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
to authenticate to MSexChange.
Have your .forward invoke sendmail(1) with your gmail address as the
sender. Then maybe a transport_maps entry to force your gmail address
to use the gmail submission service.
Did I miss something? Does that not achieve the original goal?
--
Offlist mail to t
te the gmail webmail interface. I know spammers have done it,
because stuff like that is about the only spam that gets through to
my mailboxes.
Good luck.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
does not
need to replace all the antispam functionality of smtpd.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
s address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
at the end of my list of
> recipient restrictions (after reject_unauth_destination).
Or better yet, just move on. :) You are not an open relay unless you
deliberately set it up that way.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
em.
Frankly, what you are doing strikes me as similar (if you'll forgive
an idiom) to closing the barn door after the horse has gone. If your
apache account has been compromised, you have a horse on the loose.
Go chase that horse! Postfix is a lesser problem.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
@gmail.com
Note the problem as mentioned above, but otherwise, it works.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
/www.postfix.org/SMTPD_POLICY_README.html
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
On Sun, Jul 03, 2011 at 01:44:26AM +0200, Jeroen wrote:
> On 3 July 2011 01:07, /dev/rob0 wrote:
> >> f...@bar.com > forward to foo...@gmail.com
> >
> > Same-envelope forwarding to external sites is also quite likely
> > to become a source of problems for you.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
addresses.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
On Thu, Jul 07, 2011 at 06:44:49AM -0500, Stan Hoeppner wrote:
> On 7/7/2011 5:58 AM, /dev/rob0 wrote:
> > The anchors at both ends mean you are safe. You start with ^ and
> > end with $, so nothing else can sneak in between those.
> >
> > A simpler expression t
On Thu, Jul 07, 2011 at 08:24:42AM -0500, Noel Jones wrote:
> On 7/7/2011 7:48 AM, /dev/rob0 wrote:
> > On Thu, Jul 07, 2011 at 06:44:49AM -0500, Stan Hoeppner wrote:
> >> On 7/7/2011 5:58 AM, /dev/rob0 wrote:
> >>> The anchors at both ends mean you are safe. You st
ng POP/IMAP-before-SMTP system,
but definitely do not recommend that any new site should implement
that kludge. Let it go away!
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
o measure improvements.
>
> I'm sure many have been down this road before - care to shove a n00b
> in the right direction?
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
d each have this
feature.
If as I suspect, your system has malware or other such intrusion, a
policy service will not stop these. The most common successful attack
vectors are by means of bugs in poorly-coded PHP webware, or by brute
force SSH attack bots.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
d need to write a sendmail wrapper for that
Could this be done with a non_smtpd_milters application which reads
the Received: header to determine the UID?
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
that you've been compromised, and that these spams came
through local sendmail submission. Hope not, because it will be a
mess to clean up!
One thing you should consider doing NOW is to stop Postfix, because
the more spam you relay, the more damage is done to your reputation
and del
uthorized_xforward_hosts = 0.0.0.0/0, [::/0]
These can be preceded by exclusions. For details, see:
http://www.postfix.org/postconf.5.html#smtpd_authorized_xforward_hosts
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
On Sun, Aug 07, 2011 at 02:10:35PM -0500, Noel Jones wrote:
> On 8/7/2011 12:36 PM, /dev/rob0 wrote:
> > On Sun, Aug 07, 2011 at 08:03:47AM -0700, Jack Bates wrote:
> >> On Fri, Aug 5, 2011 at 2:10 PM, Noel Jones
> >> wrote:
> >>> On 8/5/2011 3:26 PM, Jack
On Sun, Aug 07, 2011 at 03:59:10PM -0500, Noel Jones wrote:
> On 8/7/2011 3:52 PM, /dev/rob0 wrote:
> > On Sun, Aug 07, 2011 at 02:10:35PM -0500, Noel Jones wrote:
> >> # main.cf
> >> smtpd_authorized_xforward_hosts = ip.of.upstream.postfix
> >
> > Apparent
not tell the client that I was using any of these more
aggressive DNSBLs. I have a postscreen_dnsbl_reply_map returning
"multiple DNS-based blocklists" for sites other than Spamhaus.)
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
guess is possible until you
do.
http://www.postfix.org/DEBUG_README.html#mail
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
On Mon, Aug 08, 2011 at 01:46:08PM -0500, /dev/rob0 wrote:
> On Mon, Aug 08, 2011 at 12:29:38PM -0600, Stephen Atkins wrote:
> > I would like to block absolutely everything to or from this
> > domain no matter what. I found a couple of examples but they
> > don't s
e single smtp(8) log line you shared does not include the sender
address, so it was not adequate. I'm just guessing based on other
information you provided. You should show the ENTIRE non-verbose
logging of a message from when it enters Postfix until final
disposition thereof.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
think most gmail
outbounds are in my postscreen whitelist. I am quite certain that
nothing from gmail was lost.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
in test is already failed, I see no benefit in allowing a client
to proceed (whitelist it if you want it.)
Otherwise I think it's a good idea. I'd set my pass-boundary at -2.
I'm only giving those dnswl.org .0's a -1 score.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
his can be done within a single instance using a different
port (587 has been set aside for that purpose) or IP address; or if
greater distinctions are desired, such as a different content_filter
or header_checks(5), another instance might be best.
--
Offlist mail to this address is discarded un
bmission
instance is unable to route outside spcified domains, with a
"default_transport=error:No external mail" setting. Permitted
destinations could be defined via transport_maps or address class
definitions.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
mounting the
> active queue as a tmpfs or ramdisk if you're system can support
> that VM-wise. But, that can be dangerous, since you will lose
> mail if your system goes down while a message is in a volatile
> storage mount.
I wouldn't do it this way, for the very re
available via a policy service, and
it seems to have improved my spam blocking somewhat. I have aggressive
DNSBLs, which I'd never trust for reject_rbl_client, set with low
scores.
Granted, my pre-postscreen spam blocking was pretty good. I'm sure
we're only looking at a fraction of a percent here. Every little bit
helps.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
non-technical people, such as user and alias
management. A person who does not understand a Unix CLI probably also
does not understand email, and for that person to be tinkering with
Postfix settings is a bad idea.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
domain names can make it impossible to solve mail
routing problems. And if you must mung, do not use a real domain as
an example, use example.{com,net,org,...}.
4. I have a personal limit of one pastebin URL per problem. If you are
seeking free help on the Internet, make it easy for the helpers.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
.wpbl.infoDOWN
> psbl.surriel.com
>
> i get a loot 550 service not available entries in log
> and sender gets error messages.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
is address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
19 hours after an attempt
> to send mail because the Linux kernel I'm using would finally
> consider the TCP stream dead); 2) if for some reason it's not my
> own SSH process listening on port , I'm in trouble.
>
>
> Arguably this should be fixed with authenticated submission (port
> 587), possibly with certificates; but it has not happened in a
> year although people promised to look into it.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
require a non-
default setting of inet_interfaces, I would do as P@rick suggested,
and bind an alternate port, and do as Noel suggested, and redirect
port 25 from the client to this alternate port.
If it's Linux, see the REDIRECT and DNAT targets in the iptables(8)
man page. The conntrack
nally from a third party (Jeff Posluns ?)
> and are fairly old, I have added some of my own checks but the
> basic files are originals. If these checks are still worthwhile
> are there more up to date files, and if so where might they be
> found?
--
Offlist mail to this address is discard
mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
-
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
On Sunday 25 September 2011 10:51:05 John Hinton wrote:
> On 9/25/2011 10:56 AM, /dev/rob0 wrote:
> > On Sunday 25 September 2011 07:27:59 Phill Edwards wrote:
> >>> Where did you look? A source install of Postfix using default
> >>> paths places an /etc/p
301 - 400 of 1152 matches
Mail list logo
