Noel Jones skrev den 2013-01-06 19:40:
Clearly the current, vastly improved, false positive rate is still
not acceptable for everyone.
http://www.dnswl.org/tech see more on permit_dnswl_client
it does not need to be specific dnswl.org as dnsbl/dnswl, its just an
good example on postfix
Dear all,
I would like to ask the staff of postfix if they are planning (working) or
supporting EAI (http://tools.ietf.org/wg/eai/) in the feature versions?
If there is a working progress on it can anybody guide me to it?
Thank you,
AbdulRahman,
on a quick reading on the drafts, it seems to deal with CLIENT
specifications ... example:
This document provides guidelines for __email clients__ that support
these specifications for Email Address Internationalization (EAI). It
does not introduce any protocol extensions that are
The EAI group covers many parts one of them SMTP
(http://tools.ietf.org/html/rfc6531). So basically this rfc covers the MTA part.
-Original Message-
From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
On Behalf Of Leonardo Rodrigues
Sent: 7/Jan/2013 3:04 PM
Also I have found here
http://en.wikipedia.org/wiki/Email_Address_Internationalization#Internationalization
Internationalization Support
Modified versions of sendmail and postfix exist that support the proposed EAI
rules. Google has limited support for the earlier experimental RFC
As stated
Guys,
I've identified a missbehavior on postfix.
I do use destination_rate_delay for specific transport queue, and I found out
that connection cache is not working when I have
transport_destination_rate_delay 1s.
If I change the destination_rate_delay to higher than 1s, connection cache
Abdulrahman I. ALGhadir:
Dear all,
I would like to ask the staff of postfix if they are planning
(working) or supporting EAI (http://tools.ietf.org/wg/eai/) in the
feature versions?
You can already send email TEXT in any characterset that you like.
You just can't use 8-bit email addresses
Rafael Azevedo - IAGENTE:
I do use destination_rate_delay for specific transport queue, and
I found out that connection cache is not working when I have
transport_destination_rate_delay 1s.
The default time limit is 2s, and it is enforced in multiple places.
You have found only one.
As
Hi Wietse,
I don't really get. I'm also sure postfix has a way to solve this issue.
This is what I'm trying to do:
- I need to have only one process to this transport's queue.
- This queue must respect the destination's policy, so I can't have more than
20 opened connections in 10 minutes
Rafael Azevedo - IAGENTE:
Hi Wietse,
I don't really get. I'm also sure postfix has a way to solve this issue.
I told you that there are two parameters that enforce the time limit.
Wietse
Could you please refresh my mind?
Thanks.
Att.
--
Rafael Azevedo | IAGENTE
Fone: 51 3086.0262
MSN: raf...@hotmail.com
Visite: www.iagente.com.br
Em 07/01/2013, às 12:17, Wietse Venema wie...@porcupine.org escreveu:
Rafael Azevedo - IAGENTE:
Hi Wietse,
I don't really get. I'm also sure
On Mon, Jan 07, 2013 at 11:34:45AM -0200, Rafael Azevedo - IAGENTE wrote:
This is what I'm trying to do:
- I need to have only one process to this transport's queue.
mumble_destination_concurrency_limit = 1
- This queue must respect the destination's policy, so I can't
have more
Hi Viktor, thanks for helping.
I've done something very similar.
I created different named transports for specific domains and have all domains
I need a special treatment to use this named transport.
So since I'm using Postfix + MySQL, I have a transport table with all domains
and destination
On Mon, Jan 07, 2013 at 02:37:03PM -0200, Rafael Azevedo - IAGENTE wrote:
I've done something very similar.
If you want help, please take some time to read and follow the
advice you receive completely and accurately. Similar is another
way of saying incorrect.
I created different named
Hi Viktor,
Thanks once again for helping me on this.
Please understand that I'm very open and thankful for any help. I'm also
trying to understand what you meant.
Getting whitelisted is always the best solution, but believe me, there are some
providers that just don't answer any email, they
Hi Viktor,
I was reading the documentation and found out something very interesting.
If I use mumble_destination_concurrency_limit = 1, the destination is a
recipient not a domain.
Since I'm trying to control the throughput per destination domain, it is
necessary to use
Hi Viktor,
Thanks for the help.
I believe I've activated the next hop feature in my transport table.
If I understood it right, all I had to do is tell postfix that these domains
belongs to my named transport specifying the domain.
So this is how it is now:
criticaldomain.tld
On Mon, Jan 07, 2013 at 03:06:42PM -0200, Rafael Azevedo - IAGENTE wrote:
Anyway, I'll search how to use this next hoop feature and see
The term is nexthop, this specifies the next system or systems
to which the message will be forwarded en-route to its destination
mailbox. With SMTP the
On Mon, Jan 07, 2013 at 03:29:53PM -0200, Rafael Azevedo - IAGENTE wrote:
I believe I've activated the next hop feature in my transport table.
If I understood it right, all I had to do is tell postfix that
these domains belongs to my named transport specifying the domain.
So this is how
On Mon, Jan 07, 2013 at 03:19:39PM -0200, Rafael Azevedo - IAGENTE wrote:
If I use mumble_destination_concurrency_limit = 1, the destination
is a recipient not a domain.
This is wrong. The setting in question is the recipient_limit, not
the concurrency limit.
Thank you so much Viktor, now I fully understand what you said.
Cheers.
Att.
--
Rafael Azevedo | IAGENTE
Fone: 51 3086.0262
MSN: raf...@hotmail.com
Visite: www.iagente.com.br
Em 07/01/2013, às 15:57, Viktor Dukhovni postfix-us...@dukhovni.org escreveu:
On Mon, Jan 07, 2013 at 03:29:53PM
Hi Viktor,
I've done exactally what you said and notice that the connection cache is not
being used anymore.
I ran a script with loop sending email to few recipients, and the cache seems
not be working (after commenting slow_destination_rate_delay).
Changing slow_destination_rate_delay to 1s
My installation of Postfix has been running without a problem for over
two years. Suddenly it refused to accept mail from my MUA
Claws-Mail. This is the output of the claws mail log:
[13:19:59] SMTP 220 scorpio.seibercom.net ESMTP Postfix (2.10-20121031)
[13:19:59] ESMTP EHLO scorpio
[13:19:59]
On Mon, Jan 07, 2013 at 04:24:20PM -0200, Rafael Azevedo - IAGENTE wrote:
I've done exactally what you said and notice that the connection
cache is not being used anymore.
You have enabled cache-on-demand behaviour. This happens when the active
queue contains a backlog of messages to the
On 1/7/2013 12:32 PM, Gerard Seibert wrote:
My installation of Postfix has been running without a problem for over
two years. Suddenly it refused to accept mail from my MUA
Claws-Mail. This is the output of the claws mail log:
...
[13:20:00] ESMTP 250-AUTH CRAM-MD5 DIGEST-MD5 PLAIN LOGIN
On Mon, 07 Jan 2013 13:09:26 -0600
Noel Jones articulated:
On 1/7/2013 12:32 PM, Gerard Seibert wrote:
My installation of Postfix has been running without a problem for
over two years. Suddenly it refused to accept mail from my MUA
Claws-Mail. This is the output of the claws mail log:
Viktor Dukhovni:
On Mon, Jan 07, 2013 at 04:24:20PM -0200, Rafael Azevedo - IAGENTE wrote:
I've done exactally what you said and notice that the connection
cache is not being used anymore.
You have enabled cache-on-demand behaviour. This happens when the active
queue contains a backlog
On Mon, Jan 07, 2013 at 02:34:07PM -0500, Jerry wrote:
On Mon, 07 Jan 2013 13:09:26 -0600
Noel Jones articulated:
On 1/7/2013 12:32 PM, Gerard Seibert wrote:
[postconf -n]
I don't see smtpd_sasl_type listed. The default type is cyrus.
Is that what you intend? Looks as if you're using
What is the configuration forces postfix to honor what is found in
virtual_alias_maps ?
e.g.
support@$domain.com LocalAccount
Thanks.
Randy Ramsdell:
What is the configuration forces postfix to honor what is found in
virtual_alias_maps ?
e.g.
support@$domain.com LocalAccount
It does.
However, the local(8) delivery agent case-folds recipient names.
Wietse
On Mon, Jan 07, 2013 at 04:02:36PM -0500, Wietse Venema wrote:
On Mon, Jan 07, 2013 at 04:24:20PM -0200, Rafael Azevedo - IAGENTE wrote:
I've done exactally what you said and notice that the connection
cache is not being used anymore.
You have enabled cache-on-demand behaviour.
31 matches
Mail list logo
