{"action":"created","issue":{"url":"https://api.github.com/repos/jens-maus/yam/issues/368","repository_url":"https://api.github.com/repos/jens-maus/yam","labels_url":"https://api.github.com/repos/jens-maus/yam/issues/368/labels{/name}","comments_url":"https://api.github.com/repos/jens-maus/yam/issues/368/comments","events_url":"https://api.github.com/repos/jens-maus/yam/issues/368/events","html_url":"https://github.com/jens-maus/yam/issues/368","id":148366835,"number":368,"title":"YAM 2.8 SMTP helo contains not the FQDN","user":{"login":"jens-maus","id":5887769,"avatar_url":"https://avatars.githubusercontent.com/u/5887769?v=3","gravatar_id":"","url":"https://api.github.com/users/jens-maus","html_url":"https://github.com/jens-maus","followers_url":"https://api.github.com/users/jens-maus/followers","following_url":"https://api.github.com/users/jens-maus/following{/other_user}","gists_url":"https://api.github.com/users/jens-maus/gists{/gist_id}","starred_url":"https://api.github.com/users/jens-maus/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jens-maus/subscriptions","organizations_url":"https://api.github.com/users/jens-maus/orgs","repos_url":"https://api.github.com/users/jens-maus/repos","events_url":"https://api.github.com/users/jens-maus/events{/privacy}","received_events_url":"https://api.github.com/users/jens-maus/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/jens-maus/yam/labels/%23minor","name":"#minor","color":"ededed"},{"url":"https://api.github.com/repos/jens-maus/yam/labels/@undecided","name":"@undecided","color":"ededed"},{"url":"https://api.github.com/repos/jens-maus/yam/labels/bug","name":"bug","color":"ee0701"},{"url":"https://api.github.com/repos/jens-maus/yam/labels/fixed","name":"fixed","color":"ededed"},{"url":"https://api.github.com/repos/jens-maus/yam/labels/TCP/IP","name":"TCP/IP","color":"ededed"},{"url":"https://api.github.com/repos/jens-maus/yam/labels/v2.8","name":"v2.8","color":"ededed"}],"state":"open","locked":false,"assignee":null,"milestone":{"url":"https://api.github.com/repos/jens-maus/yam/milestones/5","html_url":"https://github.com/jens-maus/yam/milestones/YAM%202.9","labels_url":"https://api.github.com/repos/jens-maus/yam/milestones/5/labels","id":1705559,"number":5,"title":"YAM 2.9","description":"[[TicketQuery(milestone=YAM 2.9, order=resolution, desc=1, format=table, col=id|type|status|resolution|priority|summary)]]","creator":{"login":"jens-maus","id":5887769,"avatar_url":"https://avatars.githubusercontent.com/u/5887769?v=3","gravatar_id":"","url":"https://api.github.com/users/jens-maus","html_url":"https://github.com/jens-maus","followers_url":"https://api.github.com/users/jens-maus/followers","following_url":"https://api.github.com/users/jens-maus/following{/other_user}","gists_url":"https://api.github.com/users/jens-maus/gists{/gist_id}","starred_url":"https://api.github.com/users/jens-maus/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jens-maus/subscriptions","organizations_url":"https://api.github.com/users/jens-maus/orgs","repos_url":"https://api.github.com/users/jens-maus/repos","events_url":"https://api.github.com/users/jens-maus/events{/privacy}","received_events_url":"https://api.github.com/users/jens-maus/received_events","type":"User","site_admin":false},"open_issues":2,"closed_issues":38,"state":"closed","created_at":"2016-04-14T09:49:43Z","updated_at":"2016-04-14T13:48:14Z","due_on":"2013-12-19T23:00:00Z","closed_at":"2016-04-14T09:49:43Z"},"comments":15,"created_at":"2016-04-14T13:47:56Z","updated_at":"2016-04-14T13:48:16Z","closed_at":null,"body":"**:bust_in_silhouette: Originally by _yam.asc@schwarzes.net_ on 2013-01-11 15:49:26 +0100**\n<hr>\nWhen sending emails with YAM 2.8 the SMTP HELO contains only the hostname\nof the sender but not the FQDN, which is not correct and can cause problems with\nstrict helo filtering.\n\nWith YAM2.7 the problem does not occur.\n\n"},"comment":{"url":"https://api.github.com/repos/jens-maus/yam/issues/comments/209951237","html_url":"https://github.com/jens-maus/yam/issues/368#issuecomment-209951237","issue_url":"https://api.github.com/repos/jens-maus/yam/issues/368","id":209951237,"user":{"login":"jens-maus","id":5887769,"avatar_url":"https://avatars.githubusercontent.com/u/5887769?v=3","gravatar_id":"","url":"https://api.github.com/users/jens-maus","html_url":"https://github.com/jens-maus","followers_url":"https://api.github.com/users/jens-maus/followers","following_url":"https://api.github.com/users/jens-maus/following{/other_user}","gists_url":"https://api.github.com/users/jens-maus/gists{/gist_id}","starred_url":"https://api.github.com/users/jens-maus/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jens-maus/subscriptions","organizations_url":"https://api.github.com/users/jens-maus/orgs","repos_url":"https://api.github.com/users/jens-maus/repos","events_url":"https://api.github.com/users/jens-maus/events{/privacy}","received_events_url":"https://api.github.com/users/jens-maus/received_events","type":"User","site_admin":false},"created_at":"2016-04-14T13:48:16Z","updated_at":"2016-04-14T13:48:16Z","body":"**:bust_in_silhouette: Originally by _yam.asc@schwarzes.net_ on 2013-01-13 16:59:20 +0100**\n<hr>\nReplying to damato:\n> Replying to DrB:\n\n> Interestingly, I am running a similar setup (sendmail+milters) since over ten years now and Inhave also played \n> with numeros different milters and methods to keep SPAM traffic low. Out of my experience the following methods \n> are the only sensible ones and are efficiently fighting SPAM:\n> \n> 1. spamassassin+spamass: the most efficient way to prevent tons of SPAM to be accepted. However, spamassassin \n> have to be tunes itself to carry a global autowhitelist and bayes filter throught all user accounts. In adding \n> pyzor, razor and ddc should be enabled with spamassasin.\n\nNearly the same setup here spamass-milter with addauth patch, spamassassin + razor.\n\n> 2. DNS blacklisting: the second most efficient way to block SPAM as these blacklists are well maintained.\n\nI've dropped this, because this is also scored by spamassasin (several dnsbl).\n\n> 3. DKIM/SPF signing: to reduce the probability that mails from your domain will be flagged as SPAM themselves \n> it is a good idea to implement DKIM and SPF mechanisms in you domain. Many SPAM engines are considering DKIM/SPF \n> setups today and will consider valid DKIM/SPF mails to be flagged as Ham.\n\nYes, I'm using SPF to protect my domain (old TXT RR). For incoming mails I've used spf-milter,\nbut this ist also covered by  spamassasin, so there is no need to use the extra milter.\n\n> 4. while greylisting was very efficient years ago (> 5 years) most of the SPAMers have already adapted they \n> engines by today.  Was also using greylisting in the beginning but nowaday itis not really efficient anymore \n> and just delays your transfers. There are numeros webpages talking about this fact already. In my setup I \n> replaced greylisting with DNS blacklisting and ended up with higher SPAM recognition rates and less false-positives.\n\nThere is still one advantage, until the greylisting time is expired, the spammer run in several spam traps,\nwhich increas the dnsbl scoring.\n\n\n> 5. All users sending mail through such a sendmail server using a MUA have to use SMTP-AUTH with SSL. I have therefore \n> disabled plaintext auth and direct sending of emails without authentication. In addition, sendmail have to be \n> configured to skip all SPAM related milters iin case. Not only allows such SMTP AUTH to disable less efficient \n> SPAM checks like the EHLO checks, but other mail servers are also sometimes recognizing the authentication headers \n> added by such a server and potentially rating such mails as Ham as well.\n\nUnfortunately not all of the users are using SMTP AUTH, there is also some \"smtp after pop\" hack installed,\nor they are local (like me). There are also some scripts which want to send email in certain situations. Sure, \nit's possible to change this, but this needs time.\n\n\n> > I think the easiest way for a fix, is to add again a configuration field for the domain (like \n> > yam2.7). It's surely a little bit problematic to detect the fqdn automatically. Maybe you can\n> > try to resolve the own IP address, or take the domain part of the smtp server. Both are only\n> > hacks, I understand that you don't want to implement this.\n> \n> Well, I removed the configuration option because in most other clients such an optin is not \n> really available and the potentials are too high that an incorrect domain name is used by a user. \n> Therefore I replaced the manual option with an automatic methods which (as it seems) is still not \n> optimal. To improve the situation I have the the following in mind:\n> \n> 1. change the FQDN function to use a full domain name which adds the mail server address domain \n> if only a hostname without a domain padt was found.\n> 2. add a hidden option to allow users to specify their FQDN so that the function will use that one instead.\n\nBoth solutions would be fine for me.\n"}}