Can I please know if there is any standard way/syntax that support adding multiple email address in one email control. Suppose I need to add multiple email recipients in one email control is there a way to add those address? When I separate from comma an error is thrown. Please help.
The built-in Email Address field only supports one email. If you need to capture multiple email addresses, you could:
Create a Repeated Grid grid in which you place the Email Address field.
Create your own component, using XBL, that supports multiple addresses.
If you're after a simple solution, #1 is the way to go. If you want to have as much control as possible over how the field behaves and can afford to invest the necessary time and energy into building an XBL component, then #2 might the best option for you.
Related
So lately I have been trying to figure out if there's a way to find emails inside the phone mail box(either default one, or a chosen one, doesn't really matter at this point), that was sended too or by a specific email address.
I have read about enough_mail and imap_client but both of them offer an option to fetch a range of messages, without the option to filter by the sender.
Its worth mentioning that I wouldn't want to get a range of lets say one year emails (which also couldn't really be estimated using a number to decide what amount of messages I want to fetch, what I saw the packages offer) and iterate through them and check, its not efficient at all.
*A solution to send an email using flutter is not relevant AT ALL
Is there any way to do it using this packages, or any other options?
Thank you.
I'm tasked with creating an Outlook form that will be used to communicate rate changes to our customers, and ask for their approval. The body of the email must have some fields that are required by the sender, such as customer name, and new rate. And the email must have an approval button or similar from the recipient. Its a relatively basic workflow
As I'm researching Outlook forms, I discovered this might be better suited for Outlook templates instead. But I'm new to this, and I'm not sure the difference between the two.
Any help or advice would be much appreciated!
Custom Outlook forms should be displayed on both sides of communication if you really want them working correctly. It is very inconvenient, so this feature is not really used nowadays.
Instead, you may consider using the MailItem.VotingOptions property which returns or sets a string specifying a delimited string containing the voting options for the mail message. This property uses the character specified in the value name, sList, under HKEY_CURRENT_USER\Control Panel\International in the Windows registry, as the delimiter for multiple voting options. As a result the recipient will see possible options to choose on the UI.
When the response comes back you may check the MailItem.VotingResponse property which returns or sets a string specifying the voting response for the mail message. This property is usually set to one of the delimited values returned by the VotingOptions property on a reply to the original message.
And the third solution is to develop a COM add-in which can handle custom data and provide a convenient UI for voting, for example, a custom form region can be developed for that. Again, this solution, like custom Outlook forms, requires installing the software on both sides of communication.
My problem is two fold.
1. I have a customer base that need to send me attachments. When they register with me, I'd like to assign them a unique email address. ie. uniqueId#...com
Is there a "special" way to do this, or do I need a mail server? I'm not really across mail servers other than how to set MX records. So not sure how they really work.
The emails that they send me will have attachments. PDFs, .doc, Images. I want to automatically read the attachments using OCR technology.
More after a point in the right direction of how I would implement something like this.
We're programming a Testing Web Application for a University in ColdFusion with a MS SQL Backend.
Right now we have to manually take faxes sent to our fax machine and then find the account they are related to and input the info (the actual fax has to be found in a filing cabinet if we ever need to reference it again). What I would like to do is create a way for someone to fax to a certain number and then the fax be sent to an email account we specify.
If that worked properly we would need a way to get the email, store it somewhere on our servers and then link it to an account. The linking process would probably have to be manual and we are ok with that, but an easy way to view all the faxes sent to that email in our ColdFusion application in PDF form (searchable by the name we assign it) is what we are mainly looking for, so that we don't have to get the faxes on paper and file them by hand.
Is there a way to accomplish this? Preferably not through a paid service as we can program almost anything we need ourselves.
Hmm... have you tried services like eFax?
Why reinvent the wheel? Services like eFax and jConnect (there are several others, just Google "electronic fax service") are affordable and do half of what you are trying to do. Save yourself the effort and just spend a few bucks. You'll probably find out, too, that it will cost you less to just pay for the service than it would cost you to pay the developer to write the software.
So after you bite the bullet and sign up for an electronic faxing service, you just need an email account for it to send to, and to use CFPOP to check the inbox and download the attachments. The rest is a piece of cake.
From the sounds of it, I have built something identical to this faxing setup with Coldfusion.
After a few trials and errors I found best way to go is:
1) DIGITIZE INCOMING FAXES: Have all faxes either sent to an email address you can check via CF, or a network folder you save them on, which you can check with CF. You can absolutely keep your fax number and simply call forward incoming calls to your digital fax number.
2) PROCESS INCOMING FAXES When you find a new fax, it is best to process it and make a record of it. I store things like the file name, dig up the fax number it came from, check it against a list of known numbers, and have a routing table (in case it needs to go to someone).
3) PRINT AND ROUTE FAX Auto printing a document once in CF is possible via CF as well.
As for tables, I keep one to store each fax. I store the fax itself in a blob as well. Easy to replicate and move around, no big performance hit. I keep another table to store a list of incoming number profiles (like a caller ID table) to relate the number to a customer. I keep a table for routing rules, if an email comes from here, send it here. Last, but not least, if you have to manage multiple phone numbers, you can create multiple incoming profiles and file them.
Once you have each fax stored in the DB, you can do a lot with it and file/index/ store it digitally how you like. CFDOCUMENT will display disk based PDFs.
I ended up having to program something like this for custom routing options. It is possible to auto link items to certain files/folders/projects if you like as well with CF.
If you need to know anything else, ask, or we can discuss it off line if you need to keep some details private.
Agree with Adam. Don't create a bunch of problems for yourself - you'll save a lot of money and nerves by just using the existing service.
On the topic: I use Popfax and I kind of like it. It's comfy, gives you opportunities, discounts, contests and a lot of stuff you'd like if you'd be interested in. It's cheap (at least, 100% cheaper than your own software) and you can use it not only on PC, but also via mobile phone
My current app needs to store address information for a user. I'm currently debating whether to use the customary street address / city / state / zip textboxes and dropdowns or to go with Google's method of simply having everything on one line. Any thoughts on the pros/cons of storing address information in either of these manners?
You should split it up. It will make it far easier to do reporting down the road. What happens if you want to pull up all the residents of a state or zip code, or city? If you use all one field, you will be stuck and wish you had split it up.
Also, users will forget to put in all the information you need if you don't prompt them for it.
Judging by the user-input tag on your post, I assume you are referring to how the user enters the data, and now how you are storing the data in your back-end database.
Presumably your database will still need to store this information as separate fields, if you want to be able to sort and analyse the information (e.g. for reporting and statistics purposes).
In this case, I think it would depend on how confident you are that you could parse the addressing information properly into its individual fields.
One hybrid option would be to allow the user to enter the address as a single line, and then do a best-effort parsing of the information into the separate fields. This is similar to how Outlook manages addresses for contacts - you enter all of the information into a single memo field, and then it splits it up for you. You can then correct if it interpreted any of the fields wrong.
I would be very much against just having a single text field where users enter their address. You'd be surprised how many people will leave out their zip code or some other important info if you don't have a specific field for it. Also, as others have mentioned, it make reporting much easier to report on this information later if all the data is pre-parsed. As other users mentioned, programs like outlook will parse this information, but only because the source of the data is often the signatures of emails, which is something that is never in a consistent format.
I tend to split it up, allows searching to be done for a specific section of the address and you can limit the addresses you want to handle by knowing the formatting i.e. Only ship to east coast addresses.
1) You should split it.
2) May I recommend you read this before you attempt to do international address input?
I concur with Kibbee. I was even surprised to see people don't even read the field's labels, inverting first and last name, postal code and city, etc.
No, you can't determinate if a postal code is valid, in a Web application targeting international customers...
Some countries have alpha characters in postal code, various lengths, no state info, etc.
Definitely split the input. If you can help it--and depending upon your business requirements--it may be wise to perform address verification at the point of entry. This will allow you to know that your addresses are going into your database clean and allow you to do a number of other things such as fraud prevention. Having a verified address can help reduce shipping costs if you're shipping physical goods to your customers and can help reduce credit card merchant fees by ensuring the correct ZIP Code is submitted during AVS verification.
In the interest of full disclosure, I'm the founder of SmartyStreets. We offer CASS-certified address verification services. Users can upload a list for scrubbing (CSV/Excel/etc) to our website or use our address verification web service API called LiveAddress.