* Chris Horry :
> On 9/18/2012 16:36, Ralf Hildebrandt wrote:
[postscreen after-220 tests]
> > Those tests are useful, nonetheless :)
>
> Definitely, my only problem is that I've seen greylisting cause
> legitimate (admittedly due to poorly configured mail servers) mail to
> get lost.
I consider
I have created a policy service, which checks quota, returning 'reject' if
the mailbox is full, and 'dunno' otherwise.
smtpd_(data|recipient)_restrictions =
check_policy_service unix:private/checkfull
And it's all working fine.
However, I only want that policy to trigger for incoming mail - m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/18/2012 16:36, Ralf Hildebrandt wrote:
> * Chris Horry :
>
>> Ralf,
>>
>> I knew I'd missed something, thanks for the clarification.
>
> Those tests are useful, nonetheless :)
>
Definitely, my only problem is that I've seen greylisting cause
* Chris Horry :
> Ralf,
>
> I knew I'd missed something, thanks for the clarification.
Those tests are useful, nonetheless :)
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benjamin Franklin
Hindenburgdamm 30 | D-12203 Berlin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/18/2012 16:33, Ralf Hildebrandt wrote:
> * Chris Horry :
>> Since enabling tlsproxy+postscreen I'm seeing greylisting on TLS
>> connections:
> ...
>
>> I don't seen anything about this in the postscreen documentation
>
> "Tests after the 220 SM
* Chris Horry :
> Since enabling tlsproxy+postscreen I'm seeing greylisting on TLS
> connections:
...
> I don't seen anything about this in the postscreen documentation
"Tests after the 220 SMTP server greeting"
says
Important note: deep protocol tests are disabled by default. They are
more intr
Chris Horry:
> Sep 18 16:06:10 smitty postfix/postscreen[11721]: NOQUEUE: reject:
> RCPT from [50.31.151.68]:39082: 450 4.3.2 Service currently
> unavailable; from=,
> to=, proto=ESMTP, helo=
That has nothing to do with tlsproxy.
Instead, you have some after-220-greeting tests turned on.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Since enabling tlsproxy+postscreen I'm seeing greylisting on TLS
connections:
Sep 18 16:06:03 smitty postfix/postscreen[11721]: CONNECT from
[50.31.151.68]:39082
Sep 18 16:06:10 smitty postfix/tlsproxy[11727]: CONNECT from
[50.31.151.68]:39082
Sep 18
Hi,
I have running a postfix+mysql+dovecot+postfixadmin+roundcube server
and it working well.Now in postfixadmin i set a domain1.com alias to
domain2.com and create u...@domain2.com.I think that if someone send a
mail to u...@domain1.com,i can receive the mail in u...@domain2.com.but
i got
Hi,
among our userbase are a couple of thousand people that forward their
mail to other domains (mostly freemails). This has the obvious and
well-known downside that any spam going to this user looks like it
originated in our network, which might lead to some reputation problems.
And of course the
Le 18/09/2012 16:31, Wietse Venema a écrit :
St?phane MERLE:
T 5 10 20 40 80 160 320 640 1280 1280+
TOTAL 300 0 0 0 1 4 19 31 14 98 154
Postfix will remove/return the mail after delivery tempfails AND
the message is already more than xxx_life_time old.
You have more mai
St?phane MERLE:
> T 5 10 20 40 80 160 320 640 1280 1280+
> TOTAL 300 0 0 0 1 4 19 31 14 98 154
Postfix will remove/return the mail after delivery tempfails AND
the message is already more than xxx_life_time old.
You have more mail in the queue than Postfix can process in you
On 9/18/2012 8:38 AM, Stéphane MERLE wrote:
> Hi,
>
> I think that I miss something here, we have those 2 parameters set
> in our postfix configuration :
>
> bounce_queue_lifetime = 8h
> maximal_queue_lifetime = 8h
This is a very short lifetime; the default is 5 days. People who set
a very short
Hi,
I think that I miss something here, we have those 2 parameters set in
our postfix configuration :
bounce_queue_lifetime = 8h
maximal_queue_lifetime = 8h
so, I thought that no mail will stay in the queue after 8h, however, I
can see that mails are in the active queue for more than 1280 mi
edgardo.ghibaudo:
[ Charset ISO-8859-15 unsupported, converting... ]
> I have defined virtual users in MySQL db for the domain in
> two different Postfix servers.
> I would like to send email from a virtual user in Server1 to a virtual
> user in Server2.
> When I try to send an email I receive t
On Tue, 18 Sep 2012 13:31:14 +0200
edgardo.ghibaudo articulated:
> I have defined virtual users in MySQL db for the domain
> in two different Postfix servers. I would like to send email from a
> virtual user in Server1 to a virtual user in Server2. When I try to
> send an email I receive the foll
I have defined virtual users in MySQL db for the domain in
two different Postfix servers.
I would like to send email from a virtual user in Server1 to a virtual
user in Server2.
When I try to send an email I receive the following error
message:*Recipient address rejected: User unknown in virtua
17 matches
Mail list logo
