> -Original Message-
> From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
> On Behalf Of Gary Smith
> Sent: Thursday, February 10, 2011 8:34 PM
> To: 'postfix-users@postfix.org'
> Subject: hold after permit question
>
> I have clients relaying email through a
I have clients relaying email through a set of servers but I wanted to put a
hold in there based on specific circumstances (such as they are sending too
much data, so lets hold and inspect). I have a hash file
(/etc/postfix/maps/hold) that is dynamically updated from a central server. So
when t
On Thu, Feb 10, 2011 at 10:50:20PM +0100, Jeroen Geilman wrote:
>> and I'm not sure how
>> smtp_connection_reuse_time_limit = 300s
>>
>> could be lowered in such a way that busy destination MXes are not
>> keeping a lot of mail in the active queue...
The re-use time should equal or exceed the dur
* Jeroen Geilman :
> ... but can it absolutely, guaranteed, accept ALL mail immediately,
> and process it within your left-over timeframe ?
Yes. It's asskicking fast.
> That seems like a measurable quantity, but you could start with
> one-half of the 60 seconds for simplicity, so both possible
On 02/10/2011 07:13 PM, Ralf Hildebrandt wrote:
Goal:
=
Make mails go to a target server within 60s.
Target server is defined as either:
* the MX host of the destination domain
* my smtp_fallback_relay which keeps trying delivery
It's really fast and can take a lot of load...
... b
On Thu, Feb 10, 2011 at 02:33:09PM +, Craig Waddington wrote:
> I am trying out the postscreen server - and am very impressed
> so far. My original interest was in greylisting - so I have the
> deep protocol tests turned on so that the temporary failure code
> 45x is returned for non-whitelis
Ralf Hildebrandt:
> * Ralf Hildebrandt :
> > Goal:
> > =
> >
> > Make mails go to a target server within 60s.
> > Target server is defined as either:
> >
> > * the MX host of the destination domain
> > * my smtp_fallback_relay which keeps trying delivery
> > It's really fast and can take a
* Ralf Hildebrandt :
> Goal:
> =
>
> Make mails go to a target server within 60s.
> Target server is defined as either:
>
> * the MX host of the destination domain
> * my smtp_fallback_relay which keeps trying delivery
> It's really fast and can take a lot of load...
So it's ok to try the
* Glenn English :
> I hope I just dodged a bullet -- my aliases file 'disappeared' somehow.
> And it was empty in all the backups.
>
> But I found a 12K aliases.db; I assume this contains the translated
> aliases data. Is there a way to convert this to a plain aliases file?
postalias -s hash:ali
Goal:
=
Make mails go to a target server within 60s.
Target server is defined as either:
* the MX host of the destination domain
* my smtp_fallback_relay which keeps trying delivery
It's really fast and can take a lot of load...
Which timeouts should I lower? I think reaching a fixed thr
I hope I just dodged a bullet -- my aliases file 'disappeared' somehow. And it
was empty in all the backups.
But I found a 12K aliases.db; I assume this contains the translated aliases
data. Is there a way to convert this to a plain aliases file?
TIA...
--
Glenn English
g...@slsware.com
Justin Piszcz:
> Feb 10 10:16:38 p34 postfix/cleanup[29153]: BD7141200F4:
> message-id=
> Feb 10 10:16:38 p34 postfix/cleanup[29153]: BD7141200F4: warning: header
> X-Mailer: iPhone Mail (8C148) from unknown[166.137.8.8];
> from= to= proto=ESMTP
> helo=<[10.9.233.106]>: 0xdeadbeef iPhone Mail (
Hi,
When I attach large images > 5-10MiB/s, sometimes this occurs, I tried
setting:
tcp_windowsize = 65535
I also tried setting ecn to 0.
But neither seemed to fix the problem below. I can send the same images
to an Exchange server and they send through with no problems. Also, if I
send s
On 02/10/2011 04:59 PM, Wietse Venema wrote:
Craig Waddington:
Hi,
I am trying out the postscreen server - and am very impressed so far. My
original interest was in greylisting - so I have the deep protocol tests
turned on so that the temporary failure code 45x is returned for
non-whitelist
Victor Duchovni:
> On Thu, Feb 10, 2011 at 10:59:31AM -0500, Wietse Venema wrote:
>
> > On th eother hand, making the "PASS NEW" event a trigger for a
> > penalty time should require little new code. I added support for
> > "penalty time" late last year but it is currently unused for lack
> > of a
Robert Schetterer:
> Hi in
>
> http://www.postfix.org/MYSQL_README.html
>
> we've included the ability to have Postfix reference multiple hosts for
> access to a single mysql map. This will work if sites set up mirrored
> mysql databases on two or more hosts. Whenever queries fail with an
> error
On Thu, Feb 10, 2011 at 10:59:31AM -0500, Wietse Venema wrote:
> On th eother hand, making the "PASS NEW" event a trigger for a
> penalty time should require little new code. I added support for
> "penalty time" late last year but it is currently unused for lack
> of a "trigger" mechanism. Penalty
Mark Alan:
> On Wed, 9 Feb 2011 15:18:39 -0500 (EST), Wietse Venema
> wrote:
>
> > postscreen currently does not implement greylisting - smtpd(8)
> > currently can do that with policy daemons.
>
> Yes but they do it very late in the process
> smtpd_recipient_restrictions =
> ...
Craig Waddington:
> Hi,
>
> I am trying out the postscreen server - and am very impressed so far. My
> original interest was in greylisting - so I have the deep protocol tests
> turned on so that the temporary failure code 45x is returned for
> non-whitelisted clients.
>
> During my testing -
Thanks :-) It is working .. I forgot to use classes :-)
Peter
On Feb 10, 2011, at 1:43 PM, Nikolaos Milas wrote:
> You could try using restriction classes, as documented:
> http://www.postfix.org/RESTRICTION_CLASS_README.html
>
> For example:
>
> smtpd_restriction_classes = restr_class1
> r
On Wed, 9 Feb 2011 15:18:39 -0500 (EST), Wietse Venema
wrote:
> postscreen currently does not implement greylisting - smtpd(8)
> currently can do that with policy daemons.
Yes but they do it very late in the process
smtpd_recipient_restrictions =
...
reject_unau
Hi,
> I am trying out the postscreen server - and am very impressed so far. My
> original interest was in greylisting - so I have the deep protocol tests
> turned on so that the temporary failure code 45x is returned for
> non-whitelisted clients.
>
> During my testing - I noticed that the sma
Smart Security, version of virus signature
database 5862 (20110210) __
The message was checked by ESET Smart Security.
http://www.eset.com
Am 10.02.2011 13:57, schrieb Wietse Venema:
> Robert Schetterer:
>> Am 10.02.2011 12:48, schrieb Wietse Venema:
>>> Robert Schetterer:
Hi ,
if i use verify ( via internal network )
over smtp i want to have some fallback mech
so if verify fails for one host ( perhabs it is reboot
Robert Schetterer:
> Am 10.02.2011 12:48, schrieb Wietse Venema:
> > Robert Schetterer:
> >> Hi ,
> >> if i use verify ( via internal network )
> >> over smtp i want to have some fallback mech
> >> so if verify fails for one host ( perhabs it is rebooting etc )
> >> i wanna fallback to another host
Am 10.02.2011 12:48, schrieb Wietse Venema:
> Robert Schetterer:
>> Hi ,
>> if i use verify ( via internal network )
>> over smtp i want to have some fallback mech
>> so if verify fails for one host ( perhabs it is rebooting etc )
>> i wanna fallback to another host for verify
>> is this possible?
You could try using restriction classes, as documented:
http://www.postfix.org/RESTRICTION_CLASS_README.html
For example:
smtpd_restriction_classes = restr_class1
restr_class1= check_sender_access
hash:/etc/postfix/somesenders,permit_mynetworks,reject
smtpd_recipient_restrictions =
hash:/etc/
Am 10.02.2011 12:12, schrieb Robert Schetterer:
> Hi in
>
> http://www.postfix.org/MYSQL_README.html
>
> we've included the ability to have Postfix reference multiple hosts for
> access to a single mysql map. This will work if sites set up mirrored
> mysql databases on two or more hosts. Whenever
Robert Schetterer:
> Hi ,
> if i use verify ( via internal network )
> over smtp i want to have some fallback mech
> so if verify fails for one host ( perhabs it is rebooting etc )
> i wanna fallback to another host for verify
> is this possible?
Use address_verify_default_transport to send verifi
Hi,
I need to have this specific scenario:
I need to set up for example.com aliases for all (every...@example.com), so it
is made.
Next I need to restrict every...@example.com to local delivery only, so I made
this:
/etc/postfix/main.cf:
smtpd_recipient_restrictions = check_recipient_acces
Hi in
http://www.postfix.org/MYSQL_README.html
we've included the ability to have Postfix reference multiple hosts for
access to a single mysql map. This will work if sites set up mirrored
mysql databases on two or more hosts. Whenever queries fail with an
error at one host, the rest of the hosts
Hi ,
if i use verify ( via internal network )
over smtp i want to have some fallback mech
so if verify fails for one host ( perhabs it is rebooting etc )
i wanna fallback to another host for verify
is this possible?
--
Best Regards
MfG Robert Schetterer
Germany/Munich/Bavaria
32 matches
Mail list logo
