Postfix and save to sent mail dir - linux

I know this might be a dummy question or a question that comes from lack of knowledge, but I hope someone can still answer it. I did try to read a lot of Postfix documentation but found no answer to this. I don't even know if it's a Postfix specific or mail servers general question.
So I have a mail server, just a clean Postfix install that delivers email.
I've defined my users and connected with IMAP and SMTP using Thunderbird.
When I went to Thunderbird account settings and disabled "place a copy", Postfix did not put a copy of the sent message in the user .Sent folder.
However, I've also connected my Gmail, Hotmail or Yahoo mail and disabled the "place a copy" and still have a copy in the sent items folder.
So in this case there are 2 options:
Something is wrong with my Postfix configuration
Gmail, Hotmail, Yahoo put a copy in their sent folder as a different process on the server side

Just for the record, having searched around for a how to, and not finding one, I am posting it here:
The only (easy) way I've found to save sent emails is the sender_bcc solution (with it's attendant faults):
I am using postfix / dovecot / sieve / mysql virtual boxes
In /etc/postfix/main.cf add:
sender_bcc_maps = mysql:/etc/postfix/mysql-virtual-bcc-maps.cf
Create file /etc/postfix/mysql-virtual-bcc-maps.cf:
user = (database user)
password = (database password)
hosts = 127.0.0.1
dbname = (database databasename)
query = SELECT CONCAT_WS('',LEFT('%s', LOCATE('#', '%s')-1),'+sent#',SUBSTRING('%s', LOCATE('#', '%s')+1)) AS destination FROM virtual_users WHERE email='%s' AND autosent=1
You'll note in my query, I've added a (tinyint default 0) column to my virtual_users table so I can turn on/off this automatic sent items feature per user. This query takes the sender email address that postfix gives it, splits it in half at the # sign, and adds +sent to the address so it looks like sender+sent#domain.tld. This allows sieve in the next step to pick it up and drop it straight to sent items.
In /etc/dovecot/sieve/default.sieve add:
require ["fileinto", "mailbox", "envelope", "subaddress","imap4flags"];
if envelope :detail "to" "sent" {
addflag "\\Seen";
fileinto :create "Sent";
stop;
}
Also helpful to modify /etc/dovecot/conf.d/15-mailboxes.conf and add the auto subscribe to sent (and junk and trash and others for that matter):
mailbox Sent {
special_use = \Sent
auto = subscribe
}
I think that is all (I'm posting this the next day after doing it, so I think I got it all...)

Postfix itself does not place copies of sent messages anywhere; it receives messages and delivers them to the recipient. Saving sent messages to your own mailbox is the responsibility of your user agent (Thunderbird, in your case).
It's important to understand that Postfix (and other traditional Unix SMTP servers) don't have a "user" concept. Yes, if so configured it's possible to authenticate by supplying a username and a password, but Postfix doesn't use this identity information.
That said, it's not impossible to configure Postfix to do what you expected – sender_bcc_maps can be used to add a recipient to messages sent by you, and by adding yourself and using a filter in your mail client (or mail delivery agent like procmail) you can make sure that messages sent by you end up in the Sent folder.

I am running a Installation with automatic copies created by sender_bcc_maps. It's working fine. You have to check the sender, otherwise everyone can create sent mails in foreign sent folders.
I have solved it with two virtual domains. One for the user and one for the copy.
But there is a big problem with sender_bcc_maps. All bcc senders will be deleted in the sent copy. You cannot see anymore, who got a blind copy of this mail.

As 'ego2dot0' said above, you don't need any MDA filters (sieve etc.) to do this. It can be done using Postfix alone, although it took me a while to figure out how to do it.
You have to use sender_bcc_maps AND virtual_mailbox_maps features together.
You have to use a virtual domain dedicated specially for copies to self. If your actual domain is "your.domain.tld", you can use eg. subdomain "copyself.your.domain.tld". This subdomain does not have to actually exist, ie. be defined in the DNS (moreover, it's better that it isn't defined, so nobody accidentally sends mail to it from outside). It is a purely virtual domain that is recognized only by Postfix.
1) Configure sender_bcc_maps to BCC mail coming from user#your.domain.tld to user#copyself.your.domain.tld. You can do it for only a few selected users using a regular "hash" type map, or you can do it for all users at once using PCRE type map and regular expressions.
2) You have to define your virtual domain in virtual_mailbox_domains, like this:
virtual_mailbox_domains=copyself.your.domain.tld
3) Configure virtual_mailbox_maps so that the destination mailbox for address "user#copyself.your.domain.tld" is the actual "Sent" mailbox of the user "user". For example (assumed that you are using regular system users and Maildir format - like in my case) the path to "Sent" mailbox for user "user" will be "/home/user/Maildir/.Sent". So, you can define common part of the path as virtual_mailbox_base, eg.
virtual_mailbox_base=/home
and then in the virtual mailbox map enter the rest of the path like this:
user#copyself.your.domain.tld user/Maildir/.Sent/
(the trailing / is important to indicate the Maildir format).
Again, you can use PCRE type map to do this for all users.
4) To properly save mail to the mailbox, Postfix need to also know the proper UID and GID for the particular user, so you have to use virtual_uid_maps and virtual_gid_maps parameters as well. If you are using virtual users, it's probably enough to define "static" type maps specifying a single UID and GID of the system user that owns all the virtual mailboxes. However, if you are using system users like me, you need the proper actual UID and GID for any user. If you have only a few users, you can use a regular "hash" type map, with entries like these:
user#copyself.your.domain.tld 2001
or you can try to setup a pipeline with "pipemap" map type, that uses some PCRE maps and "unix:passwd.byname" map to obtain the UIDs and GIDs for all users (I haven't done this part, as my Postfix installation is compiled without "pipemap" type support).
So to sum everything up, use something like this:
In /etc/postfix/main.cf file, add the following lines:
sender_bcc_maps=hash:/etc/postfix/sender_bcc
virtual_mailbox_domains=copyself.your.domain.tld
virtual_mailbox_base=/home
virtual_mailbox_maps=hash:/etc/postfix/copyself
virtual_uid_maps=hash:/etc/postfix/copyself_uids
virtual_gid_maps=hash:/etc/postfix/copyself_gids
/etc/postfix/sender_bcc contains a bunch of lines like:
user#your.domain.tld user#copyself.your.domain.tld
/etc/postfix/copyself contains - respectively - lines like:
user#copyself.your.domain.tld user/Maildir/.Sent/
/etc/postfix/copyself_uids and /etc/postfix/copyself_gids contain - respectively - lines like:
user#copyself.your.domain.tld 2001
I have done this on my server and it works great for me.

Related

What makes Outlook/Exchange able to resolve a recipient or not?

I am trying to test whether staff are still employed in the organization.
The best approach I have found so far has to try send them an email.
So, using Outlook, Exchange and Python, I put the email addresses into a new email and try "Resolve" the recipient.
The behavior seems erratic. In most cases, this will produce a result, or "None".
for recipient in msg.Recipients:
try:
exchangeSays = recipient.AddressEntry.GetExchangeUser()
But now in my test case, I have a person john.smith#company.com and whilst the person does exist, is real and present, the entry will not resolve.
I've also noticed that sometimes email addresses resolve to "John Smith" and other recipients will resolve to "john.smith#company.com". I know it's resolved when the name is underlined in the email window.
What's going on here? Some questions:
Is this the best way of checking whether an person is still current?
Am i doing something wrong in my attempt to resolve the recipient?
Firstly, there is no need to create a message and send it - use Application.Session.CreateRecipient / Recipient.Resolve. If Recipient.Resolve returns true, check Recipient.AddressEntry.Type, If it is "EX", the name was resolved to a GAL user. You can however run into problems if you have a contact with the same name in your Contacts folder, and OOM does not allow to resolve against a particular container (e.g. GAL).
Note that Outlook Object Model cannot handle ambiguous names (e.g. "John Smith" will also match "John Smither") - it will simply return an error. If using Redemption is an option (I am its author), it exposes RDOSession.AddressBook.ResolveNameEx, which returns a list of matches.
On the Extended MAPI level (PR_ANR restriction) you can also resolve against a particular container, but OOM does not expose that functionality. In Redemption, you can use RDOSession.AddressBook.GAL.ResolveName/ResolveNameEx. Note however that in this case GAL provider won't resolve an SMTP address of a GAL user (go figure).
Outlook (UI only) also exposes search containers (PR_SEARCH in MAPI, you can see the one exposed by GAL if you click Ctrl + Shift + B to open the address book, then click Tools | Find). You can specify one or more fields to match (e.g. the whole display name or first and last names separately), but OOM, again, does not expose it. In Redemption, you can use RDOSession.Addressbook.GAL.Search:
set Session = CreateObject("Redemption.RDOSession")
Session.MAPIOBJECT = Application.Session.MAPIOBJECT
set AddrList = Session.Addressbook.GAL
set Search = AddrList.Search
Search.FirstName = "John"
Search.LastName = "Smith"
set AddressEntries = Search.GetResults
for each AddressEntry in AddressEntries
MsgBox AddressEntry.Name
next

Live call transfer by using asterisk

i want to transfer a call from first executive to second executive when customer call to first executive by mistake? How first executive can map customer to second executive by pressing a key by using asterisk technology?
Default transfer is *2. For exact code check features.conf
You also have dialplan Transfer application you can map on any other extension.
You have Transfer ami command usable via asterisk managment interface(AMI)
The question is a bit vague, but since you put freepbx on the tags, I suppose you are using freepbx generated dialplan.
If I understand well, when a certain inbound context calls executive1 you want
1) them to be automagically redirected on executive2 before executive1 answers
or
2) executive1 answers, realizes that call is wrong and blind-transfers call to executive2 pressing a single button (= DTMF).
CASE 1 - Automatic redirection
Edit your /etc/asterisk/extension_custom.conf
[your inbound context]
exten => <executive 1 number>,Goto(your inbound context, executive2 number, 1)
You can find the name of your inbound context in the freepbx automatic generated dialplan, or in the freepbx GUI
CASE2 - In call transfer
Refer to this post to define a new feature code for in-call transfer. Unfortunately your feature code will be likely some #digit
Associate the application
Goto(your inbound context, executive2 number, 1)
to the feature code
Hope this will help.

