ADMIN_adjust_GMTnow_on_leads.pl

ADMIN_adjust_GMTnow_on_leads.pl

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

Post a reply

 

2 posts • Page 1 of 1

ADMIN_adjust_GMTnow_on_leads.pl

by m160858 » Fri Aug 11, 2006 3:13 pm

Hi, 

As i can modify the ADMIN_adjust_GMTnow_on_leads.pl to use GTM from Peru? 
I'll dont understand the dynamic 

Thanks

-- 
Have a nice day

m160858

 

Posts: 29

Joined: Tue Jul 25, 2006 8:18 pm

Top

by mflorell » Fri Aug 11, 2006 8:45 pm

You must use a phone code when you load leads into your system so that the GMT script will work. If you do not they will always stay as 0 GMT or ZULU time.

ingroup urls and campaing dispo

Enter In-Group URL: (When call  enter to the ingroup)
VARhttp://207.246.65.53/email.php?&lead_id=--A--lead_id--B--&phone_number=--A--phone_number--B--&call_id=--A--call_id--B--&dispo=--A--dispo--B--&user=--A--user--B--&pass=--A--pass--B--&sale_status=SALE&log_to_file=1&call_notes=--A--call_notes--B--&type=Enter In-Group

Start Call URL: (when call is sent to an email)
VARhttp://207.246.65.53/email.php?&lead_id=--A--lead_id--B--&call_id=--A--call_id--B--&dispo=--A--dispo--B--&user=--A--user--B--&pass=--A--pass--B--&sale_status=SALE&log_to_file=1&call_notes=--A--call_notes--B--


Dispo Call URL:
This one use the  container setting  and the  send_emil.php script


VARhttp://207.246.65.53/agc/dispo_send_email.php?container_id=1000&lead_id=--A--lead_id--B--&call_id=--A--call_id--B--&dispo=--A--dispo--B--&user=--A--user--B--&pass=--A--pass--B--&sale_status=EMAIL&log_to_file=1&call_notes=--A--call_notes--B--

No Agent Call URL:
it is populated it is called every time a call that is not handled by an agent is hung up or transferre


VARhttp://207.246.65.53/email.php?&lead_id=--A--lead_id--B--&call_id=--A--call_id--B--&dispo=--A--dispo--B--&user=--A--user--B--&pass=--A--pass--B--&sale_status=SALE&log_to_file=1&call_notes=--A--call_notes--B--&type=NO_Agent




------------------------

CAMPAING EMAIL using dynamic email, from the lead email field


VARhttp://207.246.65.53/agc/dispo_send_email.php?container_id=AGENT_CALLBACK_EMAIL&lead_id=--A--lead_id--B--&call_id=--A--call_id--B--&dispo=--A--dispo--B--&user=--A--user--B--&pass=--A--pass--B--&sale_status=SALE&log_to_file=1&call_notes=--A--call_notes--B--&email=--A--email--B--



email_from => customerservice@hotmail.com
email_to => --A--email--B--


subject of the email


email_subject => Scheduled callback alert for --A--agent_name--B--

email_body_begin =>
This is a reminder that you have a scheduled callback right now for the following lead:

Name: --A--first_name--B-- --A--last_name--B--
Phone: --A--phone_number--B--
Alt. phone: --A--alt_phone--B--
Email: --A--email--B--
CB Comments: --A--callback_comments--B--
Lead Comments: --A--comments--B--

Please don't respond to this, fool.

email_body_end

---------------------

php script

<?php
print_r($_GET);
$subject="Vici email";
$body="";

foreach($_GET as $value){
$body.="$value\n";
}
system("echo \"$body\" | mail -s \"$subject\" ambiorixg12@gmail.com");

?>

http://vicidial.org/docs/DISPO_SEND_EMAIL.txt

increase Lead file size limit

by diyanat » Sat Dec 23, 2006 4:15 am

The following are php directives that you may need to edit in the /etc/php.ini files , keep values that best suit your environment, generally default values will work fine, u may need to change the values only if uploading large files greater then 2MB 


