Hello,
I currently use relay_domains and relay_transport as a means to relay
email on to another mail server which hands off to the MDA. Everything
works well. Occasionally there may be a delivery problem when talking
to the relay_transport that results in a bounce being generated by
Hello,
I currently use relay_domains and relay_transport as a means to relay
email on to another mail server which hands off to the MDA. Everything
works well. Occasionally there may be a delivery problem when talking
to the relay_transport that results in a bounce being generated by
On 9/24/2014 12:52 PM, Wietse Venema wrote:
Michael McCallister:
Hello,
I currently use relay_domains and relay_transport as a means to relay
email on to another mail server which hands off to the MDA. Everything
works well. Occasionally there may be a delivery problem when talking
Hi,
This is not a postfix problem but rather a problem with pfixtools which
are tools written specifically for postfix. Since I know there are some
pfixtools devs here on the list and pfixtools does not have a mailing
list, I thought I would try my luck here. I am getting a seg fault
while
Hi,
I like what I see in postscreen and am considering using some of the
after 220 tests. The issue I have in doing so is that the only
documented option for sharing postscreen_cache_map across servers is to
use memcache and memcache over wan will introduce way too much latency
from the
Hi,
Does postscreen_dnsbl_ttl apply to nxdomain responses as well? For
example, lets assume an IP lookup on zen.spamhaus.org returns nxdomain
and postscreen_dnsbl_ttl is set to an hour - postscreen won't check
again for another hour? Or does that caching only apply to non-nxdomain
On 2/10/2014 7:43 PM, Wietse Venema wrote:
Michael McCallister:
Hi,
Does postscreen_dnsbl_ttl apply to nxdomain responses as well? For
example, lets assume an IP lookup on zen.spamhaus.org returns nxdomain
and postscreen_dnsbl_ttl is set to an hour - postscreen won't check
again for another
On 2/10/2014 9:09 PM, Noel Jones wrote:
On 2/10/2014 9:45 PM, Michael McCallister wrote:
On 2/10/2014 7:43 PM, Wietse Venema wrote:
Michael McCallister:
Hi,
Does postscreen_dnsbl_ttl apply to nxdomain responses as well? For
example, lets assume an IP lookup on zen.spamhaus.org returns
On 2/4/2014 2:06 AM, Jason Woods wrote:
Hi Michael,
This looks like one of my patches broke the TCP table when using -I... :-) It
should be 500 not 400 it seems. Fruneau will be pleased ^^
I've pushed a fix to my own fork which I'll pull to Fruneau soon - its identical to
Fruneau's except for
On 2/4/2014 2:42 PM, Jason Woods wrote:
No problem!
Can you describe the issue with the space you encountered? Or steps to
reproduce?
I'll throw a fix over to Fruneau before I start working more on srs-milter.
I originally had one line in the secrets file that was probably 200-300
chars.
On 2/2/2014 11:47 PM, Jason Woods wrote:
Hi Michael,
I did some tweaks on pfixtools I will have to have a look and check for you (I
use it too.)
It's not the ideal method though and a milter is really the correct way to do
SRS as the canonical filters, although giving almost desired effect,
Thanks again Jason - I get this using your specified telnet test:
500 Hash invalid in SRS address.
So I have been playing around with it more now in light of this new
information - here is what I have found:
* It works and delivers mail when the -I switch is NOT present (this
has been my
Hi,
I am having some difficulty getting SRS to work properly with postfix
and was hoping someone here might be able to shed some light on my
issue. Some quick background on the problem:
* Almost all email on this system just gets forwarded on elsewhere (no
local deliveries). This is
13 matches
Mail list logo
