NMSMTP

← →
sapsi (2003-04-22 10:26) [0]

Добрый день
Какое свойство NMSMTP отвечает за пароль для регистрации на почтовом сервере?
Спасибо

← →
sapsi (2003-04-22 10:56) [1]

НИкто не работал с почтой?

← →
sapsi (2003-04-22 11:45) [2]

Если сначала коннектиться через компоненту nmpop, там указать пароль, а на ее коннект сделать коннект для nmsmtp, то проходит для Rambler.
Но Yandex дает ошибку "Waiting for RCPT command".
Кто знает, что это такое

← →
sapsi (2003-04-22 15:49) [3]

действительно, странно, все молчат

← →
Дмитрий К.К. (2003-04-23 08:14) [4]

А ты в курсе, что некоторые SMTP-сервера требуют аутентификацию?

← →
sapsi (2003-04-23 08:18) [5]

Я то в курсе, поэтому и спрашиваю про универсальный алгоритм связи по SMTP с любым сервером.
Мне нужно отправить письмо. Адрес с которого будет отправлено, заранее неизвестен.
Все будет вводить пользователь, в том числе и пароль.

← →
Дмитрий К.К. (2003-04-23 08:22) [6]

Надо почитать RFC, что значит "Waiting for RCPT command". Подожди, сейчас посмотрю.

← →
Дмитрий К.К. (2003-04-23 08:34) [7]

Короче, RFC 821 (а если я не ошибаюсь, TNMSMTP работает через него) гласит:

RECIPIENT (RCPT)

This command is used to identify an individual recipient of
the mail data; multiple recipients are specified by multiple
use of this command.

The forward-path consists of an optional list of hosts and a
required destination mailbox. When the list of hosts is
present, it is a source route and indicates that the mail
must be relayed to the next host on the list. If the
receiver-SMTP does not implement the relay function it may
user the same reply it would for an unknown local user
(550).

When mail is relayed, the relay host must remove itself from
the beginning forward-path and put itself at the beginning
of the reverse-path. When mail reaches its ultimate
destination (the forward-path contains only a destination
mailbox), the receiver-SMTP inserts it into the destination
mailbox in accordance with its host mail conventions.

For example, mail received at relay host A with arguments

FROM:<USERX@HOSTY.ARPA>
TO:<@HOSTA.ARPA,@HOSTB.ARPA:USERC@HOSTD.ARPA>

will be relayed on to host B with arguments

FROM:<@HOSTA.ARPA:USERX@HOSTY.ARPA>
TO:<@HOSTB.ARPA:USERC@HOSTD.ARPA>.

This command causes its forward-path argument to be appended
to the forward-path buffer.

DATA (DATA)

The receiver treats the lines following the command as mail
data from the sender. This command causes the mail data
from this command to be appended to the mail data buffer.
The mail data may contain any of the 128 ASCII character
codes.

The mail data is terminated by a line containing only a
period, that is the character sequence "<CRLF>.<CRLF>" (see
Section 4.5.2 on Transparency). This is the end of mail
data indication.

The end of mail data indication requires that the receiver
must now process the stored mail transaction information.
This processing consumes the information in the reverse-path
buffer, the forward-path buffer, and the mail data buffer,
and on the completion of this command these buffers are
cleared. If the processing is successful the receiver must
send an OK reply. If the processing fails completely the
receiver must send a failure reply.

When the receiver-SMTP accepts a message either for relaying
or for final delivery it inserts at the beginning of the
mail data a time stamp line. The time stamp line indicates
the identity of the host that sent the message, and the
identity of the host that received the message (and is
inserting this time stamp), and the date and time the
message was received. Relayed messages will have multiple
time stamp lines.

When the receiver-SMTP makes the "final delivery" of a
message it inserts at the beginning of the mail data a
return path line. The return path line preserves the
information in the <reverse-path> from the MAIL command.
Here, final delivery means the message leaves the SMTP
world. Normally, this would mean it has been delivered to
the destination user, but in some cases it may be further
processed and transmitted by another mail system.

It is possible for the mailbox in the return path be
different from the actual sender"s mailbox, for example,
if error responses are to be delivered a special error
handling mailbox rather than the message senders.

The preceding two paragraphs imply that the final mail data
will begin with a return path line, followed by one or more
time stamp lines. These lines will be followed by the mail
data header and body [2]. See Example 8.

Special mention is needed of the response and further action
required when the processing following the end of mail data
indication is partially successful. This could arise if
after accepting several recipients and the mail data, the
receiver-SMTP finds that the mail data can be successfully
delivered to some of the recipients, but it cannot be to
others (for example, due to mailbox space allocation
problems). In such a situation, the response to the DATA
command must be an OK reply. But, the receiver-SMTP must
compose and send an "undeliverable mail" notification
message to the originator of the message. Either a single
notification which lists all of the recipients that failed
to get the message, or separate notification messages must
be sent for each failed recipient (see Example 7). All
undeliverable mail notification messages are sent using the
MAIL command (even if they result from processing a SEND,
SOML, or SAML command).

← →
sapsi (2003-04-23 10:27) [8]

Спасибо...
Но стало не сильно легче от этого.
Все равно написание кода, универсального для работы с любыми серверами под вопросом

← →
Дмитрий К.К. (2003-04-23 11:25) [9]

А такого и не может быть. В любом нормальном почтовике есть пункт меню "Настройка почтового ящика", а в нем юзер ставит соответствующие галочки или убирает их.

NMSMTP Найти похожие ветки