On 11/17/13 02:11, DJ Lucas wrote:
[root@server1 named]# postmap -q administra...@lucasit.com
ldap:/etc/postfix/alias-lucasit.com.cf
Administrator
And not even 10 seconds after I sent that!
--DJ
--
This message has been scanned for viruses and
dangerous content, and is believed to be
On 11/17/13 02:01, DJ Lucas wrote:
My apologies if this comes through more than once, but I've been unable
to send to the list...getting admin bounces..hopefully just a poor
subject line.
I cannot see what is probably an obvious error, but I've reduced the
config to as simple as I
ipv6" to main.cf.
--DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
UA to send an email or it's a
> server trying to deliver an email to port 25.
>
>
Correct.
> So i'm a little confused here.
>
>
Keep reading, stay the course, it'll get much easier very quickly.
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
On 02/15/2010 01:30 AM, Stan Hoeppner wrote:
> DJ Lucas put forth on 2/15/2010 1:22 AM:
>
>
>> http://www.experts-exchange.com/Security/Software_Firewalls/Enterprise_Firewalls/Cisco_PIX_Firewall/Q_24438893.html
>>
> Never post links to information that requires a
I always dump my configs. A
friendly reminder never hurts either way.
BTW, here is a better example than the Cisco docs (IMO), probably should
have just linked to there in the first place instead of the above
gibberish. Oh well.
http://www.experts-exchange.com/Security/Software_Firewalls/Enter
bijayant kumar wrote:
Bijayant Kumar
--- On Tue, 6/1/09, DJ Lucas wrote:
From: DJ Lucas
Subject: Re: Blocking Spam
To: "postfix"
Date: Tuesday, 6 January, 2009, 6:34 AM
bijayant kumar wrote:
Hello list,
Now a days we are getting lots of spam emails from our
own
)?
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
Noel Jones wrote:
DJ Lucas wrote:
Hi guys, I believe that I already have the answer to this pretty
basic setup, but I just wanted to do a quick sanity check.
I'm setting up a backup MX, and for one of the domains that it will
relay to, it should do no filtering whatsoever as there
uired? If not, then I'd just
as soon have one less directive in the case that, or rather when, this
server is no longer mine. I try to make the configuration as
transparent as possible for the next guy.
Thanks again for the detailed answers.
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
site that it is at, since it is not
resolvable from the outside world (backupmx.mailhost.local).
Additionally, I did not use relay_recipient_maps, is it still required
with the suggested configuration?
TIA
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is
esults. Do the same find again only substitute postfix
and postconf for main.cf in the above commands. Please post the output
if you are unsure how to utilize the results.
BTW, what is the host? I believe that you mentioned 'hardened 64'
previously???
-- DJ Lucas
--
This messa
tp://www.postfix.org/SASL_README.html#build_postfix or check with
your distribution/vendor for support if postfix was supplied to you in a
package.
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
.was about 1 to 1 the first couple of weeksthen b
stated catching more. When I reversed them, b is now flagging 8:1.
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
LuKreme wrote:
> On 2-Dec-2008, at 20:21, DJ Lucas wrote:
>> I can find absolutely no reason to inadvertently mislead, or worse,
>> intentionally deceive the recipient by forging the envelope sender's
>> address. In fact, the only reason I can see, is
>> to int
esn't,
then get rid of it.
I hope that came off as a constructive, alternative vantage point rather
than being argumentative. :-)
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
DJ Lucas wrote:
ehlo [EMAIL PROTECTED]
Coincidently, I just corrected a mis-configuration in my server as a
result of that example. Commented out helo restrictions a really long
time ago...they must not have been doing too much. :-)
-- DJ Lucas
--
This message has been scanned for viruses
ient address rejected: Greylisted,
see http://postgrey.schweikert.ch/help/lucasit.com.html
quit
221 2.0.0 Bye
Connection closed by foreign host.
[EMAIL PROTECTED] ~]#
HTH
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
DJ Lucas wrote:
This has been on by default in every piece of Cisco equipment that
I've messed with (admittedly not many), did you try and disable it yet?
Oops..I forgot to mention, on the newer models, the config item for the
'smtp fu**up protocol' is now /'inspect e
dentify as the connect
string doesn't show the name, it will instead show '*** 220 **
blah'. This has been on by default in every piece of Cisco equipment
that I've messed with (admittedly not many), did you try and disable it yet?
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
ve failure logs handy right now, bad password or no auth
does fail. If you'd like me to validate that statement, I'll be more
than happy to tomorrow day when I have a bit more time. I'm off, but
I'm always open to other suggestions on that config.
Thanks.
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
DJ Lucas wrote:
Good idea or bad?
Thanks for the responses. General consensus sounds not such a good
idea...I'll leave it behind.
Thanks again.
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
to get the 5xx, and
quit wasting time in the content filter for these few messages. Is
there any pitfalls aside from the possibility of blocking a good
address every now and then? If the message is from a real person, then
I'll hear about it.
-- DJ Lucas
--
This message has bee
ot;${tempfile3}"`
do
echo -e "${sender}\tREJECT" >> /etc/postfix/blacklist
done
TODO: insert some cleanup of the current list here too...
postmap /etc/postfix/blacklist
/usr/sbin/postfix reload
# End /etc/fcron.weekly/14-auto-blacklist
Good idea or bad?
Thanks.
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
24 matches
Mail list logo