how to set the From field in an email

If I send an email from javascript, the email arrives at the destination address with the "From" field containing Anonymous%<Notes domain>#Company.com. I tried setting the fields "reply-to", "return-path", "From", "Sender", & "Principal" with what I want to appear in the "From" field.
But that often results in a bounce-back message because, I believe, it looks like the "From" address is being spoofed (which is actually is but for a good cause!). How can I modify the "From" field?
Here's the code using mail.box that's throwing the error:
function sendTestEmail(emailAddr){
print("enter sendTestEmail function");
print("emailAddr: "+emailAddr);
var mailboxdb:NotesDatabase = sessionAsSigner.getDatabase("<server>", "mail.box");
var emaildoc:NotesDocument = mailboxdb.createDocument();
emaildoc.replaceItemValue("form", "Memo");
emaildoc.replaceItemValue("sendTo", emailAddr);
emaildoc.replaceItemValue("subject", "testing email");
var body:NotesRichTextItem = emaildoc.createRichTextItem("body");
body.addNewLine();
body.appendText(" testing from javascript. ");
emaildoc.replaceItemValue("SMTPOriginator", "support#abc.com");
emaildoc.replaceItemValue("From","\"support#abc.com\" <support#abc.com>");
emaildoc.replaceItemValue("Principal","\"support#abc.com\" <support#abc.com>");
emaildoc.save(true, false);
print("exiting sendTestEmail function");
}
Copy the mail into server's database mail.box instead of sending it and set fields "Principal" and "From" to your alternative address.
Have a look at this answer too.
Set the SMTPOriginator field to the address it should be from. You might still need to populate the From, Sender and Principal as well.
Just another idea, because to me the mail.box idea should be a last resort approach.
If the mail is always to be sent by the same person (e.g. support), you could prepare a draft mail somewhere, for instance in your current database, and have a signed, scheduled agent (LS, Java) that sends the mails out.
I once used a special Extension Manager DLL to rename certain fields in outgoing mails, but I'm not going to propose that idea here...

