Re: Going through Google spam filters
On 26/07/15 22:43, Wietse Venema wrote: > Daniele Nicolodi: > Maybe this helps: > > Go to your Mail settings and Accounts tab and add the address > you are forwarding from to 'Send mail as'. This is a new feature > from user requests, where Gmail will detect that you forwarded > from that account and help prevent displaying a phishing warning. > > https://support.google.com/a/answer/175365?hl=en Hello Wietse, thanks for your reply. However, this is not the problem. Maybe I was not clear in my explanation: I'm nor trying to forward >>> >>> You did not try it. Good for you. >> >> Hello Wietse, >> >> I may have dismissed what you proposed a bit too quickly but I don't >> really understand how setting this option for a test account will affect >> my ability to send email to other Gmail accounts. > > Based on this: > > "Currently I'm able to send emails to my address @gmail.com > from the email address I'm currently using without having them > classified as spam, but not from any email address having a > different local part." > > The problem is that different accounts in your domain receive > different treatments, when they send mail to one Gmail account. > > I didn't read that as a problem sending mail to different Gmail > accounts. Sorry, I should have been more clear on the fact that this is the easy way I have to diagnose the problem. I know that most of the emails that I send from my domain to Gmail accounts are classified as spam. Only the recipients that (in a way or another) have my address whitelisted receive them in their inbox. > In any case, I agree that you need to clean up your DNS, so that > the Received: header shows zed.grinta.net as the sending host, not > grinta.net. > > Definitely: > grinta.net. IN MX pref zed.grinta.net. > zed.grinta.net. IN A 109.74.203.128 > 128.203.74.109.in-addr.arpa. IN PTR zed.grinta.net. > > Maybe: > grinta.net. IN A 109.74.203.128 > > Not: > 128.203.74.109.in-addr.arpa. IN PTR grinta.net. I fixed that, the reverse pointer took a while to propagate, it should be fine now. Thanks for your help. Cheers, Daniele
RE: Going through Google spam filters
If you have ever replied to the working sender @ grinta.net, receiving messages from that sender in Inbox @ Gmail is not relevant. The sender @ grinta.net is whitelisted in the current Gmail account. Usually, the descriptive banner displayed for messages in Web Spam folder helps to identify the cause: - content similar to spam => change the content when you test. - If you use any url shortener (public URL that can be exploited) in your body => remove them or remove any URL during tests. - complaints from multiple recipients => historical reputation of the sending source is bad. - phishing, suspicious domain etc. - Check headers for spf=pass, dkim=pass. "v=spf1 mx ~all" should be more appropriate (than "v=spf1 a ~all") since you have only one email server zed.grinta.net acting as MX and sending server, not any A host in the DNS. Marius. -Original Message- From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] On Behalf Of Daniele Nicolodi Sent: Monday, July 27, 2015 10:52 AM To: postfix-users@postfix.org Subject: Re: Going through Google spam filters On 26/07/15 22:43, Wietse Venema wrote: > Daniele Nicolodi: > Maybe this helps: > > Go to your Mail settings and Accounts tab and add the address > you are forwarding from to 'Send mail as'. This is a new feature > from user requests, where Gmail will detect that you forwarded > from that account and help prevent displaying a phishing warning. > > https://support.google.com/a/answer/175365?hl=en Hello Wietse, thanks for your reply. However, this is not the problem. Maybe I was not clear in my explanation: I'm nor trying to forward >>> >>> You did not try it. Good for you. >> >> Hello Wietse, >> >> I may have dismissed what you proposed a bit too quickly but I don't >> really understand how setting this option for a test account will affect >> my ability to send email to other Gmail accounts. > > Based on this: > > "Currently I'm able to send emails to my address @gmail.com > from the email address I'm currently using without having them > classified as spam, but not from any email address having a > different local part." > > The problem is that different accounts in your domain receive > different treatments, when they send mail to one Gmail account. > > I didn't read that as a problem sending mail to different Gmail > accounts. Sorry, I should have been more clear on the fact that this is the easy way I have to diagnose the problem. I know that most of the emails that I send from my domain to Gmail accounts are classified as spam. Only the recipients that (in a way or another) have my address whitelisted receive them in their inbox. > In any case, I agree that you need to clean up your DNS, so that > the Received: header shows zed.grinta.net as the sending host, not > grinta.net. > > Definitely: > grinta.net. IN MX pref zed.grinta.net. > zed.grinta.net. IN A 109.74.203.128 > 128.203.74.109.in-addr.arpa. IN PTR zed.grinta.net. > > Maybe: > grinta.net. IN A 109.74.203.128 > > Not: > 128.203.74.109.in-addr.arpa. IN PTR grinta.net. I fixed that, the reverse pointer took a while to propagate, it should be fine now. Thanks for your help. Cheers, Daniele
Re: PATCH: Wildcard key and inline-maps
> /usr/sbin/postconf: warning: main.cf: syntax error after '}' in "{
> send...@zwackl.de=OK }, static: { REJECT BAD SENDER } }"
There should be no SPACE after ":". Also, I haven't tested this
with postconf, assuming that it would be fine as long as every ":{
has a matching "}".
Wietse
Re: Going through Google spam filters
On 27 Jul 2015, at 12:15, Marius Gologan wrote: > If you have ever replied to the working sender @ grinta.net, receiving > messages from that sender in Inbox @ Gmail is not relevant. The sender @ > grinta.net is whitelisted in the current Gmail account. > > Usually, the descriptive banner displayed for messages in Web Spam folder > helps to identify the cause: > - content similar to spam => change the content when you test. > - If you use any url shortener (public URL that can be exploited) in your > body => remove them or remove any URL during tests. > - complaints from multiple recipients => historical reputation of the > sending source is bad. > - phishing, suspicious domain etc. > - Check headers for spf=pass, dkim=pass. > "v=spf1 mx ~all" should be more appropriate (than "v=spf1 a ~all") since you > have only one email server zed.grinta.net acting as MX and sending server, > not any A host in the DNS. == $ host grinta.net grinta.net has address 109.74.203.128 grinta.net mail is handled by 10 zed.grinta.net. == $ host zed.grinta.net zed.grinta.net has address 109.74.203.128 == There's your A record. I would still recommend using the 'mx' statement though, just in case you ever decide to move your website elsewhere. You can also try a stricter SPF record, "v=spf1 mx -all", and see if that improves things any. Mvg, Joni
enable username authentication
Hi all, I have created a dovecot and postfix email server My dovecot/IMAP users authenticate by it by there username and passwords that are either created on the local server or my email server queries the LDAP server for authentication Now I want to have SMTP authentication for my users that use postfix Basically I want my user on there email clients to tick the box on the outgoing smtp server that says, "use the same authentication method that I use for my IMAP/dovecot server How do I do this as i think atm my smtp postfix server any one can send out via it so want to lock it down Many thanks in advanced Rob -- Regards, Robert K Wild.
Re: enable username authentication
do a reverse imap auth. t On 2015-07-27 13:06, robert k Wild wrote: Hi all, I have created a dovecot and postfix email server My dovecot/IMAP users authenticate by it by there username and passwords that are either created on the local server or my email server queries the LDAP server for authentication Now I want to have SMTP authentication for my users that use postfix Basically I want my user on there email clients to tick the box on the outgoing smtp server that says, "use the same authentication method that I use for my IMAP/dovecot server How do I do this as i think atm my smtp postfix server any one can send out via it so want to lock it down Many thanks in advanced Rob -- Regards, Robert K Wild.
Re: enable username authentication
On 07/27/2015 11:06 PM, robert k Wild wrote: > I have created a dovecot and postfix email server > > Now I want to have SMTP authentication for my users that use postfix Use dovecot SASL AUTH: http://www.postfix.org/SASL_README.html#server_dovecot Peter
Re: enable username authentication
robert k Wild skrev den 2015-07-27 13:06: Now I want to have SMTP authentication for my users that use postfix http://wiki2.dovecot.org/HowTo/PostfixAndDovecotSASL
Re: SPF and forwarding
Hi, On Sun, Jul 26, 2015 at 7:50 AM, Andrew Beverley wrote: > On Sat, 2015-07-25 at 21:04 -0400, Alex wrote: >> I have a postfix-2.10.5 server on fedora, and have several users that >> forward their mail through to gmail. This is apparently enough to >> break SPF and make gmail think I'm the originator of the email, >> instead of the actual sender. Consequently, gmail considers it spam >> and moves it to a spam folder. >> >> Is there anything I can do, including somehow rewriting the email, to >> get gmail (and others, for that matter) to accept these forwarded >> emails without considering them spam? > > I've just had to deal with the same problem. Google has a variety of > workarounds, > as detailed here: > > https://support.google.com/a/answer/175365?hl=en > > I didn't find most of them particularly helpful. The last one, however, seems > to > have done the trick (adding the forwarded email account as a secondary > account in > Gmail). This requires that you have access to the account from which the email is being forwarded, correct? In my case, it is a single remote sender that is being forwarded on to gmail. Thanks, Alex
Re: SPF and forwarding
On Mon, 2015-07-27 at 09:16 -0400, Alex wrote: > Hi, > > On Sun, Jul 26, 2015 at 7:50 AM, Andrew Beverley wrote: > > On Sat, 2015-07-25 at 21:04 -0400, Alex wrote: > > > I have a postfix-2.10.5 server on fedora, and have several users that > > > forward their mail through to gmail. This is apparently enough to > > > break SPF and make gmail think I'm the originator of the email, > > > instead of the actual sender. Consequently, gmail considers it spam > > > and moves it to a spam folder. > > > > > > Is there anything I can do, including somehow rewriting the email, to > > > get gmail (and others, for that matter) to accept these forwarded > > > emails without considering them spam? > > > > I've just had to deal with the same problem. Google has a variety of > > workarounds, > > as detailed here: > > > > https://support.google.com/a/answer/175365?hl=en > > > > I didn't find most of them particularly helpful. The last one, however, > > seems > > to have done the trick (adding the forwarded email account as a secondary > > account in Gmail). > > This requires that you have access to the account from which the email > is being forwarded, correct? In my case, it is a single remote sender > that is being forwarded on to gmail. No, you need access to the account *to* which the email is forwarded. So assuming that the scenario is someone who has their own personal domain and is forwarding it to a gmail account that they own, then it should be possible. Of course, it would require each of your users to make this change, but they have the incentive to do so if it stops all their email ending up in their spam folder. Andy
