not to stir this up any more but the things I have been reading are concerning AOL blocking incoming mail if it originates from certain IP blocks. Specifically Comcast and Roadrunner's dynamic ranges. So that if you sent out a message from a relay that was in one of those IP ranges (ie your mail server was connected to a dynamic IP through RoadRunner) it would not be allowed to be delivered to an AOL mailbox. I can see that considerably cutting down on AOL users getting spam, but it would make me ask the question is it worth the trouble to send this person this message if I were just an average mail user or small business running my own smtp agent. Their email tech policy states:
"AOL's mail servers will not accept connections from systems that use dynamically assigned IP addresses. " The really weird thing is a customer (using Roadrunner at his office) actually sent me a failure message he got back last night, asking if I was having a problem on my end: ... while talking to mailin-03.mx.aol.com.: <<< 554- (RTR:BB) The IP address you are using to connect to AOL is a dynamic <<< 554- (residential) IP address. AOL will not accept future e-mail transactions <<< 554- from this IP address until your ISP removes this IP address from its list <<< 554- of dynamic (residential) IP addresses. For additional information, <<< 554 please visit http://postmaster.info.aol.com. ... while talking to mailin-04.mx.aol.com.: >>> QUIT. Sorry I wasn't very clear in the original post. and thanks for the info Alan. ted Alan Fiebig wrote: > Sorry, that doesn't make a lot of sense to me... > > If someone, as in your example, is connected to AOL and is sending a > message to an MSN address, then at that specific point in time, they > are not your customer, they are an AOL customer and as such should be > using AOL's smtp servers, definatly not yours. > > In your post, you claim that would be eating up your bandwidth in both > directions, as the message came in from AOL and then as it left going to > MSN. If you are allowing people connected to AOL to send email to MSN via > your smtp server, then you are an open relay. > > I can't believe that's what you are actually stating, so I must be > misunderstanding your post, sorry. > > In any case, I had originally explained how I prevent my customers that are > connected to my dialup ports, and that therefore receive dynamic IPs, from > sending outbound traffic destined to port 25, thereby forcing them to use my > smtp > servers. I do not see how my blocking of locally connected customers to > external > port 25 connections relates to your example of someone connected to AOL and > sending > email to MSN. > > -Alan > > > > >I guess you are in the case where clients send mail from inside your network > >to the outside. > >So going through your smtp server costs you no extra bandwith anyway. > >But when they send mail from outside to outside ( for example my client has > >an internet access with AOL and sends a mail to MSN), > >I have no reason to get their mails relayed by my SMTP server, costing me > >bandwith in both sides ( incoming and resend ) + server utilization > > > >I think that some of us manage mail mostly for their own organization, while > >others act as small ISP, both situations are very different > > > >Benoit > > > >This is the discussion list for the IMS Free email server software. > > To unsubscribe send mailto:[EMAIL PROTECTED] > > > > Delivered by Rockliffe MailSite > > http://www.rockliffe.com/mailsite > > Rock Solid Software (tm) > > This is the discussion list for the IMS Free email server software. > To unsubscribe send mailto:[EMAIL PROTECTED] > > Delivered by Rockliffe MailSite > http://www.rockliffe.com/mailsite > Rock Solid Software (tm) This is the discussion list for the IMS Free email server software. To unsubscribe send mailto:[EMAIL PROTECTED] Delivered by Rockliffe MailSite http://www.rockliffe.com/mailsite Rock Solid Software (tm)
