Yakov Lerner wrote:
Me too. I think it means that (1) "email address at KNBT that is
unavailable or no longer valid", and (2) it's time for you to add
special filtering rule to your mail reader. I mean, who said mail bot
cannot post to mailing list ?
Yakov
[...]
The mailbot is not posting to the mailing list. What happens is at follows:
1. Yakov Lerner posts to mailing list
2. Vim mailbot sends it to all subscribed addresses.
3. One of those subscribers is (let's say) [EMAIL PROTECTED]
4. KNBT mail router accepts the mail.
5. KNBT mail router (maybe another one) notices that [EMAIL PROTECTED] is
unknown
6. KNBT mail router sends a pseudo-bounce to the apparent author, i.e., Yakov
Lerner. This is the message that you see; the vim mailbot doesn't.
This points at a misconfiguration in KNBT's routers: what should happen is as
follows:
...
3. During handshaking between Vim mailbot and KNBT incoming mail exchanger,
the latter notices that [EMAIL PROTECTED] is unknown and immediately gives a 550
(or something) error reply to the "RCPT TO [EMAIL PROTECTED]" line.
4. The mail itself is not transmitted to KNBT
5. Vim mailbot notices that [EMAIL PROTECTED] couldn't be reached and remembers
which list post couldn't be sent to him.
6. After some time (or some number of failed emails), Vim listbot tries to
send a recap email to [EMAIL PROTECTED] telling him which mails were rejected.
7. Again, KNBT incoming mail exchanger refuses the transaction.
8. Vim listbot tries to send a probe email to [EMAIL PROTECTED]
9. Again, KNBT inmx refuses the transaction
10. Vim listbot unsubscribes [EMAIL PROTECTED]
This second scenario is much cleaner in that we never see any pseudo-bounces,
and eventually the unsubscribe does take place.
Best regards,
Tony.
