MIME is an e-mail message protocol (described in RFCs 1521 and 1522)
that allows messages to incorporate non-text content while still remaining compliant with RFC 822.
Obsoleted by RFC2045+.
RFC 2025, 2046, 2047, 2048, 2049 - MIME Multipurpose Internet Mail Extensions
RFC 2822, Internet Message Format :
defines the syntax of email messages themselves, including the headers (supercedes RFC 822).
RFC 2920, SMTP Service Extension for Command Pipelining :
defines an SMTP protocol extension that allows multiple commands to be sent within one TCP send operation.
RFC 3030, SMTP Service Extensions for Transmission of Large and Binary MIME Messages :
defines an SMTP extension for attaching large binary objects to email messages.
.--------------------------------------------.
| server |
| |
| 25 110 pop3 143 imap |
| 465 587 995 pop3s 993 imaps |
.--------------------------------------------.
^ ^ | |
| | V V
[smtp] [ssmtp] [pop3] [imap]
^ ^ | |
| | V V
.--------------------------------------------.
| client |
.--------------------------------------------.
SMTP
Es fa servir per enviar missatges al servidor SMTP
port 465 versus 587
Resum de diferències
Característica Port 587 Port 465
Xifratge STARTTLS (TLS explícit) SSL/TLS implícit (des de l'inici)
Inici Connexió Text pla, després s'actualitza a TLS Directament xifrat amb TLS
Estat Actual Estàndard i recomanat Històricament usat; alguns el consideren "obsolet", altres "rehabilitat" (confús)
POP3 is just a protocol to get an SMTP buffer from a server,
and SMTP does not deal with folders.
IMAP4
Internet Message Access Protocol (IMAP) is an Internet standard protocol
used by e-mail clients to retrieve e-mail messages from a mail server over a TCP/IP connection.
IMAP was designed with the goal of permitting complete management of an email box by multiple email clients.
Therefore clients generally leave messages on the server until the user explicitly deletes them.
An IMAP server typically listens on port number 143.
IMAP over SSL (IMAPS) is assigned the port number 993.
RFC 3501 - Internet Message Access Protocol - version 4rev1
SMTP transports a mail object. A mail object contains an envelope and content.
The SMTP envelope is sent as a series of SMTP protocol units.
It consists of an originator address
(to which error reports should be directed);
one or more recipient addresses;
and optional protocol extension material.
The SMTP content is sent in the SMTP DATA protocol unit
and has two parts: the headers and the body.
If the content conforms to other contemporary standards,
the headers form a collection of field/value pairs
structured as in the message format specification;
the body, if structured, is defined according to MIME.
4.1 SMTP commands Semantics and Syntax
The SMTP commands define the mail transfer
or the mail system function requested by the user.
SMTP commands are character strings terminated by <CRLF>.
The commands themselves are alphabetic characters terminated by <SP>
if parameters follow and <CRLF> otherwise.
SMTP commands
4.1.1.1 Extended HELLO (EHLO) or HELLO (HELO)
Indicate client's identity
4.1.1.2 MAIL (MAIL)
This command is used to initiate a mail transaction
in which the mail data is delivered to an SMTP server
which may, in turn, deliver it to one or more mailboxes
or pass it on to another system.
4.1.1.3 RECIPIENT (RCPT)
This command is used to identify an individual recipient of the mail data;
multiple recipients are specified by multiple use of this command.
4.1.1.4 DATA (DATA)
This command causes the mail data to be appended to the mail data buffer.
The mail data is terminated by a line containing only a period,
that is, the character sequence "<CRLF>.<CRLF>"
4.1.1.5 RESET (RSET)
This command specifies that the current mail transaction will be aborted.
Any stored sender, recipients, and mail data MUST be discarded,
and all buffers and state tables cleared.
The receiver MUST send a "250 OK" reply to a RSET command with no arguments.
A reset command may be issued by the client at any time.
4.1.1.6 VERIFY (VRFY)
This command asks the receiver to confirm
that the argument identifies a user or mailbox.
4.1.1.7 EXPAND (EXPN)
This command asks the receiver to confirm that the argument
identifies a mailing list, and if so, to return the membership of that list.
4.1.1.8 HELP (HELP)
Syntax:
"HELP" [ SP String ] CRLF
4.1.1.9 NOOP (NOOP)
This command does not affect any parameters or previously entered commands.
It specifies no action other than that the receiver send an OK reply.
4.1.1.10 QUIT (QUIT)
This command specifies that the receiver MUST send an OK reply,
and then close the transmission channel
There are three steps to SMTP mail transactions.
The transaction starts with a MAIL command
which gives the sender identification.
(In general, the MAIL command may be sent only
when no mail transaction is in progress; see section 4.1.4.)
A series of one or more RCPT commands
follows giving the receiver information.
Then a DATA command initiates transfer of the mail data
and is terminated by the "end of mail" data indicator,
which also confirms the transaction.
(1)
The first step in the procedure is the MAIL command.
MAIL FROM:<reverse-path> [SP <mail-parameters> ] <CRLF>
If accepted, the SMTP server returns a 250 OK reply. Normally, failures produce 550 or 553 replies.
(2)
The second step in the procedure is the RCPT command.
If accepted, the SMTP server returns a 250 OK reply
and stores the forward-path.
If the recipient is known not to be a deliverable address,
the SMTP server returns a 550 reply.
(3)
The third step in the procedure is the DATA command
(or some alternative specified in a service extension).
DATA <CRLF>
SMTP indicates the end of the mail data by sending a line containing only a "." (period or full stop).
If accepted, the SMTP server returns a 250 OK reply.
When RFC 822 format is being used,
the mail data include
the memo header items such as Date, Subject, To, Cc, From.
RFC 822 describes a generic message format,
and specifies some standard header information.
It says almost nothing about the body of the messages,
except that it is a chunk of ASCII text.
MIME takes advantage of that
by superimposing a format for the body text,
and it also defines some header lines of its own.
The neat thing is that since the body is still just a chunk of text,
it doesn't break any rules established by RFC 822.
This means that any RFC 822-compliant transport system
can handle MIME messages without modification.
Of course, the receiving clients of the message do care
because that chunk of text has to be converted back into a binary file.
They can do this only
if they know about the format of the message,
i.e., only if they are MIME-compliant mail readers.
#!/usr/bin/python
#
# send mail: to whoever, from whoever you think of, and from wherever you want to be :-)
#
import sys
# import socket
import smtplib
if __name__ == '__main__': # run this code only if NOT imported
print( sys.argv )
if len(sys.argv) != 5:
print( "format is <from> <to> <subject> <body>\n" )
sys.exit (-1)
else:
smtpconn = smtplib.SMTP ('localhost')
print( "Sending mail from:", sys.argv[1] )
print( "Sending mail to:", sys.argv[2] )
print( "Subject:", sys.argv[3] )
print( "Body:", sys.argv[4] )
print( "in progress..." )
smtpconn.sendmail (sys.argv[1], sys.argv[2], "Subject: " + sys.argv[3] + "\r\n" + sys.argv[4])
print( "done" )
sys.exit (0)
Requires (as Golemz) a Debian + exim (SMTP server)
A message sent to Gmail comes up as
(Open + More Options + Show Original) :
X-Gmail-Received: 725288c5991ed284d30fd3ef126d7e9433597cf8
Delivered-To: sebastiasebas@gmail.com
Received: by 10.38.125.77 with SMTP id x77cs11720rnc;
Wed, 27 Oct 2004 08:04:14 -0700 (PDT)
Received: by 10.38.152.73 with SMTP id z73mr855689rnd;
Wed, 27 Oct 2004 08:04:13 -0700 (PDT)
Return-Path: <fromme.casameva@quisapon.net>
Received: from karisma ([62.57.139.245])
by mx.gmail.com with ESMTP id 63si3302rna;
Wed, 27 Oct 2004 08:04:13 -0700 (PDT)
Received-SPF: neutral (gmail.com: 62.57.139.245 is neither permitted nor denied by
domain of fromme.casameva@quisapon.net)
Received: from karisma ([127.0.0.1])
by karisma with esmtp (Exim 3.35 #1 (Debian))
id 1CMpJJ-00038a-00
for <sebastiasebas@gmail.com>; Wed, 27 Oct 2004 17:02:01 +0200
Subject: Tema del dia
Message-Id: <E1CMpJJ-00038a-00@karisma>
From: fromme.casameva@quisapon.net
Bcc:
Date: Wed, 27 Oct 2004 17:02:01 +0200
Hola xaval - ke me'n dius ?
A similar message sent to Yahoo comes up as
(Full Headers) :
X-Apparently-To : sebastiasebas@yahoo.com via 206.190.39.206; Wed, 03 Nov 2004 09:15:08 -0800
X-YahooFilteredBulk : 62.57.139.245
X-Originating-IP : [62.57.139.245]
Return-Path : <kagalda.o.no@kagalda.brut>
Received : from 62.57.139.245 (EHLO karisma) (62.57.139.245) by mta108.mail.re2.yahoo.com
with SMTP; Wed, 03 Nov 2004 09:15:08 - 0800
Received : from karisma ([127.0.0.1]) by karisma with esmtp (Exim 3.35 #1 (Debian)) id 1CPOhN-0005Ms-00 for
<sebastiasebas@yahoo.com>; Wed, 03 Nov 2004 18:13:29 +0100
Subject : Tema del dia
Message-Id : <E1CPOhN-0005Ms-00@karisma>
From : kagalda.o.no@kagalda.brut
Bcc :
Date : Wed, 03 Nov 2004 18:13:29 +0100
Content-Length : 28
Hola xaval - ke me'n dius ?
Sending mail
from perl
#!/usr/bin/perl
$to = 'abcd@gmail.com';
$from = 'webmaster@yourdomain.com';
$subject = 'Test Email';
$message = 'This is test email sent by Perl Script';
open(MAIL, "|/usr/sbin/sendmail -t");
# Email Header
print MAIL "To: $to\n";
print MAIL "From: $from\n";
print MAIL "Subject: $subject\n\n";
# Email Body
print MAIL $message;
close(MAIL);
print "Email Sent Successfully\n";
cat my_message.txt | ssmtp myusername@gmail.com
Where my_message can be formatted to have lines for TO: and SUBJECT: and the body.
TO: abc@def.com
SUBJECT: Testing
-blank line-
Message body goes here....
2.- from bash using mail command
As "/home/sag/eines/backup_per_email/snd_email.sh" :
#!/bin/bash
echo "Trace filesystem status into a file"
myLog=/home/pi/logs/df.log
echo "Generated by /home/pi/sendemail/snd_1.sh" > $myLog
df -h >> $myLog
echo "Get external IP"
ipvariable=$(curl -m 2 -s icanhazip.com);
ipvariable=$(curl -m 2 -s http://checkip.amazonaws.com);
rc1=$?
echo ">>> (2) icanhazip rc ($rc1)" >> $myLog
echo "Send an email with a file attached"
echo "Today my external IP is {$ipvariable}."
echo "Today my external IP is {$ipvariable}." | mail --attach=$myfn -s "From RaspPi service provider" nom1@gmail.com, nom2@gmail.com
# sometimes attachment is provided via "-a $myfn"
echo "Si hi ha problemes, revisa /var/log/mail.log i /var/log/mail.err"
echo '.'
Configuration is in /etc/ssmtp/ssmtp.conf
from bash using mutt
Using mutt is far better from the configuration point of view : ~/.muttrc (privat) i /etc/Muttrc (global)
See /usr/share/doc/mutt/README.Debian for details.
# echo "my body" | mutt -s "my subject" -i body.txt -a attachment.txt recipient@example.com
-s used to specify subject of mail.
-i used to specify file containing message body.
-a used to specify attachment file, must be placed at the end of command line options
when attaching sigle or multiple files, separating filenames and recipient addresses with "--" is mandatory (man mutt)
sebas@pi0alby:~ $ echo "my BODY" | mutt -s "my SUBJECT" -- destinations@gmail.com
A one-liner with an attachment :
sebas@pi0alby:~ $ echo "my Backup is attached" | mutt -s "my Todays backup" -a my_file.tgz -- destinations@gmail.com
GPGME: CMS protocol not available
SMTP session failed: 552 5.3.4 Error: message file too big {file was 66 MB}
Could not send the message.
We always want to do it from bash :
sebas@minie:~/eines/bash$ cat 1_email_mutt.sh
#!/bin/bash
my_version="v 1.e"
myT=$(date +%R) # short time
myD=$(date +"%d/%m/%Y") # short date, 4 digit year, day before month
szHora="$myT,$myD"
my_body="*** ($szHora) - ($HOSTNAME) - cos del missatge + "${my_version}
my_subject="### ($szHora) Minie sends Email "${my_version}
echo "${my_body}" | mutt -d 5 -s "${my_subject}" -- "${my_destination}" # debug at max level
cat ~/.muttdebug0 # display last session trace
exit 0
20221106 - an error at R3, or how to debug a mutt problem
sag@odin:~ $ echo "my BODY" | mutt -s "my SUBJECT" -- seb@gmail.com
GPGME: CMS protocol not available
SASL authentication failed
Could not send the message.
sag@odin:~ $ echo "my BODY" | mutt -d 5 -s "my SUBJECT" -- seb@gmail.com
sag@odin:~ $ cat ~/.muttdebug0
[2022-11-06 14:22:39] External authentication name: adb30
[2022-11-06 14:22:39] mutt_sasl_cb_authname: getting authname for smtp.tinet.cat:465
[2022-11-06 14:22:39] mutt_sasl_cb_authname: getting user for smtp.tinet.cat:465
[2022-11-06 14:22:39] mutt_sasl_cb_pass: getting password for adb30@smtp.tinet.cat:465
[2022-11-06 14:22:39] 4> AUTH PLAIN YWRiMzAAYWRiMzAAYWRiMzAyMDAz
[2022-11-06 14:22:41] 4< 535 5.7.8 Error: authentication failed:
Solution : fix password in /etc/Muttrc, field smtp_pass
Backups are sent to
manel@yandex (+) &
sveta@aol (+) : mars/minie, pi0, odin, henry, r4
IPs are sent to pere@yandex (?) &
bisc2k9@g (+) &
z.berto (-) : mars, pi0, odin, henry
sebas@minie:~/dades/python/email/IMAP_read_mail$ ./yndx_pere_mars.sh
++++++++++++++++++++ Got (5) params.
++++++++++++++++++++++++++++++++++++++++ User (pere.pocapor).
++++++++++++++++++++++++++++++++++++++++ Pwd (iddujkfoaaycmgai).
++++++++++++++++++++++++++++++++++++++++ Box (mars).
++++++++++++++++++++++++++++++++++++++++ Server (imap.yandex.com).
(1) *** connect to server ( imap.yandex.com ).
(2) *** login to user ( pere.pocapor ).
(3) *** list of available folders or gmail labels
(4) *** connect to specific folder ( mars ).
(5) tenim 3 msg
(6) select ( 1 2 3 ) msg
(7) IDS ( b'1 2 3' ).
(8) ID LIST ( [b'1', b'2', b'3'] ).
(9) Msg ID is ( b'1' 3 ).
(10) subject { MARS, 18:07,24/07/2025 }
(9) Msg ID is ( b'2' 3 ).
(10) subject { ### tema del missatge + v 1.d }
(9) Msg ID is ( b'3' 3 ).
(10) subject { ### tema del missatge + v 1.d }
(11) close
(12) logout user {pere.pocapor} - shutdown connection to server {imap.yandex.com}.
Some more configuration is in file "/etc/Muttrc.d/gpg.rc"
individual configuration : vim ~/.mutt/muttrc
We shall use the "global" configuration, for all users of the machine
$ cat /etc/Muttrc
set from = "my_tinet_user@t1net.cat"
set realname = "My Name to be seen"
set imap_user = "my_tinet_user@t1net.cat"
set imap_pass = "my_tinet_pwd"
set smtp_url = "smtps://my_tinet_user@smtp.t1net.cat:465/"
set smtp_pass = "my_tinet_pwd"
set folder = "imaps://imap.t1net.cat:993" ; compte : tinet no te servei IMAP, nomes POP
set spoolfile = "+INBOX"
set header_cache = "/home/my_linux_user/.mutt/cache/headers"
set message_cachedir = "/home/my_linux_user/.mutt/cache/bodies"
set certificate_file = "/home/my_linux_user/.mutt/certificates"
set ssl_verify_host = no
set ssl_verify_dates = no
set mail_check = 120
set move = no
set imap_keepalive = 900
set sort = threads
set editor = "vi"
# do not write all messages to the "sent" file
set copy = no
$ mutt -D
or more specific with
mutt -D | grep use_gpg
missatge de error - GPGME: CMS protocol not available
No fem servir gpg pero rebem el missatge "GPGME: CMS protocol not available"
sag@odin:~/eines/backup $ mutt -D | grep use_gpgGPGME: CMS protocol not available
crypt_use_gpgme is set
pgp_use_gpg_agent is unset
Launch mutt with option '-e "set crypt_use_gpgme=no"'
Podremos
optar por instalar el paquete correspondiente: "apt-get install gpgsm"
O bien por deshabilitar el uso de GPGME en /etc/Muttrc.d/gpg.rc modificando:
set crypt_use_gpgme=yes
en
set crypt_use_gpgme=no
Ignorem el missatge
mutt fa backup de 1 fitxer
Codi a minie :
sebas@minie:~/eines$ cat 6_save_file_2_email.sh
#!/bin/bash
myT=$(date +%R)
myFile1="default filename"
if [ $# -eq 0 ]
then
echo "--- No arguments supplied"
exit 1
else
myFile1=$1
fi
echo ">>> backup by email of file " $myFile1
szCos="('$myT') cos x1 fitxer"
szSbj="('$myT') backup x1 fitxer"
szDesti="manel@yandex.com, sveta@aol.com"
echo "$szCos" | mutt -s "$szSbj" -a "$myFile1" -- $szDesti
rv=$?
echo "mutt rc = " $rv
exit 0
mutt fa backup dels fitxers importants
A diferents llocs fem un TGZ dels fitxers importants que tenim en una llista :
from imap_tools import MailBox # python3 -m pip install imap_tools
# Get date, subject and body len of all emails from INBOX folder
with MailBox('imap.mail.com').login('test@mail.com', 'pwd') as mbox:
for msg in mbox.fetch():
print(msg.date, msg.subject, len(msg.text or msg.html))
old mail
When you exit the "mail" command and some messages were not deleted, you get the message :
Saved 6 messages in /home/nicolau/mbox
Held 0 messages in /var/mail/nicolau
You can review old emails by :
nicolau@mars:~$ mail -f ~/mbox
Tinet
Acces al email :
Tipus de servidor de Tinet: POP (Tinet no ofereix servei IMAP)
Aixi, no podem accedir al correu de Tinet des python amb imap.py
To use Blat you must make sure that you have access
to a SMTP server via TCP-IP.
Com saber que el servidor de correu sortint està funcionant ?
netstat -an | grep 25
Com es fa servir ?
Syntax: c:\blat\blat.exe msg_body_file -t recipient -server mailserver -f sender -s subject
Example -
Mail server="smtp.mymail43.com",
recipient="test@mymail43.com",
subject="Error",
Body of e-mail=contents of file "body.txt" and
sender=same as recipient (most mail servers requires an existing sender address)
BLAT.EXE body.txt -t test@mymail43.com -server smtp.mymail43.com -f test@mymail43.com -s Error
Incoming Mail (POP3) Server - requires SSL: pop.gmail.com
Use SSL: Yes
Port: 995
Outgoing Mail (SMTP) Server - requires TLS or SSL: smtp.gmail.com (use authentication)
Use Authentication: Yes
Port for TLS/STARTTLS: 587
Port for SSL: 465
@echo off
SET USR=gmailuser
SET PWD=gmailpwd
SET SRC=origin_user@gmail.com
SET DST=destination_user@gmail.com
SET CCOPY=copied_user@domain.com
SET BCCCPY=blind_copied@dom.com
SET SBJ="subjecte de la carta"
SET MSG="msg body"
SET SVR=smtp.gmail.com
SET ATX=F1.TXT
SENDEMAIL -f %SRC% -t %DST% -cc %CCOPY% -bcc %BCCCPY% -u %SBJ% -m %MSG% -s %SVR% -a %ATX% -xu %USR% -xp %PWD%
June 2010 :
Jun 27 11:43:53 sap200xpsp3 SENDEMAIL[7216]: NOTICE => Authentication not supported by the remote SMTP server!
Jun 27 11:43:53 sap200xpsp3 SENDEMAIL[7216]: ERROR => Received: 530 5.7.0 Must issue a STARTTLS command first.
April 2017 :
c:\eines> sndemail.cmd
Apr 02 14:42:39 w500-w2008r2 sendEmail.exe[3060]: Email was sent successfully!
The first thing to do is to open a connection from your computer to your mail server.
telnet mail.domain.ext 25
You should receive a reply like:
Trying ???.???.???.???...
Connected to mail.domain.ext.
Escape character is '^]'.
220 mail.domain.ext ESMTP Sendmail ?version-number?; ?date+time+gmtoffset?
You will then need to declare where you are sending the email from:
HELO local.domain.name
Dont worry too much about your local domain name
although you really should use your exact fully qualified domain name
as seen by the outside world.
The mail server has no choice but to take your word for it
as of RFC822-RFC1123.
This should give you:
250 mail.domain.ext Hello local.domain.name [loc.al.i.p], pleased to meet you
Now give your email address:
MAIL FROM: mail@domain.ext
Should yield:
250 2.1.0 mail@domain.ext... Sender ok
Now give the recipients address:
RCPT TO: mail@otherdomain.ext
Should yield:
250 2.1.0 mail@otherdomain.ext... Recipient ok
To start composing the message issue the command DATA
If you want a subject for your email type
DATA
Subject:-type subject here-
then press enter twice (these are needed to conform to RFC 882)
You may now proceed to type the body of your message
(e.g. hello mail@otherdomain.ext from mail@domain.ext)
To tell the mail server that you have completed the message enter a single "." on a line on it's own.
The mail server should reply with:
250 2.0.0 ???????? Message accepted for delivery
You can close the connection by issuing the QUIT command.
The mailserver should reply with something like:
Here are a list of problems I've encountered and their fixes :
501 nouser@nosuchplace.here... Sender domain must exist
The domain that you are sending from must exist
503 Need MAIL before RCPT
A recipient has been specified before a sender.
550 mail@domain.ext... Relaying Denied
The mail server has refused to relay mail for you, this may be for any number of reasons but typical resons include:
Not using this provider for an internet connection and/or
Not using an email address provided by the owner of the server.
Obre
aquesta pàgina.
Fixat-hi que hi ha un "." (punt) al final de la URL.
Copia la URL en un Emilio.
Envia'l.
En rebre'l, el "punt" haurà desaparegut automàgicament.
Comprobat amb :
Gmail
Yahoo
Lotus Notes
SendEmail
Outlook
Eudora ? Encara no ...
Això ho ha descobert .. en Toni !
Ed uses :
bash shell script plus smtpclient.exe -- a open source SMTP connection and send utility.
postfix no longer logs to /var/log/mail after it has been deleted and re-created - restart service by
$ sudo service rsyslog restart
cannot open mailbox /var/mail/fmaster: Permission denied - No mail for fmaster
$ sudo adduser fmaster mail ; add to group
$ mail -s "Test Subject" fmaster@localhost < /dev/null ; send first mail, provide an empty message body
$ echo "message body" | mail -s "subject" fmaster@localhost ; set body and subject
$ sudo chmod ug+rw /var/mail/fmaster ; file is created on receive the first mail so now we can modify it
Again :
nicolau@nicolau-desktop:/var/mail$ sudo touch /var/mail/nicolau ; create file
nicolau@nicolau-desktop:/var/mail$ sudo chown nicolau:mail /var/mail/nicolau ; owner is nicolau, group is mail
nicolau@nicolau-desktop:/var/mail$ sudo chmod o-r /var/mail/nicolau ; others cant read
nicolau@nicolau-desktop:/var/mail$ sudo chmod g+rw /var/mail/nicolau ; group can read and write
nicolau@nicolau-desktop:/var/mail$ mail
No mail for nicolau
click on the Gear icon (Settings) in the top right corner and select "See all settings"
go to the "Forwarding and POP/IMAP" tab
under "IMAP access," make sure "IMAP is enabled" is selected
click "Save Changes" at the bottom
generate APP password
If you have 2FA enabled on your Google account (highly recommended!), you must generate an App Password to use with Mutt.
You cannot use your regular Google account password directly. This provides an extra layer of security.
If you don't use 2-Step Verification, Google historically allowed "Less secure app access."
However, this option is being phased out or already removed for many accounts due to security concerns.
under "Signing in to Google," if you have 2-Step Verification enabled, you'll see "App passwords." Click on it.
in "Security" under "Signing in to Google," click on (or search for) "App passwords." You might need to sign in again.
select "Mail" for the app and "Other (Custom name)" for the device. You can name it "Mutt" or anything you prefer.
click "Generate."
Google will display a 16-character password.
Copy this password immediately, as it will only be shown once.
This is the password you will use in your Mutt configuration, not your regular Google password.
Free Gmail SMPT server
Outgoing Mail (SMTP) Server: smtp.gmail.com
Use Authentication: Yes
Use Secure Connection: Yes (this can be TLS or SSL depending on your mail client)
We start with Gemini "configure gmail smtp access from mutt"
Sometimes it insists on using ssmtp or msmtp MTA agents
sebas@minie:~$ cat /etc/Muttrc
## SAG, 20250717
set from = "bcn.borinot@gmail.com"
set realname = "Mutt at Minie"
# SMTP - enviar correu
set smtp_url = "smtp://bcn.borinot@gmail.com@smtp.gmail.com:587/" # using port 587 for TLS
set smtp_pass = "olpv cdhv jxfg mljl"
# use TLS for secure connection
set ssl_starttls = yes
set ssl_force_tls = yes
# Authentication method (usually login)
set smtp_authenticators = 'login'
If you receive the message “Username failure or POP3/IMAP disabled”,
the mail program cannot access the mailbox over POP3/IMAP.
Make sure your email account password is correct and POP3/IMAP is enabled in the
Email clients section.
http://www.godaddy.com/ :
Your email account includes 250 SMTP relays per mailbox per day.
This lets you send 250 emails from your email address on a daily basis.
You can send messages to up to 100 total addresses per email message.
250 emilios/dia x 100 persones/emilio x 10 MB/persona = 250.000 MB/dia
Gmail automatically rewrites the "from" line of any e-mail you send via their SMTP gateway to your Gmail address
Gmail overrides any Reply-To settings you may have in your e-mail software in favor of the one in Gmail's web interface
Gmail SMTP does not use port 25 - ISP invisible !
