Jump to content

You wake up with Megan Fox in your bed(w/o knowing what happened yesterday), what you do?  

107 members have voted

  1. 1. You wake up with Megan Fox in your bed(w/o knowing what happened yesterday), what you do?

    • I rape her
      54
    • I ask for a dinner
      20
    • Boring, i send her home
      7
    • I'm too young to think about sex, i ask for a autograph though
      3
    • Obviously i still rape her, its a hallucination
      23


Recommended Posts

Posted

Contact php

 

<?php
//-----------------Getting data sent by flash---------------------
foreach ($_POST as $key => $value){

	if ($key != 'mail_to' && $key != 'smtp_server' && $key != 'smtp_port' && $key != 'mail_from' && $key != 'mail_subject' && $key != 'plain_text'){

		$mail_body .= '<b>'.str_replace('_',' ',$key).'</b>:<br/>';

		$mail_body .= ''.stripslashes($value).'<br/>';
	}
}
//-----------------------------------------------------------------



$message = '<html><body>'.$mail_body.'</body></html>'; //  mail body

//------------if plain text is set to true removing html tags------
if ($_POST['plain_text']=='true') {

$message = str_replace('<br/>',"\r\n", $message);

$message = strip_tags($message);

//------------------------------------------------------------------
} else {
//----otherwise composing message headers---------------------------
$headers  = 'MIME-Version: 1.0' . "\r\n";

$headers .= 'Content-type: text/html; charset=iso-8859-1' . "\r\n";
//------------------------------------------------------------------
}

//------------setting conf data-------------------------------------
$to = $_POST['mail_to'];

$from = $_POST['mail_from'];

$subject = $_POST['mail_subject'];

$smtp_server = $_POST['smtp_server'];

$smtp_port = $_POST['smtp_port'];
//------------------------------------------------------------------

//---------setting header info--------------------------------------
$headers .= 'To: '.$to. "\r\n";

$headers .= 'From: Site visitor ' .$from. "\r\n";
//------------------------------------------------------------------


if (mail($to, $subject, $message, $headers)){ // sending mail

print('&mail=1');  //succes

} else {

print('&mail=0');//failure

}

?>

 

form04Configuration

<?xml version="1.0" encoding="utf-8"?>
<!--
  --	Please read this information to learn how to set up the contact form integrated
  --	into the template.
  --	
  --	This readme file explains in details the meaning of the settings that can be
  --	done in the fcContactFormConfiguration.xml configuration file.
  --	
  --	It is recommended for you to use an XML editor to make changes to this file
  -- 	because it’s less possible to make an error in the markup which can cause to
  --	a not working contact form.
  -->
<contactFormConfiguration> 
	   
<!--
  --	An e-mail address which will be used to receive messages from your contact form.
  --	You can specify several e-mail addresses separating them with a comma.
  --	For example: first_email@domain.com, second_email@domain.com, third@domain.com
  -->
<emailTo>your_email@domain.com</emailTo>

<!--
  --	A server script type which will process sending e-mails. It depends on your
  --	hosting and in the current version of the contact form it is allowed to use
  --	two types:  php (Apache, PHP Hosting); asp (IIS web server, ASP).
  -->
<serverProcessorType>php</serverProcessorType>

<!--
  --	A name of the script file which process sending e-mails on your server (without
  --	extension). The name contact is used by default.
  -->
<serverProcessorFileName>contact</serverProcessorFileName>

<!--
  --	Set whether to validate only required fields (true/false).  The default value is
  --	true which means the not required fields of your contact form will not be validated.
  --	For example if the e-mail field of your form is set as not required (imagine it)
  --	the form will be processed even if the user types in an incorrect e-mail address.
  -->
<validateRequiredOnly>false</validateRequiredOnly>

<!--
  --	Set whether to submit the form when the Enter key is pressed even if the focus is
  --	not on the Submit button (true/false).
  -->
<submitFormOnEnter>false</submitFormOnEnter>

<!--
  --	Text showing to the user when the form is submitted without any errors.
  -->
<messageSentText>Thank you for your message.</messageSentText>

<!--
  --	Text showing in case the form is not submitted because of a server error.
  -->
<messageSentFailedText>Sorry, your message couldn't be sent</messageSentFailedText>

