Militantly FREE software support.
Militantly FREE software support.
NavigationUser loginSpam?See spam posts on this site? If so, please don't reply to the spam! Instead, just report the URL to the webmaster. |
Can't post to list with mutt/exim4?!Hello, I have got some trouble posting to this list using my prefered MUA mutt But when I use IceDove it works just fine. Here is what I think is happening: Some of the headers are not correctly added respectively removed, when sending Her some more info on my changes: 1. changed the helo_data to reflect my private IP (helo=[192.168.178.20]) as 'helo_data = [192.168.178.20]' 2. removed the local "Message-ID" which exim added by setting: 'headers_remove = "Message-ID"' in the smtp transport. 3. reconfigure exim, so it does not add any "Received:"-header: 'received_header_text = ""' since it contained my fake domain name. So, after doing these changes the headers (the ones I consider relevant) nearly Is there something I missed? Am I completely going to the wrong direction, or Any advise will be much appreciated. Thanks in advance! Regards -- Bookmark/Search this post with: 
|
• Debian Weekly News - Essential reading for any Debian fan. • Documentation - Debian's own authoritative documentation, including installation docs. • FAQ - Got questions about Debian GNU/Linux? • From Windows to Debian - Tips for converting from Windows to Debian GNU/Linux • Package of the Day. • Security - Security information and alerts! • Bug System - Bug tracking and instructions on reporting bugs. • CD Images - Where/how to get Debian GNU/Linux CD images. • Mailing List Subscription - Dozens of Debian-specific support mailing lists! • Mailing List Archives - Searchable archives of Debian's mailing lists. • Free Software Guidelines - Learn Debian's idea of what "free" software really is. • Package Listings - A very valuable tool: searchable, integrated with bug reports. • Apt-Get Sources - Sources for *.debs which are not official Debian packages. • Backports - Unofficial new software packages that have been "back-ported" to work with the Debian stable/official release. • Developer's Corner - Info about the people behind Debian, policies, and how to package *.deb files.
Can't post to list with mutt/exim4?!
On Mon, 29 Jan 2007 17:04:54 +0100
Marcus Blumhagen wrote:
> Some of the headers are not correctly added respectively removed,
> when sending with mutt/exim, so my messages don't get through the
> Spam filter. So I compared the headers provided by icedove to those
What spam filter? You can subscribe to the pseudo-list "whitelist" to
get passed Debian's filters.
[snip headers stuff]
A test mail to yourself is getting through? Did you tell mutt what
address to use? Otherwise it will use something like
user_name@localhost, which your ISP will probably reject (mine does).
Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)
--
Can't post to list with mutt/exim4?!
On Mon, Jan 29, 2007 at 07:10:44PM +0200, Andrei Popescu wrote:
> What spam filter? You can subscribe to the pseudo-list "whitelist" to
> get passed Debian's filters.
Thanks for the hint about the whitelist.
> A test mail to yourself is getting through? Did you tell mutt what
> address to use? Otherwise it will use something like
> user_name@localhost, which your ISP will probably reject (mine does).
Testmails to myself always got through, also mails to other
recipients, as I managed to subscribe to the on this way.
The problem is solved in the meantime. Made a stupid mistake in
configuring exim, it rewrote to many headers.
Regards
Marcus
--
Can't post to list with mutt/exim4?!
On Mon, Jan 29, 2007 at 05:04:54PM +0100 or thereabouts, Marcus Blumhagen wrote:
> Hello,
>
> I have got some trouble posting to this list using my prefered MUA mutt
> (1.5.13-1.1) and MTA exim4-daemon-light (4.63-12).
I'm using pretty much the same setup, and didn't do anything special in regards
to the Debian User list, other than add my e-mail to the whitelist.
> Her some more info on my changes:
>
> 1. changed the helo_data to reflect my private IP (helo=[192.168.178.20])
> as this is the helo sent by icedove, because I am behind a NAT firewall.
> Actually I think this is also not correct, but it seems to work with
> icedove:
>
> 'helo_data = [192.168.178.20]'
>
> 2. removed the local "Message-ID" which exim added by setting:
>
> 'headers_remove = "Message-ID"'
> So, after doing these changes the headers (the ones I consider relevant)
> nearly look the same when sending a message with either icedove or
> mutt/exim.
>
> Is there something I missed? Am I completely going to the wrong direction,
> or did I even overdo? Which additional information do I need to provide?
Yes, I think you're headed in the wrong direction. I never had to do any of the
things in your checklist. As the previous responder suggested, make sure that
mutt is sending out correctly to any e-mail address. I think once mutt sends
out correctly, then add yourself to the debian whitelist as suggested, should
be all that's required to send to the list successfully.
--
Regards
Stephen A.
Encrypted/Signed e-mail accepted (GPG or PGP) -- Key ID: 978BA045
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
"... an experienced, industrious, ambitious, and often quite often
picturesque liar."
-- Mark Twain
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Can't post to list with mutt/exim4?!
On Mon, Jan 29, 2007 at 02:37:38PM -0500, Stephen wrote:
> Yes, I think you're headed in the wrong direction. I never had to do any of the
> things in your checklist. As the previous responder suggested, make sure that
> mutt is sending out correctly to any e-mail address. I think once mutt sends
> out correctly, then add yourself to the debian whitelist as suggested, should
> be all that's required to send to the list successfully.
It really was the wrong direction. It was a misconfigured
headers_rewrite rule.
Anyway, now my exim setup was cleaned up by the way, since many
local parts of the headers got removed.
Regards
Marcus
--
Can't post to list with mutt/exim4?!
On Tue, Jan 30, 2007 at 02:24:16PM +0100, Marcus Blumhagen wrote:
> On Mon, Jan 29, 2007 at 02:37:38PM -0500, Stephen wrote:
> > Yes, I think you're headed in the wrong direction. I never had to do any of the
> > things in your checklist. As the previous responder suggested, make sure that
> > mutt is sending out correctly to any e-mail address. I think once mutt sends
> > out correctly, then add yourself to the debian whitelist as suggested, should
> > be all that's required to send to the list successfully.
>
> It really was the wrong direction. It was a misconfigured
> headers_rewrite rule.
>
> Anyway, now my exim setup was cleaned up by the way, since many
> local parts of the headers got removed.
I went the headers-rewrite route with exim/mutt for a while and just
go myself into more trouble. IIRC, the thing to do is set all your
headers and envelope headers in mutt and then allow
local_sender_retain and put yourself in trusted_users
local_sender_retain = true
trusted_users =
there are surely better ways to do this, or at least more maintainable
ways, but it works for me by allowing local smtp connections (like
from mutt) to retain their headers without exim tacking on local
addresses and such. There will still be evidence of the local machine
(just look at my headers), but the froms, env froms etc are all set by
mutt.
hth
A
Can't post to list with mutt/exim4?!
On Tue, 30 Jan 2007 08:02:47 -0800
Andrew Sackville-West wrote:
> I went the headers-rewrite route with exim/mutt for a while and just
> go myself into more trouble. IIRC, the thing to do is set all your
> headers and envelope headers in mutt and then allow
> local_sender_retain and put yourself in trusted_users
>
> local_sender_retain = true
> trusted_users =
>
> there are surely better ways to do this, or at least more maintainable
> ways, but it works for me by allowing local smtp connections (like
> from mutt) to retain their headers without exim tacking on local
> addresses and such. There will still be evidence of the local machine
> (just look at my headers), but the froms, env froms etc are all set by
> mutt.
The advantage of doing the rewrite in the MTA is that you don't need to
configure each MUA separately (I use Sylpheed-Claws-GTK2 and have
muttng as backup).
Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)
--
Can't post to list with mutt/exim4?!
On Tue, Jan 30, 2007 at 10:10:49PM +0200, Andrei Popescu wrote:
> On Tue, 30 Jan 2007 08:02:47 -0800
> Andrew Sackville-West wrote:
>
> > I went the headers-rewrite route with exim/mutt for a while and just
> > go myself into more trouble. IIRC, the thing to do is set all your
> > headers and envelope headers in mutt and then allow
> > local_sender_retain and put yourself in trusted_users
> >
> > local_sender_retain = true
> > trusted_users =
> >
> > there are surely better ways to do this, or at least more maintainable
> > ways, but it works for me by allowing local smtp connections (like
> > from mutt) to retain their headers without exim tacking on local
> > addresses and such. There will still be evidence of the local machine
> > (just look at my headers), but the froms, env froms etc are all set by
> > mutt.
>
> The advantage of doing the rewrite in the MTA is that you don't need to
> configure each MUA separately (I use Sylpheed-Claws-GTK2 and have
> muttng as backup).
that makes sense, though I could never get it right. Haven't tried in
a while though. Meanwhile, ISTM that many of the popular GUI MUA's
have a setup that makes it trivial for the user to set the from
address etc that they would like seen by the outside world. And I
imagine that would be the default behaviour of many people setting up
an MUA for the first time. The result is the MUA is spitting out
emails with a from "Me@myisp.com" instead of
"me@mydebianbox.fakedomain.tld" needing rewrite in the MTA to
"me@myisp.com". Of course all my experience is in a smarthost type of
arrangement with a very limited home network behind the local MTA that
connects to those smarthosts.
A
Can't post to list with mutt/exim4?!
On Tue, 30 Jan 2007 12:27:46 -0800
Andrew Sackville-West wrote:
> On Tue, Jan 30, 2007 at 10:10:49PM +0200, Andrei Popescu wrote:
> > On Tue, 30 Jan 2007 08:02:47 -0800
> > Andrew Sackville-West wrote:
> >
> > > I went the headers-rewrite route with exim/mutt for a while and
> > > just go myself into more trouble. IIRC, the thing to do is set
> > > all your headers and envelope headers in mutt and then allow
> > > local_sender_retain and put yourself in trusted_users
> > >
> > > local_sender_retain = true
> > > trusted_users =
> > >
> > > there are surely better ways to do this, or at least more
> > > maintainable ways, but it works for me by allowing local smtp
> > > connections (like from mutt) to retain their headers without exim
> > > tacking on local addresses and such. There will still be evidence
> > > of the local machine (just look at my headers), but the froms,
> > > env froms etc are all set by mutt.
> >
> > The advantage of doing the rewrite in the MTA is that you don't
> > need to configure each MUA separately (I use Sylpheed-Claws-GTK2
> > and have muttng as backup).
>
> that makes sense, though I could never get it right. Haven't tried in
I'm using postfix. The changes are very simple and well documented.
Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)
--
Can't post to list with mutt/exim4?!
On Tue, Jan 30, 2007 at 08:02:47AM -0800, Andrew Sackville-West wrote:
> I went the headers-rewrite route with exim/mutt for a while and just
> go myself into more trouble. IIRC, the thing to do is set all your
> headers and envelope headers in mutt and then allow
> local_sender_retain and put yourself in trusted_users
>
> local_sender_retain = true
> trusted_users =
Thanks for the hint, I'll try that setup. But as I am really lazy and
have only one mail address anyway it was easier than entering the
proper address in. Didn't bother to change muttrc. Also the time I
needed it I found it hard to get caff running without the need to
rewrite headers.
> There will still be evidence of the local machine
One can remove those to. For me it is sufficient to use
headers_remove = Message-ID:Received
Couldn't see any evidence of the local machine in my test mails'
headers.
Regards
Marcus
Can't post to list with mutt/exim4?!
On Mon, Jan 29, 2007 at 05:04:54PM +0100, Marcus Blumhagen wrote:
> Hello,
>
> I have got some trouble posting to this list using my prefered MUA mutt
> (1.5.13-1.1) and MTA exim4-daemon-light (4.63-12).
>
> But when I use IceDove it works just fine.
Then your MTA (exim4) looks like its working fine.
> Here is what I think is happening:
>
> Some of the headers are not correctly added respectively removed, when
> sending with mutt/exim, so my messages don't get through the Spam filter.
> So I compared the headers provided by icedove to those of exim and did some
> changes to my exim-config, so they now look pretty similar.
Can you send a local mail to yourself from mutt?
Can you send a mail to yourself via the internet from mutt?
You should get a message back from your ISP's MTA if it doesn't work
which should provide a clue as to what the problem is.
Could be a setting in your .muttrc.
For example I have:
# Uncomment if some MTA's reject mail :-(
#set use_envelope_from=yes
#set envelope_from_address="username@yourisp.mumble"
But it works fine for me commented, but I think you will need
alternates "username@yourisp.mumble"
Also check /etc/exim4/email-addresses and make sure you are added there.
Post back if still having problems.
--
Chris.
======
" ... the official version cannot be abandoned because the implication of
rejecting it is far too disturbing: that we are subject to a government
conspiracy of `X-Files' proportions and insidiousness."
Letter to the LA Times Magazine, September 18, 2005.
--