Hi all
Thank you for the various feedback I got.
I have re-worked my spamtrap SMTP dialogues.
But still I get weird behavior from yahoo servers. (not yahoo japan
this time, but servers like:
nm37.bullet.mail.ne1.yahoo.com
nm41-vm8.bullet.mail.ne1.yahoo.com
I see them repeatedly connecting, iss
On 30/10/16 21:22, Bill Cole wrote:
> On 30 Oct 2016, at 16:57, Jeremy Harris wrote:
>
>> On 30/10/16 20:31, Bill Cole wrote:
>>> On 30 Oct 2016, at 11:45, Jost Krieger wrote:
without the magical word ESMTP, no one is allowed to use EHLO.
>>>
>>> You've invented a non-existent rule. I hope no
On 30 Oct 2016, at 16:57, Jeremy Harris wrote:
On 30/10/16 20:31, Bill Cole wrote:
On 30 Oct 2016, at 11:45, Jost Krieger wrote:
without the magical word ESMTP, no one is allowed to use EHLO.
You've invented a non-existent rule. I hope no one has made the
blunder
of enshrining that non-rul
On 30/10/16 20:31, Bill Cole wrote:
> On 30 Oct 2016, at 11:45, Jost Krieger wrote:
>> without the magical word ESMTP, no one is allowed to use EHLO.
>
> You've invented a non-existent rule. I hope no one has made the blunder
> of enshrining that non-rule in code or teaching it as fact.
According
On 30 Oct 2016, at 11:45, Jost Krieger wrote:
Am 28.10.2016 um 15:18 schrieb valdis.kletni...@vt.edu:
On Fri, 28 Oct 2016 11:23:49 +0200, Benoit Panizzon said:
Nice, so Yahoo's mailservers are broken?
It's 2016. The mere fact it's sending HELO rather than EHLO is a
pretty good
indication th
On 10/28/2016 03:18 PM, valdis.kletni...@vt.edu wrote:
> On Fri, 28 Oct 2016 11:23:49 +0200, Benoit Panizzon said:
>
>> Nice, so Yahoo's mailservers are broken?
>
> It's 2016. The mere fact it's sending HELO rather than EHLO is a pretty good
> indication that it is either so decrepit or so def
>Nice, so Yahoo's mailservers are broken?
No. For one thing, Yahoo Japan is not the same company as Yahoo. There
is partial cross-ownership but they are operated separately.
For another, it's perfectly fine to send HELO if you're not planning
to ask for any optional features. These days that's
Am 28.10.2016 um 15:18 schrieb valdis.kletni...@vt.edu:
On Fri, 28 Oct 2016 11:23:49 +0200, Benoit Panizzon said:
Nice, so Yahoo's mailservers are broken?
It's 2016. The mere fact it's sending HELO rather than EHLO is a pretty good
indication that it is either so decrepit or so deficient that
On Fri, 28 Oct 2016 11:23:49 +0200, Benoit Panizzon said:
> Nice, so Yahoo's mailservers are broken?
It's 2016. The mere fact it's sending HELO rather than EHLO is a pretty good
indication that it is either so decrepit or so deficient that it can safely be
called broken.
The fact it doesn't eve
Hi Vladis
> in Appendix E). Only the EXPN and HELP commands are expected to
> result in multiline replies in normal circumstances, however
> multiline replies are allowed for any command.
>
> Note the last sentence.
Nice, so Yahoo's mailservers are broken?
-BenoƮt Panizzon-
--
I m
On Fri, 28 Oct 2016 11:09:27 +0200, Benoit Panizzon said:
> > PS: Maybe I am not supposed to send multiline prompts if a server
> > greets with HELO instead of EHLO?
>
> Note to self, next time read RFC before sending email...
>
> Old RFC 821 does not state, that a reply to HELO can be multiline.
>
> PS: Maybe I am not supposed to send multiline prompts if a server
> greets with HELO instead of EHLO?
Note to self, next time read RFC before sending email...
Old RFC 821 does not state, that a reply to HELO can be multiline.
After changing my spamtrap to only send one line in reply to HELO, it
Hello
I see a lot of connections from servers with hostnames ending in:
bullet.mail.(skk|kks).yahoo.co.jp, but no emails sent.
So I sniffed one of the connections.
I see this SMTP Handshake:
Me=> 200 Welcome to my server
Yahoo <= HELO (hostname of yahoo server)
Me=> 200-Hello I do suppo
13 matches
Mail list logo