James Platt wrote on 01/19/2018 12:27 PM:
in a properly configured (in my opinion) email client, a lot of HTML
features will be disabled for security reasons, including such things
as cookies, javascript and remote images...
Agreed to all of that, and you also want to disable "non-remote" ima
>
> (And is the html thing really that big a deal?)
>
>
> It's likely that part of the reason they were caught in a spam trap was
> because they were HTML and formatted with both very large font and half a
> dozen different colors. Also, as George points out, HTML formatting gets
> fouled up
On Fri, Jan 19, 2018 at 9:45 AM, Robby Findler
wrote:
> On Fri, Jan 19, 2018 at 8:30 AM, David Storrs
> wrote:
> > #2: Please stop spamming the list with slightly divergent items on a
> given
> > subject. Keep it confined to one subject line so that Gmail and the
> Google
> > Group will thread
I see a number of very minor issues in your code:
1) It looks like you have wrapped the keyword arguments in square brackets.
These aren’t necessary. They’re used in the documentation to indicate optional
elements.
2) It’s worth noting that these arguments are optional, so you can leave out,
On Fri, Jan 19, 2018 at 8:30 AM, David Storrs wrote:
> #2: Please stop spamming the list with slightly divergent items on a given
> subject. Keep it confined to one subject line so that Gmail and the Google
> Group will thread the discussion properly. That way everyone can benefit
> from it in t
Hi MHE,
Quick requests:
#1: Could you please not send HTML-formatted emails? They're ugly and
distracting. Keep it to plain text unless it's essential.
#2: Please stop spamming the list with slightly divergent items on a given
subject. Keep it confined to one subject line so that Gmail and t
*Hello Rackets,(require net/smtp)(smtp-send-message "smtpATserver.de"
"senderATmailadress.de"
"receiverATmailadress.de"
"NEW MESSAGE SMTP !"
7 matches
Mail list logo
