![]() It’s important to quote the curled braces to avoid the file to be interpreted as perl. To change this behaviour I created the same path in /etc/e-smith/templates-custom and placed my own files there.Ĭreated the custom template folder mkdir -p /etc/e-smith/templates-custom/var/lib/nethserver/sieve-scripts/before.sieveĬopied the nethserver 10junkmail file here (so this will be used instead of the one in /templates/…) cp /etc/e-smith/templates/var/lib/nethserver/sieve-scripts/before.sieve/10junkmail /etc/e-smith/templates-custom/var/lib/nethserver/sieve-scripts/before.sieveĮdited the 10junkmail file to require “copy”, needed for forwarding emails require Ĭreated my own sieve file echo "#20myfilter" >/etc/e-smith/templates-custom/var/lib/nethserver/sieve-scripts/before.sieve/20myfilterĮdited my own filter file 20myfilter to include the first forwarding rule. In default nethserver there is only one file 10junkmail which defines the sieve require and the rules to move spam to the Junk folder (GUI setting!) This file is created from the template (fragments) files in /etc/e-smith/templates/var/lib/nethserver/sieve-scripts/before.sieve/ The file, where the server-wide filter settings should be defined: /var/lib/nethserver/sieve-scripts/before.sieve Nethserver uses the e-smith or SEM-Server template system so I looked in their documentation. If anything, your question is an indication that perhaps you should be looking at a professional service to send out these messages on your behalf, for a fee.Think I’ve got it, I try to tell what I did until now It is unlikely that this header alone (the presence of this header, or the absence of reverse DNS information evident from the contents of it) would be sufficient for somebody to classify your message as spam, but there is really no way to control what the recipient does with this information. Recipients can do whatever they want with these headers. In other words, the contents of your message headers or envelope headers do not affect this outcome at all. In the SMTP Relayer field, enter the host name of your ISP's email server, along with your credentials on that server in case it demands authentication. To the right, the SMTP settings are now shown. If the SMTP server receives a connection from 123.45.67.89 then it will perform reverse DNS for that address, and put the results in the Received: header it adds. In the tree to the left, go to Settings -> Protocols -> SMTP. The reverse DNS lookup is usually performed based on the TCP headers, not on the text of the message. ("Reverse DNS" means that when somebody queries DNS for "what's the DNS name of 207.162.215.30" the answer would be "" or perhaps another host name, but not "unknown".) Many ISPs refuse (if you are on a "consumer" broadband plan), or will require a different hosting contract with you in order to offer this service. If you are concerned about the lack of reverse DNS, and if 207.162.215.30 is yours, then perhaps you can convince your ISP to provide reverse DNS for it. Typically each hop from one SMTP server to another adds one Received: header at the top of the message (except qmail, which adds two this is visible in your example). What's the problem then? I wonder what is strange format in brackets in the header Received : from unknow: Received: from unknown simply means that one SMTP server receiveid it from another which did not provide reverse DNS. Received: from unknown (HELO ) with SMTP 14:55:59 -0000 Now there are changes in DNS and I have headers: Message-Id: The ip from which email is sent is not blacklisted. Reply-To: List1: Confirm SubscriptionĬontent-Transfer-Encoding: quoted-printable Received: from unknown (HELO ) with SMTP 09:58:48 -0000 Spf=pass (: domain of designates 207.162.215.30 as permitted sender) Here are headers of such email: Delivered-To: by 10.76.94.204 with SMTP id de12csp111150oab Zend_Mail::setDefaultTransport($transport) Įmail config from application.ini: email.name = $transport = new Zend_Mail_Transport_Smtp($emailConfig, $emailConfig) $mailer->addTo($params) Ĭode to configure transport: $emailConfig = $this->getOption('email') Here's code for setting headers: $mailer->setFrom($params, $params) Received: from unknown (HELO ) does it mean list header "Recieved: from unknown"? Can it make email go to spam? How to avoid this strange header and make email avoid spam folder? Is there any problem with coode or maybe I have some problems with DNS settings of this domain? But for some reason email that I send has strange headers and email goes to spam folder (I see them in gmail that receive letter): Message-Id: ![]() This is confimation email of subscribing. I try to send email from our server using php and Zend_Mail.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |