Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Qmail: users

Re: [Bulk] Re: DKIM for AOL

 

 

Qmail users RSS feed   Index | Next | Previous | View Threaded


ma1l1ists at yahoo

Nov 24, 2011, 3:25 AM

Post #1 of 18 (2046 views)
Permalink
Re: [Bulk] Re: DKIM for AOL

On Wed, 23 Nov 2011 16:18:01 -0500
Vahid Moghaddasi wrote:

> I replaced the line where hostname -f is call to this:
> [ -z "$sender" ] && sender=@`hostname`.example.com
> Will this work? The reason I am asking is that I don't see anything in the
> header when I send mail out.
> I have my rsa keys in /etc/domainkeys/example.com/default and rsa.public
> files.

I had this problem too for BSD, the script is created for bash not
bourne shell and Linux's hostname.

I think I had to make some other small changes that I was going to
forward onto kyle after testing, not sure if I did in the dust of all
the other testing and fixing. I'll fetch them out when that system is
next turned on, if you haven't sorted it already.

Yeah you should see headers. One had a misspelling actually
X-DKIM-Originating. You should be able to grep for X-DKIM.

Maybe not the fastest but it is crypto and works well for Domainkeys and
DKIM ;-) and the perl module also avoided a bug that other DKIMs had
with yahoo servers.


vahid.moghaddasi at gmail

Nov 24, 2011, 8:15 AM

Post #2 of 18 (1982 views)
Permalink
Re: [Bulk] Re: DKIM for AOL [In reply to]

On Thu, Nov 24, 2011 at 6:25 AM, Kevin Chadwick <ma1l1ists [at] yahoo>wrote:

> On Wed, 23 Nov 2011 16:18:01 -0500
> Vahid Moghaddasi wrote:
>
> > I replaced the line where hostname -f is call to this:
> > [ -z "$sender" ] && sender=@`hostname`.example.com
> > Will this work? The reason I am asking is that I don't see anything in
> the
> > header when I send mail out.
> > I have my rsa keys in /etc/domainkeys/example.com/default and rsa.public
> > files.
>
> I had this problem too for BSD, the script is created for bash not
> bourne shell and Linux's hostname.
>
> I think I had to make some other small changes that I was going to
> forward onto kyle after testing, not sure if I did in the dust of all
> the other testing and fixing. I'll fetch them out when that system is
> next turned on, if you haven't sorted it already.
>
> Yeah you should see headers. One had a misspelling actually
> X-DKIM-Originating. You should be able to grep for X-DKIM.
>
> Maybe not the fastest but it is crypto and works well for Domainkeys and
> DKIM ;-) and the perl module also avoided a bug that other DKIMs had
> with yahoo servers.
>

Hi Kevin,
I would appreciate if you post the corrected script here, I am not sure if
the change I made
fixed that hostname problem or there are other places I need to change as
well.
I don't know which misspelling you are referring to but I haven't noticed
or maybe missed it.

At this time, we are only concerned about AOL as they are they only one
requiring DKIM.
I built a few qmail servers and will apply the DKIM change there and will
forward all the e-mails which
the sites require DKIM to those servers.
Thank you very much.


--
This e-mail address is not monitored so please do not send me anything
important here. Thanks.


amb-sendok-1324745978.agjpaopncikodnljnnbk at bradfo

Nov 24, 2011, 8:59 AM

Post #3 of 18 (1979 views)
Permalink
Re: [Bulk] Re: DKIM for AOL [In reply to]

Thus said Vahid Moghaddasi on Thu, 24 Nov 2011 11:15:50 EST:

> At this time, we are only concerned about AOL as they are they only
> one requiring DKIM.

Are you sure you aren't going through all this effort for naught? I am
able to send email to AOL and I don't use DKIM.

Andy


scott.brynen at visioncritical

Nov 24, 2011, 9:06 AM

Post #4 of 18 (1978 views)
Permalink
RE: [Bulk] Re: DKIM for AOL [In reply to]

I have some domains that send with DKIM, some without, and have no issues at all sending to AOL






-----Original Message-----
From: Andy Bradford [mailto:amb-sendok-1324745978.agjpaopncikodnljnnbk [at] bradfords]
Sent: Thursday, November 24, 2011 9:00 AM
To: Vahid Moghaddasi
Cc: qmail [at] list
Subject: Re: [Bulk] Re: DKIM for AOL

Thus said Vahid Moghaddasi on Thu, 24 Nov 2011 11:15:50 EST:

