ressed to exampledomainX.com and archive in a particular
> folder...
virtual_alias_domains =
virtual_alias_maps = pcre:$config_directory/blackhole.pcre
blackhole.pcre:
/^(@exampledomain1\.com)$/ $1
/^(@exampledomain2\.com)$/ $1
/^(@exampledomain3\.com)$/ $1
/./ catch...@
n.spamhaus.org, but I might be adding
spameatingmonkey. Most important advice regarding DNSBLs is to be
familiar with their policies and aware of their status. Given the
dominance of ancient syntax in your restrictions, I wouldn't be
surprised to see some dead lists among your maps_rbl_domains. :)
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
On Sun, Apr 18, 2010 at 10:38:46PM -0500, Noel Jones wrote:
> On 4/18/2010 9:56 PM, /dev/rob0 wrote:
>>
>>> reject_unauth_pipelining,
>>
>> Might catch some zombies.
>
> Note that with older postfix (postfix < 2.6 IIRC)
> reject_unauth_pipelini
thenticating users, same as
with Zen. Precede this lookup with your permit_* restrictions for
relaying users (and move submission off of port 25, if applicable.)
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
) is very simple. The
BIND 9 ARM chapter 3 has an example. This is something that might
even work out-of-the-box, no named.conf(5) at all.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
going to connect again
and keep trying. Penny wise, pound foolish.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
BOSE="on"
> DEFAULT=~/Mail/inbox
> #DEFAULT=/var/mail/fetchmail
> PMDIR=$HOME=~/.procmail
> #INCLUDERC=$PMDIR/spam.rc
>
> I don't want to rewrite headers through formail or procmail. This
> is a home setup, and fetchmail must just go get the mail and pass
> it to procmail.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
bragging.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ocalhost
Among many. I would probably choose #3.
Please do also check the BASIC_CONFIGURATION_README and ensure that
everything mentioned in there is set as you need (or is fine with
default settings.)
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
2
al on hosting
from a provider which is infested with spammers, you might have
delivery issues. You might be a "human shield".
Look up your IP address on various DNSBLs, including but not limited
to: Spamhaus, SORBS, Spamcop, Spameatingmonkey, and Barracuda. My
guess is that you'
ies first. I've seen
hundreds of things that I didn't understand, and when I get curious
about it, THAT is what I think: "I don't understand this." Try to
protect your sanity by not jumping to this conclusion so easily.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
the
following two. A message might arrive via sendmail or via the
network, but not both.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
I might as
> well just add it there.
Sure, this is an improvement over what you had, but it seems strange
to me that mynetworks would be changing frequently. Perhaps SASL AUTH
is a better solution overall?
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
the O.P. has followed some guide or HOWTO for
virtual(8) mailbox delivery without understanding that .forward
files are not supported for virtual accounts.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ring of cleanup(8). As you were told,
what you want to do is already possible by means of external content
filters and/or milters.
I believe you will find Wietse's answer to your wish here:
http://www.postfix.org/CONTENT_INSPECTION_README.html
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
e real domain names to diagnose properly. Please also include
logs if you think you need to post again.
> -- postfinger output --
[snip]
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
k:
>
> /^From:.ret@/REJECT unsolicited email
Even if adjusted to match the actual string, I don't think this is
safe. I can imagine there are legitimate senders with a localpart
"ret". Maybe someone's initials, or a nickname ...
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
olize a
> popular webmail service.
"Example" has been set aside for examples in every top-level domain,
such as example.com, example.net, et c. Newdom.com and
externaldom.com are real domains, albeit evidently just
cybersquatters.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ect
> from localhost[127.0.0.1]
"Trusted connection" means it is verified. There is no reject_warning
among what you posted.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
t? A quick Google search didn't find it.
How would that work? The client would have to tell the hostname or
domain name wanted before the STARTTLS?
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
pecial DNS
view with a different MX value for the domain in question. If
this does not make sense to you, disregard it for now, but it
might make sense later.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
/usr/sbin/postconf -d soft_bounce
soft_bounce = no
Does some distributor change this default?
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ctivated, by default, no certificate verification is done at all.
Consult your distributor's package documentation if they have set
different defaults.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
the third-party delivery agents directly support .forward files.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
otte
bingham=${number}$street
Thus "$bingham" is "7701wyandotte" in this silly example. For
real-world Postfixated examples, continue reading in your
documentation.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
:
file:///usr/doc/postfix/html/postconf.5.html#mydestination
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
is as likely to find the wrong version of a document. If a
seeker ends up at http://www.postfix.org/documentation.html , all's
well, but not necessarily so if they find someone's old, non-updated
mirror.
--
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
tion to make upgrade?
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
/SMTPD_ACCESS_README.html
and $html_directory/access.5.html
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
to acting upon a single header.
> P.S. Hiding of sender IP makes more difficult troubleshooting
> of malware incidents an so on.
Absolutely. Received: headers are your friend.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
s (I think), there might be more or other
> places.
This was wrong. Nothing posted indicated an issue in the OP's
installation of Postfix.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
w what actually was returned?
The log shows what was found in the header_checks(5) map. It is
presumed that a user who activates soft_bounce understands what
effect it will have.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
EADME.html#mail
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
red.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
d? As far as the SMTP
>>> greeting banner?
>>
>> Have you already established that this is, in fact, the issue ?
>>
> No, I am basing this assumption on your comment, "It is obviously
> the latter you have an issue with :)"
I think you missed a bit of sarcasm. No, the banner is not causing
problems, it merely pointed out to us one of the potential problems
you're facing.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
; A postfix policy server doesn't have access to the mail body. I
> guess that's a job for a milter|smtpd_proxy_filter|content_filter.
Or, perhaps a better option, implement this in a delivery agent.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
nformation.
Another thing for you to consider is that Postfix might be too big
and complex for your needs. There are other null client software
projects which might make more sense for you.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
nder "<>". I want to
> forward all by bounce to another host for some processing first, so
> have the idea of creating this 'bounce' postfix instance. Any
> thought?
Yes. I think you are solving the wrong problem. Why do you have so
many bounces that this would matter?
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
sport(5) table, but so far that's not what you have talked about.
If that's what you want, Google has examples of that on this list's
archives.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
d a "political dispute" on another SPAM-L descendent list,
spam-l.com. That list is still functioning, but I cannot personally
recommend it, for reasons which would be off-topic here.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
setting.
> Otherwise, specify .domain.tld (note the initial dot) in
> order to match subdomains.
>
> See the last sentence.
See the one before that. :) What is your setting of
parent_domain_matches_subdomains?
Repeat after me: "Oops, sorry Wietse." :)
-
On Thu, Nov 04, 2010 at 03:36:30AM +0100, Vincent Lefevre wrote:
> On 2010-11-03 21:21:24 -0500, /dev/rob0 wrote:
> > On Thu, Nov 04, 2010 at 03:08:03AM +0100, Vincent Lefevre wrote:
> > > On 2010-11-03 22:00:21 -0400, Wietse Venema wrote:
> > > > Vincent Lefevre:
>
isted in parent_domain_matches_subdomains.
"
The string list is taken from my own postconf -d, are there others
which might be used in some cases? I guess all of those except
smtpd_access_maps would be hyperlinked; and maybe that could link to
access.5.html.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
o host your own email. Running a mail
server is not a trivial task.
Google is your friend. In recent months there has been discussion
here regarding possible implementations of DNSWL for Postfix, and
that discussion also mentioned alternatives (policy servers.)
--
Offlist mail to this addre
tings for those configuration items.
[1] That might sound like a criticism of the default for
mydestination, but it is not. The default is as good as
possible, but human supervision is necessary to set up a MTA.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
otocols? Is SMTP the only one with a
problem? Can you ssh to/from the client?
You can add the client IP to debug_peer_list to get verbose logs,
which might provide a hint at what's happening. Or, try looking at
tools such as tcpdump, which can show information about what's
happening at lower levels.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
emonstrated above,
that the default smtpd_delay_reject means smtpd_sender_restrictions
won't be evaluated until the RCPT TO: command.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
is still
> be needed in my configuration? Can someone help this lost soul out?
You usually do not need to specify default values in your main.cf at
all. "setting_name = default_value_for_setting_name" is the same as
omitting it altogether.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ing of
smtpd_delay_reject was done for good reasons. You're not going to
gain much (if anything) from this change, and you will lose some
potentially important logging. Please review:
http://www.postfix.org/postconf.5.html#smtpd_delay_reject
--
Offlist mail to this address is dis
ve been examples to do this very thing posted before. No,
your requirement is not so unusual nor special.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
do as Viktor suggested, to restrict this "easy solution"
to your submission clients ONLY. Your fix will haunt you later.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ou got from your primary account logged?
If nothing is logged, then nothing arrived. There is nothing in the
thread here with which we can help you. Perhaps you have a question
for the support desk at your provider, gmail?
--
Offlist mail to this address is discarded unless
"/
ob.
But indeed, widespread ineptitude is how things got to be this
bad in the first place. Your ISP needs to outsource if they are
unable to hire good postmasters.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
On Thu, Nov 25, 2010 at 06:34:03AM -0600, /dev/rob0 wrote:
> And "dig outmx.site. mx" yields this:
> outmx.site. IN 600 10 goodrelay.1.example.net.
> outmx.site. IN 600 10 goodrelay.2.example.net.
> ...
Coffee deprivation, sorry. More like this:
outm
les
with their .new brethren.
You CAN do this Alan's way, but again, I recommend against it. For
this, I abandon the Slackware packaging system and use Postfix's own
methods. It's simple enough to remove if you ever feel the need. So
far I haven't.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
come message or DEBUG_README.html#mail which
would have told you to include relevant logs plus "postconf -n".
Without that, there is no way to guess what happened.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
On Fri, Nov 26, 2010 at 09:35:06AM +0100, Mauro wrote:
> On 25 November 2010 14:11, /dev/rob0 wrote:
> > On Thu, Nov 25, 2010 at 01:54:49PM +0100, Mauro wrote:
> >> I have a file: recipient_checks with mym...@example.com REJECT
> >> and the corresponding hashed r
pend_at_myorigin
http://www.postfix.org/BASIC_CONFIGURATION_README.html
Assuming (we can ONLY assume since there was no postconf -n provided
with the post) that the file "virtual" is virtual_alias_maps, you
should have something like this for local delivery instead:
kathy.lampard@@domain.com.auka...@localhost
with "localhost, localhost.$mydomain" included in your setting of
$mydestination.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
course
were much harder than they are now.
You have to decide whether the pain of upgrading exceeds the pain of
not upgrading.
Personally I would recommend the former, using a SRPM from Simon
Mudd: http://postfix.wl0.org/ ... it's not that painful.
--
Offlist mail to this address
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
oning that the
most significant log entries were omitted from this post. Of highest
interest are the logging which shows the mail originally coming into
Postfix. We'd want to see all logging pertaining to BF7ACFD8063, as
well as the initial connection, if it arrived via smtpd(8).
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ed, unset it:
relay_domains =
The $mydestination default setting was for backward compatibility.
Combined with the default of parent_domain_matches_subdomains, this
can cause problems, because all subdomains of mydestination domains
are now relay_domains.
--
Offlist mail to this address is discarde
mplex messages possibly including the rejected tokens, a
policy service is the way to go.
http://www.postfix.org/SMTPD_POLICY_README.html
> And would a feature request for this be appreciated?
>
> Having the return-message link to a maintained webpage providing
> information/help on how to resolve the issue might actually be
> useful.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
flist. You decide. You're all mail
administrators, so I assume you know how to override a Reply-To: in
your MUA. :) Please also observe the .sig below.)
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
On Wed, Jan 19, 2011 at 04:15:48PM +0100, Ralf Hildebrandt wrote:
> * /dev/rob0 :
> > On Tue, Jan 11, 2011 at 09:46:42PM +0100, Ralf Hildebrandt wrote:
> > > smtpd_reject_footer = Contact postmaster at charite.de for assistance
> > > caused a SIGNIFICANT inc
ality of Internet email.
Re: Mark's suggestion about the Q&A gatekeeper: thanks, I will look
into that.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ress is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
cks.
But indeed, this gives me an idea: rather than a contact form, I
might try a form which generates a limited-use non-blocked address.
The next hurdle: how to present it in a way such that the end user
can see/use it, and yet protect it from harvesting bots?
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
the default. Why?
> transport_maps = hash:/etc/postfix/maps/transport_maps
As per above, might not be needed.
> virtual_alias_maps = hash:/etc/postfix/maps/virtual_alias_maps,
> hash:/var/lib/mailman/data/virtual-mailman
If the list domain is in mydestination, there is no need for any
virtual aliasing of Mailman addresses.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
hem, one for sending & receiving. Let me know the full
> directory path & filename of the whitelist files
Again I think Brian covered that. These links might help:
http://www.postfix.org/SMTPD_ACCESS_README.html
http://jimsun.linxnet.com/misc/postfix-anti-UCE.txt
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ow weight, but
I'm not sure it will do much good there. I guess it should probably
be called from check_sender_access in smtpd restrictions.
That said, some manual log scanning has showed that it has pushed a
few results over my postscreen_dnsbl_threshold, and those did indeed
look spammy, so
_checks,
> > > check_sender_access hash:/etc/postfix/sender_checks,
> > > check_client_access hash:/etc/postfix/client_checks,
> > > check_client_access pcre:/etc/postfix/client_checks.pcre,
> > > reject_rbl_client zen.spamhaus.org,
> > > permit
> > >
> > > smtpd_data_restrictions =
> > > reject_unauth_pipelining,
> > > permit
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
; is merely to set a default value
for smtpd_sasl_type. Third, how Postfix is or is not compiled has no
bearing at all on how Dovecot SASL works.
Documented here:
http://www.postfix.org/SASL_README.html#build_dovecot
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
27;s where RHSBL makes most sense, in smtpd.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ure that I've had empty lookup maps in the past.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
.
If you really do want to beat this dead horse, it would be well
within the topicality of a list I help run:
http://spammers.dontlike.us/
We have a lot of good folks there (and I know Stan will agree!) who
can and will teach you the folly of direct-to-MX mail from dynamic
and/or tain
ocking everything!
Will your forwarder do something like this to you?
Will they notify you in advance of if if they do?
Will they warn you before Spamhaus starts blocking them?
Would they even know or care that they were blocked?
My mail is too important to be left to chance.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
re on this mailing list,
using Google searches of the list archive. I think that would be a
better method of evaluating him, than by taking his joke literally.
> If there are "significant differences that are not Debian related"
> Stefan certainly has had reasons to add them.
And I'm sure he'd be willing to discuss those reasons.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
hould an upstream project have to support the unwise
decisions of downstream packagers?
[1] Ubuntu included in this context.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
share logs and spam samples for these? Thanks.
IME with greylisting, which admittedly was not very recent, delay
time length was insignficant. A 5-second delay was as good as 5
minutes. Some bots retried, others did not.
--
Offlist mail to this address is discarded unless
"/dev/r
feature patch.
This opens up a whole new realm of possible *_dammit feature
requests. Maybe we can get that FORCEFUL_README draft ready by
the end of March?
Hmmm, some of the reject_* features could become eject_* ...
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
reen has documentation:
http://www.postfix.org/POSTSCREEN_README.html
http://www.postfix.org/postscreen.8.html
Perhaps those can point you in the right direction?
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ks Wietse, and also thanks to those early adopters
who provided the feedback on postscreen.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
> incoming attempt something like "Sorry, i have a temporary problem.
> Try to connect later".
Among other options, this would work:
http://www.postfix.org/postconf.5.html#soft_bounce
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
he
case of relay_domains, not recommended.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
postconf.5.html#canonical_maps
http://www./postfix.org/canonical.5.html
After having tried something, if it fails, use this as a guide before
asking again:
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
do ?
You were on the right track, but apparently missed this:
http://www.postfix.org/TLS_README.html#client_smtps
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
name.
If you want to serve different domains and have each one on unique
hostnames, set up different instances on different IP addresses,
where each IP address has FCrDNS as desired.
That's ridiculous and unnecessary, but for some reason also a very
popular idea.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
d them
2. Those who do understand them won't be willing to dig through
all the noise.
Remove the -v here.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
age has another unwise default,
which is to use global forwarders rather than recursion. Use
caution, and consult Debian and ISC documentation, if you decide
to run your own nameserver for the Postfix machine.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
he
issue as you have described. You want per-client (mynetworks) or per-
user (SASL AUTH) relaying.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
see:
http://www.postfix.org/DEBUG_README.html#mail
before asking again. Don't mung domain names if you want help with
mail routing issues.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
er a WAG here that you're using a prepackaged Postfix, and didn't
see the packager's README. I'll further guess that the packager
unwisely changed the default of non-chrooted Postfix.
http://www.postfix.org/DEBUG_README.html#no_chroot
--
Offlist mail to this addres
e posting again. As the advanced.html page says, it can be very
difficult to identify the source of the spam.
Also it's not really on topic here. If you'll indulge a shameless
self-promotion, this would be quite on topic on this list, which I
co-manage:
http://spammers.dontlike.us/
We do have a CBL representative who subscribes and sometimes posts.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
. See
http://www.postfix.org/DATABASE_README.html for map types overview.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
the mail users are not needing shell or other access such
as CIFS/SMB or FTP, what was the point in keeping "home directories
clean"?
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ering that the
client needs HA, I think it would be an excellent idea to run your own
nameservers. Do the easy things to improve performance before you try
the difficult ones.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
gt; I recommend using the "localhost"
> zone (or the "invalid" zone) for custom MX records. As in the
> "your.domain" example, but with "localhost" for "your.domain".
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
101 - 200 of 1152 matches
Mail list logo