You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by "Dan Mahoney, System Admin" <da...@prime.gushi.org> on 2004/10/27 21:27:50 UTC
AOL Scomp Emails
Hey all,
I just started getting AOL's SCOMP emails, and after a little twiddling to
keep them from getting seen as spam by SpamAssassin, I've found a couple
issues with them. I was wondering if anyone else had these issues, and if
anyone knew of any easy way around them.
1) AOL seems to like to leave the "To:" header set to
undisclosed_recipients@aol.com rather than setting it explicitly to the
email address you've registered for the scomp -- apparently they bcc your
email address. This causes it to set off spam filters big time. My usual
abuse@ whitelist isn't working for this -- I don't know if anyone knows a
human to contact at AOL, but this violates a huge standard AFAIK.
What could I possibly set to find this? I've set up a whitelist_from, but
I have a feeling this will get abused. I'm also not quite sure aol.net
(not .com) has an SPF record set up -- and I feel that in a sitation where
you're expected to blindly trust a "from" address should only be used
where an SPF fail is a valid reason for a reject. I've already had stupid
spammers find my abuse box, but I don't dare to think how bad it would be
if there was an address were were EXPECTING to get bcc'd emails from.
2) This is more a pine issue than anything else, but it seems when you're
viewing attached messages in pine, they're only seen in their "standard"
form (i.e. there is NO way) to view full headers for an attachment, other
than viewing the raw source of the message itself, complete with all MIME
boundaries). I'll write the pine dev-team on this, but I'm noting it here
in case anyone seems to have similar issues.
-Dan
--
"You can't call yourself a dork if you don't use UNIX!"
-Dan Mahoney, May 1997
--------Dan Mahoney--------
Techie, Sysadmin, WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144 AIM: LarpGM
Site: http://www.gushi.org
---------------------------
Re: AOL Scomp Emails
Posted by "Dan Mahoney, System Admin" <da...@prime.gushi.org>.
On Wed, 27 Oct 2004, Bart Schaefer wrote:
Here's the problem. I had the "enable-full-header-and-text" option set.
All good now, thanks.
-Dan
> On Wed, 27 Oct 2004 16:06:41 -0400 (EDT), Dan Mahoney, System Admin
> <da...@prime.gushi.org> wrote:
> > When I'm viewing full headers there is no attachment screen -- the whole
> > raw message is before me. Know if this is a tunable?
>
> In (m)ain -> (s)etup -> (c)onfig, scroll down to "Viewer Preferences"
> and select enable-msg-view-attachments
>
--
"GO HOME AND COOK!!!"
Donielle Cocossa, Taco Bell, 2:30 AM
--------Dan Mahoney--------
Techie, Sysadmin, WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144 AIM: LarpGM
Site: http://www.gushi.org
---------------------------
Re: AOL Scomp Emails
Posted by "Dan Mahoney, System Admin" <da...@prime.gushi.org>.
On Wed, 27 Oct 2004, Bart Schaefer wrote:
> On Wed, 27 Oct 2004 16:06:41 -0400 (EDT), Dan Mahoney, System Admin
> <da...@prime.gushi.org> wrote:
>> When I'm viewing full headers there is no attachment screen -- the whole
>> raw message is before me. Know if this is a tunable?
>
> In (m)ain -> (s)etup -> (c)onfig, scroll down to "Viewer Preferences"
> and select enable-msg-view-attachments
>
Nope, still no good. What that does for me is essentiall embeds the "view
attachments" into the main body of the message. Neither the "view
attachments" screen or the menu at the top is viewable in full header
mode.
--
"There is no right and wrong, there is only fun and boring."
-Fisher Stevens, "Hackers"
--------Dan Mahoney--------
Techie, Sysadmin, WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144 AIM: LarpGM
Site: http://www.gushi.org
---------------------------
Re: AOL Scomp Emails
Posted by Bart Schaefer <ba...@gmail.com>.
On Wed, 27 Oct 2004 16:06:41 -0400 (EDT), Dan Mahoney, System Admin
<da...@prime.gushi.org> wrote:
> When I'm viewing full headers there is no attachment screen -- the whole
> raw message is before me. Know if this is a tunable?
In (m)ain -> (s)etup -> (c)onfig, scroll down to "Viewer Preferences"
and select enable-msg-view-attachments
Re: AOL Scomp Emails
Posted by "Dan Mahoney, System Admin" <da...@prime.gushi.org>.
On Wed, 27 Oct 2004, Bart Schaefer wrote:
> On Wed, 27 Oct 2004 15:27:50 -0400 (EDT), Dan Mahoney, System Admin
> <da...@prime.gushi.org> wrote:
>> 2) This is more a pine issue than anything else, but it seems when you're
>> viewing attached messages in pine, they're only seen in their "standard"
>> form (i.e. there is NO way) to view full headers for an attachment
>
> View full headers in the enclosing message with 'h'.
> Then enter the attachment screen with 'v'.
> Finally, display the message/rfc822 attachment from there.
>
> The full-headers setting from the enclosing message carries over to
> the attached message, but can't be changed while viewing the attached
> message itself.
When I'm viewing full headers there is no attachment screen -- the whole
raw message is before me. Know if this is a tunable?
-Dan
--
"It doesn't matter where I live, because I live in dataspace. That's my
hometown."
-Steve Roberts, Builder of BEHEMOTH
--------Dan Mahoney--------
Techie, Sysadmin, WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144 AIM: LarpGM
Site: http://www.gushi.org
---------------------------
Re: AOL Scomp Emails
Posted by Bart Schaefer <ba...@gmail.com>.
On Wed, 27 Oct 2004 15:27:50 -0400 (EDT), Dan Mahoney, System Admin
<da...@prime.gushi.org> wrote:
> 2) This is more a pine issue than anything else, but it seems when you're
> viewing attached messages in pine, they're only seen in their "standard"
> form (i.e. there is NO way) to view full headers for an attachment
View full headers in the enclosing message with 'h'.
Then enter the attachment screen with 'v'.
Finally, display the message/rfc822 attachment from there.
The full-headers setting from the enclosing message carries over to
the attached message, but can't be changed while viewing the attached
message itself.
Re: AOL Scomp Emails
Posted by "Dan Mahoney, System Admin" <da...@prime.gushi.org>.
On Wed, 27 Oct 2004, Steven W. Orr wrote:
> The solution is not in SA. You need to set up the VERPing. I don't know
> what list manager you're using.
Personally, mailman -- but I'm setting this up more for finding things
like, say, exploited formmail scripts.
> =>2) This is more a pine issue than anything else, but it seems when you're
> =>viewing attached messages in pine, they're only seen in their "standard"
> =>form (i.e. there is NO way) to view full headers for an attachment, other
> =>than viewing the raw source of the message itself, complete with all MIME
> =>boundaries). I'll write the pine dev-team on this, but I'm noting it here
> =>in case anyone seems to have similar issues.
> =>
> =>-Dan
>
> Use the H command to see all headers. To see all the headers of an
> attachment that was, say, forwarded, just hit return while the attachment
> is highlighted.
Doesn't work. See previous email.
--
"She's NOT my girlfriend!"
-Dan Mahoney, Quite a bit recently.
--------Dan Mahoney--------
Techie, Sysadmin, WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144 AIM: LarpGM
Site: http://www.gushi.org
---------------------------
Re: AOL Scomp Emails
Posted by "Steven W. Orr" <st...@syslang.net>.
On Wednesday, Oct 27th 2004 at 15:27 -0400, quoth Dan Mahoney, System Admin:
=>Hey all,
=>
=>I just started getting AOL's SCOMP emails, and after a little twiddling to
=>keep them from getting seen as spam by SpamAssassin, I've found a couple
=>issues with them. I was wondering if anyone else had these issues, and if
=>anyone knew of any easy way around them.
=>
=>1) AOL seems to like to leave the "To:" header set to
=>undisclosed_recipients@aol.com rather than setting it explicitly to the
=>email address you've registered for the scomp -- apparently they bcc your
=>email address. This causes it to set off spam filters big time. My usual
=>abuse@ whitelist isn't working for this -- I don't know if anyone knows a
=>human to contact at AOL, but this violates a huge standard AFAIK.
It looks like you have set up a feedback loop with AOL. But a feedback
loop does you no good without VERPing your messages from your mailinglists
to your aol subscribers.
VERP == Variable Envelope Return Path
When you send to a list of people and 10 of them are @aol.com your MTA
will initiate a single conversation with aol to deliver one copy of the
message to 10 recipients. By VERPing, you cause the message to the 10 aol
recipients to differ by embedding their address into each copy. It slows
you down but allows you to identify who reported you as a spammer.
On my lists, I verp all aol addresses and immediately shut anyone off who
reports me as a spammer. (To get re-enabled they have to talk with me by
phone.)
=>What could I possibly set to find this? I've set up a whitelist_from, but
=>I have a feeling this will get abused. I'm also not quite sure aol.net
=>(not .com) has an SPF record set up -- and I feel that in a sitation where
=>you're expected to blindly trust a "from" address should only be used
=>where an SPF fail is a valid reason for a reject. I've already had stupid
=>spammers find my abuse box, but I don't dare to think how bad it would be
=>if there was an address were were EXPECTING to get bcc'd emails from.
The solution is not in SA. You need to set up the VERPing. I don't know
what list manager you're using.
=>2) This is more a pine issue than anything else, but it seems when you're
=>viewing attached messages in pine, they're only seen in their "standard"
=>form (i.e. there is NO way) to view full headers for an attachment, other
=>than viewing the raw source of the message itself, complete with all MIME
=>boundaries). I'll write the pine dev-team on this, but I'm noting it here
=>in case anyone seems to have similar issues.
=>
=>-Dan
Use the H command to see all headers. To see all the headers of an
attachment that was, say, forwarded, just hit return while the attachment
is highlighted.
--
Time flies like the wind. Fruit flies like a banana. Stranger things have .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net