On Fri, Aug 16, 2013 at 04:22:50PM -0500, lcon...@go2france.com wrote:
> postconf mail_version
> mail_version = 2.3.3
>
>
> uname -a
> Linux . 2.6.18-128.2.1.el5 #1 SMP Wed Jul 8 11:54:47 EDT 2009
> x86_64 x86_64 x86_64 GNU/Linux
>
> got an "access denied" for an IP that is in a /20 postcon
Hi Wietse,
> You removed the third instance name from the main.cf file of the
> "primary" Postfix instance (for example, the /etc/postfix/main.cf).
Its still listed right there in multi_instance_directories if that's
what you mean ?
postmulti -l also shows it ?
postconf mail_version
mail_version = 2.3.3
uname -a
Linux . 2.6.18-128.2.1.el5 #1 SMP Wed Jul 8 11:54:47 EDT 2009
x86_64 x86_64 x86_64 GNU/Linux
got an "access denied" for an IP that is in a /20 postconf confirms is
in mynetworks
the only match_hostname I see is for
smtpd_client_ev
On Aug 16, 2013, at 15.06, Scott Kitterman wrote:
> I wouldn't bother. It has only very limited deployment and is proposed for
> removal in the revision to RFC 4408 that is about to enter IETF last call.
interesting. thank you for calling attention to this.
-ben
Ben:
> Hi,
>
> I've got a three instance setup, two instances start fine. One has
> suddenly started to refuse to start.
>
> To make matters worse, nothing is logged about its failure to start, so
> I remain none the wiser !
You removed the third instance name from the main.cf file of the
"pr
b...@bitrate.net wrote:
>On Aug 16, 2013, at 01.56, Rob Tanner wrote:
>
>> What is it, besides adding the correct the DNS TXT records
>
>as there is a formal dns rr type for spf defined in rfc4408, you'll of
>course want to include that as well.
I wouldn't bother. It has only very limited deplo
Hi,
I've got a three instance setup, two instances start fine. One has
suddenly started to refuse to start.
To make matters worse, nothing is logged about its failure to start, so
I remain none the wiser !
The main.cf for the instance is as follows :
data_directory = /var/lib/postfix-inet
On Aug 16, 2013, at 01.56, Rob Tanner wrote:
> What is it, besides adding the correct the DNS TXT records
as there is a formal dns rr type for spf defined in rfc4408, you'll of course
want to include that as well.
-ben
On Tue, Aug 13, 2013 at 07:57:47PM +0100, higuita wrote:
> I have a small mail server, with ipv6 and i relay the email to
> my ISP mail server. Their mail server have now ipv6, yet every
> time my postfix tries to connect to their server it gives timeout:
>
> Aug 13 12:51:27 paquete postfix/smtp
On Wed, Aug 14, 2013 at 11:13:52PM +0200, Ralf Hildebrandt wrote:
> * lst_ho...@kwsoft.de :
>
> > >* Do I need tls_preempt_cipherlist = yes, and thus Postfix 2.8.0 or not?
> >
> > This let the *server* (Postfix) choose a cipher suggested by the
> > client, so it depends. If the client has no DH
On 2013-08-16 9:13 AM, Grant wrote:
Yes, that should whitelist known good sites from deep inspection,
certainly all the big mailers such as google, yahoo, comcast, etc.
However, I wonder why you don't have any dns blacklists such as
zen.spamhaus.org defined there. The ability of postscreen to
Ok since my explanation of the problem is poor at best I'll give an example
Incoming mail comes in like this (actual headers):
Aug 15 09:30:34 servername postfix/cleanup[11616]: BD48811882027: warning:
header Received: from mail-pa0-f66.google.com
(mail-pa0-f66.google.com[209.85.220.66])??by other
Carlos L wrote:
> Hello all,
> I'm looking for a bit
of help on a complicated scenario that I can't seem
> to get to
work.
>
> I have mail that comes into a server a server
with both a to and 'original
> to' address
>
>
What i would like to achieve is that mail going to the to addresses to
go
>>> Use a dns white list with a negative score in the
>>> postscreen_dnsbl_sites, and set a negative value for
>>> postscreen_dnsbl_whitelist_threshold. Simple example:
>>> # main.cf
>>> postscreen_dnsbl_sites = zen.spamhaus.org list.dnswl.org*-1
>>> postscreen_dnsbl_whitelist_threshold = -1
>>
>>
On Fri, Aug 16, 2013 at 08:36:25AM -0400, Carlos L wrote:
> I'm looking for a bit of help on a complicated scenario that I
> can't seem to get to work.
>
> I have mail that comes into a server a server with both a to and
> 'original to' address
>
> What i would like to achieve is that mail goin
Hello all,
I'm looking for a bit of help on a complicated scenario that I can't seem
to get to work.
I have mail that comes into a server a server with both a to and 'original
to' address
What i would like to achieve is that mail going to the to addresses to go
through a smarthost instead of loca
Hello all,
I'm looking for a bit of help on a complicated scenario that I can't seem
to get to work.
I have mail that comes into a server a server with both a to and 'original
to' address
What i would like to achieve is that mail going to the to addresses to go
through a smarthost instead of loca
On 8/16/2013 1:29 AM, Grant wrote:
>> Use a dns white list with a negative score in the
>> postscreen_dnsbl_sites, and set a negative value for
>> postscreen_dnsbl_whitelist_threshold. Simple example:
>> # main.cf
>> postscreen_dnsbl_sites = zen.spamhaus.org list.dnswl.org*-1
>> postscreen_dnsbl_w
On 8/16/2013 12:56 AM, Rob Tanner wrote:
> I've googled around a quite a bit and while I can find lots of instruction on
> what I need in order for Postfix to validate incoming mail, I find nothing
> about what I need to do to make sure Postfix does whatever it needs to do to
> make sure the MTA
19 matches
Mail list logo