> At this time, we are only concerned about AOL as they are they only
> one requiring DKIM.

Are you sure you aren't going through all this effort for naught? I am able to send email to AOL and I don't use DKIM.

Andy


vahid.moghaddasi at gmail

Nov 24, 2011, 9:47 AM

Post #5 of 18 (1984 views)
Permalink
Re: [Bulk] Re: DKIM for AOL [In reply to]

On Thu, Nov 24, 2011 at 11:59 AM, Andy Bradford <
amb-sendok-1324745977.imnhnoonijgicppgjcii [at] bradfords> wrote:

> Thus said Vahid Moghaddasi on Thu, 24 Nov 2011 11:15:50 EST:
>
> > At this time, we are only concerned about AOL as they are they only
> > one requiring DKIM.
>
> Are you sure you aren't going through all this effort for naught? I am
> able to send email to AOL and I don't use DKIM.
>
> Andy
>
>

AOL only accepts maybe the first 10-20 e-mails then it stops. The logs have
postmaster.aol.com URL in it
and instructs us to use DKIM. We (not me personally) have also spoke to AOL
representatives and they told
the same thing.


vahid.moghaddasi at gmail

Nov 24, 2011, 10:04 AM

Post #6 of 18 (1987 views)
Permalink
Re: [Bulk] Re: DKIM for AOL [In reply to]

On Thu, Nov 24, 2011 at 11:35 AM, Kevin Chadwick <ma1l1ists [at] yahoo>wrote:

> On Thu, 24 Nov 2011 11:15:50 -0500
> Vahid Moghaddasi wrote:
>
> > I would appreciate if you post the corrected script here, I am not sure
> if
> > the change I made
>
> I'll dig it out and diff it. Does it not throw any errors when run
> manually? Trying bash might work too. I wanted to keep the default
> shell without installing any extra.
>
> If you send me yours to diff it will save me getting/finding the
> original, or send me the link.
>
> Kc
>


Sure, I have also added some debugging echo but did not help me much. The
script does not
seem to give any error but I might be running it wrongly.

