New answers tagged email
The original specification of the Maildir format would be good start to answer your question. The requirement is that each new message will be stored with a unique name. Unless you're writing messages to a maildir, the format of a unique name is none of your business. A unique name can be anything that doesn't contain a colon (or slash) and ...
To do this you need to have your server 'known' to the internet so that the rest of the world (including google mail) knows where to push your emails. And then run an MTA on your server (like postfix) that the outside world can connect to, to deliver the email. The MTA is then responsible for delivering to the the spool directory. I am pretty sure that ...
It is called quoted-printable. I take the opportunity to link to another doc worth reading about character encodings: http://utf8everywhere.org/ [of course, not possible in emails, and that's why they use other types of encoding there... But still, good to read when you are about to choose which encoding to use!]
The format of the message is RFC 2282, the Internet Message Format. The file format sounds like you're describing the mbox format, which is RFC 4155. According to RFC 4155, a new message in an mbox database begins with the From keyword, a single space then the address of the reported sender, a single space and the UTC date of when the message was received. ...
The message in your inbox are separated by a double newline followed by From (notice there is no : after from. That is the simple answer. Of course you can send an email which contains one or more emails as text, including headers and that is where things get messy. If the sending program (or your programs that write the inbox) does not add length ...
That should match all your expections . http://www.mavinerc.com/home/2012/05/11/1186/
You have a rule to let the traffic out, but you don't have a rule to let the return traffic in. I'm guessing you meant for these 2 rules to be -A INPUT instead: iptables -A OUTPUT -p tcp --sport 25 -j ACCEPT iptables -A OUTPUT -p tcp --sport 587 -j ACCEPT However using the source port as a method of allowing return traffic in is a bad way to secure the ...
Any user can potentially run cron jobs. The man user might purge the catman cache. The bin user might do library and package management. The www-data user might purge caches. If any of these cron jobs give output (often to indicate a problem) it is nice to let someone know, and cron does this by default by mailing the running user. Now the simple thing to ...
the problem you are facing is, that things work a little bit differently than how you expect them to run. this is not how it works: exim receives an email exim passes the email to spamd spamd checks the email for spam and adds necessary headers spamd passes the (modified) email back to exim exim delivers the email instead it works like this: exim ...
This is a cron job that updates the indexes for mlocate, which is used when you run locate on your system to find files. This index allows the program to quickly find files without traversing the filesystem (which is much more expensive, because it's not optimised for that use case). For some reason, the lock file that stops more than one database update ...
No, as point 1 cannot be done. mail doesn't do IMAP or POP3 as provided by Dovecot. (Also once you link your home directory to /usr/bin/mail or /usr/bin/sendmail - can not do both - you not login anymore. do not do that)
Turns out the GECOS field needs to be filled in for the original user, not the user that the emails are being masqueraded to appear to be from.
With mutt instead of mail you would simply call echo "body" | mutt -s "subject" -a attachment0 attachment1 [...] -- email@example.com Here, attachmentN are the list of files that you want to attach.
The simple way: to use uuencode. Any formatting or body text are unavailable. Just a email with attachement and custom subject. uuencode /path/to/file file_name.ext | mail -s subject firstname.lastname@example.org The complex way: to use sendmail and html formatting: v_mailpart="$(uuidgen)/$(hostname)" echo "To: email@example.com Subject: subject Content-Type: multipart/mixed; ...
Top 50 recent answers are included