Google Apps for managing emails

I am using Google Apps for managing emails for some of my domains already and a friend cum client just showed interest in having a email ID on his domain. I told him that one can use Google Apps for letting Google manage their domain emails and he couldn’t ask for more. I was going to use it for one more of my domain so

I thought I would write a post on it as the already available tutorials failed to satisfy my expectations out of a tutorial. Alright. What we need to do is that as soon as the mail comes to our domain, we want that mail to go to Google’s server so that it can be collected and stored over there.

So Lets begin. First of all, Sign up for Google Standard Edition here : http://www.google.com/apps/intl/en/group/index.html You may want to look at Premier edition before signing up as there are some restrictions in the Standard edition like accounts for only 50 users can be created under Standard edition. Create a account that you will use to manage that domain account on Google Apps.

For example : admin@example.com Verify Domain ownership either by uploading a html file or by creating a CNAME record. Create a new user as the email you wanted on your domain name.

For example : mail@example.com Now login with your new user by changing the domain name to the one concerned in the URL example : http://mail.google.com/a/example.com

Now we have done the setup on Google Apps. Lets proceed to making changes in our hosting account. Login in your hosting account and look for MX entry or MX records. Enter the values one by one which are as following :

Priority  Mail Server

1                   ASPMX.L.GOOGLE.COM.

5                  ALT1.ASPMX.L.GOOGLE.COM.

5                   ALT2.ASPMX.L.GOOGLE.COM.

10              ASPMX2.GOOGLEMAIL.COM.

10              ASPMX3.GOOGLEMAIL.COM.

( The values were taken from Google Apps Admin Help. ) After making the changes, wait for the DNS to propagate which can take up to 48hrs. You have completed the setup for having your own email on domain which is managed by Google Apps. Let me know via comments if you need more help or ran into issues.