#!/bin/bash
# version 6
PATH=/bin:/usr/bin:/usr/local/bin:/var/qmail/bin
shopt -q -s extglob
host="$1"
sender="$2"
# First, figure out who the sending domain is:
[[ -z "$sender" && "$DEFAULTDOMAIN" ]] && sender="@$DEFAULTDOMAIN"
[ -z "$sender" ] && sender=@`hostname`.example.com
DOMAIN="${sender##*@}"
# Sanity-check the sender
if [[ $DOMAIN == !(+([a-zA-Z0-9\!\#$%*/?|^{}\`~&\'+=_.-])) ]] ; then
echo "DSender address contains illegal characters."
exit 0
fi
# debug
echo $DOMAIN > /tmp/DOMAIN.out
# Now, fill in the basic variables (if they don't exist already)
[ "$DKREMOTE" ] || DKREMOTE="/var/qmail/bin/qmail-remote.orig"
[ "$DKSIGN" ] || DKSIGN="/etc/domainkeys/example.com/default"
# Now try and find the right subdomain, per RFC 4871
# (you can eliminate this loop if you don't want parent domains signing
child
# domain's email)
# i commented this out but saw no change.
###if [ "$DOMAIN" ] ; then
### while [ ! -r "${DKSIGN//\%/$DOMAIN}" ] ; do
### # try parent domains, per RFC 4871, section 3.8
### DOMAIN=${DOMAIN#*.}
### DPARTS=( ${DOMAIN//./ } )
### [ ${#DPARTS[*]} -eq 1 ] && DOMAIN="${sender##*@}" && break
### done
###fi
DKSIGN="${DKSIGN//\%/$DOMAIN}" # i notices the % sign does not expand to my
domain name.
#debug
echo $DKSIGN > /tmp/DKSIGN.out
# Now that we have the correct DKSIGN value (i.e. the filename of the key to
# use to sign email), check to see if this file exists
if [ -r "$DKSIGN" ] ; then
# The key does exist, so now use it to generate signatures!
tmp=`mktemp -t dk.sign.XXXXXXXXXXXXXXXXXXX`
tmp2=`mktemp -t dk2.sign.XXXXXXXXXXXXXXXXXXX`
cat - >"$tmp"
# compute the DomainKey signature
error=`(dktest -s "$DKSIGN" -c nofws -h <"$tmp" | \
sed 's/; d=.*;/; d='"$DOMAIN"';/' > "$tmp2") 2>&1`
if [ "$error" ] ; then
# Communicate the problem to qmail (that's why the 'Z')
echo "ZDomainKey error: $error"
rm "$tmp" "$tmp2"
exit -1
fi
# compute the DKIM signature
error=`(dkimsign.pl --type=dkim --selector=default
--domain="$DOMAIN" \
--key="$DKSIGN" --method=relaxed <"$tmp" | \
tr -d '\r' >> "$tmp2") 2>&1`
if [ "$error" ] ; then
# Communicate the problem to qmail (that's why the 'Z')
echo "ZDKIM error: $error"
rm "$tmp" "$tmp2"
exit -2
fi
# feed the signatures and the original message to the real
qmail-remote
cat "$tmp2" "$tmp" | "$DKREMOTE" "$@"
retval=$?
rm "$tmp" "$tmp2"
#debug
echo "$DKREMOTE $@" > /tmp/DKREMOTE.err # this file never gets created
echo $error > /tmp/error.err
exit $retval
else
# No signature added
exec "$DKREMOTE" "$@"
#debug
echo "$DKREMOTE $@" > /tmp/DKREMOTE.out
fi


amb-sendok-1324750544.flcjdejbhocphnmgbidh at bradfo

Nov 24, 2011, 10:15 AM

Post #7 of 18 (1980 views)
Permalink
Re: [Bulk] Re: DKIM for AOL [In reply to]

Thus said Vahid Moghaddasi on Thu, 24 Nov 2011 12:47:48 EST:

> AOL only accepts maybe the first 10-20 e-mails then it stops. The logs
> have postmaster.aol.com URL in it and instructs us to use DKIM. We
> (not me personally) have also spoke to AOL representatives and they
> told the same thing.

This smells of speculation to me. I doubt even the AOL representative
knew the *real* reason why they were rejected. It sounds to me like the
AOL representative simply parroted what their website said and didn't
actually tell you *why* they were rejected, but only a speculative
suggestion that might improve your chances of getting email through. I
would seek to find some concrete answers from AOL before significantly
altering your MTA's behavior.

Andy


amb-sendok-1324750763.kjmkffffkgknoejcfoae at bradfo

Nov 24, 2011, 10:19 AM

Post #8 of 18 (1978 views)
Permalink
Re: [Bulk] Re: DKIM for AOL [In reply to]

Thus said Vahid Moghaddasi on Thu, 24 Nov 2011 12:47:48 EST:

> AOL only accepts maybe the first 10-20 e-mails then it stops.

Maybe they just don't like the volume of email. DKIM won't help with
this. You should look at serialmail. This too is a speculative
suggestion. :-) You haven't given a very good description of what you
are seeing in the logs. Are they outright 5xx rejections, or merely
temporary 4xx deferrals? If the latter, do the emails actually get
successfully delivered over time?

Andy


vahid.moghaddasi at gmail

Nov 24, 2011, 10:25 AM

Post #9 of 18 (1998 views)
Permalink
Re: [Bulk] Re: DKIM for AOL [In reply to]

On Thu, Nov 24, 2011 at 1:15 PM, Andy Bradford <
amb-sendok-1324750544.flcjdejbhocphnmgbidh [at] bradfords> wrote:

>
> This smells of speculation to me. I doubt even the AOL representative
> knew the *real* reason why they were rejected. It sounds to me like the
> AOL representative simply parroted what their website said and didn't
> actually tell you *why* they were rejected, but only a speculative
> suggestion that might improve your chances of getting email through. I
> would seek to find some concrete answers from AOL before significantly
> altering your MTA's behavior.
>
> Andy
>
>

They (AOL) have been bugging us for a while now but they started putting
pressure now.
We get this error in the log. The URL is not valid but the error DYN:T1
implies that we are
sending too many e-mails to AOL which we do. We send about maybe 8000/month
to our
costumers who have AOL e-mail address.

2011-11-23 13:24:08.953713500 delivery 1: deferral:
Connected_to_64.12.90.33_but_greeting_failed./Remote_host_said:_421_4.7.1_:_(DYN:T1)_
http://postmaster.info.aol.com/errors/421dynt1.html/


amb-sendok-1324752518.lcddbdjmacehgebkdlib at bradfo

Nov 24, 2011, 10:48 AM

Post #10 of 18 (2077 views)
Permalink
Re: [Bulk] Re: DKIM for AOL [In reply to]

Thus said Vahid Moghaddasi on Thu, 24 Nov 2011 13:25:10 EST:

> We get this error in the log. The URL is not valid but the error
> DYN:T1 implies that we are sending too many e-mails to AOL which we
> do. We send about maybe 8000/month to our costumers who have AOL
> e-mail address.

Yes, the URL is actually valid, and it says:

421 DYN:T1

* The IP address you are sending from has been temporarily rate
limited due to lack of whitelisting, unexpected changes in volume,
or poor IP reputation.

Have you asked to be whitelisted or have your volume threshold
increased? If your email to their users is expected and wanted by them,
and you can show proof of this, then maybe you could use that as
leverage to AOL. Has AOL claimed that by implementing DKIM that this 421
DYN:T1 problem will be resolved?

> 2011-11-23 13:24:08.953713500 delivery 1: deferral:
> Connected_to_64.12.90.33_but_greeting_failed./Remote_host_said:_421_4.7.1_:_(DYN:T1)_
> http://postmaster.info.aol.com/errors/421dynt1.html/

Also, I see this is a greeting failure, and a deferral. Does this
message eventually get delivered?

Andy


vahid.moghaddasi at gmail

Nov 24, 2011, 11:04 AM

Post #11 of 18 (2007 views)
Permalink
Re: [Bulk] Re: DKIM for AOL [In reply to]

On Thu, Nov 24, 2011 at 1:48 PM, Andy Bradford <
amb-sendok-1324752518.lcddbdjmacehgebkdlib [at] bradfords> wrote:

>
> Yes, the URL is actually valid, and it says:
>
> 421 DYN:T1
>
> * The IP address you are sending from has been temporarily rate
> limited due to lack of whitelisting, unexpected changes in volume,
> or poor IP reputation.
>
> Have you asked to be whitelisted or have your volume threshold
> increased? If your email to their users is expected and wanted by them,
> and you can show proof of this, then maybe you could use that as
> leverage to AOL. Has AOL claimed that by implementing DKIM that this 421
> DYN:T1 problem will be resolved?
>
Yes we did ask them to whitelist us and gave them all of our IP addresses
and that
is how we have been sending them e-mails for many years.
AOL claims that if we implement DKIM, we will have no problem sending them
e-mails.
We don't send advertising e-mails, these are our customers and e-mails
which
they expect to receive from us. We have done all we could with AOL office
to
accept our mails but no luck. DKIM is what they want.

>
> > 2011-11-23 13:24:08.953713500 delivery 1: deferral:
> >
> Connected_to_64.12.90.33_but_greeting_failed./Remote_host_said:_421_4.7.1_:_(DYN:T1)_
> > http://postmaster.info.aol.com/errors/421dynt1.html/
>
> Also, I see this is a greeting failure, and a deferral. Does this
> message eventually get delivered?
>
> No they don't. They finally bounce back to us. Last month we negotiated
with AOL to accept our mail
without DKIM for once more and they did but no more. They did not show us
any evidence that
spammers are using our domain names to send aol users e-mail so I don't
understand why they
need us to do DKIM?


ma1l1ists at yahoo

Nov 25, 2011, 3:46 AM

Post #12 of 18 (2019 views)
Permalink
Re: [Bulk] Re: DKIM for AOL [In reply to]

On Mon, 21 Nov 2011 21:36:31 -0500
Vahid Moghaddasi wrote:

> still don't see anything in the header of the mail going out. In fact, the
> script is never going
> inside the above loop.
> The DKSIGN has the value of /etc/domainkeys/example.com/default when the
> script runs.
> Do I have to do anything with /etc/tcp.smtp? I didn't touch it.

No

have you compared the section following
#First, figure out who the sending domain is.
Try replacing the if loops. Have you logged the $DOMAIN variable to check it's right.

Do you need subdomain checks, (use a / (find) RFC 4871), if not will reduce the code to inspect.


> - insatall Mail-DKIM perl module
> - install Mail-DomainKeys perl module
> - compile/install libdomainkeys-0.69
> - download dkimverify.pl and dkimsign.pl
> - replace qmail-remote with qmail-remote.sh
> - generate the keys and insert in DNS etc...

You do have qmail-remote.orig in /var/qmail/bin, right?

Have you created the domainkeys with dknew
e.g. /etc/domainkeys/gmail.com/default
cd /etc/domainkeys/gmail.com/
/usr/local/bin/dknewkey default 1024 > /etc/domainkeys/gmail.com/default.pub
#sed syntax again dependent on GNU sed or not.
/usr/bin/sed -i -e "s/default._domainkey/default._domainkey.gmail.com/" default.pub

If you then get the headers

you'll need to upload the public key to your dns. (< 1536bit (1024 above) should
fit, smaller obviously equals quicker but weaker)

Then you should get something like this on your outgoing

DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gmail.com; h=date:from:to
:subject:message-id:mime-version:content-type
:content-transfer-encoding; s=default; bh=/edzoYuyn17WXm8KeqcX/R
+khdQ=; b=g6aZr9xfhaVEUk6GdomOEhWrAqhNNKb/

DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=default; d=gmail.com;
b=KxwalhSBZf/hzgTdVeGM2Ndg

And in a Yahoo inbox

Authentication-Results: mta1097.mail.ukl.yahoo.com from=gmail.com; domainkeys=pass (ok); from=gmail.com; dkim=pass (ok)


niamh at fullbore

Nov 25, 2011, 4:56 AM

Post #13 of 18 (1978 views)
Permalink
Re: [Bulk] Re: DKIM for AOL [In reply to]

Hello Vahid,

Thursday, November 24, 2011, 7:04:21 PM, you wrote:

VM> AOL claims that if we implement DKIM, we will have no problem sending them e-mails.

As they're deferring before the message is sent how do they know if
it's signed or not?

--
Best regards,
Niamh mailto:niamh [at] fullbore


vahid.moghaddasi at gmail

Nov 25, 2011, 6:50 AM

Post #14 of 18 (1984 views)
Permalink
Re: [Bulk] Re: DKIM for AOL [In reply to]

On Fri, Nov 25, 2011 at 7:56 AM, Niamh Holding <niamh [at] fullbore> wrote:

> VM> AOL claims that if we implement DKIM, we will have no problem sending
> them e-mails.
>
> As they're deferring before the message is sent how do they know if
> it's signed or not?
>
>
>
Hi Niamh,
Hmm, I don't know that? But they accept a few e-mails then they give this
error. I guess, after a few hours, then they again accept a few mails then
give error. But in any case the e-mail to aol.com will mostly fail.
I created a free AOL e-mail account a few days ago and am able to send
e-mails to it from the qmail server, one at a time but they all land in
spam folder.
Thanks,


vahid.moghaddasi at gmail

Nov 25, 2011, 7:47 AM

Post #15 of 18 (1990 views)
Permalink
Re: [Bulk] Re: DKIM for AOL [In reply to]

On Fri, Nov 25, 2011 at 6:46 AM, Kevin Chadwick <ma1l1ists [at] yahoo>wrote:

> .
> have you compared the section following
> #First, figure out who the sending domain is.
> Try replacing the if loops. Have you logged the $DOMAIN variable to check
> it's right.
>
> Do you need subdomain checks, (use a / (find) RFC 4871), if not will
> reduce the code to inspect.
>
>
> You do have qmail-remote.orig in /var/qmail/bin, right?
>
> Sure, mail does go out just DKIM tag is not there.


> Have you created the domainkeys with dknew
> e.g. /etc/domainkeys/gmail.com/default
> cd /etc/domainkeys/gmail.com/
> /usr/local/bin/dknewkey default 1024 > /etc/domainkeys/
> gmail.com/default.pub
> #sed syntax again dependent on GNU sed or not.
> /usr/bin/sed -i -e "s/default._domainkey/default._domainkey.gmail.com/"
> default.pub
>
> I didn't do that, I followed the instruction on this site:
http://domainkeys.sourceforge.net/keygen.html
the permission and owner in /etc/domainkeys/@DOMAIN is:

-rw------- 1 qmailq other 692 Nov 23 13:37 default
-rw-r--r-- 1 root other 184 Nov 23 13:51 insert_into_DNS
-rw-r--r-- 1 qmailq other 223 Nov 23 13:37 rsa.public
and what goes into DNS is:
# cat insert_into_DNS
k=rsa; t=y;
p=MHwwDQYJKoZIhvcNAQEBBQADawAwaAJhALib8GhLuOWrHTzYo43/n9nxFuwsvq90+zBTMYA0taMm+zqgYLjcobtM/H6R4yJqxCv2W7avlULvjNcvMuUdZuyZjM+iEaZ0Cr4/R2IbkzfX4VahamvJjcT8f4iqpVMapQIDAQAB;


> you'll need to upload the public key to your dns. (< 1536bit (1024 above)
> should
> fit, smaller obviously equals quicker but weaker)
>
> Then you should get something like this on your outgoing
>
I haven't inserted anything in the DNS yet. I though that is the last step.
The $DOMAIN variable checks ok and is what I have the ssl keys in
/etc/domainkeys/$DOMAIN/default.
Unfortunately, there is no clear instruction on implementing dkim on qmail
and prerequisites before doing that. For example, every document talks
about the selector but none explains what exactly a selector is and does?
Is it a machine? Needs ports to be opened to it?
Thank you very much for your help Kevin.


vahid.moghaddasi at gmail

Nov 25, 2011, 11:26 AM

Post #16 of 18 (1982 views)
Permalink
Re: [Bulk] Re: DKIM for AOL [In reply to]

After adding a few debug lines in the script, I found qmailr is running it
but somewhere
in the instruction it said the owner of the file domainkeys/default must be
qmailq.
I changed the ownership and also, dktest could not find the ssl library in
the LD_LIBRARY_PATH so
I had to link the crypto library in /usr/lib....anyways, now I see the
following in the envelop header when
I sent e-mail to AOL:
"
Comment: DomainKeys? See http://domainkeys.sourceforge.net/
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=default; d=example.com;

b=FUsQybcHLTR6cHooUj8FJWDFPQrSJQeLVSXWRitTP2oCYYCQbtM07U22QJg8Svet1i/pdC3oMLRYHoObwAkLl/RYiC1OyXnebUHLdnqxrGOmGC3RCzm8r3bEyybPsL1K;
h=Received:Date:Message-ID:From:To:Subject;
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=example.com; h=date
:message-id:from:to:subject; s=default; bh=vBRL4hHqMoRrINfe7AfHJ
23sMRg=; b=DSMUjwsBHAqP2s1s1TAiFkJAqm5nCOwJaiFoU3s9MEg0lMroRVtVx
yXzbg0gXOa6tOpxtnWSvkrxY+AyYXKH4DU+qeSZ7jIveNTHye/l/P0WQRI1UBM1U
3HTwcqrGXqd
"
Not sure what the first line is there for?

I guess the next step is to add the following line to my DNS TXT record for
my domain?

k=rsa; t=y;
p=MHwwDQYJKoZIhvcNAQEBBQADawAwaAJhALib8GhLuOWrHTzYo43/n9nxFuwsvq90+zBTMYA0taMm+zqgYLjcobtM/H6R4yJqxCv2W7avlULvjNcvMuUdZuyZjM+iEaZ0Cr4/R2IbkzfX4VahamvJjcT8f4iqpVMapQIDAQAB;
The only problem is that, we send e-mail on behalf of our costumers to
(their)
costumers so we often have to change the sender domain in the header to
reflect
our first costumers. Will that change anything in DKIM? The actual server
who is sending
the mail out has its own domain, can I just hard code that in the script so
it always
loads /etc/domainkeys/example.com/default instead of the masked domain?
All the bounces come back to us so the e-mail know its return path to our
servers.
Thanks again for all the help.


marcus at synchromedia

Nov 25, 2011, 1:47 PM

Post #17 of 18 (1982 views)
Permalink
Re: [Bulk] Re: DKIM for AOL [In reply to]

On 25 Nov 2011, at 20:26, Vahid Moghaddasi wrote:

> The only problem is that, we send e-mail on behalf of our costumers to (their)
> costumers so we often have to change the sender domain in the header to reflect
> our first costumers. Will that change anything in DKIM? The actual server who is sending
> the mail out has its own domain, can I just hard code that in the script so it always
> loads /etc/domainkeys/example.com/default instead of the masked domain?

We do the same. In that situation, we drop the from address from the DKIM signature and sign it with our own key as an intermediary. It doesn't carry as much weight, but at least we are signing in some way which is good for Yahoo and co.

Marcus
--
Marcus Bointon
Synchromedia Limited: Creators of http://www.smartmessages.net/
UK info [at] han CRM solutions
marcus [at] synchromedia | http://www.synchromedia.co.uk/


vahid.moghaddasi at gmail

Nov 26, 2011, 7:04 AM

Post #18 of 18 (1981 views)
Permalink
Re: [Bulk] Re: DKIM for AOL [In reply to]

On Fri, Nov 25, 2011 at 4:47 PM, Marcus Bointon
<marcus [at] synchromedia>wrote:

> We do the same. In that situation, we drop the from address from the
> DKIM signature and sign it with our own key as an intermediary. It doesn't
> carry as much weight, but at least we are signing in some way which is good
> for Yahoo and co.
>
>
Great thanks, I was thinking of feeding control/me or just hard code our
domain in the script but
wasn't sure if that is common practice.

Qmail users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.