<!--
  --	Text your visitor will see while waiting till the processing is over.
  -->
<formProcessingText>processing...</formProcessingText>

<!--
  --	Your SMTP server (for ASP only).
  -->
<smtpServer>localhost</smtpServer>

<!--
  --	Your SMTP port (for ASP only).
  -->
<smtpPort>25</smtpPort>

<!--
  --	Set whether to send the message as a plain text (true) or as HTML (false).
  -->
<plainText>false</plainText>

<!--
  --	ID of the input field (in the structure XML file) to use for the “from: ”
  --	or email to use instead (for example: mailfrom@domainname.com).
  -->
<emailFromSource>2</emailFromSource>

<!--
  --	Subject of the e-mails that will be sent through this contact form or ID of
  --	the input field (in the structure XML file) to use for the “subject: ” label
  --	in your e-mail client.
  -->
<subjectSource>Contact Form from your site</subjectSource>

<!--
  --	Validation error messages that are showing to the user when the form fails to
  --	validate. The form supports different types of validators. You can change the
  --	text of the error messages the validators produce here.
  --
  --	You can use the {LABEL} keyword in these messages. It will replace it with the
  --	label value of the field where an error occurs.
  -->
<validationErrorMessages>
	    
	<!--
	  --	A required field is not filled in.
	  -->
	<message type="fieldIsRequired">{LABEL} is required.</message>

	<!--	
	  --	The specified e-mail address is incorrect.
	  -->
	<message type="emailNotValid">{LABEL} - is not valid email address.</message>

	<!--
	  --	The specified number of characters in a field is less than a required minimum.
	  -->
	<message type="minCharsLimitError">{LABEL} - The specified number of characters in a field is less than a required minimum.</message>

	<!--
	  --	The specified string does not match with the regular expression.
	  -->
	<message type="reqExpError">{LABEL} - The specified string does not match with the regular expression.</message>

	<!--
	  --	The specified number is greater than an acceptable biggest number for this field.
	  -->
	<message type="biggerThanMaxError">{LABEL} - The specified number is greater than an acceptable biggest number for this field.</message>

	<!--
	  --	The specified number is lower than an acceptable lowest number for this field.
	  -->
	<message type="lowerThanMinError">{LABEL} - The specified number is lower than an acceptable lowest number for this field.</message>

	<!--
	  --	The data is not a number.
	  -->
	<message type="notANumberError">{LABEL} - The data is not a number.</message>

	<!--
	  --	The specified number must not be negative.
	  -->
	<message type="negativeError">{LABEL} - The specified number must not be negative.</message>

	<!--
	  --	The minimum number of variants is not selected
	  -->
	<message type="minRequirementError">{LABEL} - The minimum number of variants is not selected</message>

	<!--
	  --	The number of variants selected exceeds the maximum
	  -->
	<message type="maxRequirementError">{LABEL} - The number of variants selected exceeds the maximum</message>

	<!--
	  --	The fields that should be equal do not match
	  -->
	<message type="shouldBeEqualError">{LABEL} - values do not match</message>

	<!--
	  -- 	The date has wrong format.
	  -->
	<message type="dateIsNotValidError">{LABEL} - date has wrong format</message>

</validationErrorMessages>

</contactFormConfiguration>

 