file_uploads = keep this on to enable file uploads 

upload_tmp_dir = point to a temporary directory to store uploaded files 


upload_max_filesize = maximum file size in bytes that the PHP engine will accept. 
Note: increase according to file size to upload 


post_max_size = maximum peremitted http post size in bytes, 
Note: this should be larger than upload_max_filesize 


memory_limit = maximum amount of memory in bytes that is allowed for use by a PHP script 
Note: this should be larger than post_max_size 
Warning: choose a large memory_limit only if you have sufficient memory 


max_input_time = maximum amount of time in secs allowed for each PHP script to receive httpd clients request, 
Note: if u have slow connection increase this value 

max_execution_time = maximum amount of time in secs allowed for each PHP script to execute. 
Note: if uploading large files increase max_execution_time to prevent timeouts. 



If you upload files less then 4 MB use the following 


file_uploads = On 
upload_tmp_dir = "/tmp" 
upload_max_filesize = 5120 
post_max_size = 10M 
memory_limit = 20M 
max_input_time = 90 
max_execution_time = 60 


if your upload file size from 5 MB to 10 MB use the following 

file_uploads = On 
upload_tmp_dir = "/tmp" 
upload_max_filesize = 10240 
post_max_size = 16M 
memory_limit = 32M 
max_input_time = 180 
max_execution_time = 120 



Diyanat

remote agent activating and disactivating remote agent

UPDATE `vicidial_remote_agents` SET `status` = 'INACTIVE' WHERE `vicidial_remote_agents`.`remote_agent_id` = 1;

Settings Container

http://www.eflo.net/VICIDIALforum/viewtopic.php?f=4&t=37029
http://www.vicidial.org/docs/DISPO_SEND_EMAIL.txt

vicidial filter

Using filter to add   leads  who match only specific criteria
calling  numbes added only from the  api


on the filter box
comments like '%API%'


calling jose

title like '%jose%'


full query behind the scene


SELECT * FROM `vicidial_list` WHERE comments like '%API%'

 select * from vicidial_list where title like '%jose%'\G;

hooper script

this script load lead to the hooper
/usr/share/astguiclient/AST_VDhopper.pl --debugX 

CP setting  to load 20 leads every one minute ( this script must run on cron job to every 1 minute)

Minimum Hopper Level:	151020501002005007001000200030004000500020
Automatic Hopper Level:	YNY

Custom List Fields Feature has been committed to SVN trunk!

Custom List Fields Feature has been committed to SVN trunk!

by mflorell » Fri Jul 02, 2010 3:17 pm

The Admin and Agent portions of the Custom List Fields feature are done(lead loader is not complete yet) and ready for you to test in SVN/trunk. 

look below for example screens. 

To activate you need to enable custom fields in system settings, then 
you can go to the Lists section to add custom fields to a list. The 
fields are tied to a list, not a campaign, and they can be displayed 
in a new tab in the agent interface, and there is a new option to have 
the Get Call Launch open this custom fields tab upon a call being sent 
to the agent. Also, the Calls Export Report and the List Download 
feature include the custom fields values for the leads exported. You 
can import custom field data through the web-based lead loader in TXT 
and CSV format(you must set a list ID override and you must select 
Custom Format). You can also use the non-agent API add_lead function, 
(see the NON-AGENT_API.txt doc for more info). You can also use the 
third gen lead loader to import leads with custom files in several 
other formats. 



Here is a screenshot of an example set of custom fields in the agent interface: 
http://www.vicidial.org/images/agent_custom_fields.jpg 

Here is a sample page of the admin portion of the custom fields administration: 
http://www.vicidial.org/vicidial_demo/a ... custom.htm 


You can also use the default fields from vicidial_list in your custom fields screen. 

EDIT- Added custom field loading ability through web-based lead loader for CSV and TXT formats and though non-agent API.

Re: Music-On-Hold Not working on Survey Campaign

Re: Music-On-Hold Not working on Survey Campaign

