Hello,
I'd like to limit the number of recipient a user can specify when sending
mail via our SMTP server.
In other words, I'd like to refuse the mail if the number of recipients
exceeds 10 for example.
To do so, I set smtpd_recipient_limit to 10.
To which value should I set smtpd_recipie
: Re: smtpd banner problem
On Tue, Jan 20, 2009 at 11:09:22AM +0300, Marco Tchi Hong wrote:
> But when I do : telnet myserver.tld 25 from another server I get :
> 220 **
> I don't find why I don't get the good banner.
You have a Cisco P
Hello,
In main.cf I have :
smtpd_banner = $myhostname ESMTP $mail_name (DATA TELECOM SERVICE)
But when I do : telnet myserver.tld 25 from another server I get :
220 **
I don't find why I don't get the good banner.
However, doing a telnet
Hello,
In main.cf I have :
smtpd_banner = $myhostname ESMTP $mail_name (DATA TELECOM SERVICE)
But when I do : telnet myserver.tld 25 from another server I get :
220 **
I don't find why I don't get the good banner.
However,
Hello,
I've got the same problem too since this morning...
I even tried to send mail to Yahoo with a test server with an IP address I
never used for a mail server, and I also get the 451 error message...
Marco
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] De la part
Hello,
i am currently doing a recipient check for domains relayed by my MX.
However, I'd like to skip this recipient check for mails sent from a
specific host.
How do I do this ?
Marco
>The client concurrency must not exceed the service concurrency, and
>virus scanning is CPU intensive, and in my experience this is too much.
>
>Of course in a multi-filter chain, if any of the filters are high
>latency, the combined filter latency can throttle the CPU demand
>of any CPU intensive
>These concurrency numbers are very high. Running A/V scanning
>at concurrency substantially higher than ~20 (on Dual CPU boxes) is
>generally counter-productive.
I have two Xeon 5160 Dual-Core 3,0 GHz on my box and 4Gb RAM.
About 500k mail go through this MX (50Gb traffic).
>What is the destinat
>KAV versions I've seen are not fully transparent proxies, they respond
>with banner 220 and EHLO 250 before making a downstream connection. The
>connection to the downstream server may happen as late as "." (after
>the content is scanned). It is certainly important to make sure that
>the configur
d the message to the content
filter ?
Marco
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] De la part de Wietse Venema
Envoyé : vendredi 26 septembre 2008 15:40
À : Postfix users
Objet : Re: Delivery delay problems
Marco TCHI HONG:
> Our problem is that mail st
Ok, so the problem is definitely a content filter problem ?
This has nothing to do with our Postfix configuration if I understand.
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] De la part de Wietse Venema
Envoyé : vendredi 26 septembre 2008 15:00
À : Marco TCHI
Hello,
I am using Postfix 2.3.3 and Kaspersky Antispam/Antivirus on our MX.
Mailboxes are hosted on another server.
The MX is relaying 250 domains or so, and it doesn't have resources
issues.
Our problem is that mail stay a long time in the active queue before the
content filter, but when it's sen
12 matches
Mail list logo