On Sat, 17 Jan 2009, Morten Wegelbye Nissen wrote: > Hearsayers are only useless inside a court, I'll try to get listet in > DNSWL (Actually applied for it 6-8 hours ago) - DKIM seams to be more > timeconsuming, need to read a bit about this stuff.
It's not that time-consuming and is rather trivial to configure with amavisd-new. >> Perhaps both servers are foolishly penalizing your host from being from .dk? >> > This part I do not get? Is it bad to be from .dk? Not in *my* opinion, but perhaps in someone else's. Get it? >> Are you able to disclose the sending domain? None of the domains I guessed >> have SPF records that point to mail.1.gls.dk: >> >> % dig +short TXT gls.dk mwn.dk surftown.dk sonofon.dk >> "v=spf1 mx a:mail.cohaesio.net ~all" >> > Spf is allright, the headers in the inbox on gmail.com account tells > Received-SPF: pass (google.com: domain of a...@gls-denmark.com > designates 213.83.154.181 as permitted sender) > In frustration I have added +all to the spf record. Unlikely to help. >>> I know it is not the content of the email that is the problem, >>> because I have tried sending the exact same messages via other >>> servers with luck. If I compair the headers inside GMAIL >> >> Did the rest of this sentence get cut off? Are there any spam-related >> headers on the GMail side that might give you some clues? >> > Hmm, yes parts of the sentence is missing. I was about to write the only > difference, in the header, is the host specifik once. > The headers does not contain spam specifik headers. Try contacting GMail support in your capacity as a client (you do have a gmail.com email account) and ask why email X was placed in your spam folder. -- Sahil Tandon <sa...@tandon.net>
