 |
| Prev-20 | Home | Next-20 |
| Prev-20 | Home | Next-20 |
| Prev-Msg | Prev-Thread | Postfix-users | Nov-2007 | Next-Thread | Next-Msg |
| Subject: | Re: Recipient validation |
| Group: | Postfix-users |
| From: | mouss |
| Date: | 30 Nov 2007 |
>> in fact, it was the filter that was dropping the connection
>> from postfix. possibly because the filter was overloaded...
>>
>> you have a limit of 70 connections to the filter. does the
>> filter support this many number?
>>
>> Please do read amavsid-new README.postfix. it explains many
>> parameters that could help you.
>
> I'm not using amavisd-new.
>
Rocco,
It would pay if you read more carefully. In a previous email, I said
-> see amavisd-new README.postfix. _EVEN _IF_ you don't use amavisd-new,
-> the recommended options are a plus.
Most of the recommandations in the cited document apply to any smtp/lmtp
based content filter.
> Summarizing. With this master.cf:
>
> localhost:10026 inet n - n - 70 smtpd
> -o smtpd_use_tls=no
> -o content_filter=
> -o smtpd_timeout=$imss_timeout
> -o myhostname=fqdn
> -o mynetworks=127.0.0.1
> -o smtpd_delay_reject=no
> -o smtpd_client_restrictions=permit_mynetworks,reject
> -o smtpd_sender_restrictions=
> -o smtpd_recipient_restrictions=permit_mynetworks,reject
> -o receive_override_options=no_unknown_recipient_checks,
> no_address_mappings
>
> I have huge delays in delivery emails.
>
I said:
-> you have a limit of 70 connections to the filter. does the filter
-> support this many number?
> While with this settings in master.cf:
>
> localhost:10026 inet n - n - 70 smtpd
> -o smtpd_use_tls=no
> -o content_filter=
> -o smtpd_timeout=$imss_timeout
> -o local_recipient_maps=
> -o myhostname=IMSA
> -o smtpd_client_restrictions=
> -o smtpd_sender_restrictions=
>
> As you and Victor says, there some things to adjust.
>
> Really, I have noticed that with the latter settings my server tries to
> verifies recipient als on the outgoing messages.
Fix this. only do recipient verification on your domains. either use
reject_unverified_recipients after reject_unauth_destination or replace
it wth a check like this:
check_recipient_access hash:/etc/postfix/verify_domains
== verify_domains
mydomain1.example reject_unverified_recipients
mydomain2.example reject_unverified_recipients
...
> And fails If set an
> hostname that is not a fqdn:
>
> 'xxx_yyy' 29/11/2007 22.29
>
> 450 <xxx_yyy>: Recipient address rejected:
> undeliverable address: host mx02.jumpy.it[213.215.144.92] said: 554
> 5.1.8 <postmaster>: Sender address rejected: Domain not found
> (in reply to RCPT TO command)
>
what is the "@no.fqdn" thing? my server would reject this mail as well.
use valid address.
> Moreover, if I telnet on port 25 a mail server like
> mx02.jumpy.it[213.215.144.92], I get an high delay to get answer for
> each SMTP command I send.
>
maybe this server is throttling you because you're abusing their
resource by your recipient verification probes.
> Are there any relationship between this oddity and the settings?
>
you need to see what is causing the delay: what happens to an email from
the time it enters the system until it gets out.
| Prev-Msg | Prev-Thread | Postfix-users | Nov-2007 | Next-Thread | Next-Msg |