> I don't think so, if that were the case then I would not be able to send > mail from my local computer either.
You mean using your own computer as the mail server? If that is the case then I still think is the RDNS entry, if you look at python's smptlib.py source, it will try to do a socket.gethostbyname () but will catch the exception and default to 127.0.0.1 if there is a problem, that is why running it "locally" works, in fact, if you have python 2.4 available (which does not contain the exception catching) you will get a connection error, this will be an indication of it. hth On Oct 30, 1:45 pm, Thadeus Burgess <[email protected]> wrote: > I don't think so, if that were the case then I would not be able to send > mail from my local computer either. > > I created this test python script, using smtplib. Ran the file on my local > machine on the command line. Got the mail in my @gmail account. > > Uploaded said script to the server, ran it, and never recieved the email, > however the script outputs the same information. > > http://pastebin.com/m7ecf9179 > > Disabling iptables had no effect. > > -Thadeus > > On Fri, Oct 30, 2009 at 3:25 PM, Julio <[email protected]> wrote: > > > I think you need to contact the slicehost support folks and ask them > > to set RDNS for the new ip to your domain, I have a feeling that the > > external mail server (google?) is trying to rdns your domain (i.e. "is > > example.com's ip really who it says it is?) and the response is from > > one of slicehost's domains, thus making the delivery server thing you > > are a spammer. > > > On Oct 30, 12:57 pm, Thadeus Burgess <[email protected]> wrote: > > > It really makes no sense to me at all. > > > > When running the app locally, with the exact same settings, the email > > gets > > > delivered. However when placed on my slicehost server, only emails in the > > > same domain name get sent (I can log into the other servers webmail and > > the > > > email is there) > > > > So strange!... > > > > I checked iptables.. It has. > > > > Chain OUTPUT (policy ACCEPT) > > > target prot opt source destination > > > ACCEPT all -- anywhere anywhere > > > > I would try asking in another forum, however I have no clue what is > > causing > > > it, and don't know where to direct the question. > > > > -Thadeus > > > > On Fri, Oct 30, 2009 at 2:37 PM, Thadeus Burgess <[email protected] > > >wrote: > > > > > Yes. Still the same result, only emails within the same domain get > > > > delivered. What is weird is this was all working before the A record > > switch, > > > > which only should effect the root domain, not its subdomains. > > > > > -Thadeus > > > > > On Fri, Oct 30, 2009 at 2:34 PM, mr.freeze <[email protected]> > > wrote: > > > > >> Have you tried port 587 on the server? > > > > >> mail.settings.server = mail.example.com:587 > > > > >> On Oct 30, 2:27 pm, Thadeus Burgess <[email protected]> wrote: > > > >> > Also, mail.send() is always returning True. > > > > >> > -Thadeus > > > > >> > On Fri, Oct 30, 2009 at 2:25 PM, Thadeus Burgess < > > [email protected] > > > >> >wrote: > > > > >> > > Would anybody know why I can send mail using SMTP through > > Evolution, > > > >> yet > > > >> > > when using the exact same credentials for web2py Mail(), email > > does > > > >> not get > > > >> > > sent? > > > > >> > > It is quite odd actually though. > > > > >> > > mail.settings.server = mail.example.com:25 > > > >> > > mail.settings.sender = "[email protected]" > > > >> > > mail.settings.login = "[email protected]:mypass" > > > > >> > > Now when I use a mail.send() to other email accounts within the @ > > > >> > > example.com domain, the emails get delivered, however when I use > > > >> > > mail.send() to outside of the @example.com domain, liek @gmail > > and > > > >> @yahoo, > > > >> > > the emails never get delievered. > > > > >> > > Using evolution to send, the emails get sent, using squirrelmail > > > >> interface > > > >> > > works as well. Using gmail's smtp will not deliver emails outside > > of > > > >> the @ > > > >> > > example.com domain either. > > > > >> > > This was working until I switched the DNS A record of the root > > domain > > > >> to a > > > >> > > slicehost IP, yet leaving the mail subdomain A record pointing to > > the > > > >> mail > > > >> > > server. > > > > >> > > example.com. A 123.456.789.012 > > > >> > > mail.example.com A 321.321.355.012 > > > > >> > > With evolution working correctly, I am baffled. > > > > >> > > Has anybody else ever run into this? Or have an idea on what is > > going > > > >> on > > > >> > > here. > > > > >> > > -Thadeus > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
