Cukunbaba:
> What happens if postfix don't get answer from one of rbl lists?
> Is there some default timeout and can we changed it?
DNS lookups are made by system library routines. On some systems
their retry and timeout behavior is described in the resolver(5)
manpage.
For a mail flow overview,
Thank you for the response and the info. I didn't notise that.
I have one more question.
With our particular configuration of postfix when smtp client sends mail,
before mail is put in incoming queue are all those checks:
smtpd_delay_reject = yes
smtpd_helo_required = yes
smtpd_helo_restrictions
Armando Soto Baeza skrev den 2014-05-14 23:32:
Please, remove my address from this list.
you get forwarded mails from maillist with another email address of
yours, and you are not asking the list owner now to get help, but
spamming a thread on a maillist archive, well done
I have sent mes
El 14/05/14 16:22, Noel Jones escribió:
> On 5/14/2014 10:50 AM, Benny Pedersen wrote:
>> Marius Gologan skrev den 2014-05-14 17:21:
>>> This should help you discover most (not all) IP ranges in cidr
>>> format:
>>> host -t txt outlook.com | tr " " '\n' | awk '/\./' | sed
>>> "s/include:\|ip4://g"
On 5/14/2014 10:50 AM, Benny Pedersen wrote:
> Marius Gologan skrev den 2014-05-14 17:21:
>> This should help you discover most (not all) IP ranges in cidr
>> format:
>> host -t txt outlook.com | tr " " '\n' | awk '/\./' | sed
>> "s/include:\|ip4://g" | sort -u | grep -i "[a-z]" | while read
>> rec
On Wed, May 14, 2014 at 11:32:05AM -0700, Cukunbaba wrote:
> May 13 12:54:43 smtp1 postfix/smtp[7957]: 234C4300B95:
> to=, relay=127.0.0.1[127.0.0.1]:10024, delay=4674,
> delays=4334/295/0/45, dsn=2.0.0, status=sent (250 2.0.0 from
> MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: que
Hi,
I have mail server with postfix + gnarwl + amavisd-new + clamd +
spamassassin + ldap
I have experienced yesterday huge active queue grow (about 4000 messages in
2h).
This is example of log for one of those messages:
[root@smtp ~]# cat /var/log/maillog|grep 234C4300B95
May 13 11:36:49 smtp1 p
D'Arcy J.M. Cain skrev den 2014-05-14 16:59:
It looks like hotmail is on two DNSBLs and postscreen is blocking
them. I would like to offer my users a way to whitelist individual
addresses but it looks like I can only whitelist CIDR blocks. Is
that the case or do I have another option?
dig hot
On Wed, 14 May 2014 17:44:37 +0200
Benny Pedersen wrote:
> dig hotmail.com txt
>
> use same whitelist.cidr from txt record
You mean whitelist it? That's not the issue. I see no point in
whitelisting someone *because* they send a lot of spam. I don't think
that the answer is to figure out how
Marius Gologan skrev den 2014-05-14 17:21:
This should help you discover most (not all) IP ranges in cidr format:
host -t txt outlook.com | tr " " '\n' | awk '/\./' | sed
"s/include:\|ip4://g" | sort -u | grep -i "[a-z]" | while read record;
do
host -t txt $record ; done | tr ' ' '\n' | awk -F
On Wed, 14 May 2014 10:09:19 -0500
Noel Jones wrote:
> On 5/14/2014 9:59 AM, D'Arcy J.M. Cain wrote:
> > It looks like hotmail is on two DNSBLs and postscreen is blocking
> > them. I would like to offer my users a way to whitelist individual
> > addresses but it looks like I can only whitelist CI
This should help you discover most (not all) IP ranges in cidr format:
host -t txt outlook.com | tr " " '\n' | awk '/\./' | sed
"s/include:\|ip4://g" | sort -u | grep -i "[a-z]" | while read record; do
host -t txt $record ; done | tr ' ' '\n' | awk -F ":" '/[0-9]*\.[0-9]/
{print $2"\tpermit"}' | so
On 5/14/2014 9:59 AM, D'Arcy J.M. Cain wrote:
> It looks like hotmail is on two DNSBLs and postscreen is blocking
> them. I would like to offer my users a way to whitelist individual
> addresses but it looks like I can only whitelist CIDR blocks. Is
> that the case or do I have another option?
>
It looks like hotmail is on two DNSBLs and postscreen is blocking
them. I would like to offer my users a way to whitelist individual
addresses but it looks like I can only whitelist CIDR blocks. Is
that the case or do I have another option?
Cheers.
--
D'Arcy J.M. Cain
System Administrator, Vex
Am 14.05.2014 16:31, schrieb Robert Schetterer:
> Am 14.05.2014 16:18, schrieb johnea:
>> Hello,
>>
>> Is there a simple way to extract links from an email body and submit to
>> DNSBL?
>>
>> Thank You!
>>
>> johnea
>
> some antivirus/antispam may have this feature
> good starting point is amavis
Am 14.05.2014 16:18, schrieb johnea:
>
> Hello,
>
> Is there a simple way to extract links from an email body and submit to DNSBL?
>
> Thank You!
>
> johnea
>
some antivirus/antispam may have this feature
good starting point is amavis
http://www.ijs.si/software/amavisd/
Best Regards
MfG Rob
Hello,
Is there a simple way to extract links from an email body and submit to DNSBL?
Thank You!
johnea
> "... I run clamav which weeds out some of it out, but a large amount still
seems to get through"
If you are using amavis with clamav, uncomment these lines in amavis config
file(s):
qr'^MAIL$', # retain full original message for virus checking (can be
slow)
qr'^Zip archive data',
On Wed, 14 May 2014 11:13:20 +0100
Matt Holgate wrote:
> I was wondering if greylisting would be a useful thing to try in an
> attempt to reduce the amount received?
Greylisting is great. The day that I implemented it I saw a 90%
reduction in spam. Don't hesitate.
> Problem is, I don't really
Am 14.05.2014 12:13, schrieb Matt Holgate:
> Hi folks,
>
> Most of the spam I receive these days tends to be malware with attached
> ZIP files. I run clamav which weeds out some of it out, but a large
> amount still seems to get through.
>
> I was wondering if greylisting would be a useful thing
On 14 May 2014, at 12:13, Matt Holgate wrote:
> Most of the spam I receive these days tends to be malware with attached ZIP
> files. I run clamav which weeds out some of it out, but a large amount still
> seems to get through.
>
> I was wondering if greylisting would be a useful thing to try i
Hi folks,
Most of the spam I receive these days tends to be malware with attached
ZIP files. I run clamav which weeds out some of it out, but a large
amount still seems to get through.
I was wondering if greylisting would be a useful thing to try in an
attempt to reduce the amount received?
Charles Orth:
> Hi,
>
> Has there been any thoughts on support for passing recipient DSN
> information to milter protocol (eg rcpt_dsn macro)?
According to the change log you can specify both NOTIFY and
ORCPT parameters.
Wietse
20131123
Feature: support for NOTIFY parameter in
On Tue, May 13, 2014 at 01:31:09PM +, Viktor Dukhovni wrote:
>
> The logging is misleading, it should say "Anonymous" rather than
> "untrusted". This is fixed in 2.11.1 and 2.12 snapshots.
>
> If you want authentication of this destination, you need to use a
> security level that demands aut
24 matches
Mail list logo