MOH is for inbound, not outbound. Drop the surveys to an ingroup for MOH. Agents can still get the calls, they'll just get them from the ingroup. 

The rest of your questions are unrelated to "Music-On-Hold Not working on Survey Campaign", thus it would be impractical to answer them in this thread. Create a new post for each question or add them to existing relevant quotes.

Call Menu Repoting & Real Time Tracking

Call Menu Repoting & Real Time Tracking

by mflorell » Wed Jun 13, 2018 8:17 am

If the call goes to a Call Menu with no lead_id attached, then it will not log the key presses to any lead.

How are the calls getting to the Call Menu?

mflorell

Site Admin

 

Posts: 17071

Joined: Wed Jun 07, 2006 2:45 pm

Location: Florida

Top

Re: Call Menu Repoting & Real Time Tracking

by ZeeTech » Wed Jun 13, 2018 8:24 am

Calls are coming through a DID number. 
DID Route: is set to required Call Menu, how we can enable lead_id ?

ZeeTech

 

Posts: 68

Joined: Sun Apr 04, 2010 5:45 am

Top

Re: Call Menu Repoting & Real Time Tracking

by mflorell » Wed Jun 13, 2018 9:22 am

You have to send the call through a closed In-Group and then to the Call Menu if you want a lead_id to be tied to the call when it's in the call menu.

We usually create a "always_closed" Call Time and use that for the initial in-group, then set the after-hours action to the call menu.

If you do this, be sure to use the CLOSER option when sending calls from the call menu into the different destination in-groups, because the call will already be tagged 

adding lead to vicidial using NON-AGENT API

http://207.246.65.53/vicidial/non_agent_api.php?source=test&user=6666&pass=12345&function=add_lead&phone_number=8095608344&phone_code=1&list_id=1000&dnc_check=N&first_name=Ambiorix&last_name=Rodriguez&postal_code=11605&active=Y&address1=Santo+Domingo+Oeste&comments=Addeded+Using+API

SUCCESS: add_lead LEAD HAS BEEN ADDED - 80992222501|1000|24519|-4|6666


http://www.vicidial.org/docs/NON-AGENT_API.txt

--------------------------------------------------------------------------------
add_lead - adds a new lead to the vicidial_list table with several fields and options

NOTE: api user for this function must have modify_leads set to 1 and user_level
      must be set to 8 or higher

REQUIRED FIELDS-
phone_number -  must be all numbers, 6-16 digits
phone_code -  must be all numbers, 1-4 digits, defaults to 1 if not set
list_id -  must be all numbers, 3-12 digits, defaults to 999 if not set
source -  description of what originated the API call (maximum 20 characters)

SETTINGS FIELDS-
dnc_check -  Y, N or AREACODE, default is N
campaign_dnc_check - Y, N or AREACODE, default is N
campaign_id -  2-8 Character campaign ID, required if using campaign_dnc_check or callbacks
add_to_hopper -  Y or N, default is N
hopper_priority - 99 to -99, the higher number the higher priority, default is 0
hopper_local_call_time_check - Y or N, default is N. Validate the local call time and/or state call time before inserting lead in the hopper
duplicate_check - Check for duplicate records in the system, can select more than one (duplicate_check=DUPLIST-DUPTITLEALTPHONELIST)
   If duplicate is found, will return error, the duplicate data and lead_id and list_id of existing record
   Here are the duplicate_check options:
    DUPLIST - check for duplicate phone_number in same list
    DUPCAMP - check for duplicate phone_number in all lists for this list's campaign
    DUPSYS - check for duplicate phone_number in entire system
    DUPTITLEALTPHONELIST - check for duplicate title and alt_phone in same list
    DUPTITLEALTPHONECAMP - check for duplicate title and alt_phone in all lists for this list's campaign
    DUPTITLEALTPHONESYS - check for duplicate title and alt_phone in entire system
    DUPNAMEPHONELIST - check for duplicate first_name, last_name and phone_number in same list
    DUPNAMEPHONECAMP - check for duplicate first_name, last_name and phone_number in all lists for this list's campaign
    DUPNAMEPHONESYS - check for duplicate first_name, last_name and phone_number in entire system
     "  90DAY - Added to one of the above duplicate checks(i.e. "DUPSYS90DAY"), only checks leads loaded in last 90 days