How to use filter domains with jenkins email-ext plugin?

Currently my Jenkins instance sends emails to committers (in case of failing builds).
I wish to use the email-ext plugin and write a groovy script that will only send an email in case the commit belongs to a specific domain which I want to define.
You can do this with a Default Pre-send script like:
recipients = msg.getRecipients(javax.mail.Message.RecipientType.TO)
filtered = recipients.findAll { addr -> addr.toString().contains('#gooddomain.com') }
msg.setRecipients(javax.mail.Message.RecipientType.TO, filtered as javax.mail.Address[])
From: https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+Recipes
You could do this with a pre-send script. It gives you complete access to the MimeMessage object, so you could iterate through the list of people in the To and if the domain you don't want exists in the list, you can set cancel = True
normally Jenkins use email from people's configuration (Jenkings -> People -> configure).
If you don't want to send an email to some people just remove email address.

Using filter for return-path

I am getting mail where "From" and "Reply-to" are different than "Return-Path", "Received from" as shown in this example.
How do I set filter for such mail?
Return-Path: <cybersho#bhasha.interpole.net>
Received: from bhasha.interpole.net (bhasha.interpole.net.
Received: from cybersho by bhasha.interpole.net with local (Exim 4.77)
(envelope-from <cybersho#bhasha.interpole.net>)
From: "Gadima.com" <books#gadima.com>
Reply-to: "Gadima.com" <books#gadima.com>
It doesn't seem to be possible in Gmail, unfortunately.
I fell back to my email client, Gnus (because of its amazing flexibility and lightness) to do this. The details are explained in the "6.3.3 Client-Side IMAP Splitting" section of its manual.
It was surprisingly easy. In my ".gnus.el" file, I put (I'm using the nnimap backend for Gmail) something like this:
(setq nnimap-split-methods
'(("mail-list-folder" "Return-Path: mail-list-address")
("INBOX" ""))
You'd need to adapt your "mail-list-folder" (label) and "Return-Path: mail-list-address" parts accordingly. The string containing "Return-Path: ..." is a regexp so can you can use wildcards such as .* and even groups. For example, to filter some lists I'm subscribed to, I have:
(setq nnimap-split-methods
'(("list.\\1" "^Return-Path: <\\(.*\\)-bounces.*#gnu.org>")
("INBOX" ""))
Notice the capture group, \\(.*\\) which is used to form my label, as well as the adaptations required to match the Return-Path as formed by the mailing list program.
If you'd like to try it out I can suggest the following wiki to get started: https://www.emacswiki.org/emacs/GnusGmail.

Resources