Howdy,
I've seen error "Client host rejected: Access denied" in many other
postings, but more than a day of reading has not led me to a solution.
A client is having issues sending mail to our server. I investigated
and found that postfix was rejecting the sending server with:
NOQUEUE: reject
Jesse Kretschmer wrote:
Howdy,
I've seen error "Client host rejected: Access denied" in many other
postings, but more than a day of reading has not led me to a solution.
A client is having issues sending mail to our server. I investigated
and found that postfix was rejecting the sending serv
* Noel Jones :
> Jesse Kretschmer wrote:
>> Howdy,
>> I've seen error "Client host rejected: Access denied" in many other
>> postings, but more than a day of reading has not led me to a solution.
>>
>> A client is having issues sending mail to our server. I investigated
>> and found that postf
>These are now my current settings from main.cf
Show "postconf -n" output.
>Jun 24 09:30:50 mail postfix/smtpd[44853]: NOQUEUE: reject: RCPT from
>bb02d1.eurorscg.com[69.74.116.40]: 554 5.7.1
>: Client host rejected: Access denied;
>from= to=<[1]xremov...@psyop.tv> proto=ESMTP
On Jun 24, 2009, at 2:23 PM, Jesse Kretschmer wrote:
Howdy,
I've seen error "Client host rejected: Access denied" in many other
postings, but more than a day of reading has not led me to a solution.
A client is having issues sending mail to our server. I
investigated and found that postf
Thanks for the many quick responses.I should have started with this:
# postconf -n
broken_sasl_auth_clients = yes
command_directory = /usr/local/sbin
config_directory = /usr/local/etc/postfix
content_filter = smtp-amavis:[127.0.0.1]:10024
daemon_directory = /usr/local/libexec/postfix
data_director
* Jesse Kretschmer :
> Thanks for the many quick responses.I should have started with this:
>
> # postconf -n
Nothing in here cold cause what you see.
Show master.cf please
> smtpd_recipient_restrictions = permit_mynetworks permit_sasl_authenticated
> reject_unauth_destination check_client_ac
Ralf Hildebrandt wrote:
Nothing in here cold cause what you see.
Show master.cf please
[r...@mail ~]# sed -e '/^#/d' -e '/^\s*$/d' /usr/local/etc/postfix/main.cf
soft_bounce = no
content_filter=smtp-amavis:[127.0.0.1]:10024
queue_directory = /var/spool/postfix
command_directory = /usr/local/sbin
* Jesse Kretschmer :
> Ralf Hildebrandt wrote:
>> Nothing in here cold cause what you see.
>> Show master.cf please
> [r...@mail ~]# sed -e '/^#/d' -e '/^\s*$/d' /usr/local/etc/postfix/main.cf
This hardly shows master.cf :)
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité
Ralf Hildebrandt wrote:
* Jesse Kretschmer :
Ralf Hildebrandt wrote:
Nothing in here cold cause what you see.
Show master.cf please
[r...@mail ~]# sed -e '/^#/d' -e '/^\s*$/d' /usr/local/etc/postfix/main.cf
This hardly shows master.cf :)
* Jesse Kretschmer :
>Oops. I've never actually touched the master.cf file, so when I read the
>line, I just assumed main.cf.
>
>Thanks for bearing with me. Without further ado:
>
># sed -e '/^#/d' -e '/^\s*$/d' /usr/local/etc/postfix/master.cf
>smtp inet n -
Jesse Kretschmer wrote:
Thanks for the many quick responses.
I should have started with this:
# postconf -n
delay_warning_time = 10m
Quite short, but won't break anything.
maximal_queue_lifetime = 2d
recommended minimum is 3 days, default is 5 days. If you have
lots of undeliverable mail
Ralf Hildebrandt wrote:
* Jesse Kretschmer :
Oops. I've never actually touched the master.cf file, so when I read the
line, I just assumed main.cf.
Thanks for bearing with me. Without further ado:
# sed -e '/^#/d' -e '/^\s*$/d' /usr/local/etc/postfix/master.cf
smtp inet
Noel Jones wrote:
Jesse Kretschmer wrote:
# postconf -n
delay_warning_time = 10m
Quite short, but won't break anything.
maximal_queue_lifetime = 2d
recommended minimum is 3 days, default is 5 days. If you have lots of
undeliverable mail in your queue, address the source of the
undelive
* Noel Jones :
> Jesse,
>
> You may find it helpful to add
>-o syslog_name=postfix-smtps
> to the above options to differentiate logging from the smtps service.
Amen to that!
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benja
* Jesse Kretschmer :
>>>smtp inet n - n - - smtpd
>>>smtps inet n - n - - smtpd
>>> -o smtpd_tls_wrappermode=yes
>>> -o smtpd_sasl_auth_enable=yes
>>> -o smtpd_client_restrictions=permit_sasl_authenticate
Jesse Kretschmer wrote:
Ralf Hildebrandt wrote:
smtp inet n - n - - smtpd
smtps inet n - n - - smtpd
-o smtpd_tls_wrappermode=yes
-o smtpd_sasl_auth_enable=yes
-o smtpd_client_restrictions=permit_sasl_au
Noel Jones wrote:
The "smtps" service is for your own mail clients to use. This is a
deprecated method of encryption sometimes called SSL (not to be
confused with HTTPS/SSL) in some mail clients. Clients that don't
authenticate via SASL should be rejected.
Typically only "older" MUAs and s
Noel Jones wrote:
The "smtps" service is for your own mail clients to use. This is a
deprecated method of encryption sometimes called SSL (not to be
confused with HTTPS/SSL) in some mail clients. Clients that don't
authenticate via SASL should be rejected.
Typically only "older" MUAs and s
Jesse Kretschmer wrote:
If you can explain what you mean by "allow these tls connections" we
can give more pointers.
Looking at the logs, the company that is having issues with our mail
server only has issue occasionally. It appears to be one server in
particular. This one server always start
Noel Jones wrote:
If not, they *should not* be connecting to your smtps port; their mail
server is misconfigured and it's not your problem.
This was exactly the problem. I did some troubleshooting with the mail
admin of the sending server. One of their servers was attempting to
connect on por
21 matches
Mail list logo