usacan_prefix_check - Y or N, default is N. Check for a valid 4th digit for USA and Canada phone numbers (cannot be 0 or 1)
usacan_areacode_check - Y or N, default is N. Check for a valid areacode for USA and Canada phone numbers(also checks for 10-digit length)
nanpa_ac_prefix_check - Y or N, default is N. Check for a valid NANPA areacode and prefix, if optional NANPA data is on the system
custom_fields -  Y or N, default is N. Defines whether the API will accept custom field data when inserting leads into the vicidial_list table
   For custom fields to be inserted, just add the field label as a variable to the URL string
   For example, if the field_label is "favorite_color" you would add "&favorite_color=blue"
tz_method -  <empty>, POSTAL, TZCODE or NANPA, default is <empty> which will use the country code and areacode for time zone lookups
    POSTAL relies on the postal_code field
    TZCODE relies on the owner field being populated with a proper time zone code
    NANPA relies on the optional NANPA areacode prefix data being loaded on your system
callback -  Y or N, default is N. Set this lead as a scheduled callback. campaign_id field is REQUIRED for callbacks
callback_status - 1-6 Character, callback status to use, default is CALLBK (vicidial_list status will be set to CBHOLD to lock)
callback_datetime - YYYY-MM-DD+HH:MM:SS, date and time of scheduled callback. REQUIRED if callback is set. NOW can be used for current datetime.
callback_type -  USERONLY or ANYONE, default is ANYONE
callback_user -  User ID the USERONLY callback is assigned to
callback_comments - Optional comments to appear when the callback is called back
lookup_state -  Y or N, default is N. Looks up state field from areacode list. Only works if the 'state' field is not populated.

(for fields with spaces in the values, you can replace the space with a plus + sign[address, city, first_name, etc...])
OPTIONAL FIELDS- 
vendor_lead_code - 1-20 characters
source_id  -  1-50 characters
gmt_offset_now - overridden by auto-lookup of phone_code and area_code portion of phone number if applicable
title -   1-4 characters
first_name -  1-30 characters
middle_initial - 1 character
last_name -  1-30 characters
address1 -  1-100 characters
address2 -  1-100 characters
address3 -  1-100 characters
city -   1-50 characters
state -   2 characters
province -  1-50 characters
postal_code -  1-10 characters
country_code -  3 characters
gender -  U, M, F (Undefined, Male, Female) - defaults to 'U'
date_of_birth -  YYYY-MM-DD
alt_phone -  1-12 characters
email -   1-70 characters
security_phrase - 1-100 characters
comments -  1-255 characters
multi_alt_phones - 5-1024 characters (see examples for more info)
rank -   1-5 digits
owner -   1-20 characters (user ID, Territory or user group)
entry_list_id -  WARNING! ONLY USE IF YOU KNOW WHAT YOU ARE DOING, CAN BREAK CUSTOM FIELDS! (must be all numbers, 3-12 digits, will not work if custom_fields is set to Y)


Multi-ALT-Phones format:

7275551212_1_work!7275551213_1_sister+house!1234567890_1_neighbor

The multi-alt-phones field is formatted as a field of phone-number/phone-code/phone-note set of data(phone code and alt_note are both optional and the phone code can be overridden by the force phone code flag). The record delimiter is an exclamation point with the optional phone code and note delimited within the record by an underscore character _.


Example URL strings for API calls:
http://server/vicidial/non_agent_api.php?source=test&user=6666&pass=1234&function=add_lead&phone_number=7275551111

http://server/vicidial/non_agent_api.php?source=test&user=6666&pass=1234&function=add_lead&phone_number=7275551212&phone_code=1&list_id=999&dnc_check=N&first_name=Bob&last_name=Wilson

