Host not found - Problemas ao receber e-mails de um determinado domínio

[mistymst]

Concordo, com o que voce disse.. e afinal, se o cara nao implementou de acordo o problema é DELE, e por causa desse tipo de pessoas que a Internet ainda é muito frágil.

Quanto a isso voce pode sim criar uma whitelist, mais ou menos assim:

smtpd_sender_restrictions =
check_sender_access hash:/etc/postfix/sender_checks,
reject_non_fqdn_sender,
reject_unknown_sender_domain,
permit

no meu caso isso se aplicar para os senders, no seu caso voce teria de fazer esta whitelist no:

smtpd_helo_restrictions =
permit_mynetworks,
reject_invalid_hostname,
reject_non_fqdn_hostname,
reject_unknown_hostname,
permit

mas nao me lembro exatamente qual seria a entrada do postfix... de uma olhada na documentacao e ve o que tu consegues... se nao conseguir me avisa ou beepa no gtalk que eu procuro

[Duca]

Estou vendo como se faz isso estou comendo a documentação do postfix e sites correlatos.
Cheguei até esse site: Blocking spammers with Postfix HELO controls

Contudo em vez de colocar REJECT eu coloquei ALLOW e nada , hehe.

Talvez não seja no helo_restriction como estou pensando se bem estou vendo ainda como resolver. Se alguem souber agradeço qualquer ajuda imediata, sim estou com pressa, hoje é sexta [:P]!!! uhsuahsuahsuas
To brincando, to pesquisando.

# cat /etc/postfix/checks/helo_access
mtomsw5.mto.na.mars ALLOW
isxmsw2.mtodom01.corp.mars ALLOW

# postmap checks/helo_access

ae depois no main.cf:

smtpd_helo_restrictions= permit_mynetworks,
permit_sasl_authenticated,
check_helo_access hash:/etc/postfix/helo_access,
reject_invalid_helo_hostname,
reject_non_fqdn_helo_hostname,
reject_unknown_helo_hostname

O cara enviou o e-mail e o comando Helo apresentou o mesmo erro.

Ab, DUca.

[mistymst]

Bom funciona assim:

mikael:/var/log# cat /etc/postfix/sender_checks
host.pappapak2.com 550 Spam not allowed.
educine.org.br 550 Bloqueado pelo administrador sob ordem do secretario.
earth.dotsi.pt 550 Servidor sendo abusado por spammers.
axx@gmail.com DISCARD


Ou voce coloca o "ERRO" especifica e voiola.. funciona que eh uma beleza... DISCARD discarta sem mensagens... e parece que OK aceita... deixa eu procurar aki.

[mistymst]

Aqui o:

Postfix Configuration - UCE Controls

dai ele te remete para:

Postfix manual - access(5)

ACCEPT ACTIONS
OK Accept the address etc. that matches the pattern.

all-numerical
An all-numerical result is treated as OK. This for-
mat is generated by address-based relay authoriza-
tion schemes such as pop-before-smtp.

REJECT ACTIONS
Postfix version 2.3 and later support enhanced status
codes as defined in RFC 3463. When no code is specified
at the beginning of the text below, Postfix inserts a
default enhanced status code of "5.7.1" in the case of
reject actions, and "4.7.1" in the case of defer actions.
See "ENHANCED STATUS CODES" below.

4NN text

5NN text
Reject the address etc. that matches the pattern,
and respond with the numerical three-digit code and
text. 4NN means "try again later", while 5NN means
"do not try again".

The reply code "421" causes Postfix to disconnect
immediately (Postfix version 2.3 and later).

REJECT optional text...
Reject the address etc. that matches the pattern.
Reply with $reject_code optional text... when the
optional text is specified, otherwise reply with a
generic error response message.

DEFER_IF_REJECT optional text...
Defer the request if some later restriction would
result in a REJECT action. Reply with "450 4.7.1
optional text... when the optional text is speci-
fied, otherwise reply with a generic error response
message.

This feature is available in Postfix 2.1 and later.

DEFER_IF_PERMIT optional text...
Defer the request if some later restriction would
result in a an explicit or implicit PERMIT action.
Reply with "450 4.7.1 optional text... when the
optional text is specified, otherwise reply with a
generic error response message.

This feature is available in Postfix 2.1 and later.

OTHER ACTIONS
restriction...
Apply the named UCE restriction(s) (permit, reject,
reject_unauth_destination, and so on).

BCC user@domain
Send one copy of the message to the specified
recipient.

If multiple BCC actions are specified within the
same SMTP MAIL transaction, only the last action
will be used.

This feature is not part of the stable Postfix
release.

DISCARD optional text...
Claim successful delivery and silently discard the
message. Log the optional text if specified, oth-
erwise log a generic message.

Note: this action currently affects all recipients
of the message. To discard only one recipient
without discarding the entire message, use the
transport(5) table to direct mail to the discard(8)
service.

This feature is available in Postfix 2.0 and later.

DUNNO Pretend that the lookup key was not found. This
prevents Postfix from trying substrings of the
lookup key (such as a subdomain name, or a network
address subnetwork).

This feature is available in Postfix 2.0 and later.

FILTER transport:destination
After the message is queued, send the entire mes-
sage through the specified external content filter.
The transport:destination syntax is described in
the transport(5) manual page. More information
about external content filters is in the Postfix
FILTER_README file.

Note: this action overrides the content_filter set-
ting, and currently affects all recipients of the
message.

This feature is available in Postfix 2.0 and later.

HOLD optional text...
Place the message on the hold queue, where it will
sit until someone either deletes it or releases it
for delivery. Log the optional text if specified,
otherwise log a generic message.

Mail that is placed on hold can be examined with
the postcat(1) command, and can be destroyed or
released with the postsuper(1) command.

Note: use "postsuper -r" to release mail that was
kept on hold for a significant fraction of $maxi-
mal_queue_lifetime or $bounce_queue_lifetime, or
longer. Use "postsuper -H" only for mail that will
not expire within a few delivery attempts.

Note: this action currently affects all recipients
of the message.

This feature is available in Postfix 2.0 and later.

PREPEND headername: headervalue
Prepend the specified message header to the mes-
sage. When more than one PREPEND action executes,
the first prepended header appears before the sec-
ond etc. prepended header.

Note: this action must execute before the message
content is received; it cannot execute in the con-
text of smtpd_end_of_data_restrictions.

This feature is available in Postfix 2.1 and later.

REDIRECT user@domain
After the message is queued, send the message to
the specified address instead of the intended
recipient(s).

Note: this action overrides the FILTER action, and
currently affects all recipients of the message.

This feature is available in Postfix 2.1 and later.

WARN optional text...
Log a warning with the optional text, together with
client information and if available, with helo,
sender, recipient and protocol information.

This feature is available in Postfix 2.1 and later.


Be cool

[Duca]

humm.. nisso eu dei uma olhada. E estudarei com mais afinco.

Eu fiz um teste aqui. Tirei as restrições do helo (comentei as linhas) e a mensagem do cara passou. Isso era esperado. Infelizmente tive que abrir as pernas.
Contudo preciso arranjar um jeito de nao perder minhas restricoes de HELO e deixar o cara liberado.
Bom, segundo informacões essa eh um empresa com milhares de usuarios e cada um com seu e-mail...bom e me disseram: "Pô, os caras tem milhares de contatos e só dá erro aqui?!"... bom ai já viu, né?
Trabalha peão.