Happily Microsoft have fixed their smtps stupidity, so you only need
to support it on the server if you need to support users running old
versions of Outlook etc. There was never anything particularly wrong
with smtps, apart from a dogma in the IETF that it is architecturally
wrong. The
Raoul Bhatia [IPAX] wrote:
i recently had the problem that an lotus notes server insisted on
sending emails to one of our clients via port 465. so having mandatory
authentication there actually broke delivery for an exchange sender.
Leave it broken for the other end that is. Only way to
On 22 Apr 2010, at 00:07, Franck Martin fra...@genius.com wrote:
Consider also smtps port which should be treated like smtp port and
not like submission port, or simply do not listen on smtps as TLS is
available on smtp port via esmtp.
Er, no. TLS-on-connect aka smtps (as opposed to
On 22.04.2010 13:07, Tony Finch wrote:
Er, no. TLS-on-connect aka smtps (as opposed to STARTTLS) is only used
to support Microsoft MUAs that are more than a couple of years old. They
only supported STARTTLS on port 25 and insisted on using the deprecated
TLS-on-connect mode on all other ports.
On 4/21/2010 8:16 PM, Suresh Ramasubramanian wrote:
The MAAWG BCPs have far more available than one of the worst
maintained blacklists that has ever been in existence.
For example:
http://www.maawg.org/sites/maawg/files/news/MAAWG_Port25rec0511.pdf
d/
--
Dave Crocker
Brandenburg
Hello all,
At our ISP operation, we are seeing increasing levels of traffic in our
outgoing MTA's, presumably due to spammers abusing some of our subscribers'
accounts. In fact, we are seeing connections from IPs outside of our network
as many as ten times of that from inside IPs. Probably all of
On 21/04/10 10:49 -0300, Claudio Lapidus wrote:
Hello all,
At our ISP operation, we are seeing increasing levels of traffic in our
outgoing MTA's, presumably due to spammers abusing some of our subscribers'
accounts. In fact, we are seeing connections from IPs outside of our network
as many as
spammers if they are hijacking
the users local email client settings.
-Mike
-Original Message-
From: Claudio Lapidus [mailto:clapi...@gmail.com]
Sent: Wednesday, April 21, 2010 9:49 AM
To: nanog@nanog.org
Subject: Mail Submission Protocol
Hello all,
At our ISP operation, we are seeing
On Apr 21, 2010, at 9:57 AM, Dan White wrote:
On 21/04/10 10:49 -0300, Claudio Lapidus wrote:
Hello all,
At our ISP operation, we are seeing increasing levels of traffic in our
outgoing MTA's, presumably due to spammers abusing some of our subscribers'
accounts. In fact, we are seeing
On Wed, Apr 21, 2010 at 10:49:07AM -0300, Claudio Lapidus wrote:
Hello all,
Hello Claudio,
At our ISP operation, we are seeing increasing levels of traffic in our
outgoing MTA's, presumably due to spammers abusing some of our subscribers'
accounts. In fact, we are seeing connections from
any
further
email (with exception to support-staff for example).
-Mike
-Original Message-
From: Claudio Lapidus [mailto:clapi...@gmail.com]
Sent: Wednesday, April 21, 2010 9:49 AM
To: nanog@nanog.org
Subject: Mail Submission Protocol
Hello all,
At our ISP operation, we
clients
-Mike
-Original Message-
From: Claudio Lapidus [mailto:clapi...@gmail.com]
Sent: Wednesday, April 21, 2010 9:49 AM
To: nanog@nanog.org
Subject: Mail Submission Protocol
Hello all,
At our ISP operation, we are seeing increasing levels of traffic in our
outgoing MTA's, presumably
On Wed, Apr 21, 2010 at 10:49:07AM -0300, Claudio Lapidus wrote:
At our ISP operation, we are seeing increasing levels of traffic in our
outgoing MTA's, presumably due to spammers abusing some of our subscribers'
accounts. [snip]
A discussion on this topic is happening on spam-l at the
On 21 apr 2010, at 16.14, Leen Besselink wrote:
We added SSL to our SMTP-service and tell our customers to use SSL (not TLS)
with authentication and have the mailserver listen on the TCP-ports which
the mailclients pick for that (of which their are a few if I'm not mistaken).
Assuming that
On 4/21/2010 6:49 AM, Claudio Lapidus wrote:
So we are considering ways to further filter this traffic. We are evaluating
implementation of MSA through port 587.
RFC 5068, Email Submission Operations: Access and Accountability Requirements,
is a BCP. It specifies authenticated port 587
/rblcheck.php and enter your AS/network and see how
many of your clients are spamming due to mainly botnets.
- Original Message -
From: Dave CROCKER d...@dcrocker.net
To: nanog@nanog.org
Sent: Thursday, 22 April, 2010 10:17:28 AM
Subject: Re: Mail Submission Protocol
On 4/21/2010 6:49 AM, Claudio
Log and monitor all that you can. And watch for a large number of IPs
logging into an account over a day (over a set limit - even across
country - that takes into account home - blackberry - airport lounge
- airport lounge in another country - hotel - RIPE meeting venue
type scenarios).
And
: Mail Submission Protocol
Log and monitor all that you can. And watch for a large number of IPs
logging into an account over a day (over a set limit - even across
country - that takes into account home - blackberry - airport lounge
- airport lounge in another country - hotel - RIPE meeting venue
type
: nanog@nanog.org
Sent: Thursday, 22 April, 2010 1:35:56 PM
Subject: Re: Mail Submission Protocol
Log and monitor all that you can. And watch for a large number of IPs
logging into an account over a day (over a set limit - even across
country - that takes into account home - blackberry
19 matches
Mail list logo