http://server/vicidial/non_agent_api.php?source=test&user=6666&pass=1234&function=add_lead&phone_number=7275551111&phone_code=1&list_id=999&dnc_check=N&first_name=Bob&last_name=Wilson&add_to_hopper=Y&hopper_local_call_time_check=Y

http://server/vicidial/non_agent_api.php?source=test&user=6666&pass=1234&function=add_lead&phone_number=7275551111&phone_code=1&list_id=999&dnc_check=N&campaign_dnc_check=Y&campaign_id=TESTCAMP&first_name=Bob&last_name=Wilson&address1=1234+Main+St.&city=Chicago+Heights&state=IL&add_to_hopper=Y&hopper_local_call_time_check=Y&multi_alt_phones=7275551212_1_work!7275551213_1_sister+house!1234567890_1_neighbor

http://server/vicidial/non_agent_api.php?source=test&user=6666&pass=1234&function=add_lead&phone_number=7275551212&phone_code=1&list_id=999&dnc_check=N&first_name=Bob&last_name=Wilson&duplicate_check=DUPLIST-DUPNAMEPHONELIST

http://server/vicidial/non_agent_api.php?source=test&user=6666&pass=1234&function=add_lead&phone_number=7275551212&phone_code=1&list_id=999&custom_fields=Y&favorite_color=blue

http://server/vicidial/non_agent_api.php?source=test&user=6666&pass=1234&function=add_lead&phone_number=7275551111&campaign_id=TESTCAMP&callback=Y&callback_status=CALLBK&callback_datetime=NOW&callback_type=USERONLY&callback_user=6666&callback_comments=Comments+go+here

Example responses: (The "data" values for a successful add_lead request are: phone_number, list_id, lead_id, gmt_offset_now)
SUCCESS: add_lead LEAD HAS BEEN ADDED - 7275551111|6666|999|193715|-4
NOTICE: add_lead ADDED TO HOPPER - 7275551111|6666|193715|1677922

On-hook agents feature

114. Added on-hook agent phone feature. This feature allows inbound calls from
customers to ring on an on-hook agent phone, but not be transferred to 
that agent until the agent's phone is answered. If the call times out 
then the call will go on to the next agent. This is defined in the 
Phones record and allows the agent using the vicidial.php agent screen 
to not have to stay on the phone at all times when they are logged in. 
You will need to add the following lines to the default context in your 
extensions.conf file:
; these are used for the ring_all function in VICIDIAL
exten => _8331*.,1,Playback(sip-silence)
exten => _8331*.,n,AGI(agi-VDAD_RINGALL.agi,${EXTEN})
exten => _8331*.,n,AGI(agi-VDAD_RINGALL.agi,${EXTEN})
exten => _8331*.,n,Hangup

115. Added ring_all Next Agent Call option for in-groups. This works with on-
hook agent phones to allow all available agents to have their phones
ring at the same time, with the first agent to pick up their phone 
receiving the call. It is not recommended to use this on high-volume 
systems or systems with many agents available.

On-hook agents feature

vicidial email

Debian, Ubuntu:

apt-get update && apt-get install postfix mailutils

When prompted for "General type of mail configuration," choose Internet Site.

When prompted for a "Mail name," choose a hostname to be used in mail headers as the origin of your emails. A fully-qualified domain name is preferred, but using your machine's simple hostname is OK. Regardless of what you enter here, your return address will appear to recipients as your Gmail address.

You may be prompted to set the "Root and postmaster mail recipient." Enter root, or another user who should receive mail subsystem notifications.

For any other prompts, you can choose the default values.

Fedora:

dnf update && dnf install postfix mailx

CentOS:

yum update && yum install postfix mailx cyrus-sasl cyrus-sasl-plain

OpenSUSE:

zypper update && zypper install postfix mailx cyrus-sasl

Arch Linux:

pacman -Sy postfix mailutils

FreeBSD:

Compile Postfix from the ports collection to incorporate support for SASL:

portsnap fetch extract update

cd /usr/ports/mail/postfix

