Le lundi 3 octobre 2011 19:09, Steve Jenkins a écrit :
> On Mon, Oct 3, 2011 at 10:02 AM, Reindl Harald
wrote:
> > it takes 5 minutes to clean the SPEC-File and remove
> > these patches - really i do not understand your problem
>
> It takes 5 minutes for YOU to clean the SPEC file, because you're
Le lundi 3 octobre 2011 01:05, vous avez écrit :
> Have you used sasl auth with packages built from this rpm? I've had a heck
> of a time trying to build with the pertinent features enabled on centos 5.
>
> Joe
sasl authentication for sending mail works, but the package that manages the
authentica
hello postfix list
I just updated to version postfix 2.8.5 with
the source rpm package
http://www.invoca.ch/pub/packages/postfix/RPMS/ils-5/SRPMS/
I made some changes to the file. spec
Is this correct. this does not compromise my security of my system
my file .spec
http://pastebin.com/rH5uGR
Le vendredi 16 septembre 2011 00:12, mouss a écrit :
> Le 15/09/2011 03:34, m...@smtp.fakessh.eu a écrit :
> > hello list
> > hello guru of postfix
> >
> >
> > I think I have correctly configure bind for IPv6. but I still can not
> > connect with telnet on
Le jeudi 15 septembre 2011 09:51, Robert Felber a écrit :
> On Thu, Sep 15, 2011 at 03:34:58AM +0200, m...@smtp.fakessh.eu wrote:
> > hello list
> > hello guru of postfix
> >
> >
> > I think I have correctly configure bind for IPv6. but I still can not
>
hello list
hello guru of postfix
I think I have correctly configure bind for IPv6. but I still can not connect
with telnet on my server
all testimonials are welcome
--
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x092164A7
gpg --keyserver pgp.mit.edu --recv-key 092164A7
http://urlsho
hi folks
I just find out about slow and the table
/etc/postfix/transport
you think it useful for normal use and what are the major providers to be
added to this file
all testimonials are welcome
--
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x092164A7
gpg --keyserver pgp.mit.edu --re
Le lundi 27 juin 2011 00:59, Wietse Venema a écrit :
> m...@smtp.fakessh.eu:
> > this patch it is safe ?
> >
> > http://pastebin.com/
>
> Ask the maintainer. I don't review code unless I have plains to
> maintain it.
>
> Wietse
I do not kno
Le dimanche 26 juin 2011 21:27, Wietse Venema a écrit :
> m...@smtp.fakessh.eu:
> > Le dimanche 26 juin 2011 20:54, Wietse Venema a ?crit?:
> > > m...@smtp.fakessh.eu:
> > > > I just set up the multi-line greeting patch .
> > >
> > > What patch? The
Le dimanche 26 juin 2011 20:54, Wietse Venema a écrit :
> m...@smtp.fakessh.eu:
> > I just set up the multi-line greeting patch .
>
> What patch? The official Postfix documentation has no multi-line
> banner support.
>
is it possible to declare a personal banner
http://pos
Hello folks
Hello list.
I just set up the multi-line greeting patch .
So I have to declare another banner and surprise the result is not comparable
with the official documentation.
I do not understand the system of newline \ n
this is not working
what is the right solution
--
http://pgp.m
Le vendredi 17 juin 2011 21:54, Victor Duchovni a écrit :
> On Fri, Jun 17, 2011 at 09:44:00PM +0200, m...@smtp.fakessh.eu wrote:
> > Le vendredi 17 juin 2011 21:39, Victor Duchovni a ?crit?:
> > > In that case you've over-engineered your configuration as was my guess
Le vendredi 17 juin 2011 21:39, Victor Duchovni a écrit :
> In that case you've over-engineered your configuration as was my guess.
> Now you need to construct something more restrained.
So I understand
how to build something cleaner
--
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x0921
Le vendredi 17 juin 2011 20:54, Victor Duchovni a écrit :
> On Fri, Jun 17, 2011 at 02:44:52PM -0400, Wietse Venema wrote:
> > > r13151 ~]# postconf -n | egrep postscreen
> >
> > That is not "postconf -n" output. There are too many lines of output.
>
> Or the OP tweaked or cloned default values of
Le vendredi 17 juin 2011 20:44, Wietse Venema a écrit :
> That is not "postconf -n" output. There are too many lines of output.
I assure you this is my exit.
[root@r13151 ~]# postconf -n | egrep postscreen
postscreen_access_list = permit_mynetworks
postscreen_bare_newline_action = ignore
postscree
hi folks
hi Wietse
hi mouss
are you ready ?
This is a general question on improvements to a standard config postscreen
with postfix 2.8.2
this my config :
r13151 ~]# postconf -n | egrep postscreen
postscreen_access_list = permit_mynetworks
postscreen_bare_newline_action = ignore
postscreen
Le jeudi 16 juin 2011 19:06, Wietse Venema a écrit :
> Petre Bandac:
> > hello
> >
> > in the last period I had several complains about mail originating from
> > yahoo/gmail not reaching the mailbox
> >
> > logging in the logs I found entries like this:
> >
> > ###
> > Jun 16 10:07:12 mx postfix/sm
Le dimanche 12 juin 2011 20:54, Wietse Venema a écrit :
> telnet 212.119.64.138 25
I just repeat the same test and get the other matches
r13151 ~]# telnet 212.119.64.138 25
Trying 212.119.64.138...
telnet: connect to address 212.119.64.138: Connection timed out
telnet: Unable to connect to remote
Le samedi 11 juin 2011 00:28, Noel Jones a écrit :
> On 6/10/2011 4:04 PM, m...@smtp.fakessh.eu wrote:
> > hi folks
> >
> > I asked a question.
> > there are providers that remove information from headers like X-Mailer
> > Received
> >
> >
> > w
hi folks
I asked a question.
there are providers that remove information from headers like X-Mailer
Received
when is there any good uses and customs
This is easy to set up with information like this
/^Received:/IGNORE
/^User-Agent:/ IGNORE
header_checks = regexp:/etc/postfix/maps/header_
20 matches
Mail list logo