On Wednesday 17 December 2008, Wietse Venema wrote:
klondike:
Bernhard Fischer escribi?:
I'd like to use DNSSEC with Postfix.
I did some research on the web but although DNSSEC is there nobody
really cares about it.
The most recent patch for Postfix is for release 2.3 and is based
On Wednesday 17 December 2008, mouss wrote:
Bernhard Fischer a écrit :
I'd like to use DNSSEC with Postfix.
I did some research on the web but although DNSSEC is there nobody really
cares about it.
The most recent patch for Postfix is for release 2.3 and is based on libs
(libval,
On Thursday 18 December 2008, Patrick Vande Walle wrote:
On Wed, 17 Dec 2008 20:42:55 +0100, Bernhard Fischer b...@abenteuerland.at
wrote:
I'd like to use DNSSEC with Postfix.
I did some research on the web but although DNSSEC is there nobody really
cares about it.
The most recent
Jose Ildefonso Camargo Tolosa a écrit :
On Fri, Dec 19, 2008 at 7:19 AM, Jorey Bump l...@joreybump.com wrote:
Jose Ildefonso Camargo Tolosa wrote, at 12/18/2008 06:28 AM:
I think you should send more info on your config, for example:
MX record for your domain.
myhostname entry from main.cf
$ whois linendim.com
Record created on:2008-12-15 11:45:30.0
Database last updated on: 2008-12-15 11:42:09.153
Domain Expires on:2009-12-15 11:45:31.0
A 1-second life domain name.
First, is there an existing policy server out there that checks how many
mouss a écrit :
Jose Ildefonso Camargo Tolosa a écrit :
On Fri, Dec 19, 2008 at 7:19 AM, Jorey Bump l...@joreybump.com wrote:
Jose Ildefonso Camargo Tolosa wrote, at 12/18/2008 06:28 AM:
I think you should send more info on your config, for example:
MX record for your domain.
myhostname
Justin Piszcz a écrit :
$ whois linendim.com
Record created on:2008-12-15 11:45:30.0
Database last updated on: 2008-12-15 11:42:09.153
Domain Expires on:2009-12-15 11:45:31.0
A 1-second life domain name.
First, is there an existing policy server
Justin Piszcz wrote, at 12/20/2008 05:43 AM:
$ whois linendim.com
Record created on:2008-12-15 11:45:30.0
Domain Expires on:2009-12-15 11:45:31.0
A 1-second life domain name.
What do you mean? The domain expires in one year and a second from its
creation
Jorey Bump a écrit :
Justin Piszcz wrote, at 12/20/2008 05:43 AM:
$ whois linendim.com
Record created on:2008-12-15 11:45:30.0
Domain Expires on:2009-12-15 11:45:31.0
A 1-second life domain name.
What do you mean? The domain expires in one year and a
If the problem is Mailscanner mangling the files, would an upgrade solve the
problem?
How can I test if the problem is concurrent access? Just to be sure which of
these are the problems...
Regards,
Pedro Augusto de Oliveira Pereira
Cisco Certified Network Associate - CCNA
On Fri, Dec 19, 2008
On Sat, 20 Dec 2008 13:07:03 -0200
Pedro Augusto augusto.pe...@gmail.com wrote:
On Fri, Dec 19, 2008 at 5:53 PM, Victor Duchovni
victor.ducho...@morganstanley.com wrote:
On Fri, Dec 19, 2008 at 02:47:49PM -0500, Brian Evans - Postfix List
wrote:
Pedro Augusto wrote:
Good day,
I'm
Wietse Venema escribió:
klondike:
Bernhard Fischer escribi?:
I'd like to use DNSSEC with Postfix.
I did some research on the web but although DNSSEC is there nobody really
cares about it.
The most recent patch for Postfix is for release 2.3 and is based on libs
(libval, libsres)
Hi,
How hash table in transport_maps has '*' support and it in others
options (e.g. check_client_access) dont work? Postfix always query for
'*'?
Why it is necessary if relayhost exist?
--
Reinaldo de Carvalho
http://korreio.sf.net (Now available in English)
http://python-cyrus.sf.net
Pedro Augusto a écrit :
If the problem is Mailscanner mangling the files, would an upgrade solve
the problem?
I think it's as Viktor said. I've already seen corrupted mbox files like
that.
consider using maildir instead.
How can I test if the problem is concurrent access? Just to be sure
Reinaldo de Carvalho a écrit :
Hi,
How hash table in transport_maps has '*' support and it in others
options (e.g. check_client_access) dont work? Postfix always query for
'*'?
Why it is necessary if relayhost exist?
compatibility with old versions.
Pedro Augusto:
If the problem is Mailscanner mangling the files, would an upgrade solve the
problem?
How can I test if the problem is concurrent access? Just to be sure which of
these are the problems...
Null bytes in mailbox files are usually the result of incorrect
file locking.
To find
On Fri, Dec 19, 2008 at 5:32 PM, Wietse Venema wie...@porcupine.org wrote:
Asif Iqbal:
need to test it. Just set:
smtp_tls_security_level = encrypt
Thanks, I will put that in
Just checked here that Postfix can talk SSL with [smtp.gmail.com]:587
just fine. But you need to set up
Asif Iqbal:
On Fri, Dec 19, 2008 at 5:32 PM, Wietse Venema wie...@porcupine.org wrote:
Asif Iqbal:
need to test it. Just set:
smtp_tls_security_level = encrypt
Thanks, I will put that in
Just checked here that Postfix can talk SSL with [smtp.gmail.com]:587
just fine.
Asif Iqbal wrote:
I did but still failing to relay through gmail
Dec 20 14:24:32 improvise postfix/qmgr[19372]: 4238710E3AA:
from=iqb...@improvise.lan, size=444, nrcpt=1 (queue active)
Dec 20 14:24:32 improvise postfix/smtp[19431]: 4238710E3AA:
to=vad...@gmail.com,
On Sat, Dec 20, 2008 at 7:51 PM, Sahil Tandon sa...@tandon.net wrote:
Asif Iqbal wrote:
I did but still failing to relay through gmail
Dec 20 14:24:32 improvise postfix/qmgr[19372]: 4238710E3AA:
from=iqb...@improvise.lan, size=444, nrcpt=1 (queue active)
Dec 20 14:24:32 improvise
Asif Iqbal:
Dec 20 21:25:20 improvise postfix/smtp[7157]: warning: SASL
authentication failure: No worthy mechs found
This means that the SASL (NOT: SSL) mechanisms are not properly
configured.
So I tried the openssl test and looks like I need a real certificate?!
No, you need to fix the
On 12/19/2008, Pedro Augusto (augusto.pe...@gmail.com) wrote:
It works perfectly, I have no problems sending or receiving e-mail
but sometimes the user can't receive any e-mail using his client
(such as Outlook Express) or through webmail. When we check the mail
file, the first line is full of
On Sat, Dec 20, 2008 at 9:41 PM, Wietse Venema wie...@porcupine.org wrote:
Asif Iqbal:
Dec 20 21:25:20 improvise postfix/smtp[7157]: warning: SASL
authentication failure: No worthy mechs found
This means that the SASL (NOT: SSL) mechanisms are not properly
configured.
So I tried the
hi list,
I'd like to ask how I am able to do this kind of restriction on postfix.
we have a local access restriction that denied emails from outside to
be able to reach those users on the access list.
smtpd_recipient_restrictions =
check_sender_access
aio shin wrote:
we have a local access restriction that denied emails from outside to
be able to reach those users on the access list.
smtpd_recipient_restrictions =
check_sender_access hash:/etc/postfix/restricted_senders
permit_mynetworks
permit_sasl_authenticated
25 matches
Mail list logo
