jsolo1
Premium
join:2001-07-01 | reply to NormanS
Re: [E-Mail] SMTP.rcn.com silently not relaying, again
Perhaps if all servers required authentication, port 25 could be left open. No credentials, no smtp.
--
Insanity is living in a state of disillusion. |
|
negativeduck
Premium,VIP
join:2002-02-14
Centreville, VA
| You can infact relay mail from any mail-client as user@anydomain.com through smtp.rcn.com. Case by Case restrictions to this may be imposed as result of a compromised computer or host although in several of those cases enabling smtp auth will correct this.
If you are having a trouble sending email with your "From" setup as something other than rcn.com I would suggest enabling smtp auth and seeing if that helps with your problem.
We process a tone of email with customers doing just this scenerio so there is a possibility of specific 'one off' spam domains and what not. That being said if you want to message me some details around one of these 'dropped' emails we can research into where your mail is going.
--
Bryan Laird
Director Product and Technology |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
 ·Pacific Bell - SBC
| reply to jsolo1
said by jsolo1  :Perhaps if all servers required authentication, port 25 could be left open. No credentials, no smtp. How would your email service relay agents move email if they were required to authenticate the connection? The basic idea is to separate message submission (which may require authentication) from mail transfer (which should not require authentication).
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
jsolo1
Premium
join:2001-07-01
| Norman good point. My response was based on email submission, not transmission. You do bring up a good point though. Not sure how that would work. I imagine there may be a white list of sorts?
--
Insanity is living in a state of disillusion. |
|
negativeduck
Premium,VIP
join:2002-02-14
Centreville, VA
edit:
May 13th, @05:46PM
| Several mail hosts will not accept unauthenticated delivery requests from hosts that are NOT known isp's, or rather they specifically 'reject' or do not allow communication from a host that "appears" to be a dynamic IP pool connecting to their mail exchangers.. now this is a different scenario than say 'smtp' servers while fundamentally they same they like to serve different purposes.
IE if you run your own mail-server on a standard dynamically allocated IP there is a strong chance that you will never be able to deliver your email to alot of hosts. This is where smart-hosting and smart-relaying come in where you transfer your mail to a larger ISP for delivery to another large entity.
--
Bryan Laird
Director Product and Technology |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
| reply to jsolo1
Or read RFC 2476. That is the officially designated message submission port. Also, as a de facto standard, SMTPS (SMTP w/SSL) uses port 465.
Also read RFC 2821. SMTP does not require port 25, except for mail transfer.
If all E-mail Service Providers moved message submission to either the designated message submission port (RFC 2476), or even just any other port than port 25, it would be possible to reserve port 25 for mail transfer. Each gateway mail server can then decided for itself if a connecting mail host is trustworthy (allow), or not (deny).
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