make config

In the configuration dialogs, select SASL support. All other options can remain the same. Then:

make install clean

Mailx can be installed from the binary package:

pkg install mailx

2. Configure Gmail Authentication

Create or modify a password file which will be used by Postfix to establish authentication with Gmail. In the authentication information below, replace username with your Gmail username and password with your Gmail password. If you are using a custom Gmail Apps domain name, you may replace gmail.com with your Google Apps domain.

The password file will reside in the Postfix configuration directory. The file can be named whatever you like, but the recommended filename is sasl_passwd.

Debian, Ubuntu, Fedora, CentOS, OpenSUSE, Arch Linux:

Postfix configuration files reside in the directory /etc/postfix. Create or edit the password file:

vi /etc/postfix/sasl_passwd

Add the line:

[smtp.gmail.com]:587    username@gmail.com:password

Save and close the file. Your Gmail password is stored as plaintext, so make the file accessible only by root:

# chmod 600 /etc/postfix/sasl_passwd

FreeBSD:

Postfix configuration files reside in the directory /usr/local/etc/postfix. Create or edit the password file:

vi /usr/local/etc/postfix/sasl_passwd

Add the line:

[smtp.gmail.com]:587    username@gmail.com:password

Save and close the file. Make it accessible only by root:

chmod 600 /usr/local/etc/postfix/sasl_passwd

3. Configure Postfix

There are six parameters which must be set in the Postfix configuration file main.cf. The parameters are:

relayhost, which specifies the mail relay host and port number. The host name will be enclosed in brackets to specify that no MX lookup is required.

smtp_use_tls, which enables (or disables) transport layer security.

smtp_sasl_auth_enable, which enables (or disables) SASL authentication.

smtp_sasl_security_options, which in the following configuration will be set to empty, to ensure that no Gmail-incompatible security options are used.

smtp_sasl_password_maps, which specifies the password file to use. This file will be compiled and hashed by postmap in a later step.

smtp_tls_CAfile, which specifies the list of certificate authorities to use when verifying server identity.

Debian, Ubuntu, Arch Linux:

Edit the main Postfix configuration file:

vi /etc/postfix/main.cf

Add or modify the following values:

relayhost = [smtp.gmail.com]:587
smtp_use_tls = yes
smtp_sasl_auth_enable = yes
smtp_sasl_security_options =
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt

Save and close the file.

Fedora, CentOS:

Edit the main Postfix configuration file:

vi /etc/postfix/main.cf

Add or modify the following values:

relayhost = [smtp.gmail.com]:587
smtp_use_tls = yes
smtp_sasl_auth_enable = yes
smtp_sasl_security_options =
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_tls_CAfile = /etc/ssl/certs/ca-bundle.crt

Save and close the file.

OpenSUSE:

Edit the main Postfix configuration file:

vi /etc/postfix/main.cf

Add or modify the following values:

relayhost = [smtp.gmail.com]:587
smtp_use_tls = yes
smtp_sasl_auth_enable = yes
smtp_sasl_security_options =
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_tls_CAfile = /etc/ssl/ca-bundle.pem

Save and close the file.

OpenSUSE also requires that the Postfix master process configuration file master.cf be modified. Open it for editing:

vi /etc/postfix/master.cf

Locate the line which reads:

#tlsmgr unix - - n 1000? 1 tlsmg

Uncomment it, so it reads:

tlsmgr unix - - n 1000? 1 tlsmg

Save and close the file.

FreeBSD:

Edit the main Postfix configuration file:

vi /usr/local/etc/postfix/main.cf

Add or modify the following values:

relayhost = [smtp.gmail.com]:587
smtp_use_tls = yes
smtp_sasl_auth_enable = yes
smtp_sasl_security_options =
smtp_sasl_password_maps = hash:/usr/local/etc/postfix/sasl_passwd
smtp_tls_CAfile = /etc/mail/certs/cacert.pem

Save and close the file.

4. Process Password File

Use postmap to compile and hash the contents of sasl_passwd. The results will be stored in your Postfix configuration directory in the file sasl_passwd.db.

