Hi!
I would like to set a limit rate per domain. I know i can use
« destination_rate_delay » and it works ! The problem is that the minimum
period is 1s. It permits to send 1 email per domain per second .
If i want to send for example 5 emails per domain per second, how is it
possible by using p
Hi,
postfwd allows for fine tuning of such limitation.
-nik
Philippe Bloix schrieb:
>Hi!
>
>
>I would like to set a limit rate per domain. I know i can use
>« destination_rate_delay » and it works ! The problem is that the
>minimum
>period is 1s. It permits to send 1 email per domain per seco
On Aug 13, 2013, at 15:21, Dominik George wrote:
> postfwd allows for fine tuning of such limitation.
>
>> Philippe Bloix schrieb:
>> Hi!
>>
>> I would like to set a limit rate per domain. I know i can use «
>> destination_rate_delay » and it works ! The problem is that the minimum
>> peri
Thanks Nik for your response.
I had a look in the postfwd website. The postfwd rate limit examples show
that when the limit is reached, emails are rejected.
What i would like is :
For example, my postfix relay accepts about 1000 emails (1 shot) from a
SMTP client, then the postfix server rela
On 8/13/2013 10:26 AM, Philippe Bloix wrote:
> What i would like is :
>
> For example, my postfix relay accepts about 1000 emails (1 shot)
> from a SMTP client, then the postfix server relays them with the
> rate of 5 emails per domain per second without REJECT.
As documented, the minimum delay i
On Aug 13, 2013, at 17:34, Noel Jones wrote:
> On 8/13/2013 10:26 AM, Philippe Bloix wrote:
>> What i would like is :
>>
>> For example, my postfix relay accepts about 1000 emails (1 shot)
>> from a SMTP client, then the postfix server relays them with the
>> rate of 5 emails per domain per seco
I have installed my brand new Kolab-3 mail server after extensive testing on a
virtual box.
Unfortunately, I did not test the alias feature.
If I send e-mails to to root@btspuhler, I get a message back
The mail system
: host aargau.btspuhler.com[/var/lib/imap/socket/lmtp]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/13/2013 11:58 AM, Thomas Spuhler wrote:
> I have installed my brand new Kolab-3 mail server after
> extensive testing on a virtual box. Unfortunately, I did not
> test the alias feature. If I send e-mails to to root@btspuhler,
> I get a message ba
Hi everyone,
This question is about what are best practices with respect to DNS -
including reverse DNS - when my mail server is hosted locally, and we
use an outsourced anti-spam service for inbound filtering, as well as
relaying all outbound mail through them.
I have had a recent complaint
On Tuesday, August 13, 2013 12:12:55 PM Noel Jones wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 8/13/2013 11:58 AM, Thomas Spuhler wrote:
> > I have installed my brand new Kolab-3 mail server after
> > extensive testing on a virtual box. Unfortunately, I did not
> > test the ali
On 8/13/2013 12:16 PM, Charles Marcus wrote:
> Hi everyone,
>
> This question is about what are best practices with respect to DNS -
> including reverse DNS - when my mail server is hosted locally, and
> we use an outsourced anti-spam service for inbound filtering, as
> well as relaying all outbou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/13/2013 12:30 PM, Thomas Spuhler wrote:
> On Tuesday, August 13, 2013 12:12:55 PM Noel Jones wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> On 8/13/2013 11:58 AM, Thomas Spuhler wrote:
>>> I have installed my brand new Kolab-3 mail
Am 13.08.2013 19:16, schrieb Charles Marcus:
> Hi everyone,
>
> This question is about what are best practices with respect to DNS -
> including reverse DNS - when my mail server is hosted locally, and we
> use an outsourced anti-spam service for inbound filtering, as well as
> relaying all outbou
On 2013-08-13 1:41 PM, Noel Jones wrote:
Does anyone see any problem with this email, as far as DNS/reverse
DNS goes?
All the DNS hostnames/IPs appear to match. I see nothing whatsoever
to complain about.
Thanks Noel.
You don't appear to have SPF nor DKIM configured. While in no way
requ
Hi
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[25083]: SSL_connect error to
smtp.sapo.pt[2001:8a0:2104:ff:21
On 8/13/2013 1:02 PM, Charles Marcus wrote:
>> You don't appear to have SPF nor DKIM configured. While in no way
>> required, those do give some assurance that the mail is not forged,
>> and may help. Or may not help, since you don't really know why
>> outlook is complaining.
>
> Hmmm... so this w
On Aug 13, 2013, at 20:02, Charles Marcus wrote:
> On 2013-08-13 1:41 PM, Noel Jones wrote:
>>> Does anyone see any problem with this email, as far as DNS/reverse
>>>
>>> DNS goes?
>> All the DNS hostnames/IPs appear to match. I see nothing whatsoever
>> to complain about.
>
> Thanks Noel.
>
On 08/12/2013 08:30 PM, M. Spini wrote:
I need auth to send email, and possibly give the users the possibility
to change their pwd.
Postfix supports server SASL via either dovecot or cyrus.
You can see which your installation supports with
#postconf -a
I recommend dovecot since it is much
18 matches
Mail list logo
