Voytek Eymont a écrit :
> I have a user getting rejects from several valid senders based on
> ix.dnsbl.manitu.net blacklist, like:
>
> NOQUEUE: reject: RCPT from smtpout6.poczta.onet.pl[213.180.147.166]: 554
> 5.7.1 Service unavailable; Client host [213.180.147.166] blocked using
> ix.dnsbl.manitu
Am 21.03.2010 00:16, schrieb Robert Schetterer:
> Am 19.03.2010 12:42, schrieb Wietse Venema:
>> Robert Schetterer:
>>> Am 19.03.2010 11:41, schrieb Wietse Venema:
Robert Schetterer:
> Hi @ll,
> is there a way to overide
> transport table for specific
> sender domains
> alternatively, use dnswl.org (see www.dnswl.org on how to use it with
> postfix) just before DNSBL checks.
mouss, thanks
smtpd_recipient_restrictions =
...
check_sender_access hash:/etc/postfix/freemail_access,
check_recipient_access pcre:/etc/postfix/recipient_checks.pcre,
check_helo_
Hi
I noted that postfix is writing headers with "unknown" instead of the IPv6
reverse DNS that I know exists.
e.g.
Received: from merboo.mamista.net (unknown [IPv6:2001:470:1f0b:1055::1])
by tigger.mamista.net (Postfix) with ESMTP id 581F21100B4
for ; Mon, 22 Mar 2010 02:18:00 +1
Martin Barry wrote:
Hi Martin,
> I noted that postfix is writing headers with "unknown" instead of the IPv6
> reverse DNS that I know exists.
>
> e.g.
>
> Received: from merboo.mamista.net (unknown [IPv6:2001:470:1f0b:1055::1])
> by tigger.mamista.net (Postfix) with ESMTP id 581F21100B4
Le 21/03/2010 16:32, Martin Barry a écrit :
> Hi
>
> I noted that postfix is writing headers with "unknown" instead of the IPv6
> reverse DNS that I know exists.
>
> e.g.
>
> Received: from merboo.mamista.net (unknown [IPv6:2001:470:1f0b:1055::1])
> by tigger.mamista.net (Postfix) with ES
Martin Barry:
> Hi
>
> I noted that postfix is writing headers with "unknown" instead of the IPv6
> reverse DNS that I know exists.
>
> e.g.
>
> Received: from merboo.mamista.net (unknown [IPv6:2001:470:1f0b:1055::1])
> by tigger.mamista.net (Postfix) with ESMTP id 581F21100B4
>
Voytek Eymont a écrit :
>
>> alternatively, use dnswl.org (see www.dnswl.org on how to use it with
>> postfix) just before DNSBL checks.
>
> mouss, thanks
>
>
> smtpd_recipient_restrictions =
> ...
> check_sender_access hash:/etc/postfix/freemail_access,
> check_recipient_access pcre:/etc/p
$quoted_author = "Bernhard Schmidt" ;
> >
> > $ dig -x 2001:470:1f0b:1055::1 +short
> > merboo.mamista.net.
>
> $ dig -t merboo.mamista.net +short
> 2001:470:1f0a:1055::2
>
> 1f0a != 1f0b
[facepalms]
thanks!
Marty
Postfix 2.6 running on OpenBSD works well as a mail server but there is
one specific problem for which any advice is gratefully received.
cleanup takes a long time to complete when email with attachments is
received via SMTP but not when mail arrives via pickup. This presently
causes problems for
Hi,
Please pardon the noobie question. I looked through the list archives and also
whatever docos I could locate online in an effort to help myself prior to
posting to the list.
I just installed policyd-weight and would like to configure it alongside my
postfix installation running on Debian
Hello all,
I am currently trying to configure Postfix to route incoming emails
based on email address matching to a daemon I wrote.
Here is the context : I am developing a simple mailing list management
daemon to which I want Postfix to hand emails according to mailing list
addresses it hand
Dave Green:
> Postfix 2.6 running on OpenBSD works well as a mail server but there is
> one specific problem for which any advice is gratefully received.
>
> cleanup takes a long time to complete when email with attachments is
> received via SMTP but not when mail arrives via pickup. This presentl
Marc Falzon:
[ Charset ISO-8859-1 unsupported, converting... ]
> Hello all,
>
> I am currently trying to configure Postfix to route incoming emails
> based on email address matching to a daemon I wrote.
>
> Here is the context : I am developing a simple mailing list management
> daemon to which
Thanks kindly for your reply
> There is no fundamental reason why pickup->cleanup is slower than
> smtpd->cleanup (other than different receive_override_options
> settings in master.cf).
>
> However, it is possible that you're sending mail INTO Postfix at
> a slower rate than expected.
>
> Specifi
On 21/03/10 23:11, Wietse Venema wrote:
Marc Falzon:
[ Charset ISO-8859-1 unsupported, converting... ]
Hello all,
I am currently trying to configure Postfix to route incoming emails
based on email address matching to a daemon I wrote.
Here is the context : I am developing a simple mailing list
Dave Green:
> Thanks kindly for your reply
>
> > There is no fundamental reason why pickup->cleanup is slower than
> > smtpd->cleanup (other than different receive_override_options
> > settings in master.cf).
> >
> > However, it is possible that you're sending mail INTO Postfix at
> > a slower rat
> Can you do some tests with a recent version of Postfix's own stress
> testing tool?
smtp-source -t bitbuc...@sigmasys.co.uk -l 5242880 -m 10 206.125.173.103
0m42.62s real0m0.02s user0m0.31s system
smtp-source -t bitbuc...@sigmasys.co.uk -l 5242880 -m 10 127.0.0.1
0m8.27s real
Dave Green:
> > Can you do some tests with a recent version of Postfix's own stress
> > testing tool?
>
> smtp-source -t bitbuc...@sigmasys.co.uk -l 5242880 -m 10 206.125.173.103
> 0m42.62s real0m0.02s user0m0.31s system
>
> smtp-source -t bitbuc...@sigmasys.co.uk -l 5242880 -m 10
On Sun, 21 Mar 2010, Dov Oxenberg wrote:
> Here is my main.cf:
As noted in DEBUG_README, share the output of 'postconf -n' instead of
pasting your main.cf.
> So, am I correct in my understanding I can invoke policyd-weight by
> simply adding the line "check_policy_service inet:127.0.0.1:12525"
running 2.7.0
I have not changed anything in "main.cf" or "master.cf"
Getting following error in /var/log/maillog
Mar 21 19:00:18 x postfix/smtpd[8118]: fatal: invalid "-o content_filter"
option value: missing '=' after attribute name
Mar 21 19:00:19 x postfix/master[8109]: warning: pr
running 2.7.0
I have not changed anything in "main.cf" or "master.cf"
Getting following error in /var/log/maillog
Mar 21 19:00:18 x postfix/smtpd[8118]: fatal: invalid "-o content_filter"
option value: missing '=' after attribute name
Mar 21 19:00:19 x postfix/master[8109]: warning: pro
22 matches
Mail list logo