Debian, Ubuntu, Fedora, CentOS, OpenSUSE, Arch Linux:

postmap /etc/postfix/sasl_passwd

FreeBSD:

postmap /usr/local/etc/postfix/sasl_passwd

5. Restart Postfix

Restart the Postfix service, putting your changes into effect.

Debian, Ubuntu, Fedora, CentOS, OpenSUSE, Arch Linux:

systemctl restart postfix.service

FreeBSD:

To start the Postfix service for this session only:

service postfix onestart

To start Postfix automatically when the system initializes, open /etc/rc.conf for editing:

vi /etc/rc.conf

Add the line:

postfix_enable=YES

Save and close the file. You may then run:

service postfix start

To start Postfix.

6. Enable "Less Secure Apps" In Gmail

By default, only the most secure sign-ins, such as logging in to Gmail on the web, are allowed for your Gmail account. To permit relay requests, log in to your Gmail account and turn on Allow less secure apps.

For more information, review the Google Support document "Allowing less secure apps to access your account."

7. Send A Test Email

Test your new configuration by sending an email using the mail command. Run:

mail -s "Test subject" recipient@domain.com

You will be presented with a blank line (or a CC: field, which you can bypass by pressing Enter). Type the body of your message, pressing Enter for new lines. When you are finished composing the email, type CTRL-D to send it. To cancel the email, press CTRL-C twice.

To send a precomposed email, use the command:

mail -s "Subject Here" recipient@domain.com < textfile

Where textfile is the name of a file containing the text to be sent.

Troubleshooting

If it's not working, check the logs for any Postfix errors:

Debian:

less /var/log/mail.log

Ubuntu, Fedora, CentOS, OpenSUSE, Arch Linux:

journalctl

FreeBSD:

less /var/log/maillog

If you receive authentication errors from Gmail, verify that Allow Less Secure Apps is turned on in your Gmail account settings, as specified in Step 6.

Verify that the password file sasl_passwd exists, and that its contents are formatted correctly, as specified in Step 2. If you make any changes to the password file, make sure to repeat Steps 4 and 5 to hash the new password file and restart Postfix.

If you see any TLS errors, double check the configuration in main.cf as specified in Step 3. If you make any configuration changes, restart Postfix as specified in Step 5.

 52  2018-11-21 22:44:48 zypper -n install postfix

   54  2018-11-21 22:46:51 zypper -n install cyrus-sasl

   55  2018-11-21 22:47:06 zypper -n install cyrus-imapd

   56  2018-11-21 22:47:21 zypper -n install cyrus-sasl cyrus-sasl-lib cyrus-sasl-plain

   57  2018-11-21 22:47:32 nano /etc/postfix/sasl_passwd

   58  2018-11-21 22:48:39 nano /etc/postfix/main.cf

   59  2018-11-21 22:50:26 ls /etc/ssl/certs/ca-certificates.crt

   60  2018-11-21 22:50:34 ls /etc/pki/tls/certs/ca-bundle.crt

   61  2018-11-21 22:50:48 nano /etc/postfix/main.cf

   62  2018-11-21 22:52:14 chown postfix /etc/postfix

   67  2018-11-21 22:54:06 postmap hash:/etc/postfix/sasl_passwd

error logs 

journalctl -u postfix.service

  journalctl | grep gmail


vicibox81:~ # echo "This is a test" | mail -s "Test" ambiorixg12@gmail.com

http://www.postfix.org/STANDARD_CONFIGURATION_README.html

http://postfix.state-of-mind.de/patrick.koetter/smtpauth/smtp_auth_mailservers.html

http://postfix.state-of-mind.de/patrick.koetter/smtpauth/smtp_auth_mailservers.html

https://ukietech.com/blog/programming/how-to-set-up-email-sending-from-godaddy-server-using-postfix

http://www.postfix.org/postconf.5.html

https://www.redwireservices.com/postfix-smtp-relay-via-godaddy-alternate-port-and-others