1. /*
2. Below is the function where to call console()
3. */
4. window.document.onclick = function(){ console(window.event.target.onclick) };
5. function console(msg)
6. {
7. mywin = window.open(”, ’console’, ’width=500,height=150,left=800,top=800,scrollbars=yes,location=no’);
8. if (mywin && msg!=null)
9. mywin.focus();
10. mywin.document.title=’Javascript Console…’;
11. //mywin.document.writeln(‘<h4>Javascript Log here..</h4>’);
12. if(msg!=null)
13. mywin.document.writeln(‘<div style=”font-family:Verdana, Arial, Helvetica, sans-serif; font-size:12px; border-bottom: 1px dotted #FFB64A; padding:4px;”>’+msg+’</div>’);
14. //mywin.document.writeln(“<br /><a href=\”javascript:void(0)\” onclick=\”this.document.write=”;\” >Clear</a>”);
15. //sleep(10); mywin.blur();
16. }

To create applications with the Amazon Elastic Compute Cloud (Amazon EC2), you do four things.

First you create an Amazon Machine Image (AMI) to package all your software into one image — your operating system, configuration settings, applications, and libraries. The AMI contains all the information you need to boot instances of your software.

Second, you upload this AMI for storage in the Amazon S3 (Amazon Simple Storage Service) service. Once in the storage, the AMI is available that you can securely access the AMI .Youíll need access to SSH client to talk to the S3.

Third, you register your AMI with Amazon EC2. You will get a unique number (ID) for it.

Fourth you use this AMI ID and the Amazon EC2 web service APIs to run, monitor, and terminate one or more instances of this AMI. We will tell you how to work with the command line tools and Java libraries later in this article. You must have Java version 5 or later installed to use the tools. You pay only for what you use. There is no minimum fee.

Interfaces to the web service APIs for other programming languages, including Perl, Python and Ruby will be available at a future date. Signing up for Amazon S3 and Amazon E2 If you already have an Amazon S3 account, skip this section.

To sign up, go to the Amazon S3 home page.Then in the Signup for AWS block on the upper right corner, click on a hyperlink to signup.

http://aws.amazon.com/

After following online instructions, you submit to create Amazon Web Services account. The AWS then sends you an email about your new account. In the email you receive, you will be directed to click on an URL.

You will find AWS Access Key Identifiers on the web page. Be sure to copy your AWS accountís Access Key ID and Secret Access Key and put them in a secure place. You will need them to bundle you own image. To sign up your AWS account for the Amazon EC2 service, log into your AWS account and then follow the link to Amazon EC2 in the Infrastructure Services section in the left panel.Click Your Web Services Account button at the upper right corner to bring down a menu of choices.

Select ìAWS Access Identifiers.î Go to the ìX.509 Certificateî section and then click the Create New button to create a new certificate or the Upload button to upload your own certificate.

You can only have one certificate associated with your AWS account. You must download your Private Key file, and store it in a secure location. AWS does not store your private key information. You will not be able to download the Private Key file at any other time. If you do not download now or you lose the Private Key file, you will have to create a new certificate and private key. After downloading your private key file, you must download your certificate file. You will need both files when you set up command-line tools. Getting the Command Line tools If you already have the tools, skip this section.

First, get the Command Line tools from the Amazon EC2 Resource Center and then unzip the file.

http://developer.amazonwebservices.com/connect/entry.jspa?externalID=351&categoryID=88

Second, set the environmental variable to locate the Command Line tools like this:

$ export EC2_HOME=<path-to-tools>

C:\> set EC2_HOME=<path-to-tools>

The variable is set to the path of the directory into which the command line tools were unzipped. The directory is named in the format of ec2-api-tools-A.B-rrrr and contains sub-directories named bin and lib

Third, add the bin subdirectory like this:

$ export PATH=$PATH:$EC2_Home/bin

C:> set PATH=%PATH%;%ec2_HOME%\bin

You need to identify yourself to the command line tools so they know which credentials to use for requests. First, set the variable EC2_PRIVATE_KEY to

reference your private key file like this:

$ export EC2_PRIVATE_KEY=~/.ec2/<your-private-key>

C:> set EC2_PRIVATE_KEY=c:\ec2\<your-private-key>

To find your private key, right click on the file and then click Properties and copy the information. The file ends with the .pem extension. Second, set the variable EC2_CERT to reference to your X509 certificate. Here is an example:

$ export EC2_CERT=~/.ec2/<your-cert>

C:> set EC2_CERT=c:\ec2\<your-cert>

To find your certificate number, right click on the file and then click Properties and copy the information. The file ends with the .pem extension. Running one or more instances Before you begin, make sure you have the following environmental variables correctly set up:

JAVA_HOME

EC2_HOME

EC2_PRIVATE_KEY

EC2_CERT Step

Launching an instance

If you have not found a public AMI and not generated a keypair you need to launch an instance, skip to step 4:

To launch an instance of the AMI ID, type:

PROMPT> ec2-run-instances <ami-identifier> -k gsg keypair

In the output you will get an instance identifier, the value immediately next to the INSTANCE tag, like this:

INSTANCE i-10a64379 ami-5bae4b32 pending gsg-keypair

You use the identifier to manipulate this instance (including terminating it when you are done). Once you launch an instance, you will be billed per hour for CPU time. If you leave this how-to article any time, make sure you terminate any instance you have started. To terminate the instances go to the Finishing Up section. It’s a good idea to check how the instance is doing. Wait a few minutes and then do the following:

PROMPT> ec2-describe-instances <instance-identifier>

In the output you will see next to the INSTANCE TAG the instance and AMI identifiers and then the instanceís DSN name (hostname). You will see the instance state just before the keypair name read ërunningí indicating the instance has been set up and has started running. Here is a sample output:

INSTANCE i-10a64379 ami-5bae4b32 domU-12-34-31-00-00-05.usma1.compute.amazonaws.com running gsg-keypair

There may be still a short time before the instance is accessible over the network.

Step 2: Authorizing Network Access to Your Instances Before you reach your instance over the internet, authorize traffic to it like this:

PROMPT> ec2-authorize default -p 22 PROMPT> ec2-authorize default -p 80

The first command authorizes network access instances in your default group on the standard ssh port (22). The second command opens up the standard http port (80). For details on controlled network security groups, see the Amazon EC2 Developer Guide.

Step 3: Connecting to your instance Open your web browser and go to the instance hostname indicated in the first step in the output of the ec2-describe-instances.

If the website times out, your instance may not have finished starting up yet. Wait a few minutes and then try again. Login as root and exercise full control over this instance.

PROMPT> ssh -i id_rsa-gsg-keypair root@<instance-host-name>

Your machine may have a different name for the sshcommand or use different command line options. Consult the documentation for your machine. When you are done, skip to the next section on creating one or more images.

Step 4: Finding an AMI To run an instance, you must find a suitable AMI to run.

At the prompt enter: PROMPT> ec2-describe-images

This will give you all public and private AMIs. In the output, look for the line containing the public image identified by the

ec2-public-images/getting-started.manifest.xml

value in the third column for one of the IMAGE tags. The value in the second column is the AMI ID for the same IMAGE tag.

Step 5: Generating a Keypair

Use a public/private keypair to ensure that only you will have access. One half of this keypair will be embedded into your instance to allow you login securely without a password using the other half of the keypair. Every keypair you generate requires a name, such as gsg-keypair like this: PROMPT> ec2-add-keypair gsg-keypair

You need to save the private key returned in a local file named id_rsa-gsg-keypair. Make sure you include ——BEGIN RSA PRIVATE KEY—— at the top and ——END RSA PRIVATE KEY—– at the bottom. If you do not put this file in your current directory, you should specify the full path when using the ssh command. If you are using OpenSSH, set the permissions of this file so you are the only one who can read it. Here is an example:

$ chmod 600 id_rsa-gsg-keypair; ls -l id_rsa-gsg-keypair (This is very important that change the permission)

Return to the first step to complete the process.

Creating one or more images.

You can create custom AMIs (private) and use them to launch as many instances as you need. You can take a look at the other public AMIs that are far better suited to basing the new AMIs.

Step 1: Modify an existing image Modify an image on the main web page by replacing some of the static content with your name to personalize it like this:

# sed -i -e ’s/Congratulations!/Congratulations<your-name>!/’ /var/www/html/index.html

You can confirm date and time of the file update like this:

# ls -l /var/www/html/index.html

# date

Here is a sample output for the ls command:

-rw-rw-r– 1 root root 1872 Jun 21 09:33 /var/www/html/index.html

The date and time in the output of the ls command should match the output of the date command.

Step 2: Bundling Copy your private key to the machine being bundled. You do not need the certificate:

PROMPT> scp -i id_rsa-gsg-keypair <your-private-key> root@<instance-host-name>

Bundle your image using your AWS account ID as your username.

# ec2-bundle-vol -d /mnt -k ~root/<your-private-key> -u <your-AWS-account-id>-s 1536

Confirm all necessary manifest file and image parts are found in the /mnt directory:

# ls -l /mnt/image.*

Step 3: Uploading to Amazon S3 Upload the bundle to S3 like this:

# ec2-upload-bundle -b <your-s3-bucket> -m /mnt/image.manifest.xml -a <aws-access-key-id> -s <aws-secret-access-key>

You will get continuous feedback until the upload has completed.

Step 4: Registering the AMI You must register with Amazon EC2, so you can locate it and run instances based on it. Do the folowing:

PROMPT> ec2-register <your-s3-bucket> /image.manifest.xml

In the output, you will get an AMI identifier, the value next to the IMAGE tag.

Step 5: Running instances Run the instances as follows:

PROMPT> ec2-run-instances <ami-identifier>

In the output, you will get an instance identifier, the value next to the INSTANCE tag. Here is a sample output:

INSTANCE i-10a64379 ami-5bae4b32 pending

Finishing up

First, deregister your AMI like this:

PROMPT> ec2-register <ami-identifier>

Second, delete your AMI with the following command:

PROMPT> ec2-delete-bundle -b <your-s3-bucket> -p image -a <aws-access-key-id>-s <aws-secret-access-key>

Third, terminate your instances.

PROMPT> ec2-terminate-instances <instance-identifier>

Wait a few minutes for the instance to terminate because you need to clean up your data. Check on the status of the instance as done in the first step in the Running one or more instances section. You can also terminate your instances by logging onto the instances with your ssh tool and running the shutdown -h command. If you forgot to include the -h option, you will put your instance into single user mode.

Application examples

Here are two examples – one using a public image and the other using a private image.

Example 1: Using a public image assuming a keypair has been generated

PROMPT> ec2-run-instances <ami-identifier> -k gsg keypair

PROMPT> ec2-describe-instances <instance-identifier>

PROMPT> ec2-authorize default -p 22

PROMPT> ec2-authorize default -p 80

PROMPT> ssh -i id_rsa-gsg-keypair root@<instance-host-name>

Example 2: Creating and using a private image

# sed -i -e 's/Congratulations!/Congratulations<your-name>!/' /var/www/html/index.html

# ls -l /var/www/html/index.html

# date

PROMPT> scp -i id_rsa-gsg-keypair <your-private-key> <instance-host-name>

# ec2-bundle-vol -d /mnt -k ~root/<your-private-key> -u <your-AWS-account-id>-s 1536

# ls -l /mnt/image.*

# ec2-upload-bundle -b <your-s3-bucket> -m /mnt/image.manifest.xml -a <aws-access-key-id> -s <aws-secret-access-key>

PROMPT> ec2-register <your-s3-bucket> /image.manifest.xml

PROMPT> ec2-run-instances <ami-identifier>

PROMPT> ec2-describe-instances <instance-identifier>

PROMPT> ec2-authorize default -p 22

PROMPT> ec2-authorize default -p 80

PROMPT> ssh -i id_rsa-gsg-keypair root@<instance-host-name>

Using PuTTY

PuTTY is a free SSH client for Windows. PuTTY also comes with PuTTYgen, a key generation program, and pscp, a secure copy command line tool.

To convert your private key to PuTTy format, do the following:

Step 1: Launch PuTTYgen and load id_rsa-gsg-keypair (see step 5 in the Running one or more instances section). The private key file must end with a newline character.

Step 2. Save the key as id_rsa-gs-keypair.ppk.

To use SSH with PuTTY, do the following:

Step 3. Run PuTTY and go to Connection -> SSH -> Auth.

Step 4. Under Authentication parameters click on Browse… and select the PuTTY private key file you generated in step 2.

Step 5. Under session fill in your EC2 instance host name or IP address.

Step 6. Click on Open to connect to your EC2 instance.

To use SCP with PuTTY, do the following:

Step 7. Use the scp command to copy the private key and X.509 certificate as shown in step 2 on Creating one or more images section.

Step 8. Run the same command with pscp like this:

C:\> pscp -i id_rsa-gsg-keypair.ppk <your-private-key> <your-certificate>root@<instance host name>

How to use the Firefox Extension for Amazon EC2
The Firefox extension for manipulating EC2 instances is a great tool but the download page doesn’t offer any instructions on how to use it and more than a few people have had issues configuring it properly.   In general, it’s a very simple application but there are a couple gotchas to watch out for.   I’m pretty new to this extension myself, and there are a few questions that I still have about it, so hopefully those who know more about it than I do will also read through this howto/faq/tutorial/whatever and post corrections or embellishments as necessary.
The home page for the extension is http://developer.amazonwebservices.com/connect/entry.jspa?entryID=609.
Step 1: Download and Install the Firefox Extension for Amazon EC2
The Extension can be downloaded from http://s3.amazonaws.com/ec2-downloads/ec2ui.xpi.   If you use Firefox to download the file, Firefox will detect that it is an extension and install it for you automatically.
Step 2: Run the extension
Launch Firefox and click on the Tools/EC2 UI menu item.
Step 3: Register your Credentials with the plugin
Click on the “Credentials” button in the top left of the window.   Enter your Account Name.   Your Account Name needs to match your username on the AWS developer site.   You can find by logging into the forums, clicking on “Your Control Panel” and looking at the text to the right of “Developer Connection” in the breadcrumbs at the top of the page (I think that is a consistent way to find your username – some pages seem to list your user name in the upper right hand corner and some list your first name and last name in the upper right hand corner of the page).   Then enter your Access Key and Secret Key (these can be found when you log into the Amazon Web Services home page ( http://www.amazon.com/gp/browse.html?node=3435361).
Step 4: View the list of Available AMIs
If it is not already selected, click on the “AMIs and Instances” tab at the top of the plugin and if necessary click the blue refresh button for the Available AMIs window to see the list of publicly available AMIs (Amazon Machine Images) that you can use to launch EC2 instances.
If you have any private AMIs of your own, you can add them to the list using the green “+” button.   I’m not sure what happens if you try to use the red “-“ button to remove a publicly available AMI from your list (presumably it doesn’t remove it from the global public list but I don’t know if it hides that AMI from you or if it generates an error).
Step 5: Configure the firewall settings for your default security group
EC2 wraps each machine instance in a configurable firewall.   You can open and close ports and control which IP addresses are allowed to connect to which machines.   The firewall is very powerful but if you configure it incorrectly you will not be able to access your machines other than to reboot them or shut them down.   If you don’t actively change your settings, you will not be able to connect to your machines (at least that was how my account was set up the first time that I used the Firefox EC2 UI).
At a minimum, you will probably want to open TCP port 22 (used by open SSH to allow you to log into the machine) and TCP port 80 (if you are running a web server on the machine) or port 443 (if you are serving up web pages over https).
Switch to the “Security Groups” tab.
Refresh the list of security groups by clicking the blue refresh button under “Your Groups”.
Select the default group.
To open a port 22 (used by open SSH) in the default group, click on the green check mark in the “Group Permissions” pane and specify a source of CIDR 0.0.0.0/0 (which indicates that any port on any machine can connect to the specified port(s) on instances in the default security group.   Then set the Protocol Details to TCP/IP and the port range from 22 to 22 (since we only want to open a single port here).    Click “Add” to record the settings and then repeat the process to open port 80 (from port=80, to port=80).
For simplicity while you are learning you can of course open all TCP ports by specifying a port range from 0 to 65535 but you definitely would not want to do that on a production machine (and I’d be inclined to assume that any machine which spent time with all its ports open like that would had been compromised by some trolling botnet and should be thrown away as soon as you are done getting a feel for the service).
Step 6: Generate a key pair for identifying yourself to your instances
EC2 instances use key pairs.   Key pairs are cryptographically generated identifiers that are mathematically linked by what is called a “one-way function.”   One of the identifiers is called the “public” key and the other called the “private” key.   Messages that are encrypted using the private key can only be decrypted using the public key and messages that are encrypted using the public key can only be decrypted using the private key.   If you give your instance a copy of your public key, then you and your instance can exchange messages that allow each of you to trust the identity of one another (which is a fancy way of saying that EC2 can use key pairs to allow you to log into your instances automatically without needing to remember or type in passwords).
The Firefox EC2 extension allows you to generate key pairs and store them on your local hard disk.   You should protect these key pair files as if they were passwords to the accounts on your instances because that is effectively what they are.
In a later step, when you launch an instance you will indicate which of your key pairs to provide to that instance.   You will also need to provide the key pair to the open SSH terminal program that you use to log into the instance.
To generate a key pair, click on the “Key Pairs” tab at the top of the plugin.   You can use the green key button to generate a new key pair file.   You will be asked for the name of the file to create and then prompted for a location to store the file.   I *think* that the first popup (the one that asks for the key pair name may be somewhat poorly labeled.   Many key pair generators ask the user to provide a text string to seed the randomization process that is involved in the key generation and I suspect that the first popup is actually asking for this type of seed string because after you click OK you are immediately presented with a file browser dialog asking you what you want to call the file that you are generating and where you want to store the file.   (Perhaps someone who is more familiar with the inner workings of this extension could comment on that).
If you want to use PuTTY to connect to your instance from Windows, you will need to run a separate program to convert the key pair file from the format that EC2 can read into the format that PuTTY can read.   This is discussed in the Appendix on PuTTY in the Amazon EC2 Getting Started Guide (I’d post a link, but Amazon keeps updating their docs and I haven’t seen any way to post a link to “the newest version” of the docs).
Step 7: Start up an instance of an AMI
You can launch an instance of an AMI by selecting the AMI from the list of Available AMIs and clicking the green power button icon in the “Available AMIs” window.   Clicking on the green power button will bring up the “Launch new instance(s)” popup where you further configure the instance that you are about to launch.
Using the Launch new instance(s) popup you can specify whether to launch a small, large, or extra large instance.   More importantly, you can also specify the key pair to provide to the instance.   The key pair is what allows you to log into the machine once it is launched.   If you have already created your own private AMI files you may have baked your key pairs into those images (in which case you do not need to provide a key pair here) but if you are reading this tutorial then you are probably new to EC2 and are attempting to launch a public AMI.   When you launch a public AMI, the public portion of the key pair that you specify will be provided to the instance when it launches so that it can be used to authenticate you.   In general, I believe that most public AMIs are currently installing the credentials into the root account, so that you can be allowed to log into root over an SSH connection without the need for a password.
You will also want to select a security group to launch the image into.   Security groups control the settings of the EC2 firewall.   If your security group is not configured correctly, you may be unable to log into your instance (you will always be able to shut it down using the red power button in the “Your Instances” window).
The User Data panel allows you to enter additional parameters that can be provided to the instance on launch.   If the AMI that you are launching supports User Data it will hopefully have provided documentation on what text you should enter in the User Data panel.
The Launch button sends a request to EC2 to provision and activate your server instance.   You will need to refresh the list of “Your Instances” to find out when the new instance is up and running (hopefully only about a minute or so after you hit the Launch button).
Step 8: See your list of running instances, requests, and recent shutdowns
If necessary, click the blue refresh button in the “Your Instances” window.
You can double-click on an instance to see more details about the instance (and more importantly to get a text field containing the public DNS address of your machine that you can copy the value out of for use in other programs).
The red starburst button reboots the selected instance (you will see the “State” field for the instance change if you refresh the list of instances during the reboot).
The red power button icon shuts down the selected instance.   This is obviously an important button as you will be charged for your instances until you shut them down (and, in general, you will actually be charged for longer than that as Amazon bills you for one-hour increments so an image that runs for one minute incurs the same charge as one that runs for 59 minutes).
The blue document button pops up a window to view the console output of the image.
Step 9: Log into your instance using an open SSH connection
In general, I believe that most public instances are currently being configured to allow you to log in as root.   If not, presumably the documentation on the AMI will tell you what account to use when you log in.
For Windows users, there is an Appendix on how to use PuTTY to log into your instance at the end of the EC2 Getting Started Guide (as I mentioned earlier, I don’t want to embed links to the docs here because Amazon keeps updating them and there doesn’t seem to be any way to specify a link to “the newest version” of the document   The page on “Running an Instance” in the same EC2 Getting Started Guide has similar instructions on how to connect to an instance from a Unix machine.
My unanswered Question: What does the “Account IDs” button do?
Hopefully someone who reads this posting can explain the purpose of   the Account IDs button.

Video help for EC2:
http://s3.amazonaws.com/AmazonEC2Tutorial/AmazonEC2Tutorial.html

write this code in parent window

function hideshow() {
sd=window.open(‘http://lalit241.wordpress.com’,'NewWin’,'toolbar=no,status=no,width=350,height=135′)
sd.moveTo(10,10);
}

</script>
</head>
<body onload=”hideshow()”>

Write this code in popup window

<script language=”javascript”>
var sec = 0;
function moveWin() {
sec++;
if (sec == 2) { window.blur(); }
if (sec == 3) { window.focus(); moveTo(10,350); }

window.setTimeout(“moveWin();”, 1000);
}

</script>
<body onLoad=”moveWin();” bgcolor=”#ffff00″>

function popupmat()
{

var mylink=’http://lalit241.wordpress.com’
var windowname=’lalit241′
var refocus=true;

var mywin, href;
if (typeof(mylink) == ’string’)

href=mylink;

else

href=mylink.href;

mywin = window.open(”, windowname, ‘width=400,height=200,scrollbars=yes’);
// if we just opened the window

if (

mywin.closed ||

(! mywin.document.URL) ||

(mywin.document.URL.indexOf(“about”) == 0)

)

mywin.location=href;

else if (refocus)

mywin.focus();

return false;
}

Sample code for HTML pages:

For Epassporte Integration Two Field Necessary That Provided By Epassporte To The Mearchant

acct_num

pi_code

pi_code is generated according to account number other wise you face xml apt error

<FORM ACTION=”https://www.epassporte.com/secure/eppurchase.cgi” TARGET=”NEW” METHOD=”POST”><BR>
<INPUT TYPE=”HIDDEN” NAME=”acct_num” VALUE=”[account number here]“><BR>
<INPUT TYPE=”HIDDEN” NAME=”pi_code” VALUE=”[product code here]“><BR>
<INPUT TYPE=”HIDDEN” NAME=”gohere” VALUE=”CART”><BR>
<INPUT TYPE=”HIDDEN” NAME=”dothis” VALUE=”VIEW_ITEMS”><BR>
<INPUT TYPE=”SUBMIT” VALUE=”View Cart Items” ALT=”View Cart Items”><BR>
</FORM>

Sample code for HTML pages (with quantity):

<FORM ACTION=”https://www.epassporte.com/secure/eppurchase.cgi” TARGET=”NEW” METHOD=”POST”><BR>
<INPUT TYPE=”HIDDEN” NAME=”acct_num” VALUE=”[account number here]“><BR>
<INPUT TYPE=”HIDDEN” NAME=”pi_code” VALUE=”[product code here]“><BR>
<INPUT TYPE=”HIDDEN” NAME=”amount” VALUE=”[product amount here]“><BR>
<INPUT TYPE=”HIDDEN” NAME=”product_name” VALUE=”[product desc here]“><BR>
<INPUT TYPE=”HIDDEN” NAME=”quantity” VALUE=”[product quantity here]“><BR>
<INPUT TYPE=”HIDDEN” NAME=”gohere” VALUE=”CART”><BR>
<INPUT TYPE=”HIDDEN” NAME=”dothis” VALUE=”ADD_ITEM”><BR>
<INPUT TYPE=”IMAGE” SRC=”epassporte.gif” NAME=”SUBMIT” ALT=”Pay By ePassporte”>
</FORM>

Sample code for link:

https://www.epassporte.com/secure/eppurchase.cgi?acct_num=[account number here]&pi_code=[product code here]&amount=[product amount here]&product_name=[product description here]&gohere=CART&dothis=ADD_ITEM

Money Booker Payment Basic Integration Api

Mp3 Player for Joomla 1.5. Upload your own mp3 files! Editable playlist. Create as many players as you want. Customise the mp3 player to your own colours. Simple design to fit any website. Share on other websites. Popup window option. Full vector, so you can resize gracefully. At the moment the popup has issues when Joomla SEO settings are on in global configuration. We are looking into this issue. Latest version released 28/02/09. Mp3 player resizing available in module.

Download :- http://www.unmp3.com/unmp3_download.html

A podcast (not to be confused or equated with Apple Inc’s iPod)
usually consists of a combination of audio and/or video that is made
available for download via syndication. It is this syndication aspect
of the delivery that separates a podcast from a file available for
download. The files are usually retrieved with software applications
(generically known as podcatchers) such as Apple’s iTunes so
that subscribers can listen at their convenience on devices that have
intermittent, slow, or are otherwise lacking Internet access. The
podcatcher reads an RSS feed (whose entries point to specific podcasts, usually sorted by date) to identify and retrieve the podcast.

Like the term broadcast, podcast can refer either to the content itself or to the method by which the content is syndicated; the latter is also called podcasting. A podcaster is the person who creates the content.

A podcast is syndicated via an RSS feed. This feed enables distribution over the Internet by syndicated download. Though the same content may also be made available by direct download or streaming,
a podcast is distinguished from most other digital media formats by its
ability to be syndicated, subscribed to, and downloaded automatically when new content is added.

The term is a portmanteau of the words “iPod” and “broadcast”,^[1] the Apple iPod being the brand of portable media player for which the first podcasting scripts were developed (see history of podcasting).
Such scripts allow podcasts to be automatically transferred from a
personal computer to a mobile device after they are downloaded.^[2]

As more devices other than iPods became able to synchronize with podcast feeds, a backronym developed where podcast stood for “Personal On Demand broadCAST.”^[3][4][5] though such a definition would create a misnomer,
because podcasts are not available “on demand”; they are subscribed to
and usually received at set intervals. Such a definition would more
accurately describe a direct download or streaming media.

For Joomla YOu can download component form

http://extensions.joomla.org/extensions/search/1/podcast/

Powered by ScribeFire.