Re: Login Failure Problems
Noah K <coderanger-/[email protected]> Sat, 10 Jul 2004 02:47:07 -0400
| Newsgroups | gmane.mail.yosucker.general |
|---|---|
| Message-ID | <[email protected]> |
Jeffrey F wrote: >Try a couple of things: >1) Login to yahoo mail manually and then try YoSucker again. >2) If that still does not work, edit lib/sputnik.pm. Go to line 1196 and >insert a new line that has "print;" by itself. (underneath the while) >3) Run YoSucker again but redirect the output to a file like this: > YoSucker > output.txt >4) Go back and remove the print; statement from sputnik.pm >5) Check the file for a "Set Cookie" and "Location" lines (near the top) if >you dont see either of these, try setting the FORCE4=1 option in your .conf file >6) It is still not working, send me your .conf file (remove your password) and >the output.txt file directly and I'll check it out > >-- Jeffrey >[email protected] > > >---------- Original Message ----------- >From: coderanger <coderanger-/[email protected]> >To: yosucker-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org >Sent: Wed, 07 Jul 2004 23:09:18 -0700 (PDT) >Subject: [Yosucker-general]Login Failure Problems > > > >>It seems that some of you have already seen this >>problem, but I can't get any of the existing patches >>to work, so this is my next try. I downloaded p59 a >>few days ago, having not used it in a while I figured >>I should probably upgrade, and set it up the way I >>wanted it. Everything was working just great, until a >>few hours ago, when it just stopped. Even with >>sneakysleep on, all it does is fail at the login. >> >>$ ./YoSucker >>Using inbox.conf >>SneakySleep is ON! >>Login. Failed!!! Check your username and password! >> >>After firing up ethereal, it seems like yosucker isnt >>even fully receiving the authentication pages (unless >>its supposed to do this, i dont really know). Does >>anyone have any ideas how to get this working again? >>Thanks you guys. >> >>__________________________________ >>Do you Yahoo!? >>Yahoo! Mail Address AutoComplete - You start. We finish. >>http://promotions.yahoo.com/new_mail >> >>------------------------------------------------------- >>This SF.Net email sponsored by Black Hat Briefings & Training. >>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - >>digital self defense, top technical experts, no vendor pitches, >>unmatched networking opportunities. Visit www.blackhat.com >>_______________________________________________ >>Yosucker-general mailing list >>Yosucker-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org >>https://lists.sourceforge.net/lists/listinfo/yosucker-general >> >> >------- End of Original Message ------- > > > > > Well it seems like yosucker is on the fritz again. I am attaching my output.txt and inbox.conf files. Hope you have better luck than I. For some reason it seems that the failures only happen at night, or maybe I just only notice at night (it normaly runs as a cron job). Thanks again. --Noah
output.txt
(text/plain, 688 B)
Using inbox.conf Login.HTTP/1.1 200 OK Date: Sat, 10 Jul 2004 06:38:52 GMT P3P: policyref="http://p3p.yahoo.com/w3c/p3p.xml", CP="CAO DSP COR CUR ADM DEV TAI PSA PSD IVAi IVDi CONi TELo OTPi OUR DELi SAMi OTRi UNRi PUBi IND PHY ONL UNI PUR FIN COM NAV INT DEM CNT STA POL HEA PRE GOV" Cache-Control: private Pragma: no-cache Expires: Thu, 05 Jan 1995 22:00:00 GMT Connection: close Content-Type: text/html Set-Cookie: B=3hqkkft0ev3ns&b=2; expires=Thu, 15 Apr 2010 20:00:00 GMT; path=/; domain=.yahoo.com Set-Cookie: Y=%2e; expires=Thu, 15 Apr 2010 20:00:00 GMT; path=/; domain=.yahoo.com Set-Cookie: T=z=0; expires=Thu, 01 Jan 1970 22:00:00 GMT; path=/; domain=.yahoo.com <html> <head>
inbox.conf2
(text/plain, 4.8 KB)
# sample.conf - Y(aho)o!Sucker configuration file # Copyright Dirk Diggler & Som One 1996-2001. All rides reserved. # Redistribution and use, with or without modification, # is permitted in the sense of GDWYWL # (GeneralDoWhateverYouWantLicense). # -z3r0- <Connect Info> # Set your YahooMail server address # IMPORTANT: Always leave mail.yahoo.com here # even if you normally use lets say mail.yahoo.it!!! HOST=mail.yahoo.com # Port YoSucker should connect to - if commented, defaults to 80/443 # Obsolete - note needed any more # PORT=8080 </Connect> <Login Details> # What's your YahooMail username/id? USERNAME=coderanger # Your Yahoo password - must be encrypted # (use EncPasswd utility to encrypt it) PASSWD= # Should I use a secure connection to login? # Default is 1 (Yes) - login is slower but more secure SSL=1 # Force four-step-login procedure? # This feature is needed with some accounts (e.g. rocketmail.com accounts) # Try FORCE4=1 when you experiece Abnormal Yahoo Mail behavior (02) errors during login # Options: 1 (4-step-login) / 0 (standard 3-step-login) #FORCE4=1 # Try to restore previous session, skip the login procedure # Default is 0 (No), YoSucker will login all the times # 1 (Yes) / 0 (No) RESPAWN=0 </Login> <Fetch Mail> # Where should I fetch the messages from? # CASE SENSITIVE!!! # Options are: Inbox, Sent, Trash, Draft, Bulk or any of your YM folders # Multiple comma separated folders are allowed (eg. BOX=Inbox,Bulk) BOX=Inbox,news,RPI_Forums # YoSucker will provide you with From:,To:,Subject: information for # the new messages in the DIGGEST folder, without actually fetching any message. # Apply the same options and restrictions as to BOX parameter # You DON'T have to add these folders to BOX parameter # DIGEST=Bulk # Messages will be saved (appended) in... # For procmail add procmail command line and set following PIPE to 1 # See FAQ... #OUTFILE=/home/coderanger/.yosucker/mail/coderanger OUTFILE=/var/spool/mail/coderanger # The next parameter determines whether your mail is written to # a file or redirected to another program such as "procmail" # Options: 0 (output to file) or 1 (out to pipe) # Leave 0 unless you know what you're doing PIPE=0 # Restore the read/unread status of the messages in your Yahoo box? # Note: Turning this feature ON may slow things down - especially switch 2! # 2 (Immediate) / 1 (After fetching all messages) / 0 (No) UNCHANGED=0 # Leave mail on server? - default is 1 (Yes) # If set to 0 fetched messages will be moved to # Trash folder on the server LEAVE=0 # Empty trash when logout? # 1 (Yes) / 0 (No!) TRASH=0 # Empty bulk folder when logout? # 1 (Yes) / 0 (No!) BULK=0 # Warn me when I use more then QUOTA percent of my mailbox space # Default is 85 # QUOTA=80 # LIMIT is a speed tuning option; See FAQ documentation for details # Default is 25; Set to 0 for no limit; 10-15 should be OK for daily use LIMIT=10 # Yahoo sometimes tends to lock up your account if your connection is fast # and you trying to download a lot of messages. Try to turn this feature on # if you experience YoSucker to freeze or return a lot of Header Corruption messages. # Turning this feature on can significantly slow YoSucker down. # Options: number of seconds to wait between two HTTP requests (default is 0) #SNEAKYSLEEP=5 # Quote any From_ occurence in the message body so the message doesn't get split # This may be necessary in some cases; see yosucker-general mail list for details # If unsure, leave the following line quoted or set to 0 # Options: leave message body asis = 0; quote From_ lines = 1 # QUOTEFROM=0 # Remove the "From " beginning of message delimiter (needed for some mail processing apps) # Leave commented or set to "0" unless you know EXACTLY what you're doin'!!! # Options: use delimiter = 0; NO delimiter = 1 # NOFROM=0 </Fetch> <Proxy Settings> # Set your proxy server address # PROXY=proxy.domain.com50 # Set your proxy port # PROXY_PORT=8080 # Set your proxy username # PROXY_USER=your_proxy_username # Set proxy password # Use EncProxyPasswd utility to encrypt it # PROXY_PASS=XXXXXXXXX </Proxy> <Other> # Select how much should Yo!Sucker show # Options: quiet = 0, normal = 1 DEBUG=1 # Choose an action (i.e. a command to execute when new mail arrives # ON_NEWMAIL="command attributes" # This command will be executed when YoSucker finds no new incoming messages # ON_NO_MAIL="command attributes" </Other> <Lethal Options> # IMPORTANT!!!! Setting the following CLEAN option to "KillEmAll" # will move all your messages stored in selected BOX into trash, # WITHOUT actually fetching the messages!!! Repository will be # ignored. # # BE VERY CAREFUL WITH THIS FEATURE!!! # # Never set CLEAN=KillEmAll unless you know EXACTLY what you're # doing. I warned ya! # # THIS IS A SEEK&DESTROY ALGORITHM!!! # # Options: KillEmAll (erase all messages), # all the other values will be ignored. CLEAN=0 </Lethal>