:(

 

any idea if i use hotmail i tested many stmp servers and ports but nothng :(

Guest
This topic is now closed to further replies.



  • Posts

    • 🏆 UPDATE: CLAN RACE — R$ 300 (PIX in Brazil, or the equivalent in USDT/PayPal) for the first clan ready for World B PvP Worlds opens on Friday, September 25, 19:00 BRT (GMT-3). Everyone starts together, from scratch. The challenge: the first clan with 9 members ready to enter World B wins. Ready = level 51, World C registered and the full C set equipped (weapon, armor and jewelry) with at least 3 attributes on each piece. Only Queen Ant stands between you and World B. Rules: main character only; 9 different people, each on their own PC; the server records the exact time each member became ready. Deadline: October 14. Sign up your clan on our Discord (link on the site): l2mog.com/pvp
    • 🚀 L2-Gold Custom PvP – Beta Test is LIVE! 🚀 Hey guys! We are opening a brand new Custom PvP server and looking for passionate players to help us test it out before the official grand opening! 💥 What we offer: High Rates & Custom PvP Gameplay Custom NPC Buffer, GM Shop & Global GK Balanced classes and epic custom items Interlude with c4 skills 🎁 Beta Rewards: Every active tester who reports bugs or gives feedback will receive Exclusive Custom Rewards on the official launch day! 🛑 No website needed yet! All files, patch, and support are inside our Discord. 🔗 Join Beta Test Here: [https://discord.gg/9qkSxQtTq]
    • "CAN YOU DO A BULGARIAN REVOLUT?" – WE DID. FIRST DRAFT, NO EDITS The request came in short: a photo of a bank card, Bulgaria, Revolut. We said yes and asked the only question that matters – what data. The client was on the road, asked for a couple of hours, then sent the lot: number, expiry, CVV, payment system, bank, cardholder name. Then came the part the client never sees: - ran the number through Luhn – the check digit has to add up, otherwise the card is dead the second anything automated looks at it - matched the BIN to the issuer: Revolut in Bulgaria isn't a "local bank", the cards run through Revolut Bank UAB. The number range has to actually belong there, not just start with the right digit - built the current design, not a five-year-old picture: vertical layout, flat laser print instead of embossing, correct chip module, contactless mark where it belongs - the payment system logo – with the right gradient where the circles overlap and the wordmark sitting exactly where it should. A small thing that kills half the fakes out there - and finally, physics. Plastic has to catch light: a highlight along the edge, a micro-shadow under the chip, a faint fingerprint. A phone shot, not a render Sent the draft for approval. The client looked it over, signed off with zero corrections – final files went out. One pass, no rework. A card is a deceptively simple document. Looks like a rectangle and sixteen digits. In reality it's maths in the number, a tie to the issuer, a current design and light on plastic. Miss any one of the four and the file gets exactly two seconds of attention. Need a card for a specific bank and country? Message us. We'll tell you straight what's realistic for your case – then build it. { all data published with the client's consent} › TG: @mustang_service_ms ( https:// t.me/ mustang_service_ms ) › Channel: Mustang Service ( https:// t.me/ +JPpJCETg-xM1NjNl ) #drawing #card #photoshop #revolut #case
    • ============================================================               CLExt Classic Interlude: v7.80 ============================================================   01. Fixed ValidateLocation handling and player/client position synchronization. 02. Added protection against invalid coordinates and characters falling under the map. 03. Improved XY/Z position and heading validation. 04. Fixed MoveToLocation and MoveToPawn packet conversion and target validation. 05. Fixed TargetSelected, TargetUnselected and MyTargetSelected packet handling. 06. Improved GeoData Z-location handling and disabled unsafe PathNode modifications. 07. Added ExUserInfoInventoryWeight support. 08. Fixed inventory weight and maximum load synchronization. 09. Fixed incorrect 0% inventory weight after character login. 10. Added automatic inventory weight updates after EnterWorld and inventory changes. 11. Added inventory weight packet spam protection and safe weight caching. 12. Fixed BuyList and SellList inventory, slot and weight synchronization. 13. Improved NPC target and Buy/Sell packet validation. 14. Reworked mail attachment inventory and weight validation. 15. Added all-or-nothing mail attachment receiving and safe retry handling. 16. Fixed stackable mail attachment validation and INT_MAX overflow protection. 17. Improved COD Adena validation and post-mail inventory weight refresh. 18. Improved Warehouse Deposit and Withdraw validation. 19. Added protection against malformed warehouse item counts, DBIDs and amounts. 20. Added warehouse INT_MAX, CItem and pSID validation. 21. Improved warehouse anti-dupe protection. 22. Reworked the HTML Cache system for improved stability and memory usage. 23. Added lazy HTML loading instead of loading ~20,000 files during startup. 24. Fixed HTML Cache startup crashes with large HTML collections. 25. Added thread-safe HTML Cache access and Clear/Reload support. 26. Added bad allocation, invalid HTML and oversized HTML protection. 27. Reduced HTML Cache RAM usage, startup allocations and disk I/O. 28. Added HTML Caching ON/OFF with live HTM loading support. 29. Fixed ToggleCachingHook and added VS2005-compatible live HTML handling. 30. Fixed ShortcutInit processing and skill synchronization order. 31. Improved shortcut item validation, augmentation handling and va_list safety. 32. Added LiveMode Ability Point system. 33. Added inventory-item-based Ability Points with configurable pointItemId. 34. Preserved the original level-based Ability Point system as fallback. 35. Fixed incorrect Ability Point display and inventory synchronization. 36. Improved Ability skill learning and point validation. 37. Improved OfflineShopRestore loading and FakePC/DBID handling. 38. Added safer OfflineShopRestore socket limits and batch processing. 39. Prevented thousands of restore sockets from loading simultaneously. 40. Added delayed, non-blocking OfflineShopRestore after server startup. 41. Improved OnEnterWorld initialization order and stability. 42. Improved inventory weight, SkillList and acquired-skill initialization after login. 43. Added VIP integration to the EnterWorld process. 44. Added safe UserExtData initialization without modifying the native User structure. 45. Improved duplicate Bronch Jewel and equipped-slot protection. 46. Improved Bracelet, Belt, Bronch and general UseItem validation. 47. Improved general packet, UserSocket, User, pSD and Creature validation. 48. Added safer INT32/INT64 packet handling and malformed-packet protection. 49. Improved L2Server startup memory usage and lazy resource loading. 50. Reduced unnecessary startup allocations. 51. Improved account-only KeyEngine authentication and remote account validation. 52. Removed account expiration-time requirements. 53. Added updater/restart design without requiring CLExtUpdate.exe. 54. Improved CLIEXT HWID, shared-memory and client/server version validation. 55. Improved ReadFile/WriteFile hooks and MemoryProtector handling. 56. Added UoPilot and Extreme Injector detection handling. 57. Reworked VIP point loading, saving and database synchronization. 58. Fixed VIP Level 0 initialization and first VIP activation. 59. Fixed vip.htm activation after login and from party-shared points. 60. Fixed VIP points being incorrectly reset before successful activation. 61. Improved VIP progression from Level 1 through Level 7. 62. Added proper VIP Level 7 MAX/DONE behavior with no Level 8 requirement. 63. Disabled further VIP point collection after reaching maximum level. 64. Reworked VIP BonusInfo/ReceiveVipInfo packet synchronization. 65. Fixed VIP tier, points, duration and level requirement packet fields. 66. Added VIP duration, tier, point and User validation protections. 67. Added safer 64-bit VIP EXP and party EXP calculations. 68. Preserved subclass maximum EXP protection. 69. Improved ItemDataEx validation during character loading. 70. Fixed augmentation loss during login, relog and server restart. 71. Added safe restoration of augmentation IDs directly from the database. 72. Added CItem, pSID, pExItem and User validation during ItemDataEx loading. 73. Improved Shadow Item mana and item lifetime loading. 74. Preserved item protection timeout data during character loading. 75. Added augmentation loading diagnostics and protected valid augmentation data. 76. Preserved database value 0 for genuinely non-augmented items. 77. Added RaidBoss Status synchronization with the World Map. 78. Fixed alive/dead RaidBoss status updates after spawn and death. 79. Added RaidBossStatus as the source of truth for RaidBoss map packets. 80. Fixed RaidBoss map status synchronization after server/database loading.
    • 🚀 L2AQUILA — GRAND OPENING TOMORROW! Lineage 2 Gracia Final — Like L2 Pride, but fresh. The server you've been waiting for opens tomorrow, Saturday 19/09, 16:00 (Greek time) — No Wipe · 24/7 · Anti-DDoS. ⚔️ What's inside: • EXP 9300x · SP 3000x · Adena 5500x · High drop • Max enchant +20 · Safe +3 · 24 buffs / 3 debuffs • 20 free Custom Coins for every new player on day one! • Custom farming zones (Cave of Trials, Cemetery, Ruins of Despair + more) • PvP Events · Olympiads · Offline Trading · Weddings · Balanced classes • Starter + Dynasty shops in every town — playable from minute one 📥 Download: Client + Patch at https://l2aquila.com/index.html 💬 Discord: discord.gg/5ZyBRvG4k · Facebook: facebook.com/l2aquila Be there at opening hour — bring your squad. See you at the Grand Opening! 🔥
  • Topics

×
×
  • Create New...

Important Information

This community uses essential cookies to function properly. Non-essential cookies and third-party services are used only with your consent. Read our Privacy Policy and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..